MSC Nastran 2024.1 Quick Reference Guide
Uploaded by
thanhhoangvan1607MSC Nastran 2024.1 Quick Reference Guide
Uploaded by
thanhhoangvan1607MSC Nastran Quick Reference Guide
MSC Nastran 2024.1
Quick Reference Guide
Corporate Office
Hexagon Manufacturing Intelligence, Inc. UK
78 Portsmouth Road Cedar House
Cobham, Surrey KT11 1HY
Telephone: (+44) 02070686555
Worldwide Web
www.hexagon.com
Support
https://simcompanion.hexagon.com
Disclaimer
Hexagon reserves the right to make changes in specifications and other information contained in this document without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not intended
to be exhaustive or to apply to any particular engineering problem or design. Hexagon assumes no liability or responsibility to any
person or company for direct or indirect damages resulting from the use of any information contained herein.
User Documentation: Copyright 2024 Hexagon AB and/or its subsidiaries. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of Hexagon is prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from Hexagon suppliers. Additional
terms and conditions and/or notices may apply for certain third party software. Such additional third party software terms and
conditions and/or notices may be set forth in documentation and/or at third-party software information (or successor website designated
by Hexagon from time to time).
PCGLSS 8.0, Copyright © 1992-2016, Computational Applications and System Integration Inc. All rights reserved. PCGLSS 8.0 is
licensed from Computational Applications and System Integration Inc.
The Hexagon logo, Hexagon, MSC Software logo, MSC, Dytran, Marc, MSC Nastran, Patran, e-Xstream, Digimat, and Simulating
Reality are trademarks or registered trademarks of Hexagon AB and/or its subsidiaries in the United States and/or other countries.
NASTRAN is a registered trademark of NASA. FLEXlm and FlexNet Publisher are trademarks or registered trademarks of Flexera
Software. All other trademarks are the property of their respective owners.
Use, duplicate, or disclosure by the U.S. Government is subjected to restrictions as set forth in FAR 12.212 (Commercial Computer
Software) and DFARS 227.7202 (Commercial Computer Software and Commercial Computer Software Documentation), as
applicable.
U.S. Patent 9,361,413
May 16, 2024
NA:V2024.1:Z:Z:Z:DC-QRG-PDF
Documentation Feedback
At Hexagon Manufacturing Intelligence, we strive to produce the highest quality documentation and
welcome your feedback. If you have comments or suggestions about our documentation, write to us.
Please include the following information with your feedback:
Document name
Release/Version number
Chapter/Section name
Topic title (for Online Help)
Brief description of the content (for example, incomplete/incorrect information, grammatical
errors, information that requires clarification or more details and so on).
Your suggestions for correcting/improving documentation
Note: The above mentioned e-mail address is only for providing documentation specific
feedback. If you have any technical problems, issues, or queries, please contact Technical
Support.
C O N T E N T S
MSC Nastran Quick Reference Guide
Contents
Contents
Table of Contents
Table of Contents
Preface List of MSC Nastran Guides, xx
Technical Support, xxi
Training and Internet Resources, xxi
1
Executing MSC Nastran Executing MSC Nastran, 2
2
NASTRAN Statement The NASTRAN Statement, 16
NASTRAN 17 AUTOASGN (133) 21
BUFFSIZE (1) 18 TSTAMP (135) 21
F06 (2) 18 QUADINT (141) 21
NLINES (9) 18 SCR300 (142) 21
MAXLINES (14) 18 LOCBULK (143) 21
METIME (20) 18 (144) 22
APP (21) 18 BFGS (145) 22
MACHTYPE (22) 18 FBSMEM (146) 22
DIAGA (25) 18 UWM (147) 22
CONFIG (28) 18 DBVERCHK (148) 22
ADUMi (46 - 54) 18 SCR300DEL (150) 22
HEAT (56) 18 (151) 23
DIAGB (61) 18 DBLAMKD (155) 23
PUNCH (64) 18 (162) 23
MPYAD (66) 18 (166) 23
DCMPOUT(69) 18 LDQRKD (170) 24
DELFF (77) 19 OLDQ4K (173) 24
DBSET 19 Q4TAPER (189) 24
DMAP (82) 19 Q4SKEW (190) 24
F04 (86) 19 TETRAAR (191) 24
RADMTX (87) 19 FRQSEQ (195) 24
RADLST (88) 19 SCRSAVE (196) 24
SMP (107) 19 MINFRONT (198) 25
NEWHESS (108) 20 NSEGADD (200) 25
(109) 20 CORDM (204) 25
BUFFPOOL (114) 20 (205) 25
(119) 20 DCMPSEQ (206) 25
ATTDEL (124) 20 USPARSE (209) 26
NOKEEP (125) 20 PUNCHTYPE (210) 26
SPARSE (126) 20 DISTORT (213) 26
UPDTTIM (128) 20 T3SKEW (218) 26
SMPYAD67 (129) 21 (219) 26
MAXDBSET 21 (220) 26
Main Index
(221) 26 IFPSTAR 33
(253 - 262) 26 MNLQ4C (445) 33
MAXSET (263) 26 (446) 33
QUARTICDLM (270) 26 PARCHILD(449) 34
(273) 27 (451) 34
DBCFACT (274) 27 IFPBUFF(624) 34
(275) 27 NONUPIV (653) 35
SPLINE_METRICS (281) 27 GPU_MIN_RANK (655) 35
MINDEF (303) 27 GPU_MIN_FRONT (656) 35
MPERTURB (304) 27 (662) 35
(309) 27 SEGLOG(664) 36
OLDRBE3 (310) 27 CNTBKCMP(666) 36
TBCMAG (311) 27 (670) 36
INDEX (316) 28 LMFBKCMP(676) 36
XMSG (319) 28 FFOBKCMP(677) 36
OLDDAREA (320) 28 OLDLCNTR(678) 37
RSEQCONT (357) 28 (679) 37
QLHOUL (359) 29 (684) 37
PRTPCOMP (361) 29 RDBOTH(695) 38
STRICTUAI (363) 29 S2SDEF(701) 38
STPFLG (366) 29 HDF5 (702) 39
QRMETH (370) 29 OBEAMS (725) 39
PARAMCHK (372) 29 OLDCCONE (726) 39
TZEROMAX (373) 30 METS2S (727) 39
NOLIN (386) 30 DMP (728) 39
KRYLOV1 (387) 30 N2SDOF (729) 40
KRYLOV2 (388) 30 H5NORDOF(730) 40
KRYLOV3 (389) 30 (738) 40
KRYLOV4 (390) 30 H5MTX (739) 40
KRYLOV5 (391) 30 H5MDL (740) 40
BARMASS (398) 31 ACCSDLSZ(747) 41
DPBLKTOL (402) 31 H5GM34 (751) 41
OP2NEW (403) 31 UDEFGRID(753) 41
DEF_DENS (408) 31 CNTBACK(758) 41
DEF_TECO (410) 31 OP2IMPV(761) 42
DEF_TEIJ (411) 31 IGNBLN(767) 42
DEF_DAMP (412) 31 BLNMEM(768) 42
OPTCOD (413) 32 OPENFSI(776) 42
(414) 32 H5INFO(789) 42
MDAMPEXT(426) 32 STRNCUR(778) 42
OLDTLDMTH (428) 32 CNT101(786) 43
NONLRGAP (431) 32 H5XHH (790) 43
ESLNRO (443) 32 DELTAU(800) 44
(444) 32 OFTDCMP(804) 44
3
File Management Statements Key to Descriptions, 46
The File Management Section (FMS), 47
File Management Statement Summary, 47
File Management Statement Descriptions, 48
File Management Statements, 52
- $, 52 - DBDICT, 67
- ACQUIRE, 53 - DBDIR, 81
- APIM, 54 - DBFIX, 82
- ASSIGN, 55 - DBLOAD, 83
- CONNECT, 63 - DBLOCATE, 86
- DBCLEAN, 66 - DBSETDEL, 89
Main Index
- DBUNLOAD, 90 - INCLUDE, 99
- DBUPDATE, 92 - INIT, 100
- DEFINE, 93 - MEMLIST, 104
- ENDJOB, 96 - PROJ, 105
- EXPAND, 97 - RESTART, 106
4
Executive Control Statements Key to Descriptions, 110
Executive Control Section, 111
Executive Control Statement Summary, 111
Executive Control Statement Descriptions, 112
- $, 113 - GEOMCHECK, 138
- ALTER, 114 - ID, 142
- APP, 117 - INCLUDE, 143
- CEND, 118 - LINK, 144
- COMPILE, 119 - MALTER, 146
- COMPILER, 123 - MODEL_CHECK, 150
- DIAG, 124 - SOL, 153
- DOMAINSOLVER, 128 - SOL 700,ID, 156
- ECHO, 136 - SPARSESOLVER, 168
- ENDALTER, 137 - TIME, 173
5
Case Control Commands Key to Descriptions, 176
The Case Control Section, 177
Case Control Command Descriptions, 177
Case Control Command Summary, 178
Subcase Definition, 178
Data Selection, 179
Output Selection, 184
Superelement Control, 188
Module Control, 189
Miscellaneous, 189
Case Control Commands, 191
- $, 191 - AESYMXZ (Case), 220
- $S700, 192 - AEUXREF (Case), 221
- A2GG (Case), 196 - ANALYSIS (Case), 222
- ACCELERATION (Case), 197 - APRESSURE (Case), 231
- ACFPMRESULT (Case), 200 - AUTOSPC (Case), 232
- ACPOWER (Case), 202 - AUXCASE (Case), 235
- ACTRIM (Case), 204 - AUXMODEL (Case), 236
- ADAMSMNF* (Case), 205 - AVLEXB (Case), 237
- AECONFIG (Case), 216 - AXISYMMETRIC (Case), 243
- AERCONFIG (Case), 217 - B2GG (Case), 244
- AEROF (Case), 218 - B2PP (Case), 245
- AESYMXY (Case), 219 - BC (Case), 246
Main Index
- BCHANGE (Case), 247 - FEMCHECK (Case), 370
- BCONCHK (Case), 248 - FLSFSEL (Case), 372
- BCONTACT (Case), 249 - FLSPOUT (Case), 374
- BCMOVE (Case), 253 - FLSTCNT (Case), 377
- BEGIN BULK (Case), 254 - FLUX (Case), 379
- BENDL (Case), 257 - FMETHOD (Case), 380
- BOUTPUT (Case), 259 - FORCE (Case), 381
- BSQUEAL (Case), 261 - FREQUENCY (Case), 384
- CAMPBELL (Case), 262 - FRF (Case), 385
- CLOAD (Case), 263 - GPFORCE (Case), 402
- CMETHOD (Case), 264 - GPKE (Case), 410
- CMSENRGY (Case), 265 - GPRSORT (Case), 412
- COSMSEL (Case), 268 - GPSDCON (Case), 413
- CSSCHD (Case), 269 - GPSTRAIN (Case), 414
- DBSAVE (Case), 270 - GPSTRESS (Case), 416
- DEACTEL (Case), 271 - GROUNDCHECK (Case), 418
- DEFORM (Case), 272 - GUST (Case), 420
- DESGLB (Case), 273 - GVECTOR (Case), 421
- DESMOD (Case), 274 - HADAPT (Case), 422
- DESOBJ (Case), 275 - HARMONICS (Case), 423
- DESSUB (Case), 276 - HDF5DA (Case), 424
- DESVAR (Case), 277 - HDOT (Case), 425
- DISPLACEMENT (Case), 278 - HOUTPUT (Case), 426
- DIVERG (Case), 284 - HTFLOW (Case), 427
- DLOAD (Case), 285 - IC (Case), 428
- DRSPAN (Case), 286 - ICF (Case), 430
- DSAPRT (Case), 287 - IMPERFECT (Case), 432
- DSYM (Case), 289 - INCLUDE (Case), 433
- DYSTIFF (Case), 290 - INTENSITY (Case), 434
- ECHO (Case), 292 - IRLOAD (Case), 435
- EDE (Case), 294 - K2GG (Case), 436
- EKE (Case), 297 - K2PP (Case), 437
- ELAFORCES (Case), 300 - K42GG (Case), 438
- ELSDCON (Case), 302 - LABEL (Case), 439
- ELSENS (Case), 304 - LDLABEL (Case), 440
- ELSUM (Case), 307 - LINE (Case), 441
- ENDSTEP (Case), 309 - LOAD (Case), 442
- ENDTIME (Case), 310 - LOADNAME (Case), 443
- ENDMODULE (Case), 311 - LOADSET (Case), 444
- ENTHALPY (Case), 312 - M2GG (Case), 446
- EQUILIBRIUM (Case), 313 - M2PP (Case), 447
- ERP (Case), 315 - MAPMODES (Case), 448
- ESE (Case), 319 - MASSSET (Case), 450
- EXPORTLD (Case), 323 - MASTER (Case), 451
- EXTDRIN (Case), 325 - MAXLINES (Case), 453
- EXTDROUT (Case), 334 - MAXMIN (Case), 454
- EXTMDOUT (Case), 336 - MAXMIN (Case), 456
- EXTSEOUT (Case), 347 - MAXMIN(DEF) (Case), 458
- FATIGUE (Case), 362 - MCFRACTION (Case), 461
- FBODYLD (Case), 369 - MDSET (Case), 464
Main Index
- MEFFMASS (Case), 466 - RELDISP (Case), 562
- METHOD (Case), 468 - REPCASE (Case), 564
- MFLUID (Case), 470 - RESVEC (Case), 565
- MFREQUENCY (Case), 471 - RGYRO (Case), 567
- MODALKE (Case), 475 - RIGID (Case), 568
- MODALSE (Case), 479 - ROTBENT (Case), 570
- MODES (Case), 483 - ROTSEKE (Case), 571
- MODESELECT (Case), 484 - RSDAMP (Case), 573
- MODTRAK (Case), 490 - SACCELERATION (Case), 574
- MONCARL (Case), 490 - SDAMPING (Case), 576
- MONITOR (Case), 492 - SDISPLACEMENT (Case), 578
- MPC (Case), 494 - SEALL (Case), 580
- MPCFORCES (Case), 495 - SEDAMP (Case), 581
- MPRES (Case), 498 - SEDR (Case), 582
- NHRMITR (Case), 499 - SEDV (Case), 583
- NLBUCK (Case), 500 - SEEXCLUDE (Case), 584
- NLHARM (Case), 502 - SEFINAL (Case), 586
- NLIC (Case), 503 - SEKREDUCE (Case), 587
- NLLOAD (Case), 505 - SELGENERATE (Case), 588
- NLOPRM (Case), 506 - SELREDUCE (Case), 589
- NLPARM (Case), 510 - SEMGENERATE (Case), 590
- NLRESTART (Case), 511 - SEMREDUCE (Case), 591
- NLSTEP (Case), 514 - SERESP (Case), 592
- NLSTRESS (Case), 515 - SET (Case), 593
- NONLINEAR (Case), 517 - SETP (Case), 595
- NOUTPUT (Case), 518 - SETS DEFINITION (Case), 596
- NSM (Case), 519 - SKIP (Case), 597
- NVELOCITY (Case), 520 - SLDSKIN (Case), 598
- ODSFREQ (Case), 522 - SMETHOD (Case), 599
- OFREQUENCY (Case), 523 - SOLUTION (Case), 600
- OIMPERFECT (Case), 525 - SPC (Case), 601
- OLOAD (Case), 526 - SPCFORCES (Case), 602
- OMODES (Case), 529 - SPLINOUT (Case), 605
- OTIME (Case), 531 - STATSUB (Case), 606
- OUTPUT (Case), 533 - STEP (Case), 608
- P2G (Case), 534 - STOCHASTICS (Case), 609
- PACCELERATION (Case), 535 - STRAIN (Case), 610
- PAGE (Case), 537 - STRESS (Case), 614
- PARAM (Case), 538 - STRFIELD (Case), 618
- PARTN (Case), 539 - SUBCASE (Case), 619
- PEAKOUT (Case), 540 - SUBCOM (Case), 620
- PFGRID (Case), 542 - SUBSEQ (Case), 622
- PFMODE (Case), 544 - SUBSEQ1 (Case), 623
- PFPANEL (Case), 548 - SUBSTEP (Case), 624
- PLOTID (Case), 552 - SUBTITLE (Case), 626
- POST (Case), 553 - SUPER (Case), 627
- PRESSURE (Case), 557 - SUPORT1 (Case), 629
- RANDOM (Case), 558 - SVECTOR (Case), 630
- RANDOUT (Case), 559 - SVELOCITY (Case), 631
- RCROSS (Case), 560 - SYM (Case), 633
Main Index
- SYMCOM (Case), 634 - TRIMGRP (Case), 653
- SYMSEQ (Case), 635 - TSTEP (Case), 655
- TACCELERATION (Case), 636 - TSTEPNL (Case), 656
- TDISPLACEMENT (Case), 638 - TSTRU (Case), 657
- TEMPERATURE (Case), 640 - TVELOCITY (Case), 658
- TFL (Case), 644 - UNGLUE (Case), 660
- THERMAL (Case), 645 - VCCT (Case), 661
- TITLE (Case), 647 - VECTOR (Case), 662
- TIRE (Case), 648 - VELOCITY (Case), 663
- TPASET (Case), 649 - VINTENSITY (Case), 666
- TRIM (Case), 650 - WEIGHTCHECK (Case), 669
- TRIMF (Case), 651 - WETSENS (Case), 671
Case Control Applicability Tables, 672
X-Y PLOT Commands, 686
X-Y Output Command Summary, 686
- ALLEDGE TICS, 690 - XTITLE, 724
- BALL EDGE TICS, 691 - XYPAPLOT, 725
- BLEFT TICS, 692 - XYPEAK, 726
- BRIGHT TICS, 693 - XYPLOT, 727
- CAMERA, 694 - XYPRINT, 733
- CLEAR, 695 - XYPUNCH, 734
- CSCALE, 696 - XVALUE PRINT SKIP, 735
- CURVELINESYMBOL, 697 - YAXIS, 736
- DENSITY, 698 - YBDIVISIONS, 737
- LEFT TICS, 699 - YBINTERCEPT, 738
- LONG, 700 - YBGRID LINES, 739
- LOWER TICS, 701 - YBLOG, 740
- PENSIZE, 702 - YBMAX, 741
- PLOTTER, 703 - YBMIN, 742
- RIGHT TICS, 704 - YBTITLE, 743
- SEPLOT, 705 - YBVALUE PRINT SKIP, 744
- SEUPPLOT, 706 - YDIVISIONS, 745
- TALL EDGE TICS, 707 - YINTERCEPT, 746
- TCURVE, 708 - YGRID LINES, 747
- TLEFT TICS, 709 - YLOG, 748
- TRIGHT TICS, 710 - YMAX, 749
- UPPER TICS, 711 - YMIN, 750
- XAXIS, 712 - YPAPER, 751
- XBAXIS, 713 - YTAXIS, 752
- XBGRID LINES, 714 - YTDIVISIONS, 753
- XDIVISIONS, 715 - YTGRID LINES, 754
- XGRID LINES, 716 - YTINTERCEPT, 755
- XINTERCEPT, 717 - YTITLE, 756
- XLOG, 718 - YTLOG, 757
- XMAX, 719 - YTMAX, 758
- XMIN, 720 - YTMIN, 759
- XPAPER, 721 - YTTITLE, 760
- XTAXIS, 722 - YTVALUE PRINT SKIP, 761
- XTGRID LINES, 723 - YVALUE PRINT SKIP, 762
Main Index
OUTPUT(POST) Commands, 763
- SURFACE, 763 - VOLUME, 766
OUTPUT(PLOT) Commands, 768
- AXES, 770 - PERSPECTIVE, 785
- CAMERA, 772 - PLOT, 786
- CONTOUR, 773 - PLOTTER, 794
- CSCALE, 775 - PROJECTION, 795
- DISTORTION, 776 - PTITLE, 796
- FIND, 777 - SCALE, 797
- MAXIMUM DEFORM, 779 - SEPLOT, 798
- OCULAR SEPARATION, 780 - SET, 799
- ORIGIN, 781 - SEUPPLOT, 802
- ORTHOGRAPHIC, etc., 782 - STEREOSCOPIC, 803
- PAPER SIZE, 783 - VANTAGE POINT, 804
- PEN, 784 - VIEW, 805
6
Parameters Parameter Descriptions, 808
- ACEXTMTD, 808 - ARF, 815
- ACEXTSET, 808 - ARS, 815
- ACMPF, 808 - ASCOUP, 815
- ACOUT, 808 - ASING, 815
- ACOWEAK, 809 - AUNITS, 816
- ACSYM, 809 - AUTOADJ, 816
- ACTDMP, 809 - AUTOGOUT, 816
- ACTSMP, 809 - AUTOMSET, 817
- ACTMEM, 810 - AUTOQSET, 817
- ADJMETH, 810 - AUTOSPC, 818
- ADMEXTU, 810 - AUTOSPCR, 818
- ADMPOST, 810 - AUTOSPRT, 818
- ADPCON, 810 - BAILOUT, 819
- ADSTAT, 811 - BEAMBEA, 819
- AERODOF, 811 - BEIGRED, 819
- AESDISC, 811 - BIGER, BIGER1, BIGER2, BIGER3, 819
- AESMAXIT, 811 - BUCKLE, 819
- AESMETH, 811 - BUSHNM, 819
- AESRNDM, 811 - BWKD, 820
- AESTOL, 812 - CASIEMA, 820
- AGGROT, 812 - CASIMEST, 821
- ALPHA1, ALPHA2, 812 - CASPIV, 821
- ALPHA1FL, ALPHA2FL, 813 - CB1, CB2, 821
- ALTRED, 814 - CDIF, 821
- ARBMASP, 814 - CDITER, 821
- ARBMFEM, 814 - CDPCH, 822
- ARBMNOW, 814 - CDPRT, 822
- ARBMPS, 814 - CFDIAGP, 822
- ARBMSS, 815 - CFRANDEL, 822
- ARBMSTYP, 815 - CHECKOUT, 822
Main Index
- CHKCOND, 823 - ERPC, 840
- CK1, CK2, 824 - ERPREFDB, 840
- CK3, 824 - ERPRHO, 840
- CLEANVEC, 824 - ERPRLF, 840
- CLNVCTOL, 824 - ERROR, 840
- CLOSE, 824 - ESLFSAV, 840
- CM1, CM2, 825 - ESLMOVE, 841
- COMPMATT, 825 - ESLLCOMP, 841
- CONFAC, 826 - ESLMPC1, 841
- COSUBCYC, 826 - ESLOPTEX, 842
- COSUBMAX, 826 - ESLPRT, 842
- COUPMASS, 827 - ESLPRT1, 842
- CP1, CP2, 827 - ESLRCF,user_rc_file, 843
- CQC, 827 - ESLTOPCV, 843
- CURV, 827 - ESLUNT2, 843
- CURVPLOT, 830 - ESLUNT1, 843
- CWDIAGP, 831 - EST, 843
- CWRANDEL, 831 - EULBND, 843
- DAMPTOL, 831 - EULSTRES, 844
- DBALL, 831 - EUSUBCYC, 845
- DBCCONV, 832 - EXCLUDE, 845
- DBCDIAG, 832 - EXTDR , 846
- DBCOVWRT, 832 - EXTDROUT , 846
- DBDICT, 832 - EXTDRUNT, 846
- DBDN, 833 - EXTOUT, 846
- DBDRPRJ, 833 - EXTRCV, 846
- DBDRVER, 833 - EXTUNIT, 846
- DBEXT, 833 - F2, 847
- DBRCV, 833 - FACTOR, 847
- DBUP, 833 - FASTFR, 847
- DDRMM, 833 - FBATOLR, 847
- DELCLUMP, 833 - FBLEND, 847
- DESPCH, 834 - FDRLDS, 848
- DESPCH1, 834 - FIRSTKI, 848
- DFREQ, 835 - FIXEDB, 848
- DIROUT, 835 - FKSYMFAC, 849
- DOPT, 835 - FLEXINCR, 850
- DPEPS, 835 - FLUIDMP, 850
- DPHFLG, 836 - FLUIDNE, 850
- DSNOKD, 836 - FLUIDSE, 851
- DSO, 837 - FMULTI, 851
- DSZERO, 837 - FOLLOWK, 851
- DV3PASS, 837 - FRQDEPO, 851
- DYNSPCF, 837 - FREQTOL, 851
- EIGFILT, 837 - FULLSEDR, 852
- ENFMETH, 837 - FZERO, 852
- ENFMOTN, 838 - G, GFL, 852
- EPPRT, 839 - GEOMU, 852
- EPSILONT, 839 - GPECT, 852
- EPZERO, 840 - GRADMESH, 852
Main Index
- GRAVSET, 853 - MECHPRT, 867
- GRDPNT, 853 - MESH, 867
- GUSTAERO, 854 - METHCMRS, 867
- GYROAVG, 854 - MHRED, 867
- GYROFATL, 854 - MICRO , 867
- HEATSTAT, 854 - MIDNODE , 868
- HFREQ, HFREQFL, 855 - MINIGOA, 868
- HTOCITS, 855 - MINORTHO, 868
- HTOCPRT, 855 - MINORTHR, 869
- HTOCTOL, 855 - MMFIL, 869
- HTSYM, 855 - MMMETH, 869
- ICOPT, 856 - MODACC, 869
- IFP, 856 - MODEL, 869
- INREL, 856 - MP1SET, 869
- INRLM, 857 - MPCX, 870
- IRES, 857 - MPTUNIT, 870
- ITAPE, 857 - MSG10625, 870
- IUNIT, 857 - MXICODE0, 871
- IEVLOCK, 858 - MXLAGM1, 871
- JWLDET, 858 - NASPRT, 871
- KDAMP, KDAMPFL, 858 - NDAMP, NDAMPM, 871
- KDIAG, 858 - NEWMARK, 873
- KDMFILT, 859 - NFDOPTS, 873
- K4RITZ, 860 - NHPLUS, 873
- K6ROT, 860 - NINTPTS, 873
- LANGLE, 861 - NLAYERS, 873
- LDSUM, 861 - NLHTLS, 873
- LFREQ, LFREQFL, 862 - NLHTOL, 873
- LGDISP, 862 - NLHTWK, 874
- LMFACT, 863 - NLMAX, 874
- LMODES, LMODESFL, 863 - NLMIN, 874
- LOADU, 864 - NLPACK, 874
- LOOPID, 864 - NLTOL, 875
- LSTRN, 864 - NMLOOP, 875
- MACH, 864 - NMNLFRQ, 876
- MAXACCPT, 864 - NOCOMPS, 876
- MAXAPL, 864 - NODCMP, 876
- MAXCOND, 864 - NOELOF, 876
- MAXDAMP, 865 - NOELOP, 877
- MAXLP, 865 - NOGPF, 877
- MAXMECHS, 865 - NONCUP, 877
- MAXRATIO, 865 - NQSET, 877
- MDK4OPT, 865 - NUMOUT, NUMOUT1, NUMOUT2,
- MDOPT14, 866 NUMOUT3, 877
- MDOTM, 866 - OELMOPT, 878
- MDOTMFAC, 866 - OELMSET , 878
- MDREDOPT, 866 - OG, 878
- MECHFIL, 866 - OGEOM, 878
- MECHFIX, 866 - OGRDOPT, 878
- MECHOUT, 867 - OGRDSET, 878
Main Index
- OLDSEQ, 879 - PRPJ, 897
- OLDWELD, 881 - PRPHIVZ, 897
- OMACHPR, 881 - PRTMAXIM, 897
- OMAXR, 881 - PRTRESLT, 898
- OMID, 881 - PSENPCH, 898
- OMSGLVL, 882 - PTHRES, 898
- OP2GM34, 882 - Q, 898
- OP4DIGS, 882 - RADMOD, 898
- OPCHSET, 882 - RBSETPRT, 898
- OPGEOM, 882 - REMZERO, 898
- OPGTKG, 883 - RESLTOPT, 898
- OPPHIB, 883 - RESVEC, 899
- OPPHIPA, 883 - RFORSET, 899
- OPTEXIT, 883 - RHOCP, 899
- OPTION, 884 - RIMINTP, 899
- OSETELE, 884 - RKSCHEME , 899
- OSETGRD, 884 - RMSINT, 900
- OSWELM, 884 - RMSPRMDS, 900
- OSWPPT, 885 - ROHYDRO , 900
- OUGCORD, 885 - ROMULTI , 901
- OUGSPLIT, 885 - ROSTR , 902
- OUNIT1, 885 - RSPECTRA, 902
- OUNIT2, 886 - RSPRINT, 902
- OUTOPT, 886 - RSTTEMP, 903
- PACINFID, 886 - RVLDFILT, 903
- PANELMP, 886 - S1, S1G, S1M, 903
- PATPLUS, 886 - S1AG,S1AM, 905
- PATVER, 886 - SBSPFORM, 905
- PCOMPRM, 886 - SCRSPEC, 905
- PDRMSG, 887 - SDCSV, 906
- PEMDMP, 887 - SDUNIT,n, 906
- PEMFRIM, 887 - SEKD, 906
- PEMMAPC, 887 - SEMAP, SEMAPOPT, SEMAPPRT, 907
- PEMNCOP4, 888 - SENSUOO, 908
- PEMNPART, 888 - SEP1XOVR, 908
- PEMSKIN, 889 - SEQOUT, 908
- PENFN, 889 - SERST, 908
- PERCENT, 889 - SESDAMP, 909
- PH2OUT, 889 - SESEF, 910
- PKRSP, 889 - SHIFT1, 910
- PLTMSG, 889 - SHLDAMP, 910
- POST, 890 - SIGMA, 910
- POSTEXT, 895 - SKINOUT, 911
- POSTADF, 896 - SKPAMP, 911
- POSTU, 896 - SLOOPID, 911
- PREFDB, 896 - SMALLQ, 911
- PRGPST, 896 - SNORM, 911
- PRINT, 897 - SNORMPRT, 912
- PROUT, 897 - SOFTEXIT, 913
- PRPA , 897 - SOLADJC, 913
Main Index
- SOLID, 913 - TOPOCONV, 919
- SPARSEDM, 913 - TRMBIM, 919
- SPARSEDR, 913 - TSTATIC, 919
- SPARSEPH, 914 - UGASC, 919
- SPDRRAT, 914 - UNSYMF, 919
- SPCGEN, 914 - UNSYMKB, 920
- SPDMRAT, 914 - UPDTBSH, 920
- SQSETID, 914 - USETPRT, 920
- SRCOMPS, 915 - USETSEL, 921
- SRTELTYP, 915 - USETSTRi, 921
- SRTOPT, 915 - VARPHI, 922
- START, 915 - VELCUT , 922
- STEPFCT, 915 - VMOPT, 923
- STEPFCTL, 915 - VREF, 923
- STIME, 915 - WHIRLOPT, 923
- STRUCTMP, 916 - WMODAL, 923
- SUBCASID, 916 - WRBEAMB, 924
- SUBID, 916 - WTMASS, 924
- SUPAERO, 916 - W3, W4, W3FL, W4FL, 924
- SUPDOF, 917 - WR3, WR4, WRH, 925
- SUPER, 917 - XFACT, 925
- TABID, 917 - XFACTX, 926
- TABS, 917 - XFLAG, 926
- TDAMP, 917 - XYMPCH, 926
- TESTNEG, 918 - XYUNIT, n, 927
- TFSYMFAC, 918 - ZROCMAS, 927
- TINY, 918 - ZROVEC, 927
- TOLRSC, 918
Parameter Applicability Tables, 928
7
Item Codes Item Code Description, 954
Element Stress (or Strain) Item Codes, 954
CAXIF2 (47) 955 CELAS2 (12) 962
CAXlF3 (48) 955 CELAS3 (13) 962
CAXIF4 (49) 955 CGAP (86) 962
CAXISYM (241) 956 CHEXA (67) 962
CBAR (34) 956 CHEXA (93) 963
CBAR (100) 957 CHEXAFD (202) 964
CBAR (238) 958 CHEXAFD (207) 964
CBEAM (2) 958 CIFHEX (65) 964
CBEAM (94) 958 CIFPENT (66) 965
CBEAM (239) 959 CIFQDX (73) 965
CBEAM3 (184) 959 CIFQUAD (63) 965
CBEND (69) 960 CONROD (10) 966
CBUSH (102) 960 CONROD (92) 966
CBUSH1D (40) 961 CPENTA (68) 966
CCONEAX (35) 961 CPENTA (91) 967
CDUM3 962 CPENTAFD (204) 968
CDUM9 (55-61) 962 CPENTAFD (209) 968
CELAS1 (11) 962 CPYRAM (242) 969
Main Index
CPYRAM (242) 970 CTETRA (39) 977
CQUAD4 (33) 970 CTETRA (85) 978
CQUAD4 (90) 971 CTETRAFD (205) 978
CQUAD42 (95) 971 CTETRAFD (210) 978
CQUAD4 (144) 972 CTRIA3 (74) 979
CQUAD8 (64) 973 CTRIA32 (97) 979
CQUAD82 (96) 973 CTRIA3 (88) 979
CQUADFD (201) 974 CTRIA6 (75) 979
CQUADFD (208) 974 CTRIA62 (98) 979
CQUADR (82) 974 CTRIAFD (206) 979
CQUADR (172) 974 CTRIAFD (211) 980
CQUADR (232) 974 CTRlAR (70) 980
CQUADX(18) 975 CTRIAR (173) 980
CQUADXFD (214) 975 CTRIAR (233) 980
CQUADXFD (215) 976 CTRIAX(17) 980
CROD (1) 976 CTRIAX6 (53) 980
CROD (89) 976 CTRIAXFD (212) 981
CSHEAR (4) 976 CTRIAXFD (213) 981
CSLOT3 (50) 976 CTUBE (3) 981
CSLOT4 (51) 976 CTUBE (87) 981
Element Force Item Codes, 982
CWELDP 982 CGAP (38) 987
(118) 982 CONROD (10) 987
CWELDC 982 CQUAD4 (33) 987
(117) 982 CQUAD4 (95) 987
CWELD 982 CQUAD4 (144) 988
(200) 982 CQUAD8 (64) 989
CBAR (34) 982 CQUAD82 (96) 990
CBAR (100) 983 CQUADR (82) 990
CBEAM (2) 983 CQUADR (235) 990
CBEAM3 (184) 984 CROD (1) 990
CBEND (69) 985 CSHEAR (4) 990
CBUSH (102) 985 CTRIA3 (74) 991
CCONEAX (35) 985 CTRIA32 (97) 991
CDAMP1 (20) 986 CTRlA6 (75) 991
CDAMP2 (21) 986 CTRlA62 (98) 992
CDAMP3 (22) 986 CTRIAR (70) 992
CDAMP4 (23) 986 CTRIAR (236) 992
CDUM3 thru CDUM9 (55 - 61) 986 CTUBE (3) 992
CELAS1 (11) 986 CVlSC (24) 992
CELAS2 (12) 986 CWELDP (118) 992
CELAS3 (13) 986 CWELDC (117) 992
CELAS4 (14) 986 CWELD (200) 993
Fluid Virtual Mass Pressure Item Codes, 993
2D Slideline and 3D Surface Contact Item Codes, 994
CSLIFID (116) 994 203 995
203 995
Element Strain Energy Item Codes, 996
Fatigue Item Codes, 997
Equivalent Radiated Power (ERP) Item Codes, 1003
8
Degree-of-Freedom Sets Degree-of-Freedom Set Definitions, 1006
Main Index
Degree-of-Freedom Set Bulk Data Entries, 1010
9
Bulk Data Entries Key to Descriptions, 1012
The Bulk Data Section, 1013
Bulk Data Entry Descriptions, 1014
Format of Bulk Data Entries, 1015
Continuations, 1020
Bulk Data Entry Summary, 1029
Constraints and Partitioning, 1029
Elements, 1031
Geometry, 1040
Loads, 1045
Materials, 1048
Miscellaneous, 1050
Explicit Nonlinear (SOL 700), 1055
Solution Control, 1066
Entries A - B, 1071
- $, 1071 - AEQUAD4, 1117
- /, 1072 - AERO, 1118
- ABINFL, 1076 - AEROS, 1119
- ABSNMVB, 1078 - AESCALE, 1120
- ABSNMVI, 1079 - AESTAT, 1121
- ABSNMVR, 1080 - AESURF, 1123
- ABSNMVS, 1081 - AESURFS, 1125
- ABSTRCT, 1083 - AETRIA3, 1126
- ACCEL, 1084 - ASET, 1127
- ACCEL1, 1086 - ASET1, 1129
- ACCSSPT, 1087 - ATBACC, 1131
- ACIFPRM, 1088 - ATBJNT, 1132
- ACLOAD, 1089 - ATBSEG, 1134
- ACMODL, 1090 - AXIC, 1135
- ACPEMCP, 1097 - AXIF, 1137
- ACPMCP1, 1100 - AXSLOT, 1139
- ACSRCE, 1102 - BAROR, 1140
- ACTRIM, 1104 - BARRIER, 1142
- ADUMi, 1105 - BCAUTOP, 1144
- AECOMP, 1106 - BCBDPRP, 1147
- AECOMPL, 1107 - BCBMRAD, 1154
- AEDW, 1108 - BCBODY, 1156
- AEFACT, 1109 - BCBODY1, 1168
- AEFORCE, 1110 - BCBOX, 1170
- AEGRID, 1111 - BCBZIER, 1172
- AELINK, 1112 - BCELIPS, 1174
- AELIST, 1113 - BCGRID (SOL 700 only), 1175
- AELISTC, 1114 - BCGRID, 1176
- AEPARM, 1115 - BCHANGE, 1177
- AEPRESS, 1116 - BCMATL, 1179
Main Index
- BCMOVE, 1180 - BDYLIST, 1265
- BCNURB2, 1181 - BDYOR, 1266
- BCNURBS, 1183 - BEADVAR, 1267
- BCONECT, 1185 - BEAMOR, 1271
- BCONP, 1187 - BFRlC, 1273
- BCONPRG, 1189 - BIAS, 1274
- BCONPRG-700, 1198 - BJOIN, 1277
- BCONPRP, 1204 - BLSEG, 1279
- BCONPRP-700, 1209 - BNDFIX, 1281
- BCONUDS, 1211 - BNDFIX1, 1282
- BCPARA, 1213 - BNDFREE, 1284
- BCPATCH, 1222 - BNDFRE1, 1285
- BCPFLG, 1223 - BNDGRID, 1287
- BCPROP, 1226 - BOLT, 1288
- BCRIGID, 1227 - BOLT1, 1290
- BCRGSRF, 1229 - BOUTPUT, 1293
- BCSCAP, 1230 - BRKPROP, 1295
- BCSEG, 1232 - BRKSYS, 1296
- BCSURF, 1233 - BSET, 1298
- BCTABLE, 1243 - BSET1, 1299
- BCTABLE - Glued Option, 1258 - BSQUEAL, 1301
- BCTABL1, 1262 - BSURF, 1303
- BCTRIM, 1264 - BWIDTH, 1305
Entries CA - CM, 1307
- CAABSF, 1307 - CDAMP4, 1358
- CACINF3, 1309 - CDAMP5, 1359
- CACINF4, 1310 - CDUMi, 1360
- CAERO1, 1311 - CELAS1, 1361
- CAERO2, 1313 - CELAS1D, 1362
- CAERO3, 1315 - CELAS2, 1364
- CAERO4, 1317 - CELAS2D, 1365
- CAERO5, 1319 - CELAS3, 1367
- CAMPBLL, 1323 - CELAS4, 1368
- CAXIFi, 1325 - CFAST, 1369
- CAXISYM, 1326 - CFLUIDi, 1371
- CBAR, 1328 - CGAP, 1373
- CBARAO, 1333 - CHACAB, 1375
- CBEAM, 1335 - CHACBR, 1377
- CBEAM3, 1339 - CHBDYE, 1379
- CBEND, 1343 - CHBDYG, 1383
- CBUSH, 1346 - CHBDYP, 1387
- CBUSH1D, 1350 - CHEXA, 1391
- CBUSH2D, 1351 - CIFHEX, 1395
- CCONEAX, 1352 - CIFPENT, 1397
- CDAMP1, 1353 - CIFQDX, 1399
- CDAMP1D, 1354 - CIFQUAD, 1401
- CDAMP2, 1355 - CINTC, 1403
- CDAMP2D, 1356 - CLOAD, 1404
- CDAMP3, 1357 - CMARKB2, 1405
Main Index
- CMARKN1, 1406 - CMASS3, 1409
- CMASS1, 1407 - CMASS4, 1410
- CMASS2, 1408
Entries CO - CY, 1411
- COHFRIC, 1411 - CQUAD8, 1470
- COMPUDS, 1412 - CQUADR, 1474
- CONCTL, 1415 - CQUADX, 1477
- CONM1, 1416 - CRAC2D, 1479
- CONM2, 1417 - CRAC3D, 1481
- CONROD, 1420 - CREEP, 1485
- CONTRLT, 1421 - CROD, 1490
- CONV, 1424 - CSEAM, 1492
- CONVM, 1426 - CSET, 1501
- CORD1C, 1429 - CSET1, 1502
- CORD1R, 1431 - CSHEAR, 1504
- CORD1S, 1433 - CSLOT3, 1507
- CORD2C, 1435 - CSLOT4, 1508
- CORD2R, 1437 - CSPR, 1509
- CORD2S, 1439 - CSSCHD, 1510
- CORD3G, 1441 - CSUPER, 1511
- CORD3R, 1443 - CSUPEXT, 1513
- COSMGRP, 1444 - CTETRA, 1514
- COSMINP, 1446 - CTRIA3, 1517
- COSMOUT, 1447 - CTRIA6, 1520
- COSMSEL, 1448 - CTRIAR, 1524
- COSMSRV, 1449 - CTRIAX, 1527
- COUCOHF, 1450 - CTRIAX6, 1529
- COUOPT, 1451 - CTUBE, 1532
- COUP1FL, 1453 - CVISC, 1533
- COUPINT, 1454 - CWELD, 1534
- COUPLE, 1455 - CYAX, 1544
- CPENTA, 1459 - CYJOIN, 1545
- CPYRAM, 1462 - CYLINDR, 1547
- CQUAD, 1464 - CYSUP, 1548
- CQUAD4, 1466 - CYSYM, 1550
Entries D - E, 1551
- DAMPING, 1551 - DLINK, 1572
- DAREA, 1554 - DLOAD, 1573
- DCONADD, 1555 - DMI, 1574
- DCONSTR, 1556 - DMIAX, 1578
- DDVAL, 1558 - DMIG, 1580
- DEACTEL, 1560 - DMIG,UACCEL, 1583
- DEFORM, 1561 - DMIJ, 1585
- DEFUSET, 1562 - DMIJI, 1588
- DELAY, 1563 - DMIK, 1591
- DEQATN, 1564 - DOPTPRM, 1594
- DESVAR, 1569 - DPHASE, 1602
- DETSPH, 1570 - DRESP1, 1603
- DIVERG, 1571 - DRESP2, 1616
Main Index
- DRESP3, 1622 - DYPARAM,FLOWMETH, 1697
- DSCREEN, 1625 - DYPARAM,GEOCHECK, 1700
- DTABLE, 1627 - DYPARAM,FASTCOUP, 1701
- DTABLE2, 1628 - DYPARAM,HYDROBOD, 1703
- DTI, 1629 - DYPARAM,HGCMEM, 1704
- DTI,ESTDATA, 1631 - DYPARAM,HGCOEFF, 1705
- DTI,INDTA, 1635 - DYPARAM,HGCSOL, 1706
- DTI,SETREE, 1638 - DYPARAM,HGCTWS, 1707
- DTI,SPECSEL, 1640 - DYPARAM,HGCWRP, 1708
- DTI,SPSEL, 1641 - DYPARAM,HGSHELL, 1709
- DTI,UNITS, 1642 - DYPARAM,HGSOLID, 1710
- DVBSHAP, 1644 - DYPARAM,HGTYPE, 1711
- DVCREL1, 1645 - DYPARAM,HICGRAV, 1712
- DVCREL2, 1647 - DYPARAM,HVLFAIL, 1713
- DVGRID, 1649 - DYPARAM,IMM, 1714
- DVLREL1, 1651 - DYPARAM,INFOBJ, 1715
- DVMREL1, 1653 - DYPARAM,INISTEP, 1716
- DVMREL2, 1655 - DYPARAM,LAGPR, 1717
- DVPREL1, 1657 - DYPARAM,LIMCUB, 1718
- DVPREL2, 1659 - DYPARAM,MATRMERG, 1719
- DVSHAP, 1661 - DYPARAM,MATRMRG1, 1720
- DVPSURF, 1662 - DYPARAM,MAXSTEP, 1721
- DYFSISW, 1663 - DYPARAM,MESHPLN, 1722
- DYPARAM, ATBAOUT, 1664 - DYPARAM,MINSTEP, 1723
- DYPARAM, ATBHOUT, 1665 - DYPARAM,MIXGAS, 1724
- DYPARAM, ATBTOUT, 1666 - DYPARAM,NZEROVEL, 1725
- DYPARAM,AUTOCOUP, 1667 - DYPARAM,OLDLAGT, 1726
- DYPARAM,AXIALSYM, 1669 - DYPARAM,JWLDET, 1727
- DYPARAM,AXREMAP, 1671 - DYPARAM,LIMITER, 1728
- DYPARAM,BULKL, 1672 - DYPARAM,PARALLEL, 1729
- DYPARAM,BULKQ, 1673 - DYPARAM,PLCOVCUT, 1730
- DYPARAM,BULKTYP, 1674 - DYPARAM,PMINFAIL, 1731
- DYPARAM,CFULLRIG, 1675 - DYPARAM,RBE2INFO, 1732
- DYPARAM,CLUFLIM, 1676 - DYPARAM,RHOCUT, 1733
- DYPARAM,CLUMPENR, 1677 - DYPARAM,RJSTIFF, 1734
- DYPARAM,CONM2OUT, 1678 - DYPARAM,SCALEMAS, 1735
- DYPARAM,CONTACT, 1679 - DYPARAM,SHELLFRM, 1736
- DYPARAM,COSUBMXT, 1682 - DYPARAM,SHELMSYS, 1737
- DYPARAM,COUFRIC, 1683 - DYPARAM,SHPLAST, 1738
- DYPARAM,COHESION, 1684 - DYPARAM,SHSTRDEF, 1739
- DYPARAM,DMPOPT, 1685 - DYPARAM,SHTHICK, 1740
- DYPARAM, DUMSEGS, 1686 - DYPARAM,SLELM, 1741
- DYPARAM,ELDLTH, 1687 - DYPARAM,SMP,BATCHSIZ, 1742
- DYPARAM,EULERCB, 1688 - DYPARAM,SMP,CPUINFO, 1744
- DYPARAM,EULERPR, 1689 - DYPARAM,SNDLIM, 1745
- DYPARAM,EULTRAN, 1691 - DYPARAM,SPREMAP, 1746
- DYPARAM,EUSUBMAX, 1692 - DYPARAM,SPHERSYM, 1747
- DYPARAM,EUSUBCYC, 1694 - DYPARAM,STRNOUT, 1748
- DYPARAM,FAILDT, 1695 - DYPARAM,TOLCHK, 1749
- DYPARAM,FAILOUT, 1696 - DYPARAM,VDAMP, 1750
Main Index
- DYPARAM,VELMAX, 1751 - EOSGAM, 1781
- DYPARAM,VELMAX1, 1752 - EOSIG, 1783
- DYPARAM,VISCPLAS, 1754 - EOSJWL, 1789
- ECHOOFF, 1755 - EOSMG, 1791
- ECHOON, 1756 - EOSNA, 1793
- EIGB, 1757 - EOSPOL, 1795
- EIGC, 1759 - EOSUDS, 1797
- EIGP, 1764 - EPOINT, 1798
- EIGR, 1765 - ERPPNL, 1799
- EIGRL, 1769 - EULFOR, 1800
- ELEMUDS, 1773 - EULFOR1, 1801
- ELIST, 1775 - EULFREG, 1802
- ENDDATA, 1776 - EXCLUDE, 1804
- ENDDYNA, 1777 - EXTRN, 1805
- EOSDEF, 1778
Entries F - L, 1806
- FAILJC, 1806 - FRFSPC1, 1863
- FAILMPS, 1808 - FRFXIT, 1864
- FAILUDS, 1809 - FRFXIT1, 1865
- FBADLAY, 1811 - FSICTRL, 1866
- FBALOAD, 1812 - FSLIST, 1867
- FBAPHAS, 1813 - FTGDEF, 1868
- FBODYLD, 1814 - FTGEVNT, 1873
- FBODYSB, 1815 - FTGLOAD, 1875
- FFCONTR, 1816 - FTGPARM, 1880
- FLFACT, 1818 - FTGSEQ , 1894
- FLOW, 1820 - GBAG, 1898
- FLOWC, 1822 - GBAGCOU, 1901
- FLOWDEF, 1825 - GENEL, 1902
- FLOWT, 1827 - GENUDS, 1905
- FLOWUDS, 1830 - GMBNDC, 1906
- FLSYM, 1832 - GMOVR3, 1907
- FLUTTER, 1833 - GRAV, 1908
- FORCE, 1836 - GRDSET, 1910
- FORCE1, 1837 - GRID, 1911
- FORCE2, 1838 - GRIDA, 1913
- FORCEAX, 1839 - GRIDB, 1914
- FORCUDS, 1840 - GRIDF, 1915
- FREEPT, 1842 - GRIDS, 1916
- FREQ, 1843 - GUST, 1917
- FREQ1, 1844 - H5OUT, 1918
- FREQ2, 1845 - HADACRI, 1919
- FREQ3, 1847 - HADAPTL, 1923
- FREQ4, 1850 - HDF5DA, 1925
- FREQ5, 1853 - HDF5OUT, 1926
- FRFCOMP, 1855 - HEATLOS, 1929
- FRFCONN, 1858 - HGSUPPR, 1931
- FRFFLEX, 1860 - HTRCONV, 1933
- FRFRELS, 1862 - HTRRAD, 1934
Main Index
- HYBDAMP, 1935 - IPSTRAIN, 1964
- HYDROC, 1937 - ISTRESS, 1965
- HYDROS, 1941 - ITER, 1967
- HYDSTAT, 1944 - LBSH3DG, 1970
- IMPCASE, 1946 - LEAKAGE, 1972
- IMPGEOM, 1947 - LOAD, 1975
- INCLUDE, 1951 - LOADCLID, 1977
- INFLCG, 1952 - LOADCNAM, 1978
- INFLFRC, 1954 - LOADCSUB, 1979
- INFLGAS, 1956 - LOADCYH, 1980
- INFLHB, 1958 - LOADCYN, 1982
- INFLTNK, 1959 - LOADCYT, 1983
- INFLTR, 1961 - LSEQ, 1984
- INITGAS, 1963
Entries M - O, 1985
- MASSSET, 1985 - MATS1, 2119
- MATBV, 1986 - MATS3, 2124
- MAT1, 1987 - MATS8, 2126
- MAT1A, 1991 - MATSMA, 2127
- MAT1F, 1992 - MATSORT, 2132
- MAT2, 1993 - MATT1, 2134
- MAT2F, 1996 - MATT2, 2136
- MAT3, 1998 - MATT3, 2138
- MAT4, 2000 - MATT4, 2139
- MAT5, 2002 - MATT5, 2140
- MAT8, 2003 - MATT8, 2141
- MAT8A, 2007 - MATT9, 2143
- MAT8F, 2011 - MATTEP, 2144
- MAT9, 2012 - MATTF, 2146
- MAT9F, 2015 - MATTG, 2149
- MAT10, 2016 - MATTHE, 2150
- MAT10F, 2018 - MATTORT, 2153
- MATCB, 2019 - MATTUSR, 2154
- MATDEUL, 2028 - MATTVE, 2155
- MATDIGI, 2030 - MATUDS, 2159
- MATEP, 2031 - MATUSR, 2163
- MATEP, 2042 - MATVE, 2166
- MATF, 2053 - MATVE, 2171
- MATF, 2068 - MATVP, 2173
- MATF1, 2074 - MCOHE, 2177
- MATFAB, 2075 - MDBCATP, 2179
- MATFTG , 2079 - MDBCNCT, 2182
- MATG, 2090 - MDBCPAR, 2184
- MATHE, 2093 - MDBCTB1, 2185
- MATHE, 2100 - MDBKSYS, 2187
- MATHP, 2104 - MDBNDRY, 2189
- MATORT , 2107 - MDBOLT, 2190
- MATPE1, 2112 - MDBULK, 2192
- MATRIG, 2117 - MDBUSH, 2196
Main Index
- MDCONCT, 2198 - MONPNT2, 2272
- MDDMIG, 2201 - MONPNT3, 2274
- MDEXCLD, 2203 - MONSUM, 2277
- MDFAST, 2204 - MONSUM1, 2280
- MDFSET, 2206 - MONSUMT, 2283
- MDLABEL, 2207 - MOTION, 2285
- MDLOC, 2208 - MPC, 2286
- MDLPRM, 2210 - MPCADD, 2287
- MDMIR1, 2226 - MPCAX, 2288
- MDMIR2, 2227 - MPCD, 2289
- MDMOVE, 2228 - MPCY, 2290
- MDMPC, 2229 - NHRMPRM, 2292
- MDMPLN, 2230 - NLADAPT, 2294
- MDRBE2, 2231 - NLBSH3D, 2296
- MDRBE3, 2232 - NLFREQ, 2298
- MDRJNT, 2234 - NLFREQ1, 2299
- MDROT1, 2235 - NLFREQC, 2300
- MDROT2, 2236 - NLHARM, 2302
- MDRROD, 2237 - NLMOPTS, 2303
- MDSEAM, 2238 - NLOUT, 2319
- MDSSET, 2240 - NLOUTUD, 2323
- MDTRAN, 2241 - NLPARM, 2325
- MDWELD, 2242 - NLPCI, 2333
- MESH, 2247 - NLRGAP, 2336
- METADATA, 2254 - NLRSFD, 2340
- MFLUID, 2255 - NLSTEP, 2343
- MKAERO1, 2257 - NOLIN1, 2357
- MKAERO2, 2258 - NOLIN2, 2359
- MODTRAK, 2259 - NOLIN3, 2361
- MOMAX, 2260 - NOLIN4, 2363
- MOMENT, 2261 - NSM, 2365
- MOMENT1, 2262 - NSM1, 2366
- MOMENT2, 2263 - NSMADD, 2368
- MONCARL, 2264 - NSML, 2369
- MONCNCM, 2266 - NSML1, 2370
- MONDSP1, 2266 - OMIT, 2372
- MONGRP, 2269 - OMIT1, 2373
- MONPNT1, 2270 - OMITAX, 2374
Entries P, 2375
- PAABSF, 2375 - PARAM, 2392
- PACABS, 2377 - PAXISYM, 2394
- PACBAR, 2378 - PAXSYMH, 2396
- PACINF, 2379 - PBAR, 2398
- PAERO1, 2380 - PBARL, 2401
- PAERO2, 2381 - PBARN1, 2407
- PAERO3, 2383 - PBCOMP, 2411
- PAERO4, 2385 - PBEAM, 2417
- PAERO5, 2387 - PBEAM3, 2422
- PANEL, 2391 - PBEAMD, 2425
Main Index
- PBEAML, 2426 - PLOAD2, 2551
- PBELT, 2434 - PLOAD4, 2553
- PBEMN1, 2437 - PLOADB3, 2556
- PBEND, 2441 - PLOADX1, 2558
- PBMSECT, 2450 - PLOTEL, 2561
- PBRSECT, 2455 - PLPLANE, 2562
- PBSH2DT, 2458 - PLSOLID, 2564
- PBUSH, 2460 - PLTSURF, 2565
- PBUSH1D, 2465 - PMARKER, 2566
- PBUSH2D, 2470 - PMASS, 2567
- PBUSHT, 2472 - PMINC, 2568
- PCOHE, 2478 - POINT, 2570
- PCOMP, 2479 - POINTAX, 2571
- PCOMPA, 2484 - PORFCPL, 2572
- PCOMPF, 2486 - PORFGBG, 2574
- PCOMPFQ, 2488 - PORFLOW, 2576
- PCOMPG, 2489 - PORFLWT, 2578
- PCOMPLS, 2494 - PORHOLE, 2581
- PCONEAX, 2499 - PORHYDS, 2583
- PCONV, 2501 - PORUDS, 2584
- PCONVM, 2505 - PRAC2D, 2585
- PDAMP, 2507 - PRAC3D, 2586
- PDAMP5, 2508 - PRESAX, 2587
- PDAMPT, 2509 - PRESPT, 2588
- PDISTB, 2510 - PROD, 2589
- PDISTBM, 2513 - PRODN1, 2590
- PDUMi, 2515 - PSEAM, 2592
- PELAS, 2516 - PSHEAR, 2594
- PELAS1, 2517 - PSHEARN, 2596
- PELAST, 2518 - PSHELL, 2598
- PERMEAB, 2520 - PSHELL1, 2603
- PERMGBG, 2522 - PSHLN1, 2605
- PEULER, 2524 - PSHLN2, 2610
- PEULER1, 2526 - PSHLPF, 2615
- PFAST, 2527 - PSLDN1, 2616
- PFASTT, 2532 - PSOLID, 2620
- PFTG , 2534 - PSPRMAT, 2625
- PGAP, 2538 - PTUBE, 2626
- PHBDY, 2541 - PVISC, 2628
- PLCOMP, 2542 - PVISC1, 2629
- PLOAD, 2546 - PWELD, 2630
- PLOAD1, 2548
Entries Q-S, 2633
- QBDY1, 2633 - QVECT, 2640
- QBDY2, 2634 - QVOL, 2643
- QBDY3, 2635 - RADBC, 2645
- QHBDY, 2636 - RADBND, 2646
- QSET, 2638 - RADCAV, 2647
- QSET1, 2639 - RADLST, 2649
Main Index
- RADM, 2651 - RCONN, 2677
- RADMT, 2652 - RCROSS, 2679
- RADMTX, 2653 - REFROT, 2681
- RADSET, 2654 - REFRTSE, 2683
- RANDPS, 2655 - RELEASE, 2685
- RANDT1, 2657 - RELEX, 2686
- RBAR, 2658 - RFORCE, 2687
- RBAR1, 2660 - RGYRO, 2691
- RBAX3D, 2662 - RINGAX, 2694
- RBE1, 2664 - RINGFL, 2696
- RBE2, 2666 - RJOINT, 2697
- RBE2GS, 2668 - RLOAD1, 2698
- RBE3, 2671 - RLOAD2, 2701
- RBJOINT, 2674 - ROTBENT, 2703
, 2706
- ROTHYBD, 2707 - SEQSET1, 2776
- ROTOR, 2708 - SESET, 2778
- ROTORAX, 2710 - SESUP, 2779
- ROTORG, 2712 - SET1, 2780
- ROTORSE, 2714 - SET2, 2781
- RROD, 2715 - SET3, 2782
- RSPINR, 2717 - SET4 , 2784
- RSPINT, 2725 - SETREE, 2785
- RSPLINE, 2729 - SEUSET, 2787
- RSSCON, 2731 - SEUSET1, 2788
- RTRPLT, 2734 - SHREL, 2789
- RTRPLT1, 2736 - SHRPOL, 2790
- RVDOF, 2738 - SHRUDS, 2791
- RVDOF1, 2739 - SLBDY, 2792
- SEBNDRY, 2740 - SLOAD, 2793
- SEBSET, 2741 - SLOADN1, 2794
- SEBSET1, 2742 - SNORM, 2795
- SEBULK, 2744 - SPBLND1, 2797
- SECONCT, 2748 - SPBLND2, 2799
- SECSET, 2750 - SPC, 2800
- SECSET1, 2751 - SPC1, 2802
- SECTAX, 2753 - SPCADD, 2804
- SEDLINK, 2754 - SPCAX, 2805
- SEDRSP2, 2756 - SPCD, 2806
- SEDRSP3, 2759 - SPCOFF, 2809
- SEELT, 2762 - SPCOFF1, 2810
- SEEXCLD, 2763 - SPCR, 2811
- SELABEL, 2764 - SPHERE, 2813
- SELOAD, 2765 - SPLINE1, 2814
- SELOC, 2767 - SPLINE2, 2816
- SEMPLN, 2769 - SPLINE3, 2818
- SENQSET, 2770 - SPLINE4, 2820
- SEQGP, 2771 - SPLINE5, 2822
- SEQSEP, 2772 - SPLINE6, 2824
- SEQSET, 2774 - SPLINE7, 2827
Main Index
- SPLINEX, 2829 - SUPAX, 2836
- SPLINRB, 2831 - SUPORT, 2837
- SPOINT, 2832 - SUPORT1, 2839
- SPRELAX, 2833 - SURFINI, 2841
- STOCHAS, 2834 - SWLDPRM, 2843
Entries T-Y, 2855
- TABDMP1, 2855 - TLOAD1, 2942
- TABL3D, 2858 - TLOAD2, 2945
- TABLE3D, 2862 - TMPSET, 2949
- TABLED1, 2863 - TODYNA, 2950
- TABLED2, 2866 - TOMVAR, 2951
- TABLED3, 2868 - TOPVAR, 2954
- TABLED4, 2870 - TPADEFN, 2958
- TABLED5, 2871 - TRIM, 2959
- TABLEHT, 2875 - TRIM2, 2960
- TABLEH1, 2876 - TRMCPL, 2962
- TABLEM1, 2877 - TSTEP, 2965
- TABLEM2, 2879 - TSTEPNL, 2966
- TABLEM3, 2881 - TTEMP, 2973
- TABLEM4, 2883 - UDNAME , 2974
- TABLES1, 2884 - UDSESV, 2976
- TABLEST, 2886 - UNBALNC, 2977
- TABLFTG, 2887 - UNGLUE, 2981
- TABLRPC, 2888 - USET, 2982
- TABLUDS, 2890 - USET1, 2983
- TABRND1, 2891 - UXVEC, 2985
- TABRNDG, 2894 - VCCT, 2987
- TABSCTL, 2895 - VIEW, 2989
- TCOMPG, 2897 - VIEW3D, 2991
- TEMP, 2900 - WALL, 2993
- TEMPAX, 2902 - WETELME, 2995
- TEMPB3, 2903 - WETELMG, 2996
- TEMPBC, 2905 - WETLOAD, 2997
- TEMPD, 2908 - WETSURF, 2999
- TEMPN1, 2910 - YLDHY, 3000
- TEMPP1, 2911 - YLDJC, 3001
- TEMPP3, 2914 - YLDMC, 3003
- TEMPRB, 2915 - YLDMSS, 3004
- TF, 2918 - YLDPOL, 3006
- THPAD, 2920 - YLDRPL, 3007
- TIC, 2926 - YLDSG, 3008
- TICEL, 2928 - YLDTM, 3010
- TICEUL1, 2930 - YLDUDS, 3012
- TICEUDS, 2931 - YLDVM, 3014
- TICREG, 2932 - YLDZA, 3017
- TICVAL, 2934
- TIC3, 2936
- TIM2PSD, 2938
- TIRE, 2941
Main Index
A
Configuring the Runtime Specifying Parameters, 3020
Environment Command Initialization and Runtime Configuration Files, 3020
Environment Variables, 3024
User-Defined Keywords, 3025
General Keywords, 3025
PARAM Keywords, 3026
Value Descriptors, 3027
Examples:, 3028
Resolving Duplicate Parameter Specifications, 3030
Customizing Command Initialization and Runtime Configuration Files, 3033
Examples, 3035
Symbolic Substitution, 3039
Introduction, 3039
Simple Examples, 3039
Detailed Specifications, 3041
Examples, 3050
B
Configuring MSC Nastran and Co-simulation Interfaces, 3054
Actran Co-simulation with
Workflow Manager for Virtual SEA: Case Control Command and Bulk Data Entries, 3054
Workflow Manager
Case Control Command, 3054
- BEGIN BULK SEA, 3054
Bulk Data Entries, 3055
- IJPOWER, 3055 - IJPOWER, 3055
- SEAFREQ, 3055 - SEAFREQ, 3056
- SEAPART, 3055 - SEAPART, 3056
- SEAPELL, 3055 - SEAPELL, 3058
Workflow Manager for Space: Case Control Command and Bulk Data Entries, 3058
Case Control Command, 3058
Bulk Data Entries, 3059
- ACCPL, 3059 - ACCPL, 3059
- CQUAD4A, 3059 - CQUAD4A, 3062
- CQUAD8A, 3059 - CQUAD8A, 3062
- CTRIA3A, 3059 - CTRIA3A, 3063
- CTRIA6A, 3059 - CTRIA6A, 3063
- DSF, 3059 - DSF, 3064
- PAC, 3059 - PAC, 3066
- SOLVAC, 3059 - SOLVAC, 3067
- TABLDSF, 3059 - TABLDSF, 3069
C
NLPERF SOL 400 The NLPERF - High Performance Nonlinear Solver, 3072
Main Index
Executing MSC Nastran, 3072
Activating the Convergence Monitor via the Command Line, 3072
Activating by MSC utility, 3072
File Management Statements, 3073
- CONNECT, 3073 - RESTART, 3073
Case Control Commands, 3073
- SUBCASE (Case), 3073 - EKE (Case), 3074
- ANALYSIS (Case), 3073 - ESE (Case), 3074
- STEP (Case), 3073 - GPFORCE (Case), 3074
- NLOPRM (Case), 3073 - HADAPT (Case), 3074
- BSQUEAL (Case), 3074 - IMPERFECT (Case), 3074
- COSMSEL (Case), 3074 - IRLOAD (Case), 3074
- DESGLB (Case), 3074 - MONITOR (Case), 3074
- DESMOD (Case), 3074 - NLBUCK (Case), 3074
- DESOBJ (Case), 3074 - NLIC (Case), 3074
- DESSUB (Case), 3074 - RGYRO (Case), 3075
- DESVAR (Case), 3074 - SMETHOD (Case), 3075
- EDE (Case), 3074 - STOCHASTICS (Case), 3075
Bulk Data Entries, 3075
- BCPARA, 3075 - RSSCON, 3080
- MDLPRM, 3076 - RTRPLT, 3080
- RBAR, 3076 - RTRPLT1, 3080
- RBE1, 3077 - PAXISYM, 3080
- Quadratic elements with missing mid- - PLCOMP, 3080
side node(s), 3077 - PLPLANE, 3080
- NLMOPTS, 3077 - MATDIGI, 3080
- NLPARM, 3078 - MATUSR, 3080
- NLSTEP, 3079 - MATUDS, 3080
- ACMODL, 3080 - MATTUSR, 3081
- CINTC, 3080 - TEMPRB, 3081
- RSPLINE, 3080
Parameter Entries, 3081
- AUTOMSET, 3081
- EPSILONT, 3081
- FOLLOWK, 3081
- KDIAG, 3081
- K6ROT, 3081
- LGDISP, 3082
- NLAYERS, 3082
- WTMASS, 3082
Main Index
Preface
MSC Nastran Quick Reference Guide
Preface
List of MSC Nastran Guides xx
Technical Support xxi
Training and Internet Resources xxi
Main Index
xx MSC Nastran Quick Reference Guide
List of MSC Nastran Guides
List of MSC Nastran Guides
A list of some of the MSC Nastran guides is as follows:
Installation and Release Guides
Installation and Operations Guide
Release Guide
Reference Guides
Quick Reference Guide
DMAP Programmer’s Guide
Reference Guide
Utilities Guide
Getting Started Guide
SOL 400 Getting Started Guide
MSC Nastran Error Messages Guide
Demonstration Guides
Linear Analysis
Implicit Nonlinear (SOL 400)
Explicit Nonlinear (SOL 700)
MSC Nastran Verification Guide
User’s Guides
Automated Component Modal Synthesis (ACMS)
Access Manual
Aeroelastic Analysis
Design Sensitivity and Optimization
DEMATD
Dynamic Analysis
Embedded Fatigue
Embedded Vibration Fatigue
Explicit Nonlinear (SOL 700)
High Performance Computing
Linear Static Analysis
Nonlinear (SOL 400)
Numerical Methods
Rotordynamics
Main Index
Preface xxi
Technical Support
Superelements and Modules
Thermal Analysis
User Defined Services
You may find any of these documents from Hexagon at:
https://simcompanion.hexagon.com/customers/s/article/MSC-Nastran-Support-Home-Page
Technical Support
For technical support phone numbers and contact information, please visit:
https://simcompanion.hexagon.com/customers/s/article/support-contact-information-kb8019304
Support Center (http://simcompanion.hexagon.com)
The SimCompanion link above gives you access to the wealth of resources for Hexagon products. Here you
will find product and support contact information, product documentations, knowledge base articles,
product error list, knowledge base articles and SimAcademy Webinars. It is a searchable database which allows
you to find articles relevant to your inquiry. Valid MSC customer entitlement and login is required to access
the database and documents. It is a single sign-on that gives you access to product documentation for
complete list of products from Hexagon, allows you to manage your support cases, and participate in our
discussion forums.
Training and Internet Resources
The Hexagon corporate site has the information on the latest events, products, and services for the
CAD/CAE/CAM marketplace.
Design and Engineering e-Learning
The above link will point you to schedule and description of seminars. Following courses are recommended
for beginning MSC Nastran users.
NAS120 - Linear Static Analysis using MSC Nastran and Patran
This seminar introduces basic finite element analysis techniques for linear static, normal modes, and buckling
analysis of structures using MSC Nastran and Patran. MSC Nastran data structure, the element library,
modeling practices, model validation, and guidelines for efficient solutions are discussed and illustrated with
examples and workshops. Patran will be an integral part of the examples and workshops and will be used to
generate and verify illustrative MSC Nastran models, manage analysis submission requests, and visualize
results. This seminar provides the foundation required for intermediate and advanced MSC Nastran
applications.
Main Index
xxii MSC Nastran Quick Reference Guide
Training and Internet Resources
Main Index
Chapter 1: Executing MSC Nastran
MSC Nastran Quick Reference Guide
1 Executing MSC Nastran
Executing MSC Nastran
Main Index
2 MSC Nastran Quick Reference Guide
Executing MSC Nastran
Executing MSC Nastran
MSC Nastran is executed from the command line using the command nast_ver (where nast_ver=nast20234).
This command sets environment variables in order for MSC Nastran to correctly execute on your system and
it also has capabilities to predict memory and solvers (as of MSC Nastran 2022.3 with solve=auto). The basic
format of the nast_ver command is
nast_ver input_data_file keywords
nast_ver input_data_file [keyword1=value1 keyword2=value2 …]
where input_data_file is the name of the file containing the input data and keyword=valuei is one or more
optinal keyword assignment arguments. For example, to run an MSC Nastran job using the data file
example1.dat, enter the following command:
nast_ver example1
Most keyword assignments can be specified as command line arguments and/or included in RC files. There
are some exceptions which may be specified on the command line or the User RC files, but not in the system
RC files (MSC_BASE/conf/RCfile).
There are two RC files controlled by the user:
The user RC file is in your home (or login) directory. This file should be used to define parameters
that are applied to all jobs run by the user.
The local RC file is nast20223rc on Linux and NAST20223.rcf on Windows, and is located in the
same directory as the input data file. If the “rcf” keyword is used, this local RC file is ignored. This
file should be used to define parameters that are applied to all jobs contained in the input data file
directory.
1. The tilde (~) character is not recognized within RC files.
2. Environment variables are only recognized when used in the context of a logical symbol (on Windows
NAST20223.rcf) (see Using Filenames and Logical Symbols in the MSC Nastran Installation and
Operations Guide).
3. When a keyword is specified on the command line, embedded spaces or special characters that are
significant to the shell must be properly quoted; quotes should not be used within RC files.
The keywords listed as follows are the most common for various computers, but are not available on all
computers. Also, the defaults may be site-dependent. Please consult your Keywords and Environment Variables in
the MSC Nastran Installation and Operations Guide for keyword applicability, specialized keywords, and
further discussion of the keywords and their defaults. Keywords that use yes/no values accept partial
specification and case-independent values. For example, “yes” may be specified as “y”, “ye”, or “yes” using
uppercase or lowercase letters. The examples assume the jobs are run under a Linux operating system.
acms acms={yes|no} Default: None
If set to "yes" with "solve=auto", this flag will force the ACMS solver for the eigenvalue
solution with a setting chosen from solve=auto algorithm.
If set to "no" with "solve=auto", this flag will turn off the ACMS solver choice from
solve=auto algorithm and force the Lanczos solver for the eigenvalue solution.
after after = time Default: None
Main Index
Chapter 1: Executing MSC Nastran 3
Executing MSC Nastran
(Linux) Holds the job’s execution until the time specified by time. See the description of the “at”
command in your system documentation for the format of time
Example: nast_ver example after=10:00
The job is held until 10:00 AM.
append append={yes|no} Default: no
Combines the .f04, .f06, and .log files into a single file after the run completes. If “no”
is specified, the files are not combined. If “yes” is specified, the files are combined into
one file with the suffix “.out”.
Example: nast_ver example append=yes
Result: The .f04, .f06, and .log files are combined into a file named example.out.
batch batch={yes|no} Default: yes
(Linux) Indicates how the job is to be run. If “yes” is specified, the job is run as a background
process. If “no” is specified, the job is run in the foreground. If the “aft” or “queue”
keywords are specified, the batch keyword is ignored. Jobs submitted with “batch=yes”
will run under nice(1).
Note: If the job is already running in an NQS or NQE batch job, the default is “no”.
Example: nast_ver example batch=no
Result: The job is run in the foreground.
bpool bpool=value Default: See text below.
Specifies the number of GINO and/or executive blocks, or memory size in MB, GB, etc.,
that are placed in buffer pool.
The size is specified as the number of blocks (BUFFSIZE words long), a percentage of
MEM, or the number of words or bytes followed by one of the modifiers: "T", "TW",
"TB", "G", "GW", "GB", "M", "MW", "MB", "K", "KW", "KB", "W", "B". See
Specifying Memory Sizes, 63 for a description of these modifiers.
If mem=max (which is the default) or/and solve=auto is not used, the default of bpool is
150 GINO blocks.
If solve=auto is used, bpool will be set automatically.
If mem=max is used, the default of bpool will be set to:
25% of memory for non SOL 101 or SOL 400.
the remaining memory after memory estimate needed for the solver for SOL
101 or SOL 400.
Main Index
4 MSC Nastran Quick Reference Guide
Executing MSC Nastran
Example: nast_ver example bpool=100mb
buffsize buffsize=value Default: Dependent on model size. Refer to BUFFSIZE (1)
Use to control the number of words per I/O record.
For large models, it is recommended to change buffsize to 65537, which is the maximum
allowed.
casi If set to "no", this flag will disable the Casi solver as a possible option when "solve=auto"
is specified.
dbs dbs=pathname Default= . {Current directory}
Creates database files (see Using the NASTRAN Statement in the MSC Nastran Installation and
Operations Guide) using an alternate file prefix. If “dbs” is not specified, database files are
created in the current directory using the basename of the input data file as the prefix. If
the “dbs” value is a directory, database files are created in the specified directory using
the basename of the input data file as the filename.
Note: If “dbs” is specified and “scratch=yes” is specified, a warning will be issued
and “scratch=no” is assumed.
In the following examples, assume the current directory includes subdirectories “mydir”
and “other”, and that an “example.dat” exists in both the current directory and “other”.
That is, ./example.dat, ./mydir, ./other, and ./other/example.dat exist on Linux,
and .\example.dat, .\mydir, .\other, and .\other\example.dat exist on Windows.
Example: nast_ver example
Result: Database files are created in the current directory with the name “example”
e.g., ./example.DBALL on Linux; and .\example.DBALL on Windows.
Example: nast_ver other/example
Result: Database files are created in the “other” directory with the name “example”,
e.g., ../other/example.DBALL on Linux, and .\other\example.DBALL on Windows.
Example: nast_ver example dbs=myfile
Result: Database files are created in the current directory with the name “myfile”,
e.g., ./myfile.DBALL on Linux, and .\myfile.DBALL on Windows.
Example: nast_ver example dbs=mydir
Result: Database files are created in the mydir directory with the name “example”, e.g.,
./mydir/example.DBALL on Linux, and .\mydir\example.DBALL on Windows.
Example: nast_ver example dbs=mydir/myfile
Result: Database files are created in the mydir directory with the name “myfile”,
e.g., ./mydir/myfile.DBALL on Linux, and .\mydir\myfile.DBALL on Windows
Example: nast_ver example dmp=4 host=a:b:c:d
dbs=/aa:/bb:/cc:/dd
Main Index
Chapter 1: Executing MSC Nastran 5
Executing MSC Nastran
Result: This example will set the “dbs” directory to “/aa” on host a, “/bb” on host b, “/cc”
on host c, and finally “/dd” on host d.
Note: The use of distinct per-task database directories can have a significant impact
on elapsed time performance of DMP jobs on SMP and NUMA systems.
dmp dmp=dmparallel Default: No parallelism based upon dividing the model
The dmp keyword specifies the number of processors used to efficiently obtain a
solution to the simulation. These processors may be on the same node or on multiple
nodes specified by the HOST command line option.
Specifying dmparallel > 1 and not including a DOMAINSOLVER Executive
Command Statement has the following effects.
The extraction of real eigenvalues using the default Lanczos method will be
performed in parallel in SOL 103 and 111.
The frequency response using SOL 111 will be performed in parallel.
Specifying dmp > 1 and using the DOMAINSOLVER provides the following addition
user controlled performance gains using parallel processing
The extraction of eigenvalues may be performed using Automated Component
Modal Synthesis (ACMS) which is an approximate method that is very
computational efficient when a large number of modes (high frequencies) are
required.
Design sensitivity may be performed in parallel in SOL 200
The formation of using advanced nonlinear elements stiffness matrices may be
performed in parallel for SOL 400.
It may also be necessary to define a host file if a network based distributed computing is
used. See the MSC Nastran Installation and Operators Guide.
Main Index
6 MSC Nastran Quick Reference Guide
Executing MSC Nastran
gpuid gpuid=id,id or gpuid=id:id Default: none
id: the ID of a licensed GPU device to be used in the analysis.
GPUs are used for two types of operations: matrix factorization and matrix
multiplication. In the routines that use GPUs for matrix operations , only one
GPU will be used per DMP process. So in order to use multiple GPUs, the user
must also use multiple DMP processes:
nast_ver job gpuid=0,1,...,ngpu-1 dmp=ndmp, where ndmp≥ngpu.
Each DMP process will be assigned a GPU ID in round robin fashion.
In MUMPS, MPYAD and FASTFR modules, on the other hand, multiple GPUs
can be used for matrix multiplication by a single process, as long as the number
of SMPthreads is equal to or larger than the number of GPUs. These modules
also use multiple parallel streams for data transfer between the GPU and the host
system, so it is recommended to use the maximum number of available CPU
cores/threads because that helps reduce the overhead of data transfer between the
host and the GPUs.
So, for example, in order to achieve the best performance on a system with 20
CPU cores and 2 GPUs the user is advised to run Nastran with:
nast_ver job dmp=2 smp=10 gpuid=0,1
or
nast_ver job dmp=4 smp=5 gpuid=0,1.
Only up to 8 CUDA-compatible GPUs can be supported.
gpu_min_rank gpu_min_rank=value Default: 32
The criteria for GPGPU execution during matrix factorization are the frontal
matrix front size and the rank of the frontal matrix. Minimum dimensions are set
via gpu_min_front and its companion parameter, gpu_min_rank. The value
specified must be an integer greater or equal to 1. If the rank of the frontal matrix
is smaller than value, the rank update of the front is processed on the CPU.
Otherwise, the GPGPU device would be used for the rank update of the front.
This keyword may also be set via SYSTEM cell 655.
Main Index
Chapter 1: Executing MSC Nastran 7
Executing MSC Nastran
gpu_min_front gpu_min_front=value Default: 2048
The criteria for GPGPU execution during matrix factorization are the frontal
matrix front size and the rank of the frontal matrix. Minimum dimensions are set
via gpu_min_front and its companion parameter, gpu_min_rank. The value
specified must be an integer greater or equal to 1. If the front size is smaller than
value, the rank update of the front is processed on the CPU. Otherwise, the
GPGPU device would be used for the rank update of the front. This keyword
may also be set via SYSTEM cell 656.
memorymax memorymax=maximum user Default: 0.5 x the amount of physical memory on your
memory machine
The user can enter the amount of memory as nGB or as fxphysical; f is the fraction
between 0 and 1.
When dmp is used, the amount of memory per processor is memorymax / dmp.
If the machine is going to be used by a single user or a single job, it is recommended to
set memorymax to 0.75xPhysical.
If multiple Nastran jobs are running simultaneously on the same node of a computer
system, it is recommended to set memorymax to 0.8*physical_memory divided by the
number of possible Nastran jobs running on the same node. Otherwise, one might
encounter an error due to lack of memory on small models. The error can be avoided by
using above setting in the system RC file or mem=size specified properly for the job in the
command line.
memory memory=memory_size Default=max
Specifies the amount of memory to allocate. The memory_size can be specified either as a
number of words, or as a number followed by one of the following modifiers:
G or Gw Multiply memory_size by 1024**3.
Gb Multiply memory_size by (1024**3)/bytes_per_word.
where bytes_per_word is 8or you can enter a faction of the physical memory
If "memory=estimate" is specified, ESTIMATE will be used to determine size. If
"memory=max" is specified, then the amount of memory allocated depends on the
"memorymaximum" keyword.
Example: nast_ver example memory=5gb
Result: The job is run using a memory size of 5 gigabytes.
Example: nast_ver example
memory=0.5xPhysical
Result: The job is run using one-half the amount of physical RAM.
For a more detailed description, see the memory in the MSC Nastran Installation and
Operations Guide.
Main Index
8 MSC Nastran Quick Reference Guide
Executing MSC Nastran
news news={yes|no|auto} Default=yes
Displays the news file (install_dir/msc20223/nast/news.txt on Linux and
install_dir\msc20223\nast\news.txt on Windows) in the .f06 file. If “auto” is specified,
the news file is only displayed if it has been modified since the last time it was displayed
for you. If “yes” is specified, the news file is displayed in the .f06 file regardless of when
it was last changed. If “no” is specified, the news file is not displayed in the .f06 file.
Example: nast_ver example news=yes
Result: The news file is displayed in the .f06 file after the title page block.
norun norun={yes|no} Default: no
If set to "yes" with "solve=auto", this flag will return command line chosen from
solve=auto algorithm in console (also in log file) and terminate the job.
notify notify={yes|no} Default=yes
Sends notification when the job is completed. See the “ncmd” keyword to define an
alternate notification command.
Note: If the job is queued using the queue keyword, or the job is already running in
an NQS batch job, the default is “no”.
Example: nast_ver example notify=yes
old old={yes|no} Default=yes
Saves previous copies of the .f04, .f06, .log, .op2, .out, pch, and .plt output files using
sequence numbers (additional user-specified file types can be versioned with the
“oldtypes” keyword). Sequence numbers are appended to the keyword filenames and are
separated by a period.
If “yes” is specified, the highest sequence number of each of the output files is
determined. The highest sequence number found is incremented by one to become the
new sequence number. Then, all current output files that do not include sequence
numbers are renamed using the new sequence number as a type.
Example: nast_ver example old=yes
For example, assume your current working directory contains the following files:
v2401.dat v2401.f04.1 v2401.f06 v2401.log v2401.log.1
v2401.f04 v2401.f04.2 v2401.f06.1 v2401.log.1 v2401.log.3
Main Index
Chapter 1: Executing MSC Nastran 9
Executing MSC Nastran
Apparently, the user ran the job four times, but deleted some of the files; e.g.
v2401.f04.3
v2401.f06.3
When the job is run again with “old=yes”, the files are renamed as follows:
v2401.f04 is renamed to v2401.f04.4
v2401.f06 is renamed to v2401.f06.4
v2401.log is renamed to v2401.log.4.
The sequence number 4 is used because it is one greater than the highest sequence
number of all of the selected files (the highest being v2401.log.3).
out out=pathname Default= .
Saves the output files using a different file prefix or in a different directory. If “out” is
not specified, the output files are saved in the current directory using the basename of
the input data file as a prefix. If the “out” value is a directory, output files are created in
the specified directory using the basename of the input data file as the filename.
In the following examples, assume the current directory includes subdirectories “mydir”
and “other”, and that an “example.dat” exists in both the current directory and “other”.
That is, ./example.dat, ./mydir, ./other, and ./other/example.dat exist on Linux; and
.\example.dat, .\mydir, .\other, and .\other\example.dat exist on Windows.
Example: nast_ver example
or: nast_ver other/example
Result: Output files are created in the current directory with the name “example”,
e.g., ./example.f06 on Linux and .\example.f06 on Windows.
Example: nast_ver example out=myfile
Result: Output files are created in the current directory with the name “myfile”,
e.g., ./myfile.f06 on Linux and .\myfile.f06 on Windows.
Example: nast_ver example out=mydir
Result: Output files are created in the mydir directory with the name “example”,
e.g., ./mydir/example.f06 on Linux and .\mydir\example.f06 on Windows.
Example: nast_ver example out=mydir/myfile
Result: Output files are created in the mydir directory with the name “myfile”,
e.g., ./mydir/myfile.f06 on Linux and .\mydir\myfile.f06 on Windows.
Main Index
10 MSC Nastran Quick Reference Guide
Executing MSC Nastran
rcf rcf=pathname Default=no
Specifies the name of the local RC file. If this keyword is not specified, the nast20223rc
file on Linux and NAST20223.rcf on Windows located in the input data file’s directory
is used.
Example: nast_ver example rcf=nast.rc
Result: The nastran command will process ./nast.rcf on Linux, or .\nast.rcf on
Windows in lieu of the default local RC file ./nast20223rc on Linux,
and .\NAST20223.rcf on Windows.
scratch scratch={yes|no|mini|post} Default=no
Deletes the database files at the end of the run. If the database files are not required,
“scratch=yes” can be used to remove them, thereby preventing cluttering of the directory
with unwanted files. If “mini” is specified, a reduced size database (that can only be used
for data recovery restarts) will be created. See Database Concepts in the MSC Nastran
Reference Guide for further details on the “mini” database. If scratch=post is specified, a
reduced size database intended for use by Patran or the toolkit will be created.
Scratch=post also performs the actions of NASTRAN INDEX=19. But with
scratch=post the resulting database is not restartable.
Example: nast_ver example scratch=yes
All database files created by the run are deleted at the end of the job in the same way as
the FMS statement INIT MASTER(S).
sdirectory sdirectory=directory Default: See the description below.
See Determining Resource Requirements in the MSC Nastran Installation and Operations
Guide for information on estimating a job’s total disk space requirements.
Specifies the directory to use for temporary scratch files created during the run. MSC
Nastran can create very large scratch files; therefore, the scratch directory should contain
sufficient space to store any scratch files created during a run. You must have read, write,
and execute privileges to the directory.
Linux: The default value is taken from the TMPDIR environment variable if it is set to
a nonnull value. Otherwise, the computer’s default temporary file directory is chosen;
this is usually /tmp.
Windows: The default value is taken from the TEMP environment variable.
Linux Example: nast_ver example sdir=/scratch
Result: Scratch files are created in the directory /scratch.
Main Index
Chapter 1: Executing MSC Nastran 11
Executing MSC Nastran
smp smp=value Default = 0
Specifies the maximum number of processors selected for shared-memory parallel (SMP)
processing in several numeric modules. In some cases SMP parallelization can be
combined with DMP. In such cases, the smp keyword specifies the number of threads
per process used in the simulation.
smp parallelization is available for mathematical kernels.
smp parallelization is available for the Intel MKL PARDISO solver in SOL 101, 107,
108, 111, 200, and 400; see the SPARSESOLVER section of this document.
smp parallelization is available for the NLEMG modules and is disabled in the following
cases:
heat transfer and coupled analysis simulations;
models that have contact between Advanced elements and Nastran elements;
models that have QUADR/QUAD4 or TRIAR/TRIA3 element types arranged into
the same element groups.
models that have friction.
If models have contact between Nastran and Advanced elements resulting in a SYSTEM
FATAL MESSAGE (SFM) with smp > 1, then rerun the job with
sys107=65536+number. For example, if smp=8 is desired but an SFM results, then rerun
with sys107=65544 in replace of smp=8. This turns off the SMP parallelization for
NLEMG.
solve solve={auto|train} Default (not set)
If solve=auto then Nastran will automatically select the solver/parallel/memory.
If solve=train then Pardiso memory coefficients will be updated. These options
may be placed on the command line or in the User's RC files.
spotweld <path>/spotweld.sys Default: None.
Points to the location of the spotweld.sys file used in fatigue analysis of spotwelds to
look up the diameter of the spotwelds based on the thickness of the top/bottom sheets.
See the definition of PFTG bulk data for more information.
symbol symbol=name=string Default: None
Defines a symbolic (or logical) name used in ASSIGN and INCLUDE statements and
in command line arguments. This keyword may be specified in initialization or RC files
and on the command line. The symbol definition may include references to previously
defined symbols or environment variables using the standard "$name" or "${name}"
syntax on Linux or %name% syntax on Windows. For convenience, the character
separating the "symbol" and "name" specification and the "name" and "string"
specification may be either an equal sign ("='") or a hash mark ("#"). The use of a hash
mark allows this keyword to be specified as an argument to a Windows .bat file.
Main Index
12 MSC Nastran Quick Reference Guide
Executing MSC Nastran
If "node" is specified, symbolic names defined using this keyword are not used on the
local system. Instead the specified values are passed to the remote system. This means
that any pathnames must be valid on the remote system. Use the "lsymbol" keyword to
specify symbolic names for the local system.
If "node" is not specified, symbolic names defined using the "lsymbol" keyword are
processed as if they were defined using the “symbol” keyword.
Symbolic names are processed in the order they are encountered while processing the
initialization and RC files and the command line. If a duplicate symbolic name is
encountered, the new value replaces the previously specified value.
Symbolic names must be 16 characters or less. The value assigned to the symbolic name
must be 256 characters or less. If the symbolic name used in an ASSIGN or INCLUDE
statement or in command line arguments is not defined, it is left in the filename
specification as is.
For example, many of the .tpl and .demo input data files have ASSIGN statements such
as the following:
ASSIGN 'MASTER=DBSDIR:abc.master'
The string "DBSDIR:" specifies a symbolic name that is to be replaced by another string.
The replaced string is defined by the "symbol=" keyword (or "lsymbol=" keyword if
"node" was not specified) in an initialization or RC file, on the command line, or as
environment variable. For example,
(Linux) symbol=DBSDIR=/dbs
(Windows) symbol=DBSDIR=d:\dbs
When the previous ASSIGN statement is processed, the filename assigned to the logical
name MASTER is /dbs/abc.master on Linux and d:\dbs\abc.master on
Windows. An alternate way of defining symbolic names is through the use of
environment variables. For example, typing the following command
export DBSDIR=/dbs
at a Korn shell prompt, or
setenv DBSDIR /dbs
at a C-shell prompt, or
at a Windows shell prompt, is equivalent to the “symbol” keyword definition.
Note: If a symbolic name is defined by both a symbol statement in an RC file and by
an environment variable, the symbol statement value will be used.
The section titled Environment Variables in the MSC Nastran Installation and Operations
Guide contains a list of environment variables that are automatically created by the
nastran command. Of particular interest to the logical symbol feature are the OUTDIR
and DBSDIR variables. These variables refer to the directory that will contain the
output files (set using the “out” keyword) and the directory that will contain the
permanent database files (set using the “dbs” keyword), respectively.
Main Index
Chapter 1: Executing MSC Nastran 13
Executing MSC Nastran
uds uds={filename | model} Default: None
The file name is the source file that defines user subroutines. This keyword is used to build
user service at nastran job submittal time. The user subroutines implementations are from
the specified file and the user service name is from the connect service statement in input
file.
On windows the UDS files being created may not be in "C:\Program Files". Please copy
files to a writable directory to build.
Example:
If user routine is written in Fortran: nast_ver example uds=mysource.F
If user routine is written in C++: nast_ver example
uds=mysource.cpp
The mysource.F includes all user defined subroutines. There may be multiple user
subroutines from multiple interfaces in the file. The user subroutine names are predefined
and documented in User Defined Services.
Another option to define user subroutines is to put them in BEGIN BULK UDS section
in the input file. The content in this section will be used to create source file when building
user service. If this option is used, the uds keyword should be set to model.
Example: nast_ver example uds=model
udssave udssave=pathname Default: output directory
The udssave is the location to build user service. If udssave is given, the path will be used
to build and save user service. If it is not given, the nastran output directory will be used
and the user service will be removed after nastran job run.
Example: nast_ver example uds=mysource.F
udssave=/scratch/mydir
xdbold xdbold={yes|no} Default=yes
Keeps or deletes the previous copy of the .xdb.
If “yes” is specified, the previous copy is kept and appended by the current run.
If “no” is specified, the previous copy is deleted and a new file is created. This gives the
same behavior as below FMS statement:
ASSIGN dbc=<file_name>.xdb delete
Example: nast_ver example xdbold=no
Main Index
14 MSC Nastran Quick Reference Guide
Executing MSC Nastran
Main Index
Chapter 2: NASTRAN Statement
MSC Nastran Quick Reference Guide
2 NASTRAN Statement
The NASTRAN Statement
Main Index
16 MSC Nastran Quick Reference Guide
The NASTRAN Statement
The NASTRAN Statement
The NASTRAN statement is used to specify values for certain Executive System operational parameters.
These parameters are also called system cells. The NASTRAN statement is used for exceptional circumstances
and is therefore not needed in most runs. The NASTRAN statement may also be specified in the runtime
configuration (RC) files at the system, user, and job level as described in the .
Main Index
CHAPTER 2 17
NASTRAN Statement
NASTRAN Executive System Parameter Modification
Specifies values for certain Executive System operational parameters called system cells.
Format:
NASTRAN cellnamei=expressioni, ..., cellnamen=expressionn
or
NASTRAN SYSTEM(i)=expressioni, ..., SYSTEM(n)=expressionn
Describer Meaning
cellnamei System cell names from Table 2-1.
SYSTEM Specifies the system cell number.
expression See DEFINE statement for description.
i System cell number from Table 2-1 or from the SYSTEM common block
described in the MSC Nastran User Modifiable User’s Guide.
Remarks:
1. The NASTRAN statements may appear anywhere in the File Management Section. The NASTRAN
statement may also be specified in runtime configuration (RC) files. See Customizing Command
Initialization and Runtime Configuration Files (App. A) in the MSC Nastran Installation and Operations
Guide.
2. System cell values and their associated cell names may also be set with the DEFINE statement. They
may also be set or values returned with the DMAP PUTSYS and GETSYS functions and the PARAM
module. See PUTSYS, GETSYS in the DMAP Programmer’s Guide.
3. More than one NASTRAN statement and/or DEFINE statement may be present and, if a system cell
is specified more than once among these statements, then the last specification takes precedence.
4. The expression will use type conversion rules based on the type (i.e., integer, real, or logical) of the
cellname, as defined on a previous DEFINE statement (see the DEFINE statement for conversion
rules).
5. If expression is omitted, the system cell associated with the cellname will be assigned the value as set
on a previous DEFINE statement.
Examples:
1. Either of the following statements could be used to change the default value for block size.
NASTRAN SYSTEM (1) = 8193
or
NASTRAN BUFFSIZE = 8193
or, if a prior DEFINE statement had defined a keyword MY_SYSBUF to the value 8193, then the
following code could be used:
Main Index
18 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
NASTRAN SYSTEM(1)=MY_SYSBUF
or
NASTRAN BUFFSIZE=MY_SYSBUF
2. Table 2-1 gives a summary of the recommended system cells. System Cells
.
Table 2-1 System Cell Summary
System Cell
Name (Number) Function and Reference
BUFFSIZE (1) Specifies the number of words in a physical record. Also called block
length. (Integer > 0: For DOF < 100000, Default=8193;
For 100000 ≤ DOF < 400000, Default=16385;
For DOF ≥ 400000, Default=32769)
F06 (2) Specifies FORTRAN unit number for standard output file (.f06).
(Integer>0; a value of 0 sends the results to the log file; Default=6).
This system cell may not be set for SOL 700.
NLINES (9) Specifies the number of lines printed per page of output (Integer > 0;
Default = 50). LINE (Case).
MAXLINES (14) Specifies the maximum number of output lines allowed (Integer > 0;
Default = 999999999). MAXLINES (Case)
METIME (20) Minimum time for execution summary table message. Output Description
in the MSC Nastran Reference Guide.
APP (21) Approach Flag. See the APP Executive Control statement. If APP
HEAT is specified, then this system cell is set to 1.
MACHTYPE (22) Machine type
DIAGA (25) Alternate method to set DIAGs 1 through 32. DIAG.
CONFIG (28) Machine subtype
ADUMi (46 - 54) Dummy element flag, i=1 through 9.
HEAT (56) APP
0 Structural analysis (Default).
1 Heat transfer
DIAGB (61) Alternate method to set diagnostics 33 through 64. DIAG.
PUNCH (64) Specifies FORTRAN unit number for PUNCH file (.pch).
(Default=7)
MPYAD (66) Selects/deselects multiplication methods. MPYAD in the MSC Nastran
DMAP Programmer’s Guide.
DCMPOUT(69) Controls matrix decomposition for MSCLDL and MSCLU. Same as
DECOMP in the MSC Nastran DMAP Programmer’s Guide and the Option
Selection in the MSC Nastran Numerical Methods User’s Guide.
Main Index
CHAPTER 2 19
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
0 or -1 Print up to 50 messages for null columns and zero diagonals
(Default=-1).
1 Terminates execution when first null column is encountered.
2 Suppress printing of message when a null column is
encountered.
4 Terminates execution when first zero diagonal term is
encountered.
16 Place 1.0 in diagonal position for all null columns and
proceed with the decomposition.
32 Terminates execution on zero diagonal term.
64 Exit after execution of preface for symmetric decomposition.
256 Print MAXRATIO messages (SIM 4159) from DCMP.
DELFF (77) Deletes form feeds.
DBSET Database neutral file set. SubDMAP DBFETCH in the MSC Nastran DMAP
Programmer’s Guide.
DMAP (82) Allows NOGO to operate. See Processing of User Errors in the MSC
Nastran DMAP Programmer’s Guide.
F04 (86) Specifies FORTRAN unit number for Execution Summary Table
(.f04). Output Description in the MSC Nastran Reference Guide (Integer >
0; a value of 0 sends the results to the log file; Default = 4).
RADMTX (87) Type of radiation exchange coefficients, RADMTX.
0 Energy can be lost to space (Default).
1 Direct input of a symmetric SCRIPT-AF matrix on
RADMTX and RADLST entries is allowed. Due to the
symmetry, only one-half of the RADMTX may be entered.
2 Direct input of a unsymmetric SCRIPT-AF matrix on
RADMTX and RADLST entries is allowed. Due to the
unsymmetry, the full matrix must be specified on the
RADMTX entries.
3 If you are running a view factor calculation in an opened
enclosure, NASTRAN assumes that the radiation will be lost
to space at absolute zero degrees Kelvin. You can set
SYSTEM(87)=3 so that radiation will not be lost to space.
RADLST (88) Print radiation area summary. RADLST.
SMP (107) Number of processors used for Shared Memory Parallel
Main Index
20 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
NEWHESS (108) Request complex eigenvalue method. See the EIGC entry, MSC Nastran
Numerical Methods User’s Guide.
(109) Controls DMAP execution:
0 Do not execute DMAP instruction if all outputs are
previously computed.
1 Always execute DMAP instruction (Default).
BUFFPOOL (114) Bufferpool size. Keywords and Environment Variables in the MSC Nastran
Installation and Operations Guide.
(119) Controls the type of bufferpool method to be used:
4 Use Version 2012.2 bufferpool method (Default).
≠4 Use Version 2012.1 bufferpool method.
ATTDEL (124) Controls the automatic assignment of the delivery database. Database
Concepts in the MSC Nastran Reference Guide. See also Creating and
Attaching Alternate Delivery Databases in the MSC Nastran Installation and
Operations Guide.
0 Enables automatic assigning (Default).
-1 Disables automatic assigning.
NOKEEP (125) Controls NOKEEP option of the RESTART File Management
statement.
0 Disable NOKEEP (Default)
1 Enable NOKEEP
SPARSE (126) Sparse matrix method selection for MSCLDL and MSCLU. For
unsymmetric sparse matrix decomposition method selection, see cell
number 209. The following values may be summed in order to select
sparse matrix methods in the operations listed below:
0 Deactivate sparse methods
1 Multiplication
8 Symmetric decomposition
16 Forward-backward substitution
The default is 25, which is the sum of all values.
UPDTTIM (128) Specifies database directory update time.
DBUPDATE, 92 FMS statement.
0 Do not update.
Main Index
CHAPTER 2 21
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
>0 Time, in minutes, between database directory updates.
(Default = 5 min.)
SMPYAD67 (129) Select pre-Version 67 method in the SMPYAD module. SMPYAD in the
MSC Nastran DMAP Programmer’s Guide.
0 Use current method (Default).
1 Use pre-Version 67 method.
MAXDBSET The maximum number of online DBsets attached to the run.
AUTOASGN (133) Controls autoassigning of dbsets. Sum the desired values.
(Default=7). Database Concepts in the MSC Nastran Reference Guide.
0 No databases are automatically assigned.
1 Only the primary database is automatically assigned.
2 Only the delivery database is automatically assigned.
4 Only located databases are automatically assigned.
TSTAMP (135) Controls timestamp checking of DBsets.
0 Do not check
1 Check (Default)
2 Same as 1 and print diagnostics
QUADINT (141) Specifies quadratic or linear interpolation for the line search method in
nonlinear analysis (SOL 106, SOL 129, and SOL 153).
0 Quadratic interpolation (Default)
1 Linear interpolation
SCR300 (142) Requests creation of SCR300 partition on SCRATCH DBset.
INIT FMS statement.
1 Do not create SCR300 partition.
2 Create SCR300 partition (Default).
LOCBULK (143) LOCBULK=1 or 2 specifies that Bulk Data is being obtained via the
DBLOCATE FMS statement. NASTRAN LOCBULK=2 is specified
when no Bulk Data entries, except for PARAM entries, are to be
deleted or added. All PARAM entries must be respecified. All other
entries will be ignored and, if present, may increase CPU times in
XSORT and IFP. With LOCBULK=2, the XSORT and IFP modules
will not reprocess the Bulk Data Section stored in the SEMAP run.
Also, GP1, TASNP2, SEP1 and SEP1X modules will be skipped. 0 is
the default, which assumes the RESTART FMS statement. This
system cell is recognized only in SOLs 101 through 200.
Main Index
22 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
(144) RESTART FMS statement existence flag. Set to 1 if RESTART
statement is present.
BFGS (145) Selects strategies of BFGS updates for the arc-length methods in
nonlinear analysis. Please see the Arc-Length Methods for Post-buckling
Analysis in MSC Nastran Nonlinear (SOL 400) User’s Guide.
0 Update u R and u p at every iteration with * . (Default)
1 Update u R only with
2 Update u R only with * .
FBSMEM (146) Reserve part of Nastran open core memory for I/O reduction during
FBS operations. (Default=0).
-1 or 0 Use available memory to store as much of the factor matrix
as possible during FBS operations. System Information
Message 4199 is printed in the F04 file.
1 Disable all special memory operations for FBS.
2 Increase memory reserved for sparse method by
approximately 200%.
3 Increase memory reserved for sparse method by
approximately 300%.
4 Increase memory reserved for sparse method by
approximately 400%.
UWM (147) SYSTEM(147)=1 issues a User Warning Message for a DMAP
parameter appearing on a CALL statement that has an inconsistent
authorization in the called subDMAP. 0 is the default, which means no
message is issued. A value of 1 also issues User Warning Message 1
during DMAP compilation if a module instruction is missing trailing
commas for input and output data blocks.
DBVERCHK (148) In general, databases are not compatible between major releases;
therefore, a check is performed in MSC Nastran to ensure that the
major version which created the database is the same as that being
executed. Since specific data on the database may be compatible,
SYSTEM(148) allows this check to be circumvented. However,
circumventing the check may lead to problems later in the run.
0 Check is performed (Default)
1 Check is not performed
SCR300DEL (150) Sets minimum number of blocks of SCR300 partition of SCRATCH
DBset at which it is deleted. INIT FMS statement (Default = 100).
Main Index
CHAPTER 2 23
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
(151) Requests spill or no spill of the SCR300 partition of SCRATCH
DBset. INIT FMS statement (Default = 0).
DBLAMKD (155) Differential stiffness formulation for CBEAM and CTETRA elements.
0 Current formulation (Default)
1 Pre-Version 67 formulation
(162) Reserves MSC Nastran executive first number for GINO for each of
the tables DBTEMP, FCB, DBDICT and FIST. Default value is 6000
and is often controlled in DMAP just before and just after modules
that deal with large input families. Usually a user will have no need to
modify. However if the user gets the following message:
*** SYSTEM FATAL MESSAGE 1267 (XSTORE)
NO MORE MEMORY SPACE AVAILABLE FOR EXECUTIVE
TABLES.
USER ACTION: INCREASE DEFAULT NUMBER OF
EXECUTIVE TABLES ENTRIES VIA SYSTEM CELL 162.
SYSTEM(162) IS CURRENTLY SET TO 6000
A DMAP workaround is of the form:
Just before the offending module
NP=GETSYS(NP,162) $
NP1= value $ value > 6000
PUTSYS(NP1,162) $
Just after offending module
PUTSYS(NP,162) $
(166) Controls sparse symmetric decomposition. Sum the desired values
(Default = 0).
0 No action
1 If insufficient core is encountered, then switch to
conventional decomposition and continue (Default).
2 Print diagnostics.
4 Do not issue fatal message if maximum ratios are exceeded.
Although high maximum ratios may be printed, they will not
cause job termination. This applies to the DCMP,
DECOMP, REIGL, and LANCZOS modules.
8 Output a matrix containing the maximum ratio vector in the
output slot for the upper factor.
32 Turn off internal matrix scaling in the READ module.
Main Index
24 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
64 Turn off internal matrix balancing in the READ module.
8192 Use in-core sparse Cholesky factorization method. Only
valid for the DCMP, SOLVE, and DECOMP modules. The
in-core sparse CHOLESKY factorization code is derived
from the TAUCS software package. See
http://www.tau.ac.il/~stoledo/taucs/ for more information.
LDQRKD (170) Selects the differential stiffness method for CQUAD4 and CTRIA3
elements:
0 Version 68, improved method (Default).
1 Pre-Version 68 method
OLDQ4K (173) Requests the pre-Version 68 CQUAD4 element stiffness formulation.
No value is required after the keyword. Equivalent to
SYSTEM(173)=1.
0 Default: Current QUAD4 formulation
1 Requests pre-V68 QUAD4 formulation.
2 Requests V68 - V70.5 QUAD4 formulation.
Q4TAPER (189) Specifies the maximum allowable value of taper for CQUAD4
element. Taper is computed by connecting opposite grid points and
computing the area of the enclosed triangles. Another way to think of
taper is the ratio of the areas on the two sides of a diagonal (Real > 0.0;
Default = 0.5).
Q4SKEW (190) Specifies the minimum allowable value of skew for the CQUAD4
element. Skew is the angle measured in degrees between the lines that
join opposite midsides (Real > 0.0; Default = 30.0).
TETRAAR (191) Specifies the maximum allowable aspect ratio of the longest edge to the
shortest altitude for the CTETRA element (Real > 0.0;
Default=100.0).
FRQSEQ (195) Lanczos High Performance Option: 100*Exponent for the rational
function used to determine segment boundaries. See also the ALPH
field on the EIGRL Bulk Data entry. (Integer; Default = 0, which means
equal segments.)
SCRSAVE (196) Lanczos high performance option: Controls reuse of scratch files in
segment logic.
0 Do not reuse (Default)
1 Reuse
Main Index
CHAPTER 2 25
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
MINFRONT (198) Lanczos high performance option: minimum front size. (The default
value is machine dependent).
NSEGADD (200) Number of segments in the element error table that is generated in
adaptive analysis (Default = 2).
CORDM (204) Specifies the default value for CORDM field on the PSOLID entry
(Integer >-1; Default = 0).
(205) Rank to use for real symmetric sparse decomposition high rank update.
Default is hardware dependent.
DCMPSEQ (206) Selects ordering method for sparse matrix decomposition.
0 Method selected automatically in symbolic factoring phase
(Default).
1 Minimum degree ordering.
2 Modified minimum degree ordering for indefinite matrices.
3 No ordering (uses given sequence).
4 Extreme ordering. (BEND)
8 METIS ordering. Metis was developed by George Karpis and
Vipin Kumar at the University of Minnesota. More
information may be found at
http://www.cs.umn.edu/~karypis/metis.
9 Selects the better of METIS and MMD.
10 Selects dof-based (rather than grid-based) modified
minimum degree ordering.
68 This option may reduce the number of nonzero factors in the
sparse decompensation method.
132 Similar to 68 but does not require the USET and SILS table
as input. Uses extreme reordering.
136 Same as 132 but performs METIS reordering.
260 Selects dof-based (rather than grid-based) extreme ordering.
264 Selects dof-based (rather than grid-based) METIS ordering.
1024 Selects Minimum Degree reordering in Intel MKL Pardiso
sparse solver.
2048 Selects METIS reordering in Intel MKL Pardiso sparse
solver.
4096 Selects OpenMP (SMP) METIS reordering in Intel MKL
Pardiso sparse solver.
Main Index
26 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
USPARSE (209) Unsymmetric sparse matrix method selection for the decomposition
and forward-backward substitution operations.
0 Deactivate
1 Select Nastran unsymmetric sparse factorization (Default).
16 Select UMFPACK unsymmetric sparse factorization.
64 Select LUSOL unsymmetric sparse factorization.
PUNCHTYPE (210) Used to control punch formula.
0 “Old” punch, default in MSC Nastran 2001 and earlier
versions.
1 “New” punch, default starting in MSC Nastran 2004 and
uses the NDDL.
2 Same as 1 except the line numbers are eliminated.
DISTORT (213) Element distortion fatal termination override. Applies to the TETRA
element.
0 Terminate run (Default)
1 Do not terminate run.
T3SKEW (218) Allows the user to control the minimum vertex angle for CTRIA3
elements at which USER WARNING MESSAGE 5491 is issued. See
the description of CTRIA3.
(219) Rank to use for complex symmetric sparse decomposition high rank
update (Default = 1).
(220) Rank to use for real unsymmetric sparse decomposition high rank
update (Default = 1).
(221) Rank to use for complex unsymmetric sparse decomposition high rank
update (Default = 1).
(253 - 262) SYSTEM(252) to (262) have been set aside for user DMAPS. MSC
will not use these values in its code in present or future versions. The
SSSAlter library may use this range.
MAXSET (263) Controls the default number of vectors in block or set for Lanczos
Eigenvalue extraction. See EIGRL. The default is 7 for most machines
but it is machine dependent.
QUARTICDLM (270) A value of 1 selects the new quartic formulation of the doublet lattic
kernel (N5KQ), while 0 selects the original quadratic form (Default =
0).
Main Index
CHAPTER 2 27
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
(273) A value of 1 selects the old Lanczos shift logic from Version 70 and
previous systems (Default = 0).
DBCFACT (274) Option to create an xdb file with a multi-key data format and is
intended for “large” xdb files.
0 no multi-key format (default)
2 auto-select multi-key format
4 multi-key format
(275) Specifies the timeout for ISHELL in seconds. Values greater than
2,678,400 (31 days) will be set to 31 days.
SPLINE_METRICS (281) Print additional spline quality information
=0 Don't print (default).
=1 Print quality information for each user-generated spline.
=2 Print quality information for each user-generated spline and
each Nastran-generated center-to-corner point spline.
Note that if SPLINE_METRICS is defined on the NASTRAN
statement without a numeric value, then a value of 1 will be used.
MINDEF (303) Indefinite mass matrix check, the Default = 1 does not perform the
check.
>0 Check is not performed
<0 Epsilon is set to -1.E(MINDEF)
0 MINDEF defaults to -6
MPERTURB (304) Perturbation factor for indefinite mass matrix. The Default = 1 does
not perturb the mass.
>0 The mass is not perturbed
<0 The mass 1.E(MPERTURB) is added to the diagonal terms
of the mass matrix
0 MPERTURB defaults to -6. The perturbed mass matrix is
used in the subsequent eigenvalue analysis
(309) If set to 1, requests the pre-Version 70.7 CHEXA8 element stiffness
formulation (Default = 0).
OLDRBE3 (310) If set to 1, requests the pre-Version 70.7 RBE3 formulation
(Default = 0).
TBCMAG (311) Change the stiffness to 1.0E2 if using thermal conductivity in
Btu/sec/in.F. See Bulk Data entry TEMPBC for more information. The
default stiffness is 1.0E10.
Main Index
28 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
INDEX (316) Indexes and/or saves a minimum set of data blocks to the database
needed to for postprocessing in Patran or the toolkit (Default = 0).
This cell must be used with scratch=no on the nastran command. This
cell has several options which are set by adding the following values:
1 Index IFP data blocks.
2 Index OFP data blocks.
4 Save above data blocks to the MASTER dbset.
16 Save above data blocks to the DBALL dbset.
For example, INDEX=7 will index the IFP and OFP data blocks and
save them to the MASTER dbset. (Scratch=post is equivalent to
scratch=no and INDEX=19.) But with INDEX>0 the resulting
database is not restartable.
XMSG (319) If set to 1, gives extended error messages (Default = 0).
OLDDAREA (320) Controls the conversion of DAREA Bulk Data entries for grid and
scalar points to equivalent FORCE/MOMENT/ SLOAD Bulk Data
entries as appropriate.
0 Perform the conversion, but do not give details of the
conversion (Default).
N Perform the conversion and give details of the first N such
conversions.
-1 Do not perform the conversion.
RSEQCONT (357) If system cell IFPSTAR=NO, RSEQCONT default = 0
1 causes all continuation fields to be ignored and treated as
blank. If set to 1, the continuation entries must immediately
follow the parent
2 causes fatal message to be issued if there are orphaned
continuation entries.
System cell (357) only works when IFPSTAR=NO, it is fixed to 1
when IFPSTAR=YES
Main Index
CHAPTER 2 29
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
QLHOUL (359) 0 Use the user-requested eigensolution method.
≠0 When LAN is requested, switch to AHOU if the number of
DOFs sent to the eigensolver is < “nswitch”, an input
parameter to the READ module. This parameter has an MPL
default of 20. It may be set to other values in the solution
sequences, depending on the context. When HOU,
MHOU, or AHOU is selected, switch to the new
Householder-QL solution (Default = 1).
PRTPCOMP (361) If set to 1, then the equivalent PSHELLs and MAT2s from PCOMPs
or PCOMPGs are printed to the .f06 file provided that
ECHO = NONE is not set. (Default = 0, suppresses this printout).
STRICTUAI (363) A value of 1 accepts strict UAI/Nastran Bulk Data entries
(Default = 0).
STPFLG (366) Selects the SUBCASE or STEP layout when there are a number of
SUBCASE commands and no STEP command in a Case Control file
for SOL 400 (Default = 0).
0 Keep all SUBCASE commands in the Case Control
file and insert a “STEP 1” for each SUBCASE.
1 Convert all the SUBCASE IDs into STEP IDs, and
then insert a “SUBCASE 1” before the first STEP.
QRMETH (370) When the input consists of CQUADR/CTRIAR elements,
QRMETH allows you to convert them to QUAD4/TRIA3 elements
or when the input consists of QUAD4/TRIA3 elements to convert
them to CQUADR/CTRIAR elements.
Some of the output requests for CQUAD4/CTRIA3 are not available
for CQUADR/CTRIAR, for example, the CUBIC option on the
STRESS Case Control command. In this case, the equivalent
CQUADR/CTRIAR options are used.
0 Use the user input CQUADR/CTRIAR elements. (Default)
3 Converts user input CQUADR/CTRIAR into
CQUAD4/CTRIA3.
5 Converts user input CQUAD4/CTRIA3 into
CQUADR/CTRIAR.
PARAMCHK (372) DMAP parameter initialization check.
0 Issue User Fatal Message for an input parameter that is not
used in a type statement in the subDMAP argument
(Default).
Main Index
30 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
1 Issue User Fatal Message for the initialized parameter.
TZEROMAX (373) Controls time step adjustment in nonlinear transient analysis.
>0 Maximum number of times to return to time zero.
0 No initial time step adjustment (identical to V2001), default
for SOL 400 with CGAP elements.
<0 No limit on DT adjustment.
4 Default for SOL 400 without CGAP element or for SOL
129.
NOLIN (386) (Real, Default = 1.0) Tolerance value for controlling adaptive time step
bisection for NOLIN1 entries in SOL 129. Turned off for rotor
dynamics. For NLRGAP see SYSTEM (431).
0. Bisection is suppressed (same as Version 2001).
.001 Increase accuracy slightly.
.01 Increase accuracy a little more.
1.0 Allow full adaptive time step bisection.
KRYLOV1 (387) Fast direct frequency response option.
-1 Yes
0 No (Default)
KRYLOV2 (388) Options related to fast direct frequency response analysis.
Selects subspace generation method.
1 Lanczos (Default)
2 Arnoldi (Use for unsymmetric systems)
KRYLOV3 (389) Options related to fast direct frequency response analysis. Defines
exponent of relative accuracy.
-4 Error<1.0E-4 (Default)
-6 Error<1.0E-6
KRYLOV4 (390) Options related to fast direct frequency response analysis.
Defines pole selection distance.
0 Next pole is next unconverged frequency (Default).
2 2*next frequency distance.
-2 1/2*next frequency distance.
KRYLOV5 (391) Options related to fast direct frequency response analysis. Selects
decomp/fbs tradeoff parameter determining Krylov method accuracy.
Main Index
CHAPTER 2 31
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
0 never terminate, do FBS iterations till accuracy is met
1 terminate when FBS time > decomposition time (Default)
2 terminate when FBS time > 2 * decomposition time
-2 terminate when FBS time > (1/2) * decomposition time
BARMASS (398) Allows the user to select the bar torsional mass moment of inertia.
If set to 0, request the pre-MSC Nastran 2004 (Default = 0).
If set to greater than 0, the torsional mass moment of inertia term is
included in the mass matrix formulation of bar elements. For both
values of COUPMASS, the torsional inertia is added.
For COUPMASS = 1, the axial mass will be consistent rather than
coupled.
DPBLKTOL (402) Specifies Bulk Data tolerance value for GRID, CORD2C, CORD2R,
and CORD2S entries. (Default = 0). See / Control Input Stream
section under Bulk Data Entries below
<0 Do not remove duplicate entries
0.0 Check specified Bulk Data entries for exact physical match
and remove duplicates
>0 Then perform the DPBLKTOL=0.0 check and additionally
GRID entry as duplicate if
{ x1 i – x2 i DPBLKTOL ; i = 1, 2, 3 and
( cp1 cp2 and cp1 cp2 = 0 ) and ( cd1 cd2 and
cd1 cd2 = 0 ) and (ps1 = ps2) and (seid1 = seid2)} using
entry with cpi 0 and cdi 0 if possible
OP2NEW (403) Selects the additional version information in the OUTPUT2 file.
(Default = 0)
0 Leave alone and unidentified, pre-2004 convention
1 Add version major, minor, special to tape label and change
IFP datablock locate code word 3
DEF_DENS (408) Set DEFAULT value for the MODEL_CHECK Executive statement
MAT_DENSITY=DEFAULT operation (Default = 0.0).
DEF_TECO (410) Set DEFAULT value for the MODEL_CHECK Executive statement
MAT_TECO=DEFAULT operation (Default = 0.0).
DEF_TEIJ (411) Set DEFAULT value for the MODEL_CHECK Executive statement
MAT_TEIJ=DEFAULT operation (Default = 0.0).
DEF_DAMP (412) Set DEFAULT value for the MODEL_CHECK Executive statement
MAT_DAMP=DEFAULT operation (Default = 0.0).
Main Index
32 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
OPTCOD (413) Specifies which optimization code to be used in SOL 200 (Default =
0; automatic selection for a better performance based on number of
design variables, number of constraints, number of active/violated
constraints and computer memory).
Note: Options 1 and 2 are no longer used.
3 MSCADS
4 IPOPT Optimizer
(414) Only used if COUPMASS < 0. Default = 0 Coupled Mass for CBAR
and CBEAM elements.
>0 Lumped Mass matrix will contain translational components
only for CBAR and CBEAM elements.
MDAMPEXT(426) (Integer, Default=0) If a modal damping value is computed as a result
of extrapolation and it is negative, the program terminates the job with
a user fatal message.
0 Job terminates if one or more extrapolated modal damping
values are negative.
1 Do not terminate the job if one or more extrapolated modal
damping values are negative.
OLDTLDMTH (428) If nonzero, requests the pre-version 2005 r3 method for computing
thermal expansion in CHEXA, CPENTA, and CTETRA elements.
(Default = 0).
NONLRGAP (431) (Real, Default = -1.0) Sets tolerance value for controlling adaptive time
step bisection for NLRGAP entries in SOL 129 and SOL 400. Time
step bisection will occur if the contact force magnitude changes more
than the tolerance.
= 0. (Same logic as Version 2005)
< 0. Tolerance = 1.E+9
> 0. Tolerance = 1000./SYSTEM(431)
ESLNRO (443) Flag to invoke Nonlinear Response Optimization with the concept of
Equivalent Static Loads
0 No ESLNRO (Default)
1 Turn on ESLNRO
(444) 0 Selects the pre Nastran 2010 release of IFP for bulk data
processing.
Main Index
CHAPTER 2 33
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
1 Selects the MSC Nastran 2010 release Common Data Model
for data processing, do not allow an integer in a field that the
only possible format is real. (Default)
9 Selects the MSC Nastran 2010 release Common Data Model
for data processing, allow an integer in a field that the only
possible format is real.
IFPSTAR YES Selects the MSC Nastran 2010 release Common Data Model
for data processing, do not allow an integer in a field that the
only possible format is real. (Default)
NO Select the pre MSC Nastran 2010 IFP for bulk data
processing.
On command line IFPSTAR=YES or NO is able to express the value
of 1 or 0 only.
MNLQ4C (445) Allows or disallows corner stress calculations for CQUAD4 if material
nonlinear (Default = 1).
0 Allows material nonlinear CQUAD4 corner stress
calculations if plastic deformation has occurred, results may
be totally incorrect.
1 Disallows material nonlinear CQUAD4 corner stress
calculations. If corner requested and material nonlinear
sensed, corner is turned off and center only is computed.
(446) Controls 4 noded CTETRA fluid mass calculations. (Default=0)
0 To improve the modal results for fluid mass and remove the
possibility of spurious fluid modes, a four point integration
method is used.
1 A one point integration method is used to compute the fluid
mass.
Main Index
34 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
PARCHILD(449) Bitwise control of DMP operations in SOL 400 nonlinear analysis.
Bit Value Description
1 Default System determines automatically at job startup.
When running the job on multiple hosts, the value
is set to 0; otherwise (single host), it is set to 1. User
setting of PARCHILD is not recommended.
0 Child processes execute the entire analysis. This
value is recommended for distributed execution.
1 Child processes only participate in parallel
computational tasks. Recommended for DMP
running on a single host (i.e., non-distributed
DMP execution).
2 0 DMP linear equation solver disabled.
1 DMP linear equation solver enabled (default).
3 0 DMP nonlinear element matrix generation
disabled.
1 DMP nonlinear element matrix generation
enabled (default).
To change defaults for this system cell, use the DOMAINSOLVER
command in the MSC Nastran Quick Reference Guide.
(451) If set nonzero, requests the method to calculate transverse shear
correction for elements using MID4, or “Z0” on the PCOMP to offset
a shell element. The default 0 uses a new method that avoids excessive
transverse shear stiffness. This is expected to have small effect on most
models, unless the shell is thick and the offset is large.
IFPBUFF(624) Specifies the size of IFPSTAR data base I/O transfers
Default value=1024 words
The physical I/O size is IFPBUFF words. The maximum value of
IFPBUFF is 65536 words.
Example: NASTRAN IFPBUFF=8192
Main Index
CHAPTER 2 35
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
NONUPIV (653) Parameter to select the numeric compute kernel and pivoting methods
in MSCLDL and MSCLU sparse direct solvers. Also see the bulk data
entry MDLPRM, 2210,NONUPIV.
0 Use the native Bunch-Kauffman threshold pivoting in
MSCLDL, and the native threshold partial pivoting in
MSCLU (Default).
1 Use no numeric pivoting in MSCLDL and MSCLU. BLAS3
TRSMs are called to compute the pivot column update to
improve performance. Ill-conditioned models may die of
“singular matrix” during sparse factorization.
3 LAPACK SYTRFs with Bunch-Kaufman pivoting and
GETRFs with partial pivoting are called to perform
factorizations, and BLAS3 TRSMs are called to compute
pivot column update to improve performance.
GPU_MIN_RANK (655) If the rank of the frontal matrix is smaller than value, the rank update
of the front is processed on the CPU. Otherwise, the GPGPU device
would be used for the rank update of the front. The default value for
GPU_MIN_RANK is 32.
GPU_MIN_FRONT (656) The criteria for GPGPU execution during matrix factorization are the
frontal matrix front size and the rank of the frontal matrix. Minimum
dimensions are set via gpu_min_front and its companion parameter,
gpu_min_rank. The value specified must be an integer greater or equal
to 1.
If the front size is smaller than value, the rank update of the front is
processed on the CPU. Otherwise, the GPGPU device would be used
for the rank update of the front. The default value for
GPU_MIN_FRONT is 2048.
(662) Controls CBUSH internal load calculation for radial dependence.
(Default=0)
0 Radial dependence of PBUSHT entries DOES NOT depend
on the alignment of the CBUSH element when subject to
nonlinear force deflection relations.
1 Radial dependence of PBUSHT entries DOES depend on
the alignment of the CBUSH element when subject to
nonlinear force deflection relations.
Main Index
36 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
SEGLOG(664) Control the logic to compute the default value of PENALT in
segment-to-segment contact analysis. Before v2017, Default value is 0.
0 Use the existing/old logic where the default value is based on
the average elastic stiffness of the two contact bodies and the
default error tolerance.
1 Use new logic (Default) for PENALT to avoid a too large
value of PENALT, where the default value is defined by the
body with the softer material and the minimum edge length
of the two contact bodies. This logic is often better for thin
shell structures.
CNTBKCMP(666) Control the logic to compute the contact at shell corners in node-to-
segment contact analysis to ensure backward compatibility.
0 Use the current/new contact logic for shell corners (Default).
This logic uses weighted average normal vector and adjusted
thickness for a better representation of the sharp corner at
both top and bottom of the shell.
1 Use old contact logic for shell corners to ensure backward
compatibility. This logic uses average thickness and average
normal vector even at sharp corners.
(670) Control for Automatic Contact Generation. Used when
BCONTACT=AUTO is present in case control.
0 Default, Nastran run to completion after generating acg file.
3 Nastran terminates after generating acg file.
LMFBKCMP(676) Control the logic to compute the default value of Lagrange multiplier
(LMFACT and PENFN)
0 (Default) Use new algorithm for LMFACT/PENFN, which
are two order lower than previous value used before 2013.0
Version.
1 Use old algorithm used before 2013.0 Version.
FFOBKCMP(677) Control the logic to compute the unloading follower force.
0 (Default) Use new algorithm for unloading follower force,
i.e., follower force in the previous loadcase will be unloaded
by follower force method but not by linear interpolation.
1 Use old algorithm for unloading follower force, i.e., by linear
interpolation (before 2013.0 Version).
Main Index
CHAPTER 2 37
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
OLDLCNTR(678) Ensure backward compatibility for linear connector elements.
0 Use existing (after V2014.1) algorithm with RBE3
relationships for linear connectors (Default).
1 Use old algorithm (V2014.1 or earlier) for linear connectors
to ensure backward compatibility.
PARAM,OLDWELD,YES is equivalent to a value NASTRAN
OLDLCNTR=1
(679) Controls checking for validity of sparse matrix passed to Intel MKL
Pardiso.
0 Disable matrix checking (Default)
1 Enable matrix checking for Column indices must be in
increasing order within rows
2 Enable matrix validity checking for reusing previously
computed permutation in SOL 400
(684) Control of matrix type for Intel MKL Pardiso. For more information,
see Intel MKL Paridso documentation
Main Index
38 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
RDBOTH(695) Parameter to select Rayleigh damping approach for rotordynamics
(compatibility withV2005) implementation, Integer. A cumulative
sum can be provided in case multiple features are desired in the
analysis. The parameter is allowed to take values of 1, 2, 4, 8, 16, or
any combination of them except both 4 and 8 are included, such as 12,
13, 14, etc. by checking binary bits. Default value for this parameter is
0.
0 Uses implementation for Rayleigh Damping as described in
RSPINR/RSPINT entry description (Default)
1 Switch to V2005 implementation of Rayleigh damping
where damping coefficients specified in the model through
“PARAM, ALPHA1” and “PARAM, ALPHA2” are applied
to the complete model and Rayleigh damping specified
through “ALPHAR1” and “ALPHAR2” in
RSPINR/RSPINT are not used
2 Ignore circulation effects in rotordynamic analysis.
4 Include effect of stress stiffening using method = 1 (see
RFORCE entry). Using RFORCE load step to include
differential stiffness in SOL 400 since RDBOTH=4 is not
supported in SOL 400.
8 Include effect of stress stiffening using method = 2 (see
RFORCE entry). Using RFORCE load step to include
differential stiffness in SOL 400 since RDBOTH=8 is not
supported in SOL 400.
16 This option treats rotor structural damping with an
imaginary stiffness matrix for complex eigenvalue analysis.
See RSPINR remark 10.
S2SDEF(701) Parameter to control backward compatibility of Seg-to-Seg contact
default values.
0 Original Seg-to-Seg contact default values
1 Using new Seg-to-Seg contact default values in and after
2016 version. (Default)
Main Index
CHAPTER 2 39
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
HDF5 (702) Control NH5RDB database creation.
-1 Do not create NH5RDB database (Default).
0 Create NH5RDB database without compression.
1 Create NH5RDB database with compression.
2 Create uncompressed NH5RDB database without input
data.
3 Create compressed NH5RDB database without input data.
OBEAMS (725) Control Linear format output of Advanced Nonlinear CBAR Element.
Default: 0
0 New. Output of beam stress is separated into Bending and
Axial stresses.
1 Old. Output of beam stress combines bending and axial
stresses together.
OLDCCONE (726) The CCONEAX Force/Stress Recovery element coordinate system is
inconsistent with the input RINGAX coordinate system relative to the
RINGAX A/RINGAX B order. The CCONEAX Force/Stress
Recovery has now been made consistent. For those who may have post
processing that recognized the inconsistency and do not wish to
change, the inconsistency may be restored with OLDCCONE.
0 Default: Force/Stress output consistent with RINGAX
coordinate.
1 Restore inconsistent RINGAX A/RINGAX B Force/Stress
output.
METS2S (727) Control Segment to Segment contact.
Default: 0
0 Support SEGTOSEG only since 2017 and later version
1 Old. Support SEGTOSEG.
DMP (728) The number of Distributed Memory Processes used. This option is
only useful for specific Solution Sequences as described in the MSC
Nastran HPC User’s Guide
Main Index
40 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
N2SDOF (729) Control node freedom number of contact
Default: 0
0 Depend on contact type: 3 for touching contact; 6 for glued
contact
1 Set the node freedom of contact to be 6 always
H5NORDOF(730) To suppress output rotational components to NH5RDB database
0 Output both translational and rotational components to
NH5RDB database (Default).
1 Do not output rotational components to NH5DB database.
Only used when HDF5(702) is 0 or 1.
(738) Represents the chosen matrix solver used during SOLVE=AUTO in
solution sequences 101, 400, 107 and 200.
In SOL 101, 400, 107:
1 MSCLDL
2 Pardiso
3 CASI
4 MUMPS (except 107)
In SOL 200:
11 MSCLDL and NewACMS
21 Pardiso and NewACMS
31 CASI and NewACMS
12 MSCLDL and Lanczos
22 Pardiso and Lanczos
32 CASI and Lanczos
H5MTX (739) Write matrix data in separate file
1 Write matrix data into a separate file
0 Do not write matrix data into a separate file (Default)
H5MDL (740) Write model input data in separate file
2 Write model input data only
1 Write model input data into a separate file
0 Do not write model input data into a separate file (Default)
-1 Use OP2GM34 setting for GEOM3 and GEOM4 output
Main Index
CHAPTER 2 41
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
(746) Represents the chosen solver used during solve=auto. Utilized in
specific solution sequences 103,111.
1 NewAcms
2 Lanczos
ACCSDLSZ(747) SDL work area memory size of IFPStar, defaut=100000 words
H5GM34 (751) Write GEOM3 and GEOM4 data in NH5RDB
-1 Use OP2GM34 setting (Default).
1 Write GEOM3 and GEOM4 data in NH5RDB
0 Do not write GEOM3 and GEOM4 data in NH5RDB
UDEFGRID(753) Control whether having undefined grid points on ASET/ASET1
entries is allowed.
Default=0.
0 Issue a User Warning Message and continue the simulation.
1 Issue a User Fatal Message and terminate the simulation
CNTBACK(758) BIAS=0.0 on BCONPRG/BCTABLE will be used as 0.0 in analysis.
Before 2018.2, BIAS=0.0 is treated as default, same as blank, which
will turn to the value of BIAS on BCPARA and so the user has to put
a small value to approximate absolute 0.0.
Since 20190.0, segment to-segment initial stress free contact can adjust
geometry to clear gap/penetration.
Default=0.
0 BIAS=0.0 on BCONPRG/BCTABLE is treated as 0.0 and
will override BIAS on BCPARA.
Segment-to-Segment Initial Stress Free: geometry
adjustment as Node-to-Segment method, old method turn
off.
1 (backward compatible) BIAS=0.0 on
BCONPRG/BCTABLE is treated as blank;
BIAS on BCPARA will be used in analysis.
2 Switch to Step Glue if Permanent Glue with LGDISP>1
4 (back to 2018.2) Segment-to-Segment Contact Initial Stress
Free: no geometry adjustment, old method turned on.
8 Segment-to-Segment Contact Initial Stress Free: geometry
adjustment plus old method turned on
Main Index
42 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
OP2IMPV(761) Select option to improve OUTPUT2 performance when converting
data from I8 to I4 binary format.
Default=1
0 Use the old (till V2018.2) I8-I4 conversion method.
1 Use the new conversion method
IGNBLN(767) Control if ignore blank lines in an entry followed by continuation
lines.
0 (Default) Don't ignore and issue UFM when blank lines
followed by continuations are found.
1 Ignore those blank lines.
BLNMEM(768) Memory size in bytes to store blank line numbers in input files.
8000: Default, 8000 bytes.
>=800: User specified size.
<800: Will be forcedly changed to 800.
OPENFSI(776) Type: Integer
OpenFSI interface option.
0: (Default) For implicit type, skip the putWettedNodeDisp
method call when the current time is converged and no
displacement update from last iteration.
1 Do not skip the putWettedNodeDisp call even there is no
displacement update.
Refer to MSC Nastran User Defined Services User's Guide for details.
H5INFO(789) Write job run information in NH5RDB or not.
1 Yes (Default)
0 No
STRNCUR(778) In nonlinear strain recovery for the CQUAD4 and CTRIA3 elements,
especially for nonlinear composites with offsets and MDLPRM
OFFDEF LROFF, an addition final pass of updating midplane strain
and curvature is made. In some cases, this results in strain curvature
results significantly different than those used to obtain the force and
stress results. STRNCUR allows the user to obtain the midplane strain
and curvature, and hence the ply strains, that are identical to the
midplane strain and curvature used in force and stress recovery
operations.
Main Index
CHAPTER 2 43
NASTRAN Statement
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
0 Default: geometric nonlinear midplane strain and curvature
are updated for strain recovery and may not be identical to
those used in force and stress recovery.
1 Geometric nonlinear midplane strain and curvature recovery
values are the same values as used for element force and stress
recovery when nonlinear strain recovery is requested for
elements utilizing LROFF.
2 Geometric nonlinear midplane strain and curvature recovery
values are the same values as used for element force and stress
recovery when nonlinear strain recovery is requested.
CNT101(786) Set Linear Contact (LINCNT=1) as default in SOL 101 only
0 (Default) Linear Contact off/on depends on LINCNT on
BCPARA
Note that Linear Contact is off (LINCNT=0) by default
when no BCPARA entry present.
1 Linear Contact is turned on in SOL 101, regardless of
LINCNT on BCPARA.
H5XHH (790) Write BHH, MHH and KHH matrices in NH5RDB
Main Index
44 MSC Nastran Quick Reference Guide
Executive System Parameter Modification
Table 2-1 System Cell Summary (continued)
System Cell
Name (Number) Function and Reference
0 Do not write BHH, MHH and KHH in NH5RDB
(Default)
1 Write BHH, MHH and KHH in NH5RDB
DELTAU(800) The CELAS1/3 force convention for linear elements is determined by
the relationship F=K(U1-U2). For material nonlinear CELAS1/3
elements, initiated via the PELAST, TKNID option, the force
convention is F=K(U2-U1).
0 (Default) Maintain the current PELAST; TKNID
convention F=K(U2-U1) with material nonlinear.
1 Replace the current PELAST; TKNID convention with
the linear convention F=K(U1-U2).
See Remark 6. of the PELAST entry.
OFTDCMP(804) For temperature dependent composites in SOL400 with PARAM,
COMPMATT, YES and a MID4 field specified on the resulting
smeared composite internal PSHELL entry, a MATi/MATTi with the
MATTi tables having identical properties to the original MATi entry,
the element force/moment data recovery gives results that are
inconsistent with the computed element strains when the
force/moments are relatively small in value.
0 Default: For force/moment data recovery for SOL400
with PARAM, COMPMATT, YES and a MID4 field
specified on the resulting smeared composite internal
PSHELL entry, the force/moments are recovered directly
from the nonlinear iterations at convergence.
1 For force/moment data recovery for SOL400 with
PARAM, COMPMATT, YES, the old method of
force/moment data recovery is restored. Essentially and
average stress across the plies times the ply thickness.
Main Index
Chapter 3: File Management Statements
MSC Nastran Quick Reference Guide
3 File Management
Statements
Key to Descriptions
The File Management Section (FMS)
Main Index
46 MSC Nastran Quick Reference Guide
Key to Descriptions
Key to Descriptions
A brief sentence about
the function of the
statement is given.
If the describers are
stacked vertically,
Describers in uppercase then only one may
letters are keywords that be specified.
must be specified as shown.
Describers in lower
case are variables.
The default
describers are
Brackets [] indicate that shaded.
a choice of describers Braces { } indicate that
is optional. a choice of describers
is mandatory.
Each of the describers is discussed briefly.
Further details may be discussed under
Remarks.
If the describer is in lower case, then it is a variable
and the describer’s type (e.g., Integer, Real, or
Character), allowable range, and default value are
enclosed in parentheses. If no default value is given,
the describer must be specified by the user.
The
Theremarks
remarksarearegenerally
generallyarranged
arrangedininorder
orderofof
importance
importanceand andindicate
indicatesuch
suchthings
thingsasasthe
the
statement’s
statement’srelationship
relationshiptotoother
otherstatements,
statements,
restrictions
restrictionsand
andrecommendations
recommendationsononitsitsuse,use,
and
andfurther
furtherdetails
detailsregarding
regardingthe
thedescribers.
describers.
Main Index
Chapter 3: File Management Statements 47
The File Management Section (FMS)
The File Management Section (FMS)
The File Management Section (FMS) is primarily intended for the attachment and initialization of Database
sets (DBsets) and FORTRAN files. The initialization of DBsets includes specification of their maximum size,
member names, and physical filenames. The initialization of FORTRAN files includes the specification of
their filenames, FORTRAN unit numbers, and FORTRAN attributes.
In most classes of problems that use MSC Nastran solution sequences (SOLs), no File Management
statements are required because a default File Management Section is executed at the beginning of every run.
The default File Management Section is described in the Database Concepts in the MSC Nastran Reference
Guide. If a restart is desired, then the RESTART statement is required. All other solutions may not be
restarted. If the problem is large in terms of requiring significant amounts of memory or disk space, then the
INIT, ASSIGN, and EXPAND statements may be required. If any FORTRAN files are required, then the
ASSIGN statement is required; for example, the OUTPUT2 DMAP module. The ASSIGN statement is also
required to assign databases for DBLOCATE, DBLOAD, and DBUNLOAD. Special database operations are
performed by the DBLOCATE, DBLOAD, DBUNLOAD, DBLCLEAN, ACQUIRE, DBDICT, DBFIX,
DBSETDEL, DBUPDATE, and PROJECT statements.
File Management Statement Summary
The following is a summary of all File Management statements:
$ Comment statement.
ACQUIRE Selects NDDL schema and MSC Nastran delivery database.
ASSIGN Assigns physical files to DBset members or special FORTRAN files.
CONNECT Group geometry data by evaluator and database.
DBCLEAN Deletes selected database version(s) and/or projects.
DBDICT Prints the database directory in user-defined format.
DBFIX Identifies and optionally corrects errors found in the database.
DBLOAD Loads a database previously unloaded by DBUNLOAD.
DBLOCATE Obtains data blocks and parameters from databases.
DBSETDEL Deletes DBsets.
DBUNLOAD Unloads a database for compression, transfer, or archival storage.
DBUPDATE Specifies the time between updates of the database directory.
ENDJOB Terminates a job upon completion of FMS statements.
EXPAND Concatenates additional DBset members to an existing DBset.
INCLUDE Inserts an external file in the input file.
INIT Creates a temporary or permanent DBset.
NASTRAN Specifies values for system cells.
PROJ Defines the current or default project identifier.
Main Index
48 MSC Nastran Quick Reference Guide
The File Management Section (FMS)
The FMS statements are executed in the following order regardless of their order of appearance in the input
file:
NASTRAN, DEFINE
RFINCLUDE, INCLUDE
ASSIGN, INIT, EXPAND, DBUPDATE
PROJECT
DBCLEAN
DBFIX
DBDICT(1)
DBSETDEL
ACQUIRE
RESTART
DBLOCATE
DBUNLOAD
DBLOAD
DBDIR (2), DBDICT(2)
ENDJOB
If DBDICT is specified before any of the FMS statements DBSETDEL through DBLOAD, then the
directory printout will reflect the processing of DBCLEAN and DBFIX only. If DBDICT is specified after
DBSETDEL through DBLOAD, then the directory printout will reflect the processing of all statements in
the FMS Section. We recommend that the DBDICT statements be specified last in the FMS Section.
Multiple DBLOCATE, DBLOAD, or DBUNLOAD statements are processed in the order in which they
appear. If the ENDJOB statement is specified, then only the File Management Section is processed and the
Executive Control, Case Control, and Bulk Data Sections are ignored.
File Management Statement Descriptions
File Management statements may be abbreviated down to the first four characters as long as the abbreviation
is unique relative to all other statements. Each statement is described as follows:
Description
A brief sentence about the function of the statement is given.
Format
Describers in uppercase are keywords that must be specified as shown. In addition, describers in lowercase
indicate that the user must provide a value.
Main Index
Chapter 3: File Management Statements 49
The File Management Section (FMS)
Braces { } indicate that a choice of describers is mandatory. If the describers are stacked vertically, then only
one may be specified.
Brackets [ ] indicate that a choice of describers is optional. If the describers are stacked vertically, then only
one may be specified.
Describers that are shaded indicate the defaults.
If the statement line is longer than 72 columns, then it may be continued to the next line with a comma as
long as the comma is preceded by one or more spaces and no keyword is split across lines. For example:
DBLOCATE DATABLK=(KAA) ,
WHERE(PROJECT=’FRONT BUMPER’ AND ,
SEID>0 AND VERSION=4) ,
LOGI=MASTER3
However, if a filename is to be continued on the next line, no space must precede the comma, and the
continuation line must have no leading spaces.
Example
ASSIGN SDB=’/jw/johannes/Projects/secret/Aero/Tests/wing/,
Modes/wing_modal.MASTER’
Note that all quote marks shown under formats and examples are right-handed single quotation marks and
must be entered as such. For example:
PROJ=’MYJOB’
Example
A typical example is given.
Describers and Meaning
Each of the describers is briefly discussed. The describer’s type (e.g., Integer, Real, or Character), allowable
range, and default value are enclosed in parentheses. The describer must be specified by the user if no default
value is given.
Remarks
The remarks are generally arranged in order of importance and indicate such things as the FMS statement’s
relationship to other commands, restrictions and recommendations on its use, and further descriptions of the
describers.
WHERE and CONVERT Clauses
The WHERE clause is used in the selection of items (data blocks and parameters) on the DBDICT,
DBLOCATE, DBLOAD, and DBUNLOAD statements. The CONVERT clause modifies qualifier values
of items selected by the WHERE clause on the DBLOCATE and DBLOAD statements.
Main Index
50 MSC Nastran Quick Reference Guide
The File Management Section (FMS)
The WHERE and CONVERT clauses specify values for PROJECT, VERSION, qualifiers, and DBSET.
PROJECT specifies the project-ID that is originally defined on the PROJECT FMS statement at the time
the project is created. VERSION specifies the desired version-ID under the project-ID. Qualifiers are used
to uniquely identify items on the database with the same name. For example, data block KAA has SEID as
one of its qualifiers, which is the superelement ID. An item may have more than one qualifier and the
collection of all qualifiers assigned to an item is called a path. All data blocks and parameters with qualifiers
are defined in the NDDL Sequence (NASTRAN Data Definition Language), see MSC Nastran DMAP
Programmer’s Guide. Data blocks and parameters are defined on the DATABLK and PARAM NDDL
statements. The DATABLK and PARAM statements specify the name of the data block, parameter, and also
its pathname. The pathnames are defined on the PATH NDDL statement, which lists the qualifiers assigned
to the path. Qualifiers are defined on the QUAL NDDL statement. DBSET specifies the desired DBset. The
DBset of an item is specified after the LOCATION keyword on the DATABLK and PARAM NDDL
statement.
The format of the WHERE clause is:
WHERE (where-expr)
where-expr is a logical expression that specifies the desired values of qualifiers, PROJECT, VERSION, and
DBSET. If the result of the logical expression is TRUE for an item on the database then the item is selected.
For example, WHERE(VERSlON=4 AND SElD<>2 AND SElD>0) selects all items under version 4 for all
values of SEID greater than 0 except 2.
A simple where-expr is a comparison using the following relational operators: =, >, <, <, >, >< or <>. For
example, SElD>0 means if SEID is greater than zero, then the logical expression is true. Several simple where
expressions may be joined into one where expression by the following logical operators: AND, OR, XOR,
and EQV. The NOT operator may be used to negate a where expression. For example, NOT(SEID>0) is the
same as SEID< 0. Arithmetic operations and DMAP functions may also be specified in the where expression
(see the MSC Nastran DMAP Programmer’s Guide.)
If a qualifier in a where-expr is not a qualifier in the path of a specified item, then the where-expr is set to
FALSE. If the where-expr does not contain a specification for all qualifiers in the path of an item, then the
unspecified qualifiers will be wildcarded (i.e., quali=*, all values will be selected.) The default values of
qualifiers, PROJECT, VERSION, and DBSET are described under the statement in which the WHERE
clause is specified.
Examples of the WHERE clause are:
1. Select all items in the database for all superelements except 10 and 30 from Version 1.
WHERE (VERSION=1 AND SEID>=0 AND NOT(SEID=10 OR SEID=30))
2. Select all entries in database on DBSET=DBALL from all projects and versions.
WHERE(PROJECT=PROJECT AND VERSlON>0 AND DBSET=’DBALL’)
The CONVERT clause modifies project- and version-ID, DBset-name (see INIT statement), and qualifier
values of items selected by the WHERE clause on the DBLOCATE and DBLOAD statements. It contains
one or more assignment statements separated by semicolons. The format of CONVERT clause is:
CONVERT(PROJECT=project-expr; VERSION=version-expr; ,
DBSET=DBset-expr;quali=qual-expri[;...])
Main Index
Chapter 3: File Management Statements 51
The File Management Section (FMS)
The PROJECT and VERSION statements modify the project-ID (see PROJECT FMS statement) and
version-ID. The DBSET statement modifies the DBset-name. The value of quali will be replaced by
qual-expri for selected items that have quali in their path. qual-expri is any valid expression (see Expressions
and Operators in the MSC Nastran DMAP Programmer’s Guide) containing constants or any qualifier name
defined in the path of the item. If qual-expri contains names of qualifiers not in the path of the selected item,
then a fatal message is issued. If project-expr and/or version-expr produces a project- or version-ID which
does not exist, then one will be created. Also, all version-IDs less than version-expr that do not exist will be
created; but they will be “empty.”
Examples of the CONVERT clause are:
1. Set qualifiers SEID, PEID, and SPC to constants 10, 20, 102 respectively.
CONVERT(SEID=10;PEID=20;SPC=102)
If more than one value of a qualifier is found for an item by the WHERE clause, then each value is
processed in qual-expri to define the new qualifier value for each of the selected items. In the following
example, if the original values of PEID were 1, 2, and 3; then the new values for the SElD qualifier
will be 2, 4, and 6.
2. Set all values of qualifier SElD to be twice the value of the PEID qualifier:
CONVERT(SElD=2*PElD)
Main Index
52 $
Comment
File Management Statements
$ Comment
Used to insert comments into the input file. Comment statements may appear anywhere within the input file.
Format:
$ followed by any characters out to column 80.
Example:
$ TEST FIXTURE-THIRD MODE
Remarks:
1. Comments are ignored by the program.
2. Comments will appear only in the unsorted echo of the Bulk Data.
Main Index
ACQUIRE 53
Selects NDDL Schema
ACQUIRE Selects NDDL Schema
Selects the NDDL schema and MSC Nastran delivery database to be used for primary database creation.
Format:
ACQUIRE NDDL = NDDL
nddl-name
Describer Meaning
NDDL MSC Nastran NDDL schema.
nddl-name Name of a user NDDL schema specified on a COMPILE NDDL statement
when the user NDDL was stored.
Remark:
This statement is used to specify the delivery database when the user wishes to create a solution sequence, yet
use the subDMAP objects or NDDL schema or both from the MSC-supplied delivery database.
Example:
The following requests the MSC Nastran NDDL schema to be used when creating a new database.
ACQUIRE NDDL
SOL MYDMAP
COMPILE DMAP=MYDMAP,SOUOUT=USROBJ
.
.
.
LINK MYDMAP,SOLOUT=USROBJ
Main Index
54 APIM
Define a program to be launched
APIM Define a program to be launched
Define a program to be launched in place of MSC Nastran through the Application Program Interface
Manager
Format:
APIM PROGRAM=PROG ENVIR=ENV
Example:
APIM PROGRAM=ACTWFM ENVIR=NASTPEM
Describer Meaning
PROG Program name to be launched.
Allowed Value: ACTWFM
ENVIR Environment Variable related to the program.
Allowed Value: NASTPEM
Remarks:
1. PROGRAM=ACTWFM stands for Actran Workflow Manager and ENVIR=NASTPEM allows to
perform Nastran PEM analysis using this external program in place of Nastran.
Main Index
ASSIGN 55
Assigns Physical File
ASSIGN Assigns Physical File
Assigns physical file names or other properties to DBset members or special FORTRAN files that are used by
other FMS statements or DMAP modules. Also, assigns physical name and/or other properties to modal
neutral files (.mnf ) for MSC Nastran/ADAMS interface.
Format 1: Assign a DBset member name
= filename1
ASSIGN log-name= = * [TEMP] [ DELETE] [ SYS=’sys-spec’ ]
= *
Format 2: Assign a FORTRAN file
= filename2
ASSIGN logical-key = * [UNIT = u]
= *
STATUS = NEW
OLD
UNKNOWN
FORMATTED
FORM =
UNFORMATTED UNFORMATTED_64
UNFORMATTED_32
UNFORMATTED_MIXED
TEMP
[DEFER ] [ DELETE] [SYS = ‘sys-spec’]
DELZERO
[IMPORT]
Main Index
56 ASSIGN
Assigns Physical File
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 FORTRAN file to the OPCASE using the ASCII option:
ASSIGN OPCASE=’Filename of FORTRAN file’, STATUS=NEW
4. Define SYS parameters for the SCR300 DBset file using the default file name:
ASSIGN SCR300 SYS=’...’
5. Set the default .op2 file format to UNFORMATTED_64 and assign two .op2 files, one to unit 12
with the file name "test_op2.12' and one to unit 35 with file name 'test_op2.35' in ASCII mode.
ASSIGN OUTPUT2 UNFORMATTED_64
...
ASSIGN OUTPUT2='test_op2.12' UNIT=12
ASSIGN OUTPUT2='test_op2.35' UNIT=35 FORM=FORMATTED
6. Assign a Fortran unit to the Universal File (UF) containing the FRF information for a test FRF
component to be used in an FRF Based Assembly (FBA) process.
ASSIGN UNVFILE=’testcomp_unv’ UNIT=25
Describer Meaning
log-name The name of a DBset member name. log-name may also be referenced on an
INIT statement after the LOGICAL keyword.
filename1 The physical filename assigned to the DBset member. If the default filename
(if there is one) is to be used, filename1 may be omitted or specified as * or ‘*’.
See Remark 6.
logical-key Specifies defaults for STATUS, UNIT, and FORM of FORTRAN files for
other FMS statements, DMAP modules, punching, and plotting operations.
filename2 The physical file name assigned to the FORTRAN file. If the default filename
is to be used, filename2 may be omitted or specified as * or ‘*”. See Remark 7.
UNlT=u u is the FORTRAN unit number of the FORTRAN file. If this describer is
omitted and if filename2 is omitted, this ASSIGN statement will update the
defaults for subsequent ASSIGN statements for the same logical-key value. See
Remark 7.
TEMP Requests that the file associated with log-name or logical-key/UNIT be deleted
at the end of the run. Warning, using TEMP on OP2 or XDB files will result
in the inability to postprocess the results.
DELETE Requests that the file associated with logical-key/UNIT, if it exists before the
start of the run, be deleted.
Main Index
ASSIGN 57
Assigns Physical File
Describer Meaning
DELZERO Requests that the file associated with logical-key/UNIT be deleted at the end
of the run if it is zero-length; that is, if it does not contain any data.
STATUS Specifies whether the FORTRAN file is being created (STATUS=NEW) or has
been created prior to the run (STATUS=OLD). If its status is not known, then
STATUS=UNKNOWN is specified.
FORM Indicates whether the FORTRAN file is written in ASCII
(FORM=FORMATTED) or binary (FORM=UNFORMATTED,
UNFORMATTED_64, UNFORMATTED_32, UNFORMATTED_MIX)
format. See Remark 10., 11., 12., 13. 18. and 21.
DEFER Defers opening/creating the specified file. That is, the file will not be
opened/created during MSC Nastran initialization. The file must be explicitly
opened by the module or DMAP accessing the file using, for example,
FORTIO, before it can be used.
sys-spec System-specific, machine-dependent or application-specific controls. For
DBset files, these control I/O performance. For FORTRAN files, only the
PLOT and DBC Logical-Key Names use this field. For the DBC Logical-Key,
these controls are for I/O performance just as for DBset files. For the PLOT
Logical-Key, these controls are used for PostScript processing when
FORM=FORMATTED is in effect and are ignored otherwise. See Remark 14.
RECL = l The size of a block of input/output information specified in words. See Remark
15.
SIZE = s The number of blocks allocated to the DBC database. See Remark 16.
IMPORT Imports external ifpdb. When this is absent, IFPDB is for export.
Remarks:
1. The ASSIGN statement and its applications are discussed further in the Database Concepts in the MSC
Nastran Reference Guide.
2. The log-name or logical-key describer must be the first describer on the ASSIGN statement. All other
describers may appear in any order. With the exception of log-name, logical-key, filename1,
filename2, and sys-spec, describers and values longer than four characters may be abbreviated to four
characters.
3. For FORTRAN files, the logical-key names and their default attributes are listed in Table 3-1. If a
logical-key name is identified as “Assignable YES”, then the defaults may be overridden on the
ASSIGN statement.
4. Certain reserved names may not be used for log-names or logical-key names. These names are the
logical names listed in Table 3-1 that are identified as “Assignable NO”. This list includes: SEMTRN,
LNKSWH, MESHFL, LOGFL, INPUT, PRINT, INCLD1, and CNTFL. If they are used, then a
User Fatal Message is issued. Unit numbers 1 through 10, 14, 16, 18, 19 and 21 should not be
assigned. Up to 4000 ASSIGNs are allowed. Some operating systems may have a smaller limit. To
avoid that limit use “ulmit -n 4096”. Unit numbers 1234, 1235, 1236, 1133 to 2269 are not allowed.
Main Index
58 ASSIGN
Assigns Physical File
Some operating systems may have their own limit on the number of open files as well. PUNCH and
PLOT may be used, but are not recommended. Most keyword assignments can be specified as
command line arguments and/or included in RC files. There are some exceptions such as solve=auto
may be specified on the command line or the User RC files, but not in the system RC files
(MSC_BASE/conf/RCfile).
5. If one of the logical-key names indicated in the Remarks 3. and 4. is not specified on this statement,
then it is assumed to be a DBset member name log-name as shown in Format 1.
6. If the same log-name is used on more than one DBset ASSIGN statement, the following rules apply:
a. If there is no current entry for the specified log-name, a new entry in the DBset tables will be
created. If there is an existing entry for the specified log-name, the ASSIGN parameters will
modify that entry instead of creating a new one.
b. If filename1 is omitted or is specified as * or ‘*’, the default file name or, if this is a second or
subsequent ASSIGN statement for the same log-name, the previously specified file name (or
default name if none was previously specified) will be used.
7. If the same logical-key is used on more than one FORTRAN file ASSIGN statement, the following
rules apply:
a. If filename2 is omitted (or specified as * or ‘*’) and if the UNIT describer is omitted, the ASSIGN
parameters will modify the system default entry for the logical-key, establishing the new defaults
for any subsequent ASSIGN entry for the logical-key. Note, however, that any entries previously
created with the same logical-key will not be modified by the new parameters specified on this
ASSIGN statement.
b. If the value specified by the UNIT describer matches the value for an entry created by a previous
ASSIGN statement with a UNIT describer, then:
• If the logical-key values are different, a UFM will be generated; and
• If the logical-key values are the same, the previous entry will be updated instead of having a new
entry created.
c. If the value specified by the UNIT describer does not match the value for an entry created by a
previous ASSIGN statement with a UNIT describer, then a new entry will be created in the
FORTRAN unit tables.
d. If the file name is omitted or specified as * or ‘*’, the default file name or, if this is a second or
subsequent ASSIGN statement for the same logical-key/UNIT combination, a previously
specified file name (or default name if none was previously specified) will be used.
8. If you are using IFPSTAR (default), you can use below command to import IFPDAT file created by
the initial run if the file is not located in the same directory as MASTER and DBALL files. ASSIGN
IFPDB=first_run_directory/run1.IFPDAT IMPORT.
9. STATUS, UNIT, and FORM are ignored if assigning a log-name (DBset member name).
10. FORM=FORMATTED must be specified for a unit when:
• ASCII output is desired from the OUTPUT4 DMAP modules that processes the unit. See the
MSC Nastran DMAP Programmer’s Guide.
Main Index
ASSIGN 59
Assigns Physical File
• FORMAT=NEUTRAL is selected on the DBUNLOAD and DBLOAD FMS statements that
process the unit. See the Database Concepts in the MSC Nastran Reference Guide.
• The neutral file format is desired for the OUTPUT2 module.
• PostScript output is desired for PLOT requests when “PLOTTER NAST” is in effect.
11. For the DBUNLOAD FMS statement and the OUTPUT2 and OUTPUT4 modules, binary format
may be requested using FORM=UNFORMATTED, FORM=UNFORMATTED_64,
FORM=UNFORMATTED_32 and FORM=UNFORMATTED_MIX. The output formats with
these keywords are as the following:
FORM Table (bit) Matrix (bit) Old keyword
UNFORMATTED 64 64 UNFORMATTED
UNFORMATTED_64 64 64 LITTLEENDIAN64
UNFORMATTED_32 32 32 N/A
UNFORMATTED_MIX 32 64 LITTLEENDIAN
12. The FORM= describer is ignored for the DBLOAD FMS statement and INPUTT2 and INPUTT4
modules. MSC Nastran determines the actual file format when it accesses the specified file. If the
FORM= describer is specified on an ASSIGN statement for these logical-keys, the syntax of the
describer will be validated but will otherwise be ignored. However,
• For non-native binary files the INPUTT2 modules can only process data blocks with an NDDL
description. (See the MSC Nastran DMAP Programmer’s Guide under the DATABLK statement.) An
NDDL description is required for TYPE=TABLE and none is required for TYPE=MATRIX. The
data block must be processed with FORM=UNFORMATTED if TYPE=UNSTRUCTURED,
KDICT, or KELM.
• Although formatted files are machine independent, if the file in unformatted DBLOAD can only
process input files in native binary format.
13. For the DBUNLOAD FMS statement and OUTPUT2 module, if FORM is other than
UNFORMATTED (or equivalent, e.g., UNFORMATTED_32 on a Linux or Windows platform),
then only data blocks with an NDDL description are processed. (See the MSC Nastran DMAP
Programmer’s Guide under the DATABLK statement.) An NDDL description is required for
TYPE=TABLE and none is required for TYPE=MATRIX. The data block must be processed with
FORM=UNFORMATTED if TYPE=UNSTRUCTURED, KDICT, or KELM.
14. See the for further information on sys-spec controls and on machine-dependent aspects of the
ASSIGN statement. Also, if there are SYS specifications on more than one ASSIGN statement
specifying the same log-name or logical-key/UNIT combination, the second and subsequent
specifications will appended to the current SYS specification with a comma separator.
15. Currently the RECL keyword is used by the DBC module and has a default minimum of 1024 words.
The maximum allowed is 65536 words and is used to increase the database capacity.
Main Index
60 ASSIGN
Assigns Physical File
16. The SIZE keyword is used by the DBC module and has a default of 16777215. The maximum
allowed is 2147483647 and is used to increase the database capacity. Patran releases before 2001
should use the defaults for RECL and SIZE or database verification failures will occur.
17. logical-key name MNF does not utilize UNIT or FORM.
18. For logical-key DBC, if the .xdb file is new, the desired binary format may be specified in the same
way as for the OUTPUT2 and OUTPUT4 modules, as described in Remark 11., except that
FORM=FORMATTED is not valid. If the .xdb file is not new, the FORM= describer is ignored and
MSC Nastran determines the format of the existing .xdb file. MSC Nastran can read and or update
an .xdb file in any valid format. Note, on long-word systems (mode=i8) the effect of 64-bit output
files is that ADAMS(MNF), Patran, and SimXpert may fail to process the results.
19. SOL700 reserves unit numbers 87-92 for its internal use. When using SOL700 users should not use
these unit number to avoid conflicts.
20. The total length of any line in an ASSIGN statement must not exceed 72 characters. Long file names
may be split across multiple lines with commas at the end of line and next to be without spaces. For
example, the file: ASSIGN SCR300='E:\hrishikesh_scr300\testing\delimiter\issue\scratch.SCR300' DELETE
should be specified with the following input: ASSIGN SCR300='E:\hrishikesh_scr300\testing\,
delimiter\issue\scratch.SCR300' DELETE.
Table 3-1 FORTRAN Files and Their Default Attributes
Logical Physical Unit Description/
Key Name Name No. Form Status Assignable Open Access Application
SEMTRN sdir/data.f01 1 FORMATTED NEW NO YES SEQ. Input Data Copy Unit
LNKSWH sdir/data.f02 2 UNFORMATTED NEW NO YES SEQ. Link Switch Unit
MESHFL sdir/data.f03 3 FORMATTED NEW NO YES SEQ. Input Data Copy Unit
LOGFl out.f04 4 FORMATTED NEW NO YES SEQ. Execution Summary
Unit
INPUT data.dat 5 FORMATTED OLD NO YES SEQ. Input File Unit
PRINT out.f06 6 FORMATTED NEW NO YES SEQ. Main Print Output
Unit
PUNCH out.pch 7 FORMATTED NEW YES YES SEQ. Default Punch Output
Uniit
authorize.dat 8 FORMATTED OLD NO YES SEQ. Authorization File
INCLD1 NO Available for Use
CNTFL NO Available for Use
INPUTT2 REQ REQ OLD YES NO SEQ. INPUTT2 Unit
OUTPUT2+ out.op2 12 UNFORMATTED* NEW YES YES SEQ. OUTPUT2 Unit
INPUTT4 REQ REQ OLD YES NO SEQ. INPUTT4 Unit
OUTPUT4 REQ REQ UNFORMATTED* NEW YES NO SEQ. OUTPUT4 Unit
PLOT out.plt 14 UNFORMATTED++ NEW YES YES SEQ. Plotter Output Unit
BULKECHO out.becho 18 FORMATTED NEW YES YES SEQ. Bulk EchoUnit
OUTPUT2F out 19 UNFORMATTED NEW YES SEQ. Named OUTPUT2
Pattern
OPCASE REQ 22 FORMATED NEW YES SEQ. Available for Use
TOPDES out.des 21 FORMATTED NEW YES YES SEQ. Topology Optimization
Main Index
ASSIGN 61
Assigns Physical File
Table 3-1 FORTRAN Files and Their Default Attributes (continued)
Logical Physical Unit Description/
Key Name Name No. Form Status Assignable Open Access Application
AESO out.AESO 23 FORMATTED NEW YES YES SEQ. Optimization
DBC out.xdb 40 UNFORMATTED NEW YES YES DIRECT Database Converter
Unit
DBUNLOA REQ 50 UNFORMATTED* NEW YES NO SEQ. DBUNLOAD FMS
D statement
DBLOAD REQ 51 OLD YES NO SEQ. DBLOAD FMS
statement
MNF out.mnf none none NEW YES NO SEQ. Interface for
ADAMS/Flex
A502LU Available for Use
DBMIG Available for Use
USERFILE REQ REQ REQ REQ YES NO SEQ. Any User-Defined File
UNVFILE REQ REQ FORMATTED OLD YES NO SEQ. Universal File (UF)
Unit
ADFFILE out.afu none none NEW YES NO SEQ. Associated Data File
Unit
IFPDB out.IFPDB no no NEW YES NO SEQ Export or import
IFPDAT file
ACG out.acg no no NEW YES NO SEQ Automatic Contact
Generation file
HDF5 out.h5 no no NEW YES NO N/A Nastran HDF5 result
database
HDF5IN pre_run.h5 REQ no OLD YES NO SEQ Read displacement or
eigenvector datasets
from MSC Nastran
hdf5 result database
IMPFIN example.impf REQ no OLD YES NO N/A Read imperfection file
out.singularities.bdf various FORMATTED NEW NO YES SEQ SET1 for massless
mechanisms
where:
Logical Key Name Specifies the logical-key NAME used on the ASSIGN statement.
Physical Name Specifies the default name used to open the file; i.e., the default
filename2 name.
“REQ” means that this parameter is required in the ASSIGN statement
from the user.
Unit No. Specifies the default FORTRAN unit number used by MSC Nastran.
“REQ” means that this parameter is required in the ASSIGN statement
from the user.
Form Specifies the default FORM used when the file is opened.
Status Specifies the default STATUS used when the file is opened.
“REQ” means that this parameter is required in the ASSIGN statement
from the user.
Main Index
62 ASSIGN
Assigns Physical File
Assignable If “YES”, the user may assign a physical file to this logical name.
If “NO”, the unit (if any) and logical name are reserved by MSC
Nastran.
Open If “YES”, the file is opened by default.
If “NO”, the file must be explicitly opened.
Access If “SEQ”, the file is opened for sequential access.
If “DIRECT”, the file is opened for direct access.
sdir The scratch directory specified using the “sdirectory” keyword.
data The name of the input data file with all directory and extensions
removed.
out The directory and file prefix specified using the “out” keyword or taken
by default.
Notes: + The actual logical-key name for this is “.op2”. If you use “OUTPUT2” (even though
this is still the logical-key name put out by Patran) you will get a User Fatal Message
from MSC Nastran.
* FORMATTED is required for neutral-format OUTPUT2 files and ASCII-format
OUTPUT4 files.
++ If FORM=FORMATTED is specified, the default extension is changed to “.ps” and,
if PLOTTER NAST is requested (PLOTTER SC is not supported in PostScript
mode), the plot data will be generated in PostScript format directly instead of having
to use the PLOTPS or MSCPLOTPS utility programs. Any desired plotting options
may be specified as keywords in the SYS= field of the ASSIGN statement or using the
SYSFIELD command-line option, specifying PLOT(keyword=value,...).
The valid keywords are the same as those that can be specified for the PLOTPS or
MSCPLOTPS utility programs except that the “begin”, “debug”, “dump”, “end”,
“format” and “output” keywords are not allowed. PostScript mode can be made the
default by specifying the following ASSIGN statement in an RC file:
ASSIGN PLOT=*,FORM=FORMATTED
This ASSIGN statement may also include a SYS= specification if any special
PostScript keywords are to be used for every plot.
21. Refer to Remarks 10., 11., 12., 13. and 18. above. For UNFORMATTED, the default is 64-bit
machine precision. The Linux and Windows platforms, currently supported by MSC Nastran, are
binary compatible. FORMATTED involves converting the binary numbers into a compressed ASCII
representation, which will result in some roundoff. In a numerically stable problem, the roundoff
should not cause problems. However, if the model is not numerically stable or the user is performing
operations which require numeric precision, then the roundoff may come into play. See, also, IEEE
754-2008, published in August 2008 for roundoff criterion.
Main Index
CONNECT 63
User Defined Service and Group Evaluator Data
CONNECT User Defined Service and Group Evaluator Data
Defines the newly introduced Simulation Component Architecture (SCA) User Defined Service (UDS) into
MSC Nastran via a new CONNECT SERVICE statement. Bulk Data entries such as NLRSFD and
MATUDS refer to this new service.
External geometric or beam cross section entities, external design responses, and external splines are still
defined through the old grouping also described below. These entities should belong to the same
evaluator-class (set of routines that process them), and in the case of geometric data, should reside on the same
database.
1. A group of external beam cross section entities. These entities should belong to the same evaluator-
class (a set of routines that process them). The PBARL and PBEAML entries relate to the
BEAMEVAL type.
2. A group of external spline entities. The SPLINEX Bulk Data entry relates to the SPLINEX type.
3. A group of external design response entities. The DRESP3 Bulk Data entry relates to the DRESP3
type.
UDS Format:
CONNECT SERVICE <service_identifier> <service_name>
Old Group Format:
GEOMEVAL
BEAMEVAL
CONNECT group evaluator ’path’ ’data’
DRESP3
SPLINEX
UDS Examples:
CONNECT SERVICE mysub ' SCA.MDSolver.Util.Ums '
Creates a service identifier “mysub” which points to the “SCA.MDSolver.Util.Ums” service.
CONNECT SERVICE MYSUB ' ExtServ.Nlrsfd '
In this case, the user is requesting the NLRSFD Bulk Data entry with the GRPNAME MYSUB
obtain its characteristics from the externally connected service defined in the CDL file under the
component keyword. The user must create an external shared object library (dynamic link library on
Windows) using the SCA Scons utility and configure it to function with the MSC Nastran executable.
Old Group Examples:
CONNECT BEAMEVAL HOIST, NEWBEAMS
Main Index
64 CONNECT
User Defined Service and Group Evaluator Data
In this case, the user is requesting that all calculations on PBARL and PBEAML Bulk Data entries
that are grouped as HOIST use the NEWBEAMS evaluator. In this case, the user must supply the
NEWBEAMS beam cross section evaluator library, and configure it to function with the Nastran
executable program.
CONNECT DRESP3 TAILWING, EXTRESP
In this case, the user is requesting that all calculations on DRESP3 Bulk Data entries, that are grouped
as TAILWING use the EXTRESP evaluator. Thus, the user must create the EXTRESP external
response server program, and configure it to function with the MSC Nastran executable.
CONNECT SPLINEX SPLNGRP EXTSPLN
In this case, the user is requesting that all calculations on SPLINEX Bulk Data entries, that are
grouped as SPLNGRP, use the EXTPLN evaluator. Thus, the user must create the EXTSPLN
external spline server program and configure it to function with the Nastran executable.
Describer Meaning
(UDS Format)
group Group name referenced by the GROUP field on the NLRSFD and MATUDS
Bulk Data entries.
service_identifier service_identifier is a name tag (8 characters long) which will be used to identify
the service implementation to be used for a specific bulk data entry.
service_name service_name is the name of service
Describer Meaning
(Old Group Format)
group Group name referenced by the GROUP field on DRESP3, PBARL, PBEAML,
and SPLINEX Bulk Data entries.
evaluator Identifies the particular class of evaluator to which the geometric, beam cross
section, external response, or external spline entities belong. Entities belonging
to one evaluator-class are handled by the same set of routines (either MSC-
provided or user-provided). For geometry, two classes of evaluators are
provided internally with MSC Nastran. They are MSCRPC (rational
parametric cubic) and MSCEQN (generic equation). For beam cross sections,
the class MSCBML (MSC Beam Library) is provided internally. Users may
develop custom evaluator libraries for geometry, beam cross sections, external
responses, or external splines and configure them for use with MSC Nastran.
See Remarks 4., 5., and 7.
path Optional pathname or filename used by evaluator. Path must be enclosed by
single quotation marks if it contains lowercase characters.
data Optional character string passed to the evaluator. Data must be enclosed by
single quotation marks if it contains lowercase characters or embedded blanks.
Main Index
CONNECT 65
User Defined Service and Group Evaluator Data
Remarks (UDS Format):
1. The process of enabling User Defined Services in MSC Nastran consists of the following four steps:
a. Creating the desired implementation for the User Defined Services in the form of dynamic-link
libraries,
b. Defining the location of the user defined service, service catalogue, service resource directory.
c. Specifying the proper commands in the model to load the service,
d. Identifying the elements that use the user supplied implementation.
2. In order to create a dynamic-link library suitable for usage with MSC Nastran, a build environment
is delivered to assist the user in building the library. Please refer to the Simulation Component
Architecture Guide and the User Defined Service Guide which describe the features and capabilities of
the build system.
Remarks (Old Group Format):
1. CONNECT requests:
• An external data base or evaluator, or
• A user-defined grouping for beam cross section data defined by PBARL and PBEAML entries.
2. Two reserved group names, MSCGRP0 and MSCGRP1, have been predefined for geometric entities.
The group MSCGRP0 corresponds to the MSCRPC (rational parametric cubic) evaluator and the
group MSCGRP1 corresponds to the MSCEQN (Generic Equation) evaluator.
3. A single reserved group name, MSCBML0, has been predefined for beam cross section entities. It may
be used in the PBARL and PBEAML entries without being defined explicitly by means of a
CONNECT FMS statement. It corresponds to the MSCBML (MSC Beam-Library) evaluator.
4. Custom geometric evaluator libraries developed by users should comply with the MSC Nastran
Geometry Evaluator Developer’s Guide.
5. Custom beam cross section evaluator libraries developed by users should comply with the guidelines
in the MSC Nastran V69 Release Guide, Section 3.1, Beam Cross-Section Library, and Appendix C:
Adding Your Own Beam Cross-Section Library.
6. Custom responses developed by users should comply with the procedures and guidelines in “Support
of External Response in SOL 200” on page 55 of the MSC Nastran 2004 Release Guide.
7. Once developed, an evaluator may be configured as:
• Internal, where the evaluator routines are linked with the rest of the Nastran object modules to
comprise the Nastran executable program; or
• External, where the evaluator routines are linked with an MSC-provided server program to
constitute an independent geometry server.
Main Index
66 DBCLEAN
Deletes Database Versions and/or Projects
DBCLEAN Deletes Database Versions and/or Projects
Deletes one or more versions and/or projects from the database.
Format:
DBCLEAN VERSlON = {version-ID,*} [PROJECT={’project-lD’,*}]
Describer Meaning
version-ID Version identifier of the database to be deleted.
* Wildcard. All versions or projects to be deleted.
project-ID Project identifier of the project to be deleted. (See the FMS statement, PROJ,
105.)
Remarks:
1. There may be up to ten DBCLEAN statements in the FMS Section.
2. If no project-ID is given, the current project-ID is assumed.
Example:
DBCLEAN VERS = 7 PROJ = ’OUTER WING - LEFT’
The preceding example would delete from the database all data blocks and parameters stored under Version
7 of the project identified as OUTER WING - LEFT.
Main Index
DBDICT 67
Prints Database Directory Tables
DBDICT Prints Database Directory Tables
DBDICT prints the following database directory tables:
Data blocks described by an NDDL DATABLK statement.
Parameters described by an NDDL PARAM statement.
All unique paths (KEYs) and their qualifier values.
Qualifiers and their current values.
Data blocks not described by an NDDL DATABLK statement.
Parameters not described by an NDDL PARAM statement.
Project and version information.
Basic Format:
The basic format of DBDICT specifies which tables to print and prints all items (data blocks and parameters)
found in the directory. Also, the attributes (colnames) to be printed, and the print format, are predefined.
Note that more than one table may be specified on the same DBDICT statement.
DBDICT DATABLK PARAM PROJVERS QUALCURR QUALIFIERS
Examples:
DBDICT
DBDICT PARAM PROJVERS
Full Format:
The full format permits the selection of items by name and/or by the WHERE describer. The full format also
permits the attributes to be printed using the SELECT describer. In addition, the print format can be
specified with the SORT, FORMAT, and LABEL describers. Note that the full format only allows the
specification of a single table on a DBDICT statement.
DATABLK *
=
DATABLK LOCAL datablk-list
PARAM *
DBDICT = WHERE(where-expr),
PARAM LOCAL param-list
PROJVERS
QUALCURR
QUALIFIERS
SELECT(colname[- ‘ col-label’]. . . ),
Main Index
68 DBDICT
Prints Database Directory Tables
FORMAT (FWIDTH = w [.d] DWIDTH = w [.d] AWIDTH = a IWIDTH = i,
LWIDTH = k COLSPACE = c VALUE = w,
colname = col-width, . . .),
SORT colname = A ,
D
RIGHT
LABEL page - title‘ CENTER
LEFT
Describer Meaning
DATABLK Print the data blocks. datablk-list specifies a list of NDDL-defined data blocks
separated by commas. If LOCAL is specified, the non-NDDL-defined data
blocks are printed.
PARAM Print the parameter table. param-list specifies a list of parameters separated by
commas. If LOCAL is specified, the non-NDDL-defined parameters are
printed.
PROJVERS Print the project-version table.
QUALIFIERS Print the qualifier table.
QUALCURR Print the current values of the qualifiers. SORT is ignored.
where-expr Logical expression that specifies the desired values of colnames described below.
For example, WHERE(VERSION=4 AND SEID < >2 AND SEID>0) selects
all items under version 4 for all values of SEID greater than 0 except 2. See the
beginning of this section for a further description. The default for VERSION is
the last version, and PROJECT is the current project. The default for qual
is*,which is all qualifier values found on the database. See also Remark 12.
SELECT Specifies a list of column names to be printed. The order of the specified
colnames will be printed from left to right. If colname is not specified, then all
columns will be printed.
colname Column name. Colname specifies a particular attribute of the database item such
as data block name (NAME), creation date (CDATE), number of blocks
(SIZE), or qualifier name (SEID, SPC, etc.). The allowable colnames are given
in the Remarks.
col-label The label to printed above the column identified by colname. The default for
col-label is the colname. col-label may not be specified for the following
colnames: QUALSET, QUALALL, and TRAILER.
Main Index
DBDICT 69
Prints Database Directory Tables
Describer Meaning
FWIDTH=w.d Specifies the default width for single-precision real numbers in real and complex
qualifiers (Integers: w>0 and d>0; Default=12.5).
DWIDTH=w.d Specifies the default width for double-precision real numbers in real and
complex qualifiers (Integers: w>0 and d>0; Default=17.10).
AWIDTH=a Specifies the default width for character string qualifiers. Character strings are
printed with enclosing single quotation marks, even if the string is blank
(Integer>0; Default=8).
IWIDTH=i Specifies the default width for integer qualifiers (Integer> 0; see Remarks for
defaults).
LWIDTH=k Specifies the default width for logical qualifiers. Logical values are printed as
either “T” for TRUE or “F” for FALSE (Integer> 0; Default=1).
COLSPACE=c Specifies the default number of spaces between columns (Integer> 0; see
Remarks for defaults).
VALUE=w Specifies the default width for parameter values. The values are printed as
character strings with left justification (Integer>0; Default=40)
col-width The print width of the data under colname or qual-name. For real numbers,
specify w.d where w is the width of the field and d is the number of digits in the
mantissa. For integers and character strings, specify w, where w is the width of
the field. col-width may not be specified for colnames QUALSET, QUALALL,
and TRAILER.
SORT Specifies how the rows are sorted. The sort is performed in order according to
each colname specified in the list. A “D” following the colname causes the sort
to be in descending order. An “A” following the colname causes the sort to be in
ascending order. Colnames QUALSET, QUALALL, and TRAILER may not be
specified under SORT. Each colname specified in SORT must be separated by
commas.
page-title A title to be printed on each page of the directory output.
RIGHT, Print justification of the page title.
CENTER, LEFT
Main Index
70 DBDICT
Prints Database Directory Tables
Remarks:
1. DBDICT prints seven different tables according to a default or a user-defined format. The tables are:
Table 1 DBDICT Tables
See
Describer Description Default Page-Title Remark
DATABLK Data blocks described by a NDDL DATABLOCKS 2.
NDDL DATABLK statement.
PARAM Parameters described by a NDDL PARAMETERS 3.
NDDL PARAM statement.
QUALCURR Current qualifiers and their CURRENT 4.
values. QUALIFIERS
QUALIFIERS Qualifiers and their values for QUALIFIERS 5.
each key number.
DATABLK(LOCAL) Data blocks not described by a LOCAL DATABLOCKS 6.
NDDL DATABLK statement.
PARAM(LOCAL) Parameters not described by a LOCAL PARAMETERS 7.
NDDL PARAM statement.
PROJVERS Project-Version. PROJECT-VERSION 8.
If DBDICT is specified without any describers, then the NDDL Data blocks Table will be printed.
See Remark 2.
DATABLK(LOCAL) and PARAM(LOCAL) produce no output, and QUALCURR produces the
default values specified on the NDDL QUAL statement.
The defaults and allowable colnames for SELECT, FORMAT, SORT, and LABEL depend on the
table. The defaults are described in the following remarks and tables.
2. The default print of the NDDL Data Blocks Table is obtained by
DBDICT
or
DBDICT DATABLK
and is equivalent to
DBDICT DATABLK ,
SELECT(NAME,DATABASE,DBSET,PROJ,VERS,CDATE,CTIME,
SIZE,KEY,PURGED=’PU’,EQUIVD=’EQ’,
POINTER=’FILE’,QUALSET) ,
FORMAT(NAME=8,DBSET=8,CDATE=6,CTIME=6,SIZE=5,
KEY=4 ,PURGED=4,EQUIVD=4,POINTER=8,
IWIDTH=5,COLSPACE=1) ,
SORT(PROJ=A,VERS=A,DBSET=A,NAME=A) ,
LABEL(’NDDL DATABLOCKS’ CENTER)
Main Index
DBDICT 71
Prints Database Directory Tables
and looks like:
* * * * D I C T I O N A R Y P R I N T * * * *
EXECUTION OF DMAP STATEMENT NUMBER 20
MODULE NAME = DBDICT , SUBDMAP SEKRRS , OSCAR RECORD NUMBER 16
NDDL DATABLOCKS
NAME DATABASE DBSET PROJ VERS CDATE CTIME SIZE KEY PU EQ FILE SEID PEID LOAD SPC MPC METH
----------------------------------------------------------------------------------------------------------------
------------------------------------------------------------
AGG MASTER DBALL 1 1 930805 72340 0 326 1 0 132484 0 0
AXIC MASTER DBALL 1 1 930805 72336 0 315 1 0 65764
BGPDTS MASTER DBALL 1 1 930805 72338 1 324 0 2 131332 0
BGPDTX MASTER DBALL 1 1 930805 72338 1 324 0 1 131332 0
BJJ MASTER DBALL 1 1 930805 72341 0 332 1 0 132612 0
BULK MASTER DBALL 1 1 930805 72336 2 315 0 0 65700
CASECC MASTER DBALL 1 1 930805 72336 1 316 0 2 67428
Figure 3-1 DBDICT DATABLK Example
Table 2 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.
Table 2 DBDICT DATABLK Colnames
Default Default
colname col-width col-label Description
PROJECT 40 PROJECT NAME Project name defined by
PROJECT statement.
PROJ 4 PROJ NO Project number associated
with PROJECT.
VERS 4 VERSION Version number.
CDATE 6 CDATE Creation date.
CTIME 6 CTIME Creation time.
NAME 8 NAME Parameter name.
DATABASE 8 DATABASE MASTER DBset name.
DBSET 8 DBSET DBset name.
RDATE 6 RDATE Revision date.
RTIME 6 RTIME Revision time.
SIZE 5 SIZE Number of blocks.
qual-name See Note. qualifier name Qualifier name.
KEY 4 KEY Key number.
TRLi 8 TRLi i-th word in the trailer.
TRAILER 8 TRLi All 10 trailer words.
EXTNAME 8 EXTNAME Extended name.
EQUIVD 4 EQ Equivalenced flag.
Main Index
72 DBDICT
Prints Database Directory Tables
Table 2 DBDICT DATABLK Colnames (continued)
Default Default
colname col-width col-label Description
PURGED 4 PU Purged flag.
EQFLAG 4 EF Scratch equivalenced flag.
SCRFLAG 4 SF Scratch DBSET flag.
POINTER 8 POINTER Directory pointer.
DBENTRY 8 DBENTRY Database entry pointer.
FEQCHAIN 8 FEQCHAIN Forward equivalence chain.
BEQCHAIN 8 BEQCHAIN Backward equivalence chain.
DBDIR20 9 DBDIR(20) Directory word 20.
QUALALL See Note. qualifier name All qualifiers.
QUALSET See Note. qualifier name Predefined subset of all
qualifiers.
Note: Default widths for qualifiers are DWIDTH=17.10, IWIDTH=5, LWIDTH=1,
AWIDTH=8, and FWIDTH=12.5.
3. The default print of the NDDL Parameter Table is obtained by
DBDICT PARAM
and is equivalent to
DBDICT PARAM,
SELECT(NAME,DATABASE,DBSET,PROJ,VERS,CDATE,CTIME,
KEY,VALUE,QUALSET),
FORMAT(NAME=8,DATABASE=8,DBSET=8,CDATE=6,CTIME=6,
KEY=4,VALUE=40,IWIDTH=5,COLSPACE=1),
SORT(PROJ=A,VERS=A,DBSET=A,NAME=A),
LABEL(’NDDL PARAMETERS’ CENTER)
Main Index
DBDICT 73
Prints Database Directory Tables
and looks like:
* * * * D I C T I O N A R Y P R I N T * * * *
EXECUTION OF DMAP STATEMENT NUMBER 21
MODULE NAME = DBDICT , SUBDMAP SEKRRS , OSCAR RECORD NUMBER 17
NDDL PARAMETERS
NAME DATABASE DBSET PROJ VERS CDATE CTIME KEY VALUE SEID PEID LOAD SPC MPC METH
------------------------------------------------------------------------------------------------
ACOUSTIC MASTER MASTER 1 1 930805 72338 323 0 0 0
ALTRED MASTER MASTER 1 1 930805 72338 319 NO
BCHNG MASTER MASTER 1 1 930805 72337 325 FALSE 0
DBALLX MASTER MASTER 1 1 930805 72336 318 DBALL -1 -1
EPSBIG MASTER MASTER 1 1 930805 72339 323 1.000000E+12 0 0
ERROR MASTER MASTER 1 1 930805 72338 319 -1
FIXEDB MASTER MASTER 1 1 930805 72338 323 0 0 0
Figure 3-2 DBDICT PARAM Example
Table 3 gives the allowable colnames along with a description that may be specified in the FORMAT,
SELECT, and SORT describers.
Table 3 DBDICT PARAM Colnames
Default Default
colname col-width col-label Description
PROJECT 40 PROJECT NAME Project name defined by
PROJECT statement.
PROJ 5 PROJ Project number associated with
PROJECT.
VERS 4 VERS Version number.
CDATE 6 CDATE Creation date.
CTIME 6 CTIME Creation time.
NAME 8 NAME Parameter name.
DATABASE 8 DATABASE MASTER DBset name.
DBSET 8 DBSET DBset name.
RDATE 6 RDATE Revision date.
RTIME 6 RTIME Revision time.
POINTER 8 POINTER Directory pointer.
VALUE 40 VALUE Parameter value.
KEY 4 KEY Key number.
qual-name See Note. qualifier name Qualifier name.
QUALALL See Note. qualifier name All qualifiers.
QUALSET See Note. qualifier name Predefined subset of all qualifiers.
Main Index
74 DBDICT
Prints Database Directory Tables
Note: Default widths for qualifiers are DWIDTH=17.10, AWIDTH=8, IWIDTH=5,
LWIDTH=1, and FWIDTH=12.5.
4. The default print of the qualifier table is obtained by
DBDICT QUALIFIERS
and is equivalent to
DBDICT QUALIFIERS ,
SELECT(KEY QUALALL) ,
FORMAT(DWIDTH=17.10 AWIDTH=8 IWIDTH=5 LWIDTH=1 ,
FWIDTH=12.5 COLSPACE=2) SORT(KEY=A) ,
LABEL(’QUALIFIERS’ CENTER )
and looks like:
* * * * D I C T I O N A R Y P R I N T * * * *
EXECUTION OF DMAP STATEMENT NUMBER 22
MODULE NAME = DBDICT , SUBDMAP SEKRRS , OSCAR RECORD NUMBER 18
QUALIFIERS
KEY APRCH B2GG B2PP BMETH CMETH CONFIG DEFORM DELTA DESITER DLOAD DRMM DYRD EXTRCV FMETH FREQ
FSCOUP GUST HIGHQUAL HINDEX IC IKBAR IMACHNO IPANEL IQ ISA ISOLAPP K2GG K2PP LOAD
M2GG M2PP MACHINE METH METHF MFLUID MODEL MPC MTEMP NCASE NL99 NLOAD NLOOP NOQUAL OPERALEV
OPERASYS P2G PEID PVALID SDAMP SEDWN SEID SOLAPP SOLID SPC STATSUB SUBDMAP SUBMODEL SUPORT
TEMPLD TFL TSTEP ZNAME ZUZR1 ZUZR2 ZUZR3
-------------------------------------------------------------------------------------------------------------
335 ’ ’ F 0
0 ’ ’
’ ’ 0
’ ’ 0 0 0
-------------------------------------------------------------------------------------------------------------
336 ’ ’ 0
0 ’ ’
0 0 -1
0 0 0
Figure 3-3 DBDICT QUALIFIERS Example
QUALALL selects all qualifiers to be printed. The qualifiers will be printed in alphabetic order.
QUALSET selects only the qualifiers SEID, PEID, SPC, MPC, LOAD, and METH to be printed.
Table 4 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers. QUALALL and QUALSET may not be specified in the FORMAT
or SORT describers. The qualifier names and values are not printed one per row, but rather from left
to right as one logical line that is allowed to wrap after 132 columns.
Main Index
DBDICT 75
Prints Database Directory Tables
Table 4 DBDICT QUALIFIERS Colnames
Default Default
colname col-width col-label Description
KEY 5 KEY Key number.
qual-name See Note. qualifier name Qualifier name.
QUALALL See Note. qualifier name All qualifiers.
QUALSET See Note. qualifier name Predefined subset of all
qualifiers.
Note: Default widths for qualifiers are DWIDTH=17.10, IWIDTH=5, LWIDTH=1, and
FWIDTH=12.5. AWIDTH defaults to the length specified on the QUAL statement in
the NDDL sequence.
5. The default print of the current qualifier table is obtained by
DBDICT QUALCURR
and is equivalent to
DBDICT QUALCURR SELECT(QUALALL),
FORMAT(AWIDTH=8,IWIDTH=5,LWIDTH=1,COLSPACE=2),
LABEL=(’CURRENT QUALIFIERS’ CENTER)
and looks like:
* * * * D I C T I O N A R Y P R I N T * * * *
EXECUTION OF DMAP STATEMENT NUMBER 24
MODULE NAME = DBDICT , SUBDMAP SEKRRS , OSCAR RECORD NUMBER 20
CURRENT QUALIFIERS
APRCH B2GG B2PP BMETH CMETH CONFIG DEFORM DELTA DESITER DLOAD DRMM DYRD EXTRCV FMETH FREQ FSCOUP
GUST HIGHQUAL HINDEX IC IKBAR IMACHNO IPANEL IQ ISA ISOLAPP K2GG K2PP LOAD M2GG
M2PP MACHINE METH METHF MFLUID MODEL MPC MTEMP NCASE NL99 NLOAD NLOOP NOQUAL OPERALEV OPERASYS
P2G PEID PVALID SDAMP SEDWN SEID SOLAPP SOLID SPC STATSUB SUBDMAP SUBMODEL SUPORT
TEMPLD TFL TSTEP ZNAME ZUZR1 ZUZR2 ZUZR3
-----------------------------------------------------------------------------------------------------------
’ ’ ’ ’ ’ ’ 0 0 0 0 F 0 0 F 0 0 0 0 F
0 0 0 0 0 0 0 0 0 1 ’ ’ ’ ’ 300 ’ ’
’ ’ 0 0 0 0 0 100 0 0 0 0 -1 0 0 0
’ ’ 0 0 0 0 0 ’ ’ 0 400 0 ’ ’ 0 0
0 0 0 ’ ’ 0 0 0
----------------------------------------------------------------------------------------------------------
Figure 3-4 DBDICT QUALCURR Example
Table 5 gives the allowable colnames and a description that may be specified in the SELECT
describers.
Main Index
76 DBDICT
Prints Database Directory Tables
Table 5 DBDICT QUALCURR Colnames
Default Default
colname col-width col-label Description
qual-name See Note. qualifier name Qualifier name.
QUALALL See Note. qualifier name All qualifiers.
QUALSET See Note. qualifier name Predefined subset of all qualifiers.
Note: Default widths for qualifiers are DWIDTH=17.10, IWIDTH=5, LWIDTH=1, and
FWIDTH=12.5. AWIDTH defaults to the length specified on the QUAL statement in
the NDDL sequence.
6. The default print of the Local Data Block Table is obtained by
DBDICT DATABLK(LOCAL)
and is equivalent to
DBDICT DATABLK(LOCAL),
SELECT(NAME,SUBDMAP,SIZE=’BLOCKS’,PURGED=’PU’,
EQUIVD=’EQ’,POINTER,TRL1,TRL2,TRL3,TRL4,
TRL5,TRL6,TRL7),
FORMAT(NAME=8,SUBDMAP=8,IWIDTH=8,COLSPACE=2),
SORT(NAME=A) LABEL(’LOCAL DATABLOCKS’ CENTER)
and looks like:
* * * * D I C T I O N A R Y P R I N T * * * *
EXECUTION OF DMAP STATEMENT NUMBER 23
MODULE NAME = DBDICT , SUBDMAP SEKRRS , OSCAR RECORD NUMBER 19
LOCAL DATABLOCKS
NAME SUBDMAP BLOCKS PU EQ POINTER TRL1 TRL2 TRL3 TRL4 TRL5 TRL6 TRL7
-------------------------------------------------------------------------------------------------
CASEW PHASE1DR 1 0 0 131780 201 4 0 308 0 0 0
Figure 3-5 DBDICT DATABLK(LOCAL) Example
TRLi specifies the data block trailer word i where 1 < i < 10. TRAILER selects all 10 data block trailer
words.
Table 6 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.
Main Index
DBDICT 77
Prints Database Directory Tables
Table 6 DBDICT DATABLK(LOCAL) Colnames
Default Default
colname col-width col-label Description
NAME 8 NAME Parameter name.
SUBDMAP 8 SUBDMAP SubDMAP name.
SIZE 8 BLOCKS Number of blocks.
EQUIVD 8 EQ Equivalenced flag.
PURGED 8 PU Scratch flag.
POINTER 8 POINTER Directory pointer.
TRLi 8 TRLi i-th word in the trailer.
TRAILER 8 TRLi All 10 trailer words.
EXTNAME 8 EXTNAME Extended name.
7. The default print of the local parameter table is obtained by
DBDICT PARAM(LOCAL)
and is equivalent to
DBDICT PARAM(LOCAL) SELECT(NAME,SUBDMAP,VALUE),
FORMAT(COLSPACE=4,VALUE=40,AWIDTH=8),
SORT(NAME=A) LABEL(’ LOCAL PARAMETERS’ CENTER)
and looks like:
* * * * D I C T I O N A R Y P R I N T * * * *
EXECUTION OF DMAP STATEMENT NUMBER 24
MODULE NAME = DBDICT , SUBDMAP SEKRRS , OSCAR RECORD NUMBER 20
LOCAL PARAMETERS
NAME SUBDMAP VALUE
----------------------------------------------------------------
AERO SESTATIC FALSE
AERO PHASE1DR FALSE
ALTRED SESTATIC NO
ALTRED PHASE1DR NO
ALWAYS PHASE1DR -1
ALWAYS PHASE1C -1
ALWAYS SEKRRS -1
ALWAYS SESTATIC -1
APP PHASE1DR STATICS
APP PHASE1C STATICS
APP SESTATIC STATICS
APRCH SESTATIC
ASING PHASE1DR 0
ASING SEKRRS 0
ASING PHASE1C 0
ASING SESTATIC 0
Figure 3-6 DBDICT PARAM(LOCAL) Example
Table 7 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.
Main Index
78 DBDICT
Prints Database Directory Tables
Table 7 DBDICT PARAM(LOCAL) Colnames
Default Default
colname col-width col-label Description
NAME 8 NAME Parameter name.
SUBDMAP 8 SUBDMAP SubDMAP name.
VALUE 40 VALUE Parameter name.
8. The default print of Project-Version Table is obtained by
DBDICT PROJVERS
and is equivalent to
DBDICT PROJVERS ,
SELECT(PROJECT=’PROJECT NAME’,PROJ=’PROJ NO.’ ,
VERS=’VERSION’,DELFLG=’DELETED’ ,
CDATE=’CREATION DATE’ CTIME=’CREATION
TIME’) ,
FORMAT(PROJECT=40,PROJ=10,VERS=10,DELFLG=7,
COLSPACE=1 ,CDATE=13,CTIME=13) ,
LABEL(’PROJECT-VERSION’,CENTER) ,
SORT(PROJ=A,VERS=A)
and looks like:
* * * * D I C T I O N A R Y P R I N T * * * *
EXECUTION OF DMAP STATEMENT NUMBER 19
MODULE NAME = DBDICT , SUBDMAP SEKRRS , OSCAR RECORD NUMBER 15
PROJECT-VERSION
PROJECT NAME PROJ NO. VERSION DELETED CREATION DATE CREATION TIME
---------------------------------------------------------------------------------------------------
’LEFT FENDER ’ 1 1 930805 72319
Figure 3-7 DBDICT PROJVERS Example
Table 8 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.
Table 8 DBDICT PROJVERS Colnames
Default Default
colname col-width col-label Description
PROJECT 40 PROJECT NAME Project name defined by PROJECT statement.
PROJ 10 PROJ NO Project number associated with PROJECT.
Main Index
DBDICT 79
Prints Database Directory Tables
Table 8 DBDICT PROJVERS Colnames
Default Default
colname col-width col-label Description
VERS 10 VERSION Version number.
DELFLG 7 DELETED Flag indicating whether this project/version has
been deleted by the RESTART NOKEEP or
DBCLEAN statements.
CDATE 13 CREATION DATE Creation date.
CTIME 13 CREATION TIME Creation time.
CDATE is printed as YYMMDD where YY, MM, and DD are the year, month, and date,
respectively. CTIME is HHMMSS where HH, MM, and SS are the hour, minute, and second,
respectively.
9. If a parameter or qualifier value is defined to be character string, then the value will be printed with
enclosing single quotation marks. Blank strings will also be printed with single quotation marks.
10. If a given qualifier is not in the path of a given data block or parameter, then blank spaces will be
printed.
11. A line will wrap if additional columns need to be printed and not enough space is available on the
output (assumed to be 132). The first column of each additional line is to be indented by the width
of the first column printed for the entry.
12. The where-expr has the following rules:
• If the where-expr specifies a colname that is not assigned to the data block or parameter, then no
directory information will be printed for that data block or parameter. For example, given that
SPC is not a qualifier for KGG, the following DBDICT statement will produce no output:
DBDICT DATABLK=KGG WHERE(SPC=10)
• If the where-expr does not specify a colname that is assigned to the data block (or parameter), then
the qualifier is wildcarded. For example, given that SEID is a qualifier for KAA, the following
DBDICT statements are equivalent:
DBDICT DATABLK=KAA
DBDICT DATABLK=KAA WHERE(SEID = *)
13. A colname specified in the where-expr must be specified in the SELECT clause if the SELECT clause
is also specified.
Examples:
1. Print the project version table with a title.
DBDICT PROJVERS SORT(PROJ,VERSION) LABEL(’PROJECT
VERSION TABLE’ LEFT)
2. Print a directory of all data blocks qualified with PEID=10 or SEID=10. Print columns for the
NAME and DBSET, and the qualifiers SPC, MPC, and LOAD.
DBDICT DATABLK SELECT(NAME,SPC,MPC,LOAD,DBSET,SIZE,
Main Index
80 DBDICT
Prints Database Directory Tables
SEID,PEID) ,
SORT(NAME,SIZE=D) WHERE( SEID=10 OR PEID=10)
Main Index
DBDIR 81
Prints Database Directory Tables
DBDIR Prints Database Directory Tables
Obsolete. See the DBDICT statement.
Main Index
82 DBFIX
Database Directory Error Detection
DBFIX Database Directory Error Detection
Detects and optionally corrects errors in the database directory.
Format:
DBFIX LIST CORRECT
NOLIST NOCORRECT
Example:
DBFIX LIST,NOCORRECT
The preceding example requests a printout of the directory pointers and any errors, but not the corrections.
Describer Meaning
LIST Requests a debug listing of the database directory pointers.
NOLIST Suppresses a debug listing of the database directory.
CORRECT Corrects the database if any errors are found.
NOCORRECT Suppresses the correction of the database.
Remarks:
1. It is recommended that a backup copy of the database be made before this statement is used, since
corrections of the database are achieved through the deletion of data. Data blocks and parameters are
deleted from the database if they have (1) incorrect paths (different than listed in the NDDL); (2)
incorrect names (two or more names that are not equivalenced and reference the same data), or (3)
incorrect directory pointers.
2. NOLIST does not suppress the listing of any corrections made to the database.
Main Index
DBLOAD 83
Loads a Database from a FORTRAN File
DBLOAD Loads a Database from a FORTRAN File
Recovers data blocks or parameters from a database created by the DBUNLOAD statement.
Format:
* *
DBLOAD DATABLK = PARAM = WHERE where-expr ,
(datablk-list) (param-list)
CONVERT convert-expr UNIT = unit FORMAT BINARY OVRWRT
NEUTRAL NOOVRWRT
Example:
1. Load the database stored in ASClI format on FORTRAN unit 12.
DBLOAD UNIT=12 FORMAT=NEUTRAL
ASSIGN DBLOAD=’physical file name of unloaded database’
UNIT=12 FORMATTED
2. Load version 1 of KAA under project FRONT BUMPER and store it on the primary database under
version 5 and project BUMPER. Overwrite duplicates found on the primary database.
DBLOAD DATABLK=(KAA) WHERE(PROJECT=’FRONT BUMPER’
AND,SEID=10 AND VERSION=1) CONVERT(VERSION=5; ,
PROJECT=’BUMPER’) OVRWRT
ASSIGN DBLOAD=’physical file name of unloaded database’
Describer Meaning
datablk-list Specifies a list of data blocks separated by commas. The default is * which
selects all data blocks. The loaded data block may be renamed in the primary
database by specifying a slash after the old name, followed by the new name.
For example, if KLL is to be renamed to KLL1, then DATABLK=(KLL/KLL1)
is specified.
param-list Specifies a list of parameters separated by commas. The default is *, which
selects all parameters. The loaded parameter may be renamed in the primary
database by specifying a slash after the old name followed by the new name. For
example, if LUSETS is to be renamed to LUSET, then
PARAM=(LUSETS/LUSET) is specified.
Main Index
84 DBLOAD
Loads a Database from a FORTRAN File
Describer Meaning
where-expr A logical expression that specifies the desired values of qualifiers PROJECT,
VERSION, and DBSET. For example, WHERE(VERSlON=4 AND
SElD<>2 AND SEID>0) selects all items under version 4 for all values of SElD
greater than 0 except 2. See the beginning of this section for more information
on WHERE and CONVERT clauses.
The default for VERSION is * for all versions; PROJECT is * for all projects;
and DBSET is* for all DBsets. The default for qual is *, which is all qualifier
values found on the loaded database. See also Remark 8.
convert-expr Modifies the values for PROJECT, VERSION, DBSET, and qualifiers selected
by the where-expr. The format of convert-expr is:
PROJECT=project-expr; VERSION=version-expr; DBSET=DBset-name;
quali=qual-expri[;..]
For example, CONVERT (SEID=100+SElD; SPC=102). See the beginning of
this section for more information on WHERE and CONVERT clauses.
The default action for VERSION and PROJECT is to use the same version lDs
and project IDs; i.e., CONVERT(PROJECT=PROJECT;
VERSlON=VERSlON). But if either PROJECT or VERSION is specified in
the convert-expr, then both must be specified. The default action for qualifiers
and DBSET is to use the same values as long as they are defined in both
databases. If not, see Remark 8.
unit Specifies the FORTRAN unit number of the database to be loaded. The unit
must be specified on an ASSIGN statement that references the physical
filename of the loaded database. The default is 51.
OVRWRT By default, if duplicate data blocks or parameters exist on the loaded and
NOOVRWRT primary databases, then a fatal message is issued. A duplicate means that a data
block or parameter has not only the same name but also the same qualifier
values, PROJECT, VERSION, and DBSET as a data block or parameter on
the primary database.
NEUTRAL The database to be loaded may be in BINARY or NEUTRAL format. BlNARY
BINARY indicates the database to be loaded is in binary or FORTRAN unformatted
format. NEUTRAL indicates the database to be loaded is in ASClI format. The
default is BlNARY.
Remarks:
1. The DBLOAD statement and its applications are discussed further in Database Concepts in the MSC
Nastran Reference Guide.
2. If the DATABLK keyword is specified and PARAM is not specified, then only data blocks may be
loaded. If the PARAM keyword is specified and DATABLK is not specified, then only parameters
may be loaded. If neither DATABLK nor PARAM is specified, then all data blocks and parameters
may be loaded.
Main Index
DBLOAD 85
Loads a Database from a FORTRAN File
3. The DB keyword is equivalent to DATABLK, and the PARM keyword is equivalent to PARAM.
4. The database to be loaded is attached as read-only. In other words, items can only be fetched and not
stored on this database.
5. If more than one DBLOAD statement is specified, then they will be processed in the order in which
they appear. If a duplicate data block or parameter is found on two or more different DBLOAD
statements, then the last duplicate will be used.
6. If NEUTRAL is specified, then the FORMATTED keyword must be specified on the corresponding
ASSIGN statement.
7. If a data block or parameter is being renamed, then the new name must be defined in the NDDL of
the primary database.
8. If the database to be loaded and the primary database have different NDDL schemes and CONVERT
is not used, then the following is performed:
• If a qualifier in the NDDL of the database to be loaded is not in the NDDL of the primary
database, then all of its values are converted to the null value corresponding to its type. For
example, if the qualifier is integer, real, double-precision, complex, or character, then the value is
converted to 0, 0., 0.D0, (0.,0.), or blank, respectively. If this conversion results in a duplicate
data block(s) or parameter(s), then a User Warning Message is printed and the duplicates are not
loaded.
• If a DBset-name in the NDDL of the database to be loaded is not in the NDDL of the primary
database, then its values will be converted to the PARAM default value in the NDDL of the
database to be loaded.
9. Data blocks that are equivalenced on the database to be loaded remain equivalenced as long as they
are loaded in the same DBLOAD statement or in consecutive DBLOAD statements with the same
unit number. Otherwise, a separate copy for the secondary data block is produced.
10. It is not possible to restart from a database created by DBLOAD in the same run.
11. SOL 190 (or DBTRANS) is also required with DBLOAD if:
• The database to be loaded has a different BUFFSlZE.
• The database to be loaded is in neutral format or is being transferred between different machine
types.
See also the Database Concepts in the MSC Nastran Reference Guide.
Main Index
86 DBLOCATE
Attaches Secondary Databases
DBLOCATE Attaches Secondary Databases
Obtains data blocks or parameters from prior versions of the primary database, or other databases.
DBLOCATE may also be used to compress the primary database and to migrate databases created in prior
MSC Nastran versions.
Format:
DBLOCATE DATABLK = * PARAM = * WHERE where-expr ,
datablk-list param-list
CONVERT convert-expr LOGICAL = dbname OVRWRT COPY
NOOVRWRT
Example:
1. Locate in version 4 of MASTER3 all data blocks named KAA for all superelements with IDs greater
than 0.
DBLOCATE DATABLK=(KAA) WHERE(PROJECT=’FRONT BUMPER’ ,AND
SEID>0 AND VERSION=4) LOGI=MASTER3
ASSIGN MASTER3=’physical file name of master DBset’
2. Copy all data blocks and parameters from the last version of MASTER3 to the primary database. For
all items with the qualifier SEID, change the SEID to twice the old ID number.
DBLOCATE CONVERT(SEID=2*SEID) COPY LOGI=MASTER3
ASSIGN MASTER3=’physical file name of master DBset’
3. Compress a database with multiple versions. All versions under the current project-ID (see PROJ
statement) will be copied from the database OLDDB to NEWDB.
ASSIGN MASTER3=’physical filename of new master DBset’
ASSIGN OLDDB=’physical filename of old master DBset’
DBLOCATE LOGI=OLDDB COPY WHERE(VERSION=*) ,
CONVERT(VERSION=VERSION;PROJECT=PROJECT)
Main Index
DBLOCATE 87
Attaches Secondary Databases
Describer Meaning
datablk-list Specifies a list of data blocks separated by commas. The default is *, which selects all data
blocks. The located data block may be renamed in the primary database by specifying a
slash after the old name followed by the new name. For example, if KLL is to be renamed
to KLL1, then DATABLK=(KLL/KLL1) is specified.
param-list Specifies a list of parameters separated by commas. The default is *, which selects all
parameters. The located parameter may be renamed in the primary database by
specifying a slash after the old name followed by the new name. For example, if LUSETS
is to be renamed to LUSET, then PARAM=(LUSETS/LUSET) is specified.
where-expr A logical expression that specifies the desired values of qualifiers PROJECT, VERSION,
and DBSET. For example, WHERE(VERSlON= 4 AND SEID<>2 AND SEID>0)
selects all items under version 4 for all values of SEID greater than 0 except 2. See the
beginning of this section for more information on WHERE and CONVERT clauses.
The default for VERSION is the last version-ID and PROJECT is the current
project-ID. The default for qual is *, which is all qualifier values found on the located
database. See also Remark 9.
convert-expr Modifies the values for PROJECT, VERSION, DBSET, and qualifiers selected by the
where-expr. The format of convert-expr is:
PROJECT=project-expr; VERSION=version-expr; DBSET=DBset-name;
quali=qual-expri[;...]
For example,
CONVERT (SEID=100+SEID; SPC=102)
See the beginning of this section for more information on WHERE and CONVERT
clauses.
The default action for VERSION and PROJECT is to convert to the current version-ID
and current project-ID. But if either PROJECT or VERSION is specified in the
convert-expr, then both must be specified. See Example 3. The default action for
qualifiers and DBSET is to use the same values as long both databases have the same
NDDL scheme. If not, see Remark 9.
dbname Specifies the logical name of the master directory DBset of the located database. dbname
must be specified on an ASSIGN statement, which references the physical file name. By
default, the located database is also the primary database. (If dbname is specified for the
primary database, then dbname must be MASTER.)
OVRWRT By default, duplicate data blocks or parameters on the located database will take
NOOVRWRT precedence over those on the primary database. A duplicate means that a data block or
parameter has not only the same name but also the same qualifier values, PROJECT,
VERSION, and DBSET as the data block or parameter on the primary database. If
NOOVRWRT is specified, then a fatal message is issued.
COPY Requests that the located data blocks or parameters be copied to the primary database.
Main Index
88 DBLOCATE
Attaches Secondary Databases
Remarks:
1. The DBLOCATE statement and its applications are discussed further in the Database Concepts in the
MSC Nastran Reference Guide.
2. If the DATABLK keyword is specified and PARAM is not specified, then only data blocks may be
located. If the PARAM keyword is specified and DATABLK is not specified, then only parameters
may be located. If neither DATABLK nor PARAM is specified, then all data blocks and parameters
may be located.
3. The DB keyword is equivalent to DATABLK, and the PARM keyword is equivalent to PARAM.
4. If more than one DBLOCATE statement is specified, then they will be processed in the order in
which they appear. If a duplicate data block or parameter is found on two or more different
DBLOCATE statements, then the last duplicate will be used.
5. If the located database is not the primary database, then it is attached for read-only purposes. In other
words, items can only be fetched and not stored on the located database.
6. If the RESTART FMS statement is also specified, then located data blocks and parameters are treated
as if they exist in the restart version. In other words, restart equivalences will be made on located items
at the beginning of the run and can be subsequently broken as a result of regeneration and/or NDDL
dependencies.
7. If a data block or parameter is being renamed, then the new name must be defined in the NDDL of
the primary database.
8. If LOGICAL refers to the primary database and one version is to be copied to another, then the items
are equivalenced.
9. If the located database and the primary database have different NDDL schemes and CONVERT is
not used, then the following is performed:
• If a qualifier in the NDDL of the located database is not in the NDDL of the primary database,
then all of its values are converted to the null value corresponding to its type. For example, if the
qualifier is integer, real, double precision, complex or character then the value is converted to 0,
0., 0.D0, (0.,0.), or blank, respectively. If this conversion results in a duplicate data block(s) or
parameter(s), then a User Warning Message is printed and the duplicates are not located.
• If a dbset-name in the NDDL of the located database is not in the NDDL of the primary database,
then its values will be converted to the PARAM default value in the NDDL of the located
database.
Main Index
DBSETDEL 89
Deletes a DBset
DBSETDEL Deletes a DBset
Deletes a DBset, all of its members, and associated physical files.
Format:
DBSETDEL dbsetnamei
Example:
Delete DBset DBUP20 from the database.
DBSETDEL DBUP20
Describer Meaning
dbsetnamei Specifies the name(s) of DBset(s) to be deleted. The DBset names MASTER,
OBJSCR, or SCRATCH may not be specified.
Remarks:
1. The DBSETDEL statement and its applications are discussed further in Database Concepts in the MSC
Nastran Reference Guide.
2. If dbsetnamei does not exist, then no action is taken.
3. After a DBset has been deleted with this statement, it may be recreated with the INIT statement in a
subsequent run.
Main Index
90 DBUNLOAD
Unloads a Database to a FORTRAN File
DBUNLOAD Unloads a Database to a FORTRAN File
Stores data blocks or parameters from the primary database onto a FORTRAN file in a binary or neutral
format, for purposes of database compression or database transfer between different computers.
Format:
DBUNLOAD DATABLK = * PARAM = * WHERE where-expr
datablk-list param-list
UNIT = unit FORMAT = BINARY REWIND
NEUTRAL NOREWIND
Example:
1. Unload the database in ASCII format onto FORTRAN unit 12.
DBUNLOAD UNIT=12 FORMAT=NEUTRAL
ASSIGN DBUNLOAD=’physical file name of FORTRAN unit 12’ ,
UNIT=12 FORMATTED
2. Unload version 1 of KAA under project FRONT BUMPER.
DBUNLOAD DATABLK=(KAA) WHERE(PROJECT=’FRONT BUMPER’ ,AND
SEID=10 AND VERSION=1)
ASSIGN DBUNLOAD=’physical file name of FORTRAN unit 50’
Describer Meaning
datablk-list Specifies a list of data blocks separated by commas. The default is*, which selects
all data blocks.
param-list Specifies a list parameters separated by commas. The default is*, which selects
all parameters.
where-expr Logical expression that specifies the desired values of qualifiers PROJECT,
VERSION, and DBSET. For example,
WHERE(VERSION=4 AND SElD<>2 AND SElD>0)
selects all items under version 4 for all values of SEID greater than 0 except 2.
See the beginning of this section on WHERE and CONVERT Clauses.
Main Index
DBUNLOAD 91
Unloads a Database to a FORTRAN File
Describer Meaning
The default for VERSION is * for all versions; PROJECT is* for all projects;
and DBSET is * for all DBsets. The default for qual is*, which is all qualifier
values found on the primary database.
unit Specifies the FORTRAN unit number to unload the database. The unit must
be specified on an ASSIGN statement, which references its physical filename.
The default is 50.
NEUTRAL The database may be unloaded in BINARY or NEUTRAL format. BlNARY
BINARY indicates the database is to be unloaded in binary or FORTRAN unformatted.
NEUTRAL indicates the database is to be unloaded in ASCII format. The
default is BlNARY.
NOREWIND By default, if DBUNLOAD is executed more than once for the same unit, then
REWIND the unit is not rewound. REWlND requests that the unit be rewound prior to
unloading.
Remarks:
1. The DBUNLOAD statement and its applications are discussed further in Database Concepts in the
MSC Nastran Reference Guide.
2. If the DATABLK keyword is specified and PARAM is not specified, then only data blocks may be
unloaded. If the PARAM keyword is specified and DATABLK is not specified, then only parameters
may be unloaded. If neither DATABLK nor PARAM is specified, then all data blocks and parameters
may be unloaded.
3. The DB keyword is equivalent to DATABLK, and the PARM keyword is equivalent to PARAM.
4. If more than one DBUNLOAD statement is specified, then they will be processed in the order in
which they appear.
5. If NEUTRAL is specified, then the FORMATTED keyword must be specified on the corresponding
ASSIGN statement.
6. If NEUTRAL is specified, then only data blocks with an NDDL description are unloaded. (See the
MSC Nastran DMAP Programmer’s Guide under the DATABLK statement.) An NDDL description is
required for TYPE=TABLE and none is required for TYPE=MATRlX. The data block must be
unloaded in BINARY if TYPE=UNSTRUCTURED, KDlCT, or KELM.
7. Data blocks that are equivalenced on the primary database remain equivalenced as long as they are
unloaded in the same DBUNLOAD statement or in consecutive DBUNLOAD statements with the
same unit number. Otherwise, a separate copy for the secondary data block is produced.
Main Index
92 DBUPDATE
Specifies Database Directory Update Interval
DBUPDATE Specifies Database Directory Update Interval
Specifies the maximum length of CPU time between database directory updates to the MASTER DBset. This
statement is intended to be used if the INIT MASTER(RAM=r) option is specified.
Format:
DBUPDATE [=] update-time
Example:
DBUPDATE = 5.5
The preceding example would call for a database directory update at the end of a DMAP module execution
after five and one-half minutes of CPU time have elapsed from the last update.
Describer Meaning
update-time CPU time interval in minutes (real or integer) between database directory
updates.
Remarks:
1. The difference in CPU time from the last update is checked after the execution of each DMAP
instruction. The database directory is updated if this difference is greater than update-time.
Update-time and CPU time is accurate to the nearest whole second only.
2. If update-time < 0, then database directory updates are only performed at the end of the run.
3. Defaults for update-time are machine dependent and may be found in the MSC Nastran Installation
and Operations Guide.
4. Periodic updates of the directory tables to MASTER DBset increases the integrity of the database
during system crashes (for example, crashes due to insufficient time or space).
5. Directory updates are performed automatically at various points in the execution of the DMAP in
addition to those specified by DBUPDATE. An asterisk appears after the word “BEGN” in the
executive summary table whenever an update occurs. See the Output Description in the MSC Nastran
Reference Guide. These updates occur whenever a permanent data block, parameter DMAP
equivalence, or restart equivalence is broken. Updates also occur upon deletions. Additions to the
database do not automatically cause a directory update to take place.
6. This statement is in effect only when INIT MASTER(RAM=r) is being used. INIT MASTER(S) and
INIT MASTER(NORAM) disable periodic and automatic updates.
7. Update-time may also be changed with the DMAP instruction PUTSYS(update-time, 128) or the
NASTRAN SYSTEM(128)=update-time statement. (The update-time must be a real,
single-precision value specified in minutes.)
Main Index
DEFINE 93
Parameter Definition
DEFINE Parameter Definition
Assigns user-defined keywords (or cellnames) to a NASTRAN system cell. (See the NASTRAN statement for
a description of “cellname”.) In addition, the DEFINE statement provides a mechanism to set default values
for system cells.
Format:
DEFINE keyword [ =expression ] [ LOCATION=SYSTEM(i) ] [ TYPE=type ]
Describer Meaning
keyword User-defined name, 1 through 24 characters in length. The first character must be
alphabetic. The following characters can be used for keywords: A through Z, _, and
0 through 9. Any other characters are invalid.
expression Expression produces a single value from a set of constant and/or variable parameters
separated by operators. The value is assigned to the “keyword” and is also used to set
the value for the NASTRAN system cell specified by “LOCATION”. TYPE
determines both the type of the result and the type conversions that will be applied
to the constants and variables within the expression--mixed mode expressions are
allowed (see Remark 6.). The parentheses can be used to change the order of
precedence. Operations within parentheses are performed first, with the usual order
of precedence being maintained within the parentheses. The variable parameters
within the expression must be keywords previously defined on a DEFINE statement.
The following operations are allowed:
Parameter Type Operator Operation
Integer or Real + Addition
- Subtraction
Multiplication
* Division
/
Logical + Bit-wise OR
Logical - Bit clear. For example, the result of
a-b is equal to the value of a with the
bits associated with b set to 0.
Main Index
94 DEFINE
Parameter Definition
Describer Meaning
SYSTEM(I) Specifies the NASTRAN system cell number to be associated with the keyword.
type The type of expression result, and the type of conversions that will be applied to the
constants and variables within the expression. Allowable data types are as follows:
Description Type
Integer (default) I
Real R
Logical LOGICAL
Remarks:
1. If TYPE, LOCATION, and EXPRESSION are omitted, the default data type is Integer and the
default value is zero.
2. If EXPRESSION is omitted, an internal default will be assigned to the keyword/cellname based on
the LOCATION (See The NASTRAN Statement for a list of internal default values).
3. A DEFINE statement that specifies a LOCATION is actually setting the default for a NASTRAN
system cell,I and therefore it is not necessary to also set the system cell value on a subsequent
NASTRAN statement unless the user wishes to override the previous DEFINE statement setting.
Also, since more than one DEFINE statement may be present for the same “keyword”, the last
specification takes precedence. “Keywords” referenced on a NASTRAN statement, or in an
expression on the DEFINE statement, are automatically substituted by the last specification of the
“keyword” prior to the current statement being processed.
4. DEFINE statements may also be specified in runtime configuration (RC) files. See the .
5. System cells may also be set with the NASTRAN statement. In addition, they may be set or values
returned with the DMAP PUTSYS and GETSYS functions and the PARAM module. See the MSC
Nastran DMAP Programmer’s Guide.
6. Each operand within the expression will be converted to the result type prior to the arithmetic
operation. For example: the statement “DEFINE JJ=2.5 + 3.6 TYPE=I” would result in 2.5 and 3.6
being converted to 2 and 3, respectively, and the result of 5 would be assigned to JJ.
Examples:
1. Change the default value for block size:
DEFINE BUFFSIZE=8193 LOCATION=SYSTEM(1)
2. Set the sparse matrix selection to forward-backward substitution only:
DEFINE SPARSE=16 LOCATION=SYSTEM(126)
Main Index
DEFINE 95
Parameter Definition
3. Define the system cell keyword and default value for the maximum output line count and then reset
it to another value on a NASTRAN statement. Note: The DEFINE statement would typically be
placed in an RC file and the NASTRAN statement would be placed in the File Management Section
whenever the user wants to override the DEFINE statement default setting.
DEFINE MAXLINES=999999999 LOCATION=SYSTEM(9)
NASTRAN MAXLINES=100000
4. Define system cells that behave like “toggles,” turning some feature on or off:
DEFINE MESH=2 LOCATION=(31)
DEFINE NOMESH=0 LOCATION=(31)
NASTRAN MESH
Note: Since each subsequent DEFINE statement redefines the default value, the second
DEFINE of system cell location 31 sets the default value to 0. A NASTRAN statement
can then be inserted in the input file to reset the MESH system cell back to a value of 2.
This same technique can be used with any system cell where the user wishes to refer to
the system cell keyword and have the system cell set to a previous DEFINE statement
default.
5. Invalid usage of the DEFINE and NASTRAN statement:
DEFINE BUFFSIZE=8193
NASTRAN BUFFSIZE=8193
Valid usage:
DEFINE BUFFSIZE=8193 LOCATION=SYSTEM(1)
NASTRAN BUFFSIZE=8193
Main Index
96 ENDJOB
Terminates Job
ENDJOB Terminates Job
Terminates the job at a user-specified location in the FMS Section.
Format:
ENDJOB
Example:
DBDICT
ENDJOB
Remark:
ENDJOB is normally used after a DBDICT statement, or after database initialization.
Main Index
EXPAND 97
Concatenates New DBset Members
EXPAND Concatenates New DBset Members
Concatenates additional DBset members on an existing permanent DBset previously defined with an INIT
statement.
Format:
EXPAND dbset-name LOGlCAL=( log-namei [(max-sizei)]...)
Example:
ASSIGN DBMEM02=’physical file name’
EXPAND DBALL LOGICAL=(DBMEM02)
This would create and add the DBset member DBMEM02 to the existing DBset DBALL.
Describer Meaning
dbset-name The name of a DBset previously defined with an INIT statement.
log-namei Specifies the logical name of a DBset member. log-namei may also be
referenced on an ASSIGN statement which refers to the physical file name of
the DBset member.
Main Index
98 EXPAND
Concatenates New DBset Members
Describer Meaning
max-sizei Specifies the maximum size in blocks, words or bytes of a DBset member. For
storage units specified in words or bytes, the size must be followed by one of
the following unit keywords:
Unit Keyword Storage Unit
W Words
B Bytes
KW, K Kilowords (1024 words)
KB Kilobytes (1024 bytes)
MW, M Megawords (10242 words)
MB Megabytes (10242 bytes)
GW, G Gigawords (10243 words)
GB Gigabytes (10243 bytes)
TW, T Terawords (10244 words)
TB Terabytes (10244 bytes)
For example, 100MB = 100 megabytes, 1.5GB = 1.2 gigabytes = 1536
megabytes, and 2.5M = 2.5 megawords = 2560 kilowords. The size of a block
in words is defined by BUFFSlZE.
Remark:
1. On all computers with dynamic file allocation, the physical filename of a DBset member may be
specified on an ASSIGN statement:
ASSIGN log-name=’physical filename’
If an ASSIGN statement is not specified for the member, then a name is automatically assigned. The
naming convention is described in Database Concepts in the MSC Nastran Reference Guide.
Main Index
INCLUDE 99
Inserts External File
INCLUDE Inserts External File
Inserts an external file into the input file. The INCLUDE statement may appear anywhere within the input
data file.
Format:
INCLUDE 'filename'
Example:
The following INCLUDE statement is used to obtain the bulk data from another file called
MYBULK.DATA:
SOL 101
CEND
TITLE = STATIC ANALYSIS
LOAD = 100
BEGIN BULK
INCLUDE 'MYBULK.DATA'
ENDDATA
Describer Meaning
filename Physical filename of the external file to be inserted. The user must supply the
name according to installation or machine requirements. It is recommended
that the filename be enclosed by single right-hand quotation marks ( ‘ ).
Remarks:
1. INCLUDE statements may be nested; that is, INCLUDE statements may appear inside the external
file. The nested depth level must not be greater than 10.
2. The total length of any line in an INCLUDE statement must not exceed 72 characters. Long file
names may be split across multiple lines. For example, the file:
/dir123/dir456/dir789/filename.dat
may be included with the following input:
INCLUDE ‘/dir123
/dir456
/dir789/filename.dat’
3. See the for more examples.
Main Index
100 INIT
Creates a DBset
INIT Creates a DBset
Creates a temporary or permanent DBset. For the SCRATCH and MASTER DBsets, all or some of their
space may be allocated to real memory.
Format 1: Initialize any DBset except MASTER and SCRATCH:
INIT DBset-name [LOGICAL=(log-namei(max-sizei),...) BUFFSIZE=b CLUSTER=c]
Format 2: Initialize the MASTER DBset:
INIT MASTER RAM = r S LOGICAL = (log-name(max-sizei), ...),
NORAM
BUFFSIZE = b CLUSTER = c ]
Format 3: Initialize the SCRATCH DBset:
INIT SCRATCH MEM = m LOGICAL = (log-name(max-sizei), ...),
NOMEM
SCR300 = (log-namei(max-sizei),...) BUFFSIZE = b CLUSTER=c ]
Example:
1. Modify the default allocation of the DBALL DBset to 50000 blocks:
INIT DBALL LOGI=(DBALL(50000))
2. Do not allocate any real memory for the MASTER and SCRATCH DBsets:
INIT MASTER(NORAM)
INIT SCRATCH(NOMEM)
3. Create a new DBset called DBUP with two members DBUP1 and DBUP2:
INIT DBUP LOGI=(DBUP1, DBUP2)
ASSIGN DBUP1 =’physical filename 1’
ASSIGN DBUP2=’physical filename 2’
Main Index
INIT 101
Creates a DBset
Describer Meaning
dbset-name The name of a temporary or permanent DBset.
MASTER
SCRATCH
log-namei Specifies the logical name of a DBset member. log-namei may also be referenced
on an ASSIGN statement, which refers to the physical file name of the DBset
member. If no log-namei is specified, then the DBset will have one member and
the log-name will be the same as the DBset-name. A maximum of twenty
log-names may be specified. For the SCRATCH DBset, see also Remark 8.
SCR300 is a special keyword that indicates that the log-names are members
reserved for DMAP module internal scratch files.
max-sizei Specifies the maximum size, in blocks, words, or bytes, of a DBset member. For
storage units specified in words or bytes, the size must be followed by one of the
following unit keywords:
Unit Keyword Storage Unit
W Words
B Bytes
KW, K Kilowords (1024 words)
KB Kilobytes (1024 bytes)
MW, M Megawords (10242 words)
MB Megabytes (10242 bytes)
GW, G Gigawords (10243 words)
GB Gigabytes (10243 bytes)
TW, T Terawords (10244 words)
TB Terabytes (10244 bytes)
For example, 100MB = 100 megabytes, 1.5GB = 1.5 gigabytes = 1536
megabytes, and 2.5M = 2.5 megawords = 2560 kilowords. The size of a block
in words is defined by BUFFSlZE. The default for DBALL and SCRATCH
may be found in the and ranges from 250,000 blocks to 4,000,000 blocks.
RAM RAM=r requests that r words of real memory are to be allocated for the
NORAM MASTER DBset. See the nast20234 Command in the MSC Nastran Reference
Guide. The default is RAM or RAM=30000. NORAM or RAM=0 specifies that
no real memory is to be allocated.
Main Index
102 INIT
Creates a DBset
Describer Meaning
S If the primary database is being created in the run, this option requests that all
DBsets in the primary database will be automatically deleted at the end of the
run. INIT MASTER(S) is equivalent to specifying scr=yes on the “nastran”
statement. See Executing MSC Nastran, 1. If the run is a restart, then this option is
ignored.
MEM MEM=m specifies that m blocks of real memory are to be allocated for the
NOMEM SCRATCH DBset. See The NASTRAN Statement (Optional) (p. 13) in the MSC
Nastran Reference Guide. The default m is machine dependent and may be
found in the . NOMEM or MEM=0 requests that no real memory is to be
allocated.
BUFFSlZE BUFFSlZE=b specifies the number of words per block in the DBset and will
override the value specified by the BUFFSlZE keyword on the NASTRAN
statement. The default for b is obtained from the NASTRAN BUFFSIZE
statement.
CLUSTER CLUSTER=c specifies the number of blocks per cluster in the DBset. The
default is 1, and any other value is not recommended.
Remarks:
1. The INIT statement and its applications are further discussed in Database Concepts in the MSC Nastran
Reference Guide.
2. Four DBsets are predefined and automatically allocated by the program. Their DBset-names are
MASTER, DBALL, SCRATCH, and OBJSCR, and they are described in Database Concepts in the
MSC Nastran Reference Guide.
3. On all computers with dynamic file allocation, the physical filename of a DBset member may
specified on an ASSIGN statement:
ASSIGN log-name=’physical filename’
If an ASSIGN statement is not specified for the member, then a name is automatically assigned. The
naming convention is described in Database Concepts in the MSC Nastran Reference Guide.
4. It is recommended that there be sufficient physical space to hold a DBset member should it reach its
maximum size (max-sizei). The max-sizei may be converted to words by multiplying by b. A summary
of space usage and allocation is printed at the end of the execution summary table.
5. In restart runs, the INIT statement is ignored for preexisting permanent DBsets. The INIT statement
is intended to be specified only in the run in which the DBset is being created. If more DBset
members need to be added to the DBset, then the EXPAND statement is used.
6. If RAM or RAM=r is specified and the run terminates because the computer operating system detects
insufficient space or time, or the computer halts due to a power outage or operator interruption, then
it may not be possible to restart from the database. See the DBUPDATE FMS statement.
Main Index
INIT 103
Creates a DBset
7. BUFFSIZE=b and CLUSTER=c must satisfy the following inequality:
64000
b --------------- + 5
c
8. By default, the SCRATCH DBset is divided into two partitions: LOGICAL and SCR300. The
LOGICAL partition, log-names after the LOGICAL keyword, are reserved for DMAP scratch data
blocks, and the SCR300 partition for DMAP module internal scratch files.
• The maximum total number of log-names for LOGICAL and SCR300 is 20. For example, if
LOGICAL has 8 log-names, then SCR300 can have no more than 12 log-names.
• If NASTRAN SYSTEM(142)=1 is specified, then the SCR300 partition is not created and
internal scratch files, along with DMAP scratch data blocks, will reside on the LOGICAL
partition. The default is SYSTEM(142)=2.
• If NASTRAN SYSTEM(151)=1 is specified and the LOGICAL partition has reached its
maximum size, then the SCR300 partition will be used. The default is SYSTEM(151)=0.
• By default, the space specified for the SCR300 partition is released to the operating system after
each DMAP module is executed if the module used more than 100 blocks for internal scratch files.
If 100 blocks is not a desirable threshold, then it may be changed by specifying NASTRAN
SYSTEM(150)=t, where t is the number of blocks for the threshold.
9. BUFFSlZE=b is predefined for DBset-names MSCOBJ, OBJSCR, and USROBJ and may not be
changed by BUFFSIZE on this statement or if the NASTRAN BUFFSlZE=bmax statement (see The
NASTRAN Statement (Optional) (p. 13) in the MSC Nastran Reference Guide). The default for b is
recommended for all except very large problems. bmax must reflect the maximum of b specified for
all DBsets attached to the run, including the delivery database. See for the defaults of b and bmax.
10. If INIT MASTER(RAM=r) and INIT SCRATCH(MEM=m) are specified, then BUFFSIZE for
these DBsets must be the same. If not, a warning message is issued, and the BUFFSlZE for the
SCRATCH DBset is reset to that of the MASTER DBset.
11. Only one INIT statement per dbset-name may be specified in the File Management Section.
Main Index
104 MEMLIST
Specify Datablocks Eligible for SMEM
MEMLIST Specify Datablocks Eligible for SMEM
Specifies a list of scratch datablocks that may reside in scratch memory (SMEM).
Format:
MEMLIST DATABLK = (DBname1, DBname2, ..., DBnamei)
Example:
MEMLIST DATABLK = (KOO, MOO, KQQ, MQQ)
If generated, datablocks KOO, MOO, KQQ, and MQQ will reside in scratch memory. All other datablocks
will be excluded from scratch memory.
Describer Meaning
DBnamei Name of a Nastran datablock.
Remarks:
1. Only NDDL and local scratch datablocks may be included in MEMLIST specification.
2. Datablocks specified will reside in SMEM on a first-come, first-served basis.
3. Datablocks not specified by this statement will not reside in SMEM.
4. Database directories for the SCRATCH DBset reside in SMEM and are not affected by any
MEMLIST specification.
5. Continuation lines are allowed.
6. Multiple MEMLIST statementss are honored.
7. Scratch I/O activity is reported in the .f04 file by including DIAG 42 in the Executive Control
Section.
Main Index
PROJ 105
Defines Database Project-Identifier
PROJ Defines Database Project-Identifier
Defines the current or default project identifier, project-ID.
Format:
PROJ [=] ’project-ID’
Examples:
1. PROJ = ’MY JOB’
2. The following project-ID will be truncated to 40 characters:
PROJ ’CAR MODEL 1999 BODY FRAME SYM - PROTYP B RUN’
and all subsequent restarts must have the statement.
PROJ ’CAR MODEL 1999 BODY FRAME SYM - PROTYP B’
Describer Meaning
project-ID Project identifier. Must be enclosed in single quotes. (Character string,
maximum of 40 characters; Default=blank)
Remarks:
1. There may be only one PROJECT statement in the File Management Section. The PROJECT
statement must be specified before all DBCLEAN, DBDICT, RESTART, DBLOCATE, and
DBLOAD statements where project-ID is not specified by the user.
2. This statement is optional and specifies that all data blocks and parameters to be stored on or accessed
from the database in the current run shall also be identified by project-ID. Therefore, in subsequent
runs that may access this data through other FMS statements such as RESTART, the project-ID must
be specified.
3. Project-ID is the default on DBCLEAN, DBDICT, and RESTART FMS statements and in the
WHERE and CONVERT clause of the DBLOCATE statement.
4. Leading blanks and trailing blanks enclosed within the single quotes are ignored. All other blanks are
considered part of the project-ID.
Main Index
106 RESTART
Reuses Database From a Previous Run
RESTART Reuses Database From a Previous Run
Requests that data stored in a previous run be used in the current run.
Format:
RESTART PROJECT=project VERSION = version-ID KEEP LOGICAL = dbname
LAST NOKEEP
Examples:
1. RESTART VERSION=7
Version number 7 will be retrieved for this run (version 8). At the end of the run, version 7 will be
deleted.
2. PROJ=’FENDER’
RESTART
The last version under project-ID FENDER will be used in the current run.
3. ASSIGN RUN1=’run1.MASTER’
RESTART LOGICAL=RUN1
The run1.MASTER and its associated database will be used (read only) for restart purposes.
Describer Meaning
project-ID Project identifier. See description of the PROJ FMS statement. Must be
enclosed in single right-hand quotation marks (’) (Character string, maximum
of 40 characters; default is the project-ID specified on the PROJ FMS
statement).
version-ID Version number (Integer > 0).
LAST Specifies the last version under project-ID.
KEEP Data stored under VERSION will remain on the database after the run is
completed.
NOKEEP Data stored under VERSION will be deleted from the database after the run is
completed.
dbname Specifies the logical name of an existing MASTER (master directory) DBset to
be used for restart purposes. This MASTER and its associated database will be
opened in a read-only mode to perform the restart; any new data will be written
to the database for the current run. For read-only restart (NOKEEP), the
logical name MASTER should not be used and UFM 10626 will be issued.
Remarks:
1. There may only be one RESTART statement in the File Management Section.
Main Index
RESTART 107
Reuses Database From a Previous Run
2. A new version-ID is automatically assigned whenever a restart is performed.
3. If project-ID or version-ID or both are specified and cannot be found, then a fatal message will be
issued.
4. The RESTART statement is required to perform restarts in solution sequences 101 through 400.
5. If PROJECT is not specified, then the run will restart from the project-ID specified on the PROJ
statement (See Example 2.).
6. Databases created by one MSC Nastran version typically cannot be directly restarted into a different
MSC Nastran version. Restrictions are typically documented in the current release guide; however, a
DBLOCATE type restart might work.
7. Restarts do not work with DMP. Restarts do not work with ACMS for versions released before 2018.
8. If NASTRAN IFPSTAR=YES (default) and scr=no then the Bulk Data images will be stored on the
IFPDAT file; for example, if the input file name is run1 then run1.IFPDAT will be created along
with run1.MASTER and run1.DBALL. Please note the following when performing a restart.
a. If run1.IFPDAT, run1.MASTER and run1.DBALL are in the same folder then only the
MASTER file needs to be specified on an ASSIGN statement. For example, ASSI
cold='run1.MASTER' RESTART LOGI=cold
b. If run1.IFPDAT is in a different folder than that of run1.MASTER and run1.DBALL (or
IFPDAT has been renamed in the same folder) then both the MASTER and IFPDAT must
specified on ASSIGN statements and the IMPORT keyword must be specified on the ASSIGN
IFPDB statement:
ASSI cold='run1.MASTER'
RESTART LOGI=cold
ASSI IFPDB='other_folder/run1.IFPDAT' IMPORT
9. For SOL 400 one must also use NLRESTART (Case).
10. The database is not suitable for restart if any of the following was specified in the cold start. If a restart
is attempted then the program will issue User Fatal Message 9061.
a. EXTSEOUT(DMIGDB or MATDB or MATRIXDB) without defining DBEXT.
b. scr=post
c. scr=no and “NASTRAN SYSTEM(316)>0”.
11. Restarts of SOL 112 fatigue analyses also require case control FATIGUE(STROUT=-1). Please see
Ap. A: Restarts in MSC.Nastran Embedded Fatigue User's Guide for restarts for fatigue analyses.
Main Index
108 RESTART
Reuses Database From a Previous Run
Main Index
Chapter 4: Executive Control Statements
MSC Nastran Quick Reference Guide
4 Executive Control
Statements
Key to Descriptions
Executive Control Statement Descriptions
Main Index
108 MSC Nastran Quick Reference Guide
Key to Descriptions
Key to Descriptions
Braces { } indicate A brief sentence Brackets [ ] indicate
that a choice of de- about the function that a choice of de-
scribers is mandato- of the statement is scribers is optional.
ry. given.
The
Thedefault
defaultdescribers
describersare
are
shaded.
shaded.
Describers in uppercase letters are
keywords that must be specified as
shown.
Describers in lower
case are variables.
If the describers are stacked vertically,
then only one may be specified.
If the describer is in lower case, then it is a variable and
the describer’s type (e.g., Integer, Real, or Character),
allowable range, and default value are enclosed in pa-
rentheses. If no default value is given, the describer
must be specified by the user.
Each of the describers is discussed briefly.
Further details may be discussed under
Remarks.
The remarks are generally arranged in order of im-
portance and indicate such things as the statement’s
relationship to other statements, restrictions and rec-
ommendations on its use, and further details regard-
ing the describers.
Main Index
Chapter 4: Executive Control Statements 109
Key to Descriptions
Executive Control Section
This section describes the Executive Control statements. These statements select a solution sequence and
various diagnostics.
Most Executive Control statements are order independent. The exceptions are the COMPILE, COMPILER,
ALTER, ENDALTER, and LINK statements. If used, the LINK statement must appear after all COMPILE
statements. The COMPILER statement (or equivalent DIAGs) must appear before all COMPILE
statements. The COMPILER statement also sets the defaults for subsequent COMPILE statements.
Executive Control Statement Summary
The Executive Control statements are summarized as follows:
ALTER Specifies deletion and/or insertion of the DMAP statements that follow.
APP Specifies an approach in a solution sequence.
CEND Designates the end of the Executive Control statements.
COMPILE Requests compilation of specified subDMAPs or the NDDL file.
COMPILER Specifies DMAP compilation diagnostics.
DIAG Requests diagnostic output or modifies operational parameters.
DOMAINSOLVER Selects domain decomposition solution methods.
ECHO Controls the echo of Executive Control statements.
ENDALTER Designates the end of a DMAP sequence headed by an ALTER.
GEOMCHECK Specifies tolerance values and options for optional finite element geometry
tests.
ID Specifies a comment.
LINK Requests the link of a main subDMAP.
MALTER Inserts and/or deletes DMAP statements in solution sequences
MODEL_CHECK Specifies model checkout run options.
SOL Requests execution of a solution sequence or DMAP program.
SOL 700,ID Executes MSC Nastran Explicit Nonlinear (SOL 700)
SPARSESOLVER Specifies various options used in sparse solution if equations operations.
TIME Sets the maximum allowable execution time.
Main Index
110 MSC Nastran Quick Reference Guide
Executive Control Statement Descriptions
Executive Control Statement Descriptions
Executive Control statements may be abbreviated down to the first four characters as long as the abbreviation
is unique relative to all other statements. Each statement is described as follows:
Description
A brief sentence about the function of the statement is given.
Format
Describers in uppercase are keywords that must be specified as shown. In addition, describers in lowercase
indicate that the user must provide a value.
Braces { } indicate that a choice of describers is mandatory. If the describers are stacked vertically, then only
one may be specified.
Brackets [ ] indicate that a choice of describers is optional. If the describers are stacked vertically, then only
one may be specified.
Describers that are shaded indicate the defaults.
If the statement line is longer than 72 columns, then it may be continued to the next line with a comma. For
example:
COMPILE SEDRCVR SOUIN=MSCSOU,
NOREF NOLIST
Example
A typical example is given.
Describers and Meaning
Each of the describers is briefly discussed. The describer’s type (e.g., Integer, Real, or Character), its allowable
range, and its default value are enclosed in parentheses. The describer must be specified by the user if no
default value is given.
Remarks
The remarks in the remarks section are generally arranged in order of importance and indicate such things as
the Executive Control statement’s relationship to other statements, restrictions and recommendations on its
use, and further descriptions of the describers.
Main Index
$ 111
Comment
$ Comment
Used to insert comments into the input file. Comment statements may appear anywhere within the input file.
Format:
$ followed by any characters out to column 80.
Example:
$ TEST FIXTURE-THIRD MODE
Remarks:
1. Comments are ignored by the program.
2. Comments will appear only in the unsorted echo of the bulk data.
Main Index
112 ALTER
Inserts and/or Deletes DMAP Statements
ALTER Inserts and/or Deletes DMAP Statements
Inserts and/or deletes DMAP statements in a subDMAP.
Format:
ALTER k1 [,k2]
or
ALTER ’string1’[(occurrence,offset)] ,[’string2’[(occurrence,offset)]
]
or
ALTER k1 , [’string2’[(occurrence,offset)] ]
or
ALTER ’string1’[(occurrence,offset)] , [k2]
Examples:
1. The following alter will insert a MATPRN DMAP statement after the first occurrence of the string
’SDR2’ in subDMAP DSASTAT:
SOL 101
COMPILE DSASTAT $
ALTER ’SDR2’ $
MATPRN OESDS1//$
CEND
2. The following alter will delete the second occurrence of the OUTPUT4 DMAP statement in
subDMAP DSASTAT and replace it with a MATPRN DMAP statement:
SOL 101
COMPILE DSASTAT $
ALTER ’OUTPUT4’(2),’OUTPUT4’(2) $
$ OR
$ ALTER ’OUTPUT4’(2),’’ $
MATPRN OESDS1//$
CEND
Describer Meaning
k1 If k2 or ’string2’ is not specified, the subsequent DMAP statements will be
inserted after either the statement number k1 or the ’string1’,
[(occurrence,offset)] reference point.
k1, k2 DMAP statements numbered k1 through k2 will be deleted and may be
replaced with subsequent DMAP statements.
’string1’ if ’string2’ or k2 is not specified, the subsequent DMAP statements will be
inserted after the first occurrence of ’string1’.
Main Index
ALTER 113
Inserts and/or Deletes DMAP Statements
Describer Meaning
’string1’,’string2’ DMAP statements beginning with the first occurrence of ’string1’ through
DMAP statements containing the first occurrence of ’string2’ will be deleted
and may be replaced with subsequent DMAP statements.
occurrence This flag indicates which occurrence of the preceding string is to be used,
starting at the beginning of the subDMAP (Integer > 0; Default = 1).
offset This flag indicates the offset from the reference DMAP statement.
Depending on the sign the specific DMAP statement may be above (-offset)
or below (+offset) the referenced DMAP statement (Integer; Default = 0).
Remarks:
1. The ALTER statement must be preceded by a COMPILE Executive Control statement. In other
words, the ALTER statement cannot follow a MALTER statement without a preceding COMPILE
statement.
2. If an MALTER statement is used in conjunction with the ALTER statement, then the MALTER
should be placed above the COMPILE statements. Failure to place the MALTER in this position may
cause ALTER statements to be ignored.
3. The ALTERs can reference the DMAP statements in any order within a subDMAP. Two restrictions
on ordering are:
• K2 or ’string2’(occurence, offset) references must refer to a DMAP statement number that is
greater than or equal to the k1 or ’string1’(occurrence,offset) reference within a single ALTER
statement.
• K1 or ’string1’ and k2 or ’string2’ cannot overlap DMAP line positions with another ALTER that
references the same subDMAP.
4. The ’string1’ or ’string2’ used as a search pattern will apply to one complete DMAP statement; i.e., a
multiline DMAP statement will be searched for a pattern match as if each 72 character line of the
DMAP statement were concatenated together into one string–all blanks and comments either
embedded or immediately preceding the DMAP statement, will be retained. However, comments are
ignored for the following type of alter:
alter ‘^ *gp0’
5. Within a SUBDMAP, both ’string1’ and ’string2’ will be used to search for a pattern match starting
at the beginning of the subDMAP–not at the current position of the last string match.
6. The special characters (metacharacters) used for string searching are described in Remark 9. The
characters <, >, and $, which are common DMAP characters, are also special metacharacters. If they
are to be used in the search string as regular characters, then they must be preceded by a backward
slash (\). For example, to find the string
IF(DDRMM >=-1)
the command is
ALTER ’IF (DDRMM \>= -1)’ $
7. The ALTER statement must not exceed 72 characters (no continuations are allowed).
Main Index
114 ALTER
Inserts and/or Deletes DMAP Statements
8. ’string2’ (r2,02) can be defaulted to ’string1’ (r1,01) by using a null string (’’). For example, the alter
statement
ALTER ’string1’(r1,01),’’
is equivalent to
ALTER ’string1’(r1,01),’string1’(r1,01)
The defaults for (r2,02) using the null string can be overridden by specifying (r2,02).
As another example, the alter statement
ALTER ’string1’(r1,01),’’(r2,02)
is equivalent to
ALTER ’string1’(r1,01),’string1’(r2,02)
9. Metacharacters*:
. Matches any single character except newline.
* Matches any number (including zero) of the single character (including a character
specified by a regular expression) that immediately precedes it. For example, since
“.” (dot) means any character, “.*” means “match any number of characters”.
[...] Matches any one of the characters enclosed between the brackets. For example,
or < > “[AB]” matches either “A” or “B”. A range of consecutive characters can be
specified by separating the first and last characters in the range with a hyphen. For
example “[A-Z]” will match any uppercase letter from A to Z and “[0-9]” will
match any digit from 0 to 9. Some metacharacters lose special meaning inside
brackets. A circumflex (^) as the first character in the bracket tries to match any one
character not in the list.
^ or ! Requires that the following regular expression be found at the beginning of the line.
or . Note that these metacharacters may lead to User Fatal Message 802 if the preceding
line is a comment.
$ Requires that the preceding regular expression be found at the end of the line.
\ Treats the following special character as an ordinary character. For example, “\.”
stands for a period and “\*” for an asterisk. Also, to search for a tic (’), the search
string must be single quotes.
’ Marks the beginning and end of a pattern to be matched.
Note: Nonportable characters such as [ ] and ^ should be replaced (e.g., ^ ->! and [ ] -><>)
if portability is required. However, all the preceding characters are recognized by
MSC Nastran.
10. If a string-based alter uses the “!” in the expression (find occurrence at the beginning of line), it is
possible MSC Nastran will fail with User Fatal Message 802.
Main Index
APP 115
Specifies Solution Sequence Approach
APP Specifies Solution Sequence Approach
Selects heat transfer analysis in the linear static solution sequence SOL 101, or a coupled analysis combining
heat transfer and structural analysis in SOL 153.
Format:
APP approach
Example:
The following requests a heat transfer rather than a structural analysis in SOL 101.
SOL 101
APP HEAT
Describer Meaning
approach Specifies one of the following:
HEAT Indicates that heat transfer is to be performed in SOL 101.
COUPLED Indicates that a coupled analysis combining heat transfer and
structural analysis is to be preformed in SOL 153.
Remarks:
1. The APP statement is optional.
2. The APP HEAT statement applies only to linear static SOL 101. The APP HEAT statement is not
required in SOLs 153 and 159, or in SOL 101 if PARAM,HEATSTAT,YES is specified.
3. The NASTRAN HEAT=1 statement is an alternate specification of APP HEAT. See Executing MSC
Nastran, 1.
Main Index
116 CEND
End of Executive Control Section Delimiter
CEND End of Executive Control Section Delimiter
Designates the end of the Executive Control Section.
Format:
CEND
Remark:
1. CEND is an optional statement. If CEND is not specified, then the program will automatically insert
one.
Main Index
COMPILE 117
Compiles DMAP Statements
COMPILE Compiles DMAP Statements
Requests the compilation of a subDMAP, subDMAP alter, or NDDL sequence.
Format 1: Compiles a subDMAP or subDMAP alter sequence
COMPILE SUBDMAP subDMAP-name SOUIN = souin-DBset SOUOUT = souout-DBset,
DMAP
OBJOUT = objout-DBset LIST REF DECK
NOLIST NOREF NODECK
Format 2: Compiles an NDDL sequence
REF DECK
COMPILE NDDL = nddl-name SOUIN = souin-dbset LIST
SOUOUT = souout-dbset NOLIST NOREF NODECK
Examples:
1. The following compiles an alter in subDMAP PHASEIDR:
COMPILE PHASE1DR
ALTER ’CALL PHASE1A’
CEND
2. The following compiles a subDMAP called MYDMAP. (SUBDMAP and END are DMAP
statements; see the MSC Nastran DMAP Programmer’s Guide):
COMPILE MYDMAP LIST REF
SUBDMAP MYDMAP $
.
.
.
END $
CEND
3. The following obtains a listing of the NDDL:
ACQUIRE NDDL
COMPILE NDDL=NDDL LIST
CEND
Main Index
118 COMPILE
Compiles DMAP Statements
Describer Meaning
subDMAP-name The name of a subDMAP sequence. SubDMAP-name must be 1 to 8
alphanumeric characters in length and the first character must be alphabetic.
The keywords DMAP and SUBDMAP are optional and do not have to be
specified.
nddl-name The name of an NDDL sequence (Character; 1 to 8 alphanumeric characters
in length and the first character must be alphabetic). The keyword NDDL
must be specified.
souin-DBset The name of a DBset from which the subDMAP or NDDL source
statements will be retrieved (Character; 1 to 8 alphanumeric characters in
length and the first character must be alphabetic). The default is MSCSOU
if the next statement is not a subDMAP statement.
souout-DBset The name of a DBset on which the subDMAP or NDDL source statements
will be stored (Character; 1 to 8 alphanumeric characters in length and the
first character must be alphabetic). The default is the SCRATCH DBset.
objout-DBset The name of a DBset on which the subDMAP object code will be stored
(Character; 1 to 8 alphanumeric characters in length and the first character
must be alphabetic). The default is the OBJSCR DBset.
LIST,NOLIST LIST requests a compiled listing of the subDMAP or NDDL sequence.
NOLIST suppresses the listing. NOLIST is the default.
REF,NOREF REF requests a compiled cross reference of the subDMAP or NDDL
sequence. NOREF suppresses the cross reference. NOREF is the default.
DECK,NODECK DECK requests the subDMAP or NDDL source statements to be written to
the PUNCH file. NODECK suppresses the writing to the PUNCH file.
NODECK is the default.
Remarks:
1. SubDMAP names for MSC Nastran solution sequences are given in the SOL statement description.
The “COMPILER LIST REF” statement may be used to determine the appropriate
subDMAP-name.
2. If a subDMAP is being compiled and SOUIN=souin-DBset is specified, then an ALTER Executive
Control statement, or an INCLUDE statement which contains an ALTER statement as the first non-
comment line, must appear immediately after this statement. If not, then the SUBDMAP DMAP
statement must appear immediately after this statement. See the MSC Nastran DMAP Programmer’s Guide.
3. Starting in MSC/Nastran Version 69, DBsets USRSOU and USROBJ were no longer automatically
created. They must be initialized by the INIT FMS statement and then may be specified for
souin-dbset (or souout-dbset) and objout-dbset, respectively. They may be used to store the
subDMAP source statements and object code on the primary database for reexecution in a subsequent
run. Consider the following example:
In the first run, the following COMPILE statement compiles and stores a subDMAP called
MYDMAP:
Main Index
COMPILE 119
Compiles DMAP Statements
COMPILE MYDMAP SOUOUT=USRSOU OBJOUT=USROBJ
SUBDMAP MYDMAP $
.
.
END $
CEND
In the second run, the SOL statement is used to execute the MYDMAP stored in the previous run.
The LINK statement is required to retrieve the object code from the USROBJ DBset:
SOL MYDMAP
LINK MYDMAP INCL=USROBJ
CEND
In the third run, the COMPILE statement is used to alter MYDMAP and execute:
SOL MYDMAP
COMPILE MYDMAP SOUIN=USRSOU
ALTER...
.
.
.
CEND
4. If SOUOUT or OBJOUT is specified and a subDMAP with the same name as subDMAP-name
already exists on the database, then its source statements or object code will be replaced.
5. A COMPILE statement is required for each subDMAP to be compiled. If two or more COMPILE
statements reference the same subDMAP name, then only the last is used in the linking of the object
code. If the COMPILE statement is being used only to alter a subDMAP and two or more
COMPILE statements reference the same subDMAP name, then the multiple alters are assembled
and the subDMAP is compiled only once.
6. Only one COMPILE statement for an NDDL sequence may be specified in the input file.
• SOUIN=souin-DBset requests only a compilation of the NDDL sequence stored on souin-DBset
for purposes of obtaining a listing or a cross reference, and it cannot be modified with the ALTER
statement. See Remark 3. COMPILE NDDL=NDDL SOUIN=MSCSOU LIST requests a
listing of the MSC Nastran NDDL sequence. The ACQUIRE FMS statement or the SOL
statement must be specified in order to attach the corresponding delivery database.
• To alter the MSC Nastran NDDL sequences, the entire modified NDDL sequence is included
after the COMPILE statement, and SOUIN=souin-DBset is not specified.
• SOUOUT=souout-DBset requests the storage of the NDDL source statements on the
souout-DBset, and may not be specified with SOUIN=souin-DBset.
7. The COMPILER statement may be used to override the defaults of NOLIST, NOREF, and
NODECK. In other words, if LIST or NOLIST, REF or NOREF, or DECK or NODECK is not
specified, then the corresponding option on the COMPILER statement will be used. In the following
example, REF on the COMPILER statement will override the default of NOREF on the COMPILE
statement:
COMPILER REF
Main Index
120 COMPILE
Compiles DMAP Statements
COMPILE MYDMAP
8. MSCSOU and MSCOBJ, specified with SOUOUT and OBJOUT, are special DBsets similar to
USRSOU and USROBJ except that they are used in the creation or modification of a delivery
database. For an example application, see the .
Main Index
COMPILER 121
DMAP Compiler Output Options
COMPILER DMAP Compiler Output Options
Requests compilation of a DMAP sequence and/or overrides defaults on the COMPILE statement.
Format:
COMPILER = LIST DECK REF GO SORT
NOLIST NODECK NOREF NOGO NOSORT
Example:
COMPILER=LIST
Describer Meaning
LIST, NOLIST LIST requests the compilation listing of the solution sequence. NOLIST suppresses the
listing.
DECK, DECK requests that the DMAP source statements of the solution sequence be written
NODECK to the PUNCH file. NODECK suppresses the DECK option.
REF, NOREF REF requests a compilation cross reference. NOREF suppresses a compilation cross
reference.
GO, NOGO GO requests the execution of the solution sequence following compilation. NOGO
requests termination following compilation.
SORT, SORT compiles subDMAPs in alphabetical order. NOSORT compiles subDMAPs in
NOSORT calling sequence order.
Remarks:
1. REF is equivalent to DIAG 4. LIST is equivalent to DIAG 14. DECK is equivalent to DIAG 17.
2. NOGO is an alternative to NOEXE on the SOL statement.
3. This statement provides a means of obtaining a compilation or source listing, or both, of a complete
solution sequence, including all the component subDMAPs.
4. See the COMPILE statement to compile a single subDMAP.
5. This statement also requests the automatic link of the solution sequence. Therefore, all objects must
be created in the current run or obtained from the DBset such as USROBJ. See the COMPILE
statement for how to create and store objects.
6. The COMPILER statement may be used to override the defaults of NOLIST, NOREF, NODECK
on the COMPILE entry when they are not explicitly specified. However, COMPILER LIST
produces a list of the entire solution sequence. If a listing of only specific subdmaps is desired, then
COMPILER LIST should not be specified and the LIST request should be made on the COMPILE
entry.
COMPILER REF
COMPILE MYDMAP
Main Index
122 DIAG
Requests Diagnostic Output
DIAG Requests Diagnostic Output
Requests diagnostic output or special options.
Format:
DIAG [=] k1[k2, ..., kn]
Examples:
DIAG 8,53
or
DIAG 8
DIAG 53
Describer Meaning
ki A list separated by commas and/or spaces of desired diagnostics.
Remarks:
1. The DIAG statement is optional.
2. Multiple DIAG statements are allowed.
3. The following table lists the possible values for ki and their corresponding actions:
k=1 Dumps memory when a nonpreface fatal message is generated.
k=2 Prints database directory information before and after each DMAP statement. Prints
bufferpooling information.
k=3 Prints “DATABASE USAGE STATISTICS” after execution of each functional
module. This message is the same as the output that appears after the run terminates.
See the Output Description in the MSC Nastran Reference Guide.
k=4 Prints cross-reference tables for compiled sequences. Equivalent to the COMPILER
REF statement.
k=5 Prints the BEGIN time on the operator’s console for each functional module. See the
Output Description in the MSC Nastran Reference Guide.
k=6 Prints the END time for each functional module in the log file or day file, and on the
operator’s console. Modules that consume less time than the threshold set by
SYSTEM(20) do not create a message. See the Output Description in the MSC Nastran
Reference Guide.
k=7 Prints eigenvalue extraction diagnostics for the complex determinate method.
k=8 Prints matrix trailers as the matrices are generated in the execution summary table.
See the Output Description in the MSC Nastran Reference Guide.
Main Index
DIAG 123
Requests Diagnostic Output
k=9 Prints a message in the .f04 file when EQUIV and EQUIVX perform a successful
equivalence; in other words, both the input and output exists.
k=10 Selects an alternate option for averaging nonlinear loading (NOLINi Bulk Data
entry) in linear transient analysis. Replaces N n + 1 with
Nn + 1 + Nn + Nn – 1 3 .
k=11 DBLOAD, DBUNLOAD, and DBLOCATE diagnostics.
k=12 Prints eigenvalue extraction diagnostics for complex inverse power and complex
Lanczos methods.
k=13 Prints the open core length (the value of REAL). See the Output Description in the MSC
Nastran Reference Guide.
k=14 Prints solution sequence. Equivalent to the COMPILER LIST statement.
k=15 Prints table trailers.
k=16 Traces real inverse power eigenvalue extraction operations
k=17 Punches solution sequences. Equivalent to the COMPILER DECK statement.
k=18 In aeroelastic analysis, prints internal grid points specified on SET2 Bulk Data
entries.
k=19 Prints data for MPYAD and FBS method selection in the execution summary table.
k=20 Similar to DIAG 2 except the output appears in the execution summary table and has
a briefer and more user-friendly format. However, the .f04 file will be quite large if
DIAG 20 is specified with an MSC Nastran solution sequence. A DMAP alter with
DIAGON(20) and DIAGOFF(20) is recommended. DIAG 20 also prints DBMGR,
DBFETCH, and DBSTORE subDMAP diagnostics. See the MSC Nastran DMAP
Programmer’s Guide.
k=21 Prints diagnostics of DBDICT and DBENTRY table.
k=22 EQUIV and EQUIVX module diagnostics.
k=23 Not used.
k=24 Prints files that are left open at the end of a module execution. Also prints DBVIEW
diagnostics.
k=25 Outputs internal plot diagnostics.
k=27 Prints Input File Processor (IFP) table. See the MSC Nastran Programmer’s Manual,
Section 4.5.9.
k=28 Punches the link specification table (XBSBD). The Bulk Data and Case Control
Sections are ignored, and no analysis is performed.
k=29 Process link specification table update. The Bulk Data and Case Control Sections are
ignored, and no analysis is performed.
Main Index
124 DIAG
Requests Diagnostic Output
k=30 In link 1, punches the XSEMii data (i.e., sets ii via DIAG 1 through 15). The Bulk
Data and Case Control Sections are ignored, and no analysis is performed. After link
1, this turns on BUG output. Used also by MATPRN module. See also Remark 5 on
the TSTEP, 2965 Bulk Data entry.
k=31 Prints link specification table and module properties list (MPL) data. The Bulk Data
and Case Control Sections are ignored, and no analysis is performed.
k=32 Prints diagnostics for XSTORE and PVA expansion.
k=33 Not used.
k=34 Turns off plot line optimization.
k=35 Prints diagnostics for 2-D slideline contact analysis in SOLs 106 and 129.
k=37 Disables the superelement congruence test option and ignores User Fatal Messages
4277 and 4278. A better alternative is available with PARAM,CONFAC. See
Parameters, 805.
k=38 Prints material angles for CQUAD4, CQUAD8, CTRIA3, and CTRIA6 elements.
The angle is printed only for elements that use the MCID option of the connection
entry.
k=39 Traces module FA1 operations and aerodynamic splining in SOLs 145 and 146.
k=41 Traces GINO OPEN/CLOSE operations.
k=42 Prints output on .f04 file the usage statistic for datablock defined in the FMS
command, MEMLIST.
k=43 Print output for Buffer Pool Diagnostics.
k=44 Prints a mini-dump for fatal errors and suppresses user message exit.
k=45 Prints the same database directory information as DIAG 2 except that it prints only
after each DMAP statement.
k=46 Used by MSC Nastran development for GINO printout.
k=47 Prints DBMGR, DBFETCH, and DBSTORE subDMAP diagnostics.
k=48 Used by MSC Nastran development for GINO printout.
k=49 DIAG 49 is obsolete and should not be used. The utility f04rprt should be used to
summarize the .f04 execution summary instead.
k=50 Traces the nonlinear solution in SOLs 106, 129, 153, and 159. Prints subcase status;
echoes NLPARM, NLPCI, and entry fields; and prints initial arc-length. Prints
iteration summary only in SOLs 129, and 159.
In static aeroelastic analysis (SOL 144), prints transformation information associated
with the generation of the DJX matrix in the ADG module and intermediate
solutions information in the ASG module.
k=51 Prints intermediate displacement, load error vectors, and additional iteration
information helpful in debugging in SOLs 106, 129, 153, and 159.
k=52 Disables the printing of errors at each time step in SOLs 129 and 159.
Main Index
DIAG 125
Requests Diagnostic Output
k=53 MESSAGE module output will also be printed in the execution summary table. See
the Output Description in the MSC Nastran Reference Guide.
k=54 Linker debug print.
k=55 Performance timing.
k=56 Extended print of execution summary table (prints all DMAP statements and
RESTART deletions). See the Output Description in the MSC Nastran Reference Guide.
k=57 Executive table (XDIRLD) performance timing and last-time-used (LTU)
diagnostics.
k=58 Data block deletion debug and timing constants echo.
k=59 Buffpool debug printout.
k=60 Prints diagnostics for data block cleanup at the end of each module execution in
subroutines DBCLN, DBEADD, and DBERPL.
k=61 GINO block allocator diagnostics.
k=62 GINO block manager diagnostics.
k=63 Prints each item checked by the RESTART module and its NDDL description.
Main Index
126 DOMAINSOLVER
Domain Decomposition Solution Method
DOMAINSOLVER Domain Decomposition Solution Method
Selects domain decomposition solution methods.
Format:
STAT
MODES
FREQ DOF
DOMAINSOLVER ACMS
PARTOPT = GRID ,NUMDOM = int
DSA
FREQ
NLSOLV ELEM
STATRED
SUPER
YES
UPFACT = real , PRINT = NCLUST = int CLUSTSZ = int COMPMETH = GRID ,
NO
NONE
BEND
FLUID
PARCHILD MSCMLV
MODEL = STRUCT RUNOPT = , PARTMETH = TIPSIZE = int,
MULTIPAR METISG
BOTH
METISO
0
NEW STATIC DIRECT
VERSION = SCHED = ,GRPSIZ = N , REDOPT=
OLD DYNAMIC AMSR
–1
MINDOF=int, XFACT=real, XFACTX=real
Examples:
DOMAINSOLVER STAT (PARTOPT=DOF)
DOMAINSOLVER ACMS (UPFACT=3.0,NUMDOM=128)
DOMAINSOLVER DSA
DOMAINSOLVER STAT, NLSOLV
DOMAINSOLVER ACMS (PARTMETH=BEND, NUMDOM=128)
DOMAINSOLVER ACMS (PARTMETH=METISO, TIPSIZE=500)
DOMAINSOLVER STAT (PARTMETH=MSCMLV)
DOMAINSOLVER ACMS (VERSION=NEW) - default
DOMAINSOLVER ACMS (VERSION=OLD)
DOMAINSOLVER ACMS (MODEL=STRUCT, UPFACT=5.0)
DOMAINSOLVER STATRED (REDOPT=AMSR)
The keywords function as follows:
Main Index
DOMAINSOLVER 127
Domain Decomposition Solution Method
STAT Linear statics.
MODES Normal modes or buckling.
FREQ Frequency response.
ACMS Automated component modal synthesis.
DSA Design sensitivity analysis. (See Remark 2.)
NLSOLV Nonlinear analysis
STATRED Static Reduction
The descriptions of the parameters are as follows:
PARTOPT Partitioning option. Selects which domain is to be decomposed.
DOF Degree of freedom domain.
GRID Grid point (geometric) domain.
FREQ Frequency domain.
ELEM Finite element domain.
The default is dependent upon solution sequence. See Table 4-1 for further
descriptions.
Note that ACMS (VERSION=NEW) requires PARTOPT=DOF. If it is not set by
the user, ACMS will use it automatically. However, if the user specifies a different
value for PARTOPT, for example, ACMS (VERSION=NEW, PARTOPT=GRID),
then MSC Nastran will execute old ACMS rather than new ACMS.
NUMDOM Selects the number of domains as follows:
(ACMS) If NUMDOM = 0 or 1, then the model will not be split. Default depends on the
model size and the value of PARTOPT.
NUMDOM will be ignored for ACMS (VERSION=NEW); instead of the number
of domains, new ACMS uses the size of the tip domains being specified via TIPSIZE
(see below).
NUMDOM Default = dmp; if NUMDOM has any other value, it will automatically be set to dmp
(STAT) (equal to the number of processors used for the run). The model will be divided into
NUMDOM domains in either the geometric (grid-based) or DOF domains,
depending on the value of PARTOPT.
NUMDOM Default = dmp; if NUMDOM has any other value, it will be reset to dmp (equal to
(MODES) the number of processors used for the run). The model will be divided into
NUMDOM domains in either the frequency, geometric (grid-based) or DOF
domains, depending on the value of PARTOPT.
Main Index
128 DOMAINSOLVER
Domain Decomposition Solution Method
NUMDOM Default = dmp; if NUMDOM has any other value, it will automatically be set to dmp
(FREQ) (equal to the number of processors used for the run). The frequency range will be
divided into NUMDOM regions which are then solved independently.
UPFACT By default, the frequency range used for upstream component modes is two times
(ACMS) larger than the desired range on the EIGR/L entry. To modify this factor, specify the
UPFACT parameter (Real; Default=2.0 for STRUCT and 5.0 for FLUID).
PRINT Controls intermediate print of upstream and data recovery processing in .f06 and .f04
(ACMS) files. Default=‘NO’. If PRINT=NO and an error occurs upstream, the intermediate
output is placed in a separate output file named “jid.acms_out” for examination.
NCLUST Specifies the number of frequency segments for hierarchic parallel Lanczos. The
(MODES) frequency range is divided into NLCUST segments and, if PARTOPT=DOF, the
stiffness and mass matrices are partitioned into dmp/NCLUST matrix domains. If
PARTOPT = GRID, or if PARTOPT is not specified, the model geometry is
partitioned into dmp/NCLUST domains.
CLUSTSZ Specifies the number of matrix or geometric domains for hierarchic parallel Lanczos.
(MODES) If PARTOPT=DOF, the stiffness and mass matrices are partitioned into CLUSTSZ
matrix domains. If PARTOPT = GRID, or if PARTOPT is not specified, the model
geometry is partitioned into CLUSTSZ domains. In either case, the frequency range
is divided into dmp/CLUSTSZ frequency segments.
MODEL Default=BOTH. Model specification to which ACMS parameters are applied.
(ACMS) MODEL can be STRUCT or FLUID, or BOTH. For MODEL=BOTH (default),
the specified options apply to both structure and fluid models
MINDOF Default for STRUCT is 65. Default for FLUID is 250,000. MINDOF is the
(ACMS) minimum number of degrees of freedom below which ACMS will not execute. If the
number of DOF in the structural model is less than MINDOF
(MODEL=STRUCT), a Fatal error is issued. If the number of fluid DOF is less than
MINDOF. (MODEL=FLUID), a Warning message is issued, and the fluid
eigensolution is computed with Lanczos. PARAM,MDMINDOF applies only to the
structural model and will override this DOMAINSOLVER entry.
PARAM,MDMINDOF will be deprecated in a future release.
XFACT Default=0.5 for both STRUCT and FLUID. XFACT is used in the ACMS1 module
(ACMS) to determine a threshold for reorthogonalization of component eigenvectors. Valid
values are from 0.1 to 1.0. This option should be used only for very special
conditions.
XFACTX Default=1.0 for both STRUCT and FLUID. XFACTX is used in the ACMS1
(ACMS) module to define the maximum frequency range for internal reorthogonalization
operations. Valid values are from 0.1 to 1.0. This options should be used only for very
special conditions.
Main Index
DOMAINSOLVER 129
Domain Decomposition Solution Method
COMPMETH Specifies the compression method used before domain decomposition.
COMPMETH is considered only for keywords STAT, MODES and ACMS with
PARTOPT = DOF, for all other settings of the keyword and parameter PARTOPT,
COMPMETH will be ignored. The following are valid options for COMPMETH:
SUPER Specifies the SUPER compression method. (Default)
GRID Specifies the GRID compression method.
(Default for ACMS version=NEW for structure A-set.)
NONE Specifies that no compression should be done.
RUNOPT Specifies the DMP run option. The following are valid options for RUNOPT:
PARCHILD Specifies "parent-child" DMP execution mode. Only the Parent
DMP process executes the full Nastran solution. This is optimal for
single-host DMP execution.
MULTIPAR Specifies "multiple-parent" DMP execution mode. All DMP
processes execute the full Nastran solution. This is optimal for
multiple-host DMP execution.
Nastran detects single- and multiple-host DMP execution and sets the default run
option accordingly.
PARTMETH Partitioning option (characher string). PARTMETH selects which method is used for
domain decomposition.
BEND Specifies the Extreme/BEND partitioning method
MSCMLV Specifies the MSCMLV partitioning method
METISG Specifies the METIS partitioning method based on number of tip
domains requested (see NUMDOM above)
METISO Specifies the METIS partitioning method based on the desired tip size
(see TIPSIZE below). Available for ACMS only.
Note: NUMDOM (see above) will be ignored for
PARTMETH=METISO.
Note: ACMS (VERSION=NEW) requires PARTMETH=METISO.
If this is not set by the user, ACMS will use it automatically. If the user
sets a different value for PARTMETH when ACMS
(VERSION=NEW) is also specified, then the MSC Nastran will
automatically re-set PARTMETH to METISO and run with new
ACMS.
TIPSIZE Specifies a desired number of nodes in the tip domains (integer). ACMS only. This is
used only when PARTMETH=METISO; otherwise, it is ignored.
Default: 1000 (ACMS Version=OLD);
200 (ACMS Version=NEW)
Main Index
130 DOMAINSOLVER
Domain Decomposition Solution Method
VERSION Selects new ACMS (MSC Nastran Version 2017 +) or old ACMS (prior to MSC
Nastran Version 2017). The default value of VERSION is ‘NEW’.
SCHED For ACMS parallel scheduling with VERSION=NEW. Default is DYNAMIC, which
is generally more efficient. Select STATIC for static parallel scheduling. See Remark 7.
GRPSIZ Specifies parallel group size for ACMS Dynamic scheduling. Integer:
0 Default
N Set parallel group size to “N” SMP threads.
-1 Use single parallel group; number of threads in the group is NSMP
(Number of SMP).
REDOPT Reduction Option. Specifies how to perform static reduction for External SE and
(STATRED) Modules. Default is DIRECT. Specify AMSR for the Automatic Multilevel Static
Reduction method.
Main Index
DOMAINSOLVER 131
Domain Decomposition Solution Method
Table 4-1 Analysis Types vs Supported Partitioning Methods
Partitioning Methods Available
Solution
Sequence DMP Method GRID DOF FREQ DOF+FREQ ELEM
101 STAT * *
MODES * * *
103
ACMS(OLD) * *
ACMS(NEW) *
105 MODES * *
108 FREQ *
MODES *
110
ACMS *
MODES * *
ACMS(OLD) * * * *
111
ACMS(NEW) *
FREQ *
MODES *
112
ACMS *
MODES * * *
ACMS * * *
200
FREQ *
DSA
400 STAT *
NLSOLV *
ACMS *
* - means “supported”.
The DOMAINSOLVER command is optional. If “dmp=” is specified on the command without a
DOMAINSOLVER command in the Executive Control Section, the actions shown in Table 4-2 will result
based on solution sequence.
Main Index
132 DOMAINSOLVER
Domain Decomposition Solution Method
Table 4-2 DOMAINSOLVER Defaults with “dmp=” on command line
Default DOMAINSOLVER Options
Solution Sequence DMP Method Partitioning Option
101 STAT DOF
103 MODES DOF
105 MODES DOF
108 FREQ FREQ
110 MODES FREQ
MODES FREQ
111
FREQ FREQ
112 MODES FREQ
MODES DOF
200
FREQ FREQ
400 STAT DOF
NLSOLV ELEM
Note that DOMAINSOLVER ACMS is not the default for the relevant solution sequences, but it is the
recommended option for larger models for SOL 103, 111, 112, and 200 to obtain the best performance.
Remarks:
1. Grid Point Weight Generator output selected by PARAM,GRDPNT or the WEIGHTCHECK Case
Control command is not available when PARTOPT=GRID.
2. In SOL 200, design sensitivity calculations may be performed in a distributed parallel environment
in SOL 200 with the DSA keyword. It is a coarse parallel implementation that divides the sensitivity
task across a number of processors so that each processes a subset of the total number of design
variables. Following the sensitivity analysis and before optimization, the separate sensitivity data are
appended into a global sensitivity set. Also,
a. The dmp=n keyword must be specified on the Nastran submittal command where n is the
number of available processors.
b. The ACMS keyword may also be specified or modified along with DSA. For example,
DOMAINSOLVER DSA, ACMS
3. In SOL 400, the STAT method is used for DMP parallelism of matrix factorization and the NLSOLV
method is used for DMP parallelism of the NLEMG process. The NLSOLV method is intended for
nonlinear analysis using advanced nonlinear methods. To only use the STAT method or to change
its option to use, for example, a different compression method, specify the following
DOMAINSOLVER command:
DOMAINSOLVER STAT(COMPMETH=GRID)
Main Index
DOMAINSOLVER 133
Domain Decomposition Solution Method
Note that if STAT is changed as specified above, then the DMP parallelism for NLEMG will be
turned off. If you want to change the STAT as described above and also keep NLSOLV for NLEMG
parallelism, then use the following DOMAINSOLVER command:
DOMAINSOLVER NLSOLV,STAT(COMPMETH=GRID)
Note that this can equivalently be written as follows:
DOMAINSOLVER NLSOLV
DOMAINSOLVER STAT(COMPMETH=GRID)
Lastly, to only use the NLSOLV method for NLEMG parallelism, specify the following option:
DOMAINSOLVER NLSOLV
4. In SOL 400, the DOMAINSOLVER NLSOLV (RUNOPT=MULTIPAR) is not supported in
combination with Intel MKL Pardiso Solver option, i.e., SPARSESOLVER
NLSOLV(FACTMETH=PRDLDL).
5. In SOL 111, the MODES or ACMS option is used for DMP parallelism of the modal calculations
and the FREQ option is used for the DMP parallelism of the frequency response calculations. The
DOMAINSOLVER FREQ is always turned on for SOL 111. To use the ACMS option for the modal
calculation, use the following DOMAINSOLVER command:
DOMAINSOLVER ACMS
Furthermore, if the MODES option needs to be changed for SOL 111, then the correct approach is
to include the following DOMAINSOLVER option:
DOMAINSOLVER MODES(PARTOPT=GRID).
6. Residual vectors are not available when PARTOPT=GRID.
7. Dynamic parallel scheduling is available for ACMS and VERSION=NEW. Dynamic scheduling
provides better parallel speedup for larger numbers of threads. For NSMP less than or equal to 2,
static scheduling is used regardless of the setting of SCHED.
8. DMP processing for buckling (solution sequence 105) with PARTOPT=DOF is only available when
the MUMPS solver is specified using the SPARSESOLVER executive control statement:
SPARSESOLVER READ (FACTMETH=MUMPS)
Main Index
134 ECHO
Controls Printed Echo
ECHO Controls Printed Echo
Controls the echo (printout) of the Executive Control Section.
Formats:
ECHOOFF
ECHOON
Remarks:
1. The ECHO statement is optional.
2. ECHOOFF suppresses the echo of subsequent Executive Control statements. ECHOON reactivates
the echo after an ECHOOFF statement.
Main Index
ENDALTER 135
End of DMAP Alter
ENDALTER End of DMAP Alter
Designates the end of an alter.
Format:
ENDALTER
Remark:
1. The ENDALTER statement is required when using an alter unless the alter package ends with a
CEND, COMPILE, or LINK statement.
Main Index
136 GEOMCHECK
Specifies Geometry Check Options
GEOMCHECK Specifies Geometry Check Options
Specifies tolerance values and options for optional finite element geometry tests.
Format:
FATAL
GEOMCHECK test_keyword = tol_value MSGLIMIT = n MSGTYPE = INFORM
WARN
SUMMARY ADVNLELM NONE
Examples:
1. Set the tolerance for the CQUAD4 element skew angle test to 15.0 degrees and limit messages to 50:
GEOMCHECK Q4_SKEW=15.0,MSGLIMIT=50
2. Limit messages to 500 for each element type:
GEOMCHECK MSGLIMIT=500
3. Set the message type to fatal for CQUAD4 element taper tests:
GEOMCHECK Q4_TAPER,MSGTYPE=FATAL
4. Request summary table output only using default tolerance values:
GEOMCHECK SUMMARY
5. Request advanced and conventional element geometry check output using default tolerance values:
GEOMCHECK ADVNLELM
Describer Meaning
test_keyword A keyword associated with the particular element geometry test. See Remark 2. for a list
of acceptable selections.
tol_value Tolerance value to be used for the specified test. See Remark 2. for default values of the
test tolerances.
n The minimum number of messages that will be produced. The default is 100 messages
for each element type. See Remark 3.
FATAL Geometry tests that exceed tolerance values produce fatal messages. See Remark 4.
INFORM Geometry tests that exceed tolerance values produce informative messages. See Remark 4.
WARN Geometry tests that exceed tolerance values produce warning messages. See Remark 4.
SUMMARY A summary table of the geometry tests performed is produced. No individual element
information messages are output.
ADVNLELM Geometry check performed on Advanced and conventional elements. If no
ADVNLELM, geometry check only performed on conventional element.
NONE None of the optional element geometry tests will be performed.
Main Index
GEOMCHECK 137
Specifies Geometry Check Options
Remarks:
1. The GEOMCHECK statement controls the number and severity of certain informational and
warning messages produced by element matrix generation geometry checking operations. Controls
are currently available for the CQUAD4, CQUADR, CTRIA3, CTRIAR, CHEXA, CPENTA,
CTETRA, CPYRAM, CBAR, and CBEAM elements only. Multiple GEOMCHECK statement may
be present. Continuations are acceptable.
2. The following table summarizes the acceptable specifications for test_keyword.
Name Value Type Default Comment
Q4_SKEW Real > 0.0 30.0 Skew angle in degrees.
Q4_TAPER Real > 0.0 0.50 Taper ratio.
Q4_WARP Real > 0.0 0.05 Surface warping factor.
Q4_IAMIN Real > 0.0 30.0 Minimum interior angle in degrees.
Q4_IAMAX Real > 0.0 150.0 Maximum interior angle in degrees.
T3_SKEW Real > 0.0 10.0 Skew angle in degrees.
T3_IAMAX Real > 0.0 160.0 Maximum interior angle in degrees.
TET_AR Real > 0.0 100.0 Longest edge to shortest edge aspect ratio.
TET_EPLR Real > 0.0 0.50 Edge point length ratio.
TET_EPIA Real > 0.0 150.0 Edge point included angle in degrees.
TET_DETJ Real 0.0 | J | minimum value.
TET_DETG Real 0.0 | J | minimum value at vertex point.
HEX_AR Real > 0.0 100.0 Longest edge to shortest edge aspect ratio.
HEX_EPLR Real > 0.0 0.50 Edge point length ratio.
HEX_EPIA Real > 0.0 150.0 Edge Point Included Angle in degrees.
HEX_DETJ Real 0.0 | J | minimum value.
HEX_WARP Real > 0.0 0.707 Face warp coefficient.
PEN_AR Real > 0.0 100.0 Longest edge to shortest edge aspect ratio.
PEN_EPLR Real > 0.0 0.50 Edge point length ratio.
PEN_EPIA Real > 0.0 150.0 Edge point included angle in degrees.
PEN_DETJ Real 0.0 | J | minimum value.
PEN_WARP Real > 0.0 0.707 Quadrilateral face warp coefficient.
PYR_AR Real > 0.0 100.0 Longest edge to shortest edge aspect ratio.
PYR_EPLR Real > 0.0 0.50 Edge point length ratio.
PYR_EPIA Real > 0.0 150.0 Edge point included angle in degrees.
Main Index
138 GEOMCHECK
Specifies Geometry Check Options
Name Value Type Default Comment
PYR_DETJ Real 0.0 | J | minimum value.
PYR_WARP Real > 0.0 0.707 Quadrilateral face warp coefficient.
BEAM_OFF Real > 0.0 0.15 CBEAM element offset length ratio.
BAR_OFF Real > 0.0 0.15 CBAR element offset length ratio.
where:
• Test_keyword names starting with the characters Q4 are applicable to CQUAD4 and CQUADR
elements. Test_keyword names starting with the characters T3 are applicable to CTRIA3 and
CTRIAR elements. Test_keyword names starting with the characters TET_ are applicable to
CTETRA elements. Test_keyword names starting with the characters HEX_ are applicable to
CHEXA elements. Test_keyword names starting with the characters PEN_ are applicable to
CPENTA elements. Test_keyword names starting with the characters PYR_ are applicable to
CPYRAM elements.
• Skew angle for the quadrilateral element is defined to be the angle between the lines that join
midpoints of the opposite sides of the quadrilateral. Skew angle for the triangular element is
defined to be the smallest angle at any of the three vertices.
• Interior angles are defined to be the angles formed by the edges that meet at the corner node of
an element. There are four for quadrilateral shapes and three for triangular shapes.
• Taper ratio for the quadrilateral element is defined to be the absolute value of [the ratio of the area
of the triangle formed at each corner grid point to one half the area of the quadrilateral minus 1.0.
The largest of the four ratios is compared against the tolerance value. Note that as the ratio
approaches 0.0, the shape approaches a rectangle.
• Surface warping factor for a quadrilateral is defined to be the distance of the corner points of the
element to the mean plane of the grid points divided by the average of the element diagonal
lengths. For flat elements (such that all of the grid points lie in a plane), this factor is zero.
• The edge point length ratio and edge point included angle tests are only performed for the solid
elements when edge node points exist. The length ratio test evaluates the relative position of the
edge node point along a straight line connecting the two vertex nodes of that edge. Ideally, the
edge point should be located on this line at a point midway between the two end points. The
default tolerance allows the edge node to be positioned anywhere between the two quarter points
on this line. In addition, the angle between the lines joining the edge node and the end points is
determined. If the angle is less than the tolerance (default is 150 ), then the interior angle test is
considered violated and a diagnostic message will be generated if appropriate.
• The face warp coefficient test tolerance is the cosine of the angle formed between the normal
vectors located at diagonally opposite corner points on each face surface. This value is 1.0 for a
face where all four corners lie in a plane. The default tolerance allows angles of up to 45 before
a message is generated.
Main Index
GEOMCHECK 139
Specifies Geometry Check Options
3. A single line of output summarizing the results of all tests for an element will be output if any of the
geometry tests exceeds the test tolerance. Only the first n of these messages will be produced. A
summary of the test results indicating the number of tolerances exceeded, as well as the element
producing the worst violation, is also output. If the SUMMARY keyword has been specified, only the
summary table is produced and none of the single line element messages will be output.
4. When SUMMARY is not specified, each geometry test that exceeds the tolerance will be identified in
the single line output summary by an indicator based on the specification for MSGTYPE. For the
FATAL option, the indicator is “FAIL”; for the INFORM option, it is “xxxx”; for the WARN option,
it is “WARN”. If the FATAL option is specified and any test fails, the run is terminated.
5. GEOMCHECK does not apply on PEM elements which appear under BEGIN BULK
TRMC=trimid.
Main Index
140 ID
Comment
ID Comment
Specifies a comment.
Format:
ID [=] i1, i2
Describer Meaning
i1, i2 Character strings (1 to 8 characters in length and the first character must be
alphabetic).
Remark:
1. The ID statement is optional and not used by the program.
Main Index
INCLUDE 141
Inserts External File
INCLUDE Inserts External File
Inserts an external file into the input file. The INCLUDE statement may appear anywhere within the input
data file.
Format:
INCLUDE ’filename’
Example:
The following INCLUDE statement is used to obtain the bulk data from another file called
MYEXEC.DATA:
SOL 101
INCLUDE ’MYEXEC.DATA’
CEND
TITLE = STATIC ANALYSIS
LOAD = 100
BEGIN BULK
ENDDATA
Describer Meaning
filename Physical filename of the external file to be inserted. The user must supply the name
according to installation or machine requirements. It is recommended that the
filename be enclosed by single right-hand quotation marks (’).
Remarks:
1. INCLUDE statements may be nested; that is, INCLUDE statements may appear inside the external
file. The nested depth level must not be greater than 10.
2. The total length of any line in an INCLUDE statement must not exceed 72 characters. Long file
names may be split across multiple lines. For example, the file
/dir123/dir456/dir789/filename.dat
may be included with the following input:
INCLUDE ‘/dir123
/dir456
/dir789/filename.dat’
3. See the for more examples.
Main Index
142 LINK
Links a Main SubDMAP
LINK Links a Main SubDMAP
Links a main subDMAP to form a solution sequence.
Format:
n
LINK SOLOUT = solout-DBset EXECOUT - exeout-DBset,
subDMAP-name
INCLUDE - incl-DBset MAP SOLNAME = newname
NOMAP
Examples:
1. LINK STATICS
Links the STATICS main subDMAP. The program links any subDMAPs compiled in this run, with
any other subDMAP objects called in STATICS and stored on the MSCOBJ DBset.
2. LINK MYDMAP,SOLNAM=STATICS,SOLOUT=USROBJ, NOMAP,INCLUDE=USROBJ
Links MYDMAP and renames the solution sequence executable to STATICS. The executable will
be saved on the USROBJ DBset. The order of search for subDMAP objects is:
• Compiled subDMAP in this run.
• USROBJ DBset.
Describer Meaning
n The solution number of the main subDMAP. See the SOL statement
description for the list of valid numbers (Integer > 0).
subDMAP-name The name of a main subDMAP. See the MSC Nastran DMAP Programmer’s Guide
(Character; 1 to 8 alphanumeric characters in length and the first character
must be alphabetic).
solout-DBset The name of a DBset where the solution sequence executable and the link
table of the solution sequence may be stored. See Remark 6. (Character; 1
to 8 alphanumeric characters in length and the first character must be
alphabetic).
exeout-DBset The name of an alternate DBset different than solout-DBset where only the
solution sequence executable may be stored. See Remark 6. (Character; 1 to
8 alphanumeric characters in length and the first character must be
alphabetic).
incl-DBset The name of a DBset where other subDMAP objects are obtained. See
Remark 2. (Character; 1 to 8 alphanumeric characters in length and the first
character must be alphabetic).
Main Index
LINK 143
Links a Main SubDMAP
Describer Meaning
newname A new name which is referenced by the SOL statement. (Character; 1 to 8
alphanumeric characters in length and the first character must be
alphabetic; default is subDMAP-name.)
MAP Prints the link map. A link map will give the name of all the subDMAPs that
make up the solution sequence.
NOMAP Suppresses printing of the link map.
Remarks:
1. All DBsets specified on this statement must have the same BUFFSIZE. See the INIT, 100 FMS
statement.
2. SubDMAP objects are created with the COMPILE statement either in the current run or obtained
from previous runs. The LINK statement collects objects in the following order:
• Objects created with the COMPILE statement in the current run.
• Objects residing on the DBset-name specified by the INCLUDE keyword. The default is
MSCOBJ.
3. Upon successful linking of a subDMAP, the subDMAP may be executed with the SOL statement.
4. The LINK statement must appear after all the COMPILE packages, if any. A compile package begins
with the COMPILE statement and is delimited by the ENDALTER, CEND, LINK, or another
COMPILE statement.
5. The link table is necessary for COMPILER (or DIAG 4, 14, 17) Executive Control statement
requests and the automatic link process.
6. EXEOUT is useful in building delivery databases where executables are not to be saved. EXEOUT
will be defaulted to the same DBset as specified by SOLOUT.
Main Index
144 MALTER
Inserts and/or Deletes DMAP Statements in Solution Sequences
MALTER Inserts and/or Deletes DMAP Statements in Solution Sequences
Inserts or deletes DMAP statements by allowing a global “string” search across all subDMAPs within the
current solution sequence.
Format:
MALTER ‘string1’[(occurrence,offset)] , [‘string2’[(occurrence,offset)] ]
or
MALTER ’string1’[(occurrence,offset)] , [k2]
Examples:
1. The following MALTER will insert a MATPRN DMAP statement to print the KJJ matrix for each
superelement.
SOL 101
MALTER ’MALTER:AFTER SUPERELEMENT STIFFNESS .* GENERATION’
MESSAGE //’SEID=’/SEID $
MATPRN KJJZ/ $
2. The following MALTER will add a user DMAP after the PREFACE modules in SOL 100
(USERDMAP).
SOL 101
MALTER ’AFTER CALL PREFACE’
.
.
.
Describer Meaning
’string1’ If ‘string2’ or k2 is not specified, the subsequent DMAP statements will be
inserted after the first occurrence of ‘string1’.
’string1’,’string2’ DMAP statements beginning with the first occurrence of ‘string1’ through
DMAP statements containing the first occurrence of ’string2’ will be deleted and
may be replaced with subsequence DMAP statements.
k2 If k2 is specified, it is applied to the subDMAP in which ‘string1’ was found
(Integer > 0).
occurrence This flag indicates which occurrence of the preceding string is to be used, starting
at the beginning of the subDMAP (Integer > 0; Default=1).
offset This flag indicates the offset from the referenced DMAP statement. Depending
on the sign, the specific DMAP statement may be above (-offset) or below
(+offset) the referenced DMAP statement (Integer; Default = 0).
Main Index
MALTER 145
Inserts and/or Deletes DMAP Statements in Solution Sequences
Remarks:
1. If an MALTER statement is used in conjunction with the ALTER statement, then the MALTER
should be placed above the COMPILE statements. Failure to place the MALTER in this position may
cause ALTER statements to be ignored.
2. The MALTER statement can reference the DMAP statements in any order within a subDMAP. Two
restrictions on ordering are:
• K2 or ’string2’(occurence,offset) references must refer to a DMAP line number that is greater than
or equal to the k1 or ’string1’(occurrence,offset) reference within a single MALTER statement.
• ’string1’ and k2 or ’string2’ cannot overlap DMAP line positions with another MALTER that
references the same subDMAP.
3. The ’string1’ or ’string2’ used as a search pattern will apply to one complete DMAP statement; i.e., a
multiline DMAP statement will be searched for a pattern match as if each 72 character line of the
DMAP statement were concatenated together into one string; all blanks and comments (either
embedded or immediately preceding the DMAP statement) will be retained.
4. The special characters used for string searching are described in Remark 9. The characters <, >, and
$, which are common DMAP characters, are also special metacharacters. If they are to be used in the
search string as regular characters, then they must be preceded by a backward slash (\). For example,
to find the string
IF (DDRMM >=-1)
the command is
ALTER ’IF (DDRMM \>=-1)’ $
5. ’string2’ (r2,02) can be defaulted to ’string1’ (r1,01) by using a null string (’’). For example, the alter
statement
MALTER ’string1’(r1,01),’’
is equivalent to
MALTER ’string1’(r1,01),’string1’(r1,01)
The defaults for (r2,02) using the null string can be overridden by specifying (r2,02).
As another example, the alter statement
MALTER ’string1’(r1,01),’’(r2,02)
is equivalent to
MALTER ’string1’(r1,01),’string1’(r2,02)
6. The existing COMPILE statement options, such as LIST, XREF, SOUIN, etc., cannot be directly
specified on the new MALTER statement. They are obtained as follows:
• If a COMPILE statement exists for the subDMAP referenced by the MALTER, then options
from this COMPILE statement will be used.
Otherwise, they will be taken from the COMPILER statement, with the exception that the LIST,
and SORT option is always on.
Main Index
146 MALTER
Inserts and/or Deletes DMAP Statements in Solution Sequences
7. The MALTER string search order is as follows:
• All COMPILE statement references that are part of the existing solution sequence (i.e., SOL=)
are searched first.
• Then, all remaining subDMAPs in the solution sequence are searched in ascending alphabetical
order.
• Within a subDMAP, both ’string1’ and ’string2’ will be used to search for a pattern match starting
at the beginning of the subDMAP (not at the current position of the last string match).
8. The MALTER statement must not exceed 72 characters (no continuations are allowed).
9. Metacharacters:
. Matches any single character except newline.
* Matches any number (including zero) of the single character (including a
character specified by a regular expression) that immediately precedes it. For
example, since “.” (dot) means any character, “.*” means “match any number of
characters.”
[...] Matches any one of the characters enclosed between the brackets. For example,
or< > “[AB]” matches either “A” or “B”. A range of consecutive characters can be
specified by separating the first and last characters in the range with a hyphen.
For example “[A-Z]” will match any uppercase letter from A to Z and “[0-9]”
will match any digit from 0 to 9. Some metacharacters lose special meaning
inside brackets. A circumflex (^) as the first character in the bracket tries to
match any one character not in the list.
^ or ! Requires that the following regular expression be found at the beginning of the
or . line.
$ Requires that the preceding regular expression be found at the end of the line.
\ Treats the following special character as an ordinary character. For example “\.”
stands for a period and “\*” for an asterisk. Also, to search for a tic (’), the search
string must be “\’”.
’ Marks the beginning and end of a pattern to be matched.
Note: Nonportable characters such as [ ] and ^ should be replaced (e.g., ^ ! and
[ ] < > ) if portability is required. However, all the preceding characters are
recognized by MSC Nastran.
10. Labels for use with the MALTER have been included in the solution sequences. See Table 1. These
labels will be maintained in future versions and it is strongly suggested that alters which use the
MALTER command take advantage of the unique MALTER labels. Use of the MALTER labels will
significantly reduce the time required to convert alters between versions.
Main Index
MALTER 147
Inserts and/or Deletes DMAP Statements in Solution Sequences
Table 1 DMAP Labels and Corresponding SubDMAP Positions
DMAP MALTER Labels
$MALTER:AFTER PREFACE MODULES
$MALTER:TOP OF PHASE 1 SUPERELEMENT LOOP, AFTER PARAMETERS AND
QUALIFIERS SET
$MALTER:AFTER SUPERELEMENT STIFFNESS, VISCOUS DAMPING, MASS,
AND ELEMENT STRUCTURAL DAMPING GENERATION (KJJZ, BJJZ, MJJZ,
K4JJ)
$MALTER:AFTER X2JJ MATRICES READ (K2JJ, M2JJ, B2JJ)
$MALTER:AFTER TOTAL SUPERELEMENT STIFFNESS, VISCOUS DAMPING,
AND MASS FORMULATED, STRUCTURAL + DIRECT INPUT
$MALTER:AFTER SUPERELEMENT LOAD GENERATION (PJ)
$MALTER:AFTER UPSTREAM SUPERELEMENT MATRIX AND LOAD ASSEMBLY
(KGG, BGG, MGG, K4GG, PG)
$MALTER:AFTER SUPERELEMENT MATRIX AND LOAD REDUCTION TO A-SET,
STATIC AND DYNAMIC (KAA, KLAA, MAA, MLAA, BAA, K4AA, PA)
$MALTER:BOTTOM OF PHASE 1 SUPERELEMENT LOOP
$MALTER:AFTER X2PP MATRICES READ (K2PP, M2PP, B2PP)
$MALTER:AFTER SUPERELEMENT DISPLACEMENT RECOVERY (UG)
$MALTER:AFTER ELEMENT STRESS, STRAIN, ETC. DATA RECOVERY, SORT1
(OUGV1, OES1, OEF1, ETC.)
$MALTER:AFTER ELEMENT STRESS, STRAIN, ETC. DATA RECOVERY, SORT2
(OUGV2, OES2, OEF2, ETC.)
$MALTER:BOTTOM OF SUPERELEMENT DATA RECOVERY LOOP
$MALTER:USERDMAP - AFTER CALL PREFACE
Main Index
148 MODEL_CHECK
Specifies Model Check Options
MODEL_CHECK Specifies Model Check Options
Specifies model checkout run and specifies options to be used.
Format:
OFF
OFF
MODEL_CHECK MAT_DENSITY =
MAT_TECO = ,
DEFAULT DEFAULT
OFF OFF
MAT_TEIJ = ij MAT_DAMPING = ge ,
DEFAULT DEFAULT
CHECKOUT PRINT = item_list
Examples:
1. Execute a basic model checkout run. No special output is required.
MODEL_CHECK CHECKOUT
2. Execute a model checkout run. Print coordinate system and basic grid point data.
MODEL_CHECK CHECKOUT PRINT=(CSTM,BGPDT)
3. Execute a full solution. Modify the material density temporarily to a value of 0.0.
MODEL_CHECK MAT_DENSITY=OFF
or
MODEL_CHECK MAT_DENSITY=0.0
4. Execute a full solution. Temporarily modify the values for material density and thermal expansion
coefficient.
MODEL_CHECK MAT_DENSITY=0.001 MAT_TECO=1.0 MAT_TEIJ=0.0
Describer Meaning
MAT_DENSITY Selects material density processing option.
Value to be used for the density.
MAT_TECO Selects material thermal expansion direct coefficient processing option.
Value to be used for the thermal expansion direct coefficients.
MAT_TEIJ Selects material thermal expansion shear coefficient processing option.
ij Value to be used for the thermal expansion shear coefficients.
Main Index
MODEL_CHECK 149
Specifies Model Check Options
Describer Meaning
MAT_DAMPING Selects material structural element damping processing option.
ge Value to be used for the structural element damping coefficient.
OFF Sets material property value to zero.
DEFAULT Material property value is set to system default value. See Remark 3.
CHECKOUT Selects model checkout solution option. See Remark 5.
PRINT Selects items to be printed during model checkout solution.
item_list List of model data items to be printed during model checkout run. If more than
one item is specified, enclose the list in parenthesis. See Remark 6.
Remarks:
1. The MODEL_CHECK statement is ignored in RESTART runs.
2. The values specified for material properties using the MODEL_CHECK statement will be used to
temporarily update data for all MAT1, MAT2, MAT3, MAT8, and MAT9 Bulk Data entries only
for the duration of the run. These values do not replace data specified on the MATi Bulk Data
entries. Caution should be used when postprocessing results via the PARAM POST options since
operations using inconsistent data could be performed. Furthermore, when layered composite
element properties and materials (PSHELL and MAT2 MID1/MID2/MID3/MID4) are generated,
these equivalent MAT2 property entries are not considered to be original input data and the effects
of the MODEL_CHECK directives are permanently reflected in these MAT2 properties. Restarts
should not be attempted in this case.
3. System default values of 0.0 have been defined for each of the properties. The defaults can be changed
using the following Nastran statement keywords: DEF_DENS for MAT_DENSITY, DEF_TECO
for MAT_TECO, DEF_TEIJ for MAT_TEIJ, and DEF_DAMP for MAT_DAMPING.
4. The MAT_TECO describer causes the direct components of the thermal expansion coefficient to be
modified. The MAT_TEIJ describer causes the shear components of the thermal expansion
coefficient to be modified.
5. The CHECKOUT option has the same effect as a PARAM,CHECKOUT,YES Bulk Data entry.
6. The following table summarizes the acceptable specifications for the PRINT item_list.
Value Output Generated Parameter
CSTM Coordinate systems PRTCSTM
BGPDT Basic grid point data PRTBGPDT
GPTT Grid point temperature data PRTGPTT
MGG G-set mass matrix PRTMGG
PG G-set load vectors PRTPG
Main Index
150 MODEL_CHECK
Specifies Model Check Options
See the DMAP parameter descriptions in Section 5 for a discussion of the parameter name in the last
column of the table and the output generated. The specification of a print item has the effect of
adding a PARAM,parameter,YES entry to the Case Control Section of the file.
Main Index
SOL 151
Executes a Solution Sequence
SOL Executes a Solution Sequence
Specifies the solution sequence or main subDMAP to be executed.
Format:
n
SOL SOLIN = obj-DBset NOEXE
subDMAP-name
Examples:
1. In the following example, SOL 103 is executed from MSCOBJ.
SOL 103
2. In the following example, the PHASE0 subDMAP is altered, SOL 103 is relinked onto the OBJSCR
DBset (which is the default for SOLOUT), and SOL 103 is executed.
SOL 103
COMPILE PHASE1
ALTER ’DTIIN’
TABPT SETREE,,,,// $
.
.
.
ENDALTER $
3. In the following example, the solution sequence called DYNAMICS is executed from the USROBJ
DBset.
SOL DYNAMICS SOLIN = USROBJ
Describer Meaning
n Solution number. See Remark 6. for the list of valid numbers (Integer > 0).
subDMAP-name The name of a main subDMAP. See the MSC Nastran DMAP Programmer’s Guide
(Character; 1 to 8 alphanumeric characters in length and the first character must
be alphabetic).
obj-DBset The character name of a DBset where the OSCAR is stored. See Remarks 1. and
2. (Character; 1 to 8 alphanumeric characters in length and the first character
must be alphabetic).
NOEXE Suppresses execution after compilation and/or linkage of the solution is
complete. Also, the Bulk Data Section and Case Control Section are not read or
processed.
Main Index
152 SOL
Executes a Solution Sequence
Remarks:
1. If SOLIN keyword is not given and if there are no LINK statements within the input data, the
program will perform an automatic link. The program will first collect the objects created in the
current run by the COMPILE statement and the remaining objects stored in the MSCOBJ DBset.
The program will then perform an automatic link of the collected objects.
2. If the SOLIN keyword is not given but a LINK statement is provided, the SOLIN default will be
obtained from the SOLOUT keyword on the LINK statement.
3. The operation sequence control array (OSCAR) defines the problem solution sequence. The OSCAR
consists of a sequence of entries with each entry containing all of the information needed to execute
one step of the problem solution. The OSCAR is generated from information supplied by the user’s
entries in the Executive Control Section.
4. The SOLIN keyword will skip the automatic link and execute the OSCAR on the specified DBset.
5. The DOMAINSOLVER may be used in conjunction with solution sequences 101, 103, 108, and
111 to select domain decomposition solution methods.
6. The following Solution Sequences are currently available in MSC Nastran:
Table 2 Solution Sequences
SOL Number SOL Name Description
101 SESTATIC Statics with options:
Linear steady state heat transfer.
Alternate reduction.
Inertia relief.
103 SEMODES Normal modes.
105 SEBUCKL Buckling with options:
Static analysis.
Alternate reduction.
Inertia relief.
106 NLSTATIC Nonlinear or linear statics.
107 SEDCEIG Direct complex eigenvalues.
108 SEDFREQ Direct frequency response.
109 SEDTRAN Direct transient response.
110 SEMCEIG Modal complex eigenvalues.
111 SEMFREQ Modal frequency response.
112 SEMTRAN Modal transient response.
114 CYCSTATX Cyclic statics with option:
Alternate reduction.
115 CYCMODE Cyclic normal modes.
116 CYCBUCKL Cyclic buckling.
Main Index
SOL 153
Executes a Solution Sequence
Table 2 Solution Sequences
SOL Number SOL Name Description
118 CYCFREQ Cyclic direct frequency response.
128 SENLHARM Nonlinear Harmonic Response
129 NLTRAN Nonlinear or linear transient response.
144 AESTAT Static aeroelastic response.
145 SEFLUTTR Aerodynamic flutter.
146 SEAERO Aeroelastic response.
153 NLSCSH Static structural and/or steady state heat Transfer
analysis with options:
Linear or nonlinear analysis.
159 NLTCSH Transient structural and/or transient heat Transfer
analysis with options:
Linear or nonlinear analysis.
200 DESOPT Design optimization.
400 NONLIN Nonlinear Static and Implicit Transient Analysis and
all linear sequences from statics, modes, frequency,
and transient inclusive with perturbation analysis
based on previous nonlinear analysis
700 NLTRAN ( See SOL Nonlinear Explicit Transient Analysis
700,ID, 154)
Main Index
154 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)
SOL 700,ID Executes MSC Nastran Explicit Nonlinear (SOL 700)
Format:
SOL 700,ID PATH= STOP= NP(or DMP700)= FSIDMP= INTELMPI=
Examples:
SOL 700,129 PATH=3 NP=4
(700,129 request nonlinear transient dynamics, path=3 requests use of the SOL 700 script called out in file
sol700.pth, np=4 requests that 4 processors be used)
Summary:
SOL 700 is an Executive Control statement like SOL that activates an explicit nonlinear transient analysis
integration scheme. The calculations will not be performed directly within MSC Nastran. Instead, SOL 700
will use a separate solver spawned from MSC Nastran.
The SOL 700 statement will spawn an executable which is a 3D, explicit nonlinear analyses code DMP
(distributed memory parallel processing domain decomposition) capabilities.
For ID=129 or NLTRAN, SOL 700 will generate an intermediate input data file, jid.dytr.dat, where “jid” is
the name of the MSC Nastran input file without the extension). For example, if the MSC Nastran input file
is named abcd.dat, (or abcd.bdf) then “jid”=abcd).
Unless specified differently using the STOP=3 option, the executable will be executed from MSC Nastran
on any computer system capable of doing so (which includes most Linux systems and Windows systems). For
it to run, it must be installed, properly licensed, and accessible from the directory where the MSC Nastran
input data resides, MSC_BASE must be provided in the environment.
Nastran SOL 700 Update:
Starting in MSC Nastran 2019.0 there is a change in the execution of MSC Nastran SOL 700. SOL 700 with
LS-Dyna is no longer supported by MSC Nastran. Instead, a new explicit solver is introduced in MSC
Nastran 2019.0. This version can be activated by adding VERSION = PRIMARY to SOL 700 in the input
file or simply by leaving it blank as this will be the default. A new license feature will be needed to run this
new version: NA_Explicit_Dytran.
The new SOL 700 will support both DMP and SMP parallelization. For this, the solver will pull licenses
from the following license feature: NA_Parallel.
Customers that have a lease agreement will no longer be able to run MSC Nastran SOL 700 jobs from version
of MSC Nastran before 2018.0. The binaries needed were in the prior version located in msc20223/dytran
directory of the MSC Nastran installation. However, this directory will be missing after the installation of
MSC Nastran 2022.3.
Paid-up customers of MSC Nastran before 2018.0 can continue to use MSC Nastran SOL 700 jobs from
version of MSC Nastran before 2018.0. For those customers, there will be no change in the FlexLM License
features.
Main Index
SOL 700,ID 155
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Executive Control Parameters:
The required ID may be one of several valid solution sequence integers or names shown in Table 2 for the SOL
statement. Examples are 129 and NLTRAN.
The following solutions are available: 101, 106, 109, 129 (and their equivalent names).
All items on the SOL 700,ID after ID itself may be specified by environmental variables. This may be done
any way environmental variables can be set. They may be set by the MSC Nastran user at run time or by the
system administrator when MSC Nastran is installed. Any values specified on the SOL statement override
those in the environment. Environmental variables are fully described in the . A keywords file is available to
describe the format of each variable. The variable is normally set in the system-wide rc file, a user’s rc file, a
local rc file or in a script used to submit MSC Nastran.
The following describes the various options for PATH. We suggest that PATH=3 for all computer systems.
PATH=1 (Windows Only)
If PATH=1 is specified, MSC Nastran will determine the proper command to execute a serial run. To aid
MSC Nastran in determining where Dytran is located, the dynrun.pth file must be located in the same
directory where the MSC Nastran input file resides. The dynrun.pth file must contain one line providing the
location (complete path) of the SOL 700 run script. A typical example of the line in the file dynrun.pth
follows.
Windows c:\sol700\
A string is appended to this path to form the complete command used to execute the SOL 700 executable.
“dytran jid=name.dytr.dat”
For Windows, MSC Nastran will spawn the external executable using the following command assuming the
MSC Nastran input data is named enf2e.dat. (Although the example appears like it is on multiple lines, it is
actually on a single line.)
c:\sol700/dytran jid=enf2e.dytr.dat
PATH=3 (All Systems)
If PATH=3 is specified, a script or batch file located in the same directory as the SOL 700 executable will be
executed. The name of the executable is dytran (linux) or dytran.exe (Windows). This directory and name of
the script is determined by the first line in a file named sol700.pth which must be in the same directory as
the Nastran input file. Options are specified on subsequent lines of the sol700.pth file. For example, if
Nastran is installed in C:\Program Files\MSC.Software\MSC_Nastran\20223, the dytran.exe
location is C:\Program Files\MSC.Software\MSC_Nastran\2022.3\msc20223
\dytran\win64\bin\dytran. To use sol700.pth file, the first line must be C:\Program
Files\MSC.Software\MSC_Nastran\20223\msc20223\dytran\win64\bin\dytran
Main Index
156 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Available PATH=3 options for Windows PC systems are as follows:
exe= The full path to the executable that is to be used.
Optional -- If exe= is omitted, the directory where the script or batch file resides (first line of
sol700.pth) will be used and dytran for Linux and dytran.exe for windows will be appended. If
exe= is used, it must be the second line in the sol700.pth file.
nproc Number of processors. (only for DMP run)
(Default is to used NP on the SOL 700 line. If NP and nproc are omitted, the default is 1). For
parallel execution, the directory where the MSC Nastran input file exists must be shared with
read/write privileges. If wdir is used, it must also be shared (see below). The directory where
the Dytran executable resides must also be shared for parallel execution.
ncpus Number of processors. (only for SMP)
(Default is not used.) If ncpus is greater than 1 in sol700.pth, Nastran SOL 700 automatically
uses SMP capability.
bat Run in background or foreground (Default).
hlist Host file name. Name of a hostfile containing the same information as “machine”
The format of hostfile is as follows for the example for machine:
machine1 2
machine1 4
intelmpi To activate the Intel MPI set intelmpi equal to yes. Default is no. If intelmpi=yes is placed
directly on the command line (not in sol700.pth) Intel MPI will be activated too.
atb the name of atb file.
imm the name of imm file.
A Windows example of the file sol700.pth for the PATH=3 case follows.
C:\MSC.Software\MSC_Nastran\20223\msc20223\dytran\win64\bin\dytran nastran
nproc=4
For the above example, MSC Nastran will create the following command to spawn the SOL 700 executable
assuming your input file is named abcd.dat. (Although the example appears like it is on multiple lines, it is
actually on a single line.)
C:\Program Files\MSC.Software\MSC_Nastran\20223\msc20223\dytran\win64\bin\dytran
nastran nproc=6
Available PATH=3 options for Linux systems follows:
debug Specifying debug=yes indicates if you want to keep scratch files and other debug
information to investigate when a job fails to run. Default is no.
exe The full path to the executable for Dytran that is to be used. (Optional)
fsidmp Specifying fsidmp=yes indicates to run the FSI Distributed Memory Parallel version.
Default is no. If FSIDMP=YES is placed directly on the command line (not in sol700.pth)
FSI Distributed Memory Parallel will be activated too.
Main Index
SOL 700,ID 157
Executes MSC Nastran Explicit Nonlinear (SOL 700)
hlist The (local) filename containing the hosts list. If this file is not given or not found, a default
local hosts list is used. Note that the MPI universe in which the selected nodes and CPUs
reside is expected to exist and be accessible (i.e., be booted).
nproc Number of processors. (only for DMP run)
(Default is to use NP on the SOL 700 line. If NP and nproc are omitted, the default is 1.)
NOTE: The number of requested processes must be a power of 2.
ncpus Number of processors. (only for SMP)
(Default is not used.) If ncpus is greater than 1 in sol700.pth, Nastran SOL 700
automatically uses SMP capability.
atb the name of atb file.
imm the name of imm file.
A Linux example of the file sol700.pth for the PATH=3 case is as follows:
/app/msc/msc20223/dytran/linux64/bin/dytran nastran nproc=4
For the above example, MSC Nastran will create the a command similar to the following to spawn the SOL
700 executable assuming your input file is named abcd.dat
/app/msc/msc20223/dytran/linux64/bin/dytran nastran nproc=4
If PATH is not specified, the default search path will be used to locate the dytran executable. This version
will be located in a subdirectory named dytran/machine below the MSC Nastran base directory
(MSC_BASE). Not all PATH=3 options are available using this default path option.
STOP
STOP is an optional item. STOP is used to prevent execution of Dytran or prevent execution of MSC
Nastran after IFP if so desired. The various options are as follows:
STOP=1
If STOP=1 MSC Nastran will gracefully stop after IFP. This option is used to prevent MSC Nastran from
performing its own solution (normally used when the solution is performed with ID=129).
STOP=3
STOP=3 MSC Nastran is stopped after IFP and Dytran is not executed. This would be the normal STOP
option if the user wants to examine the intermediate input file, make some changes and then execute Dytran
manually.
The following files are potentially affected by the COPYR option:
NP(or DMP700)=the Number of Processors
NP(or DMP700)=the number of processors (domains) for parallel processing. The default is one. In order to
use more than one domain, MPI, Lam, POE, or whatever parallel program is needed must be properly
installed on all computers involved and a hostfile designating which computers are to be used for each domain
Main Index
158 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)
must have been setup prior to running the job. If NP>1, PATH=3 is used and a file named sol700.pth is
located in the same directory as the MSC Nastran input data. The sol700.pth file should contain all
commands necessary to run in parallel. This file must have execute permissions.
Item Case Control Commands Available in SOL 700
$ Y
BCONTACT Y
BEGIN BULK Y (Other BEGIN forms are not allowed)
DLOAD Y
ECHO Y
ENDTIME Y
ENDSTEP Y
IC Y
LOADSET Y
$S700 Y
SET Y
SPC Y
TITLE Y
TSTEP Y (Same as )
TSTEPNL Y
The following summarizes the Bulk Data entries for SOL 700:
Item Bulk Data Entries Available in SOL 700 Fatal Error
ABINFL Y
ATBACC Y
ATBJNT Y
ATBSEG Y
BARRIER Y
BCBODY Y
BCBODY1 Y
BCBOX Y
BCELIPS Y
Main Index
SOL 700,ID 159
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Item Bulk Data Entries Available in SOL 700 Fatal Error
BCGRID Y
BCMATL Y
BCONECT Y
BCONPRG Y
BCONPRP Y
BCPROP Y
BCSEG Y
BCTABL1 Y
BCTABLE Y
BIAS Y
BJOIN Y
BSURF Y
CBAR Y
CBEAM Y
CDAMP1 Y
CDAMP1D Y
CDAMP2 Y
CDAMP2D Y
CELAS1 Y
CELAS1D Y
CELAS2 Y
CELAS2D Y
CHEXA Y(8 Nodes only)
CMARKB2 Y
CMARKN1 Y
COHFRIC Y
COMPUDS Y
CORD1C Y
Main Index
160 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Item Bulk Data Entries Available in SOL 700 Fatal Error
CORD1R Y
CORD1S Y
CORD2C Y
CORD2R Y
CORD2S Y
CORD3R Y
COUCOHF Y
COUOPT Y
COUP1FL Y
COUPINT Y
COUPLE Y
CPENTA Y(5 Nodes only)
CQUAD4 Y
CROD Y
CSPR Y
CTETRA Y (4 Audio Nodes only)
CTRIA3 Y
CTUBE Y
CVISC Y
CYLINDR Y
DAREA Y
DETSPH Y
DLOAD Y
DYFSISW Y
DYPARAM Y
ENDDATA Y
ENDDYNA Y
EOSDEF Y
Main Index
SOL 700,ID 161
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Item Bulk Data Entries Available in SOL 700 Fatal Error
EOSGAM Y
EOSIG Y
EOSJWL Y
EOSMG Y
EOSNA Y
EOSPOL Y
EOSTAIT Y
EOSUDS Y
EULFOR Y
EULFOR1 Y
EULFREG Y
FAILJC Y
FAILMPS Y
FAILUDS Y
FFCONTR Y
FLOW Y
FLOWC Y
FLOWDEF Y
FLOWT Y
FLOWUDS N
FORCE Y
FORCE2 Y
FORCUDS Y
GBAG Y
GBAGCOU Y
GRAV Y
GRDSET Y
GRID Y
Main Index
162 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Item Bulk Data Entries Available in SOL 700 Fatal Error
HEATLOS Y
HGSUPPR Y
HTRCONV Y
HTRRAD Y
HYDSTAT Y
INCLUDE Y
INFLCG Y
INFLFRC Y
INFLGAS Y
INFLHB Y
INFLTNK Y
INFLTR Y
INITGAS Y
LOAD Y
LEAKAGE Y
LSEQ Y
MAT1 Y
MAT2 Y
MAT8 Y
MATBV Y
MATDEUL Y
MATEP Y
MATF Y
MATFAB Y
MATHE Y
MATORT Y
MATRIG Y
MATVE Y
Main Index
SOL 700,ID 163
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Item Bulk Data Entries Available in SOL 700 Fatal Error
MESH Y
MOMENT Y
MOMENT2 Y
NLOUTUD Y
PBAR Y
PBARL Y
PBEAM Y
PBEAML Y
PBELT Y
PCOMP Y
PDAMP Y
PELAS Y
PELAS1 Y
PERMEAB Y
PERMGBG Y
PEULER Y
PEULER1 Y
PLOAD Y
PLOAD2 Y
PLOAD4 Y (Continuation supported)
PMARKER Y
PMINC Y
PORFCPL Y
PORFGBG Y
PORFLOW Y
PORFLWT Y
PORHOLE Y
PORHYDS Y
Main Index
164 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Item Bulk Data Entries Available in SOL 700 Fatal Error
PORUDS Y
PROD Y
PSHELL Y
PSHELL1 Y
PSOLID Y
PVISC Y
PVISC1 Y
RBE2 Y
RBJOINT Y
RELEX Y
RFORCE (CID, METHOD, continuation line not supported)
SHREL Y
SHRPOL Y
SHRUDS Y
SPC Y
SPC1 Y
SPCADD Y
SPHERE Y
SURFINI Y
TABLED1 Y
TABLUDS Y
TIC Y
TIC3 Y (New Dytran type entry)
TICEL Y
TICEUDS Y
TICEUL1 Y
TICREG Y
TICVAL Y
Main Index
SOL 700,ID 165
Executes MSC Nastran Explicit Nonlinear (SOL 700)
Item Bulk Data Entries Available in SOL 700 Fatal Error
TLOAD1 Y
TLOAD2 N
TODYNA Y
TSTEP Y (Changed to TSTEPNL)
TSTEPNL Y
WALL Y
WALL Y (New rigid wall entry)
YLDHY Y
YLDJC Y
YLDMSS Y
YLDPOL Y
YLDRPL Y
YLDSG Y
YLDTM Y
YLDUDS Y
YLDVM Y
YLDZA Y
Main Index
166 SPARSESOLVER
Sparse Solver Options
SPARSESOLVER Sparse Solver Options
Specifies options used in sparse solution of equations operations.
Format:
SPARSESOLVER target COMPMETH = cmeth , ORDMETH = ometh ,
T
FACTMETH = fmeth MDTRATIO = NO CHART = nsegs ,
R
T T T
NO TABLE , NMAXRAT = nratios , MAXRAT = maxratio ,
R R R
GRID
SORT = VALUE
BOTH
T
MDTSTATS = NO CHART , = nsegs
R
T T T
NO TABLE , NMAXVAL = nmax , NMINVAL = nmin
R R R
T T
MAXVAL = vmax , MINVAL = vmin
R R
BLRTOL = blrtol , NREFINE = nrefine MAXEPS = maxeps ,
GRID
SORT = VALUE , MMEMINC = n% MUMPXPRT = xopt
BOTH
Examples:
1. For the READ module, specify METIS reordering, and for the FRRD1 module, specify the UMFLU
factorization method:
SPARSESOLVER READ (ORDMETH=METIS)
SPARSESOLVER FRRD1 (FACTMETH=UMFLU)
2. Request matrix diagonal term ratio output:
Main Index
SPARSESOLVER 167
Sparse Solver Options
SPARSESOLVER DCMP ( MDTRATIO )
3. Request matrix diagonal term ratio output in chart format for translational DOFs, and limit the
number of printed diagonal ratios to 50:
SPARSESOLVER DCMP ( MDTRATIO=(CHART,TABLET,NMAXRATT=50) )
4. Request Matrix Diagonal Term statistics output for:
• Chart format for translational and rotational DOF
• Table format for translational dof limited to largest 10 terms greater than 1.0E+08
• Table format for translational dof limited to smallest 20 terms smaller than 1.0
• Table format for rotational dof limited to smallest 30 terms smaller than 100.0
SPARSESOLVER DCMP (MDTSTATS=(CHART,TABLET,NMAXVALT=10,
MAXVALT=1.0E+08, NMINVALT=20, MINVALT=1.0,TABLER, NMINVALR=30,
MINVALR=100.00))
Describer Meaning
target The target application for the options. The target application choices are: CEAD,
DCMP, DECOMP, MDSTAT, NLSOLVE, READ, SOLVE, FRRD1, and
TRD1.
cmeth Compression method to be used (Default = GRID).
The choices for compression method are: GRID, SUPER, GRDSUPER and
NONE.
ometh Ordering method to be used (Default = Automatic). The choices for ordering
method are: AMF, BEND, MD, METIS, MMD, PRDMD, PRDMETIS,
PRDSMPMS, MUMMETIS, MUMAMD, and NONE. The default
automatically selects among METIS, MMD and BEND.
fmeth Factorization method to be used.
The choices for factorization method are: MSCLDL, MSCLU, UMFLU,
NUMFLU, PRDLDL, PRDLU, MUMPS, and MUMPSBLR. For default
factorization methods, see Remarks 18.-25. below.
NO No output is to be produced for the keyword.
T The keyword applies to translational DOF only.
R The keyword applies to rotational DOF only.
nsegs Number of bars to be used in chart (Default = 0).
nratios Number of diagonal term ratios to be included in table (Default = 25).
maxratio Diagonal term ratio above which ratios are included in the table (Default =
1.0E+5).
GRID Table output is sorted on GRID ID and component code.
VALUE Sort table output on term values.
BOTH Table is output once sorted on GRID ID and once on term value.
Main Index
168 SPARSESOLVER
Sparse Solver Options
Describer Meaning
nmax Number of largest values to print (Default = 25).
nmin Number of smallest values to print (Default = 25).
vmax All terms larger than vmax are printed (Default = 1.0E+10).
vmin All terms smaller than vmin are printed (Default = 1.0).
blrtol MUMPS Block Low Rank drop tolerance (Default=1.0E-8).
nrefine Number of iterative refinement steps for the MUMPS BLR solver option
(default=0).
maxeps Maximum eps for MUMPS and PARSIO solver option (default = 1.e-3)
mmeminc For the MUMPS solver, the percentage increase in memory over the estimates
provided during the symbolic phase (Default=20). Should be a positive value;
recommended to be no more than 50.
mumpxprt Expert and experimental options for the MUMPS solver. See the HPC User's
Guide for details.
Remarks:
1. All of the keywords for the target application must be enclosed in parentheses.
2. The following table correlates target applications with available factorization methods.
Module MSCLDL MSCLU UMFLU NUMFLU PRDLDL PRDLU MUMPS
CEAD Yes Yes No Yes No Yes No
DCMP Yes Yes No No Yes No Yes
DECOMP Yes Yes No No No No No
FRRD1 Yes Yes Yes No No Yes No
MDSTAT Yes Yes No No No No No
NLSOLV Yes Yes No No Yes No Yes
READ Yes No No No No No Yes
SOLVE Yes Yes No No No No Yes
TRD1 Yes Yes Yes No No No No
3. More than one SPARSESOLVER entry may be used, so that one may specify different options for
different target modules.
4. System cell 206 can specify both a reordering method and a compression method by adding the
respective values. For example, to specify GRDSUPER compression method with BEND reordering,
SYSTEM(206) would be set to 68 (since 64+4=68). Or, to specify SUPER compression with METIS
reordering, SYSTEM(206) would be set to 136 (since 128+8=136).
Main Index
SPARSESOLVER 169
Sparse Solver Options
5. Note that SYSTEM(166), SYSTEM(206) and SYSTEM(209) have precedence over the
SPARSESOLVER command, whether set on the submittal line or in DMAP.
6. System cell 166 can also be used to turn on extra diagnostic output from the sparse factorization by
setting SYSTEM(166)=2.
7. The UMFLU factorization method ignores COMPMETH and ORDMETH since it contains its
own compression/reordering method.
8. The matrix diagonal term ratio (MDTRATIO) and value (MDTSTATS) keywords and options are
used only by the DCMP target application. They will be ignored by other target applications.
9. The MDTRATIO and MDTSTATS keywords apply to both translational and rotational degrees of
freedom unless modified by the T or R describer. Separate output is produced for each of the
translational and rotational degrees of freedom in the matrix.
10. The MDTRATIO and MDTSTATS CHART option default produces a chart of values contained
in powers of ten bandwidths. A specification for the nsegs describer causes the bandwidth to be
internally computed to produce nsegs bars. Bars are produced for the bandwidths only if they contain
terms.
11. MDTRATIO and MDTSTATS keywords are processed in the order given. It is possible for a
keyword to modify the effects of a previously processed keyword. For example, the combination
CHART, CHARTR=5 produces different outputs compared to CHARTR=5, CHART.
12. The MDTRATIO NMAXRAT describer limits the content of the TABLE output to the specified
highest number of diagonal ratios that exceed the value of the MAXRAT describer.
13. MDTSTATS generates output for matrix diagonal term values. For the TABLE option, it produces
a table containing the NMINVAL=nmin smallest terms smaller than MINVAL=vmin as well as the
NMAXVAL=nmax largest terms larger than MAXVAL=vmax.
14. The ORDMETH option must be one of PRDMD, PRDMETIS, or PRDSMPMS for PRDLDL and
PRDLU.
15. The COMPMETH option is ignored for PRDLDL and PRDLU.
16. The DOMAINSOLVER (RUNOPT=MULTIPAR) option is not supported with PRDLDL or
PRDLU.
17. For PRDLDL and PRDLU, if there is not sufficient memory for an in-core solver, then an out-of-
core solver will be attempted and performance will be negatively affected.
18. The following special rules apply for PRDLDL for NLSOLV:
a. The maximum number of threads used is given by DMP*SMP, and PRDLDL will choose a
number of threads, up to this maximum, most suitable to the problem size.
b. PRDLDL is supported only when FNT or PFNT method is used for nonlinear iteration
(KMETHOD of NLPARM or NLSTEP).
c. If the problem fails to converge with PRDLDL, then add MDLPRM,LMT2MPC,1 to the bulk
data section in order to convert Lagrange multipliers to MPCs.
19. The following special rules apply for PRDLDL for DCMP:
a. DMP is not supported for PRDLDL for DCMP as it only gets parallelism from SMP
Main Index
170 SPARSESOLVER
Sparse Solver Options
b. PRDLDL automatically provides parallelization over multiple RHSs with SMP.
c. If PRDLDL encounters a zero pivot issue (SFM 11332), the user should rerun with bulk data
entry MDLPRM,PRDMTYPE,-2 to have Intel MKL Pardiso regard the matrix as indefinite, and
entry MDLPRM,PRDWMTCH,0 in order to turn off weighted matching.
20. The following special rules apply for PRDLU for CEAD:
a. PRDLU is only supported for the CLAN option within CEAD (refer to CMETHOD option).
21. The following special rules apply for PRDLU for FRRD1:
a. The Krylov solver is not supported with PRDLU for FRRD1.
b. DMP is supported for PRDLU for FRRD1.
c. MKL Pardiso is not supported in the uncoupled solution algorithm for FRRD1.
d. MKL Pardiso is the default solver for FRRD1 except for the following cases:
– SOL 111 symmetric solution without frequency dependence, in which case MSCLDL is used.
– Iterative solver specified by user.
22. For CEAD, the default solver matrix decomposition is PRDLU(Pardiso).
23. User specified factorization method (fmeth) via SPARSESOLVER entry or SYSTEM(209) may be
overwritten automatically due to matrix type or symmetry by MSC Nastran.
24. Several options for Intel MKL Pardiso are controlled using the MDLPRM bulk data entry. See the PRD*
parameters detailed in the MDLPRM section.
25. Mumps sparse direct solver with DCMP and NLSOLV module is currently supported in SOL 101
only.
26. The Mumps sparse direct solver with READ only supports DMP with
DOMAINSOLVER MODES (PARTOPT=FREQ, NCLUST=NDMP)
For example, when using DMP=4 and the Mumps solver in the READ module, use
SPARSESOLVER READ (FACTMETH=MUMPS)
DOMAINSOLVER MODES (PARTOPT=FREQ, NCLUST=4)
Main Index
TIME 171
Sets Maximum CPU and I/O Time
TIME Sets Maximum CPU and I/O Time
Sets the maximum CPU and I/O time.
Format:
TIME[=]t1[,t2]
Examples:
1. The following example designates a runtime of 8 hours:
TIME 480
2. The following example designates 90 seconds:
TIME 1.5
Describer Meaning
t1 Maximum allowable execution time in CPU minutes (Real or Integer>0;
Default=1.89E9 seconds).
t2 Maximum allowable I/O limit in minutes (Real or Integer>0; Default is infinity,
which is machine dependent).
Remarks:
1. The TIME statement is optional.
2. If t2 is specified then t1 must be specified.
Main Index
172 TIME
Sets Maximum CPU and I/O Time
Main Index
Chapter 5: Case Control Commands
MSC Nastran Implicit Nonlinear (SOL 600) User’s GuideMSC Nastran Quick Reference
Guide
5 Case Control Commands
Key to Descriptions
The Case Control Section
Case Control Command Summary
Case Control Commands
Case Control Applicability Tables
OUTPUT(PLOT) Commands
X-Y PLOT Commands
OUTPUT(POST) Commands
Main Index
176 MSC Nastran Quick Reference Guide
Key to Descriptions
Key to Descriptions
Brackets [ ] indicate that AAbrief
brief description ofthe
description of the
a choice of describers is command
command isisgiven.
given.
optional.
Describers
Describers ininuppercase
uppercase letters
letters are keywords
are keywords that mustthat
be speci-
must
fied asbe specified as shown.
shown.
Describers
Describers inin
lower
lower case
case are
are variables.
variables.
IfIfthe
the describers are
describers are
stacked vertically,then Braces
Braces {{ }}indicate
indicate that
that a
stacked vertically, achoice
choiceofofdescribers
describers
then
only oneonlymay
onebemay
speci- is
be specified. ismandatory.
mandatory.
fied.
The
The default describersareare
default describers shaded.
shaded.
.Parentheses are required if
items inside the parentheses
are specified.
Each of the describers is discussed briefly. Further
details may be discussed under Remarks.
If the describer is in lower case, then it is a variable
and the describer’s type (e.g., Integer, Real, or
Character), allowable range, and default value are
enclosed in parentheses. If no default value is
given, the describer must be specified by the user.
The remarks are generally arranged in order of
importance and indicate such things as which
Bulk Data entries are selected by the Case
Control command, the command’s relationship
to other commands, restrictions and
recommendations on its use, and further details
regarding the describers.
Main Index
CHAPTER 5 177
The Case Control Section
The Case Control Section
The Case Control Section has several basic functions. Specifically, it:
Selects loads and constraints.
Requests printing, plotting, and/or punching of input and out data (plotter commands are described
in Plotting in the MSC Nastran Reference Guide).
Defines the subcase structure for the analysis.
Table 5-3 through Table 5-8 at the end of this section indicate the applicability of each command in all solution
sequences.
Case Control Command Descriptions
Case Control commands may be abbreviated down to the first four characters if the abbreviation is unique
relative to all other commands. If not, the full name of the command (or at least the first eight characters if
the name exceeds eight characters) must be specified in order to avoid errors. Each command is described as
follows:
Description
A brief sentence about the function of the command is given.
Format
Describers in uppercase are keywords that must be specified as shown. In addition, describers in lowercase
indicate that the user must provide a value.
Braces { } indicate that a choice of describers is mandatory. If the describers are stacked vertically, then only
one may be specified.
Brackets [ ] indicate that a choice of describers is optional. If the describers are stacked vertically, then only
one may be specified.
Describers that are shaded indicate the defaults.
If the command line is longer than 72 columns, then it may be continued to the next line with a comma. For
example:
SET 1 = 5, 6, 7, 8, 9,
10 THRU 55
Example
A typical example is given.
Describers and Meaning
Each of the describers is briefly discussed. The describer’s type (e.g., Integer, Real, or Character), allowable
range, and default value are enclosed in parentheses. The describer must be specified by the user if no default
value is given.
Main Index
178 MSC Nastran Quick Reference Guide
Case Control Command Summary
Remarks
The remarks are generally arranged in order of importance and indicate such things as which Bulk Data
entries are selected by the Case Control command; the command’s relationship to other commands,
restrictions and recommendations on the command’s use; and further descriptions of the describers.
Case Control Command Summary
This section contains a summary of all Case Control commands under the following headings:
Subcase Definition
1. Output Request Delimiters
OUTPUT (Case) Delimits the various types of commands for the structure
plotter, curve plotter and grid point stress.
OUTPUT(PLOT) Beginning of structure plotter output request.
OUTPUT(POST)
or
Indicates beginning of grid point stress output requests.
SETS DEFINITION
OUTPUT(XYOUT)
or Indicates beginning of curve plotter output request.
OUTPUT(XYPLOT)
2. Subcase Delimiters
REPCASE (Case) Delimits and identifies a repeated output request subcase.
SUBCASE (Case) Delimits and identifies a subcase.
SUBCOM (Case) Delimits and identifies a combination subcase.
SYM (Case) Delimits and identifies a symmetry subcase.
SYMCOM (Case) Delimits and identifies a symmetry combination subcase.
3. Subcase Control
MASTER (Case) Allows the redefinition of a MASTER subcase.
MODES (Case) Repeats a subcase.
Main Index
CHAPTER 5 179
Case Control Command Summary
SUBSEQ (Case) Gives the coefficients for forming a linear combination of the
previous subcases.
SYMSEQ (Case) Gives the coefficients for combining the symmetry subcases
into the total structure.
Data Selection
1. Static Load Selection
DEFORM (Case) Selects the element deformation set.
CLOAD (Case) Requests a CLOAD Bulk Data entry that defines a list of superelement
loads and their scale factors in nonlinear static analysis only.
LOAD (Case) Selects an external static loading set.
LOADNAME (Case) Provides a name to be associated with a loading condition.
2. Dynamic Load Selection
DLOAD (Case) Selects a dynamic load or an acoustic source to be applied in a transient
or frequency response problem.
LOADSET (Case) Selects a sequence of static load sets to be applied to the structural
model. The load sets may be referenced by dynamic load commands.
NONLINEAR (Case) Selects nonlinear dynamic load set for transient problems.
3. Constraint Selection
AXISYMMETRIC Selects boundary conditions for an axisymmetric shell problem or
(Case) specifies the existence of fluid harmonics for hydroelastic problems.
AUTOSPC (Case) Requests that stiffness singularities and near singularities be
automatically constrained via single or multipoint constraints.
BC (Case) Identifies multiple boundary conditions for normal modes, buckling,
and flutter analysis in SOLs 103, 105, 145, and 200.
DSYM (Case) Provides for either one or two planes of overall symmetry in DIH-type
cyclic symmetry problems.
MPC (Case) Selects a multipoint constraint set.
SPC (Case) Selects a single-point constraint set to be applied.
Main Index
180 MSC Nastran Quick Reference Guide
Case Control Command Summary
STATSUB (Case) Selects the static solution to use in forming the differential stiffness for
buckling, normal modes, complex eigenvalue, frequency response, and
transient response analysis.
SUPORT1 (Case) Selects the fictitious support set (SUPORT1 entries only) to be applied
to the model.
4. Thermal Field Selection
TEMPERATURE (Case) Selects the temperature set to be used in either material property
calculations, or thermal loading in heat transfer and structural
analysis.
TEMPERATURE (Case) Selects initial temperature distribution for temperature-dependent
(INITIAL) material properties and heat transfer problems.
TEMPERATURE (Case) Selects temperature set for static thermal load.
(LOAD)
TEMPERATURE (Case) Selects temperature set for temperature-dependent material
(MATERIAL) properties.
TSTRU (Case) Defines a temperature set ID for a structures run based on a heat
transfer subcase.
5. Static Solution Conditions
SMETHOD (Case) Selects iterative solver parameters.
6. Dynamic Solution Conditions
CMETHOD (Case) Selects complex eigenvalue extraction parameters.
FREQUENCY (Case) Selects the set of forcing frequencies to be solved in frequency
response problems.
FRF (Case) Specifies data for Frequency Response Function (FRF) generation or
for the FRF Based Assembly (FBA) process.
IC (Case) Selects the initial conditions for direct transient analysis (SOLs 109,
129, and 159).
METHOD (Case) Selects the real eigenvalue extraction parameters.
MODESELECT (Case) Requests a set of computed mode shapes for inclusion in dynamic
analysis.
NSM (Case) Selects nonstructural mass set.
Main Index
CHAPTER 5 181
Case Control Command Summary
RANDOM (Case) Selects the RANDPS and RANDT1 Bulk Data entries to be used in
random analysis.
RESVEC (Case) Specifies options for and the calculation of residual vectors.
RGYRO (Case) Activates gyroscopic effects and selects RGRYO or UNBALNC
entries.
SDAMPING (Case) Requests modal damping as a function of natural frequency in
modal solutions, or viscoelastic materials as a function of frequency
in direct frequency response analysis.
SMETHOD (Case) Selects iterative solver override options in frequency response
analysis.
TSTEP (Case) Selects integration and output time steps for linear or nonlinear
transient analysis.
7. Direct Input Matrix Selection
A2GG (Case) Selects direct input fluid-structure coupling matrix.
B2GG (Case) Selects direct input damping matrices.
B2PP (Case) Selects direct input damping matrices.
K2GG (Case) Selects direct input stiffness matrices.
K2PP (Case) Selects direct input stiffness matrices, which are not included in normal
modes.
K42GG (Case) Selects direct input structural damping matrices.
M2GG (Case) Selects direct input mass matrices.
M2PP (Case) Selects direct input mass matrices, which are not included in normal
modes.
MFLUID (Case) Selects the MFLUID Bulk Data entries to be used to specify the fluid-
structure interface.
P2G (Case) Selects direct input load matrices.
TFL (Case) Selects the transfer function set(s) to be added to the direct input
matrices.
8. Nonlinear Analysis
ENDSTEP (Case) Specifies final analysis step for SOL 700.
ENDTIME (Case) Specifies final analysis time for SOL 700.
NLBUCK (Case) Perform a nonlinear buckling analysis in SOL 400.
NLHARM (Case) Selects the parameters used for nonlinear harmonic response analysis.
Main Index
182 MSC Nastran Quick Reference Guide
Case Control Command Summary
NLOPRM (Case) Controls MSC Nastran nonlinear output, debug printout and debug
POST.
NLPARM (Case) Selects the parameters used for nonlinear static analysis.
NLSTEP (Case) Selects integration and output time steps for static and transient nonlinear
analysis in SOL 400.
STEP (Case) Defines and identifies a nonlinear analysis for SOL 400.
SUBSTEP (Case) Delineates and identifies a nonlinear analysis SUBSTEP for COUPLED
analysis in SOL 400.
TSTEPNL (Case) Defines parametric controls and data for nonlinear transient structural or
heat transfer analysis. is intended for SOLs 129, 159 and 700.
9. Aerodynamic Analysis
AECONFIG (Case) Assigns the aerodynamic configuration parameter used to locate the
associated datablocks on the aerodynamic and aeroelastic databases.
AESYMXY (Case) Aerodynamic XY plane of symmetry flag.
AESYMXZ (Case) Aerodynamic XZ plane of symmetry flag.
AEUXREF (Case) Define the reference aerodynamic extra point (controller) vector)
CSSCHD (Case) Aerodynamic control surface schedule.
DIVERG (Case) Selects the divergence parameters in a static aeroelastic divergence
problem.
FMETHOD (Case) Selects the parameters to be used in the aerodynamic flutter analysis.
GUST (Case) Selects the field in an aerodynamic response problem.
TRIM (Case) Selects trim variable constraints in static aeroelastic response.
10. Design Sensitivity and Optimization (SOL 200)
ANALYSIS (Case) Specifies the type of analysis being performed for the current subcase.
AUXCASE (Case) Delimits Case Control commands for an auxiliary model in SOL 200.
AUXMODEL (Case) References an auxiliary model for generation of boundary shapes in
shape optimization.
DESGLB (Case) Selects the design constraints to be applied at the global level in a design
optimization task.
DESMOD (Case) Assigns the design model parameter used to locate the associated
datablocks for merging of two or more SOL 200 using the MultiOpt
tookit application.
Main Index
CHAPTER 5 183
Case Control Command Summary
DESOBJ (Case) Selects the DRESP1 or DRESP2 entry to be used as the design objective.
DESSUB (Case) Selects the design constraints to be used in a design optimization task for
the current subcase.
DESVAR (Case) Selects a set of DESVAR entries for the design set to be used.
DRSPAN (Case) Selects a set of DRESP1 and DRESP2 entries for the current subcase that
are to be used in a DRESP2 or DRESP3 response that spans subcase.
DSAPRT (Case) Specifies design sensitivity output parameters.
MODTRAK (Case) Selects mode tracking options in design optimization (SOL 200).
11. Adaptive Meshing
HADAPT (Case) Specifies Mesh adaptivity control parameters.
12. Fluid-Structure Analysis
A2GG (Case) Selects a direct input fluid-structure coupling matrix.
ACFPMRESULT Requests output of acoustic field point mesh results.
(Case)
ACPOWER (Case) Request output of the power radiated from the wetted surface.
FLSFSEL (Case) Fluid-structure parameter collector for frequency and fluid superelement
selection.
FLSPOUT (Case) Fluid-structure parameter collector for mode participation.
FLSTCNT (Case) Fluid-structure parameter collector for symmetry and force request.
INTENSITY (Case) Requests output of acoustic intensity on wetted surface.
TRIMGRP (Case) Selection of Trim Component(s)
13. Nastran/ADAMS Interface
ADAMSMNF* Control for Nastran/ADAMS interface modal neutral file (MNF).
(Case)
For MSC Nastran 2004, to ensure compatibility with the Adams msc2mnf took
kit, if the ADAMSMNF Case Control command has the keyword
ADMOUT=YES, the Nastran SYSTEM word OP2NEW is automatically set
to OP2NEW=0. This means that any output2 files generated will have a pre-
MSC Nastran 2004 format.
14. Contact
Main Index
184 MSC Nastran Quick Reference Guide
Case Control Command Summary
BCHANGE (Case) Selects the change of the definition contact bodies in contact analysis.
BCMOVE (Case) Contact body movement selection in contact analysis.
BCONCHK (Case) Requests contact model check.
BCONTACT (Case) Requests contact analysis.
BOUTPUT (Case) Requests output for contact analysis.
BSQUEAL (Case) Selects data for brake squeal analysis
UNGLUE (Case) Selects the grids should use standard contact instead of glued contact
in glued bodies.
15. Monte-Carlo simulation
MONCARL (Case) Control for Monte-Carlo simulation.
Output Selection
1. Output Control
ECHO (Case) Controls echo (i.e., printout) of the Bulk Data.
ECHOOFF Suppresses echo of Case Control.
ECHOON Reactivates echo of Case Control.
LABEL (Case) Defines a character string that will appear on the third heading line of each
page of printer output.
LINE (Case) Defines the maximum number of output lines per printed page.
MAXLINES Sets the maximum number of output lines.
(Case)
PAGE (Case) Causes a page eject in the echo of the Case Control Section.
PLOTID (Case) Defines a character string that will appear on the first frame of any plotter
output.
POST (Case) Activates postprocessor operations for selected output data.
SKIP (Case) Activates or deactivates the execution of subsequent commands in the Case
Control Section (including plot commands).
SKIPON Defines commands in the Case Control Section that are not to be processed.
SKIPOFF Resumes processing of commands in the Case Control Section.
Main Index
CHAPTER 5 185
Case Control Command Summary
SUBTITLE Defines a subtitle that will appear on the second heading line of each page of
(Case) printer output.
TITLE (Case) Defines a character string that will appear on the first heading line of each page
of MSC Nastran printer output.
2. Set Definition
MAXMIN (Case) Specifies options for max/min surveys of certain output data associated with
grid points.
OFREQUENCY Selects a set of frequencies for output requests.
(Case)
OMODES (Case) Selects a set of modes for output requests.
OTIME (Case) Selects a set of times for output requests.
PARTN (Case) Specifies a list of grid point identification numbers that will be partitioned
with the DMAP module MATMOD (Option 17). In SOLs 111 and 200,
the PARTN Case Control command specifies the points at which modal
participation factors are to be computed.
SET (Case) Defines a set of element or grid point numbers to be plotted.
SURFACE Defines a surface for the calculation of grid point stresses, strains, or mesh
stress discontinuities.
VOLUME Defines a volume for the calculation of grid point stresses, strains, or mesh
stress discontinuities.
Main Index
186 MSC Nastran Quick Reference Guide
Case Control Command Summary
3. Physical Set Output Requests
ACCELERATION (Case) Requests the form and type of acceleration vector output.
BOUTPUT (Case) Requests line or 3D (SOLs 101, 106, 129, 153, 159 and 400)
contact output.
CMSENRGY (Case) Requests the output of component (superelement) modal strain,
kinetic, and damping energies.
DISPLACEMENT (Case), Requests the form and type of displacement or pressure vector
VECTOR (Case), or output. Note: PRESSURE and VECTOR are equivalent
PRESSURE (Case) commands.
EDE (Case) Requests the output of the energy loss per cycle in selected
elements.
EKE (Case) Requests the output of the kinetic energy in selected elements.
ELSDCON (Case) Requests mesh stress discontinuities based on element stresses (see
STRESS).
ENTHALPY (Case) Requests form of enthalpy vector output in transient heat transfer
analysis (SOL 159).
ESE (Case) Requests the output of the strain energy in selected elements.
EQUILIBRIUM (Case) Requests equilibrium force balance output.
FATIGUE (Case) Request a fatigue analysis with life/damage output in SOLs 101,
103, 108, 111, or 112.
FLUX (Case) Requests the form and type of gradient and flux output in heat
transfer analysis.
FORCE (Case) or Requests the form and type of element force output or particle
ELFORCE velocity output in coupled fluid-structural analysis. Note:
ELFORCE is an equivalent command.
GPFORCE (Case) Requests grid point force balance at selected grid points.
GPKE (Case) Requests the output of the kinetic energy at selected grid points in
normal modes analysis only.
GPSDCON (Case) Requests mesh stress discontinuities based on grid point stresses
(see GPSTRESS).
GPSTRAIN (Case) Requests grid points strains.
GPSTRESS (Case) Requests grid point stresses.
GVECTOR (Case) Requests the form and type of g-set eigenvector output in SOLs
200 and 400.
HDOT (Case) Requests form of rate of change of enthalpy vector output in
transient heat transfer analysis (SOL 159).
MCFRACTION (Case) Requests modal contribution fractions output.
Main Index
CHAPTER 5 187
Case Control Command Summary
MODALKE (Case) Requests modal kinetic energy output.
MODALSE (Case) Requests modal strain energy output.
MEFFMASS (Case) Requests the output of the modal effective mass, participation
factors, and modal effective mass fractions in normal modes
analysis.
MPCFORCES (Case) Requests the form and type of multipoint force of constraint vector
output.
NLSTRESS (Case) Requests the form and type of nonlinear element stress output in
SOL 106.
NOUTPUT (Case) Requests physical output in cyclic symmetry problems.
OLOAD (Case) Requests the form and type of applied load vector output.
RCROSS (Case) Requests computation and output of cross-power spectral density
and cross-correlation functions in random analysis.
ROTSEKE (Case) Request rotor modal strain and kinetic energies in complex
eigenvalue analysis for selected rotor IDs.
SPCFORCES (Case) Requests the form and type of single-point force of constraint
vector output.
STRAIN (Case) Requests the form and type of strain output.
STRESS (Case) or Requests the form and type of element stress output. Note:
ELSTRESS ELSTRESS is an equivalent command.
STRFIELD (Case) Requests the computation of grid point stresses for graphical
postprocessing and mesh stress discontinuities.
THERMAL (Case) Requests the form and type of temperature output.
VELOCITY (Case) Requests the form and type of velocity vector output.
4. Solution Set Output Requests
AEROF (Case) Requests the aerodynamic loads on aerodynamic control points.
APRESSURE (Case) Requests the aerodynamic pressures in static aeroelastic response.
HARMONICS (Case) Controls the number of harmonics output in axisymmetric shell or
axisymmetric fluid problems; controls the number of harmonics to be
used for analysis in cyclic symmetry problems.
HOUTPUT (Case) Requests harmonic output in cyclic symmetry problems.
MPRES (Case) Requests the pressure for selected wetted surface elements when virtual
mass (MFLUID) is used.
NLLOAD (Case) Requests the form and type of nonlinear load output for transient
problems.
Main Index
188 MSC Nastran Quick Reference Guide
Case Control Command Summary
SACCELERATION Requests the form and type of solution set acceleration output.
(Case)
SDISPLACEMENT Requests the form and type of solution set displacement output.
(Case)
SVECTOR (Case) Requests the form and type of solution set eigenvector output.
SVELOCITY (Case) Requests the form and type of solution set velocity output.
TRIMF (Case) Specifies options for the output of trim loads from a static aeroelastic
analysis as FORCE/MOMENT Bulk Data entries.
5. Model Checkout
ELSUM (Case) Requests a summary of element properties for output.
GROUNDCHECK Requests grounding check analysis on stiffness matrix to expose
(Case) unintentional constraints by moving the model rigidly.
WEIGHTCHECK At each stage of the mass matrix reduction, computes rigid body mass
(Case) and compares with the rigid body mass t the g-set.
Superelement Control
EXTDRIN (Case) Requests the job to perform an external superelement data recovery
restart. Also specifies the storage media of the boundary solution data.
EXTDROUT (Case) Requests the job to store external superelement boundary displacements
and column labels; e.g., eigenvalues, forcing frequencies, time steps. Also
specifies the storage media of the boundary solution data.
EXTSEOUT (Case) Specifies the data to be saved for an external superelement, and the
medium on which the data is to be saved.
LDLABEL (Case) Assigns a character string to an external superelement creation run's
subcase in order to identify the static load in the assembly run.
SEALL (Case) Specifies the superelement identification numbers of phase 1 processing
wherein all matrices and loads are generated and assembled. Controls
execution of the solution sequence.
SEDR (Case) Specifies the superelement identification numbers for which data
recovery will be performed.
SEDV (Case) Specifies the superelement identification numbers for which the design
variables will be processed.
SEEXCLUDE (Case) Specifies the superelement identification numbers for which all matrices
and loads will not be assembled into the downstream superelement.
Main Index
CHAPTER 5 189
Case Control Command Summary
SEFINAL (Case) Specifies the superelement identification number of the final
superelement to be assembled.
SEKREDUCE (Case) Specifies the superelement identification numbers for which stiffness
matrices are assembled and reduced.
SELGENERATE Specifies the superelement identification numbers for which static loads
(Case) will be generated.
SELREDUCE (Case) Specifies the superelement identification numbers for which the static
load matrices will be assembled and reduced.
SEMGENERATE Specifies the superelement identification numbers for which stiffness,
(Case) mass, and damping matrices will be generated.
SEMREDUCE (Case) Specifies the superelement identification numbers for which the mass
and damping matrices will be assembled and reduced. In buckling
analysis, the differential stiffness matrices are assembled and reduced.
SERESP (Case) Specifies the superelement identification numbers for which the design
sensitivity matrices will be generated.
SOLUTION (Case) Selects the solution ID for a 3rd step external superelement data recovery
restart in SOL 400.
SUPER (Case) Assigns a subcase(s) to a superelement or set of superelements.
Module Control
EXTMDOUT (Case) Specifies the data to be saved for an external module, and the medium on
which the data is to be saved.
Miscellaneous
$ Used to insert comments into the input file. Comment statements may
appear anywhere within the input file.
BEGIN BULK (Case) Designates the end of the Case Control Section and/or the beginning of
a Bulk Data Section.
INCLUDE (Case) Inserts an external file into the input file. The INCLUDE statement may
appear anywhere within the input data file.
NSM (Case) Request nonstructural mass distribution selection.
OUTPUT (Case) Delimits the various types of commands for the structure plotter, curve
plotter, grid point stress, and MSGSTRESS.
PARAM (Case) Specifies values for parameters.
Main Index
190 MSC Nastran Quick Reference Guide
Case Control Command Summary
POST (Case) Controls selection of data to be output for postprocessing.
RIGID (Case) Selects type of rigid element formulations to be used.
Main Index
CHAPTER 5 191
Case Control Commands
Case Control Commands
$ Comment
Used to insert comments into the input file. Comment statements may appear anywhere within the input file.
For SOL 700 only, the string ‘$S700’ (starting in column 1 with a blank in column 6) may be used to transfer
any Case Control string directly to Dytran. For example:
$S700 ELOUT(TEST1)=XVEL,YVEL,ZVEL,DENSITY,SIE,PRESSURE,fmat
will become
ELOUT(TEST1)=XVEL,YVEL,ZVEL,DENSITY,SIE,PRESSURE,fmat
in the Case Control Section of the Dytran input (jid.dytr.dat) file. Please see descriptions of ‘$S700’ Case
Control entries elsewhere in this section.
Format:
$ followed by any characters out to column 80.
Example:
$ TEST FIXTURE-THIRD MODE
Remarks:
1. Comments are ignored by the program.
2. Comments will appear only in the unsorted echo of the Bulk Data.
Main Index
192 MSC Nastran Quick Reference Guide
Direct Case Control Command for SOL 700
$S700 Direct Case Control Command for SOL 700
All entries which start with $S700 in the Case Control Section will be passed directly to the SOL 700 solver.
Import of Euler results and the control of output generation are using this entry:
Output Control:
No need to use the Nastran classical case control output (STRESS,DISP,…). This option controls ARC
(state file) and THS (time history file) output files.
You need to specify the following for a complete output specification:
1. Type of the file
2. What entities (e.g., grid points, elements, rigid bodies, etc.)
3. What results are output
4. How often it is saved
5. How often data is written
Format:
$S700 TYPE(logical_file) = ARCHIVE
$S700 Entity Type(logical_file) = setid
$S700 SET setid = idi
$S700 Entity Var(logical_file) = var
$S700 TIMES(logical_file) = ti
$S700 STEPS(logical_file) = stepi
$S700 SAVE(logical_file) = n
Example:
$S700 TYPE (elements) = ARCHIVE
$S700 ELEMENTS (elements) = 1
$S700 SET 1 = 16805 THRU 16875 16877 THRU 16947 16949 THRU 18080 ,
$S700 59 THRU 945 1067 1068 1069 1070 1181 THRU 1412 ,
$S700 1423 THRU 2965 3076 THRU 3930 4041 THRU 4895 ,
$S700 5006 THRU 5860 5971 THRU 7744 10855 THRU 12025 ,
$S700 12138 THRU 12990 13103 THRU 13955 14068 THRU 14920 ,
$S700 15033 THRU 15885 15998 THRU 16875 16877 THRU 16947 ,
$S700 16949 THRU 18080 16805 THRU 16875 16877 THRU 16947 ,
$S700 17005 THRU 18080 16949 THRU 17004 BY 1
$S700 ELOUT (elements) = EFFSTS, PRESSURE, FMAT, YMOM ,
$S700 QDIS,
$S700 MASST
$S700 TIMES (elements) = 0,THRU,END,BY,4e-4
$S700 SAVE (elements) = 1
Main Index
CHAPTER 5 193
Direct Case Control Command for SOL 700
Describer Meaning
logical_file The logical name of the file to which the user output is written. The logical name may
not contain any spaces or special characters and must be restricted to 8 characters or less.
(Characters; Required)
setid Number of a SET command. Only data for elements that appear in the set are output.
(Integer > 0; Required)
Idi Identification numbers at which the output is requested. “THRU” and “BY”; for the
“THRU” and “BY” options, respectively. See Remark 2. (Integer > 0 or characters;
Required)
Var Variable name to be output. See Remark 5. (Characters; Required)
Ti Times at which output is required. “THRU” and “BY”; for the “THRU” and “BY”
options, respectively. “END” indicates the end time of analysis. See Remarks 3. and 4.
(Real > 0.0 or characters; Required)
stepi Steps at which output is required. “THRU” and “BY”; for the “THRU” and “BY”
options, respectively. See Remarks 3. and 4. (Integer > 0 or characters; Required)
N The number of times an output file is written before it is closed and saved. (Integer > 0;
Required)
Remarks:
1. Default of ARC output control is set to the ARC file generation of all Eulerian elements with all
available variables.
2. Continuation lines are supported for SET, ELOUT, TIMES and STEPS. The continuation lines
must start with at least two spaces after the $S700 string. A comma (,) at the end of a line signifies
that the next line is a continuation.
3. Either STEPS or TIMES must be specified. STEPS and TIMES can not be used for the same
logical_file.
4. A list of times or steps should be in ascending order.
5. Check Chapter 11: Outputting Results in MSC Nastran SOL700 User’s Guide. It includes all Entity types,
Entity variables and Variable names.
Import Euler results:
Specifies an Euler archive that was created during a previous simulation and is used as input for a transient
analysis. The Euler archive is mapped onto a set of Euler elements that can equal in size or either finer or
coarser.
Format:
$S700 EULINIT, filename,CYCLE,MESH-ID
Example:
$S700 EULINIT,AXISYM_ALLEULER_0.ARC,60
Main Index
194 MSC Nastran Quick Reference Guide
Direct Case Control Command for SOL 700
Describer Meaning
filename The filename of the ARC file to be used.
CYCLE Cycle number.
MESH-ID The MESH ID of the target elements.
Remarks:
1. The target elements are the elements defined in the follow-up run and are the elements that will be
initialized using the import archive.
2. Both defined and imported Euler elements need to be orthogonal in the global system.
3. MESH-ID enables support for multiple Euler domains. If MESH-ID is not set the import archive
will be mapped onto all Euler elements.
4. For multi-material Euler analyses with multiple Eulerian materials all material variables in the import
archive require the material number. These material variables are MASS, DENSITY, SIE, FMAT.
The required list of variables for a MMHYDRO run are: MASSXX, SIEXX, FMATXX, XVEL,
YVEL, ZVEL. Here XX denotes the material number. FOR MMSTREN the variables TXX, TYY,
TZZ, TXY, TYZ, TZX, EFFPLS have to be added. If the multi-material run uses only one Eulerian
material then the material numbers can be left out.
5. For multi-material Euler analyses with EOSIG, the following has to be added for the IG materials:
MASS-EXX, MASS-PXX, RHO-EXX, RHO-PXX, IGBURNXX, FMAT-PXX, FMAT-PXX, SIE-
EXX, and SIE-PXX. Here XX denotes the material number
6. For the single-material Hydro Euler solver the required list is MASS, DENSITY, SIE, FMAT, and
FVUNC.
7. IF FVUNC is not included in the Import archive it is assumed that all elements in this archive are
fully uncovered. It is allowed to import such an archive in a simulation with a coupling surface. In
this follow up simulation the target elements can have uncover fractions different from one. In this
case conservative quantities of imported elements are reduced by the uncover fraction of the target
element. This is to avoid unwanted pressure increases. It simply means that any mass of the import
archive that is located in the covered part of the target elements is thrown away. As a result not all
mass in the import archive is mapped to the target elements. How much of the mass of the import
archive is mapped is shown in the out file.
8. In the OUT file, a summary is shown of all variables that are mapped.
9. In the follow-up run, the cycle and time are taken from the import archive. The results of the first
cycle of the follow-up run are determined from remapping only and has not gone through an equation
of state yet. This will happen in the next cycle
10. If needed the remapping can be checked by doing only one additional cycle in the follow-up run with
a quite small time step. Then, the follow-up OUT file shows two cycles and the results should be
almost identical to the results of the import archive. Also, material summaries in the OUT file
between first run and follow-up run should be identical. The only exceptions are the summaries of
momentum, kinetic energy, and total energy per material. For these three quantities, only the total
amounts will remain constant between first and follow-up run.
Main Index
CHAPTER 5 195
Direct Case Control Command for SOL 700
11. To remap a spherical symmetric or an axial symmetric Euler archive, the DYPARAMs
DYPARAM,SPREMAP and DYPARAM,AXREMAP have to be used. Also, the remapping of a spherical
symmetric Euler domain onto a 2-D axial symmetric Euler domain is supported.
Main Index
196 MSC Nastran Quick Reference Guide
Selects a Direct Input Fluid-Structure Coupling Matrix
A2GG (Case) Selects a Direct Input Fluid-Structure Coupling Matrix
Selects a direct input fluid-structure coupling matrix.
Format:
A2GG = name
Example:
A2GG = AGG0
Describer Meaning
name Name of a fluid-structure coupling matrix that is input on the DMIG Bulk Data entry.
Remarks:
1. DMIG entries will not be used unless selected by the A2GG Case Control command.
2. This entry must be above subcase level or in the first subcase.
3. If the A2GG Case Control command selects a DMIG entry, then Nastran will add the selected fluid-
structure coupling matrix to the computed coupling matrix. To replace the computed coupling
matrix with the selected A2GG matrix, set PARAM,ASCOUP,NO. The user may still define panels
with the panel selection procedure.
4. When filling out the DMIG entries: IFO = 1, NCOL = g-size, GJ-column index corresponds to fluid
points, CJ = 0, Gi-row index corresponds to structural points, Ci-corresponds to DOF, Ai-the area
values.
5. A2GG is supported in dynamic solutions with fluid-structure coupling.
6. Only one A2GG command should be used.
Main Index
CHAPTER 5 197
Acceleration Output Request
ACCELERATION (Case) Acceleration Output Request
Requests form and type of acceleration vector output.
Format:
NONE
SORT1 PRINT, PUNCH PRINT, PUNCH
ACCELERATION ODS = sid ,
SORT2 PLOT PLOT
ALL
ALL
REAL or IMAG PSDF ATOC ,CRMS RPRINT
RPUNCH ,CID = n
PHASE or RALL NORPRINT
NONE
Examples:
ACCELERATION=5
ACCELERTION(SORT2, PHASE)=ALL
ACCELERTION(SORT1, PRINT, PUNCH, PHASE)=17
ACCELERATION(SORT2, PRINT, PSDF, CRMS, RPUNCH)=20
ACCELERATION(PRINT, RALL, NORPRINT)=ALL
ACCELERATION (REAL, SORT2, ODS(PLOT)=ALL, PLOT, PUNCH) = 100
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load,
frequency, eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid
point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ODS Requests Operational Deflection Shape (ODS) acceleration output. See
Remark 7.
Main Index
198 MSC Nastran Quick Reference Guide
Acceleration Output Request
Describer Meaning
sid Set identification of a previously appearing SET command. Only accelerations
at grid points that appear on this SET command will be output as ODS
acceleration (Integer > 0).
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output
is in degrees.
PSDF Requests the power spectral density function be calculated for random analysis
postprocessing. Request must be made above the subcase level and RANDOM
must be selected in the Case Control Section. See Remark 5.
ATOC Requests the autocorrelation function be calculated for random analysis
postprocessing. Request must be made above the subcase level and RANDOM
must be selected in the Case Control Section. See Remark 5.
CRMS Requests the cumulative root mean square function be calculated for random
analysis postprocessing. Request must be made above the subcase level and
RANDOM must be selected in the Case Control Section. See Remark 5.
RALL Requests all of PSDF, ATOC and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level and RANDOM
must be selected in the Case Control Section. See Remark 5.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
RPUNCH Writes random analysis results in the punch file.
CID Requests printing of output coordinate system ID in printed output file (.f06).
ALL Accelerations at all points will be output.
n Set identification of a previously appearing SET command. Only accelerations
of points with identification numbers that appear on this SET command will
be output (Integer > 0).
NONE No results will be output (Default).
Remarks:
1. Acceleration output is only available for transient and frequency response problems. Acceleration is
only available for transient and frequency response problems and when response spectra is requested
in eigenvalue analysis.
2. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
3. ACCELERATION=NONE allows overriding an overall output request.
4. Acceleration results are output in the global coordinate system (see field CD on the GRID Bulk Data
entry).
Main Index
CHAPTER 5 199
Acceleration Output Request
5. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
6. Note that the CID keyword affects only grid point related output, such as displacement (DISP),
velocity (VELO), acceleration (ACCEL), OLOAD, SPCforce (SPCF), and MPCforce (MPCF). In
addition, the CID keyword needs to appear only once in a grid-related output request anywhere in
the Case Control Section to turn on the printing algorithm.
7. ODS request must work with Case Control command, ODSFREQ, which specifies a selection of the
excitation frequencies for ODS output.
Main Index
200 MSC Nastran Quick Reference Guide
Acoustic Field Point Mesh Results Output Request
ACFPMRESULT (Case) Acoustic Field Point Mesh Results Output Request
Requests output of field point mesh results. This Case Control command can be used in SOL 108 and SOL
111 or SOL 200 with ANALYSIS = DFREQ or MFREQ.
Format:
ACFPMRESULT SORT1 PRINT,PUNCH VELOCITY = YES
SORT2 PLOT NO
ALL
REAL or IMAG
POWER = YES = n
PHASE NO
NONE
Describer Meaning
SORT1 Output will be presented as tabular listing of grid points for each excitation
frequency (Default).
SORT2 Output will be presented as a tabular listing of excitation frequencies for each
grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
VELOCITY Requests output of particle velocities (Default = NO).
REAL or IMAG Requests rectangular format (real or imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase
output is in degrees.
POWER Requests output of power through field point mesh (Default = YES).
ALL Results of all field point meshes, AFPMIDs, will be processed.
Main Index
CHAPTER 5 201
Acoustic Field Point Mesh Results Output Request
Describer Meaning
n Set identification of a previously defined set of field point mesh identifiers,
AFPMIDs, Results will be processed for the field point meshes in this set only.
NONE Field point mesh results will not be processed. ACFPMRESULT = NONE
overrides an overall request.
Remark:
1. If the acoustic model references multiple PACINF entries that do not have coincident pole locations
and if the acoustic field point meshes contain element data, then a PACINFID parameter entry is
required in the bulk data for each mesh to identify the PACINF bulk data entry that is used to define
the location of the pole. Data recovery operations require that the element surface normal vector
point away from the pole location.
2. The member of set for ACFPMRESULT must be the IDs of 'BEGIN AFPM='; not GRID IDs or
element IDs under a 'BEGIN AFPM='.
3. Bulk Data entry, ACIFPRM, can be used to adjust some parameters related to infinite elements and
acoustic field point mesh.
Main Index
202 MSC Nastran Quick Reference Guide
Acoustic Power Output Request
ACPOWER (Case) Acoustic Power Output Request
Requests output of the power radiated from the wetted surface.
This Case Control command can be used in SOL 108 and SOL 111 or SOL 200 with ANALYSIS = DFREQ
or MFREQ.
Format:
ALL
ACPOWER SORT1 PRINT,PUNCH CSV = unit = n
SORT2 PLOT
NONE
Describer Meaning
SORT1 Output will be presented as a tabular listing of panels for each excitation frequency.
SORT2 Output will be presented as a tabular listing of excitation frequencies for each panel
(Default).
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
CSV Results will be written to a .CSV file. See Remark 1.
unit Unit of the .csv file as used on the ASSIGN statement.
ALL Radiated power will be processed for the wetted surface and all panels.
n Set identification of a previously defined set of panels. Radiated power will be
processed for the wetted surface and all panels in the referenced set.
NONE Radiated power will not be processed.
ACPOWER = NONE overrides an overall request.
Remarks:
1. If output to an .CSV file is requested, the file must be assigned with logical key “USERFILE” and
FORM=FORMATTED, e.g.,
Main Index
CHAPTER 5 203
Acoustic Power Output Request
ASSIGN USERFILE = ‘myfile.csv’ UNIT=50 FORM=FORMATTED STATUS=NEW
2. The mean radiated acoustic power per period (PA) is computed as:
1
P A = --- REAL v * A p
2
where, v * is the complex conjugate transpose of the complex velocity of the wetted surface, A
is the coupling matrix, and p is the acoustic pressure.
3. Nastran's ACPOWER may show different results from other software packages, such as Actran, due
to the differences in handling the fluid damping. Nastran applies fluid damping to the fluid “stiffness”
term while Actran applies fluid damping to the fluid "mass" term.
Main Index
204 MSC Nastran Quick Reference Guide
ACTRAN Trimmed Material Matrices for SOL 111 and SOL 200 with ANALYSIS = DFREQ or MFREQ
ACTRIM (Case) ACTRAN Trimmed Material Matrices for SOL 111 and SOL 200 with
ANALYSIS = DFREQ or MFREQ
Select ACTRAN trimmed material matrices.
Format:
ACTRIM = name1, name2, … namen
Example:
ACTRIM = FLOOR_F, FLOOR_R, DASH
SET 10 = FR_LH, RR_LH
ACTRIM = 10
Describer Meaning
namei Name of the ACTRAN trimmed material matrices that is input on the ACTRIM
bulk data entry, or name list.
Remarks:
1. This entry must be above subcase level or in the first subcase.
2. If the ACTRIM Case Control command selects ACTRIM bulk data entries, Nastran will add the
selected ACTRAN matrices to fluid-structure coupling problem in all subcases.
3. ACTRIM is supported in frequency response analysis for fluid-structure coupling problem and the
frequency dependent algorithm will be adopted automatically.
4. PARAM, ACSYM, YES should be set for ACTRIM (default).
5. The effect of ACTRIM will be considered in standard frequency response analysis and participation
factor analysis by PFMODE, PFPANEL and PFGRID.
Main Index
CHAPTER 5 205
Control for Nastran/ADAMS Interface
ADAMSMNF* (Case) Control for Nastran/ADAMS Interface
Control for Nastran/ADAMS Interface modal neutral file (.mnf)
Format:
NO YES
ADAMSMNF FLEXBODY = FLEXONLY =
YES NO
NO NO
ADMCHECK = ADMOUT =
YES YES
YES YES
OUTGSTRS = OUTGSTRN =
NO NO
NO NO
OUTSTRS = OUTSTRN =
YES YES
– 1.0 1.0e8
V1ORTHO = V2ORTHO =
value1 value2
PARTIAL
CONSTANT
MINVAR = FULL
NONE
RIGID
NONE MNF
YES
PSETID = setid plotel EXPORT = DB MONITOR =
NO
ALL BOTH
ACSETID = n
Example(s):
ADAMSMNF FLEXBODY = YES
SET 10 = 55, 67, 1889
ADAMSMNF FLEXBODY = YES ACSETID = 10
Main Index
206 MSC Nastran Quick Reference Guide
Control for Nastran/ADAMS Interface
Note: *Nastran/ADAMS modal stress recovery (MSR) interface is also available. See Remark 19.
NASTRAN/ADAMS MNF can be used with SOL 400 as described in Remark 21.
ADAMSMNF cannot be run in linear solution sequences with RIGID=LAGRANGE. A fatal
will be issued. The main reason is that the Lagrange multipliers are in the wrong set for the
boundary solution and resulting orthonormal modes will in general not be correct.
Describer Meaning
FLEXBODY Requests that the Nastran/ADAMS interface be executed.
NO Executes standard Nastran.
YES Executes Nastran/ADAMS interface.
FLEXONLY Requests standard DMAP solution and data recovery following Nastran/Adams
interface execution.
YES Executes only the Nastran/ADAMS interface.
NO Executes Nastran/ADAMS interface and standard DMAP solution and data
recovery.
ADMCHECK Requests Nastran/ADAMS diagnostic output.
YES Prints diagnostic output.
NO Suppresses diagnostic output.
ADMOUT Requests that the Nastran/ADAMS interface outputs Nastran .op2 files.
YES .op2 files are generated.
NO Requests that .op2 files are not generated.
OUTGSTRS Controls grid point stress output to .op2 file or .mnf or both.
YES Grid point stress is output to .op2 file or .mnf or both.
NO Grid point stress is not output to .op2 file, or .mnf file.
OUTGSTRN Controls grid point strain output to .op2 file, or .mnf or both.
YES Grid point strain is output to .op2 file or .mnf or both.
NO Grid point strain is not output to .op2 file or .mnf.
OUTSTRS Controls element stress output to .op2 file.
YES Element stress is output to .op2 file.
NO Element stress is not output to .op2 file.
OUTSTRN Controls element strain output to .op2 file.
YES Element strain is output to .op2 file.
NO Element strain is not output to .op2 file.
Main Index
CHAPTER 5 207
Control for Nastran/ADAMS Interface
Describer Meaning
V1ORTHO Lower frequency bound of the Craig-Bampton modes in cycles/unit time.
value1 Value of lower bound.
V2ORTHO Higher frequency bound of the Craig-Bampton modes in cycles/unit time.
value2 Value of higher bound.
MINVAR Requests the type of mass invariants to be computed. See Remark 3.
FULL All nine mass invariants will be calculated.
CONSTANT Only mass invariants (5-1), (5-2), (5-6), and (5-7) will be calculated.
PARTIAL All mass invariants except (5-5) and (5-9) will be calculated.
NONE No mass invariants are computed. (This option is invalid for structure/fluid
coupled system. )
RIGID No modal information is output to the .mnf file. Only units, grid point
coordinates, element connectivity, interface nodes, and invariant (5-1), (5-2), and
(5-7) data are shared in the .mnf file.
EXPORT Controls modal output.
MNF output to MNF file
DB output to Nastran database
BOTH output to Nastran database and MNF file
PSETID Selects a set of elements (including PLOTEL) whose grids are retained in the
MNF, and whose connectivity defines face geometry for ADAMS display.
setid plotel Specified in the OUTPUT(PLOT) Section of Nastran.
ALL Select all the sets defined in the OUTPUT(PLOT) Section of Nastran.
MONITOR Request or suppress output of monitor point data to Adams MNF. Default is
output (Yes). Specify No to suppress output.
ACSETID Include fluid modes from acoustic grids defined in SET in the MNF. See Remark
23.
n SET id that defines the fluid grids.
Remarks:
1. This entry represents a collection of PARAM,name,value entries. A license is required for the
Nastran/ADAMS interface.
2. ADAMSMNF FLEXBODY = YES is required to execute the Nastran/ADAMS interface, all other
ADAMSMNF items are optional. The ADAMSMNF FLEXBODY = YES must occur above subcase
level.
If you want standard Nastran data recovery in addition to that produced for ADAMS, you need to
run with FLEXONLY=NO. The orthonormal modes produced for ADAMS and the modes
produced by the standard MSC Nastran run may be viewed in Patran if run with PARAM,POST,0.
Main Index
208 MSC Nastran Quick Reference Guide
Control for Nastran/ADAMS Interface
3. The nine mass invariants are defined by Eqs. (5-1) through (5-9):
N
1
I =
11
mp (5-1)
p=1
N
2
I =
31
mp sp (5-2)
p=1
3 N
Ij
= m p p j = 1 M (5-3)
3M p=1
N
4
I = *
3M
m p s̃ p + I p p
p
(5-4)
p=1
5 N
Ij
= m p ̃ pj p j = 1 M (5-5)
3M p=1
N
6
I = T *T *
MM
mp p p + p Ip p (5-6)
p=1
N
7
I = T
33
m p s̃ p s̃ p + I p (5-7)
p=1
8 N
Ij
= m p s̃ p ̃ pj j = 1 M (5-8)
33 p=1
9 N
Ijk
= m p ̃ pj ̃ pk j k = 1 M (5-9)
33 p=1
T
where s p = xyz are the coordinates of grid point p in the basic coordinate system;
0 –z y
s̃ p = z 0 –x
–y x 0
Main Index
CHAPTER 5 209
Control for Nastran/ADAMS Interface
is the skew-symmetric vector cross product operator; p is the partitioned orthogonal modal matrix
*
that corresponds to the translational degrees-of-freedom of grid p; I p is the inertia tensor; p is the
partitioned orthogonal modal matrix that corresponds to the rotational degrees-of-freedom of grid p;
̃ pf is the skew-symmetric matrix formed for each grid translational degree-of-freedom for each
mode; M is the number of modes; and N is the number of grid points.
4. The preceding mass invariant calculation currently depends on a lumped mass formulation. The
parameter PARAM,COUPMASS should not be specified when executing the Nastran/ADAMS
interface.
5. If the CONM1 is used, M21, M31, and M32 entries should be left blank.
1 2 7
6. If PARAM,GRDPNT,value specified, mass invariants I , I , and I will be obtained from an
Nastran grid point weight generator execution in the basic system.
7. The following DTI,UNITS Bulk Data entry is required for a FLEXBODY=YES run:
Since ADAMS is not a unitless code (as is Nastran), units must be specified. A DTI Bulk Data entry
provides ‘UNITS’ (a unique identifier) input as the following example illustrates. Once identified, the
units will apply to all superelements in the model. Acceptable character input strings are listed in the
following table.
Format:
DTI UNITS 1 MASS FORCE LENGTH TIME
Example:
DTI UNITS 1 KG N M S
Main Index
210 MSC Nastran Quick Reference Guide
Control for Nastran/ADAMS Interface
Mass: Force:
kg - kilogram n - newton
lbm - pound-mass lbf - pounds-force
slug - slug kgf - kilograms-force
gram - gram ozf - ounce-force
ozm - ounce-mass dyne - dyne
klbm - kilo pound-mass (1000.lbm) kn - kilonewton
mgg - megagram klbf - kilo pound-force (1000.lbf )
slinch - 12 slugs mn - millinewton
ug - microgram un - micronewton
ng - nanogram nn - nanonewton
uston - US ton
Length: Time:
km - kilometer h - hour
m - meter min - minute
cm - centimeter s - sec
mm - millimeter ms - millisecond
mi - mile us - microsecond
ft - foot nanosec - nanosecond
in - inch d - day
um- micrometer
nm - nanometer
ang - angstrom
yd - yard
mil - milli-inch
uin - micro-inch
A note of clarification about UNITS and its relation to Nastran’s WTMASS parameter: WTMASS,
though necessary to achieve units consistency in Nastran, is ignored in the output for ADAMS. Units
data for ADAMS is supplied on the UNITS DTI entry. For example, consider a model with mass in
grams, force in Newtons, length in meters, and time in seconds. A WTMASS parameter equal to
0.001 would ensure that Nastran works with a consistent set of units (kg, N, and m). The units
reported to ADAMS should then be: “DTI, UNITS, 1, GRAM, N, M, S.”
8. OUTSTRS or OUTSTRN entries require the use of the standard Nastran STRESS= or STRAIN=
Case Control commands to produce element stress or strain. STRESS(PLOT)= or STRAIN(PLOT)=
will suppress stress or strain output to the Nastran .f06 file.
9. OUTGSTRS or OUTGSTRN entries require the use of the standard Nastran STRESS= or
STRAIN= Case Control commands used in conjunction with GPSTRESS= or GPSTRAIN= Case
Control commands to produce grid point stress or strain. GPSTRESS(PLOT)= or
GPSTRAIN(PLOT)= will suppress grid stress or strain output to the Nastran .f06 file.
Main Index
CHAPTER 5 211
Control for Nastran/ADAMS Interface
10. To reduce the finite element mesh detail for dynamic simulations, PSETID=set_entry is used to
define a set of PLOTELs or other elements used to display the component in ADAMS. If a mass
invariant computation is requested, this option can significantly reduce the size of the .mnf without
compromising accuracy in the ADAMS simulation.
If PSETID specifies an existing set from the OUTPUT(PLOT) Section of Nastran, this single set is
used explicitly to define elements to display in ADAMS. Otherwise, the Nastran Case Control
Section will be searched for a matching set ID. This matching set ID list then represents a list of
OUTPUT(PLOT) defined elements sets, the union of which will be used to define a set of PLOTELS
or other elements used to display the component in ADAMS. If the user wishes to select all of the sets
in the OUTPUT(PLOT) Section, then use PSETID=ALL.
The elements defined may include rigid element IDs. When defining these sets, do not use
EXCLUDE and EXCEPT descriptions.
If a superelement analysis is being executed, any element defined on the PSETID=set_entry that lies
entirely on the superelement boundary (i.e., all of its grids are a-set or exterior to the superelement)
must also be specified on a SEELT Bulk Data entry. The SEELT entry would not be required for part
superelements, as boundary elements stay with their component.
OUTPUT(PLOT)
SET 7722 = 10001 THRU 10010
11. The ADMOUT=YES option requires the following assignment command in the File Management
Section of the Nastran file:
ASSIGN OUTPUT2=’name.out’ STATUS=UNKNOWN UNIT=20 FORM=UNFORM
It causes .op2 files with an .out extension to be generated. FLEXBODY=YES is required with its use.
The files’ outputs are: DTI-units, SE-number of superelements (9999 if residual), SEIDX-
superelement id, ASETX-size of a-set, BGPDTS-grid location table, GEOM2S-element connections,
GEOM4S-constraints and sets, MGGEW-physical mass external sort with weight mass removed,
VAEXT-a-set partition vector, VGEXT-g-set partition vector, VAPEXT-eigenvalue size partition
vector, MAAEW-modal mass, KAAE-modal stiffness, BAAE-modal damping, RAE-modal preload,
PAE-modal loads, CMODEXT-component modes, OES1-element stress shapes, OSTR1-element
strain shapes, OGS1-grid point stress shapes, OGSTR1-grid point strain shapes, OGSIPL-grid point
physical preload stress, OGTRIPL-grid point physical preload strain. The files are output for each
superelement and their generation depends on the loading and output requests.
To ensure compatibility with the ADAMS .op2-to-.mnf translator, if the ADAMSMNF Case
Control command has the keyword ADMOUT=YES, the Nastran SYSTEM word OP2NEW is
automatically set to OP2NEW=0. This means that any .op2 files generated will have a pre-MSC
Nastran 2004 format.
12. Environment variables controlling .mnf generation can be set before submitting the Nastran job, or
by using the Nastran keyword ‘MNFWRITEOPTIONS’ which can be abbreviated to any short
unique string such as ‘MNFW’. The Nastran keyword can be entered on the NASTRAN submittal
command line or in a user .nastran rc file. For example, interior grids and elements can be removed
in the .mnf by entering, prior to the Nastran submittal, with Korn shell:
export MDI_MNFWRITE_OPTIONS=strip_face
with C shell:
Main Index
212 MSC Nastran Quick Reference Guide
Control for Nastran/ADAMS Interface
setenv MDI_MNFWRITE_OPTIONS=strip_face
Or, at the time of Nastran submittal:
nastran_submittal_command jid MNFW=strip_face
Consult the ADAMS/Flex documentation for more information on the use of environment variables
during .mnf generation.
The command
nastran_submittal_command help mnfw
will generate the description of the symbol keyword.
The command
nastran_submittal_command help all
will generate a complete set of Nastran submittal keywords.
13. .mnf naming convention is as follows: for a single superelement run, ‘jid.mnf ’; for a residual only or
multiple superelement run ‘jid_seid.mnf’, etc.; where seid1 and seid2 are the integer numbers of the
superelement. The default location of these files is the same directory as the jid.f06 file. See the
ASSIGN .mnf command to change directory location.
14. When supplying SPOINT/QSET combinations, there should be a sufficient number of
combinations to correctly capture the modal shapes. If n is the number of modes specified on the
EIGR or EIGRL Bulk Data entries and p is the number of loadcases specified, then the number of
SPOINTs(ns) should be at least ns = n + 6 + p assuming that residual flexibility is on. In
general, there cannot be too many SPOINTS, as excess ones will simply be truncated with no
performance penalty.
15. The user can have Nastran automatically specify the SPOINT/QSET by including, above the Case
Control Section the parameter PARAM,AUTOQSET,YES. In this case no SPOINT/QSET can
appear in the Bulk Data. See the PARAM,AUTOQSET description for detailed requirements or
limitations.
16. By default, MSC Nastran 2005 will create a version 6.0 MNF. ADAMS 2005 is able to read the
version 6.0 .mnf file. Earlier ADAMS versions are not able to read a 6.0 .mnf file. Nastran can be
instructed to write a backward-compatible .mnf file by submitting the Nastran job with
MNFWRITEOPTIONS=full_str. Alternatively, the user may set the environment variable
MDI_MNFWRITE_OPTIONS to ‘full_str’. See Remark 12. for more information on controlling
the .mnf format.
17. In addition to modal stiffness and modal mass matrices, the modal damping matrix may also be
output to the .mnf. The damping allowed is the standard Nastran damping matrix consisting of
B gg viscous damping, 1 w4 K4 gg structural damping, g w3 + 2 K gg
structural and Rayleigh damping, and 1 M gg Rayleigh damping. Where g is set by
PARAM,G,value, w3 is set by PARAM,W3,value; w4 is set by PARAM,W4,value; 1 is set by
PARAM,ALPHA1,value,0.;and 2 is set by PARAM,ALPHA2,value,0.
Main Index
CHAPTER 5 213
Control for Nastran/ADAMS Interface
Additionally, B2H modal damping can be included by use of the Case Control command
SDAMP=n. For part superelement or superelement analyses, modal damping for each individual part
or superelement can be controlled by PARAM,SESDAMP,YES (PARAM,SESDAMP,NO is the
default).
SESDAMP
sesdamp = no Modal damping for each superelement SDAMP TABDMP1
using the free boundary modes. SDAMP above subcase.
sesdamp = yes Modal damping for each superelement SDAMP TABDMP1
using the fixed boundary CMS modes. SDAMP in superelement subcase.
For part superelements
each part may have a PARAM,SESDAMP
The Nastran/ADAMS interface does not allow for adding modal damping to structural damping
using PARAM,KDAMP,-1.
Direct input damping may also be included with the Case Control command B2GG=n. For part
superelement or superelement analyses, use of this command with the Nastran/ADAMS interface
requires fully expanded case control.
18. If preload is present in the model, physical gridpoint stress and strain for the preload may be output
to the .mnf using standard GPSTRESS= or GPSTRAIN= commands.
If preload is generated in a SOL 106 run for a SOL 103 restart, and the physical grid point stresses
for the preload are desired for the SOL 103 MNF run, then PARAM,FLEXNLS,YES is required
above the subcase level in the SOL 106 run.
For preload generated in a SOL 106 run for a SOL 103 restart, the preload subcase must be replicated
in the first subcase of the SOL 103 run.
19. After using the Nastran/ADAMS interface to produce an .mnf file and after preforming an ADAMS
solution, it is possible to bring the ADAMS results into Nastran for modal data recovery. ADAMS
produces .op2 files for input to Nastran SOL 111 and SOL 112. The files are binary format with an
.mdf extension. The File Management Section requires an assign command for each file:
ASSIGN INPUTT2=’name.mdf’ UNIT=ni
with a DLOAD = ni in the appropriate subcase.
Also, in the Bulk Data Section, the parameter PARAM,ADMPOST = m (m = 0, by default no MSR
performed) is required. If m = 1, rigid body motion is not considered in the structural deformation.
If m = 2, rigid body motion is considered in the structural deformation.
Full details of the generation of the .mdf files and their use with Nastran are to be found in the
Nastran/ADAMS durability documentation.
20. In order to obtain consistent ADAMS results in Nastran data recovery run, when ADAMS data
brought back into Nastran SOL 111 or SOL 112, Nastran must be restarted from either of the
following two options:
a. From the original Nastran database that was produced during SOL103 MNF creation run
(created MNF is used in ADAMS run).
Main Index
214 MSC Nastran Quick Reference Guide
Control for Nastran/ADAMS Interface
b. From the external SE (*.op2) that was produced during SOL103 MNF creation run (created
MNF is used in ADAMS run). The File Management section requires to assign command for
external SE op2.
ASSIGN INPUTT2='EXTSE100.OP2' UNIT=ni
with following PARAM entries
PARAM ADMPOST,1 or 2 $
PARAM ADMEXTU , ni $ Where ni = unit # of external SE op2.
21. Typically SOL 400 is used to produce a preload for an ADAMS flexbody MNF run.
a. In the preload run the structure should be statically supported and follower loading must be
applied as a self equilibrating load set (not with SPC relationships!). In the ANALYSIS=MODES
step the structure must be a free-free structure as the resulting orthonormalization requires that
six rigid body modes be present.
In order to produce modal amplitudes and mode shapes and to ensure residual vector calculations,
SPOINTs and Q-sets are required. The SPOINTs must be included in the MAIN Bulk Data as
they are included in the overall matrix size.
A new BULK data section labeled BEGIN FLXBDY =id must be included with the run. This new
bulk section must contain the Q-set associate with the SPOINTs (in main bulk!) for modal
amplitudes and the A-set required for attachment point designation.
The example below is a typical SOL400 problem setup:
SOL 400
CEND
$ Case Control Section
$ Output ADAMSMNF REQUIRED ABOVE SUBCASE
ADAMSMNF flexbody=yes, psetid=all, outgstrs=yes, outgstrn=yes
SUBCASE 1
$ Preload
STEP 10
$ Static load and support for preload
SUBTITLE = PRELOAD
ANALYSIS = NLSTATICS
NLSTEP = 110
LOAD = 120
SPC = 130
BCONTACT = 140
SPCF = ALL
$ Generate stress and strain grid shapes
STRESS(PLOT) = ALL
STRAIN(PLOT) = ALL
GPSTRESS(PLOT) = ALL
GPSTRAIN(PLOT) = ALL
$ Modal Step for Producing MNF
$ Default: Select the end of previous load step to output
$ ADAMSMNF
STEP 20
ANALYSIS = MODES
$ Select real Eigen Value Parameters
METHOD = 210
Main Index
CHAPTER 5 215
Control for Nastran/ADAMS Interface
$ Turn residual vectors on
RESVEC = COMPONENT
STRESS(PLOT) = ALL
STRAIN(PLOT) = ALL
GPSTRESS(PLOT) = ALL
GPSTRAIN(PLOT) = ALL
b. In the above example, the SPC set in the ANALYSIS=NLSTAT must be a static (non-redundant)
constraint condition. Note that in the ANALYSIS=MODES STEP, the SPC constraint set has
been removed.
In SOL 400, the definition of the attachment a-set for identifying attachment points and for q-
set for specifying the desired number of modal amplitudes for orthonormalization is done in a
separate new FLXBDY Bulk Data Section shown below:
$ FLEXBODY Bulk section
BEGIN BULK FLXBDY = 10
$ Attachment point and component mode (A-SET) selection
ASET1,123456,1,11,111,121
QSET1,0,100001,THRU,100020
In SOL400, the ASET/ASET1 and QSET/QSET1, MUST, appear in the FLXBDY bulk data
section.
Currently, only one FLXBDY bulk data section (with a positive Flexbody ID) is supported in
SOL 400. Any non set related Bulk entries appearing in this Section will be ignored.
c. If CONTACT is required as part of the preloading for the FLEXBODY=YES run, it is Highly
Recommended that the friction option be turned on by using an appropriate BCPARA bulk data
entry setting, e.g.,
$ Select bilinear Coulomb friction for all subcases
BCPARA, 0, FTYPE, 6
If contact friction is not turned on, the tangential motion between the two parts coming into
contact will most likely not be constrained and incorrect or fatal results will occur.
d. If RIGID elements (RBE1/RBE2/RBE3/RBAR/RROD/RJOINT) are in the model, then the
Case Control RIGID= LAGRANGE (default for SOL400) should be used to avoid possible
wrong results. If an attachment point happens to touch a rigid element, the point should be
associated with the independent degree of freedom of the rigid element. Though not
recommended, if for some modeling requirement, a dependent rigid element grid is required to
be in the attachment set, the user MUST include at least one independent/reference grid for that
specific rigid element in the ASET.
22. For STRUCTURE and FLUID coupled system, METHOD(COUPLED) can be used for MNF
generation. However, all nodes on fluid face need to be coupled with structure for ADAMSMNF
otherwise, mass and inertia of moment will be incorrect in MNF.
23. ACSETID references the SET of fluid grids for which acoustic modes are exported. A small number
of fluid grids is recommended for ACSETID. A warning message is issued and acoustic modes are not
exported if this set does not exist or if ACSETID=ALL is chosen by the user.
Main Index
216 MSC Nastran Quick Reference Guide
Aeroelastic Configuration Name
AECONFIG (Case) Aeroelastic Configuration Name
Assigns the aerodynamic configuration parameter used to locate the associated datablocks on the
aerodynamic and aeroelastic databases.
Format: Assign a DBset member name
AECONFIG =config-name
Example:
Assign a MASTER file for the aerodynamic and aeroelastic DBsets
AECONFIG =PROTO_A
Describer Meaning
config-name The configuration name. This is the aerodynamic supergroup name identified
as part of the aeroelastic model (Character; Default = AEROSG2D).
Remarks:
1. Typically, the aeroelastic configuration name is specified as the aerodynamic supergroup as part of the
model generation in MSC FlightLoads.
2. If AECONFIG is not present, aerodynamic and aeroelastic datablocks will be created from the data
in the Bulk Data Section and assigned the default value AECONFIG=AEROSG2D.
3. Multiple configuration names are supported.
4. AECONFIG is typically assigned above the subcase level. If it is overridden at the subcase level, it is
necessary to attach an existing aerodynamic database.
Main Index
CHAPTER 5 217
Aerodynamic Model to be Used for the Rigid Aerodynamics
AERCONFIG (Case) Aerodynamic Model to be Used for the Rigid Aerodynamics
Enables the user to select a different mesh for the rigid portion of the aerodynamics than for the elastic
portion.
Format:
AERCONFIG=config-name
Examples:
AERC=RAERO
Describer Meaning
AERC The configuration name. This is the aerodynamic supergroup name for the
aerodynamic model that is used to create the rigid aerodynamics.
Remarks:
1. If the AERCONFIG Case Control command is not present in the subcase, the rigid portion of the
aerodynamics is based on the same AECONFIG as the flexible aerodynamics.
2. The rigid aerodynamics must be precomputed and attached from an assigned database using FMS
commands such as:
ASSIGN RMASTER = “raero.master”
DBLOCATE WHERE(AECONFIG=’rconfig’) LOGICAL=RMASTER
Main Index
218 MSC Nastran Quick Reference Guide
Aerodynamic Force Output Request
AEROF (Case) Aerodynamic Force Output Request
Requests the aerodynamic loads on aerodynamic control points.
Format:
AEROF=n
Examples:
AEROF=ALL
AEROF=5
Describer Meaning
n Set identification of a previously appearing SET command (Integer > 0).
ALL Forces at all points will be output.
Remarks:
1. This command is supported in SOLs 144, 146 (frequency response only) and 200 for
ANALYSIS=SAERO.
2. The SET command references box or body element identification numbers.
3. Output is in the units of force or moment.
4. Only aerodynamic forces on points specified on the SET command will be output.
Main Index
CHAPTER 5 219
Aerodynamic Flow Symmetry About The XY Plane
AESYMXY (Case) Aerodynamic Flow Symmetry About The XY Plane
Aerodynamic XY plane of symmetry flag. This is used to indicate whether the aerodynamic model has
symmetry with respect to the ground.
Format:
SYMMETRIC
AESYMXY = ANTISYMMETRIC
ASYMMETRIC
Example:
AESYMXY = ASYMMETRIC
Describer Meaning
SYMMETRIC Indicates that the aerodynamic model is moving in a symmetric manner
with respect to the XY plane.
ANTISYMMETRIC Indicates that the aerodynamic model is moving in an antisymmetric
manner with respect to the XY plane.
ASYMMTRIC Indicates that the aerodynamic model has no reflection about the XY
plane.
Remarks:
1. If AESYMXY is not present in case control, aerodynamic XY symmetry will be determined from the
SYMXY field of the AEROS Bulk Data entry for static aeroelastic analysis, and from the SYMXY field
of the AERO Bulk Data entry for flutter and dynamic aeroelastic analysis.
2. If AESYMXY is present above the subcase level, it is applied to all subcases until overridden.
3. SYMMETRIC implies ground effect, and ASYMMETRIC implies free air analysis.
4. Multiple aerodynamic symmetries are supported.
Main Index
220 MSC Nastran Quick Reference Guide
Aerodynamic Flow Symmetry About The XZ Plane
AESYMXZ (Case) Aerodynamic Flow Symmetry About The XZ Plane
Aerodynamic XZ plane of symmetry flag. This is used to support symmetric models about the centerline.
Format:
SYMMETRIC
AESYMXZ = ANTISYMMETRIC
ASYMMETRIC
Example:
AESYMXZ = SYMMETRIC
Describer Meaning
SYMMETRIC Indicates that a half span aerodynamic model is moving in a symmetric
manner with respect to the XZ plane.
ANTISYMMETRIC Indicates that a half span aerodynamic model is moving in an
antisymmetric manner with respect to the XZ plane.
ASYMMETRIC Indicates that a full aerodynamic model is provided (Default).
Remark:
1. If AESYMXZ is not present in case control, aerodynamic XZ symmetry will be determined from the
SYMXZ field of the AEROS Bulk Data entry for static aeroelastic analysis, and from the SYMXZ field
of the AERO Bulk Data entry for flutter and dynamic aeroelastic analysis.
2. If AESYMXZ is present above the subcase level, it is applied to all subcases until overridden.
3. Multiple aerodynamic symmetries are supported.
Main Index
CHAPTER 5 221
Defines the Reference Aerodynamic Extra Point (Controller) Vector
AEUXREF (Case) Defines the Reference Aerodynamic Extra Point (Controller) Vector
Reference UXVEC selector for the aeroelastic trim analysis. This is used to indicate an aerodynamic extra
point vector about which the stability derivatives are to be computed and printed. The stability derivatives
are the change in force due to a unit perturbation of each parameter in the aerodynamic extra point set. Due
to the nonlinear nature of the aeroelastic loads, the stability derivatives can be (but are not required to be) a
function of the point about which the slope is computed. This input defines which point is to be used in
computing the stability derivatives for printing (local slopes will be computed as needed in the trim solver).
This selection is typically done within each subcase, but a case control default can be defined by placing an
entry above the subcase level.
Format:
n
AEUXREF =
TRIM
Examples:
AEUXREF=100
AEUXREF=TRIM
Describer Meaning
n The identification number of a UXVEC Bulk Data entry that defines the point
about which stability derivatives will be computed in TRIM cases.
TRIM Indicates that the stability derivatives should be computed about the trimmed state.
Remarks:
1. If, for a particular subcase, AEUXREF is not defined, the “free stream” state will be used (that is, the
stability derivatives will be computed about zero values for all parameters). This results in upward
compatibility with the linear database paradigm.
2. Only one of a TRIM or a UXVEC ID may be specified on any given subcase. To see stability
derivatives about additional points, you must define additional trim subcases.
Main Index
222 MSC Nastran Quick Reference Guide
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
ANALYSIS (Case) Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
Specifies the type of analysis being performed for the current SUBCASE/STEP/SUBSTEP.
For its usage in NLPERF SOL 400, refer to ANALYSIS (CASE) in the Ap. C: NLPERF SOL 400.
Format:
ANALYSIS=type
Examples:
SOL 200
SUBCASE 10
ANALYSIS=STATIC
SUBCASE 20
ANALYSIS=MODES
Describer Meaning
type Analysis type. Allowable values and applicable solution sequences (Character):
STATICS Linear Static Analysis (SOLs 200 & 400)
MODES Normal Modes Analysis (SOLs 110, 111, 112, 106, 200, & 400) See
Remarks 2., 3. and 4.
BUCK Buckling (SOLs 200 and 400)
DFREQ Direct Frequency (SOLs 106, 200 and 400). See Remark 4.
MFREQ Modal Frequency (SOLs 200 and 400)
MTRAN Modal Transient (SOLs 200 and 400)
DCEIG Direct Complex - Eigenvalue Analysis (SOLs 200 & 400)
MCEIG Modal Complex - Eigenvalue Analysis (SOLs 200 & 400)
SAERO Static Aeroelasticity (SOLs 200 and 400)
DIVERGE Static Aeroelastic - Divergence (SOLs 200 & 400.
FLUTTER Flutter (SOLs 200 and 400)
HEAT Heat Transfer Analysis (SOLs 153 and 159)
STRUCTURE Structural Analysis (SOLs 153 & 159 only, default for these two
SOLs is HEAT)
HSTAT Steady State Heat Transfer (SOL 400)
HTRAN Transient Heat Transfer (SOL 400)
NLSTATICS Nonlinear Static Analysis (SOL 400). See Remark
NLTRAN Nonlinear Transient Analysis (SOL 400). See Remark 3.
HOT2COLD Hot-to-cold Analysis (SOL 106 only). See Remark 4.
Main Index
CHAPTER 5 223
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
Remarks:
1. This entry is used in solution sequences that are capable of multiple analysis types and selects the
actual analysis to be performed in the SUBCASE (or for SOL 400 the SUBCASE, STEP, or
SUBSTEP).
• For linear solution sequences SOLs 110, 111, and 112 and the nonlinear SOLs 106, 153, and
159, and for Optimization SOL 200 there can be only one ANALYSIS= per SUBCASE
• For SOL 200, EVERY SUBCASE including any superelement SUBCASE must be assigned an
ANALYSIS= Case Control command either in the explicit SUBCASE or above all SUBCASEs in
which case it defaults to all the subcases.
• For SOL 400 there can, for single physics analysis or chained multi physics analysis, be only one
ANALYSIS= per STEP.
• For SOL 400 coupled multi physics analysis there can be only one ANALYSIS= per SUBSTEP.
2. In the linear solution sequences SOLs 110, 111, 112, 145, and 146 this entry allows data recovery of
the normal modes data used in the in the complex Eigenvalue analysis, modal frequency analysis, or
modal transient analysis. All commands which control the boundary conditions (SPC, MPC, and
SUPORT) and METHOD selection should be copied inside the ANALYSIS=MODES SUBCASE
or specified above the SUBCASE level. Note in the example below, SOL111 is a frequency response
solution sequence so in the frequency response SUBCASE 2 below an ANALYSIS=MFREQ is
allowed but not required.
SOL 111
METH=40
SPC=1
SUBCASE 1 $ Normal Modes
ANALYSIS=MODES
DISP=ALL
SUBCASE 2 $ Frequency response
STRESS=ALL
DLOAD=12
FREQ=4
3. SOL 400 analysis allows for seven analysis type combinations (nonlinear single physics, nonlinear
chained physics, nonlinear coupled physics, linear perturbation analysis, standard linear physics,
nonlinear chained analysis with mesh/time change physics, and nonlinear response optimization with
ESLNRO (Equivalent Static Loads Nonlinear Response Optimization)).
If there are linear, nonlinear and perturbation subcases, the linear subcases will be solved first. The
linear subcases are reordered for processing and the output will be in the following order regardless of
original subcase number: STATICS, MODES, BUCKLING, DFREQ or MFREQ, DCEIG or
MCEIG, SAERO, FLUTTER.
The general rule is: The solutions of all SUBCASEs are independent of each other. The solution of
any STEP is a continuation of the solution of the previous STEP in the same SUBCASE. The
solutions of the SUBSTEPs occur simultaneously within a STEP (coupled analysis):
Additionally the following rules should be observed:
• All Coupled Multi-Physics steps have to come before the Single-Physics steps.
• Single-Physics steps can follow the Multi-Physics Steps.
Main Index
224 MSC Nastran Quick Reference Guide
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
• All linear perturbation steps need to be at the end after definition of all possible coupled multi-
physics steps and single-physics steps.
• The Case Control Command NLIC used for Nonlinear Initial Condition should be referenced
for further requirements between the analysis types allowed in SOL 400.
a. Nonlinear single physics: Nonlinear structures or nonlinear heat: For nonlinear structures a
ANALYSIS=NLSTAT must come before a ANALYSIS=NLTRAN. Only Statics to Transient is
allowed for structures. For heat transfer a nonlinear steady state heat transfer to a nonlinear
transient heat transfer is also allowed from V2022.3.
A structural example:
SUBCASE 1
STEP 10
ANALYSIS=NLSTAT
STEP 20
ANALYSIS=NLSTAT
STEP 30
ANALYSIS=NLTRAN
b. Nonlinear chained physics: A nonlinear steady state heat with results used for a nonlinear static
structural analysis. Only a steady state heat to a structural nonlinear Statics is allowed.
SUBCASE 1
STEP 10
ANALYSIS=HSTAT
STEP 20
ANALYSIS=NLSTAT
c. Nonlinear coupled physics: This allows for four combinations of STEP/SUBSTEP within the
SUBCASE
• ANALYSIS=HSTAT for the first SUBSTEP and ANALYSIS=NLSTAT for the second
SUBSTEP
• ANALYSIS=HTRAN for the first SUBSTEP and ANALYSIS=NLTRAN for the second
SUBSTEP
• ANALYSIS=HTRAN for the first SUBSTEP and ANALYSIS=NLSTAT for the second
SUBSTEP
• ANALYSIS=HSTAT for the first SUBSTEP and ANALYSIS=NLTRAN for the second
SUBSTEP
A coupled analysis example is:
SUBCASE 100
STEP 10
STRESS= ALL
NLSTRESS=ALL
NLSTEP=84
SUBSTEP 1
ANALYSIS=HSTAT
THERMAL=ALL
FLUX=ALL
SPC=35
LOAD=11
Main Index
CHAPTER 5 225
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
ANALYSIS=NLSTAT
SPC=2
LOAD=110
DISP(PLOT)=1456
STEP 20
ANALYSIS=NLTRAN (single physics rules follow)
d. Linear perturbation analysis: Linear perturbation analysis is run directly after a nonlinear static
(ANALYSIS=NLSTAT) analysis using additional STEP commands containing
ANALYSIS=BUCK, MODES, DFREQ, MFREQ, MTRAN, DCEIG, and MCEIG entries.It
should be noted that ANALYSIS=BUCK for linear perturbation:
It should be noted that ANALYSIS=BUCK for linear perturbation:
1. is not recommended if the model is highly nonlinear. NLBUCK Case Control command is
recommended for highly nonlinear models.
2. includes the differential stiffness in the static analysis step (ANALYSIS=NLSTAT and
ANALYSIS=STATIC) and therefore will not match the results of an equivalent SOL 105 run.
Here is an example of linear perturbation with frequency response analysis:
SOL 400
CEND
TITLE=MSC Nastran SOL 400, Linear Perturbation Analysis
SUBTI=3D General Contact with Large Displacement Turned on
$
SUBCASE 1
STEP 1
LABEL=Nonlinear Static Analysis with Contact
ANALYSIS = NLSTATIC
NLPARM = 1
BCONTACT = 1
BOUTPUT=ALL
SPC = 2
LOAD = 3
DISPLACEMENT(SORT1,REAL)=ALL
STEP 2
LABEL=Linear Perturbation, DFREQ
ANALYSIS = DFREQ
DLOAD=200
FREQ =10
AUTOSPC=YES
Main Index
226 MSC Nastran Quick Reference Guide
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
SPC = 2
DISPLACEMENT = ALL
STEP 3
LABEL=Linear Perturbation, MFREQ
ANALYSIS = MFREQ
NLIC STEP 1 LOADFAC 1.0
METHOD = 30
DLOAD=200
FREQ =10
AUTOSPC=YES
RESVEC =NO
SPC = 2
DISPLACEMENT = ALL
e. Standard linear physics: Runs can include ANALYSIS=STATICS, MODES, BUCKL, DFREQ,
MFREQ, MTRAN, DCEIG, MCEIG, SAERO, and FLUTTER. It is recommended to use
RIGID=LINEAR if the same answers are desired as in non-SOL 400. These are standard
SUBCASE type of analysis. If there are rigid elements present then RIGID=LINEAR is
recommended if the same results are desired as in SOLs 103, 105, 107, 108, 110, 111, 112, 145,
and 146.
An example is:
SUBCASE 2
LABEL=Linear Static
ANALYSIS = STATIC
LOAD = 1001
DISP = 10
STRESS = ALL
SUBCASE 101
DISP = 10
STRESS = ALL
$
STEP 11
LABEL=Nonlinear Statics, Load 1001
ANALYSIS = NLSTATIC
NLPARM = 11
LOAD = 1001
$
STEP 12
LABEL=Nonlinear Statics, Load 1005
ANALYSIS = NLSTATIC
NLPARM = 11
LOAD = 1005
$
STEP 13
LABEL=Linear Perturbation, Modes
Main Index
CHAPTER 5 227
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
ANALYSIS = MODES
METHOD = 1003
RESVEC = NO
AUTOSPC(NOPRINT) = YES
DISPL = ALL
SUBCASE 1004
LABEL=Get Linear Normal Modes
ANALYSIS = MODES
SVECTOR = ALL
METHOD = 1004
f. Nonlinear chained analysis with mesh/time change physics: A standard single physics nonlinear
steady state ANALYSIS=HSTAT or transient heat transfer ANALYSIS=HTRAN with either
scratch=no or scratch=mini on the job submittal. This is followed by a mechanical job submittal
with an ASSIGN hrun='name_of_heat_run.MASTER' and DBLOC DATABLK=(HEATDB)
LOGI=hrun in the File Management Section of the Nastran executive and an
ANALYSIS=NLSTAT or ANALYSIS=NLTRAN with a
TEMP(LOAD,HSUB,HSTEP,HTIME) in the subsequent mechanical job STEP. The
subsequent mechanical job can have both a different mesh than the heat job and different time
steps.
An example:
SOL 400 (submitted with SCRATCH=MINI from a bulk file named
Course_Mesh_Heat.dat)
CEND
SPC = 1
IC = 10
THERMAL=ALL
SUBCASE 3
STEP 4
ANALYSIS=HSTAT
NLPARM = 1
LOAD = 202
SUBCASE 10 (Note if STEP not provided STEP=1 defaulted)
ANALYSIS=HTRAN
NLPARM = 2
DLOAD = 404
BEGIN BULK
SOL 400 (Mechanical run using solution from
Course_Mesh_Heat.dat)
ASSIGN hrun= 'Course_Mesh_Heat.MASTER' (the ticks ( ' ) are
required)
DBLOC DATABLK=(HEATDB), LOGI=hrun
CEND
TEMPERATURE(INITIAL) = 1
SUBCASE 1
ANALYSIS=NLTRAN
STEP 1
= 1
SPC = 2
TEMP (LOAD, HSUBC=3) = 3
DISPLACEMENT(SORT1,REAL)=ALL
Main Index
228 MSC Nastran Quick Reference Guide
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
NLSTRESS = ALL
STRESS = ALL
STEP 2
= 2
SPC = 2
TEMP (LOAD, HSUBC=10, HTIME=0.80) = 4
DISPLACEMENT(SORT1,REAL)=ALL
NLSTRESS = ALL
STRESS = ALL
SUBCASE 2
ANALYSIS=NLTRAN
STEP 3
= 3
SPC = 2
TEMP (LOAD, HSUBC=10, HTIME=ALL) = 5
DISPLACEMENT(SORT1,REAL)=ALL
NLSTRESS = ALL
stress = all
BEGIN BULK
g. Sequential steady-state thermal analysis to transient thermal analysis (HSTAT to HTRAN) in a
single run.
In the Case Control Command section, specify ANALYSIS=HSTAT in Step 1 and
ANALYSIS=HTRAN in Step 2. Sample inputs are listed below.
TEMP(INIT) = 20
SPC = 10
THERMAL = ALL
FLUX = ALL
STEP 1
ANALYSIS = HSTAT
NLPARM = 100
LOAD = 100
STEP 2
ANALYSIS = HTRAN
TSTEPNL = 200
DLOAD = 200
h. Nonlinear response optimization with ESLNRO: A standard single physics nonlinear
ANALYSIS=NLSTAT is performed with a NASTRAN ESLOPT=1in the bulk data file. Besides
the usual model grid, loads, element data etc., the bulk data file should contain the standard SOL
200 design criteria.
An example:
NASTRAN ESLOPT=1 $
SOL 400
CEND
Main Index
CHAPTER 5 229
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
DESOBJ(MIN) = 10000
ANALYSIS = NLSTATIC
DESSUB = 1
LOAD = 300
SPC = 1
STRESS = ALL
DISP = ALL
NLPARM = 1
BEGIN BULK
4. In SOL 106, the ANALYSIS Case Control command may be used to define a ‘linear’ perturbation
analysis SUBCASE or a user input of the ‘stressed’ or deformed geometry (normal bulk data input)
and ‘unload’ the structure to determine the unstressed shape SUBCASE.
a. ‘Linear’ perturbation analysis: The ANALYSIS Case Control command may be used to define a
‘linear’ perturbation analysis SUBCASE, separate from the subcases used to load the model.
Normal modes and frequency response subcases with ANALYSIS=MODES or
ANALYSIS=DFREQ will use the final displacement results and loads from the previous nonlinear
subcase to generate the stiffness, differential stiffness, and follower force matrices for use in the
‘linear’ response analyses. Data recovery will be based on the requests above and within the
subcase.
SOL 106
CEND
$
SUBCASE 1
$ LOAD STRUCTURE
LOAD= 100
NLPARM= 100
SUBCASE 2
$ NORMAL MODES
ANALYSIS= MODES
METHOD= 100
DISP= ALL
SUBCASE 3
$ FREQUENCY RESPONSE
ANALYSIS= DFREQ
SET 100= 1 THRU 1000
DISP= 100
SUBCASE 4
$ CONTINUE LOADING STRUCTURE
LOAD= 200
NLPARM= 100
DISP= ALL
SUBCASE 5
$ NORMAL MODES AT THE NEW LOADING
ANALYSIS= MODES
Main Index
230 MSC Nastran Quick Reference Guide
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment
In the previous example, subcases 2 and 3 will use the results from subcase 1, subcase 4 will
continue the loading application, and subcase 5 will use the results from subcase 4. For the ‘linear’
analyses, the mass matrix will be based on the undeformed geometry and the damping matrix will
be generated using the deformed geometry. This will allow analyses of ‘large’ displacement results
(PARAM, LGDISP, 1), in addition to material nonlinear analyses.
b. User input of the ‘stressed’ or deformed geometry: ANALYSIS=HOT2COLD allows the user to
input the ‘stressed’ or deformed geometry (normal bulk data input) and ‘unload’ the structure to
determine the unstressed shape. This uses an iterative technique with each iteration a nonlinear
analysis. This feature will also ‘reset’ the geometry to the ‘unstressed’ position for additional
subcases. Related PARAMETERS are HTOCTOL, HTOCITS, and HTOCPRT.
An example is:
SUBCASE 1
$ UNLOAD STRUCTURE
ANALYSIS=HOT2COLD
LOAD= 100
NLPARM= 100
SUBCASE 2
$ NORMAL MODES UNLOADED STRUCTURE
ANALYSIS= MODES
METHOD= 100
DISP=ALL
SUBCASE 3
$ LOAD the STRUCTURE
LOAD= 100
NLPARM= 100
SUBCASE 4
$ NORMAL MODES OF LOADED STRUCTURE
ANALYSIS= MODES
METHOD= 100
DISP= ALL
SUBCASE 1 unloads the model. SUBCASE 2 calculates the modes of the ‘undeformed’ structure;
the differential stiffness and follower force effects will not be included. SUBCASE 3 loads the
model. SUBCASE 4 calculates the modes of the loaded structure; the differential stiffness and
follower forces effects will be included.
Main Index
CHAPTER 5 231
Aerodynamic Pressure Output Request
APRESSURE (Case) Aerodynamic Pressure Output Request
Requests the aerodynamic pressures in static aeroelastic response.
Format:
APRES = n
ALL
Examples:
APRES=ALL
APRES=6
Describer Meaning
n Set identification number of a previously appearing SET command. Only aerodynamic
pressures on the referenced aerodynamic boxes will be output (Integer > 0).
ALL Pressures at all points will be output.
Main Index
232 MSC Nastran Quick Reference Guide
Constrains Stiffness Singularities via m-sets or s-sets
AUTOSPC (Case) Constrains Stiffness Singularities via m-sets or s-sets
Requests that stiffness singularities and near singularities be automatically constrained via single or
multipoint constraints.
Format:
AUTOSPC RESIDUAL PRINT NOPUNCH SID = n EPS = r1
NOPRINT PUNCH
EPSSING = r2 SPC ZERO = YES
MPC NOZERO NO
Examples:
AUTOSPC=YES
AUTOSPC (PRINT, PUNCH, SID=100, EPS=1.E-6, MPC)=YES
Describer Meaning
RESIDUAL For SOL 400, applies AUTOSPC to both the residual structure and
superelements. See Remarks 6. and 7.
For SOL 101, applies AUTOSPC to analysis with contact. See Remark 9.
PRINT Enables the printout of a summary table of singularities
NOPRINT Disables the printout of a summary table of singularities (Default).
NOPUNCH Disables the creation of SPC or MPC Bulk Data entries in the PUNCH file
(Default).
PUNCH Generates SPC or MPC Bulk Data entry format in the PUNCH file.
SID=n Specifies a set identification number for option PUNCH (Default = 999).
EPS=r1 Identifies singularities with a stiffness ratio smaller than r1 to be automatically
constrained with single or multipoint constraints. See Remark 2. (Default = 1.E-8
or 1.E-5 if RESIDUAL describer is present).
EPSSING=r2 Identifies the potential singularities with stiffness ratios less than r2. See Remark
2. (Default=1.E-8 or 1.E-5 if RESIDUAL describer is present).
Main Index
CHAPTER 5 233
Constrains Stiffness Singularities via m-sets or s-sets
Describer Meaning
SPC Applies single-point constraints on degrees of freedom identified as singular.
(Default)
MPC Applies multipoint constraints on degrees of freedom identified as singular.
ZERO Requests the printout of singularities with zero stiffness ratios in the singularity
summary table (Default).
NOZERO Disables the printout of those singularities with zero stiffness ratios in the
singularity summary table.
Remarks:
1. AUTOSPC specifies the action to take when singularities exist in the stiffness matrix.
AUTOSPC=YES means that singularities will be constrained automatically. AUTOSPC=NO means
that singularities will not be constrained. If AUTOSPC=NO, then the user should take extra caution
analyzing the results of the grid point singularity table and the computed epsilons. See Constraint and
Mechanism Problem Identification in SubDMAP SEKR in the MSC Nastran Reference Guide for details of
singularity and mechanism identification and constraint.
2. Singularity ratios smaller than EPSSING are listed as potentially singular. If AUTOSPC=YES, then
the identified singularities with a ratio smaller than EPS will be automatically constrained. If
EPSSING has the same value as EPS, then all singularities are listed. If EPSSING is larger than EPS,
the printout of singularity ratios equal to exactly zero is suppressed. EPSSING must be greater than
or equal to EPS. If not, the program will set EPSSING equal to EPS.
3. If the PUNCH keyword is specified, then automatically generated SPCs or MPCs are placed in SPCi
or MPCi Bulk Data entry format on the PUNCH file.
4. By default, in all solution sequences except 106, 129 and 400, the auto-SPC operation is performed
for both superelements and the residual structure. (Auto-SPC processing is disabled in heat transfer
analysis). In SOLs 106, 129 and 400, the default is to perform the operation only on superelements.
If it is desired to perform auto-SPC on the residual structure in:
a. SOLs 106, then specify PARAM,AUTOSPCR,YES and is only applied to the omitted degrees-
of-freedom. The AUTOSPC command is ignored for the residual structure.
b. SOLs 129, then specify PARAM,AUTOSPCR,YES. The AUTOSPC command is ignored for
the residual structure.
c. For SOL 400, see Remarks 6. and 7.
5. The MPC option may be somewhat more expensive than the SPC option. However, it provides more
realistic structural modeling than the SPC. When the MPC option is selected, the multipoint
constraint may be applied on some degree of freedom for which the stiffness matrix is identified as
singular. If the MPC is inapplicable to some degree of freedom, the SPC is used instead.
Main Index
234 MSC Nastran Quick Reference Guide
Constrains Stiffness Singularities via m-sets or s-sets
6. For SOL 400, if RESIDUAL option is requested, the AUTOSPC operation is applied to both the
residual structure and the superelements. Without RESIDUAL option, the AUTOSPC operation is
applied to the superelements only. For default (no AUTOSPCE command), AUTOSPC operation
is not applied to the residual structure, but it is applied to the superelements. Both parameters
PARAM,AUTOSPC and PARAM,AUTOSPCR have no effect in SOL 400. Please note that the
AUTOSPC (RESIDUAL) command should not be used in the geometrical nonlinear analysis,
because it may over constrain the structural model.
7. For SOL 400, the AUTOSPC (RESIDUAL) command can be placed above the subcase level,
between subcase and step, and below the step level. The AUTOSPC operation is performed each step
of a subcase if it is required. In the following example, step 10 uses SPC option, step 20 uses MPC
option, and no AUTOSPC operation is performed for step 30.
SUBCASE 1
STEP 10
AUTOSPC(RESIDUAL,SPC) = YES
LOAD = 10
STEP 20
AUTOSPC(RESIDUAL,MPC) = YES
LOAD = 20
STEP 30
LOAD = 30
For superelements, only one AUTOSPC command can be specified. If there are multiple AUTOSPC
commands in the Case Control packet, the one for the first step of the first subcase will be used. In
the previous example, the AUTOSPC under step 10 is used.
8. For SOL 400, AUTOSPC equals YES for linear perturbation if DOMAINSOLVER ACMS is
defined in the executive system.
9. For SOL 101 with contact, user can turn on AUTOSPC by using RESIDUAL option. i.e., when
AUTOSPC(RESIDUAL)=YES, AUTOSPC will be turned on for analysis with contact.
Main Index
CHAPTER 5 235
Auxiliary Model Case Control Delimiter
AUXCASE (Case) Auxiliary Model Case Control Delimiter
Indicates (delimits) the beginning of Case Control commands for an auxiliary model in SOL 200.
Format:
AUXCASE
Examples:
AUXCAS
AUXC
Remarks:
1. AUXCASE commands must follow the primary model Case Control commands.
2. All Case Control commands following this entry are applicable until the next AUXCASE command,
or the BEGIN BULK delimiter. Commands from preceding Case Control Sections are ignored.
3. Each auxiliary model Case Control must be delimited with the AUXCASE command.
4. The AUXMODEL command is used to associate the auxiliary model Case Control with a particular
auxiliary model.
Main Index
236 MSC Nastran Quick Reference Guide
Auxiliary Model Identification Number
AUXMODEL (Case) Auxiliary Model Identification Number
References an auxiliary model for generation of boundary shapes in shape optimization.
Format:
AUXMODEL=n
Examples:
AUXMODEL=4
AUXM=4
Describer Meaning
n Auxiliary model identification number. (Integer > 0)
Remarks:
1. AUXMODEL references a particular auxiliary model for analysis and may only be specified in the
auxiliary model Case Control Section.
2. See the BEGIN BULK delimiter for the Bulk Data definition of an auxiliary model.
Main Index
CHAPTER 5 237
Control for MSC Nastran-AVL EXCITE™ Interface
AVLEXB (Case) Control for MSC Nastran-AVL EXCITE™ Interface
Control for MSC Nastran-AVL EXCITETM Interface: (1) EXB file export from SOL 103 and SOL 400, (2)
EXCITETM results import and data recovery in SOL 111, 112 and 400.
AVLEXB [EXBBODY = {YES, NO}],
[MASINVAR = {FULL, FIRST, NONE}],
[RECOVRYM = {YES, NO}],
[EXBOSET = {U1-U5, ALL}],
[OUTGSTRS = {YES, NO}],
[OUTGSTRN = {YES, NO}],
[V1ORTHO = {-1.0, value1}],
[V2ORTHO = {1.0e8, value2}],
[MFFEXP = {YES, NO}],
Format: [NOD6 = {YES, NO}],
[AVLPOST = {YES, NO}],
[POSTUNT = {INP4_UNIT_NUM}],
[EXBONLY = { YES, NO}]
Examples:
EXB file export
AVLEXB EXBBODY = YES
AVL EXCITETM results import and data recovery
AVLEXB EXBBODY=NO AVLPOST=YES POSTUNT=130
Main Index
238 MSC Nastran Quick Reference Guide
Control for MSC Nastran-AVL EXCITE™ Interface
Describer Meaning
EXBBODY Controls the output of MSC Nastran-AVL EXCITETM (Default = NO):
1. NO: Do not output AVL EXB Flexible body.
2. YES: Output AVL EXB Flexible body.
MASINVAR Requests the type of mass invariants to be computed (Default = FULL) :
1. FULL: All inertia invariants are computed.
2. FIRST: Only first order inertia invariants are computed.
3. NONE: No inertia invariants are computed.
RECOVRYM Controls the output of recovery (output transformation) matrix (Default = No) :
1. YES: Output A-set to (O+M)-set recovery matrix.
2. NO: Do not output the A-set to (O+M)-set recovery matrix.
EXBOSET Selects a set of DOFs for controlling the output of recovery matrix (Default =
ALL):
1. U1-U5: DOFs in the user defined set only are included in the O-set output
to the EXB file and the partial recovery matrix output for these DOFs.
These need to be defined in the bulk data using the USET/USET1 bulk
data entry.
2. ALL: Complete O-set in the model is retained for recovery.
OUTGSTRS Outputs Grid Point Modal Stresses (Default = NO) to the MSC Nastran op2
requires PARAM,POST,1 or PARAM,POST,-1.
OUTGSTRN Outputs Grid Point Modal Strains (Default = NO) to the MSC Nastran op2
requires PARAM,POST,1 or PARAM,POST,-1.
V1ORTHO Lower frequency bound of the Craig-Bampton modes in cycles/unit time.
value1: Value of the lower bound.
V2ORTHO Higher frequency bound of the Craig-Bampton modes in cycles/unit time.
value2: Value of higher bound.
MFFEXP Requests output of Mass matrix of O+M set (Default = No). MFFEXP = YES
requires the user to request full recovery (RECOVRYM=YES and EXBOSET =
ALL).
Main Index
CHAPTER 5 239
Control for MSC Nastran-AVL EXCITE™ Interface
Describer Meaning
NOD6 If model is pure bar/beam elements with concentrated masses, this option can
output the element dictionary table as well as element stiffness matrix (Default =
No):
1. YES: Output KDICT & KELM
2. NO: Do not output KDICT & KELM
If NOD6 = YES these parameters are automatically set MASINVAR = NONE,
RECOVRYM = NO, MFFEXP = NO, EXBOSET = YES
AVLPOST Requests data recovery using the INP4 file generated by AVL EXCITETM (Default
= No):
1. YES: Request data recovery
2. NO: data recovery
AVLPOST = YES requires EXBBODY = NO as the MSC Nastran AVL
EXCITETM interface cannot generate the EXB file and conduct data recovery in
the same run.
POSTUNT Unit number of the assigned INP4 file generated by AVL EXCITETM which will
be used for data recovery.
EXBONLY Requests standard DMAP solution and data recovery following
MSC Nastran-AVL EXCITETM interface (Default = NO):
1. NO: Proceed with standard DMAP solution and data recovery after
generating EXB file.
2. YES: Executes only MSC Nastran-AVL EXCITETM interface.
Remarks:
1. It is highly recommended that the user should run MSC Nastran for Step-1 with maximum smp
setting. Calculation of higher order mass invariants are very computation intensive; to make their
calculation faster MSC Nastran leverages efficient shared memory parallelization (SMP).
2. To minimize the data storage and enable efficient data recovery in MSC Nastran, the use of MSC
Nastran-AVL EXCITETM Interface requires the use of EXTSEOUT feature. The use of this feature
would be in its standard MSC Nastran capacity in SOL 103 or 400, e.g.:
ASSIGN OUTPUT2='crankextse.op2',UNIT=80,DELETE
...
EXTSEOUT(ASMBULK,EXTBULK,EXTID=20,DMIGOP2=80)
...
During step-1 (EXB file export), to limit the size of external superelement (SE) .op2 the user should
only request outputs for sets of physical quantities that are of interest. For, e.g., displacement and
stress on surface nodes:
Main Index
240 MSC Nastran Quick Reference Guide
Control for MSC Nastran-AVL EXCITE™ Interface
DISP(PLOT) = 101
...
STRESS(PLOT) = 102
above, the displacement and velocity can only be recovered on set 101 and stresses on set 102 during
step-2 (data recovery).
DISP=ALL, STRESS=ALL, STRAIN=ALL, etc., should be used carefully for large models during
step-1 as it could lead to significant performance degradation and large external SE .op2 file size.
3. AVL EXCITETM supports the following flexbody types which will be set automatically based on the
user inputs of AVLEXB case controls:
a. CON6: Is General large motion flexbody which is selected when the user enters “NOD6=NO”
and “MASINVAR=FULL/FIRST”.
b. SMOT: Is Small motion flexbody which is selected when the user enters “NOD6=NO” and
“MASINVAR=NONE”.
c. NOD6: Is a special flexbody model consisting of pure bar/beam (1-D) elements with
concentrated masses. It is selected when the user enters “NOD6=YES”. Here the dictionary table
for bar/beam elements for each bear/beam element shall be outputted into the EXB file. NOD6
automatically means that the following are not calculated and output into the EXB file: (1) Mass
invarients, (2) Recovery Matrix, (3) A-set Orthonormalization and associated
Eigenvalue/Eigenvector and (4) Component modes.
4. MSC Nastran does not export KELM to EXB file for NOD6 body. AVL EXCITETM v2019 provides
a utility to calculate and write KELM to existing EXB file.
5. Degree of freedom (dof) table (DOFTtable) is written to EXB file for the following dof sets:
a. A-set : Dof table for a-set are always written out to the EXB file.
b. O+M-set : Dof table for o+m-set are only written out to the EXB file if the recovery matrix is
requested by the user. In case the user selects partial recovery by specifying the EXBOSET only a
subset of o+m-set would be output in the dof Table.
6. GEOM table contains the coordinates of nodes in MSC Nastran basic coordinate system. Two table
of coordinates are always written to the EXB file: (1) A-set and (2) F+M-set.
7. OUTGSTRS or OUTGSTRN entries require the use of the standard MSC Nastran STRESS= or
STRAIN= Case Control commands used in conjunction with GPSTRESS= or GPSTRAIN= Case
Control commands to produce modal grid point stress or strain. They also require the use of
PARAM,POST,-1 or PARAM,POST,1. GSTRESS(PLOT)= or GPSTRAIN(PLOT)= will suppress
grid stress or strain output to the MSC Nastran .f06 file. The modal grid point stress or strain are not
output to the EXB file but to standard MSC Nastran .op2 file.
8. The default value of “MASINVAR = FULL” calculates all the mass invariants. In case of large models
the calculations of higher order mass invariants can be time consuming; hence, it is recommended
that the user first run with either “MASINVAR = FIRST” or “MASINVAR =NONE” to validate the
model.
9. MFFEXP = YES requests output of Mass matrix of F+M set and requires the user to request full
recovery (RECOVRYM=YES and EXBOSET = ALL).
Main Index
CHAPTER 5 241
Control for MSC Nastran-AVL EXCITE™ Interface
10. Typically SOL 400 is used to produce a preloaded AVL EXCITETM EXB file.
a. Standard SOL 400 nonlinear analysis prohibits the existence of an o-set; hence the EXTSEOUT
case control must be used (see above Remark 2.).
b. In the preload run the structure should be statically supported and follower loading must be
applied as a self equilibrating load set (not with SPC relationships!). In the ANALYSIS=MODES
step, usually, the structure should be a free-free structure to preserve its six rigid body modes. In
order to produce modal amplitudes and mode shapes and to ensure residual vector calculations,
SPOINTs and Q-sets are required.
The example below is a typical SOL400 problem setup:
ASSIGN OUTPUT2='seplt3rbe.out2',UNIT=80,DELETE
SOL 400
CEND
$
$ Initiate an Nastran-AVL-EXCITETM interface run
$ AVL REQUIRED ABOVE SUBCASE
AVLEXB EXBBODY=YES, EXBONLY=YES
SUBCASE 1
$ Preload
STEP 10
$ Static load and support for preload
SUBTITLE = PRELOAD
ANALYSIS = NLSTATICS
NLSTEP = 110
LOAD = 120
SPC = 130
BCONTACT = 140
SPCF = ALL
$ Generate stress and strain grid shapes
STRESS(PLOT) = ALL
STRAIN(PLOT) = ALL
GPSTRESS(PLOT) = ALL
GPSTRAIN(PLOT) = ALL
$ Modal Step for Producing EXB file
$ Default: Select the end of previous load step to output
$ AVL EXCITETM EXB
STEP 20
$ EXTSEOUT must be used to as Standard SOL 400 nonlinear analysis
$ prohibits the existence of an o-set
EXTSEOUT(ASMBULK,EXTBULK,EXTID=100) DMIGOP2=80
ANALYSIS = MODES
$ Select real Eigen Value Parameters
METHOD = 210
$ Turn residual vectors on
RESVEC = COMPONENT
STRESS(PLOT) = ALL
STRAIN(PLOT) = ALL
GPSTRESS(PLOT) = ALL
GPSTRAIN(PLOT) = ALL
c. In the above example, the SPC set in the ANALYSIS=NLSTAT must be a static (nonredundant)
constraint condition. Note that in the ANALYSIS=MODES STEP, the SPC constraint set has
been removed. The definition of the attachment a-set for identifying attachment points and for
q-set for specifying the desired number of modal amplitudes for orthonormalization should be
done in the main bulk data section, e.g.:
Main Index
242 MSC Nastran Quick Reference Guide
Control for MSC Nastran-AVL EXCITE™ Interface
$ Main Bulk section
$ Attachment point and component mode (A-SET) selection
ASET1,123456,1,11,111,121
QSET1,0,100001,THRU,100020
d. If CONTACT is required as part of the preloading, it is highly recommended that the friction
option be turned on by using an appropriate BCPARA bulk data entry setting, e.g.,
$ Select bilinear Coulomb friction for all subcases
BCPARA, 0, FTYPE, 6
If contact friction is not turned on, the tangential motion between the two parts coming into
contact will most likely not be constrained and incorrect or fatal results will occur.
11. The AVL EXCITETM solver expects singularities, other than the rigid body modes, of the model to
be constrained; hence, it is recommended that the user constrain singularities automatically using the
PARAM,AUTOSPC in SOL 103 and AUTOSPC (RESIDUAL) command in SOL 400.
12. After conducting the AVL EXCITETM simulation the data recovery is conducted in SOL 111, SOL
112 and SOL 400 using the EXTSEOUT feature. Using External SE to conduct data recovery would
make the data recovery faster and minimize the database size by storing only the information required
for recovery. The user interface for data recovery is straightforward requiring the attachment of the
SE databases, stored on the .op2 file, generated in the SE generation step during EXB file export
together with the ASM and PCH files.
13. During the data recovery it should be noted that PARAM,POST setting for the External SE are not
picked up from the main bulk. If physical quantities inside External SE (stresses,etc) are to be output
to op2 the user can add PARAM,POST in the case control if they want it applied globally or add
PARAM,POST manually to the External SE pch file.
14. Virtual mass is supported in MSC Nastran-AVL EXCITETM Interface by setting MASINVAR=NONE
and through the use of standard VMOPT parameter entry.
15. For STRUCTURE and FLUID coupled system, METHOD(COUPLED) can be used for EXB
generation. However, all nodes on fluid face needs to be coupled with structure for AVLEXB
otherwise, mass and inertia of moment will be incorrect in EXB.
Main Index
CHAPTER 5 243
Conical Shell Boundary Conditions
AXISYMMETRIC (Case) Conical Shell Boundary Conditions
Selects boundary conditions for an axisymmetric shell problem or specifies the existence of fluid harmonics
for hydroelastic problems.
Format:
SINE
AXISYMMETRIC = COSINE
FLUID
Example:
AXISYMMETRIC=COSINE
Describer Meaning
SINE Sine boundary conditions will be used.
COSINE Cosine boundary conditions will be used.
FLUID Existence of fluid harmonics.
Remarks:
1. This command is required for conical shell problems.
2. If this command is used for hydroelastic problems, at least one harmonic must be specified on the
AXIF command.
3. See the Surface Elements in the MSC Nastran Reference Guide for a discussion of the conical shell
problem.
4. The sine boundary condition will constrain components 1, 3, and 5 at every ring for the zero
harmonic.
5. The cosine boundary condition will constrain components 2, 4, and 6 at every ring for the zero
harmonic.
6. SPC and MPC Case Control commands may also be used to specify additional constraints. See Case
Control Commands.
Main Index
244 MSC Nastran Quick Reference Guide
Direct Input Damping Matrix Selection
B2GG (Case) Direct Input Damping Matrix Selection
Selects direct input damping matrix or matrices.
Format:
B2GG=name
Examples:
B2GG = BDMIG
B2GG = BDMIG1, BDMIG2, BDMIG3
B2GG = 1.25*BDMIG1, 1.0*BDMIG2, 0.82*BDMIG3
SET 100 = B1, B2
B2GG = 100
Describer Meaning
2
name Name of B gg matrix that is input on the DMIG Bulk Data entry, or name
list, with or without factors (see Remark 5.).
Remarks:
1. DMIG matrices will not be used unless selected.
2. Terms are added to the damping matrix before any constraints are applied.
3. The matrix must be symmetric, and field 4 on the DMIG,name Bulk Data entry must contain the
integer 6.
4. A scale factor may be applied to this input via the PARAM, CB2 entry. See Parameters.
5. The formats of the name list:
a. Names without factor.
Names separated by comma or blank.
b. Names with factors.
Each entry in the list consists of a factor, followed by a star, followed by a name. The entries are
separated by commas or blanks. The factors are real numbers. Each name must be with a factor
including 1.0.
Main Index
CHAPTER 5 245
Direct Input Damping Matrix Selection
B2PP (Case) Direct Input Damping Matrix Selection
Selects direct input damping matrix or matrices.
Format:
B2PP=name
Example:
B2PP = BDMIG
B2PP = BDMIG1, BDMIG2, BDMIG3
B2PP = 5.06*BDMIG1, 1.0*BDMIG2, 0.85*BDMIG3
B2PP = (1.25, 0.5) *BDMIG1, (1.0, 0.0) *BDMIG2, (0.82,-2.2) *BDMIG3
Describer Meaning
2
name Name of B pp matrix that is input on the DMIG or DMIAX Bulk Data entry,
or name list, with or without factors. See Remark 7. (Character).
Remarks:
1. DMIG entries will not be used unless selected.
2. B2PP is used only in dynamics problems.
3. DMIAX entries will not be used unless selected by the B2PP command.
4. The matrix must be square or symmetric, and field 4 on the DMIG,name Bulk Data entry must
contain a 1 or 6.
5. It is recommended that PARAM,AUTOSPC,NO be specified. See the Constraint and Mechanism
Problem Identification in SubDMAP SEKR in the MSC Nastran Reference Guide.
6. The matrices are additive if multiple matrices are referenced on the B2PP command.
7. The formats of the name list:
a. Names without factor
Names separated by comma or blank.
b. Names with factors.
Each entry in the list consists of a factor, followed by a star, followed by a name. The entries are
separated by commas or blanks. The factors are either all real numbers, or all complex numbers
in the form of two real numbers, separated by a comma, within parentheses as shown in the
preceding example. The first real number of the pair is the real part, and the second is the
imaginary part. Either part may be zero or blank, but not both. Mixed real numbers and complex
numbers are not allowed. Each name must be with a factor including 1.0 for real and (1.0, 0.0)
for complex.
Main Index
246 MSC Nastran Quick Reference Guide
Boundary Condition Identification
BC (Case) Boundary Condition Identification
Identifies multiple boundary conditions for normal modes, buckling, and flutter analysis in SOLs 103, 105,
145, and 200.
Format:
BC=n
Example:
BC=23
Describer Meaning
n Identification number (Integer > 0).
Remarks:
1. In SOLs 103, 105, 145, and 200, BC is required in each subcase if multiple boundary conditions are
specified for normal modes, buckling, or flutter analysis.
2. If only one boundary condition is specified, then BC does not have to be specified, and n defaults to
zero.
Main Index
CHAPTER 5 247
Contact Bodies Definition Change Selection
BCHANGE (Case) Contact Bodies Definition Change Selection
Selects the changes of the definition of contact bodies in SOL 400.
Format:
BCHANGE=n
Example:
BCHANGE=10
Describer Meaning
n Set identification of the BCHANGE Bulk Data entry, see Remark 2. (Integer > 0)
Remarks:
1. This command is used only in SOL 400 for 3D Contact analysis.
2. The default SID of the BCHANGE Bulk Data entry is defined on the BCONTACT Case Control
command if applicable; however, the SID on the BCHANGE Case Control command can overwrite
it.
Main Index
248 MSC Nastran Quick Reference Guide
Contact Model Check
BCONCHK (Case) Contact Model Check
This entry is used to activate contact model check before analysis in SOL 101, 103, 105, 107~112, 200 and
400.
With the contact model check, the initial contact status is checked and output. Displacement-like vectors
and norm distance of active nodes to the corresponding contact body and distance to the body are generated.
Sign of the distance stands for its status: positive for gap; 0.0 on surface; negative for penetration. It is a global
case control and must be above SUBCASE.
Note that BCONCHK does not support BCONTACT=ALLBODY, i.e., no contact status check is reported
when BCONTACT=ALLBODY.
Format:
RUN
PRINT PUNCH
BCONCHK = STOP
PLOT
STEP
Example:
BCONCHK(PRINT)= Run
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
RUN Execute contact model check and proceed analysis normally.
STOP Only run contact check and exit job before normal analysis.
STEP Execute contact check at each output request LOAD/TIME step.
Main Index
CHAPTER 5 249
Selects 3D Contact Surfaces
BCONTACT (Case) Selects 3D Contact Surfaces
This entry activates contact analysis and selects contact definition tables.
Overview of contact type definition:
General Contact - two bodies may come into contact and separate at any point in the simulation and the
bodies may slide along each other's surface with or without friction. The fundamental constraint is no relative
normal displacement when bodies are in contact. General contact is available in SOL 101, SOL 400 or SOL
700 only. For SOL 101, contact is the only source of nonlinearity; no large displacements, large rotations or
material nonlinearity is available.
Glued Contact - two bodies may come into contact and separate at any point in the simulation, but when in
contact there is no relative sliding. The fundamental constraint is no relative normal displacement or
tangential displacement when bodies are in contact. One can consider this equivalent to two surfaces that
have infinite friction. Note that the word glued, only refers to the constraint on the tangential behavior.
Bodies that are in glued contact may lose contact if the separation (force or stress based)criteria is exceeded,
due to Unglue or Breaking Glue.
Step Glued Contact - this is available for SOL 400 only. Step Glued contact is activated using a negative
value of IGLUE for each contact pair. It is similar to Glued Contact; there are two conditions.
1. The contact status is checked at the beginning of the step, and those nodes or segments that are in
contact remain in glued contact for the entire step. The constraints will change due to large rotations.
Furthermore, if a large tensile force or stress develop over the interface in the current loadcase, no
separation occurs for these regions which are initially in contact. Performing an Unglue of Breaking
glue is also not enforced during the step for these regions. This may be successfully used to model the
union of dissimilar meshes, where at a later time, one wants to separate the bodies (like opening of a
door).
2. When using Step Glue, conventional contact occurs for the nodes/segments of the body which are
not in contact at the beginning of the step. That means when they come into contact, they glue, but
they may separate within the same step.
Permanently Glued Contact -this is a special case of contact, where the initial configuration is used to
determine the contact constraint, and these contact changes do not change throughout the analysis. Nodes
or segments which are not initially in contact do not come into contact, and in fact may penetrate the model.
The constraint is a glue type, meaning there is no relative normal or tangential displacement. Permanent
glued may be used to connect dissimilar meshes or for simple assembly modeling when no other contact
occurs. The bodies never separate. Permanent glue should not be used in models that experience large
rotations. Permanent Glued contact is applicable to SOL 101, 103, 105, 107, 108, 109, 110, 111, 112, 144,
145, 146, SOL 200 and SOL 400. Permanent Glued contact is activated if the BCTABLE or BCTABL1 that
is referenced in the first Load case (SOL 100*) or in the first Step (SOL 200) has a value of IGLUE greater
than zero for all contact body pairs.
If the user requires conventional (general) contact for the complete simulation, but Permanent Glued contact
is invoked, i.e., all the IGLUE > 0 in the first load case, use Bulk Data entry “BCPARA,0,NLGLUE,1” to
deactivate the Permanent Glue in the contact analysis. Please note that if any IGLUE <0 in the first load case
Main Index
250 MSC Nastran Quick Reference Guide
Selects 3D Contact Surfaces
of the first load step or first subcase, Permanent Glued contact is not invoked, no matter what NLGLUE is
defined in BCPARA. i.e., NLGLUE is ignored
If the user requires conventional (general) contact for the complete simulation, but Permanent Glued contact
is invoked, useBulk Data “BCPARA,0,NLGLUE,1” to deactivate the Permanent Glue in a subsequent step.
If large rotation/deformation effect present, turning on SYSTEM(758)=2 will switch Permanently Glued
Contact to Step Glued Contact automatically in SOL 400.
Because glued contact is very useful in assembly modeling problems encountered in engineering practice,
several special cases are considered as well.
Moment Carrying Glue - For General Contact - when a node or surface comes into contact the default
condition is that constraints are only placed on the translational degrees of freedom. When Moment Carrying
Glue is activated the rotational degrees of freedom are also constrained to ensure moment carrying behavior.
This may be used with either beam elements or shell elements.
Symmetry Contact - Deformable contact with a rigid Symmetry surface. In this case no friction is allowed.
Furthermore no separation is allowed, and finally if the rigid surface is contacted by beams or shells - the
rotations are automatically constrained to satisfy the symmetry constraints. You do not need to specify any
additional input, other than specifying that the rigid surface is a SYMM body.
Format:
n
BCONTACT= ALLBODY or ALLELE or AUTO(,ctype)
NONE
SOL 700 only
Examples:
BCONTACT = 5
BCONTACT=ALLBODY
BCONTACT=AUTO,PGLUE
Describer Meaning
n Identification number of a BCTABLE, BCTABL1, BCONECT, BCHANGE, and/or
BCMOVE Bulk Data entry.
ALLBODY All bodies defined using all the BCBODY entries can potentially contact each other.
This option can only be used if it applies to all subcases. (all SOLs) In SOL 400, when
BCONTACT=ALLBODY, in any STEP, all BCBODY entries defined in the model can
potentially contact each other. In this case, no BCTABLE, BCTABL1, BCONECT is
required. See also Remark 3.
Main Index
CHAPTER 5 251
Selects 3D Contact Surfaces
Describer Meaning
NONE All contact definitions (BCTABLE, BCTABL1, BCONECT, BCBODY, and
BCBODY1) are ignored. For SOL 400 and SOL 101, if BCONTACT = NONE is
entered in any subcase, it applies for all subcases. (Default for SOLs 101 and 400.)
AUTO(,ctype) Automatic generate contact. ctype is optional. It may be
TOUCH (default) -- general touching contact;
PGLUE -- Permanently glued contact;
GGLUE -- General Glued Contact; and
SGLUE -- Step Glued Contact.
It works with bulk data section entry BCAUTOP, BCAUTOP is optional. See remark 5.
and 6.
Remarks:
1. BCONTACT is recognized in SOLs 101, 400, and 700, and under the special condition of
permanent glued contact in SOLs 103, 105, 107, 108, 109, 110, 111, 112 and 200. The standard
SOL 200 (without calling SOL 400) can only support permanent glue; but when SOL 200 calls SOL
400 (or say SOL 400 optimization), it can support all contact types.
2. For SOLs 101 and 400, if the form BCONTACT=n is applied in any loadcase (subcase or step),
Nastran looks into the Bulk Data file to get all BCTABLE, BCTABL1 or BCONECT (required),
BCMOVE (optional) and BCHANGE (optional), in the same SID=n. The user can always specify
Case Control commands, BCMOVE and/or BCHANGE, to select different SID.
BCONTACT=0 can invoke initial preload contact conditions, such that the contact bodies just touch
each other before analysis begins, but it's not necessary. If presence of BCTABLE, 0, initial contact
condition is also processed, no matter if BCONTACT=0 is given or not. (please refer to BCTABLE,
0 for more information).
The contact analysis during any loadcase is dominated by BCONTACT=n (n>0). Without the
presence of BCONTACT=n (n>0), no contact analysis works in that particular loadcase.
In SOL 400 one can have multiple contact interaction types in the model meaning general contact,
glued contact, step contact on a contact pair basis. These can change from step to step by activating
a new BCTABLE or BCTABL1.
SOL 700 allows only one BCONTACT Case Control command and only one subcase.
3. For SOLs 101 and 400, if the form BCONTACT=ALLBODY is applied in any loadcase (subcase or
step), Nastran does not look into corresponding BCTABLE, BCTABL1 or BCONECT but uses the
defaults for all entries on BCTABLE, BCONPRG or BCONPRP. If the user wants to specify
BCMOVE and/or BCHANGE Bulk Data entries, the BCMOVE and/or BCHANGE Case Control
commands must be given.
Main Index
252 MSC Nastran Quick Reference Guide
Selects 3D Contact Surfaces
4. Permanent glued contact for small deformation and rotation is initiated by BCONTACT=n pointing
to BCTABLE/BCONECT referring a valid positive IGLUE field.
If all secondary's for the BCTABLE or BCONPRG corresponding to the first loadcase (first subcase
and first step) contain IGLUE >0, permanent glued contact with small rotation condition is used for
all SECNDRY entries in all subcases and all steps unless BCPARA,0,NLGLUE,1 is specified.
If IGLUE < 0 exists, step glue is activated to support large deformation and large rotation.
5. For glue contact (PGLUE, GGLUE, and SGLUE), default is to implement the moment carrying glue
without node projection, i.e., Ensures full moment carrying glue when shells contact. The node is not
projected onto the contact body and an existing initial gap or overlap between the node and the
contacted body is not removed, as the node is not projected onto the contacted body. Unless IGLUE
is defined in BCAUTOP.
6. CTYPE can be specified by Bulk Data entry BCAUTOP also; the value of CTYPE in BCAUTOP is
used if it is specified, as it takes precedence.
7. When BCONTACT=AUTO is specified, and ACG file is generated. An ACG file (exctension .acg)
is a file consists of all generated contact bodies, contact pairs and parameters. The name of the ACG
file can be specified by ASSIGN FMS statement.
8. When BCONTACT=AUTO is specified, only elements in residual structure are used to construct
contact bodies in superelement models.
9. BEAMB in Bulk Data entry BCPARA is set to 1 when BCONTACT=AUTO is specified.
10. When BCONTACT=AUTO is specified and modules are present, the contact generation is in two
levels: individual module and across modules. For individual module, contact data generation is
activated when an BCAUTOP Bulk Data section entry exists in the module. If there is no
BCAUTOP, no contact data is generated for the module, and user supplied contact data can be used.
For across modules, contact pair generation is activated by MDBCPAR entry, and parameters are
defined by MDBCATP entry.
11. When BCONTACT=AUTO is specified, for a non-modules deck or a module with a BCAUTOP in
a modules deck, entries of BSURF, BCBODY, BCTABLE, BCTABL1, BCONECT, BCONPRP,
BCONPRG, BCPROP, BCSCAP, BCSURF and BCGRID are not allowed in the bulk data section.
In a modules deck, BSURF, BCONECT, BCONPRP, BCONPRG, BCPROP, BCSCAP, BCSURF
and BCGRID are allowed in a module if there is no BCAUTOP entry in the module.
Main Index
CHAPTER 5 253
Contact Body Movement Selection
BCMOVE (Case) Contact Body Movement Selection
Selects movement of bodies in contact in SOL 400.
Format:
BCMOVE=n
Example:
BCMOVE=10
Describer Meaning
n Set identification of the BCMOVE Bulk Data entry. (Integer > 0)
Remarks:
1. This command is used only in SOL 400 for 3D Contact analysis.
2. The default SID of the BCMOVE Bulk Data entry is defined on the BCONTACT Case Control
command if applicable; however, the SID on the BCHANGE Case Control command can overwrite
it.
Main Index
254 MSC Nastran Quick Reference Guide
Case Control and Bulk Data Delimiter
BEGIN BULK (Case) Case Control and Bulk Data Delimiter
Designates the end of the Case Control Section and/or the beginning of a Bulk Data Section.
Format:
AFPM = afpmid
ARBMODEL = arbmid
AUXMODEL = auxmind
MASSID = massid LABEL = masslabel
MODULE = moduleid APPEND LABEL = modlabel
BEGIN BULK FLXBDY = flexbody
SUPER = seid
TRMC = trimid
UDS
ACTIVE
PASSIVE
Examples:
BEGIN BULK
BEGIN AUXMODEL=22
BEGIN BULK TRMC=101
BEGIN TRMC=102
Describer Meaning
AFPM Indicates the beginning of an acoustic field point mesh Bulk Data Section.
afpmid Acoustic field point mesh identification number (Integer > 0).
ARBMODEL Indicates the beginning of a finite element model FEM for an arbitrary beam cross-
section.
arbmid FEM identification number (Integer > 0).
AUXMODEL Indicates the beginning of an auxiliary model Bulk Data Section.
auxmid Auxiliary model identification number (Integer > 0).
FLXBDY Indicates the beginning of a Adams/Nastran MNF flexbody Bulk Data Section for
SOL400 analysis.
flexbody Flexbody MNF component identification number (Integer>0; Required). Component
usually consists of ASET and QSET description for attachment points.
Main Index
CHAPTER 5 255
Case Control and Bulk Data Delimiter
Describer Meaning
MASSID Indicates the beginning of the incremental mass case Bulk Data Section.
massid Incremental mass case identification number (Integer>0; Required).
LABEL Indicates a massid label.
MODULE Indicates the beginning of a Module Bulk Data section
moduleid Module identification number (Integer>0).See Remark 11.
APPEND Indicates append data to a module.
LABEL Indicates a Module label. This option will be converted to an MDLABEL Bulk Data
entry in the main Bulk Data section.
modlabel Module label.
SUPER Indicates the beginning of partitioned superelement Bulk Data Section.
seid Superelement identification number (Integer > 0).
TRMC Indicates the beginning of Bulk Data Section for a trim component model. See
Remark 9.
trimid Trim component identification number (Integer>0; Required).
UDS Indicates the beginning of user defined subroutine section.
ACTIVE Indicates the beginning of an active sub-model Bulk Data Section for Single-step TPA.
See Remark 13.
PASSIVE Indicates the beginning of a passive sub-model Bulk Data Section for Single-step TPA.
See Remark 13.
Remarks:
1. BEGIN BULK is not required but it is highly recommended that the user supply it. If not specified,
then the program will automatically insert one, before the first unique bulk type entry. Parameters are
not considered unique bulk type entries so automatic BEGIN BULK inclusion will come after any
parameter that precedes entries unique to bulk.
2. For an auxiliary model, AUXMID is referenced by the AUXMODEL Case Control command.
3. Partitioned Bulk Data Sections defined by BEGIN SUPER are used to define only one superelement
(Part Superelement). Bulk Data commands such as SESET, which define list superelements are
ignored in partitioned Bulk Data Sections.
Superelements specified by a BEGIN SUPER entry can be automatically attached to other
superelements based on relative locations of grid points. For connection to the downstream
superelement, the global coordinate directions of the attachment grid points of the upstream
superelement will be internally transformed to the global coordinate directions of the grid points of
the downstream superelement. For displacement data recovery, the output will be in the original
global coordinate directions.
Main Index
256 MSC Nastran Quick Reference Guide
Case Control and Bulk Data Delimiter
4. An acoustic field point mesh section defined by BEGIN AFPM is used to define one acoustic field
point mesh. Acoustic field point meshes are used for postprocessing of acoustic results in the far field
only; i.e., at locations within the acoustic infinite elements.
5. The BEGIN SUPER, BEGIN AUXMODEL, and BEGIN AFPM Bulk Data entries must lie
between BEGIN BULK and ENDDATA.
6. When employing part superelements using the BEGIN BULK SUPER (or BEGIN SUPER) entry,
it should be noted that any parameters that are specified in the main Bulk Data Section apply only to
the residual and not to any of the part superelements. Accordingly, to apply certain parameters to all
of the superelements, they must be specified in the Case Control Section, or explicitly in all of the
BEGIN BULK SUPER (or BEGIN SUPER) portions of the Bulk Data. A common example of such
a parameter specification is PARAM,POST, which is used to request postprocessing of results.
7. arbmid can be referenced under the OUTM keyword of the PBMSECT Bulk Data entry to define
the geometry of the arbitrary beam cross-section.
8. For model using user defined subroutines, the subroutines can be put in the UDS section. Nastran
can build user service from the subroutines using command line keyword uds=model. See the
document User Defined Service User's Guide for detail.
9. The parameter WTMASS is supported for trim components with a PARAM, WTMASS, value in
each BEGIN TRMC=n Bulk Data.
10. BEGIN MODULE command can only be specified after the BEGIN BULK or an ENDMODULE
command has already been specified. In other words, a Module Bulk Data section cannot be nested
inside another Module’s Bulk Data section.
11. The same module identification number can appear multiple times if APPEND is specified, otherwise
a user fatal message will be issued.
12. For BEGIN [BULK] AFPM, Bulk Data entry, ACIFPRM, can be used to adjust some parameters
related to infinite elements and acoustic field point mesh.
13. The active sub-model contains the associated connector elements, such as CBUSH and RBEi,
connecting the interface GRID points from the passive sub-model to the active side. The passive sub-
model contains the interface GRID points, defined by the Bulk Data entry, TPADEFN. Case
Control command, TPASET, must be specified for Single-step TPA.
Main Index
CHAPTER 5 257
BAR/BEAM end load Subcase Selection
BENDL (Case) BAR/BEAM end load Subcase Selection
Function to calculate bar end loads and shear flow.
Format:
ALL
YES
BENDL PRINT = = n
NO
NONE
Examples:
To output a table of bar end loads/shear flows.
BENDL = ALL
To output a table of bar end loads/shear flows and print table to F06.
BENDL (PRINT=YES) = ALL
Describer Meaning
PRINT Prints bar end loads and panel shear flow to the F06 file.
YES BAR/BEAM end loads and associated CSHEAR, CQUAD4 and CTRIA3 panel shear
flows will be printed.
NO BAR/BEAM end loads and associated CSHEAR, CQUAD4 and CTRIA3 panel shear
flows will not be printed. (Default)
ALL Select all bar/beam/rod type elements associated with “Shell” panels.
n Identification of a previously defined SET listing “Flange/Boom” elements.
NONE Turn off BENDL in selected subcases.
Remarks:
1. A BENDL Case Control Command is to appear in any subcase for which Bar End Loads and Panel
shear flows are required. This entry is only applicable in SOL101 or ANALYSIS=STATIC.
2. The presence of BENDL in a linear statics run will automatically turn on GPFORCE=ALL as well as
PARAM, NOELOF, 1.
3. Only CSHEAR, CQUAD4, CTRIA3, CQUADR, and CTRIAR panels will contribute to shear flow
and bar end load calculations.
4. Include MDLPRM HDF5 to output OUTSFLOW data block to the HDF5 output file.
Main Index
258 MSC Nastran Quick Reference Guide
BAR/BEAM end load Subcase Selection
5. The following figure shows a typical bar end load and shear flow panel.
6. Print and table FORMAT is:
B A R E N D L O A D S A P P R O X I M A T I O N S ( C B A R )
ELEMENT TOTAL END LOADS
ID. END 1 END 2
6 -1.994413E+03 -1.136868E-13
11 2.082592E+03 3.638604E-01
16 -4.721992E+02 -7.329887E+01
21 4.984904E+02 -4.987337E+02
B A R E N D L O A D S S H E A R F L O W A P P R O X I M A T I O N S ( C
Q U A D 4 )
ELEMENT ID. SHEAR 12 SHEAR 23 SHEAR 34 SHEAR 41
1 9.972063E+01 -2.493060E+02 -9.972063E+01 3.989003E+01
Main Index
CHAPTER 5 259
Line Contact or 3D Contact Output Requests
BOUTPUT (Case) Line Contact or 3D Contact Output Requests
Selects contact regions for output.
Format:
ALL
SORT1 PRINT, PUNCH
BOUTPUT ( ) = n
SORT2 PLOT
NONE
Examples:
BOUTPUT=ALL
BOUTPUT=5
Describer Meaning
SORT1 Output is presented as a tabular listing of secondary nodes for each load or time
depending on the solution sequence.
SORT2 Output is presented as a tabular listing of load or time for each secondary node.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Histories of all the secondary nodes (all nodes for 3D Contact) listed in all the
BOUTPUT Bulk Data entries are output. If no BOUTPUT Bulk Data entries are
specified, histories of all the secondary nodes in all the contact regions are output.
n Set identification of previously appearing SET command. Only contact regions with
identification numbers that appear on the SET command are selected for output. If
there is a BOUTPUT Bulk Data entry for a contact region selected via the set
command, histories for secondary nodes listed in the Bulk Data entry are output. If
there is no BOUTPUT Bulk Data entry for a contact region selected via the set
command, histories for all the secondary nodes in that contact region are output.
NONE Result histories for secondary nodes are not calculated or output.
Main Index
260 MSC Nastran Quick Reference Guide
Line Contact or 3D Contact Output Requests
Remarks:
1. BOUTPUT is processed in SOLs 101, 106, 129, 153, 159 and 400 only.
For other solution sequences, only the initial contact status may be output when presence of
BCTABLE or BCTABL1 with ID=0.
2. SORT1 is the default in SOLs 106 and 153. SORT2 is the default in SOLs 129 and 159.
3. Only SORT1 is available for 3D Contact.
4. The initial contact status may be output when presence of BCTABLE/ID=0. Please note that all the
contact force/stress in the initial state are zero. Only the contact status is relevant.
Main Index
CHAPTER 5 261
Brake Squeal Analysis Data Selection
BSQUEAL (Case) Brake Squeal Analysis Data Selection
Selects data for brake squeal analysis in SOL 400.
Note that ACMODL is not supported in NLPERF SOL 400.
Format:
BSQUEAL= n
Example:
BSQUEAL=10
Describer Meaning
n Set identification number of a BSQUEAL Bulk Data entry (Integer > 0).
Remark:
1. This command is used only in SOL 400 for brake squeal analysis with 3D Contact.
2. This command is not available with segment-to-segment contact.
Main Index
262 MSC Nastran Quick Reference Guide
Campbell Diagram Parameters
CAMPBELL (Case) Campbell Diagram Parameters
Specifies Campbell Diagram parameters.
Format:
CAMPBELL= n
Example:
CAMPBELL= 10
Describer Meaning
n Identification number of a CAMPBLL Bulk Data entry (Integer > 0).
Remark:
1. CAMPBELL option is supported for SOL 107, SOL110, SOL 200 and SOL 400 analysis.
2. When there is a Case Control request for Campbell diagram, the selected RGYRO Bulk Data entry
must have the ASYNC option specified in its SYNCFLG field (Field 3). Otherwise, the program
terminates the execution with an appropriate fatal message.
Main Index
CHAPTER 5 263
Static Load Request for Upstream Superelement Loads
CLOAD (Case) Static Load Request for Upstream Superelement Loads
Requests a CLOAD Bulk Data entry that defines a list of superelement loads and their scale factors in
nonlinear static analysis only.
Format:
CLOAD=n
Example:
CLOAD=15
Describer Meaning
n Identification number of a unique CLOAD Bulk Data entry (Integer > 0).
Remarks:
1. This command may only appear in the residual structure subcases (see the Case Control command,
SUPER (Case)) and, if used, it must be specified in all of them.
2. The CLOAD Bulk Data entry must reference previously processed LSEQ (load sequence) Bulk Data
that was requested by LOADSET Case Control commands on the upstream (SUPER 0)
subcases.
3. The resulting load is added to those produced by LOAD and TEMP(LOAD) Case Control
commands in the residual structure subcases.
Main Index
264 MSC Nastran Quick Reference Guide
Complex Eigenvalue Extraction Method Selection
CMETHOD (Case) Complex Eigenvalue Extraction Method Selection
Selects complex eigenvalue extraction parameters.
Format:
CMETHOD=n
Example:
CMETHOD=77
Describer Meaning
n Set identification of EIGC (and EIGP) Bulk Data entry (Integer > 0).
Remarks:
1. The CMETHOD command must be specified in order to compute complex eigenvalues.
2. See description of the parameter, UNSYMF, to perform complex eigenvalue analysis in SOL 106.
Main Index
CHAPTER 5 265
Component Modal Synthesis Energy Output Request
CMSENRGY (Case) Component Modal Synthesis Energy Output Request
Requests the form and type of component modal synthesis (CMS) energy output.
Format:
MODE
CMSENRGY( PRINT, PUNCH REAL or IMAG ESORT = ASCEND
PLOT PHASE
RATIO
BOTH ALL ALL
RESPONSE = MODAL CMSE = NONE CMKE = NONE
TOTAL TOTAL
FORCED QSET QSET
ALL ALL
CMDE = NONE FILTER = 0.001 TOPN = m = n
TOTAL fratio
QSET NONE
Example:
CMSENRGY (PHASE,RESPONSE=FORCED,CMSE=TOTAL,CMKE=QSET) = ALL
SET 1001 = 10,40
CMSENRGY (PUNCH,PRINT,RESPONSE=BOTH,CMSE=ALL,FILTER=0.01) = 1001
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ESORT Keyword selecting one of the output sorting options: MODE, ASCEND, or RATIO.
Main Index
266 MSC Nastran Quick Reference Guide
Component Modal Synthesis Energy Output Request
Describer Meaning
MODE Results are output in order of increasing CMS natural mode number.
ASCEND Results are output in order of increasing energy ratio magnitudes.
RATIO Results are output in order of decreasing energy ratio magnitudes.
RESPONSE Keyword selecting the types of results to be produced.
BOTH Requests output for both free and forced response solutions.
MODAL Specifies that output is to be generated for the free (or real eigenvalue)
response solution.
FORCED Specifies that output is to be generated for the forced response (modal
frequency or modal transient) solution.
CMSE Keyword requesting output of CMS strain energy ratios.
CMKE Keyword requesting output of CMS kinetic energy ratios.
CMDE Keyword requesting output of CMS damping energy ratios.
ALL Requests both TOTAL and QSET output.
NONE Requests that no CMS energy output be generated.
TOTAL Requests CMS energy ratio totals in all component modes of a
superelement.
QSET Requests CMS energy ratios for individual component modes.
FILTER Keyword specifying the value of the printed output data filter.
fratio Value of output filter ratio (Default = 0.001).
TOPN Keyword specifying the number of largest CMS energy ratios to be output.
m The number of largest CMS energy ratios to be output (Default is all
ratios).
n Results for superelement IDs in SET n will be output.
ALL Results for all recovered superelements will be output.
NONE No CMS energy ratios will be output.
Remarks:
1. The CMSENRGY command may be requested in the modal solution sequences (SOLs 110, 111,
112, 145, 146, 200) and the real eigenvalue analysis solution sequences (SOLs 103 and 106). It is
intended for use when superelements are defined and component modal synthesis techniques are
employed. (See the MODALKE and MODALSE Case Control commands for other options.)
2. ESORT, FILTER, and TOPN describers apply only to QSET results output. TOTAL results output
is always in increasing order of superelement ID number.
3. QSET CMS energy ratios are output in increasing order of component mode number unless the
ESORT keyword specifies a particular sorting order. If a sorting order is specified, the magnitude of
the energy ratio is sorted. DESCEND can be used as a synonym for RATIO.
Main Index
CHAPTER 5 267
Component Modal Synthesis Energy Output Request
4. The FILTER keyword specifies an absolute value that is used to limit the amount of printed output
produced. It is applied to the magnitude of the CMS energy ratio. If the CMS energy ratio magnitude
is less than fratio for any natural mode, no output for that natural mode is produced. THRESH can
be used as a synonym for FILTER.
5. In order to obtain unforced response (RESPONSE=BOTH or MODAL) output in SOL 111 and
SOL 112, a subcase containing the ANALYSIS = MODES option must be present.
6. For modal transient response solution sequences, response quantities are real numbers. There are no
imaginary terms. Therefore, polar representations of the data have no meaning.
Main Index
268 MSC Nastran Quick Reference Guide
Select CoSIM Service
COSMSEL (Case) Select CoSIM Service
Activates Co-Simulation service and select the definition of co-simulation.
Note that COSMSEL is not supported in NLPERF SOL 400.
Format:
COSMSEL = n
Example:
COSMSEL = 21
Describer Meaning
n Identification number of a COSMSEL Bulk Data entry.
Remark:
1. COSMSEL is recognized in SOL 400 only.
Main Index
CHAPTER 5 269
Aerodynamic Control Surface Schedule
CSSCHD (Case) Aerodynamic Control Surface Schedule
Selects control system schedule information.
Format:
CSSCHD = n
Example:
CSSCHD=10
Describer Meaning
n Set identification of a control system schedule that appears on a CSSCHD Bulk
Data entry.
Remark:
1. One or more CSSCHD Bulk Data entries can be invoked by this Case Control command.
Main Index
270 MSC Nastran Quick Reference Guide
Saving Control Parameter of Datablocks for Advanced Nonlinear Elements
DBSAVE (Case) Saving Control Parameter of Datablocks for Advanced Nonlinear Elements
Selects saving of datablocks of advanced nonlinear elements for static and transient nonlinear analysis in SOL
400.
Format:
DBSAVE=n
Example:
DBSAVE =2
SUBCASE=1
ANALYSIS=HSTAT
SUBCASE=2
ANALYSIS=NLSTAT
DBSAVE = -1
SUBCASE=1
STEP = 1
ANALYSIS=NLSTAT
DBSAVE = 1
STEP = 2
ANALYSIS=NLSTAT
SUBCASE=2
ANALYSIS=NLSTAT
SUBCASE=3
ANALYSIS=NLSTAT
SUBCASE=4
ANALYSIS=NLSTAT
Describer Meaning
n selected value to control saving of datablocks of advanced nonlinear elements (Integer > =
-1).(Default=0)
-1 No datablocks of advanced nonlinear elements is saved
0 Saving datablocks of advanced nonlinear elements at the end of each loadcase
>0 Saving datablocks of advanced nonlinear elements at the every nth output
request of results
Remarks:
1. DBSAVE can be applied above all the subcases, within subcases, and steps. DBSAVE above all the
subcases is going to be applied to all the subcases.
2. If DBSAVE is present both above subcase and in step, the DBSAVE in step is dominant and used to
control datablocks saving in this step.
3. When DBSAVE=-1, advanced nonlinear element can't be used in Linear Perturbation or other
analysis step with NLIC.
Main Index
CHAPTER 5 271
Elements to be Deactivated for SOL 400 Analysis
DEACTEL (Case) Elements to be Deactivated for SOL 400 Analysis
Indicates which DEACTEL Bulk Data entry is used to control the elements to be deactivated in a single
physics job, or a particular physics pass of a coupled job. SOL 400 for NLSTATIC, and NLTRAN, as well
Perturbation analyses only.
Format:
DEACTEL=N
Example:
DEACTEL=2
Describer Meaning
N ID of a matching DEACTEL Bulk Data entry specifying the elements to be
deactivated.
Remarks:
1. Usage is limited to the first subcase (or prior to it), the first step or the first substep of a particular
physics pass. Elements are deactivated at the start of the job or the start of the particular physics pass
and remain deactivated for the entire job.
2. Elements deactivated can not be reactivated at later stage in the analysis.
Main Index
272 MSC Nastran Quick Reference Guide
Element Deformation Static Load
DEFORM (Case) Element Deformation Static Load
Selects the element deformation set.
Format:
DEFORM=n
Example:
DEFORM=27
Describer Meaning
n Set identification number of DEFORM Bulk Data entries (Integer > 0).
Remarks:
1. DEFORM Bulk Data entries will not be used unless selected by the DEFORM command in the Case
Control Section.
2. DEFORM is only applicable in linear statics, inertia relief, differential stiffness, and buckling
problems (SOLs 101, 105, 114, and 200), and will produce a fatal message in other solution
sequences.
3. The total load applied will be the sum of external (LOAD), thermal (TEMP(LOAD)), element
deformation (DEFORM), and constrained displacement loads (SPC, SPCD).
4. Static, thermal, and element deformation loads should have unique identification numbers.
5. In the superelement solution sequences, if the DEFORM Case Control command is used in a cold
start, it must also be specified in the restart.
Main Index
CHAPTER 5 273
Request Design Constraints at the Global Level
DESGLB (Case) Request Design Constraints at the Global Level
Selects the design constraints to be applied at the global level in a design optimization task.
Note that DESGLB is not supported in NLPERF SOL 400.
Format:
DESGLB=n
Examples:
DESGLB=10
DESG=25
Describer Meaning
n Set identification of a set of DCONSTR or a DCONADD Bulk Data entry
identification number (Integer > 0).
Remarks:
1. If used, this command must occur before the first subcase.
2. The DESGLB Case Control command is optional and invokes constraints that are to be applied
independently of a particular subcase. These constraints could be based on responses that are
independent of subcases (e.g., WEIGHT, VOLUME, WMPID, FRMASS, and FATIGUE). The
DESGLB command must be used when applying constraints to FRMASS, WMPID and FATIGUE
responses.
3. The DESGLB Case Control command can be used to invoke constraints that are not functions of
DRESP1 entries; e.g., DRESP2 responses that are not functions of DRESP1 responses are subcase
independent.
4. Constraints that are applied to responses that span subcases through the use of the DRSPAN
command must be invoked using the DESGLB command.
Main Index
274 MSC Nastran Quick Reference Guide
Design Model Name
DESMOD (Case) Design Model Name
Assigns the design model parameter used to locate the associated datablocks for merging of two or more SOL
200 models using the MultiOpt application.
Note that DESMOD is not supported in NLPERF SOL 400.
Format:
DESMOD=name
Examples:
DESMOD=FLUTTER
Describer Meaning
Name User-specified name to designate the model. (The first 8 characters must be
unique)
Remarks:
1. The name is an attribute of the datablocks that require merging across models in order to perform a
simultaneous design.
2. The parameter is only used with MultiOpt, that merges simultaneous models.
3. A unique value of DESMOD is needed for each model invoked by MultiOpt.
4. If DESMOD is used in a SOL 200 input file that is not being used in MultiOpt, it will result in a
fatal error.
5. MultiOpt supports Multi Model Optimization (MMO) and Global Optimization (GO), see Design
Sensitivity and Optimization User’s Guide
Main Index
CHAPTER 5 275
Design Objective
DESOBJ (Case) Design Objective
Selects the DRESP1, DRESP2 or DRESP3 entry to be used as the design objective.
Note that DESOBJ is not supported in NLPERF SOL 400.
Format:
DESOBJ ( MAX ) = n
MIN
Examples:
DESOBJ=10
DESO=25
Describer Meaning
MIN Specifies that the objective is to be minimized.
MAX Specifies that the objective is to be maximized.
n Set identification number of a DRESP1, DRESP2 or DRESP3 Bulk Data entry
(Integer > 0).
Remarks:
1. A DESOBJ command is required for a design optimization task and is optional for a sensitivity task.
Only one DESOBJ command may appear in a Case Control Section.
2. The referenced DRESPi entry must define a scalar response (e.g., WEIGHT or VOLUME).
3. If the DESOBJ command refers to a global response, such as weight, it should appear above the first
subcase. If the DESOBJ command refers to a subcase-dependent response such as an element stress,
it should appear in that subcase. If it refers to a subcase dependent response but is inserted above the
first subcase, it will select the response from the first subcase for the objective and ignore the responses
in subsequent subcases.
4. Using DREPS2 with weight factors, SOL200 can support multiple objective optimization.
5. MSC Nastran MultiOpt utility supports Multi Model Optimization (MMO) and Global
Optimization (GO), see Design Sensitivity and Optimization User’s Guide
Main Index
276 MSC Nastran Quick Reference Guide
Design Constraints Request at the Subcase Level
DESSUB (Case) Design Constraints Request at the Subcase Level
Selects the design constraints to be used in a design optimization task for the current subcase.
Note that DESSUB is not supported in NLPERF SOL 400.
Format:
DESSUB=n
Examples:
DESSUB=10
DESS=25
Describer Meaning
n Set identification of a set of DCONSTR and/or a DCONADD Bulk Data entry
identification number (Integer > 0).
Remarks:
1. A DESSUB Case Control command is required for every subcase for which constraints are to be
applied. An exception to this is ‘global constraints’, which are selected by the DESGLB Case Control
command.
2. All DCONSTR and DCONADD Bulk Data entries with the selected set ID will be used.
3. Constraints cannot be applied to the FRMASS, FATIGUE, or FRFTG response using the DESSSUB
command. Use the DESGLB command instead.
Main Index
CHAPTER 5 277
Design Variable Selection
DESVAR (Case) Design Variable Selection
Selects a set of DESVAR entries for the design set to be used.
Note that DESVAR is not supported in NLPERF SOL 400.
Format:
DESVAR = ALL
n
Example:
DESVAR=10
Describer Meaning
n Set identification of a previously appearing SET command (Integer > 0).
Only DESVAR Case Control commands with IDs that appear on this SET
command will be used in the SOL 200 design task.
Remarks:
1. Only one DESVAR Case Control command may appear in the Case Control Section and should
appear above all subcase commands.
2. The DESVAR Case Control command is optional. If it is absent, all DESVAR Bulk Data entries will
be used.
Main Index
278 MSC Nastran Quick Reference Guide
Displacement Output Request
DISPLACEMENT (Case) Displacement Output Request
Requests the form and type of displacement or pressure vector output. Note: PRESSURE and VECTOR are
equivalent commands.
Format:
NONE
DISPLACEMENT ( SORT1 PRINT, PUNCH ODS PRINT, PUNCH = sid
SORT2 PLOT PLOT
ALL
REAL or IMAG PSDF, ATOC, CRMS RPRINT RPUNCH CID ----------------------------------------------------
TM = f -
PHASE RALL NORPRINT T1 = f T2 = f T3 = f
STRUCTURE
ALL
FLUID
RM = f - [CONNECTOR = ALL ,
----------------------------------------------------- = n
R1 = f R2 = f R3 = f m BOTH
NONE
NONE
Examples:
DISPLACEMENT=5
DISPLACEMENTS(REAL)=ALL
DISPLACEMENT(SORT2, PUNCH, REAL)=ALL
DISPLACEMENT(SORT2, PRINT, PSDF, CRMS, RPUNCH)=20
DISPLACEMENT(PRINT, RALL, NORPRINT)=ALL
DISP (T1=1.-3, T3=1.-2) = ALL
DISP (TM=1.-3, PRINT,PLOT) = ALL
DISP (TM=1.-3,PRINT,PLOT,SORT2) = 20
DISP (CONN=23)=54
DISPLACEMENT(PLOT,PRINT,BOTH) = ALL
DISP (REAL, SORT2, ODS(PLOT)=ALL, PLOT, PUNCH) = 100
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load, frequency,
eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of load, frequency, or time for each grid
point.
Main Index
CHAPTER 5 279
Displacement Output Request
Describer Meaning
PRINT or (blank) Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PUNCH X X*
PLOT X X*
X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ODS Requests Operational Deflection Shape (ODS) acceleration output. See Remark 12.
sid Set identification of a previously appearing SET command. Only accelerations at
grid points that appear on this SET command will be output as ODS acceleration
(Integer > 0).
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
PSDF Requests that the power spectral density function be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM must
be selected in the Case Control Section. See Remark 6.
ATOC Requests that the autocorrelation function be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM must
be selected in the Case Control Section. See Remark 6.
CRMS Requests that the cumulative root mean square function be calculated for random
analysis postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in the Case Control Section. See Remark 6.
RALL Request that all of PSDF, ATOC, and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM must
be selected in the Case Control Section. See Remark 6.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
RPUNCH Writes random analysis results in the punch file.
CID Requests printing of output coordinate system ID in printed output file, (.f06).
TM Translational magnitude filter. See Remark 8.
T1, T2, T3 Translational component filters. See Remark 8.
RM Rotational magnitude filters. See Remark 8.
R1, R2, R3 Rotational component filters. See Remark 8.
Main Index
280 MSC Nastran Quick Reference Guide
Displacement Output Request
Describer Meaning
F Filter value (Real > 0.0). See Remark 8.
CONNECTOR A set of CWELD or CFAST, elements are defined from which auxiliary grids will be
determined for output post-processing for displacement display in the basic system.
This command produces the following actions:
The auxiliary point “grids” determined by the set m of connector elements specified
on this entry will be appended to the set n defined on the right side of the DISP
command.
m is the identification of a connector element set defined by a previously appearing
SET command.
If DISP(...)=NONE, then no points will be output even if the user has defined the
keyword CONN=ALL or CONN=m.
If DISP(...)=ALL, then auxiliary point “grids” for all connectors will be generated
regardless if CONN= is specified.
If the user wishes to produce displacements for all the connector elements and have
them appended to the set n defined on the right side of the DISP command, please
just specify CONN=ALL.
ALL Displacements for all points will be output.
n Set identification of a previously appearing SET command. Only displacements of
points with identification numbers that appear on this SET command will be output
(Integer > 0).
NONE Displacement for no points will be output.
STRUCTURE, Request eigenvector output data type for normal mode computation (SOL 103)
FLUID, BOTH with METHOD(COUPLED) case control. Structure displacement only, Fluid
pressure only or both Structure displacement and Fluid pressure output separately.
Default is NONE for both structure displacement and fluid pressure together. See
Remark 10.
Remarks:
1. The defaults for SORT1 and SORT2 depend on the type of analysis:
a. SORT1 is the default in static analysis, frequency response, steady state heat transfer analysis, real
and complex eigenvalue analysis, flutter analysis, and buckling analysis.
b. SORT2 is the default in transient response analysis (structural and heat transfer). SORT2 is not
available for real eigenvalue (including buckling), complex eigenvalue, or flutter analysis. If
SORT1 is selected in a transient solution for one or more of the commands ACCE, DISP,
ENTH, FORC, HDOT, MPCF, OLOA, SPCF, STRA, STRE, and VELO, then the remaining
Main Index
CHAPTER 5 281
Displacement Output Request
commands will also be output in SORT1 format. If SORT2 is selected in a static or frequency
response solution for one or more of the commands ACCE, DISP, FORC, MPCF, OLOA,
SPCF, STRA, STRE, and VELO, then the remaining commands will also be output in SORT2
format.
c. XY plot requests forces SORT2 and overrides SORT1 requests!
d. If a RANDOM request occurs the output will be in SORT2 format, even if SORT1 is requested.
2. VECTOR and PRESSURE are alternate forms and are equivalent to DISPLACEMENT. In complex
analysis, the pressure is ALWAYS magnitude-phase.
3. DISPLACEMENT=NONE overrides an overall output request.
4. The units of translation are the same as the units of length of the model. Rotations are in units of
radians.
5. Displacement results are output in the global coordinate system (see field CD on the GRID Bulk
Data entry).
6. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
7. Note that the CID keyword affects only grid point related output, such as DISPlacement, VELOcity,
ACCEleration, OLOAD, SPCForce and MPCForce. In addition, CID keyword needs to appear only
once in a grid-related output request anywhere in the Case Control Section to turn on the printing
algorithm.
8. Displacement components may be selected to control filtering to reduce the amount of output
produced. When magnitudes are selected, the component values are ignored. Only a single positive
value for f can be supplied, and comparisons are performed in the global reference frame.
Comparisons are performed after the SET intersection is performed against the domain. Selection of
this option does not effect the MAXMIN(GRID) operations. Scalar comparisons are performed using
the minimum of all supplied values for the filters.
For complex vectors encountered in frequency response analysis, the magnitudes TM and RM follow
a derivation using a deterministic interpretation and are calculated as follows:
• For Grid Points
TM
Define
C1 = T1real**2 + T2real**2 + T3real**2
C2 = T1imag**2 + T2imag**2 + T3imag**2
C3 = T1real*T1imag + T2real*T2imag + T3real*T3imag
C4 = (C1 + C2)/2
C5 = (C1 - C2)/2
Then,
TM = C4 + SQRT (C5**2 + C3**2)
RM
Main Index
282 MSC Nastran Quick Reference Guide
Displacement Output Request
The calculations are similar to the above, except that R1, R2 and R3 are used in place of T1, T2
and T3, respectively.
• For Scalar Points
In this case, TM and RM have the same meaning.
Define
C1 = T1real**2
C2 = T1imag**2
C3 = T1real*T1imag
C4 = (C1 + C2)/2
C5 = (C1 - C2)/2
Then,
TM (or RM) = C4 + SQRT (C5**2 + C3**2)
9. When using filters, the compound usage of the verbs PRINT, PLOT is allowed. The entries in the
printed output are the entries that exceed any threshold, while the remaining entries within the SET
are marked as plot to allow for postprocessing operations. When SORT2 is selected, then PRINT,
PLOT must be used to allow for table transpose operations to occur. When any entry in the SORT2
format is above the threshold, all values for time or frequency will be printed for the grid point.
10. Default eigenvector output format of coupled mode computation (SOL 103) is structure
displacement and fluid pressure combined in one datablock per same modes DISP(PRINT) = ALL.
The eigenvector table has normal title in f06 file.
REAL EIGENVECTOR NO. 1
To get structure displacement and fluid pressure separately from coupled mode computation (with
METHOD(coupled) in SOL 103), DISP(PRINT,STRUCTURE) = ALL is used for
STRUCTURAL displacement only. The eigenvector table has title (STRUCTURE) in f06 file.
REAL EIGENVECTOR(STRUCTURE) NO. 1
DISP(PRINT,FLUID) = ALL is used for FLUID pressure only. The eigenvector table has the title
(FLUID)in f06 file.
REAL EIGENVECTOR(FLUID) NO. 1
DISP(PRINT,BOTH) = ALL is used for both STRUCTURAL displacement and FLUID pressure
but separately. Each eigenvector table includes its own title (STRUCTURE) or (FLUID) in f06 file.
REAL EIGENVECTOR(STRUCTURE) NO. 1
………
REAL EIGENVECTOR(FLUID) NO. 1
………
11. When DISPLACEMENT is requested at a fluid grid, the output is the fluid pressure. When
VELOCITY and ACCELERATION are also requested at the same fluid grid, the outputs represent
the first and second derivatives of the fluid pressure, respectively. If these pressure derivatives are not
interested in, both VELOCITY and ACCELERATION should be requested only at the structural
grids.
Main Index
CHAPTER 5 283
Displacement Output Request
12. ODS request must work with Case Control command, ODSFREQ, which specifies a selection of the
excitation frequencies for ODS output.
Main Index
284 MSC Nastran Quick Reference Guide
Static Aeroelastic Divergence Request
DIVERG (Case) Static Aeroelastic Divergence Request
Selects the divergence parameters in a static aeroelastic divergence problem.
Format:
DIVERG=n
Example:
DIVERG=70
Describer Meaning
n Set identification of a DIVERG Bulk Data entry (Integer > 0).
Remark:
1. Static aeroelastic divergence analysis can be performed only in SOLs 144, 200 and 400.
Main Index
CHAPTER 5 285
Dynamic Load Set Selection
DLOAD (Case) Dynamic Load Set Selection
Selects a dynamic load or an acoustic source to be applied in a transient or frequency response problem.
Format:
DLOAD=n
Example:
DLOAD=73
Describer Meaning
n Set identification of a DLOAD, RLOAD1, RLOAD2, TLOAD1, TLOAD2, or
ACSRCE Bulk Data entry (Integer > 0).
Remarks:
1. RLOAD1 and RLOAD2 may only be selected in a frequency response problem.
2. TLOAD1 and TLOAD2 may be selected in a transient or frequency response problem.
3. Either an RLOADi or TLOADi entry (but not both) must be selected in an aeroelastic response
problem. If RLOADi is selected, a frequency response is calculated. If TLOADi is selected, the
transient response is computed by Fourier transform. When there are only gust loads (GUST Bulk
Data entry), the DLOAD selects a TLOADi or RLOADi Bulk Data entry with zero load, along with
field 3 of the GUST command.
4. The DLOAD command will be ignored if specified for upstream superelements in dynamic analysis.
To apply loads to upstream superelements, refer to the LOADSET Case Control command.
5. For nonlinear dynamic analysis with SOL 400, TEMPERATURE load can't be applied by
DLOAD/TEMP/TLOADi. TEMP (case control) and TTEMP (Bulk data) should be used to apply
the temperature load. However, for pure linear analysis, DLOAD/TEMP has to be used for
temperature load.
Main Index
286 MSC Nastran Quick Reference Guide
Response Spanning Set Selection
DRSPAN (Case) Response Spanning Set Selection
Selects a set of DRESP1 and/or DRESP2 entries for the current subcase that are to be used in a DRESP2 or
DRESP3 response that spans subcases.
Format:
DRSPAN=n
Example:
DRSPAN=10
Describer Meaning
n Set identification of a previously appearing SET command (Integer > 0).
Remarks:
1. In SOL 200, DRESP2 or DRESP3 Bulk Data entries can invoke DRESP1 and DRESP2 responses
that span subcases if these DRESP1/DRESP2 responses have been identified using a DRSPAN Case
Control command that references a SET request that identifies the DRESP1/DRESP2 Bulk Data
entries.
2. Each DRESP1/DRESP2 identified must produce a scalar value.
3. The DRSPAN Case Control command must be at the subcase level, whereas the SET request can be
specified above the subcase level.
4. A DRESP2 or DRESP3 that SPANS subcases, cannot reference another DRESP3.
5. To check the value of spanned response, set parameter P2 of DOPTPRM to a value equal to or larger
than 8 (see DOPTPRM for details). Note that verification requires performing hand calculation
based on user-provided DEQATN for the spanned response.
Main Index
CHAPTER 5 287
Design Sensitivity Output Parameters
DSAPRT (Case) Design Sensitivity Output Parameters
Specifies design sensitivity output parameters.
Format:
FORMATTED ALL
DSAPRT UNFORMATTED NOEXPORT START = i BY = j END = k = n
EXPORT
NOPRINT NONE
Examples:
DSAPRT(FORMATTED,EXPORT)
DSAPRT(FORMATTED,START=FIRST,BY=3,END=LAST)=101
DSAPRT(UNFORMATTED,START=FIRST)
DSAPRT(UNFORMATTED,EXPORT)
DSAPRT(FORMATTED,END=4)=ALL
DSAPRT(UNFORMATTED,END=SENS)=ALL
DSAPRT(NOPRINT, EXPORT)
Describer Meaning
FORMATTED Output will be presented with headings and labels.
UNFORMATTED Output will be printed as a matrix print (see description of the MATPRN
module in the MSC Nastran DMAP Programmer’s Guide).
NOPRINT No output will be printed.
EXPORT Output will be exported to an external binary file specified by
PARAM,IUNIT.
NOEXPORT Output will not be exported to an external binary file.
START=i Specifies the first design cycle for output (Integer > 0 or Character:
“FIRST” or “LAST”; Default = 1 or “FIRST”).
BY=j Specifies the design cycle interval for output. See Remark 2. (Integer > 0;
Default = 0).
END=k Specifies the last design cycle for output. (Integer > 0 or Character:
“FIRST”, “LAST”, or “SENS”; Default = “LAST”)
ALL All retained design responses (defined on DRESP1, DRESP2 and
DRESP3 entries) will be output.
n Set identification of a previously appearing SET command. Only
sensitivities of retained responses with identification numbers that appear
on this SET command will be output (Integer > 0).
Main Index
288 MSC Nastran Quick Reference Guide
Design Sensitivity Output Parameters
Remarks:
1. Only one DSAPRT may appear in the Case Control Section and it must occur with or above the first
SUBCASE command.
2. Sensitivity data will be output at design cycles i, i+j, i+2j, ..., k. Note that the BY=0 implies no
sensitivity results will be output at the intermediate design cycles.
3. END=SENS requests design sensitivity analysis, and no optimization will be performed.
4. If both DSAPRT and PARAM,OPTEXIT, 4, -4, or 7 are specified, then DSAPRT overrides
PARAM,OPTEXIT, 4, -4, or 7. PARAM,OPTEXIT values and the equivalent DSAPRT commands
are described as follows:
OPTEXIT Equivalent DSAPRT Command
4 DSAPRT(UNFORMATTED, END=SENS)
-4 DSAPRT(NOPRINT, EXPORT, END=SENS)
7 DSAPRT(UNFORMATTED, START=LAST)
5. The n and NONE options are not supported for UNFORMATTED output. Only the
UNFORMATTED option is supported for EXPORT.
6. PARAM,DSZERO can be used to set a threshold for the absolute value of the formatted sensitivity
prints.
7. Design Sensitivity analysis is never performed following a discrete design optimization. Therefore, no
sensitivity output will be produced with DSAPRT(END=LAST) when discrete optimization is
performed at the end of a job.
8. Formatted sensitivity data can also be written into Comma Separated Values(or CSV) file with
following steps
a. DSAPRT(formatted,..) request in case control. Note that 'formatted' is a default option.
b. PARAM,XYUNIT,52 in bulk data. Unit 52 is simply chosen as an example.
c. file assignment statement, such as
ASSIGN USERFILE='jobname.csv' FORM=formatted STATUS=new UNIT=52
Main Index
CHAPTER 5 289
Dihedral Symmetry Option in Cyclic Symmetry
DSYM (Case) Dihedral Symmetry Option in Cyclic Symmetry
Provides for either one or two planes of overall symmetry in DIH-type cyclic symmetry problems.
Format:
S
A
SS
DSYM =
SA
AS
AA
Example:
DSYM=AS
Describer Meaning
S, A The problem is assumed to be symmetrical (S) or antisymmetrical (A) with
respect to the plane containing side 1 of segment 1.
SS, SA, The problem is assumed to be symmetrical (or antisymmetrical) with respect to
AS, AA the plane containing side 1 of segment 1 (denoted by the first symbol), and also
with respect to a plane perpendicular to side 1 (denoted by the second symbol).
Main Index
290 MSC Nastran Quick Reference Guide
Dynamic Stiffness Output Request
DYSTIFF (Case) Dynamic Stiffness Output Request
Requests the form and type of dynamic stiffness output in SOL 108, 111, 200 and SOL 400 only.
ALL
SORT1 PRINT,PUNCH REAL or IMAG
DYSTIFF = n
SORT2 PLOT PHASE
NONE
Examples:
DYSTIFF = ALL
DYSTIFF (REAL, PUNCH, PRINT)=17
DYSTIFF = 25
DYSTIFF (SORT2, PRINT)=20
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each frequency.
SORT2 Output will be presented as a tabular listing of frequency for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output
is in degrees.
ALL Dynamic Stiffness at all points will be output. See remark 2.
n Set identification of a previously appearing SET command. Only dynamic
stiffness of points with identification numbers that appear on this SET
command will be output. (Integer >0).
NONE No dynamic Stiffness will be output (Default).
Main Index
CHAPTER 5 291
Dynamic Stiffness Output Request
Remarks:
1. DYSTIFF is available for SOL 108, 111 and SOL 200 and 400 with ANALYSIS=DFREQ and
MFREQ.
2. See Remark 1. under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
3. DYSTIFF=NONE suppresses the generation of dynamic stiffness output.
4. Dynamic Stiffness, di at a grid point is computed as, di=fi/ui where fi is the load applied and ui is the
complex displacement. The dynamic stiffness will be output for the grids having load applied on it.
5. Refrain from using ALL which may produce voluminous output.
6. The dynamic stiffness output will be subjected to the mechanical load only.
Main Index
292 MSC Nastran Quick Reference Guide
Bulk Data Echo Request
ECHO (Case) Bulk Data Echo Request
Controls echo (i.e., printout) of the Bulk Data.
Format:
SORT EXCEPT cdni,... SORT
BOTH FILE
ECHO = UNSORT PUNCH
BOTH NEWBULK
NONE
Examples:
ECHO=UNSORT
ECHO=BOTH
ECHO=PUNCH, SORT (MAT1, PARAM)
ECHO=SORT (EXCEPT DMI, DMIG)
ECHO=BOTH,PUNCH,FILE
(In the above examples See Remark 7.: the PUNCH keyword will always result in the PUNCH file
containing the entire bulk data input. Explicit inclusion indicators (CDNI) such as (MAT1, PARAM) will
always cause a F06 file to be written that contains only the (CDNI) data.)
Describer Meaning
SORT The sorted (arranged in alphanumeric order) Bulk Data will be printed.
EXCEPT Excludes cdni Bulk Data entries from sorted echo printout. See Remark 6.
cdni,... Defines Bulk Data entry names to be included, or excluded by EXCEPT, in the
sorted echo printout. The PUNCH (.pch) file is not affected by cdni.
UNSORT The unsorted Bulk Data will be printed. If SORT is also not specified, the sorted
Bulk Data will not be printed.
BOTH Both sorted and unsorted Bulk Data will be printed. This is equivalent to
ECHO=SORT, UNSORT.
NONE Neither sorted nor unsorted Bulk Data will be printed.
PUNCH The entire Bulk Data will be written to the punch (.pch) file. See Remark 7. for
options.
FILE The entire Bulk Data echo will be written to the separate file with a default suffix
of .BECHO in *.f06 form. A user-defined filename must be specified in the
ASSIGN statement.
NEWBULK In SOL 200, a complete unsorted Bulk Data file is written to the PUNCH file
with updated design model entries.
Main Index
CHAPTER 5 293
Bulk Data Echo Request
Remarks:
1. If no ECHO command appears, sorted Bulk Data will be printed.
2. Comments will appear at the front of the sorted file if ECHO=PUNCH.
3. Portions of the unsorted Bulk Data can be selectively echoed by including the commands ECHOON
and ECHOOFF at various places within the Bulk Data. ECHOOFF stops the unsorted echo until
an ECHOON commands is encountered. Many such pairs of commands may be used. The
ECHOON and ECHOOFF command may be used in the Executive and Case Control Sections;
however, ECHOOFF should not be the first entry and continuation entries are not handled correctly.
4. If the SORT (cdni,...) describer is specified in a restart in SOLs 101 through 200, then the
continuation entries will not be printed.
5. If the SORT (cdni,...) describer is used, then it must appear as the last describer, as in the preceding
example.
6. If the EXCEPT describer is specified, then it must be specified before all cdni. All Bulk Data entry
types will be listed except those given for cdn1, cdn2, etc. If EXCEPT is not specified, then only those
Bulk Data entry types listed under cdn1, cdn2, etc. will be listed.
7. PUNCH without options or PUNCH(SORT) produces a sorted listing of the entire bulk data input
in the punch file. PUNCH(NEWBULK) produces unsorted bulk data input with updated design
model entries in the punch file. PUNCH(BOTH) combines these two outputs.
Main Index
294 MSC Nastran Quick Reference Guide
Element Energy Loss Per Cycle Output Request
EDE (Case) Element Energy Loss Per Cycle Output Request
Requests the output of the energy loss per cycle in selected elements.
Note that EDE is not supported in NLPERF SOL 400.
Format:
AVERAGE ALL
PRINT, PUNCH
EDE ( AMPLITUDE THRESH = p NOPERCENT = n
PLOT
PEAK NONE
Examples:
EDE=ALL
EDE(PUNCH, THRESH=.0001)=19
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
AVERAGE Requests average energy (in frequency response analysis only) (Default).
AMPLITUDE Requests amplitude of energy (in frequency response analysis only).
PEAK Requests peak energy (for frequency response analysis only). PEAK is the sum of
AVERAGE and AMPLITUDE.
THRESH Energies for elements having an energy value of less than p% will be suppressed in
all output files: print, punch, plot, .op2, and .xdb. THRESH overrides the value of
TINY described in Remark 1. (Default = 0.001).
NOPERCENT Do not compute TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM and
PERCENT OF TOTAL. The values will appear as zeros. Sparse data recovery and
NOPERCENT can result in significant reduction in computing resources. But if
RTYPE=TOTSE appears on a DRESP1 entry then full data recovery is necessary
and no savings will be realized.
ALL Energy for all elements will be computed.
Main Index
CHAPTER 5 295
Element Energy Loss Per Cycle Output Request
Describer Meaning
n Set identification number. Energy for all elements specified on the SET n
command will be computed. The SET n command must be specified in the same
subcase as the EDE command, or above all subcases (Integer > 0).
NONE Element energy loss will not be output.
Remarks:
1. If THRESH = p is not specified, then p defaults to the values specified by user parameter TINY.
2. The energy calculations include the contribution of initial thermal strain.
3. Energy density (element energy divided by element volume) is also computed in some solution
sequences. It can be suppressed by use of PARAM,EST,-1.
4. For frequency response analysis, the energy may be computed in one of three ways as selected by
AVERAGE:
T T
E o = u r B e u r + u i B e u i
AMPLITUDE:
T T 2 T 2
E a = u r B e u r – u i B e u i + 2 u r B e u i
PEAK:
E peak = E o + E a
where:
E = elemental energy.
ur = displacement (real part).
ui = displacement (imaginary part).
Be = elemental damping.
5. In SOLs 111 and 112, EDE is not available if both PARAM,DDRMM,0 and
PARAM,SPARSEDR,NO are specified.
6. Only damping from the viscous dampers (e.g., CVISC, CDAMPi, etc.) are included. Structural
damping is not included in the calculation.
7. The usages of REPCASE and OMODES Case Control directives is not supported for ESE, EKE,
EDE and GPFO output selections and should not be used.
8. If there are any frequency dependent CBUSH elements present, and PARAM, BUSHNM, NO; then
all CBUSH elements will be excluded from the element energy loss output.
Main Index
296 MSC Nastran Quick Reference Guide
Element Energy Loss Per Cycle Output Request
9. For transient response, EDE is computed in a quasi-static manner at each time
1 T
step: --- v B e u ; where Be is elemental damping and v and u are velocity and displacement
2
respectively.
Main Index
CHAPTER 5 297
Element Kinetic Energy Output Request
EKE (Case) Element Kinetic Energy Output Request
Requests the output of the kinetic energy in selected elements.
Note that EKE is not supported in NLPERF SOL 400.
Format:
AVERAGE ALL
PRINT, PUNCH
EKE ( AMPLITUDE THRESH = p NOPERCENT ) = n
PLOT
PEAK NONE
Examples:
EKE=ALL
EKE(PUNCH, THRESH=.0001)=19
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
AVERAGE Requests average energy (in frequency response analysis only) (Default).
AMPLITUDE Requests amplitude of energy (in frequency response analysis only).
PEAK Requests peak energy (for frequency response analysis only). PEAK is the sum of
AVERAGE and AMPLITUDE.
THRESH Kinetic energies for elements having a energy value of less than p% will be
suppressed in all output files: print, punch, plot, .op2, and .xdb. THRESH
overrides the value of TINY described in Remark 1. (Default = 0.001).
NOPERCENT Do not compute TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM and
PERCENT OF TOTAL. The values will appear as zeros. Sparse data recovery and
NOPERCENT can result in significant reduction in computing resources. But if
RTYPE=TOTSE appears on a DRESP1 entry then full data recovery is necessary
and no savings will be realized.
ALL Kinetic energy for all elements will be computed.
Main Index
298 MSC Nastran Quick Reference Guide
Element Kinetic Energy Output Request
Describer Meaning
n Set identification number. Energy for all elements specified on the SET n
command will be computed. The SET n command must be specified in the same
subcase as the EKE command, or above all subcases (Integer > 0).
NONE Kinetic energy values will not be output.
Remarks:
1. If THRESH = p is not specified, then p defaults to the values specified by user parameter TINY.
2. The energy calculations include the contribution of initial thermal strain.
3. Energy density (element energy divided by element volume) is also computed in some solution
sequences. It can be suppressed by use of PARAM,EST,-1.
4. For frequency response analysis, the energy values may be computed in one of three ways as selected
by
AVERAGE:
1 T T
E o = --- v r M e v r + v i M e v i
4
AMPLITUDE:
1 T T 2 T 2
E a = --- v r M e v r – v i M e v i + 2 v r M e v i
4
PEAK:
E peak = E o + E a
where:
E = elemental energy.
v r = velocity (real part).
v i = velocity (imaginary part).
M e = elemental mass.
5. In SOLs 111 and 112, EKE is not available if both PARAM,DDRMM,0 and
PARAM,SPARSEDR,NO are specified.
6. The usages of REPCASE and OMODES Case Control directives is not supported for ESE, EKE,
EDE and GPFO output selections and should not be used.
7. EKE output request is available in SOL 400 multi-disciplinary and linear perturbation analyses using
MODES and MCEIG types of analysis.
Main Index
CHAPTER 5 299
Element Kinetic Energy Output Request
8. If there are any frequency dependent CBUSH elements present, and PARAM, BUSHNM, NO; then
all CBUSH elements will be excluded from the element kinetic energy output.
9. For transient response, EKE is computed in a quasi-static manner at each time
1 T
step: --- v M e v ; where Me is elemental mass and v is velocity.
2
Main Index
300 MSC Nastran Quick Reference Guide
Elastic Forces Output Request
ELAFORCES (Case) Elastic Forces Output Request
Requests the form and type of elastic forces output.
Format:
ALL
ELAFORCES ( SORT1 PRINT, PUNCH , REAL or IMAG ) = n
SORT2 PLOT PHASE
NONE
Examples:
ELAFORCE=ALL
ELAF(REAL, PUNCH, PRINT)=17
ELAFORCE=25
ELAFORCE(SORT2, PRINT)=20
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load, frequency,
eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
ALL Elastic forces for all points will be output. See Remarks 2.
Main Index
CHAPTER 5 301
Elastic Forces Output Request
Describer Meaning
NONE No elastic force will be output.
n Set identification of a previously appearing SET command. Only points with
identification numbers that appear on this SET command will be output
(Integer >0).
Remarks:
1. Refrain from using ALL in transient analysis which may produce voluminous output.
2. See Remark 1. under DISPLACEMENT (Case), for a discussion of SORT1 and SORT2.
3. ELAFORCE=NONE suppresses the generation of elastic forces output.
4. Although ELAFOR selects the desired grid IDs, it is to be noted that the connections should be
included in the computation. Hence, Fi of a point the requested set can be also expressed as
n
Fi = Kij uj
j=1
5. ELAFORCE is available for SOL 108, 109, 111, 112 and SOL 200 with ANALYSIS=DFREQ,
MFREQ and MTRAN. Note that ELAFORCE is available for output only and can not be utilized
as design response.
6. ELAFORCE does not support external SE via OTM due to limitation.
7. ELAFORCE does not support DOMAINSOLVER with PARTOPT=grid.
Main Index
302 MSC Nastran Quick Reference Guide
Element Stress Discontinuity Output Request
ELSDCON (Case) Element Stress Discontinuity Output Request
Requests mesh stress discontinuities based on element stresses.
Format:
ALL
PRINT, PUNCH
ELSDCON = n
PLOT
NONE
Examples:
ELSDCON=ALL
ELSDCON=19
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Stress discontinuity requests for all SURFACE and VOLUME Case Control
commands defined in the OUTPUT(POST) Section will be output.
n Set identification number of a previously appearing SET command. Only surfaces
and volumes with identification numbers that appear on this SET command will be
included in the stress discontinuity output request (Integer >0).
NONE No element stress discontinuity output.
Remarks:
1. This output is available in linear static analysis SOLs 101 and 144 only. Output will be presented for
each surface or volume as a tabular listing of stress discontinuities for each subcase.
2. Only elements used to define the surface or volume are output. See the description of the SURFACE
or VOLUME Case Control commands.
Main Index
CHAPTER 5 303
Element Stress Discontinuity Output Request
3. Element stress output (STRESS) must be requested for elements referenced on SURFACE and
VOLUME Case Control commands. Also, the GPSTRESS command must be present for printed
output and the STRFIELD command for postprocessing output using the .xdb file
(PARAM,POST,0) for the same surfaces and volumes.
Main Index
304 MSC Nastran Quick Reference Guide
Element Sensitivity Output for SOL 108/111
ELSENS (Case) Element Sensitivity Output for SOL 108/111
Select SOLUTION frequencies and RESPONSE DOFs for the generation element sensitivity.
Format:
PRINT, PUNCH REAL or IMAG
ELSENS THRESH = P RESPONSE = r
PLOT PHASE
SOLUTION = ALL
setf
ALL
MASS, STIFF, DYNAMIC, SQMASS, SQSTIFF, SQDYNA = n
NONE
Example
SET 81 = 100.0, 120.0
SET 91 = 11240/T3, 4001/T1
SET 96 = 15920 THRU 15950
$
ELSENS(RESPONSE=91, SOLUTION=81,MASS,STIFF,DYNAMIC) = 96
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
THRESH The magnitude of element sensitivity less than p will be suppressed in all output files:
print, punch, plot, .op2, and .xdb. (Default = 0.0).
RESPONSE Adjoint load response will be computed for unit load applied at grid point components
in SET r.
Main Index
CHAPTER 5 305
Element Sensitivity Output for SOL 108/111
Describer Meaning
SOLUTION Frequency responses at these forcing frequencies, defined in setf, will be used for
element sensitivity computation. (Default=all forcing frequencies)
MASS Sensitivity with element mass matrices will be computed and output.
STIFF Sensitivity with element stiffness matrices will be computed and output.
DYNAMIC Sensitivity with element stiffness and mass matrices will be computed and output.
SQMASS Squared sensitivity with element mass matrices will be computed and output.
SQSTIF Squared sensitivity with element stiffness matrices will be computed and output.
SQDYNA Squared sensitivity with element stiffness and mass matrices will be computed and
output.
ALL Sensitivities for all elements will be calculated.
n Set identification number. Sensitivity for all elements specified on the SET n
command will be calculated. The SET n command must be specified in the same
subcase as the ELSSENS command, or above all subcases ( Integer > 0 ). The IDs in
set n must be EID (element ID).
NONE Elemental sensitivity will not be output.
Remarks:
1. Set r for RESPONSE has no default.
2. The equations various options of ELSENS are as follows:
ELSENS(MASS) = [Usetf]t[-2Melem][Ur]
ELSENS(STIFF) = [Usetf]t[Kelem][Ur]
ELSENS(DYNAMIC) = [Usetf]t[-2Melem][Ur] + [Usetf]t[Kelem][Ur]
ELSENS(SQMASS) = [Usetf]t[-2Melem][Ur] + [Usetf]*t[-2Melem]* [Ur]*
ELSENS(SQSTIF) = [Usetf]t[Kelem][Ur] + [Usetf]*t[Kelem]* [Ur]*
ELSENS(SQDYNA) = [Usetf]t[-2Melem][Ur] + [Usetf]t[Kelem][Ur] +
[Usetf]*t[-2Melem]* [Ur]* + [Usetf]*t[Kelem]* [Ur]*
where [Usetf] is the displacement of SOLUTION
Main Index
306 MSC Nastran Quick Reference Guide
Element Sensitivity Output for SOL 108/111
[Ur] is the displacement of RESPONSE
[Kelem] is element stiffness matrix
[Melem] is element mass matrix
superscript * means complex conjugate of the term.
Refer to the Compute Element Sensitivity based on Frequency Response Function and Element Matrix in the MSC
Nastran Dynamic Analysis User's Guide, for more details.
3. The ELSENS is valid for symmetric formulation only since the formulation is based on the symmetric
equation as described in the MSC Nastran Dynamic Analysis User's Guide.
Main Index
CHAPTER 5 307
Element Summary Output Request
ELSUM (Case) Element Summary Output Request
Requests that a summary of element properties grouped by element type and/or element property type are to
be printed.
Format:
ALL
ELSUM EID, PID, BOTH, EIDSUM, PIDSUM, NSMCONT,SUMMARY = n
NONE
Examples:
ELSUM = 9
ELSUM (PID) = ALL
Describer Meaning
EID Element summary output is grouped by element type.
PID Element summary output is grouped by element property type.
BOTH Both EID and PID groupings are produced.
EIDSUM Only a summary of the mass totals for the EID grouping is produced.
PIDSUM Only a summary of the mass totals for the PID grouping is produced.
NSMCONT Nonstructural mass contributions from NSM, NSM1, NSML, and NSML1 Bulk
Data entries are identified.
SUMMARY Only a summary of the mass totals is produced.
ALL Element summary output for all elements
n Set identification of a previously appearing SET command. Produces output for
only those elements whose identification numbers appear in the list of this SET
command.
NONE No element summary output is produced.
Remarks:
1. The ELSUM Case Control command produces a summary of properties for elements. The properties
include element ID, material ID, length or thickness, area, volume, structural mass, nonstructural
mass, total mass, and the product of total mass * WTMASS. Total mass is the sum of the structural
and nonstructural masses.
Main Index
308 MSC Nastran Quick Reference Guide
Element Summary Output Request
2. Certain element types produce only partial data. For these element types, no mass data is produced,
and mass totals will not include any contributions from these element types. Mass data is computed
for the following element types: CBAR, CBEAM, CBEND, CHEXA, CMASSi, CONM1,
CONM2, CONROD, CPENTA, CQUAD4, CQUAD8, CQUADR, CRAC2D, CRAC3D,
CROD, CSHEAR, CTETRA, CTRIA3, CTRIA6, CTRIAR, CTRIAX6, and CTUBE. The mass of
elements with mid side nodes is approximated using only the geometry of the corner nodes. To get
an accurate total mass, use the output from the Grid Point Weight Generator (PARAM,GRDPNT).
3. EIDSUM takes precedence over EID if both are present. Likewise, PIDSUM takes precedence over
PID.
4. The ELSUM Case Control command is ignored in heat transfer solution sequences.
5. The NSMCONT describer produces various amounts of output depending upon whether the
summary option is selected (SUMMARY, PIDSUM or EIDSUM requested). If NSMCONT is
combined with PID, a table is produced that identifies the contribution of each NSM type Bulk Data
entry to the total element nonstructural mass. If SUMMARY is included with PID and NSMCONT,
an additional table is produced that identifies the mass contributions for each property type by
property ID.
6. ELSUM output is only available for the PRINT option, not the PUNCH or PLOT options used in
other commands.
7. ELSUM does not support advanced nonlinear elements.
Main Index
CHAPTER 5 309
Specifies Final Analysis Step
ENDSTEP (Case) Specifies Final Analysis Step
Specifies final analysis step for SOL 700.
Format:
ENDSTEP = Value
Example:
ENDSTEP = 10000
Describer Meaning
Value Steps to end the simulation (Integer, Default = 9999999).
Main Index
310 MSC Nastran Quick Reference Guide
Specifies Final Analysis Time
ENDTIME (Case) Specifies Final Analysis Time
Specifies final analysis time for SOL 700.
Format:
ENDTIME = Value
Example:
ENDTIME = 0.01
Describer Meaning
Value Time in the applicable units for the model (usually seconds) (Real; Default =
1e+20).
Main Index
CHAPTER 5 311
Module Bulk Data section delimiter
ENDMODULE (Case) Module Bulk Data section delimiter
Indicates (delimits) the end of a Module’s Bulk Data section.
Format:
ENDMODULE
Example:
ENDMODULE
END MODULE
Remarks:
1. A BEGIN MODULE command must appear somewhere before ENDMODULE.
2. The ENDDATA command may be used to terminate the last Module’s Bulk Data section.
Main Index
312 MSC Nastran Quick Reference Guide
Heat Transfer Enthalpy Output Request
ENTHALPY (Case) Heat Transfer Enthalpy Output Request
Requests form of enthalpy vector output in transient heat transfer analysis (SOL 159).
Format:
ALL
SORT1 PRINT, PUNCH
ENTHALPY ( ) = n
SORT2 PLOT
NONE
Example:
ENTHALPY=5
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each time.
SORT2 Output will be presented as a tabular listing of time for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in
Bulk Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being
deprecated.
ALL Enthalpy for all grid points will be output.
n Set identification of previously appearing SET command. Only enthalpies of grid
points with identification numbers that appear on this SET command will be
output (Integer > 0).
NONE Enthalpy for no grid points will be output.
Remark:
1. ENTHALPY=NONE is used to override a previous ENTHALPY = n or ENTHALPY = ALL
command.
Main Index
CHAPTER 5 313
Equilibrium Force Output Request
EQUILIBRIUM (Case) Equilibrium Force Output Request
Specifies options for equilibrium force balance output of applied loads, single point constraint forces and
forces due to multi-point constraints and rigid elements.
Format:
YES
PRINT, PUNCH
EQUILIBRIUM ( ) = gid
PLOT
NONE
Examples:
EQUILIBRIUM
EQUILIBRIUM = 501
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
YES Requests moment summation referenced to origin of basic coordinate system.
gid Requests moment summation referenced to basic system location specified by the
coordinates of grid point gid.
NONE Equilibrium force balance output will not be generated.
Remarks:
1. The EQUILIBRIUM Case Control command produces a summary of the applied loads, single point
forces of constraint (SPC), and multipoint/rigid body element forces of constraint (MPC), as well as
a summation of these quantities. In order for the summation to represent all of the forces in the
problem, these forces must be available and, therefore, the specification of an EQUILIBRIUM Case
Control command causes the program to automatically compute the SPC and MPC forces. However,
if desired, the associated Case Control commands should request output. The single point forces of
constraint are requested by the presence of an SPCFORCE command, and the multipoint/RBE
constraint forces are requested by an MPCFORCE command. Applied loads are automatically
generated by the presence of the LOAD selection Case Control command.
Main Index
314 MSC Nastran Quick Reference Guide
Equilibrium Force Output Request
2. Results are always output in the basic coordinate system.
3. The EQUILIBRIUM Case Control command is applicable to Linear Static analysis (SOL101) only,
and does not produce output if any superelements are present.
Main Index
CHAPTER 5 315
Equivalent Radiated Power Panel Participation Factor Output Request
ERP (Case) Equivalent Radiated Power Panel Participation Factor Output Request
Requests the form and type of ERP panel participation factor output for frequency or transient analysis.
Format:
ALL
SORT2 PRINT, PUNCH setf
ERP SOLUTION = ,
SORT1 PLOT sett
peak
ALL
MPF = nlm MPFSORT = sorttype , ELEMENT ,
NONE
frequency
0.01
KEY = fraction FILTER = ,
real _value
time
1.0 1.0
ERPRHO = ERPC =
real _value real _value
1.0 1.0
RHOCP = ERPRLF =
real _value real _value
ALL
1.0
ERPREFDB = CSV = unit = setp
real _value
NONE
Examples:
SET 17 = 10.,20.,30.,40.,80.,100. $ A list of frequencies
SET 25 = ROOF, DOORLF $ A list of ERP Panel names
$ from a ERPPNL Bulk Entry
ERP ( PRINT,PUNCH,SOLUTION=17,KEY=frac ) = 25
ERP ( PRINT,PUNCH,SOLUTION=peak, KEY=frac ) = 25
Main Index
316 MSC Nastran Quick Reference Guide
Equivalent Radiated Power Panel Participation Factor Output Request
Describer Meaning
SORT1 Output is presented as a tabular listing of ERP panels for each frequency.
SORT2 Output is presented as a tabular listing of frequency for each ERP panel.
PRINT or (blank) Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PUNCH X X*
PLOT X X*
X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
SOLUTION Keyword to select frequencies or time.
ALL If associated with SOLUTION, all frequencies or times are selected. If
associated with setp, all ERPPNL entries are selected.
setf Identifier of Case Control SET command defining frequencies.
sett Identifier of Case Control SET command defining times.
peak Requests ERP output at peak frequencies found by PEAKOUT Case
Control command. See Remark 14. (Character).
MPF Requests the output of Modal Participation Factors for ERP. See Remark 9.
ALL All structural modes for which MPF will be computed
nlm Number of lowest structural modes for which MPF will be computed
NONE MPF will not be computed. (Default)
MPFSORT Keyword selecting the sort type. Default is sorting by increasing natural mode
number. See Remark 10.
Sorttype Sort options:
ABSA output will be sorted by absolute value in ascending order.
ABSD output will be sorted by absolute value in descending order.
ALGA output will be sorted by algebraic value in ascending order.
ALGD output will be sorted by algebraic value in descending order
ELEMENT Keyword to request element–by-element ERP output
Main Index
CHAPTER 5 317
Equivalent Radiated Power Panel Participation Factor Output Request
Describer Meaning
KEY Keyword selecting the output item used to sort the printed output. The default
produces output sorted on either frequency (SORT2) or ERP panel name (SORT1).
KEY=fraction produces output sorted in descending order of the fractional ERP value
of maximum ERP across all frequencies or time steps of a panel.
KEY=time produces output sorted on either time (SORT2) or ERP panel name
(SORT1). In transient the default KEY=frequency will automatically become
KEY=time.
FILTER Keyword specifying the value of a filter to be applied to the printed output only. ERP
values are printed only if the fractional ERP value of maximum ERP across all
frequencies or time steps of a panel exceeds the filter value.
ERPRHO Fluid density for Equivalent Radiated Power (ERP) analysis. This item is actually an
MSC Nastran parameter.
ERPC Phase speed of the fluid for Equivalent Radiated Power (ERP) analysis. This item is
actually an Nastran parameter.
ERPRLF Radiation loss factor. In frequency the scale factor C = ERPRLF * (½ERPRHO *
ERPC). In transient the scale factor C = ERPRLF * (ERPRHO * ERPC).
RHOCP Scale factor used in dB computation. This item is actually an MSC Nastran parameter.
ERPREFDB Scale factor used in dB computation. This item is actually an MSC Nastran parameter.
ERP
The dB calculation is ERPdB = 10 log RHOCP ------------------------------ .
ERPREFDB
CSV Results will be written to a .csv file.
unit Unit of the .csv file as used on the required ASSIGN statement.
ALL ERP output for ALL panels computed.
setp Identifier of case control SET command defining NAMEi entries from an ERPPNL
Bulk Data entry defining panels.
NONE No ERP output is produced.
Remarks:
1. ERP is required to produce any ERP output and ERP request must appear either above SUBCASE
level or within 1st SUBCASE. Subsequent SUBCASEs, from 2nd onwards, may or may not have
ERP request.
2. Output is generated in SORT2 by default. Unlike other Case Control requesting SORT2 format, the
ERP command does not force all other output into SORT2 format.
3. FILTER has no effect on PUNCHed, CSV or OP2 output.
Main Index
318 MSC Nastran Quick Reference Guide
Equivalent Radiated Power Panel Participation Factor Output Request
4. In addition to individual panel output a summary named ALLPANEL is produced. If there are
multiple subcases, the panel name is formed from the serial subcase number (1-nsubc) and the
characters ‘ALLP’ as in ALLP0002 unless the ERP command request output for ALL panels across
the Subcases. In this case, the summary panel name ALLPANEL is retained.
5. Selectable frequencies are dependent on the presence of an OFREQ Case Control command.
6. ERPRHO, ERPC, ERPRLF, RHOCP, and ERPREFDB are actually PARAM,name,value entries.
7. The filter process avoids printing ERP for cases where ERP/ERPMAX is less than the FILTER value.
ERPMAX is the maximum ERP value across all frequencies for a panel.
8. If output to a .csv file is requested, the file must be assigned with logical key USERFILE and
FORM=FORMATTED, e.g.,
ASSIGN USERFILE = myfile.csv UNIT=50 FORM=FORMATTED STATUS=NEW
9. The MPF of ERP will be computed with the same parameters, such as SOLUTION, csv, setp and etc.
10. MPFs for ERP are sorted by increasing order of natural frequencies unless the MPFSORT keyword
specifies a different sorting order. If a sorting order is specified, the KEY keyword selects the item that
is used for sorting. Since ERP is always positive, ABSA/ALGA and ABSD/ALGD will produce same
sorting results.
11. Element ERP includes elements defined via ERPPNL and SET3. For 3D element types, such as
HEXA, PENTA and TETRA, element ERP includes those elements at the outer surface of the model.
For an element with multiple faces exposed, the element ERP is the summation of ERP of all exposed
faces.
12. MPF for ERP and element ERP may increases the volume of output significantly.
13. Mathematically ERP calculated with squares of normal velocity multiplied with element area. The
sum over this product, multiplied with a constant yield the ERP over a panel. ERP values can be
calculated for both structure and structure-fluid models.
panel
2
ERP = C V n S
surf
where, C = ERPRLF ERPRHO ERPC
and = 1/2 for frequency response and = 1 for transient response.
Only direct frequency response and modal frequency response are supported. In addition to the ERP
calculation, an ERPDB calculation is also performed to calculate an equivalent radiated power sound
pressure level.
RHOCP
ERPdb = log 10 -------------------------------- ERP value
ERPREFDB
14. Peak frequency search is controlled by Case Control command, PEAKOUT, which is activated by
Solution=peak
Main Index
CHAPTER 5 319
Element Strain Energy Output Request
ESE (Case) Element Strain Energy Output Request
Requests the output of the strain energy in selected elements.
Note that ESE is not supported in NLPERF SOL 400.
Format:
NONE AVERAGE
PRINT, PUNCH PRINT, PUNCH
ESE ( ODS = sid AMPLITUDE
PLOT PLOT
ALL PEAK
THRESH = p NOPERCENT = ALL
n
Examples:
ESE=ALL
ESE (PUNCH, THRESH=.0001)=19
ESE (ODS(PLOT)=ALL, PLOT, PUNCH) = 100
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in
Bulk Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being
deprecated.
ODS Requests Operational Deflection Shape (ODS) element strain energy output. See
Remark 12.
sid Set identification of a previously appearing SET command. Only strain energy at
the elements that appear on this SET command will be output as ODS element
strain energies (Integer > 0).
AVERAGE Requests average energy in frequency response analysis only.
AMPLITUDE Requests amplitude of energy in frequency response analysis only.
Main Index
320 MSC Nastran Quick Reference Guide
Element Strain Energy Output Request
Describer Meaning
PEAK Requests peak energy for frequency response analysis only. PEAK is the sum of
AVERAGE and AMPLITUDE.
THRESH Energies for elements having an energy value of less than p% will be suppressed
in all output files: print, punch, plot, .op2, and .xdb. THRESH overrides the
value of TINY described in Remark 1. (Default = 0.001).
NOPERCENT Do not compute TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM and
PERCENT OF TOTAL. The values will appear as zeros. Sparse data recovery and
NOPERCENT can result in significant reduction in computing resources. But if
RTYPE=TOTSE appears on a DRESP1 entry then full data recovery is necessary
and no savings will be realized.
ALL Energy values for all elements will be computed.
n Set identification number. Energy for all elements specified on the SET n
command will be computed. The SET n command must be specified in the same
subcase as the ESE command, or above all subcases (Integer >0).
NONE Element strain energy will not be output.
Remarks:
1. If THRESH = p is not specified, then p defaults to the values specified by user parameter TINY.
THRESH (or TINY) less than 0.0 are considered as 0.0, thus, to obtain negative strain energy values
the user, needs to set PARAM, XFLAG, 16384 to override tiny screening for ESE. This will yield all
strain energy plus, minus, zero of all elements selected.
2. The energy calculations include the contribution of initial thermal strain.
3. Energy density (element strain energy divided by element volume) is also computed in some solution
sequences. It can be suppressed by use of PARAM,EST,-1.
4. For frequency response analysis, the energy may be computed in one of three ways as selected by
AVERAGE:
1 T T
E o = --- u r K e u r + u i K e u i
4
AMPLITUDE:
1 T T 2 T 2
E a = --- u r K e u r – u i K e u i + 2 u r K e u i
4
PEAK:
Epeak = Eo + Ea
where:
Main Index
CHAPTER 5 321
Element Strain Energy Output Request
E = elemental energy.
{ur} = displacement (real part).
{ui} = displacement (imaginary part).
[Ke] = elemental stiffness.
5. In SOLs 111 and 112, ESE is not available if both PARAM,DDRMM,0 and
PARAM,SPARSEDR,NO are specified.
6. Element data recovery for thermal loads is not currently implemented in dynamics.
7. Element strain energy is available for nonlinear static analysis (SOL 106). However, in a normal
modes analysis in SOL 106 with PARAM,NMLOOP (or ANALYSIS=MODES) or a PARAM
NMLOOP restart into SOL 103, energies are computed for elements with linear properties only. ESE
output request is also available in SOL 400 linear and nonlinear static analyses as well as multi-
disciplinary and linear perturbation analyses using MODES and MCEIG types of analysis. All other
nonlinear solution sequences do not support element strain energy output.
8. The strain energy for nonlinear elements is calculated by integrating the specific energy rate, the inner
product of strain rate, and stress over element volume and time.
t
·T
E = dV d (5-10)
0V
where:
= stress tensor
·
= tensor of the strain rate
V = element volume
t = actual time in the load history
Loads from temperature changes are included in Eq. (5-10). If we assume a linear variation of
temperatures from subcase to subcase, then the strain energy in Eq. (5-10) for the special case of linear
material and geometry becomes
1 T 1 T
E = --- u K e u – --- u P et (5-11)
2 2
where P et is the element load vector for temperature differences.
For linear elements, the default definition of element strain energy is
1 T T
E = --- u K e u – u P et (5-12)
2
Main Index
322 MSC Nastran Quick Reference Guide
Element Strain Energy Output Request
where P et is the element load vector for temperature differences and element deformation.
In Eq. (5-12), the temperatures are assumed to be constant within a subcase. The default definition of
the strain energy for linear elements differs from the definition for nonlinear elements by a factor of
1/2 in the temperature loads. To request the strain energy for linear elements using Eq. (5-11), set the
parameter XFLAG to 2; the default value for XFLAG is 0, which uses Eq. (5-12) for the strain energy
of linear elements.
9. The usages of REPCASE and OMODES Case Control directives is not supported for ESE, EKE,
EDE and GPFO output selections and should not be used.
10. If there are any frequency dependent CBUSH elements present, and PARAM, BUSHNM, NO; then
all CBUSH elements will be excluded from the element strain energy output.
1 T
11. For transient response, ESE is computed in a quasi-static manner at each time step: --- u K e u ; where
2
Ke is elemental stiffness and u is displacement.
12. ODS request must work with Case Control command, ODSFREQ, which specifies a selection of the
excitation frequencies for ODS output.
Main Index
CHAPTER 5 323
Saves a Load Vector on the Database for Subsequent Reuse
EXPORTLD (Case) Saves a Load Vector on the Database for Subsequent Reuse
Saves the load vector for the current subcase on the database.
Format:
EXPORTLD ( LOADID = lid LOADNAME = Idname = n
ALL
Examples:
EXPO(LOADNAME=LANDGEAR)
EXPORTLD=10
Describer Meaning
LOADID=lid User assignable value for the LOADID describer. Used to uniquely identify a
saved load vector for later retrieval (using DBLOCATE, for example). The
default value is the subcase ID.
LOADNAME=Idname User-assignable value (of up to eight characters) for the LOADNAME
describer. Used to uniquely identify a saved load vector for later retrieval. The
default value is blank.
N Results for grid point components in SET n will be exported.
ALL Results for ALL grid point components will be exported. Default is ALL.
Remarks:
1. Each load vector is stored individually as a one column matrix that is qualified by LOADID and
LOADNAME. The combination of both the LOADID and the LOADNAME describers should
uniquely identify the load vector to avoid overwriting (or possibly triggering the output twice rule an
existing load vector).
2. If placed above the SUBCASE entry, then the load vectors for all subcases are saved.
3. The load vectors are qualified by LOADID and LOADNAME for selection using the WHERE clause
on FMS commands that support it.
4. The following table shows the value of the LOADID and LOADNAME describers that are assigned
for various EXPORTLD requests:
Main Index
324 MSC Nastran Quick Reference Guide
Saves a Load Vector on the Database for Subsequent Reuse
Example Results
EXPORTLD LOADID=subcase ID, LOADNAME=’ ‘ -
default value applied.
EXPORTLD(LOADID=12) LOADID=12, LOADNAME=’ ‘
EXPORTLD(LOADID=1,LOADNAME=F LOADID=1, LOADNAME=’FORCE12’
ORCE12)
EXPORTLD(LOADNAME=ALLCASES) LOADID=subcase ID,
LOADNAME=’ALLCASES’
5. The load vector is typically imported into a run using the FMS DBLOCATE statement. The
imported load is referenced by using its LOADID value on a LOAD Case Control command or Bulk
Data entry. For example:
ASSIGN loads1=’run1.MASTER’
DBLOCATE datablk=(EXTLD) WHERE(LOADNAME=’ALLCASES’),
CONVERT (LOADID=LOADID+1000) LOGICAL=loads1
...
CEND
LOADS=1001 $ Select external load with LOADID=1001, imported from
previous run.
Main Index
CHAPTER 5 325
External Superelement Data Recovery Restart Run Request
EXTDRIN (Case) External Superelement Data Recovery Restart Run Request
Requests the job to perform an external superelement data recovery restart. Also specifies the storage media
of the boundary solution data.
DMIGOP2 = unitop2
Format:
MATRIXOP4orMATOP4 = unitop4
EXTDRIN MATRIX or MATDB
DMIGDB
Examples:
EXTDRIN
EXTDRIN(DMIGOP2=45)
EXTDRIN(MATOP4)
Describer Meaning
DMIGOP2 = unitop2 Retrieve the boundary solution data stored in DMIG Bulk Data internal format
on an .op2 file whose Fortran unit number is given by unitop2 (Integer > 0,
Default=31).
MATRIXOP4 or Retrieve the boundary solution data on an .op4 file whose Fortran unit number
MATOP4 = unitop4 is given by unitop4. (Integer > 0, Default=31).
MATRIXDB or Retrieve the boundary solution data stored in the standard matrix format from
MATDB the database.
DMIGDB Retrieve the boundary solution data stored in the DMIG Bulk Data internal
format from the database.
Remarks:
1. EXTDRIN is intended for step three in external superelement analysis. External superelement data
recovery is accomplished by restarting from the data base created in step one (external superelement
creation run) and attaching the boundary solution data from step two (assembly run). The boundary
solution data must have been stored in step two via the EXTDROUT Case Control command or user
parameter EXTDROUT.
2. External superelement data recovery restarts are limited to SOLs 101, 103, 107 through 112, and
400.
3. EXTDRIN must be specified above all subcases.
4. User parameters EXTDR and EXTDRUNT are the old method for requesting an external
superelement data recovery restart. EXTDRIN Case Control command takes precedence over the
EXTDR and EXTDRUNT user parameters.
5. If data recovery is desired for the external component in SOLs 101, 103, 107 through 112 and 400,
there are four methods to transmit the displacements of the reduced model, in Step 2, to the external
full model. The method is selected by the EXTDROUT Case Control command in Step 2. The
options are as follows:
Main Index
326 MSC Nastran Quick Reference Guide
External Superelement Data Recovery Restart Run Request
a. EXTDROUT(MATRIXDB[=dbext]). The displacements of the reduced component model are
stored directly on the database. The sequencing of the displacement degrees-of-freedom
corresponds to the sequencing in the reduced model. Keyword dbext exports the boundary
solution data to a new DBset initialized by the “INIT dbext” statement in the File Management
section of the input.
b. EXTDROUT(DMIGDB[=dbext]). The displacements of the reduced model are stored on the
database in a format which allows automatic connection to the reduced component model if the
reduction grid points and scalar points are the same grid points and scalar points used in the
analysis model. Keyword dbext exports the boundary solution data to a new DBset initialized by
the “INIT dbext” statement in the File Management section of the input.
c. EXTDROUT(DMIGOP2=unit). The same as EXTDROUT(DMIGDB) except that the
displacements of the reduced model are written into a .op2 file using a unit specified by the unit
keyword (Default=31) and the output unit can be assigned to a specific file by using an ASSIGN
OUTPUT2 command in the File Management Section.
d. EXTDROUT(MATOP4=unit). The same as EXTDROUT(MATRIXDB) except that the
displacements of the reduced model are written into a .op4 file using a unit specified by the unit
keyword (Default=31) and the output unit can be assigned to a specific file by using an ASSIGN
OUTPUT4 command in the File Management Section.
Data recovery restart for the external superelement (Step 3) is available in SOLs 101, 103, 107
through 112, and 400 and is accomplished by using a restart procedure from the data base created in
Step 1 and specifying the EXTDRIN Case Control command to import the solutions from Step 2.
The method on inputting the reduced displacements into the component model depends on the
method used to output the external component in Step 2. The setups for Steps 2 and 3 are:
Main Index
CHAPTER 5 327
External Superelement Data Recovery Restart Run Request
EXTDROUT Step-2 Step-3
Option Assembly Job Data Recovery for External SE
MATRIXDB, If dbext is specified in EXTDROUT In FMS:
or DMIGDB then in FMS:
ASSIGN SEXX=’step1.MASTER’
RESTART LOGICAL=SEXX
INIT dbext ASSIGN SEYYY=’step2.MASTER’
DBLOCATE DATABLK=(EXTDB),
In Case Control: WHERE(SEID=YYY), LOGICAL=SEYYY
EXTDROUT(MATRIXDB(or
DMIGDB)[=dbext]) In Case Control:
EXTDRIN(MATRIXDB or DMIGDB)
On command line run with scr=no
assuming job name is called
‘step2.dat’
DMIGOP2 In FMS: In FMS:
ASSIGN ASSIGN SEXX=’step1.MASTER’
OUTPUT2=’extsedr.op2’, RESTART LOGICAL=SEXX
UNIT=45 ASSIGN INPUTT2=’extsedr.op2’,
UNIT=45
In Case Control:
In Case Control:
EXTDROUT(DMIGOP2=45)
EXTDRIN(DMIGOP2=45)
MATOP4 In FMS: In FMS:
ASSIGN ASSIGN SEXX=’step1.MASTER’
OUTPUT4=’extsedr.op4’, RESTART LOGICAL=SEXX
UNIT=45 ASSIGN INPUTT4=’extsedr.op4’,
UNIT=45
In Case Control:
EXTDROUT(MATOP4=45)
In Case Control:
EXTDRIN(MATOP4=45)
6. For SOL 101, the Step 3 Case Control structure must match the system model subcase structure in
the numbers of loading conditions. The loading used in step one to generate the loads transmitted to
the analysis model must also be specified in this step. If the analysis model had more loading
conditions than the component model, then the loadings defined in Step 1 must be specified first.
7. For SOLs 103 and 107 through 112, the Step 3 Case Control structure must match the analysis
model subcase structure in the number of eigenvalue extractions, FREQ/DLOAD or
TSTEP/DLOAD subcases.
Main Index
328 MSC Nastran Quick Reference Guide
External Superelement Data Recovery Restart Run Request
8. SOL 400 with multidisciplinary and linear perturbation analyses will produce multiple boundary
solutions in Step 2; i.e., a boundary solution for each SUBCASE with a unique ANALYSIS
command. Hence in SOL 400 for Step 3 as soon as the boundary solutions have been imported, a
summary of the boundary solutions will be printed in the f06. Here is a sample:
=====================================================================================================================================
Assembly Run Solutions
==========|==========|==========|==========|==========|==============================================================================
Solution | Analysis | | | Super- |
ID | type | Subcase | Step | element | Title/Subtitle/Label
==========|==========|==========|==========|==========|==============================================================================
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
1 | STATICS | 2 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | STATICS
| |----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
| | 5 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | STATICS FOR BUCKLING ANALYSIS
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
2 | MODES | 7 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | NORMAL MODES - SOLVE ALL EIGENVALUES
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
3 | BUCKLE | 6 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | BUCKLING - SOLVE ALL EIGENVALUES
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
4 | MODES | 3 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | MODAL FREQUENCY - FOUR FREQUENCIES AND DELTA-F=.001 AND F1=1.04
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
5 | MFREQ | 3 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | MODAL FREQUENCY - FOUR FREQUENCIES AND DELTA-F=.001 AND F1=1.04
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
6 | MODES | 1 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | MODAL TRANSIENT - FIFTY TIME STEPS AND DELTA-T=.001
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
7 | MTRAN | 1 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | MODAL TRANSIENT - FIFTY TIME STEPS AND DELTA-T=.001
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODEL T-6A (NTA) SEPARATION LOADS ANALYSIS, 270 KEAS
8 | MCEIG | 4 | 0 | 100 | HALF AIRCRAFT MODEL WITH PYLON & HMP,CNTRLS LOCKED
| | | | | MODAL COMPLEX - SOLVE FOR FIRST FIVE EIGENVALUES
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
The “Solution ID” column contains an arbitrary identification number which may be specified on
the SOLUTION Case Control command in Step 3 whose usage will be described below. The
“Analysis Type”, “Subcase”, and “Step” columns are the same as the ANALYSIS, SUBCASE, and
STEP commands specified on Step 2. The “Superelement” column pertains the external
superelement ID processed in Step 2. The “Title/Subtitle/Label” is taken from the TITLE,
SUBTITLE, and LABEL commands specified in Step 2.
In Step 3, as with any restart, the Case Control must contain the same loads and boundary condition
(LBC) commands specified in Step 1 like LOAD, SPC, MPC, METHOD, etc. If there is only one
subcase specified in Step 3 then, by default, SOL 400 will perform external superelement data
recovery for all solutions above. Here is a sample Step 3 Case Control setup:
EXTDRIN ...
SPC=1
MPC=3
LOAD=5
$
DISP=ALL
STRESS=ALL
The displacement and element stress request for all solutions listed in the table above will be
computed.
Main Index
CHAPTER 5 329
External Superelement Data Recovery Restart Run Request
If, however, data recovery is desired at only a few solutions then a SUBCASE and SOLUTION
command pair is required to obtain data recovery at each of the desired solutions. The subcases may
be specified in any order and the SOLUTION command specifies the desired “Solution ID” from
the table above. For example,
EXTDRIN ...
SPC=1
MPC=3
SUBCASE 1
SOLUTION=5
STRESS=ALL
SUBCASE 2
SOLUTION=3
DISP=ALL
Alternatively, the ANALYSIS command may be used instead of the SOLUTION command. For
example,
EXTDRIN ...
SPC=1
MPC=3
SUBCASE 1
ANALYSIS=MFREQ
STRESS=ALL
SUBCASE 2
ANALYSIS=BUCKLE
DISP=ALL
If there is more than on solution associated with a particular analysis type, then results will be
computed for all “Solution IDs” corresponding to that analysis type.
9. In Step 2, more than one external superelement may be processed by EXTDROUT. The following
must be noted if DMIGOP2 or MATOP4 is used.
a. In SOLs 101, 103, and 107 through 112, the user must specify separate EXTDROUT as shown
in the example below:
SUBCASE 1
SUPER=10
EXTDROUT(DMIGOP2=45)
SUBCASE 2
SUPER=20
EXTDROUT(DMIGOP2=46)
b. In SOL 400, the user may specify separate EXTDROUT as described above or the same
EXTDROUT command for all external superelements. If the user specifies the same
EXTDROUT, then in the 3rd step a fatal message will be issued as shown below:
=====================================================================================================================================
Assembly Run Solutions
==========|==========|==========|==========|==========|==============================================================================
Solution | Analysis | | | Super- |
ID | type | Subcase | Step | element | Title/Subtitle/Label
==========|==========|==========|==========|==========|==============================================================================
| | | | | MODAL, 3-STEP EXTERNAL SE, DMIGDB, ASSEMBLY
1 | MODES | 1 | 0 | 10 |
| | | | |
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
| | | | | MODAL, 3-STEP EXTERNAL SE, DMIGDB, ASSEMBLY
2 | MODES | 1 | 0 | 20 |
| | | | |
----------|----------|----------|----------|----------|------------------------------------------------------------------------------
*** USER FATAL MESSAGE 22907 (EXTDRSUM)
Main Index
330 MSC Nastran Quick Reference Guide
External Superelement Data Recovery Restart Run Request
The attached boundary solutions %1 contains solutions for more than one external superelement
and the desired superelement ID has not been selected.
USER ACTION: If the EXTDROUT Case Control command (or PARAM,EXTDROUT) specified DMIGOP2 or
MATOP4 then you must specify the superelement ID on the SUPER Case Control
command to select the appropriate boundary solution.
If EXTDROUT Case Control command (or PARAM,EXTDROUT) specified MATRIXDB or
DMIGDB then you must specify the superelement ID
a) On the SUPER Case Control command to select the appropiate boundary solution.
or
b) In the WHERE(SEID=superelement_ID) clause on the DBLOCATE statement of the
boundary solutions database to select the appropiate boundary solution.
The summary shows that the solution file contains solutions for superelements 10 and 20 and the
message indicates that only one solution may be processed. So the user must specify the SUPER
command to select the desired superelement; e.g.,
SUPER=10
EXTDRIN(DMIGOP2=45)
Alternatively for EXTDRIN(DMIGDB or MATRIXDB) only, the user may specify
WHERE(SEID=10) on the DBLOCATE statement of the boundary solution database.
10. The following examples continue from the examples described in Remark 18 under the EXTSEOUT
Case Control command description.
Example 1. MATDB / MATRIXDB or DMIGDB Option
Assembly Job (assume input file is named “assembly.dat”)
• File Management Section (FMS) Requirement only if it is desired to store the
boundary solutions on a dbset separate from DBALL
INIT EXTDRDB
• Case Control Requirement for MATDB / MATRIXDB Option.
Store boundary solutions on the DBALL dbset
EXTDROUT
Store boundary solutions on the EXTDRDB dbset
EXTDROUT ( MATRIXDB = EXTDRDB )
• Case Control Requirement for DMIGDB Option
Store boundary solutions on the DBALL dbset
EXTDROUT ( DMIGDB )
Store boundary solutions on the EXTDRDB dbset
EXTDROUT ( DMIGDB = EXTDRDB )
For all options above, “scr = no” must be specified on the Nastran command line to ensure that
the databases are saved at the end of the jobs.
External Superelement Data Recovery Restart Job (repeat following setup for each
superelement)
• File Management Section (FMS) Requirement
Main Index
CHAPTER 5 331
External Superelement Data Recovery Restart Run Request
Example 1. MATDB / MATRIXDB or DMIGDB Option
ASSIGN SE10=’extse10.MASTER’
RESTART LOGI=SE10
ASSIGN ASMB=’assembly.MASTER’
DBLOC DATABLK=(EXTDB) WHERE(SEID=10) LOGI=SE10
• Case Control Requirement for MATDB / MATRIXDB Option
EXTDRIN
• Case Control Requirement for DMIGDB Option
EXTDRIN ( DMIGDB )
Example 2. DMIGOP2 Option
Assembly Job
• Setup for SOLs 101, 103, 107 through 112, and 400 each superelement boundary
solution is stored on a separate Fortran unit
• File Management Section (FMS) Requirement
ASSIGN OUTPUT2=’extse10dr.op2’ UNIT=25 DELETE
ASSIGN OUTPUT2=’extse20dr.op2’ UNIT=26 DELETE
ASSIGN OUTPUT2=’extse30dr.op2’ UNIT=27 DELETE
• Case Control Requirement
SUBCASE 1
SUPER = 10
EXTDROUT ( DMIGOP2 = 25 )
SUBCASE 2
SUPER = 20
EXTDROUT ( DMIGOP2 = 26 )
SUBCASE 3
SUPER = 30
EXTDROUT ( DMIGOP2 = 27 )
• Alternative setup for SOL 400 only – all superelement boundary solutions are
stored on the same Fortran unit
• File Management Section (FMS) Requirement
ASSIGN OUTPUT2=’extalldr.op2’ UNIT=25 DELETE
• Case Control Requirement
EXTDROUT ( DMIGOP2 = 25 )
External Superelement Data Recovery Restart Job (repeat following setup for each
superelement)
• Setup for SOLs 101, 103, 107 through 112, and 400
Main Index
332 MSC Nastran Quick Reference Guide
External Superelement Data Recovery Restart Run Request
Example 2. DMIGOP2 Option
• File Management Section (FMS) Requirement
ASSIGN SE10=’extse10.MASTER’
RESTART LOGICAL=SE10
ASSIGN INPUTT2=’extse10dr.op2’ UNIT=25
• Case Control Requirement
EXTDRIN ( DMIGOP2 = 25 )
• Alternative setup for SOL 400 only – all superelement boundary solutions are
stored on the same Fortran unit
• File Management Section (FMS) Requirement
ASSIGN SE10=’extse10.MASTER’
RESTART LOGICAL=SE10
ASSIGN INPUTT2=’extalldr.op2’ UNIT=25
• Case Control Requirement – SUPER command is required to select the correct
superelement boundary solution
SUPER = 10
EXTDRIN ( DMIGOP2 = 25 )
Example 3. MATOP4 Option
Assembly Job
• Setup for SOLs 101, 103, 107 through 112, and 400 each superelement boundary
solution is stored on a separate Fortran unit.
• File Management Section (FMS) Requirement
ASSIGN OUTPUT4=’extse10dr.op4’ UNIT=25 DELETE
ASSIGN OUTPUT4=’extse20dr.op4’ UNIT=26 DELETE
ASSIGN OUTPUT4=’extse30dr.op4’ UNIT=27 DELETE
• Case Control Requirement
SUBCASE 1
SUPER = 10
EXTDROUT ( MATOP4 = 25 )
SUBCASE 2
SUPER = 20
EXTDROUT ( MATOP4 = 26 )
SUBCASE 3
SUPER = 30
EXTDROUT ( MATOP4 = 27 )
• Alternative setup for SOL 400 only – all superelement boundary solutions are
stored on the same Fortran unit.
Main Index
CHAPTER 5 333
External Superelement Data Recovery Restart Run Request
Example 3. MATOP4 Option
• File Management Section (FMS) Requirement
ASSIGN OUTPUT4=’extalldr.op4’ UNIT=25 DELETE
• Case Control Requirement
EXTDROUT ( MATOP4 = 25 )
External Superelement Data Recovery Restart Job (repeat following setup for each
superelement)
• Setup for SOLs 101, 103, 107 through 112, and 400
• File Management Section (FMS) Requirement
ASSIGN SE10=’extse10.MASTER’
RESTART LOGICAL=SE10
ASSIGN INPUTT4=’extse10dr.op4’ UNIT=25
• Case Control Requirement
EXTDRIN ( MATOP4 = 25 )
Alternative setup for SOL 400 only – all superelement boundary solutions are stored
on the same Fortran unit
• File Management Section (FMS) Requirement
ASSIGN SE10=’extse10.MASTER’
RESTART LOGICAL=SE10
ASSIGN INPUTT4=’extalldr.op4’ UNIT=25
• Case Control Requirement – SUPER command is required to select the correct
superelement boundary solution
SUPER = 10
EXTDRIN ( MATOP4 = 25 )
Main Index
334 MSC Nastran Quick Reference Guide
External Superelement Boundary Solution Storage Request.
EXTDROUT (Case) External Superelement Boundary Solution Storage Request.
Requests the job to store external superelement boundary displacements and column labels; e.g., eigenvalues,
forcing frequencies, time steps. Also specifies the storage media of the boundary solution data.
DMIGOP2 = unitop2
Format:
MATRIXOP4orMATOP4 = unitop4 NOCASE
EXTDROUT MATRIXDBorMATDB = dbext
DMIGDB = dbext
Examples:
EXTDROUT
EXTDROUT(DMIGOP2=45)
EXTDROUT(MATOP4 NOCASE)
Describer Meaning
DMIGOP2 = unitop2 Store the boundary solution data in DMIG Bulk Data internal format on an
.op2 file whose Fortran unit number is given by unitop2 (Integer > 0,
Default=31).
MATRIXOP4 or Store the boundary solution data on an .op4 file whose Fortran unit number is
MATOP4 = unitop4 given by unitop4. (Integer ≠ 0, Default=31). unitop4 is a non-zero integer with
the following meanings:
unitop4 > 0: Store in sparse format
unitop4 < 0: Store in non-sparse format on Fortran unit number given by
|unitop4
MATRIXDB or Store the boundary solution data in the standard matrix format in the database.
MATDB = dbext Dbext is the name of a new dbset on which to store the boundary data. Dbext
must be allocated on an INIT FMS statement.
DMIGDB Store the boundary solution data in the DMIG Bulk Data internal format in
the database. Dbext is the name of a new dbset on which to store the boundary
data. Dbext must be allocated on an INIT FMS statement.
NOCASE NOCASEBy default in SOL 400 only, the TITLE/SUBTITLE/LABEL
contents are exported along with boundary data. Specify NOCASE if you do
not want these contents to be exported.
Remarks:
1. EXTDROUT is intended for step two (or assembly run) in external superelement analysis.
2. EXTDROUT is honored in SOLs 101, 103, 107 through 112, and 400 only.
Main Index
CHAPTER 5 335
External Superelement Boundary Solution Storage Request.
3. In SOLs 101, 103, and 107 through 112, if there are multiple external superelements and DMIGOP2
or MATOP4 is requested then EXTDROUT must be specified in separate subcases for each external
superelement along with the SUPER command and unitop4 or unitop2 must be unique for each
external superelement. Separate EXTDROUT commands are not required in SOL 400. See Remarks
9. and 10. under the EXTDRIN Case Control command description.
4. User parameters EXTDROUT and EXTDRUNT are the old method for requesting the storage of
boundary solution data. EXTDROUT Case Control command takes precedence over the
EXTDROUT and EXTDRUNT user parameters.
5. See EXTDRIN’s case control command description for a description of EXTDROUT and
EXTDRIN usage.
Main Index
336 MSC Nastran Quick Reference Guide
External Module Creation Specification
EXTMDOUT (Case) External Module Creation Specification
Request the creation of an external module in SOLs 101, 103, 107 through 112, or 400 only.
Format:
EXTMDOUT STIFFNESS MASS DAMPING K4DAMP LOADS,
MAN
ASMBULK = EXTBULK , EXTID = mdid
AUTO
MATDB (or MATRIXDB) = dbext
DMIGDB = dbext
cccccc
DMIGSFIX = DMIGOP2 = unitop2
EXTID
DMIGPCH
MATOP4 (or MATRIXOP4) = unitop4
Example(s):
EXTMDOUT
EXTMDOUT(DMIGOP2=26)
EXTMDOUT(ASMBULK EXTID=200)
EXTMDOUT(ASMBULK EXTBULK EXTID=100)
EXTMDOUT(ASMBULK=AUTO EXTBULK EXTID=100)
EXTMDOUT(ASMBULK=MANQ EXTID=10 DMIGDB)
EXTMDOUT(ASMBULK EXTID=100 DMIGOP2=26)
EXTMDOUT(ASMBULK EXTID=100 DMIGPCH)
EXTMDOUT(ASMBULK EXTID=100 DMIGSFIX=XSE100 DMIGPCH)
EXTMDOUT(ASMBULK EXTID=200 DMIGSFIX=EXTID DMIGPCH)
EXTMDOUT(ASMBULK EXTID=100 MATOP4=26)
EXTMDOUT(ASMBULK EXTID=200 MATOP4=-25)
(See also Remarks 17. and 18.)
.
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 1. and 2.
K4DAMP Store the boundary structural damping matrix. See Remark 1.
Main Index
CHAPTER 5 337
External Module Creation Specification
Describer Meaning
LOADS Store the boundary static loads matrix. See Remark 1.
ASMBULK or Generate Bulk Data entries for use in a subsequent module assembly process
ASMBULK = MAN and store them on the assembly punch file (.asm). This data, which is used
in the main bulk data portion of a subsequent assembly job, includes an
MDBULK entry that specifies MANUAL as the method for searching
boundary points, and an MDCONCT entry that defines connections for
boundary grid and scalar points. See Remarks 3., 5., and 14.
ASMBULK = AUTO Generate Bulk Data entries for use in a subsequent module assembly process,
and store them on the assembly punch file (.asm). This data, which is to be
used in the main bulk data portion of a subsequent assembly job, includes
an MDBULK entry that specifies AUTO as the method for searching
boundary points, and an MDCONCT entry that defines connections for
boundary scalar points. See Remarks 3., 5., and 14.
EXTBULK Generate Bulk Data entries related to the external module and store them on
the standard punch file (.pch). This data is used in the BEGIN MODULE
portion of the bulk data of a subsequent assembly job. EXTBULK need not
be specified if DMIGPCH or MATOP4 (see the following descriptions) is
specified. See Remarks 3., 6., 7. and 14.
Note that, in general, the EXTBULK keyword is not required and is
provided solely for user convenience. In the absence of EXTBULK and the
associated output on the standard punch file resulting from it, the
subsequent assembly job will retrieve the required data for the external
superelement from the medium on which the boundary matrices are stored.
EXTID=mdid mdid (integer > 0) is the module ID to be used on the MDBULK and
MDCONCT (if applicable) Bulk Data entries stored on the assembly punch
file (.asm) if ASMBULK is specified, and in the BEGIN MODULE Bulk
Data entry stored on the standard punch file (.pch) if EXTBULK or
DMIGPCH is specified. See Remarks 3. to 8., 12., and 16.
DMIGSFIX = cccccc cccccc is the suffix (up to six characters) to be employed in the names of the
DMIG matrices stored on the standard punch file (.pch) if the DMIGPCH
option is specified. See Remarks 9. to 12. See also Example 3 in Remark 17.
DMIGSFIX = EXTID The mdid defined by the EXTID keyword is the suffix to be employed in the
names of the DMIG matrices stored on the standard punch file (.pch) if the
DMIGPCH option is specified. See Remarks 3., 9. to 12. See also Example 3
in Remark 17.
MATDB Store the boundary matrices and other information on the database. Dbext
(or MATRIXDB) = dbext is the name of a new dbset on which to store the boundary matrices. Dbext
(Default) must be allocated on an INIT FMS statement. By default, matrices are
stored on DBALL. See Example 1 in Remark 17.
Main Index
338 MSC Nastran Quick Reference Guide
External Module Creation Specification
Describer Meaning
DMIGDB= dbext Similar to MATDB (or MATRIXDB) except that the boundary matrices are
stored as DMIG Bulk Data entries on the database.Dbext is the name of a
new dbset on which to store the boundary matrices. Dbext must be allocated
on an INIT FMS statement. By default, matrices are stored on DBALL. See
Example 1 in Remark 17.
DMIGOP2 = unitop2 Store the boundary matrices as DMIG Bulk Data entries on an .op2 file
whose Fortran unit number is given by unitop2 (Integer > 0). See Remark 15.
See also Example 2 in Remark 17.
DMIGPCH Store the boundary matrices as DMIG Bulk Data entries on the standard
punch file (.pch). Note that, if boundary matrices include both structural
and fluid grids, use DMIGOP2 instead. See Remarks 3. and 6. to 14. See also
Example 3 in Remark 17.
MATOP4 = unitop4 unitop4 is a non-zero integer with the following meanings:
(or MATRIXOP4 =
unitop4) unitop4 > 0
Store the boundary matrices in sparse format on an .op4 file whose Fortran
unit number is given by unitop4
unitop4 < 0
Store the boundary matrices in non-sparse format on an .op4 file whose
Fortran unit number is given by |unitop4|
See Remarks 3., 6., 7., 14., and 15. See also Example 4 in Remark 17.
Remarks:
1. If none of the describers STIFFNESS through FSCOUP is specified, then all matrices are stored.
2. STIFFNESS and DAMPING may be abbreviated to STIF and DAMP, respectively.
3. EXTID with an mdid value must be specified if one or more of ASMBULK, EXTBULK,
DMIGPCH, or MATOP4 are specified.
If the DMIGSFIX = EXTID form is employed along with the DMIGPCH specification, the value
mdid may not exceed 999999 since this value becomes part of the names given to the DMIG matrices
generated on the standard punch file (.pch). See Remark 12., and Example 3 in Remark 17.
If PARAM,AUTOQSET,YES is specified to used generate the Q-set degrees of freedom (DOFs)
(generalized coordinates), the value mdid may not exceed 999 since this value becomes part of the
automatically generated IDs of the SPOINTs representing the Q-set DOFs. See explanation in Item
c under Remark 16.
4. If ASMBULK or ASMBULK = MAN is specified, the following Bulk Data entries are generated and
stored on the assembly punch file (.asm):
Main Index
CHAPTER 5 339
External Module Creation Specification
MDBULK mdid … (specifies MANUAL as the method for searching
boundary points)
MDCONCT mdid …(defines connections for boundary grid and scalar
points)
GRID entries for boundary and access grid points
SPOINT entries for boundary and access scalar points
CORD2x entries associated with the boundary and access GRID
entries
5. If ASMBULK = AUTO is specified, the following Bulk Data entries are generated and stored on the
assembly punch file (.asm):
MDBULK mdid … (specifies AUTO as the method for searching
boundary points)
MDCONCT mdid … (defines connections for boundary scalar
points)
GRID entries for access grid points
CORD2x entries associated with the access grid points
SPOINT entries for boundary and access scalar points
6. If DMIGPCH or MATOP4 is specified, then EXTBULK need not be specified. Also, the model
cannot have rotors (ROTOR, ROTORG, ROTORSE, and ROTORAX Bulk Data entries).
7. If DMIGPCH is not specified, but EXTBULK or MATOP4 is specified, the following Bulk Data
entries are generated and stored on the standard punch file (.pch):
BEGIN MODULE mdid
GRID entries for boundary points
GRID entries for interior points referenced by PLOTEL entries
SPOINT entries for boundary scalar points as well as for Q-set
points
CORD2x entries associated with the above GRID entries
EXTRN
ASET
PLOTEL
END MODULE
8. If DMIGPCH is specified, the following Bulk Data entries are generated and stored on the standard
punch file (.pch):
BEGIN MODULE mdid
GRID entries for boundary points
SPOINT entries for boundary scalar points as well as for Q-set
points
CORD2x entries associated with the boundary GRID entries
ASET/ASET1
PLOTEL entries referencing the boundary GRID entries
DMIG entries for the requested boundary matrices
END MODULE
9. The DMIGSFIX keyword is ignored if DMIGPCH is not specified.
10. If DMIGPCH is specified without the DMIGSFIX keyword, then the boundary DMIG matrices
generated and stored on the standard punch file (.pch) will have names of the following form:
KAAX (boundary stiffness matrix)
Main Index
340 MSC Nastran Quick Reference Guide
External Module Creation Specification
MAAX (boundary mass matrix)
BAAX (boundary viscous damping matrix)
K4AAX (boundary structural damping matrix)
PAX (boundary load matrix)
AAX (boundary fluid-structure coupling matrix)
See Example 3 in Remark 17.
11. If the DMIGSFIX = cccccc form is employed along with the DMIGPCH specification, then the
boundary DMIG matrices generated and stored on the standard punch file (.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)
Acccccc (boundary fluid-structure coupling matrix)
See Example 3 in Remark 17.
12. If the DMIGSFIX = EXTID form is employed along with the DMIGPCH specification, then the
boundary DMIG matrices generated and stored on the standard punch file (.pch) will have names of
the following form:
Kmdid (boundary stiffness matrix)
Mmdid (boundary mass matrix)
Bmdid (boundary viscous damping matrix)
K4mdid (boundary structural damping matrix)
Pmdid (boundary load matrix)
where mdid is the module ID specified by the EXTID keyword.
See Example 3 in Remark 17.
13. If the DMIGPCH option is specified, the boundary DMIG matrices generated and stored on the
standard punch file (.pch) may not be as accurate as the boundary matrices resulting from the other
options (MATDB/MATRIXDB, or DMIGOP2 ,or MATOP4). Accordingly, this may result in
decreased accuracy from the subsequent assembly job using these DMIG matrices.
14. The punch output resulting from EXTMDOUT usage is determined by ASMBULK, EXTBULK,
DMIGPCH, and MATOP4 as follows:
No ASMBULK, EXTBULK, DMIGPCH or MATOP4
No punch output.
ASMBULK, but no EXTBULK, or DMIGPCH, or MATOP4
Punch output is generated and stored on the assembly punch file (.asm) as indicated in Remarks 4.
through 5.
No ASMBULK, but EXTBULK, DMIGPCH, or MATOP4
Punch output is generated and stored on the standard punch file (.pch) as indicated in Remarks 7. or
8. (as appropriate).
Main Index
CHAPTER 5 341
External Module Creation Specification
ASMBULK and EXTBULK, DMIGPCH or MATOP4
Punch output consists of two distinct and separate parts. One part is generated and stored on the
assembly punch file (.asm) as indicated in Remarks 4. through 5. The other part is generated and
stored on the standard punch file (.pch) as indicated in Remarks 7. or 8. (as appropriate).
15. If DMIGOP2 = unitop2 or MATOP4 = unitop4 is specified, an appropriate ASSIGN OUTPUT2 or
ASSIGN OUTPUT4 statement must be present in the File Management Section (FMS) for the
specified Fortran unit numbers. See Examples 2 and 4 in Remark 17.
16. The creation of an external module using EXTMDOUT involves running a Nastran job, with the
following additional data:
a. The data for the creation of the external module is specified by the EXTMDOUT Case Control
command. It is best to specify this command above the subcase level. However, if the Nastran job
itself involves modules, then the EXTMDOUT command may also be specified within the
subcase that is applicable to the residual.
b. The boundary points of the external module are specified by ASET/ASET1 Bulk Data entries.
c. If the external module creation involves component mode reduction, then Q-set degrees of
freedom (DOFs) (generalized coordinates) must be defined. This can be done either by
automatically defining them via PARAM,AUTOQSET,YES or by explicitly specifying them via
QSET/QSET1 Bulk Data entries. Note that for the latter case of explicit definition, only
SPOINTs may be specified as Q-set points; no grid points may be specified. If this requirement
is not met, the program terminates the execution with an appropriate fatal message.
If PARAM,AUTOQSET,YES is specified, SPOINTs are automatically generated internally to
represent the Q-set DOFs. The IDs of these SPOINTs are of the form 9sssnnnn where sss is the
module ID mdid specified by the EXTID keyword, and nnnn is a mode number. Both sss and
nnnn will have leading zeros inserted in them to ensure that sss is a three-digit number and nnnn
is a four-digit number. Thus, for example, the Q-set DOF corresponding to the 8th mode of
superelement ID 5 would be represented by an SPOINT with an automatically generated ID of
90050008, while the Q-set DOF corresponding to the 50th mode of module ID 25 would be
represented by an SPOINT with an automatically generated ID of 90250050.
Because of the preceding numbering scheme, the module ID mdid specified by the EXTID
keyword must necessarily not exceed 999 when PARAM,AUTOQSET,YES is specified. The
program terminates the job with a User Fatal Message if this condition is not met.
Further, because of the preceding numbering scheme, the user should ensure that, when
PARAM,AUTOQSET,YES is specified, the IDs of the grid and scalar points of the external
module do not conflict with the automatically generated SPOINT IDs of the Q-set DOFs. The
program terminates the job with a User Fatal Message if this condition is not met.
d. The fixity of the boundary DOFs for the component mode reduction may be specified using the
BSETi/BNDFIXi and CSETi/BNDFREE/BNDFRE1 Bulk Data entries. (The default scenario
assumes that all boundary DOFs are fixed for component mode reduction.)
e. The output for the external module is generated in the assembly job. This output consists of
displacements, velocities, accelerations, SPC forces, MPC forces and element stresses, strains and
forces. However, in order for this output to be generated in the assembly job, the output requests
must be specified in the external module creation run. Normally, the only output requests for the
Main Index
342 MSC Nastran Quick Reference Guide
External Module Creation Specification
external module that are honored in the assembly job are those that are specified in the creation
run. There is, however, one important exception to this: the output for the boundary and access
grid and scalar points, as well as for all grid points associated with PLOTEL entries, can be
obtained in the assembly job even if there is no output request specified for these points in the creation
run.
If the creation run contains the load requests TEMPERATURE (LOAD) or DEFORM, then
element stresses and element forces will not be available in the assembly run.
f. If EXTMDOUT is used in SOL 400 for a multidisciplinary or linear perturbation analysis and
there are rigid elements present then RIGID=LINEAR must be specified.
17. The following examples illustrate details of job setups for the external module creation and the
subsequent assembly process for various scenarios. These examples assume that there are three
external module creation jobs, one each for external module 10 (extmd10.dat), module 20
(extmd20.dat) and module 30 (extmd30.dat), followed by an assembly job.
Example 1. MATDB / MATRIXDB or DMIGDB Option
External Module Creation Jobs
• Case Control Requirement for the MATDB / MATRIXDB option
Module 10: EXTMDOUT (ASMBULK EXTID = 10)
Module 20: EXTMDOUT (ASMBULK EXTID = 20)
Module 30: EXTMDOUT (ASMBULK EXTID = 30)
The EXTBULK keyword may be specified, but it is not necessary.
• Case Control Requirement for the DMIGDB option
Module 10: EXTMDOUT (ASMBULK EXTID = 10 DMIGDB)
Module 20: EXTMDOUT (ASMBULK EXTID = 20 DMIGDB)
Module 30: EXTMDOUT (ASMBULK EXTID = 30 DMIGDB)
For both options, scr = no should be specified on the Nastran job command line to ensure
that the databases are saved at the end of the jobs.
Assembly Job
• File Management Section (FMS) Requirement
(Note: If DBEXT was specified on the EXTMDOUT command in the External Module Creation
Jobs then the extmd10.DBALL, etc. files may be hidden (moved or renamed) from the Assembly
Job for purposes of security or privacy.)
ASSIGN dbname10=’extmd10.MASTER’
ASSIGN dbname20=’extmd20.MASTER’
ASSIGN dbname30=’extmd30.MASTER’
DBLOCATE DATABLK=(EXTDB, EXTROTDB) CONVERT(SEID=10)
LOGICAL=dbname10
Main Index
CHAPTER 5 343
External Module Creation Specification
Example 1. MATDB / MATRIXDB or DMIGDB Option (continued)
DBLOCATE DATABLK=(EXTDB,EXTROTDB) CONVERT(SEID=20)
LOGICAL=dbname20
DBLOCATE DATABLK=(EXTDB, EXTROTDB) CONVERT(SEID=30)
LOGICAL=dbname30
(Note: All of the data blocks stored on the databases for the external Modules have the
same common name of EXTDB or EXTROTDB for external Modules with rotors.)
• Bulk Data Requirement
The following INCLUDEs are required. They may be specified anywhere in the Main
Bulk Data.
INCLUDE ‘extmd10.asm’
INCLUDE ‘extmd20.asm’
INCLUDE ‘extmd30.asm’
Example 2. DMIGOP2 Option
External Module Creation Jobs
• File Management Section (FMS) Requirement
ASSIGN OUTPUT2=’extmd10_op2’ UNIT=25 DELETE
ASSIGN OUTPUT2=’extmd20_op2’ UNIT=26 DELETE
ASSIGN OUTPUT2=’extmd30_op2’ UNIT=27 DELETE
• Case Control Requirement
Module 10: EXTMDOUT (ASMBULK EXTID = 10 DMIGOP2 = 25)
Module 20: EXTMDOUT (ASMBULK EXTID = 20 DMIGOP2 = 26)
Module 30: EXTMDOUT (ASMBULK EXTID = 30 DMIGOP2 = 27)
The EXTBULK keyword may be specified, but it is not necessary.
scr = yes may be specified on the Nastran command line
Assembly Job
• File Management Section (FMS) Requirement
ASSIGN INPUTT2=’extmd10_op2’ UNIT=25
ASSIGN INPUTT2=’extmd20_op2’ UNIT=26
ASSIGN INPUTT2=’extmd30_op2’ UNIT=27
• Bulk Data Requirement
Main Index
344 MSC Nastran Quick Reference Guide
External Module Creation Specification
Example 2. DMIGOP2 Option (continued)
The following INCLUDEs are required. They may be specified anywhere in the main
bulk data.
INCLUDE ‘extmd10.asm’
INCLUDE ‘extmd20.asm’
INCLUDE ‘extmd30.asm’
Example 3. DMIGPCH Option
External Module Creation Jobs
• Case Control Requirement
Module 10: EXTMDOUT (ASMBULK EXTID = 10 DMIGPCH)
Module 20: EXTMDOUT (ASMBULK EXTID = 20 DMIGPCH,
DMIGSFIX = XSE20)
Module 30: EXTMDOUT (ASMBULK EXTID = 30 DMIGPCH,
DMIGSFIX = EXTID)
scr = yes may be specified on the Nastran command line since there is no need for the
databases to be saved at the end of the jobs.
Assembly Job
• Case Control Requirement
K2GG = (KAAX, KXSE20, K30)
M2GG = (MAAX, MXSE20, M30)
B2GG = (BAAX, BXSE20, B30)
K42GG = (K4AAX, K4XSE20, K430)
P2G = (PAX, PXSE20, P30)
A2GG = (AAX, AXSE20, A30)
• Bulk Data Requirement
The following INCLUDEs are required. They may be specified anywhere in the main
bulk data.
INCLUDE ‘extmd10.asm’
INCLUDE ‘extmd20.asm’
INCLUDE ‘extmd30.asm’
Main Index
CHAPTER 5 345
External Module Creation Specification
Example 3. DMIGPCH Option (continued)
The following INCLUDEs are also required. They must be grouped together and
specified at the very end of the main bulk data (just before the ENDDATA delimiter).
INCLUDE ‘extmd10.pch’
INCLUDE ‘extmd20.pch’
INCLUDE ‘extmd30.pch’
Example 4. MATOP4 Option
External Module Creation Jobs
• File Management Section (FMS) Requirement
ASSIGN OUTPUT4=’extmd10_op4’ UNIT=25 DELETE
ASSIGN OUTPUT4=’extmd20_op4’ UNIT=26 DELETE
ASSIGN OUTPUT4=’extmd30_op4’ UNIT=27 DELETE
• Case Control Requirement
Module 10: EXTMDOUT (ASMBULK EXTID = 10 MATOP4 = 25)
Module 20: EXTMDOUT (ASMBULK EXTID = 20 MATOP4 = 26)
Module 30: EXTMDOUT (ASMBULK EXTID = 30 MATOP4 = -27)
Note: Boundary matrices will be stored in sparse format on .op4 files with Fortran unit
numbers 25 and 26 and in non-sparse format on the .op4 file with Fortran unit number
27.
scr = yes may be specified on the Nastran command line
Assembly Job
• File Management Section (FMS) Requirement
ASSIGN INPUTT4=’extmd10_op4’ UNIT=25
ASSIGN INPUTT4=’extmd20_op4’ UNIT=26
ASSIGN INPUTT4=’extmd30_op4’ UNIT=27
• Bulk Data Requirement
The following INCLUDEs are required. They may be specified anywhere in the main
bulk data.
INCLUDE ‘extmd10.asm’
INCLUDE ‘extmd20.asm’
INCLUDE ‘extmd30.asm’
Main Index
346 MSC Nastran Quick Reference Guide
External Module Creation Specification
Example 4. MATOP4 Option (continued)
The following INCLUDEs are also required. They must be grouped together and
specified at the very end of the main bulk data (just before the ENDDATA delimiter).
INCLUDE ‘extmd10.pch’
INCLUDE ‘extmd20.pch’
INCLUDE ‘extmd30.pch’
18. If EXTBULK is specified, then METADATA entries will be copied to the .pch file.
19. Data recovery for the external module is possible via the two-step method.
a. In the two-step method, EXTMDOUT automatically generates output transformation matrices
(OTMs) based on STRESS, FORCE, DISPLACEMENT, SPCFORCE, MPCFORCE,
STRAIN, and MONITOR Case Control commands specified in the first (creation) run. Then in
the second (assembly) run, data recovery is performed on the external module. This data recovery
is limited to certain element types and specialized outputs. For example, grid point forces and
stresses, corner stresses, strain and kinetic energies, and composite stresses are not supported in
the OTMs. If Modules are present in the first run, then OTMs are generated for those grid points
and elements in Module 0 only.
b. The two-step method is described in more detail in the MSC Nastran Superelements amd Modules
User's Guide.
c. For dynamically reduced external modules, the displacement OTMs created with dynamic
reduction include both the dynamic effects of the o-set and also the fixed boundary effects of the
o-set due to interior loads. With the two-step method, only one of these effects should be included
in a SOL 101, 106 and 400 (with ANALYSIS=STATICS) assembly. Therefore, if there are
interior loads in the external module and the two-step method is being used, attaching the
dynamically reduced external modules in a static analysis of the assembly is not recommended.
20. Module can be used in conjunction with residual structures in fluid-structure interaction analysis /
acoustic analysis, with the following restrictions:
a. If the module contains both structural and fluid degrees-of-freedom (dof), then the residual
structure can only have either structural dof or fluid dof - it cannot have both.
b. Similarly, if the residual structure has both structural and fluid dof, then the module should only
have either structural dof or fluid dof - it cannot have both.
Main Index
CHAPTER 5 347
External Superelement Creation Specification
EXTSEOUT (Case) External Superelement Creation Specification
Request the creation of an external superelement in SOLs 101, 103, 107 through 112, or 400 only.
Format:
EXTSEOUT STIFFNESS MASS DAMPING K4DAMP LOADS FSCOUP,
MAN
QSET
ASMBULK = MANQ EXTBULK , EXTID = seid
ASET
AUTO
MATDB (or MATRIXDB) = dbext
DMIGDB = dbext
cccccc DMIGOP2 = unitop2
DMIGSFIX =
EXTID DMIGPCH
MATOP4 (or MATRIXOP4) = unitop4
HDF5
Example(s):
EXTSEOUT
EXTSEOUT(DMIGOP2=26)
EXTSEOUT(ASMBULK EXTID=200)
EXTSEOUT(ASMBULK EXTBULK EXTID=100)
EXTSEOUT(ASMBULK=AUTO EXTBULK EXTID=100)
EXTSEOUT(ASMBULK=MANQ EXTID=10 DMIGDB)
EXTSEOUT(ASMBULK EXTID=100 DMIGOP2=26)
EXTSEOUT(ASMBULK EXTID=100 DMIGPCH)
EXTSEOUT(ASMBULK EXTID=100 DMIGSFIX=XSE100 DMIGPCH)
EXTSEOUT(ASMBULK EXTID=200 DMIGSFIX=EXTID DMIGPCH)
EXTSEOUT(ASMBULK EXTID=100 MATOP4=26)
EXTSEOUT(ASMBULK EXTID=200 MATOP4=-25)
EXTSEOUT(ASMBULK=MANQ,EXTBULK,EXTID=20,HDF5)
(See also Remarks 17. and 18.)
Main Index
348 MSC Nastran Quick Reference Guide
External Superelement Creation Specification
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 1. and 2.
K4DAMP Store the boundary structural damping matrix. See Remark 1.
LOADS Store the boundary static loads matrix. See Remark 1.
FSCOUP Store the boundary fluid-structure coupling matrix. See Remark 1.
ASMBULK or Generate Bulk Data entries for use in a subsequent superelement assembly
ASMBULK = MAN process and store them on the assembly punch file (.asm). This data, which
is used in the main bulk data portion of a subsequent assembly job, includes
an SEBULK entry that specifies MANUAL as the method for searching
boundary points, and an SECONCT entry that defines connections for
boundary grid and scalar points. See Remarks 3., 6., and 15.
ASMBULK = MANQ Similar to the ASMBULK = MAN option, except that the generated
SECONCT entry defines connections not only for boundary grid and scalar
points, but also for Q-set points. This allows the user to have control over
the Q-set points of the external superelement in the subsequent assembly
job. See Remarks 3., 5., and 15.
ASMBULK = AUTO Generate Bulk Data entries for use in a subsequent superelement assembly
process, and store them on the assembly punch file (.asm). This data, which
is to be used in the main bulk data portion of a subsequent assembly job,
includes an SEBULK entry that specifies AUTO as the method for searching
boundary points, and an SECONCT entry that defines connections for
boundary scalar points. See Remarks 3., 6., and 15.
EXTBULK Generate Bulk Data entries related to the external superelement and store
them on the standard punch file (.pch). This data is used in the BEGIN
SUPER portion of the bulk data of a subsequent assembly job. EXTBULK
need not be specified if DMIGPCH or MATOP4 (see the following
descriptions) is specified. See Remarks 3., 7., 8., and 15.
Note that, in general, the EXTBULK keyword is not required and is
provided solely for user convenience. In the absence of EXTBULK and the
associated output on the standard punch file resulting from it, the
subsequent assembly job will retrieve the required data for the external
superelement from the medium on which the boundary matrices are stored.
EXTID=seid seid (integer > 0) is the superelement ID to be used on the SEBULK and
SECONCT (if applicable) Bulk Data entries stored on the assembly punch
file (.asm) if ASMBULK is specified, and in the BEGIN SUPER Bulk Data
entry stored on the standard punch file (.pch) if EXTBULK or DMIGPCH
is specified. See Remarks 3. - 9., 13., and 17.
Main Index
CHAPTER 5 349
External Superelement Creation Specification
Describer Meaning
DMIGSFIX = cccccc cccccc is the suffix (up to six characters) to be employed in the names of the
DMIG matrices stored on the standard punch file (.pch) if the DMIGPCH
option is specified. See Remarks 10. - 13. See also Example 3 in Remark 18.
DMIGSFIX = EXTID The seid defined by the EXTID keyword is the suffix to be employed in the
names of the DMIG matrices stored on the standard punch file (.pch) if the
DMIGPCH option is specified. See Remarks 3., 10. - 13. See also Example 3
in Remark 18.
MATDB Store the boundary matrices and other information on the database. Dbext
(or MATRIXDB) = dbext is the name of a new dbset on which to store the boundary matrices. Dbext
(Default) must be allocated on an INIT FMS statement. By default, matrices are
stored on DBALL. See Example 1 in Remark 18. Dbext is required if 3-step
external superelement data recovery will be performed.
DMIGDB= dbext Similar to MATDB (or MATRIXDB) except that the boundary matrices are
stored as DMIG Bulk Data entries on the database.Dbext is the name of a
new dbset on which to store the boundary matrices. Dbext must be allocated
on an INIT FMS statement. By default, matrices are stored on DBALL. See
Example 1 in Remark 18. Dbext is required if 3-step external superelement
data recovery will be performed.
DMIGOP2 = unitop2 Store the boundary matrices as DMIG Bulk Data entries on an .op2 file
whose Fortran unit number is given by unitop2 (Integer > 0). See Remark 16.
See also Example 2 in Remark 18.
DMIGPCH Store the boundary matrices as DMIG Bulk Data entries on the standard
punch file (.pch). Note that, if boundary matrices include both structural
and fluid grids, use DMIGOP2 instead. See Remarks 3. and 7. - 15. See also
Example 3 in Remark 18.
MATOP4 = unitop4 unitop4 is a non-zero integer with the following meanings:
(or MATRIXOP4 =
unitop4) unitop4 > 0
Store the boundary matrices in sparse format on an .op4 file whose Fortran
unit number is given by unitop4
unitop4 < 0
Store the boundary matrices in non-sparse format on an .op4 file whose
Fortran unit number is given by |unitop4|
See Remarks 3., 7., 8., 15., and 16. See also Example 4 in Remark 18.
Main Index
350 MSC Nastran Quick Reference Guide
External Superelement Creation Specification
Describer Meaning
HDF5 Output the required reduced matrices, loads, displacement OTM of the
current run to support the generation of the smart superelement (SSE) to the
file jobname.odys.h5
ASET/QSET Specifies how the external superelement’s q-set dofs (dynamic degrees-of-
freedom) are defined on the exported file. By default, all q-set dofs are
written to QSET/QSET1 entries which means the superelement’s modes
will be “added” to but not synthesized into the assembly’s modes. By
specifying ASET, the q-set dofs are written to ASET/ASET1 entries and will
be synthesized into the assembly’s. The ASET/QSET switch does not affect
DMIGPCH media option which always writes ASET/ASET1 entries.
Remarks:
1. If none of the describers STIFFNESS through FSCOUP is specified, then all matrices are stored.
2. STIFFNESS and DAMPING may be abbreviated to STIF and DAMP, respectively.
3. EXTID with an seid value must be specified if one or more of ASMBULK, EXTBULK, DMIGPCH,
or MATOP4 are specified.
If the DMIGSFIX = EXTID form is employed along with the DMIGPCH specification, the value
seid may not exceed 999999 since this value becomes part of the names given to the DMIG matrices
generated on the standard punch file (.pch). See Remark 13., and Example 3 in Remark 18.
If PARAM,AUTOQSET,YES is specified to used generate the Q-set degrees of freedom (DOFs)
(generalized coordinates), the value seid may not exceed 999 since this value becomes part of the
automatically generated IDs of the SPOINTs representing the Q-set DOFs. See explanation in Item
c under Remark 17.
4. If ASMBULK is specified, the following Bulk Data entries are generated and stored on the assembly
punch file (.asm):
SEBULK seid … (specifies MANUAL as the method for searching
boundary points)
SECONCT seid …(defines connections for boundary grid and scalar
points)
GRID entries for boundary and access grid points
SPOINT entries for boundary and access scalar points
CORD2x entries associated with the boundary and access GRID
entries
5. If ASMBULK = MANQ is specified, the following Bulk Data entries are generated and stored on the
assembly punch file (.asm):
SEBULK seid ... (specifies MANUAL as the method for searching
boundary points)
SECONCT seid ... (defines connections for boundary grid and
scalar points as well as for Q-set points)
GRID entries for boundary and access grid points
Main Index
CHAPTER 5 351
External Superelement Creation Specification
SPOINT entries for boundary and access scalar points as well as
for Q-set points
CORD2x entries associated with the boundary and access GRID
entries
6. If ASMBULK = AUTO is specified, the following Bulk Data entries are generated and stored on the
assembly punch file (.asm):
SEBULK seid … (specifies AUTO as the method for searching
boundary points)
SECONCT seid … (defines connections for boundary scalar
points)
GRID entries for access grid points
CORD2x entries associated with the access grid points
SPOINT entries for boundary and access scalar points
7. If DMIGPCH or MATOP4 is specified, then EXTBULK need not be specified. Also, the model
cannot have rotors (ROTOR, ROTORG, ROTORSE, and ROTORAX Bulk Data entries).
8. If DMIGPCH is not specified, but EXTBULK or MATOP4 is specified, the following Bulk Data
entries are generated and stored on the standard punch file (.pch):
BEGIN BULK seid
GRID entries for boundary points
GRID entries for interior points referenced by PLOTEL entries
SPOINT entries for boundary scalar points as well as for Q-set
points
CORD2x entries associated with the above GRID entries
EXTRN
ASET
QSET/QSET1
PLOTEL
9. If DMIGPCH is specified, the following Bulk Data entries are generated and stored on the standard
punch file (.pch):
BEGIN SUPER seid
GRID entries for boundary points
SPOINT entries for boundary scalar points as well as for Q-set
points
CORD2x entries associated with the boundary GRID entries
ASET/ASET1
PLOTEL entries referencing the boundary GRID entries
DMIG entries for the requested boundary matrices
10. The DMIGSFIX keyword is ignored if DMIGPCH is not specified.
11. If DMIGPCH is specified without the DMIGSFIX keyword, then the boundary DMIG matrices
generated and stored on the standard punch file (.pch) will have names 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)
AAX (boundary fluid-structure coupling matrix)
Main Index
352 MSC Nastran Quick Reference Guide
External Superelement Creation Specification
See Example 3 in Remark 18.
12. If the DMIGSFIX = cccccc form is employed along with the DMIGPCH specification, then the
boundary DMIG matrices generated and stored on the standard punch file (.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)
Acccccc (boundary fluid-structure coupling matrix)
See Example 3 in Remark 18.
13. If the DMIGSFIX = EXTID form is employed along with the DMIGPCH specification, then the
boundary DMIG matrices generated and stored on the standard punch file (.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)
Aseid (boundary fluid-structure coupling matrix)
where seid is the superelement ID specified by the EXTID keyword.
See Example 3 in Remark 18.
14. If the DMIGPCH option is specified, the boundary DMIG matrices generated and stored on the
standard punch file (.pch) may not be as accurate as the boundary matrices resulting from the other
options (MATDB/MATRIXDB, or DMIGOP2 ,or MATOP4). Accordingly, this may result in
decreased accuracy from the subsequent assembly job using these DMIG matrices.
15. The punch output resulting from EXTSEOUT usage is determined by ASMBULK, EXTBULK,
DMIGPCH, and MATOP4 as follows:
No ASMBULK, EXTBULK, DMIGPCH or MATOP4
No punch output.
ASMBULK, but no EXTBULK, or DMIGPCH, or MATOP4
Punch output is generated and stored on the assembly punch file (.asm) as indicated in Remarks 4.
through 6.
No ASMBULK, but EXTBULK, DMIGPCH, or MATOP4
Punch output is generated and stored on the standard punch file (.pch) as indicated in Remarks 8. or
9. (as appropriate).
ASMBULK and EXTBULK, DMIGPCH or MATOP4
Punch output consists of two distinct and separate parts. One part is generated and stored on the
assembly punch file (.asm) as indicated in Remarks 4. through 6. The other part is generated and
stored on the standard punch file (.pch) as indicated in Remarks 8. or 9. (as appropriate).
Main Index
CHAPTER 5 353
External Superelement Creation Specification
16. If DMIGOP2 = unitop2 or MATOP4 = unitop4 is specified, an appropriate ASSIGN OUTPUT2 or
ASSIGN OUTPUT4 statement must be present in the File Management Section (FMS) for the
specified Fortran unit numbers. See Examples 2 and 4 in Remark 18.
If one has an input file of extse10.dat and assigns an output2 file with following assign statement
for an external superelement creation job to save the reduced boundary matrices and OTM matrices,
ASSIGN OUTPUT2='extse10.op2' UNIT=25 DELETE
...
$ Case Control Command
EXTSEOUT(ASMBULK EXTID=10 DMIGOP2=25)
...
Nastran will issue the following fatal error message:
*** USER FATAL MESSAGE 732 (OPFUNT)
LOGICAL NAMES 'OP2 ' AND 'OUTPUT2 ' ARE ASSIGNED TO THE SAME
PHYSICAL FILE.
USER INFORMATION: PHYSICAL FILE NAME 1: ./extse10.op2
PHYSICAL FILE NAME 2: extse10.op2
USER ACTION: CHANGE FILE NAME ON ONE OF THE ASSOCIATED ASSIGN
STATEMENTS.
This error occurs since it uses the default physical op2 file of extse10.op2 that Nastran is supposed to
use and save op2 results. This error can be simply avoided by using a different op2 file name to save
the reduced boundary matrices and OTM matrices as follows:
ASSIGN OUTPUT2='extse10_rbm.op2' UNIT=25 DELETE
17. The creation of an external superelement using EXTSEOUT involves running a Nastran job, with
the following additional data:
a. The data for the creation of the external superelement is specified by the EXTSEOUT Case
Control command. It is best to specify this command above the subcase level. However, if the
Nastran job itself involves superelements, then the EXTSEOUT command may also be specified
within the subcase that is applicable to the residual.
b. The boundary points of the external superelement are specified by ASET/ASET1 Bulk Data
entries.
c. If the external superelement creation involves component mode reduction, then Q-set degrees of
freedom (DOFs) (generalized coordinates) must be defined. This can be done either by
automatically defining them via PARAM,AUTOQSET,YES or by explicitly specifying them via
QSET/QSET1 Bulk Data entries. Note that for the latter case of explicit definition, only
SPOINTs may be specified as Q-set points; no grid points may be specified. If this requirement
is not met, the program terminates the execution with an appropriate fatal message.
Main Index
354 MSC Nastran Quick Reference Guide
External Superelement Creation Specification
If PARAM,AUTOQSET,YES is specified, SPOINTs are automatically generated internally to
represent the Q-set DOFs. The IDs of these SPOINTs are of the form 9sssnnnn where sss is the
superelement ID seid specified by the EXTID keyword, and nnnn is a mode number. Both sss and
nnnn will have leading zeros inserted in them to ensure that sss is a three-digit number and nnnn
is a four-digit number. Thus, for example, the Q-set DOF corresponding to the 8th mode of
superelement ID 5 would be represented by an SPOINT with an automatically generated ID of
90050008, while the Q-set DOF corresponding to the 50th mode of superelement ID 25 would
be represented by an SPOINT with an automatically generated ID of 90250050.
Because of the preceding numbering scheme, the superelement ID seid specified by the EXTID
keyword must necessarily not exceed 999 when PARAM,AUTOQSET,YES is specified. The
program terminates the job with a User Fatal Message if this condition is not met.
Further, because of the preceding numbering scheme, the user should ensure that, when
PARAM,AUTOQSET,YES is specified, the IDs of the grid and scalar points of the external
superelement do not conflict with the automatically generated SPOINT IDs of the Q-set DOFs.
The program terminates the job with a User Fatal Message if this condition is not met.
d. The fixity of the boundary DOFs for the component mode reduction may be specified using the
BSETi/BNDFIXi and CSETi/BNDFREE/BNDFRE1 Bulk Data entries. (The default scenario
assumes that all boundary DOFs are fixed for component mode reduction.)
e. The output for the external superelement is generated in the assembly job. This output consists
of displacements, velocities, accelerations, SPC forces, MPC forces and element stresses, strains
and forces. However, in order for this output to be generated in the assembly job, the output
requests must be specified in the external superelement creation run. Normally, the only output
requests for the external superelement that are honored in the assembly job are those that are
specified in the creation run. There is, however, one important exception to this: the output for
the boundary and access grid and scalar points, as well as for all grid points associated with
PLOTEL entries, can be obtained in the assembly job even if there is no output request specified for
these points in the creation run.
If the creation run contains the load requests TEMPERATURE (LOAD) or DEFORM, then
element stresses and element forces will not be available in the assembly run.
f. If the assembly job involves the use of PARAM Bulk Data entries, then the following points
should be noted:
• PARAM entries specified in the main bulk data portion of the input data apply only to the residual
and not to the external superelements.
• PARAM entries specified in the BEGIN SUPER portion of the Bulk Data for an external
superelement apply only to that superelement.
• The most convenient way of ensuring that PARAM entries apply not only to the residual, but also
to all external superelements, is to specify such PARAM entries in the Case Control Section, not
in the main bulk data. This is particularly relevant for PARAMs such as POST.
g. If EXTSEOUT is used in SOL 400 for a multidisciplinary or linear perturbation analysis and
there are rigid elements present then RIGID=LINEAR must be specified.
Main Index
CHAPTER 5 355
External Superelement Creation Specification
18. The following examples illustrate details of job setups for the external superelement creation and the
subsequent assembly process for various scenarios. These examples assume that there are three
external superelement creation jobs, one each for external SE 10 (extse10.dat), SE 20 (extse20.dat)
and SE 30 (extse30.dat), followed by an assembly job.
Example 1. MATDB / MATRIXDB or DMIGDB Option
External SE Creation Jobs
• File Management Section FMS Requirement only if 3rd step external superelement
data recovery is desired
SE 10: INIT EXTDB
SE 20: INIT EXTDB
SE 30: INIT EXTDB
These INIT statements along with the DBEXT keyword below will create separate
DBsets called “extse10.EXDTB”, “extse20.EXTDB”, and “extse30.EXTDB” and store
the necessary data for the Assembly Job on them. All other data will be stored on
DBALL.
• Case Control Requirement for the MATDB / MATRIXDB option if 3rd step external
superelement data recovery is not desired.
SE 10: EXTSEOUT (ASMBULK EXTID = 10)
SE 20: EXTSEOUT (ASMBULK EXTID = 20)
SE 30: EXTSEOUT (ASMBULK EXTID = 30)
The EXTBULK keyword may be specified, but it is not necessary.
• Case Control Requirement for the DMIGDB option if 3rd step external superelement
data recovery is not desired.
SE 10: EXTSEOUT (ASMBULK EXTID = 10 DMIGDB)
SE 20: EXTSEOUT (ASMBULK EXTID = 20 DMIGDB)
SE 30: EXTSEOUT (ASMBULK EXTID = 30 DMIGDB)
For both options, scr = no should be specified on the Nastran job command line to ensure
that the databases are saved at the end of the jobs.
• Case Control Requirement for the MATDB / MATRIXDB option if 3rd step external
superelement data recovery is desired.
SE 10: EXTSEOUT (ASMBULK EXTID = 10 MATDB=SE10)
SE 20: EXTSEOUT (ASMBULK EXTID = 10 MATDB=SE20)
SE 30: EXTSEOUT (ASMBULK EXTID = 10 MATDB=SE30)
• Case Control Requirement for the DMIGDB option if 3rd step external superelement
data recovery is desired.
SE 10: EXTSEOUT (ASMBULK EXTID = 10 DMIGDB=SE10)
Main Index
356 MSC Nastran Quick Reference Guide
External Superelement Creation Specification
Example 1. MATDB / MATRIXDB or DMIGDB Option (continued)
SE 20: EXTSEOUT (ASMBULK EXTID = 10 DMIGDB=SE20)
SE 30: EXTSEOUT (ASMBULK EXTID = 10 DMIGDB=SE30)
Assembly Job
• File Management Section (FMS) Requirement
(Note: If DBEXT was specified on the EXTSEOUT command in the External SE Creation Jobs
then the extse10.DBALL, etc. files may be hidden (moved or renamed) from the Assembly Job for
purposes of security or privacy.)
ASSIGN dbname10=’extse10.MASTER’
ASSIGN dbname20=’extse20.MASTER’
ASSIGN dbname30=’extse30.MASTER’
DBLOCATE DATABLK=(EXTDB, EXTROTDB) CONVERT(SEID=10)
LOGICAL=dbname10
DBLOCATE DATABLK=(EXTDB,EXTROTDB) CONVERT(SEID=20)
LOGICAL=dbname20
DBLOCATE DATABLK=(EXTDB, EXTROTDB) CONVERT(SEID=30)
LOGICAL=dbname30
(Note: All of the data blocks stored on the databases for the external SEs have the same
common name of EXTDB or EXTROTDB for external SEs with rotors.)
• Case Control Requirement
If 3rd step data recovery is desired for the external superelement, specify EXTDROUT
Case Control command in a separate subcase for each superelement. See also the examples
under Remark 10 of the EXTDRIN Case Control command for additional File
Management and Case Control requirements for the Assembly Job.
• Bulk Data Requirement
The following INCLUDEs are required. They may be specified anywhere in the Main
Bulk Data.
INCLUDE ‘extse10.asm’
INCLUDE ‘extse20.asm’
INCLUDE ‘extse30.asm’
Main Index
CHAPTER 5 357
External Superelement Creation Specification
Example 2. DMIGOP2 Option
External SE Creation Jobs
• File Management Section (FMS) Requirement
ASSIGN OUTPUT2=’extse10_op2’ UNIT=25 DELETE
ASSIGN OUTPUT2=’extse20_op2’ UNIT=26 DELETE
ASSIGN OUTPUT2=’extse30_op2’ UNIT=27 DELETE
• Case Control Requirement
SE 10: EXTSEOUT (ASMBULK EXTID = 10 DMIGOP2 = 25)
SE 20: EXTSEOUT (ASMBULK EXTID = 20 DMIGOP2 = 26)
SE 30: EXTSEOUT (ASMBULK EXTID = 30 DMIGOP2 = 27)
The EXTBULK keyword may be specified, but it is not necessary.
scr = yes may be specified on the Nastran command line unless a 3rd step external
superelement data recovery restart is desired.
Assembly Job
• File Management Section (FMS) Requirement
ASSIGN INPUTT2=’extse10_op2’ UNIT=25
ASSIGN INPUTT2=’extse20_op2’ UNIT=26
ASSIGN INPUTT2=’extse30_op2’ UNIT=27
• Case Control Requirement
If 3rd step data recovery is desired for the external superelement, specify EXTDROUT
Case Control command in a separate subcase for each superelement. See also the examples
under Remark 10 of the EXTDRIN Case Control command for additional File
Management and Case Control requirements for the Assembly Job.
• Bulk Data Requirement
The following INCLUDEs are required. They may be specified anywhere in the main
bulk data.
INCLUDE ‘extse10.asm’
INCLUDE ‘extse20.asm’
INCLUDE ‘extse30.asm’
Example 3. DMIGPCH Option
External SE Creation Jobs
• Case Control Requirement
SE 10: EXTSEOUT (ASMBULK EXTID = 10 DMIGPCH)
SE 20: EXTSEOUT (ASMBULK EXTID = 20 DMIGPCH,
Main Index
358 MSC Nastran Quick Reference Guide
External Superelement Creation Specification
Example 3. DMIGPCH Option (continued)
DMIGSFIX = XSE20)
SE 30: EXTSEOUT (ASMBULK EXTID = 30 DMIGPCH,
DMIGSFIX = EXTID)
scr = yes may be specified on the Nastran command line since there is no need for the
databases to be saved at the end of the jobs.
Assembly Job
• Case Control Requirement
K2GG = (KAAX, KXSE20, K30)
M2GG = (MAAX, MXSE20, M30)
B2GG = (BAAX, BXSE20, B30)
K42GG = (K4AAX, K4XSE20, K430)
P2G = (PAX, PXSE20, P30)
A2GG = (AAX, AXSE20, A30)
• Case Control Requirement
If 3rd step data recovery is desired for the external superelement, specify EXTDROUT
Case Control command along with the commands above in a separate subcase for each
superelement See also the examples under Remark 10 of the EXTDRIN Case Control
command for additional File Management and Case Control requirements for the
Assembly Job.
• Bulk Data Requirement
The following INCLUDEs are required. They may be specified anywhere in the main
bulk data.
INCLUDE ‘extse10.asm’
INCLUDE ‘extse20.asm’
INCLUDE ‘extse30.asm’
The following INCLUDEs are also required. They must be grouped together and
specified at the very end of the main bulk data (just before the ENDDATA delimiter).
INCLUDE ‘extse10.pch’
INCLUDE ‘extse20.pch’
INCLUDE ‘extse30.pch’
Main Index
CHAPTER 5 359
External Superelement Creation Specification
Example 4. MATOP4 Option
External SE Creation Jobs
• File Management Section (FMS) Requirement
ASSIGN OUTPUT4=’extse10_op4’ UNIT=25 DELETE
ASSIGN OUTPUT4=’extse20_op4’ UNIT=26 DELETE
ASSIGN OUTPUT4=’extse30_op4’ UNIT=27 DELETE
• Case Control Requirement
SE 10: EXTSEOUT (ASMBULK EXTID = 10 MATOP4 = 25)
SE 20: EXTSEOUT (ASMBULK EXTID = 20 MATOP4 = 26)
SE 30: EXTSEOUT (ASMBULK EXTID = 30 MATOP4 = -27)
Note: Boundary matrices will be stored in sparse format on .op4 files with Fortran unit
numbers 25 and 26 and in non-sparse format on the .op4 file with Fortran unit number
27.
scr = yes may be specified on the Nastran command line unless a 3rd step external
superelement data recovery restart is desired.
Assembly Job
• File Management Section (FMS) Requirement
ASSIGN INPUTT4=’extse10_op4’ UNIT=25
ASSIGN INPUTT4=’extse20_op4’ UNIT=26
ASSIGN INPUTT4=’extse30_op4’ UNIT=27
• Case Control Requirement
If 3rd step data recovery is desired for the external superelement, specify EXTDROUT
Case Control command in a separate subcase for each superelement. See also the examples
under Remark 10 of the EXTDRIN Case Control command for additional File
Management and Case Control requirements for the Assembly Job.
• Bulk Data Requirement
The following INCLUDEs are required. They may be specified anywhere in the main
bulk data.
INCLUDE ‘extse10.asm’
INCLUDE ‘extse20.asm’
INCLUDE ‘extse30.asm’
The following INCLUDEs are also required. They must be grouped together and
specified at the very end of the main bulk data (just before the ENDDATA delimiter).
INCLUDE ‘extse10.pch’
INCLUDE ‘extse20.pch’
INCLUDE ‘extse30.pch’
Main Index
360 MSC Nastran Quick Reference Guide
External Superelement Creation Specification
19. If EXTBULK, MATOP4, DMIGOP2, or DMIGPCH is specified, then METADATA entries will
be copied to the .pch file.
20. Data recovery for the external superelement is possible via two methods: two-step and three-step.
a. In the two-step method, EXTSEOUT automatically generates output transformation matrices
(OTMs) based on STRESS, FORCE, DISPLACEMENT, SPCFORCE, MPCFORCE,
STRAIN, and MONITOR Case Control commands specified in the first (creation) run. Then in
the second (assembly) run, data recovery is performed on the external superelement. This data
recovery is limited to certain element types and specialized outputs. For example, grid point forces
and stresses, corner stresses, strain and kinetic energies, and composite stresses are not supported
in the OTMs. If Modules are present in the first run, then OTMs are generated for those grid
points and elements in Module 0 only.
b. The three-step method requires a restart of the first run to perform data recovery on the external
superelement. This method supports all data recovery options in the two-step method as well as
grid point forces and stresses, corner stresses, strain and kinetic energies, and composite stresses.
The method is explained in the description of the EXTDRIN Case Control command. If
Modules are present in the first run, this method allows for data recovery in any Module.
c. Both methods are described in more detail in the MSC Nastran Superelements amd Modules User's
Guide.
d. For dynamically reduced external superelements, the displacement OTMs created with dynamic
reduction include both the dynamic effects of the o-set and also the fixed boundary effects of the
o-set due to interior loads. With the two-step method, only one of these effects should be included
in a SOL 101, 106 and 400 (with ANALYSIS=STATICS) assembly. Therefore, if there are
interior loads in the external superelement and the two-step method is being used, attaching the
dynamically reduced external superelements in a static analysis of the assembly is not
recommended.
21. Superelement can be used in conjunction with residual structures in fluid-structure interaction
analysis / acoustic analysis, with the following restrictions:
a. If the superelement contains both structural and fluid degrees-of-freedom (dof), then the residual
structure can only have either structural dof or fluid dof - it cannot have both.
b. Similarly, if the residual structure has both structural and fluid dof, then the superelement should
only have either structural dof or fluid dof - it cannot have both.
22. If the LDLABEL Case Control command is present, the program will automatically create an internal
METADATA table with the LDLABEL and SUBCASE information which may be written to the
.pch file. For example, the following Case Control commands:
SUBCASE 10
LDLABEL=Z FORCE ON 825
LOAD=1000
SUBCASE 20
LDLABEL=Z FORCE ON 836
LOAD=2000
SUBCASE 30
LDLABEL=Z FORCE ON 812
LOAD=3000
Main Index
CHAPTER 5 361
External Superelement Creation Specification
will produce the following METADATA entry in the .pch file if the EXTBULK, DMIGOP2,
DMIGPCH, or MATOP4 are used.
METADATAXSLDLBL:100
10 1000
Z FORCE ON 825
20 2000
Z FORCE ON 836
30 3000
Z FORCE ON 812
Also, if DMIGDB, MATDB, or DMIGOP2 are specified, the same information will be written to
an internal table called XSLDLBL on the database or op2 file.
Main Index
362 MSC Nastran Quick Reference Guide
Fatigue Output Request
FATIGUE (Case) Fatigue Output Request
Requests one or more fatigue analyses for use in pseudo-static (SOL 101), modal (SOL 103), modal transient
(SOL 112), and frequency response (SOL 108 and SOL 111) runs.
Format (SOL 101, 103, 112, 200 with ANALYSIS=STATICS):
FATIGUE ( SORT1 PRINT, PUNCH FORMAT = CODE BULK
SORT2 PLOT SET
STATICS STROUT = CODE ) = n
Format (SOL 108, 111, 200 with ANALYSIS=DFREQ or MFREQ) (See Remark 12.):
FREQ
FATIGUE ( SORT1 PRINT, PUNCH FORMAT = CODE BULK DFREQ ) = n
SORT2 PLOT
MFREQ
Examples:
FATIGUE=100
SET 99 = 100, 200
FATIGUE(SET)=99
Describer Meaning
SORT1 Printed output will be presented as a tabular listing of elements for each fatigue
analysis or event. In the case of duty cycle, where multiple events are output
(EVNTOUT=1 on FTGSEQ bulk data), each event is presented as a separate fatigue
analysis. Output written to the OEFTG data blocks is always in SORT1 format.
SORT2 Printed output will be presented as a tabular listing of events for each element, node,
or angle. This is only applicable for duty cycle (loading sequences with more than one
event - EVNTOUT=1 on FTGSEQ bulk data). If there is only one event, the output
is identical to SORT1. Output written to the OEFTG data blocks is always in SORT1
format.
Main Index
CHAPTER 5 363
Fatigue Output Request
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
See Remark 15. regarding data blocks produced by the FATIGUE case control.
FORMAT Request that fatigue be output in specific file formats. See Remark 6. and 11.
STROUT Request that certain stress or strain output be included. See Remarks 13. and 14.
CODE Codes for specific file format or stress output. See Remark 6., 11., and 13.
BULK Specifies that the n refers directly to bulk data IDs of FTGSEQ/ FTGLOAD,
FTGPARM and FTGDEF entries of the same ID (default) to process.
SET Specifies that the n refers to a previously appearing SET ID (SOL 101, 103, & 112
only) containing the IDs of FTGSEQ/FTGLOAD, FTGPARM, FTGDEF bulk data
entries to process. This is a mechanism to request multiple fatigue output requests in
a single analysis run.
STATICS SOL 200 only. Specifies the FATIGUE case control is for ANALYSIS=STATICS
subcases in a SOL 200 optimization run. This is the default if not specified. See
Remark 9.
FREQ SOL 200 only. Either of these specifies the FATIGUE case control is for frequency
DFREQ response (ANALYSIS=MFREQ or DFREQ) subcases in a SOL 200 optimization run.
MFREQ This is not the default and must be specified if the FATIGUE case control is referenced
on a DRESP1 of type FRFTG. See Remark 9.
n ID of FTGSEQ/FTGLOAD, FTGPARM, FTGDEF bulk data entries of the same ID
(BULK option) to process, or
ID of a previously occurring SET case control entry (SET option) containing the IDs
of the FTGSEQ/FTGLOAD, FTGPARM, FTGDEF bulk data entries to process
(SOL 101, 103, & 112 only).
Main Index
364 MSC Nastran Quick Reference Guide
Fatigue Output Request
Remarks:
1. A single FATIGUE case control is required to perform one (SOL 108/111) or more (SOL
101/103/112) fatigue analyses and must be present above the SUBCASE level. If not present, no
fatigue analysis will occur regardless of the presence of other bulk data related to fatigue analysis.
2. It is not necessary to include any case control STRESS and/or STRAIN output requests in order for
the FATIGUE output request to obtain the necessary stresses or strains for the fatigue calculation.
3. For a single fatigue analysis, BULK=n points to a FTGDEF, a FTGPARM, and a FTGSEQ (or
FTGLOAD) entry, each with ID=n.
4. For multiple fatigue analyses, SET=n points to a previously appearing SET case control and each
member of the SET is the ID of a FTGDEF, a FTGPARM, and a FTGSEQ (or FTGLOAD) bulk
data entry with that ID (SOL 101, 103, or 112 only).
5. A fatigue analysis must have, at a minimum, loading and material data defined on either FTGSEQ
or FTGLOAD and MATFTG bulk data entries, respectively, for a fatigue analysis to be valid.
FTGPARM and FTGDEF entries can be absent, in which case, defaults will be used.
6. The following additional, optional, fatigue output file formats may be requested. The given codes
must be summed if multiple files are requested. Example: CSV file and FEF file CODE would be
64+128=192. Note the following:
• For multi-layered results, such as shells that compute top and bottom results, a separate file for
each is generated for FEF formats with _top (or _t) or _bottom (or _b) designations in the
name. For FEF file output, if only a single file with worst case layer results is desired, add 256 or
10,000 to the CODE. In this case no additional designation is put in the file name or _w is used.
Using the above example would give 448 or 10192. Either mechanism works. Other designations
that can appear in the filenames are _N or_E for element nodal or element center, respectively,
and _EVi for event i, or _EVS for event summary only.
• Note that CSV file output only ever creates a single file as both layers are reported in the single file.
• Some output is not available for duty cycle jobs if EVNTOUT>0 on the FTGSEQ bulk data
entry. Check messages if the f06 and log files if the requested output files are not being
generated.
CODE for SOLs CODE for SOLs
File Format 101/103/112 108/111
No additional output 0 0
CSV File (Comma Separated - Excel File)* 64 64
FEF (Patran Results File)† 128 128
* For random vibration fatigue using SOLs 108 or 111, the CSV file output request is also
dependent on the LOGLVL field setting on the FTGPARM entry. By default a
<jid>PSD.csv file is always generated, which at a minimum contains the input PSD,
stress transfer function (TF) and result PSD for the critical entity.
Main Index
CHAPTER 5 365
Fatigue Output Request
†SOL 101, 103, 112 produce FEF files of type ‘PATRAN 2 els’ or ‘PATRAN 2 nod’ with
.fef extension; SOL 108, 111 produce FEF files of type ‘PATRAN 2 els’ with .els_fef
extension. Also see Remark 11.
7. RESTARTs are possible with FATIGUE output request as long as the stress/strain state of the entities
requested does not change. Most parameters on the FTGPARM (LOC excluded as it requires a
different set of stresses/strains) can be changed on a RESTART. Different loading (FTGSEQ) and
materials (MATFTG) can also be investigated using the RESTART capability (SOLs 101, 103, &
112 only).
8. Standard fatigue output is:
Stress-Life (SN) Analysis Strain-Life (eN) Analysis
LIFE (Repeats*) LIFE (Repeats)
LOG of LIFE (Repeats) LOG of LIFE (Repeats)
LIFE (user units)† LIFE (user units)
LOG of LIFE (user units) LOG of LIFE (user units)
DAMAGE DAMAGE
LOG of DAMAGE LOG of DAMAGE
MAX STRESS‡ MAX STRESS or STRAIN **
MIN STRESS MIN STRESS or STRAIN
*Or Seconds for SOL 108 and SOL 111
†User units are fatigue equivalent units as defined on the FTGSEQ or FTGLOAD entry and
other output is available depending on the settings of the FTGPARM entry. Please see those
entries for more detail.
‡For SOLs 108 and 111 Maximum Stress = Mean Stress + MAXPEAK*RMS Stress, Mini-
mum Stress = Mean Stress - MAXPEAK*RMS Stress. MAXPEAK is defined on FTGPARM
entry and is defaulted to 3.0.
**Depends on FTGPARM line used: STRESS or STRAIN.
9. STATICS, FREQ, DFREQ, MFREQ options are utilized in SOL 200 only. Fatigue and design
sensitivity analysis will be performed for the designated analysis type only. If STATICS is specified
(default), FATIGUE case control must be associated with subcases containing ANALYSIS=STATIC
for a pseudo-static fatigue analysis and the fatigue DRESP1 responses/constraints specified must be
of RTYPE=FATIGUE. If one of FREQ, DFREQ, MFREQ is specified, FATIGUE case control must
be associated with subcases containing ANALYSIS=MFREQ or DFREQ for random vibration
fatigue analysis and the fatigue DRESP1 response/constraints specified must be of RTYPE=FRFTG.
10. For SOL 108/111 with FATIGUE analysis, PARAM,SPARSEDR,no and PARAM,DDRMM,-1
both must be present. Otherwise, FATIGUE analysis will be skipped. Or, PARAM,SPARSEDR,yes,
which is default, can be used instead.
Main Index
366 MSC Nastran Quick Reference Guide
Fatigue Output Request
11. The FEF file output request produces PATRAN 2 style elemental or nodal ASCII results files that
can be imported directly into Patran for post processing. In order to import these files into Patran a
template file is also required in order to tell Patran how to map the columns of data in the files to
proper, meaningful labels. The analysis job produces both the FEF file and the corresponding
template files. The template file has the extension .tml or .res_tmpl with the same base name as
the FEF file. Jobs run with LOC=ELEM or NODE on the FTGPARM entry create elemental based
FEF files or all SOL sequences. Jobs run with LOC=NODA produce nodal based FEF files for SOLs
101, 103, and 112 and produce elemental based FEF files for SOLs 108 and 111. In Patran these
files are imported under the File|Import menu with the Object set to Results and the Format set to
either PATRAN 2 els... or PATRAN 2 nod... for elemental or nodal based FEF results files,
respectively. The Element Node Results switch must be set to Connectivity Based for proper import
of elemental based results.
You must use the job produced template files to import the FEF files. However, if you routinely
postprocess in Patran you may wish to copy the appropriate template file to the standard template file
location provided with the Patran installation. The advantage of putting it where the standard
template files reside is that you may select it directly from the list without navigating the file browser
to the location of the job produced template files. The disadvantage is that if you use customized
fatigue equivalent units, the labels may change and not match.
12. When a FATIGUE case control is present to perform random vibration fatigue analysis using SOLs
108 and 111, only one FREQUENCY case control set is allowed for all transfer function SUBCASEs
and should be above the SUBCASE level or only present in 1st SUBCASE. The FREQUENCY set
cannot change from SUBCASE to SUBCASE or a fatal error is issued.
13. SOL 101, 103, or 112 only: The following additional, optional, stress or stain output may be
requested. The given codes must be summed if multiple requests are required. Example: CODE
would be 1+2=3 for fatigue stress and maximum stress range vector results. The presence of this
output request overrides the STROUT entry on the FTGPARM entry. If PLOT is specified in the
FATIGUE case control, no output is printed and only available in the OUTPUT2 or HDF5 files.
Main Index
CHAPTER 5 367
Fatigue Output Request
Additional Stress/Strain Output CODE
No additional output 0
Fatigue Stress/Strain - these are the physical (or modal) stress/strain tensors passed 1
to the fatigue analysis for each requested entity of the fatigue analysis for each
SUBCASE (or mode). Valid for SOL 101, 103, and 112 only.
Maximum Stress/Strain Range Magnitude or Vector- this is the stress/strain 2
maximum range magnitude (for all scalar COMB values of the FTGPARM entry)
or vector (for 2D critical plane* analysis, COMB=CRITICAL) for all requested
entities at the critical angle for SOLs 101, 103, and 112 only, as returned from the
fatigue analysis. When LOC=ELEM or NODE on the FTGPARM entry, the
computed vector is in the basic coordinate system. For LOC=NODA, the
computed vector is in the SURFACE system as defined by OUTPUT field on the
NAVG line of the FTGPARM entry. For scalar COMB values, a vector is not
computed and only the x-component of the vector is provided. The other two
components are always zero in this case.
Stress/Strain Scalar Response Time History - this is the computed scalar response 4
time history in model consistent units (for all COMBs on the FTGPARM entry) at
all time points as returned from the fatigue analysis for SOLs 101, 103, and 112
only. This is the actual response from which rainflow ranges and damage are
computed. While individual events are processed, the ALL event is not processed
when METHOD=0 on FTGPARM. Also LAYER=1 or 2 on the FTGPARM entry
is honored for STROUT=4, but LAYER=0 prints values for both top and bottom.
To limit output and ensure decent performance maxENTS on the FTGDEF entry
is defaulted to 100 and if the number of entities exceeds this, the job stops. Setting
maxENTS to a high number is not recommended due to performance issues.
Stress/Strain Tensor Time History - this is the computed tensor time history 8
response at all time points for all requested entities used by the fatigue analysis for
SOL 112 only.
* COMB = CRITICAL on the FTGPARM entry.
14. STROUT is not honored in manual restarts using SOL FTGRSTRT (automatic restarts are OK).
STROUT=4 may use additional memory space on your system. For STROUT=4, it is also highly
recommended to limit the number of requested entities on the FTGDEF bulk data entry. If the job
stops because too many entities are requested, you can set maxENTS on the FTGDEF entry.
STROUT=4 has the potential to produce enormous amounts of response data and external files,
which can severely affect performance and disk space. STROUT=4 produces temporary CSV
response files of each entity. These CSV files are deleted after the job completes unless scr=no is used
when submitting the job. When METHOD=0 on the FTGSEQ entry, STROUT=4 only produces
responses for each event.
Main Index
368 MSC Nastran Quick Reference Guide
Fatigue Output Request
15. Output Data Blocks: The following table indicates the output data blocks produced by the
FATIGUE case control and which parameters trigger creation of those data blocks. See the DMAP
Programmers Guide for a description of these data blocks.
Data Block Comment
OEFTG SOL 101, 103, 112 only. This is the standard output data block for that is
produced simply by the presence of a FATIGUE case control containing
fatigue life/damage and related data for time-based fatigue analysis. Data
from STROUT=2 is also written to this data block.
OEFTGM SOL 101, 103, 112 only. This is the multiaxial/biaxial output data block
that is produced by the presence of a FATIGUE case control with the usage
of the MULTI key word on the FTGPARM entry for time-based fatigue
analysis
OEFTGV SOL 108, 111 only. This is the standard output data block for that is
produced simply by the presence of a FATIGUE case control containing
fatigue life/damage and related data for frequency-based fatigue analysis.
OES1FS SOL 101 only. This is a physical stress tensor data block like OES that is
created due to the presence of STROUT=1 usage in a FATIGUE case
control.
OESFTGR SOL 103, 112 only. This is a modal stress tensor data block like OES that
is created due to the presence of STROUT=1 usage in a FATIGUE case
control.
OEFTGRS SOL 101, 103, 112 only. This is the scalar stress history response data block
created due to the presence of STROUT=4 usage in a FATIGUE case
control.
OES1FS SOL 112 only. This is a tensor stress history data block like OES that is
created due to the presence of STROUT=8 usage in a FATIGUE case
control.
Main Index
CHAPTER 5 369
Free Body Load Output Request
FBODYLD (Case) Free Body Load Output Request
Selects a set of submodels for which free body loads are to be produced and stored.
Format:
ALL
FBODYLD(LID) =
name1 name2 name3
Examples:
FBODYLD=ALL
FOBDYLD(100)=WINGLD
FBODYLD(200)=WINGLD,TAILLD
Describer Meaning
LID Optional user-defined load ID. If LID is not supplied, the subcase ID is used to define
this value.
ALL Loads will be produced for all FBODYLD Bulk Data entries.
namei Name of an FBODYLD Bulk Data entry that defines the submodel to be used for the
load.
Remarks:
1. It is recommended, but not required, that the LID be unique across subcases.
2. A separate load is created for each namei.
3. The name list supplies one or more names separated by comma or blank.
4. Each load is stored individually as a one column matrix that is qualified by LID, namei, submodel
name, loadcase label, and submodel label (where submodel name is the name on the FBODYSB Bulk
Data entry, loadcase label is the label on the FBODYLD Bulk Data entry, and submodel is the label
on the FBODYSB Bulk Data entry).
Main Index
370 MSC Nastran Quick Reference Guide
Specifies model checking options
FEMCHECK (Case) Specifies model checking options
Specifies model checking options at the start of the run. Specifically checks for RBE3 elements with
unconnected independent (Gij) grids and RBE2 elements with unconnected dependent (GMi) grids. Also
validates some other case controls in Frequency and Transient analysis before start of the run. RBE2 will only
result in WARNING messages, and all other options will result in FATAL messages.
Format:
ALL
n
FEMCHECK =
RBE3, RBE2, DLOAD, FREQ, SDAMP, TSTEP
RBE3RFIX RBE3TLVL= RBE3THR=n
Examples:
FEMCHECK=ALL
FEMCHECK=RBE3, RBE2, DLOAD, FREQ, SDAMP, TSTEP
FEMCHECK = RBE3RFIX, RBE3TLVL=1.25, RBE3THR=200
Describer Meaning
NONE No checking. This is the default.
ALL Turns on all checking listed in the following.
RBE3 To make sure every independent (Gij) grid on a RBE3 bulk data entry is attached to an
element, PLOTEL, or DMIG.
RBE2 To give a WARNING message for each dependent (GMi) grid on a RBE2 bulk data
entry that is not attached to an element, PLOTEL, or DMIG.
DLOAD For frequency analysis, check if DLOAD case control is specified. For transient analysis.
check if DLOAD or IC case control is specified. Make sure DLOAD case control refers
to a valid bulk data entry, i.e. DLOAD, RLOAD1, RLOAD2, TLOAD1, TLOAD2,
ACSRCE, ACLOAD.
FREQ Check if FREQUENCY case control is specified for frequency analysis. FREQ case
control must also refer to a valid bulk data entry, i.e. FREQ, FREQ1, FREQ2, FREQ3,
FREQ4, FREQ5.
SDAMP Check if SDAMPING Case Control references a valid Bulk Data entry. It must refer to
a valid bulk data entry, i.e. TABLED1, TABLED2, TABLED3, TABLED4, TABLED5,
TABDMP1.
TSTEP For SOL 108/109/111/112, TSTEP case control must refer to a TSTEP bulk data entry.
For SOL 129/159, TSTEP case control should refer to a TSTEPNL bulk data entry.
RBE3RFIX Turns on RBE3 REFC Rotational DOF Correction. See Remark 2.
Main Index
CHAPTER 5 371
Specifies model checking options
Describer Meaning
RBE3TLVL Controls the level of trimming (Real; Default = -1.0, No trimming). See Remark 3. and 4.
Higher value makes trimming more aggressive. 2.0 > > 1.0 is the recommended start
value.
RBE3THR Controls threshold for trimming RBE3s. Specifies the minimum number of connected
grids a RBE3 needs to have to consider it for trimming
n Value of RBE3THR. RBE3s that have connected grids less that n will not be considered
for trimming (Integer > 20 or < 0; Default = 500). See Remark 5.
Remark:
1. This command should be applied above all SUBCASEs.
2. If RBE3 has its reference GRID connecting elements having rotational stiffness-such as beams and
shells-then ideally this RBE3's reference GRID should have rotational components enabled-that is,
its REFC should have 456 components turned on-so that moments applied to it can be transferred
to the underlying independent GRIDs. Specifying RBE3RFIX automatically adds 456 components
to the REFC field of RBE3 in case its reference grid is connected to elements with rotational DOFs.
3. Numerical processing of models having large number of RBE3 having lots of connected grids can take
excessive amount of time while contributing little to the quality of results (displacements, stresses,
strains, etc). Large number of RBE3 connected grids (legs) of these models generally are modeling
artifacts. Turning on the RBE3 trimming capability for these models-by using RBE3TLVL-is
essential for solving them efficiently.
4. RBE3 trimming is based on the proximity of independent grids and a higher value of RBE3TLVL,
, makes the trimming more aggressive.
a. 2.0 > > 1.0 is the recommended start value. This would remove RBE3 legs 1.0 to 2.0 element
length away from retained grid.
b. > 0.5 removes RBE3 legs that are midside grids of quadratic elements
5. RBE3THR value n should be greater than 20. If the model has a RBE3 with more than 2000
connected grids MSC Nastran will issue a warning to the user if the RBE3 trimming is not turned
on. If the model has a RBE3 with more than 100,000 connected grids MSC Nastran will issue a fatal
message if the RBE3 trimming is not turned on. The user can override this behavior (not
recommended) by choosing n < 0.
Main Index
372 MSC Nastran Quick Reference Guide
Control for Fluid-Structure Frequency Selection
FLSFSEL (Case) Control for Fluid-Structure Frequency Selection
Control for fluid-structure frequency selection.
Format:
0.0 1. + 30
FLSFSEL LFREQFL = HFREQFL =
fl 1 fl 2
0.0 1. + 30
LFREQ = HFREQ =
fs 1 fs 2
0 0
LMODESFL = LMODES =
mf ms
0
FLUIDSE =
seidf
Example:
FLSFSEL
.
HFREQ = 4. HFREQFL = 9
Describer Meaning
LFREQFL Requests in Hertz, lower bound frequency for modal fluid calculations.
fl 1 Lower frequency range for fluid, real number.
HFREQFL Requests in Hertz, upper bound frequency for modal fluid calculations.
fl 2 Upper frequency range for fluid, real number.
LFREQ Requests in Hertz, lower bound frequency for modal structure calculations.
fs 1 Lower frequency range for structure, real number.
HFREQ Requests in Hertz, upper bound frequency for modal structure calculations.
fs 2 Upper frequency range for structure, real number
LMODESFL Lowest modes for fluid portion of model, 0 implies LFREQFL-HFREQFL will
determine number of modes.
mf Number of lowest modes to use for fluid portion of model.
LMODES Lowest modes for structure portion of model, 0 implies LFREQ-HFREQ will
determine number of modes.
ms Number of lowest modes to use for structure portion of model.
Main Index
CHAPTER 5 373
Control for Fluid-Structure Frequency Selection
Describer Meaning
FLUIDSE Defines a specified superelement to be used for fluids only.
seidf Defines a fluid only superelement.
Remarks:
1. This entry represents a collection of PARAM,name,value entries. See Parameters for detailed
description of the parameters collected on this entry. The value of any of these parameters may be
given as either the character value given in this description, or the numeric value given in Parameters
of this guide.
2. If LMODES (or LMODESFL)=0, the retained modes are determined by the parameters LFREQ and
HFREQ (or LFREQFL and HFREQFL).
Main Index
374 MSC Nastran Quick Reference Guide
Control for Fluid-Structure Mode Participation Output
FLSPOUT (Case) Control for Fluid-Structure Mode Participation Output
Control for fluid-structure mode participation output.
Format:
ALL
ALL
FLSPOUT FLUIDMP = n modes GRIDFMP = setf
participations
NONE
ALL
1. – 11
OUTFMP = p highest FEPS =
epsf
NOPRINT
0.95
ARF = --------------
arf_v
ALL ALL
STRUCTMP = m modes OUTSMP = q highest
NONE NOPRINT
ALL ALL
PANELMP = setp participations GRIDMP = setg participations
NONE NONE
1. – 11 0.95
SEPS = ARS =
epss ars_v
ABSOLUTE
DESCENDING YES
PSORT = REAL O2E =
ASCENDING NO
IMAGINARY
Examples:
SET 23 = ROOF, DRIVERSD
SET 211 = 1023, 4069, 56790
Main Index
CHAPTER 5 375
Control for Fluid-Structure Mode Participation Output
FLSPOUT FLUIDMP = 30 STRUCTMP = 40, OUTSMP = 30,
PANELMP = 23 GRIDMP = 211
Describer Meaning
FLUIDMP Requests fluid participation calculation of fluid response on selected fluid points.
ALL Requests that all the fluid modes extracted be used.
n Requests that up to the first n fluid modes be used.
NONE Requests no participation calculation.
GRIDFMP Requests inclusion or exclusion of specific fluid grids to be used in all the requested
types of participation calculations. These are also the fluid grids that can be referred
to on plot and .op2 tables.
ALL Requests inclusion in all the requested types of the participation calculations of all
fluid points.
setf Case Control set ID listing a selected set of fluid grids to be used in all the requested
types of participation calculations.
OUTFMP Requests the FLUID FLUIDMP participation factors to be output for print.
ALL Requests that all FLUID FLUIDMP participation factors to be output for print.
p Requests the p highest FLUIDMP participation factors to be output.
NOPRINT Produces tables for plotting but do not print any results.
FEPS Filters threshold for fluid participation.
epsf Threshold value.
ARF Acceptance ratio for fluid participation.
arf_v Fluid participation values arf_v* max_value in a column of the output matrix
will be set to zero.
STRUCTMP Requests structural, load, and panel participation calculations on the selected fluid
points. FLUIDMP must be specified for this command to become active.
ALL Requests that all the structural modes extracted be used.
m Requests that up to the first m structural modes be used.
NONE Requests no participation calculation.
OUTSMP Requests that structural STRUCTMP participation factors to be output for print.
ALL Request that all STRUCTMP participation factors be output.
q Requests that the q highest STRUCTMP participation factors be output.
NOPRINT Produces tables for plotting but does not print any results.
PANELMP Requests inclusion or exclusion of panel participation calculations on the selected
fluid points. FLUIDMP and STRUCTMP must both be specified for this
command to become active.
Main Index
376 MSC Nastran Quick Reference Guide
Control for Fluid-Structure Mode Participation Output
Describer Meaning
ALL Requests all panels defined be included in the participation calculations on the
selected fluid points.
setp Case Control set ID listing selected panels for panel participation calculations on the
selected fluid points.
the set consists of the character names of the panels (new V2001)
NONE Requests exclusion from the participation calculations.
GRIDMP Requests inclusion or exclusion of a structural panel grid participation calculation
on the selected fluid points. FLUIDMP and STRUCTMP must both be specified
for this command to become active.
ALL Requests, for panels selected, that each and every individual panel grid be included
as a separate calculation in the participation calculations on selected fluid points.
setg Case Control set ID listing structural panel grids for grid mode participation on the
selected fluid points.
NONE Requests exclusion from the participation calculations.
SEPS Filter threshold for structure participation.
epss Threshold value.
ARS Acceptance ratio for structure related fluid participation.
ars_v Structure fluid participation values arf_v* max_value in a column of the
output matrix will be set to zero.
PSORT Requests type of sort.
O2E Controls generation of tables of mode participation versus natural frequency for
excitation frequencies. These tables are accessible in XYPLOT.
Remarks:
1. This entry represents a collection of PARAM,name,value entries and must appear above the subcase
level. See Parameters for detailed descriptions of the parameters collected on this entry. The value of
any of these parameters may be given as either the character value given in this description, or the
numeric value given in Parameters on this guide.
2. If n, m, p, or q are greater than the number computed, Nastran will invoke the ALL option for the
current value.
3. PSORT values must occur in pairs such as (ABSOLUTE,DESCENDING).
4. The underlined item in the { } braces give the value of the keyword if the keyword and its describers
are omitted from this entry. For example, if FLUIDMP is omitted from the FLSPOUT entry, then
no fluid mode participation will be computed (unless a PARAM,FLUIDMP,value explicitly appears
in a subcase or Bulk Data Entries).
Main Index
CHAPTER 5 377
Miscellaneous Fluid-Structure Control Parameters
FLSTCNT (Case) Miscellaneous Fluid-Structure Control Parameters
Control for fluid-structure symmetry and force requests.
Format:
PEAK
YES RMS
FLSTCNT ACSYM = ACOUT =
NO PEAKINT
RMSINT
1.0 YES
PREFDB = ASCOUP =
prp NO
NONE
PUNCH
SKINOUT =
PRINT
ALL
Example(s):
FLSTCNT ACSYM = YES ACOUT = RMS
Describer Meaning
ACSYM Requests symmetric or nonsymmetric solution for fluid-structure analysis.
YES Requests symmetrized coupled fluid-structure analysis.
NO Requests no symmetric coupled fluid-structure analysis.
ACOUT Requests peak or rms for output to be used with the FORCE request.
PEAK, PEAKINT Requests peak value output to be used with the FORCE request.
RMS, RMSINT Requests rms value output to be used with the FORCE request.
PREFDB Specifies the peak reference pressure.
prp Value for the peak reference pressure.
ASCOUP Request a coupled or noncoupled fluid-structure analysis.
YES Request a coupled fluid-structure analysis.
NO Request a noncoupled fluid-structure analysis.
SKINOUT Request that sets of grid point and element lists be output for both the fluid and
structure at the fluid-structure interface.
Main Index
378 MSC Nastran Quick Reference Guide
Miscellaneous Fluid-Structure Control Parameters
Describer Meaning
NONE Requests no output of sets.
PUNCH Requests set output to punch file (.pch) only.
PRINT Requests set output to .f06 file only.
ALL Requests set output to both .pch and .f06 files.
Remarks:
1. This entry represents a collection of PARAM,name,value entries. See Parameters for detailed
descriptions of the parameters collected on this entry. The value of any of these parameters may be
given as either the character value given in this description, or the numeric value given under the
parameter description in this guide.
2. Options with suffix INT generates INTENSITY, instead of ACCLERATION. Unlike
ACCELERATION which is complex, INTENSITY is a scalar quantity.
Main Index
CHAPTER 5 379
Heat Transfer Gradient and Flux Output Request
FLUX (Case) Heat Transfer Gradient and Flux Output Request
Requests the form and type of gradient and flux output in heat transfer analysis.
Format:
ALL
PRINT PUNCH
FLUX = n
PLOT
NONE
Examples:
FLUX=ALL
FLUX(PUNCH,PRINT)=17
FLUX=25
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Flux for all elements will be output.
NONE Flux for no elements will be output.
n Set identification of a previously appearing SET command. Only fluxes of elements
with identification numbers that appear on this SET command will be output
(Integer > 0).
Remarks:
1. FLUX=ALL in SOL 159 may produce excessive output.
2. FLUX=NONE overrides an overall request.
Main Index
380 MSC Nastran Quick Reference Guide
Flutter Analysis Method Parameter Selection
FMETHOD (Case) Flutter Analysis Method Parameter Selection
Selects the parameters to be used by the aerodynamic flutter analysis.
Format:
FMETHOD=n
Example:
FMETHOD=72
Describer Meaning
n Set identification number of a FLUTTER Bulk Data entry (Integer > 0).
Remarks:
1. An FMETHOD command is required for flutter analysis.
2. A CMETHOD command is also required for the K-method of flutter analysis.
3. If this entry is being used in SOL 200 in conjunction with flutter design conditions, the METHOD
selected on the FLUTTER Bulk Data entry must be “PK” or “PKNL”.
Main Index
CHAPTER 5 381
Element Force Output or Particle Velocity Request
FORCE (Case) Element Force Output or Particle Velocity Request
Requests the form and type of element force output, or particle velocity output, in coupled fluid-structural
analysis. Note: ELFORCE is an equivalent command.
Format:
CENTER
SORT1 PRINT PUNCH REAL or IMAG CORNER or BILIN
FORCE ( ,
SORT2 PLOT PHASE SGAGE
CUBIC
ALL
PSDF,ATOC,CRMS RPRINT
, RPUNCH ) = n
or RALL NORPRINT
NONE
Examples:
FORCE=ALL
FORCE(REAL, PUNCH, PRINT)=17
FORCE=25
FORCE(SORT2, PRINT, PSDF, CRMS, RPUNCH)=20
FORCE(PRINT, RALL, NORPRINT)=ALL
Describer Meaning
SORT1 Output will be presented as a tabular listing of elements for each load, frequency,
eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each element
type.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
Main Index
382 MSC Nastran Quick Reference Guide
Element Force Output or Particle Velocity Request
Describer Meaning
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is
in degrees.
PSDF Requests the power spectral density function be calculated and stored in the
database for random analysis postprocessing. Request must be made above the
subcase level, and RANDOM must be selected in the Case Control Section. See
Remark 8.
ATOC Requests the autocorrelation function be calculated and stored in the database for
random analysis postprocessing. Request must be made above the subcase level,
and RANDOM must be selected in the Case Control Section. See Remark 8.
CRMS Requests the cumulative root mean square function be calculated for random
analysis postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in the Case Control Section. See Remark 8.
RALL Requests all of PSDF, ATOC, and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM
must be selected in the Case Control Section. See Remark 8.
CENTER Output CQUAD4, CQUADR, and CTRIAR element forces at the center only.
The default for CQUAD4 is CENTER. The default for CQUADR and CTRIAR
is CORNER.
CORNER or Output CQUAD4, QUADR, and CTRIAR element forces at the center and at
BILIN the grid points using strain gage approach with bilinear extrapolation.
SGAGE Output CQUAD4 element forces at the center and at the grid points using strain
gage approach.
CUBIC Output CQUAD4 element forces at the center and at the grid points using cubic
bending correction.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
RPUNCH Writes random analysis results in the punch file.
ALL Forces for all elements will be output.
n Set identification of a previously appearing SET command. Only forces of
elements with identification numbers that appear on this SET command will be
output (Integer > 0).
NONE Forces for no elements will be output.
Remarks:
1. ALL should not be used in a transient problem.
2. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
Main Index
CHAPTER 5 383
Element Force Output or Particle Velocity Request
3. ELFORCE is an alternate form and is entirely equivalent to FORCE.
4. FORCE=NONE overrides an overall request.
5. If PARAM,SPARSEDR,NO is specified, then to request force output on damping elements in modal
frequency response analysis (e.g., SOL 111), the mode displacement method (PARAM,DDRMM,-
1) must be selected.
Force output on damping elements is not available in transient response analysis.
6. In nonlinear transient analysis, the FORCE request is ignored for nonlinear elements in SOL129. In
SOL400 with "ANALYSIS=NLTRAN" Element FORCE output for the CWELD/CFAST elements
is available. All other elements capable of force output such as the CBEAM, CQUAD4, etc., will not
produce nonlinear transient force output.
If "PARAM, OLDWELD, YES" is specified, then the CWELD/CFAST elements will not produce
with "ANALYSIS=NLTRAN" Element FORCE output.
7. The options CENTER, CORNER, CUBIC, SGAGE, and BILIN are recognized only in the first
subcase, and determine the option to be used in all subsequent subcases with the STRESS, STRAIN,
and FORCE Case Control commands. Consequently, options specified in subcases other than the
first subcase will be ignored. The BILIN or CORNER option is not available for advanced nonlinear
elements and nonlinear material or composite elements. The default option will be applied to those
elements.
a. If the STRESS command is specified in the first subcase, then the option on the STRESS
command is used in all subcases with STRESS, STRAIN, and FORCE commands.
b. If the STRAIN command and no STRESS command is specified in the first subcase, then the
option on the STRAIN command is used in all subcases containing STRESS, STRAIN, and
FORCE commands.
c. If the FORCE command and no STRESS or STRAIN commands is specified in the first subcase,
then the option on the FORCE command is used in all subcases containing STRESS, STRAIN,
and FORCE commands.
d. If STRESS, STRAIN, and FORCE commands are not specified in the first subcase, then the
CENTER option is used in all subcases containing STRESS, STRAIN, and FORCE commands.
8. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
9. In general, for nonlinear elements, force output is not available. For CGAP, CELASi, or CBUSH
elements in nonlinear analysis, use the STRESS in NLSTRESS command to obtain force output.
10. Forces and moment output for line elements are total forces and for shell elements they are forces per
unit length.
11. The FORCE request is ignored for solid elements in all solution sequences as it has no meaning for
solids.
12. Random response for element type CBEAM3 is not supported.
Main Index
384 MSC Nastran Quick Reference Guide
Frequency Set Selection
FREQUENCY (Case) Frequency Set Selection
Selects the set of forcing frequencies to be solved in frequency response problems.
Format:
FREQUENCY=n
Example:
FREQUENCY=17
Describer Meaning
n Set identification number of FREQ, FREQ1, FREQ2, FREQ3, FREQ4, and
FREQ5 Bulk Data entries. (Integer > 0)
Remarks:
1. A frequency set selection is required for a frequency response problem.
2. A frequency set selection is required for transient response by Fourier methods (SOL 146).
3. All FREQi entries with the same set identification numbers will be used. Duplicate frequencies will
be ignored. f N and f N – 1 are considered duplicated if
f N – f N – 1 DFREQ f MAX – f MIN
–5
where DFREQ is a user parameter with a default of 10. f MAX and f MIN are the maximum and
minimum excitation frequencies of the combined FREQi entries, respectively.
4. If there are multiple frequency response subcases, improved performance can be obtained by making
the all the subcases that share the same FREQUENCY ID contiguous. For SOL 200, it is an error if
there are noncontiguous subcases that have the same boundary condition and FREQUENCY ID.
5. When a FATIGUE case control is also present to perform random vibration fatigue analysis using
SOLs 108 and 111, only one FREQUENCY case control set is allowed for all transfer function
SUBCASEs and should be above the SUBCASE level or only present in 1st SUBCASE. The
FREQUENCY set cannot change from SUBCASE to SUBCASE or a fatal error is issued.
Main Index
CHAPTER 5 385
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
FRF (Case) Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA)
Specification
Specifies the information needed for FRF generation and/or the FBA process. SOLs 108 and 111 only.
Format:
GEN
FRF ASM COMPID = cmpid COMPNAME = cmpname
GENASM
UNIT
UNITALL
CONNPTS = setid XITOUT =
USER
USERTOTL
COMP
ALL STD
ASSEMBLY
ASMOUT = LOADLBL = ALT
CONNINFO
ALTX
n
cname
DB
OP2 = unit
Main Index
386 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
ALL
ICFGEN= n
compname
ICFDB
=
n ICFOP2={icfunit
ICFUSE=
compname
ICFAUTO= n
compname
Examples:
FRF
FRF (COMPID = 10 COMPNAME = WING CONNPTS = 1000 LOADLBL = ALT)
FRF (COMPID = 20 COMPNAME = STRUT CONNPTS = 2000 OP2 = 25)
FRF (COMPID = 30 COMPNAME = BODY CONNPTS = 300 XITOUT = UNITALL)
FRF (ASM)
FRF (ASM LOADLBL = ALTX)
FRF (ASM ASMOUT = ALL)
FRF (GENASM COMPID = 50 COMPNAME = SUSPENSN CONNPTS = 200)
FRF (ASM ICFGEN = ALL)
FRF (ASM ICFUSE = 100)
FRF (ASM ICFGEN = 200 ICFOP2 = 33)
FRF (ASM ICFUSE = -1 ICFOP2 = 33)
FRF (ASM ICFAUTO = 100)
FRF
.
(ASM ICFAUTO = -5 ICFOP2 = 31)
Describer Meaning
GEN Generate the FRFs for the specified component. See Remarks 3. and 4.,
(Default) and the Examples in Remark 13.
ASM Compute the FRFs of an assembly of components from the FRFs of the
individual components. See Remarks 5., 9., 10. and 11., and Examples 2
and 3 in Remark 13.
GENASM Generate the FRFs for the specified component and follow it by
computing the FRFs of an assembly of components from the FRFs of the
individual components. See Remarks 4., 9., 10. and 11., and Examples 4
and 5 in Remark 13.
COMPID = cmpid cmpid (Integer > 0) is the identification number of the component whose
FRFs are to be generated. See Remarks 3. through 7., and Examples 2
through 5 in Remark 13.
COMPNAME = cmpname cmpname (up to eight characters) is the name of the component whose
FRFs are to be generated. See Remarks 3. through 7., and Examples 2
through 5 in Remark 13.
Main Index
CHAPTER 5 387
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Describer Meaning
CONNPTS = setid setid (integer > 0) refers to the set that defines the points at which the FRF
component specified by the COMPID/COMPNAME keywords is to be
connected during a subsequent FRF based assembly (FBA) process. Only
those points that are defined in this set (and no others) will be considered
for connection during the FBA process. See Remarks 7., 12.(c) and 12.(d),
and Examples 2 through 5 in Remark 13.
XITOUT = UNIT Output the FRF results only for those unit excitations that are specified
explicitly via FRFXIT / FRFXIT1 Bulk Data entries or implicitly via the
DLOAD Case Control request. See Remark 8.
The output for each of the above excitations is identified by a separate
subcase. The IDs of these subcases are numbered consecutively starting
from 1.
XITOUT = UNITALL Output FRF results not only for unit excitations specified explicitly via
FRFXIT / FRFXIT1 Bulk Data entries or implicitly via the DLOAD Case
Control command, but also for unit excitations that are internally applied
automatically by the program at the connection points of the FRF
component(s). See Remarks 8. and 12.(c), and Example 2 in Remark 13.
The output for each of the above excitations is identified by a separate
subcase. The IDs of these subcases are numbered consecutively starting
from 1.
Main Index
388 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Describer Meaning
XITOUT = USER Output the FRF results for the following excitations implied by the
DLOAD Case Control request:
a. A separate excitation for each individual DOF that has a non-
zero load value specified for it
b. An excitation representing the total load
Thus, if a DLOAD Case Control request involves non-zero load values on
N DOFs, then this request gives results for (N+1) excitations, with the first
N such excitations representing individual and separate loads on the N
DOFs and the (N+1)th excitation representing the total load. See Remark
8.
The output for each of the above (N+1) excitations is identified by a
separate coded subcase ID of the form xxxxyyyy. Here xxxx is the user
subcase ID corresponding to the DLOAD under consideration. For the
first N excitations, yyyy has values ranging from 1 through N (with leading
zeros where appropriate). For the (N+1)th excitation representing the total
load, the coded subcase ID is of the form xxxx9999.
Because of the above coded numbering scheme, when XITOUT = USER
is specified (or assumed; see Remark 8), the program will not allow any
user subcase ID to exceed 9999. If it does, the program terminates the job
with an appropriate fatal message.
XITOUT = USERTOTL Output the FRF results for the single excitation representing the total load
implied the DLOAD Case Control request. This corresponds to the
(N+1)th excitation mentioned earlier. See Remark 8.
The output for this single excitation representing the total load is identified
by the coded subcase ID of the form xxxx9999 where xxxx is the user
subcase ID corresponding to the DLOAD under consideration.
Because of the above coded numbering scheme, when XITOUT =
USERTOTL is specified, the program will not allow any user subcase ID
to exceed 9999. If it does, the program terminates the job with an
appropriate fatal message.
ASMOUT = CONNINFO In the FBA process, terminate the job after generating the FRF component
connection information output without performing any further FRF
assembly calculations.
ASMOUT = COMP In the FBA process, output the FRF results for all of the individual FRF
(Default) components comprising the assembly. See Remarks 10. and 11.
Main Index
CHAPTER 5 389
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Describer Meaning
ASMOUT = ALL In the FBA process, output the FRF results not only for all of the
individual FRF components comprising the assembly, but also for the
assembled FRF configuration considered as a separate entity. See Remarks
10. and 11., and Example 3 in Remark 13. See also Remark 2.
ASMOUT = ASSEMBLY In the FBA process, output the FRF results only for the assembled FRF
configuration considered as a separate entity. This is equivalent to
specifying ASMOUT = 0 (described later). See Remarks 2. and 10.
ASMOUT = n n is an integer with the following meanings:
n=0
In the FBA process, output the FRF results only for the assembled FRF
configuration considered as a separate entity. This is equivalent to
specifying ASMOUT = ASSEMBLY (described earlier). See Remarks 2.
and 10.
n>0
In the FBA process, output the FRF results only for those FRF
components of the assembly whose IDs are specified by SET ID n.
n<0
In the FBA process, output the FRF results only for that single FRF
component of the assembly whose ID is given by n .
ASMOUT = cname In the FBA process, output the FRF results only for that single FRF
component of the assembly whose name is given by cname.
LOADLBL = STD The load labels in the output in the FRF and FBA jobs explicitly identify
(Default) the grid (or scalar) point and its component where the load is applied.
LOADLBL = ALT The load labels in the output in the FRF and FBA jobs identify the grid
(or scalar) point and its component where the load is applied by using the
following notation:
GGGGGGGG:+C
where GGGGGGGG is the grid (or scalar) point ID and C indicates the
component where the load is applied. C may have the following values:
X Indicates grid point component 1 or a scalar point
Y Indicates grid point component 2
Z Indicates grid point component 3
RX Indicates grid point component 4
RY Indicates grid point component 5
RZ Indicates grid point component 6
LOADLBL = ALTX Same as LOADLBL = ALT except that the load labels also identify whether
the load applied is a unit load or a user load.
Main Index
390 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Describer Meaning
DB Store the FRF matrices and other information on the database. See
(Default) Examples 2 and 4 in Remark 13.
OP2 = unit Store the FRF matrices and other information on an OUTPUT2 file
whose Fortran unit number is given by unit (integer > 0). See Examples 3
and 5 in Remark 13.
ICFGEN = ALL Generate ICF information in the FBA process for all of the FRF
components of the assembly
ICFGEN = n n is a non-zero integer with the following meanings:
n>0
Generate ICF information in the FBA process only for those FRF
components of the assembly whose IDs are included in SET n,
n<0
Generate ICF information in the FBA process only for that single FRF
component of the assembly whose ID is given by |n|.
ICFGEN = compname Generate ICF information for the FRF component whose name is given
by compname.
ICFUSE = n n is a non-zero integer with the following meanings:
n>0
Use ICF information by employing in the FBA process a
Configuration that consists of only those FRF components whose
IDs are specified by SET ID n.
n<0
Use ICF information by employing in the FBA process a Configuration
that consists of only that single FRF component whose ID is given by |n|.
ICFUSE = compname Configuration that consists of only that single FRF component whose
name is given by compname.
Main Index
CHAPTER 5 391
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Describer Meaning
ICFAUTO = n n is a non-zero integer with the following meanings:
n>0
First generate and then use ICF information in the FBA process only for
those FRF components whose IDs are specified by SET ID n.
n < 0: First generate and then use ICF information only for the single FRF
component whose ID is given by |n|.
ICFAUTO = compname First generate and then use ICF information for the single FRF component
whose name is given by compname.
ICFDB (Default) ICF information is to be stored or is resident on the database.
ICFOP2 = icfunit ICF information is to be stored or is resident on an OUTPUT2 file whose
Fortran unit number is given by icfunit (integer > 0).
Remarks:
1. This command is supported only in SOLs 108 and 111.
2. A component ID of 0 is assigned to the assembled FRF configuration resulting from the FBA process.
3. The COMPNAME keyword must be specified if the COMPID keyword is specified and vice versa.
4. If the COMPID/COMPNAME keywords are specified along with the GEN/GENASM keyword,
then it implies that the FRFs computed for the specified component are employed in a subsequent
FBA process. In this case, the FRF generation results will be saved on the specified medium, and the
.asm (assembly punch) file will be generated and saved with a single FRFCOMP Bulk Data entry
in it for subsequent use in an FBA process.
5. If the COMPID/COMPNAME keywords are not specified with the GEN/GENASM keyword, then
it implies that the FRFs computed are for a single shot configuration with no subsequent FBA process
involved. In this case, the GENASM keyword is equivalent to the GEN keyword.
6. The COMPID/COMPNAME keywords are ignored if the ASM keyword is specified.
7. The CONNPTS keyword must be specified if the COMPID/COMPNAME keywords are specified.
It is ignored otherwise.
8. If the XITOUT keyword is not specified, the default of XITOUT = UNIT is assumed if there is no
DLOAD Case Control request and the default of XITOUT = USER is assumed if there is a DLOAD
Case Control request. If the user specifies XITOUT = USER or XITOUT = USERTOTL, but there
is no DLOAD Case Control request, the program issues a warning message and assumes XITOUT =
UNIT.
9. If the ASM/GENASM keyword is specified, the resulting FBA process will generate a connection
information table in the .f06 file, indicating the relationship between the internal point IDs of the
assembled FRF configuration (referred to as component 0 as indicated in Remark 2.) and the external
point IDs of the associated FRF components.
Main Index
392 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
10. The normal output from an FBA process run, implied by the default of ASMOUT = COMP, gives
the results for the individual FRF components that comprise the assembled FRF configuration. If
output is also desired for the assembled configuration as a separate entity (component 0 as indicated
in Remark 2.), then ASMOUT = ALL must be specified in the FRF command to obtain the expanded
output. However, in this case, the output for component 0 will be limited to displacements,
velocities, and accelerations, and these will be output in terms of the internal point IDs mentioned in
Remark 9. See Example 3 in Remark 13.
11. The ASMOUT keyword is ignored if the GEN keyword is specified.
12. The generation of FRFs for a component and their use in a subsequent FBA process using the FRF
Case Control command involves running a standard SOL 108 or SOL 111 job, with the following
additional data:
a. The DOFs where loads are to be applied must be specified either indirectly via the DLOAD Case
Control command and/or directly via the FRFXIT/FRFXIT1 Bulk Data entries. The DLOAD
Case Control command points to appropriate Bulk Data loading entries. All DOFs with nonzero
load values will have unit loads applied to them. The FRFXIT entry permits specification of unit
load for a single DOF with a label. The FRFXIT1 entry permits specification of unit loads at
multiple DOFs.
b. There is no requirement that unit loading data be defined for every component for which FRFs
are generated, since some components in a configuration may not have any loads applied to them.
c. Regardless of whether an FRF component has unit loads explicitly specified for it, as in Remark
12(a) or not, as in Remark 12(b), the program will internally apply unit loads automatically at all
DOFs for all connection points comprising the set referenced by the CONNPTS keyword. This
ensures that correct results are obtained from subsequent FBA processes.
d. The specific points at which FRFs are computed in an FRF generation run consist of the
following:
• All points specified via DISP, VELO, and ACCE requests
• All points associated with elements for which STRESS/FORCE requests are specified
• All points at which unit loads are applied (as per the scheme indicated in Remark 12(a)
• All points comprising the set referenced by the CONNPTS keyword
• All grid points referenced in PLOTEL Bulk Data entries
e. It is assumed in an FBA process that the FRFs of all of the FRF components have been generated
at the same forcing frequencies, and that these are also the forcing frequencies at which the FBA
process is to be performed. As a result, the FBA process derives these forcing frequencies from the
saved data of the first of the FRF components being assembled, and uses them in the FBA process.
In order to ensure the validity of the FBA process, the program checks to make sure that all of the
FRF components have been generated using the same number of forcing frequencies and further
that all of these forcing frequencies are the same for all of the FRF components. If both of these
conditions are not met, the program terminates the job with an appropriate fatal message.
13. The following examples illustrate details of job setups for FRF generation and the subsequent FBA
process for various scenarios.
Main Index
CHAPTER 5 393
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 1 involves FRF generation for a single shot configuration without any FBA process.
Examples 2 through 5 assume that there are three components – 10, 20 and 30 – for which FRFs are
to be generated (frgen10.dat, frfgen20.dat and frgen30.dat) and that the FRFs of these components
are to be subsequently assembled in an FBA process to obtain the FRFs of the assembled
configuration.
Example 6 illustrates an FBA process involving the assembly of two components – 10 and 20 – whose
FRFs are generated by Nastran, with a third FRF component – 40 – whose FRFs have been generated
from test, with its FRF and other information resident on an Universal File (UF).
Examples 2, 3 and 6 illustrate the use of the ASM option for the FBA process while Examples 4 and
5 illustrate the use of the GENASM option for the FBA process.
Examples 7 through 13 deal with an airplane model comprising five FRF components, namely,
fuselage (1), horizontal tail (2), vertical tail (3), inboard wings (4) and outboard wings (5). Example
7 illustrates the generation of the FRFs for these five components while the other examples are FBA
jobs that illustrate the generation and usage of ICFs (inter component forces) for several scenarios
using the ICFGEN, ICFUSE and ICFAUTO keywords of the FRF Case Control command,
employing both database and OUTPUT2 usage.
Loading data must be defined for Example 1 either via FRFXIT/FRFXIT1 Bulk Data entries or via
the DLOAD Case Control request. For all other examples, loading data may be defined as desired
either in the FRF generation runs or in the FBA process or both.
)
Example 1. Generate FRFs for a Single Shot Configuration with No Subsequent FBA Process
FRF Generation Job
• Case Control Requirement
FRF
Loading data must be defined either via the DLOAD Case Control command and/or
via FRFXIT/FRFXIT1 Bulk Data entries.
Example 2. Generate FRFs for Components 10, 20, and 30 Using the DB Option and
Subsequently Assemble Their FRFs to Obtain FRFs of the Assembled Configuration Using the
ASM Option
FRF Generation Jobs
• Case Control Requirement
FRF component 10: FRF (COMPID = 10 COMPNAME = COMP10 CONNPTS = 100)
FRF component 20: FRF (COMPID = 20 COMPNAME = COMP20 CONNPTS = 200)
FRF component 30: FRF (COMPID = 30 COMPNAME = COMP30 CONNPTS = 300)
For these jobs, scr = no should be specified on the Nastran job command lines to ensure
that the databases are saved at the end of the jobs.
These jobs automatically generate .asm files for subsequent use by the FBA job.
Main Index
394 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 2. Generate FRFs for Components 10, 20, and 30 Using the DB Option and
Subsequently Assemble Their FRFs to Obtain FRFs of the Assembled Configuration Using the
ASM Option
FBA Job
• File Management Section (FMS) Requirement
ASSIGN dbname10 = ‘frfgen10.MASTER’
ASSIGN dbname20 = ‘frfgen20.MASTER’
ASSIGN dbname30 = ‘frfgen30.MASTER’
DBLOCATE DATABLK = (FRFDB) LOGICAL = dbname10
DBLOCATE DATABLK = (FRFDB) LOGICAL = dbname20
DBLOCATE DATABLK = (FRFDB) LOGICAL = dbname30
(Note: All of the data blocks stored on the databases from the FRF generation runs have
the same common name of FRFDB.)
• Case Control Requirement
FRF (ASM XITOUT = UNITALL)
The XITOUT = UNITALL request gives output for all unit excitations (both user
specified unit loads and internally applied unit loads).
• Bulk Data Requirement
The following INCLUDEs are required.
INCLUDE ‘frfgen10.asm’
INCLUDE ‘frfgen20.asm’
INCLUDE ‘frfgen30.asm’
Example 3. Generate FRFs for Components 10, 20, and 30 Using the OP2 Option and
Subsequently Assemble Their FRFs to Obtain FRFs of the Assembled Configuration Using the
ASM Option
FRF Generation Jobs
• File Management Section (FMS) Requirement
ASSIGN OUTPUT2 = ‘frfgen10_op2’ UNIT = 25 DELETE
ASSIGN OUTPUT2 = ‘frfgen20_op2’ UNIT = 26 DELETE
ASSIGN OUTPUT2 = ‘frfgen30_op2’ UNIT = 27 DELELE
For these jobs, scr = yes may be specified on the Nastran job command lines since there
is no need for the databases to be saved at the end of the jobs.
These jobs automatically generate .asm files for subsequent use by the FBA job.
• Case Control Requirement
Main Index
CHAPTER 5 395
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 3. Generate FRFs for Components 10, 20, and 30 Using the OP2 Option and
Subsequently Assemble Their FRFs to Obtain FRFs of the Assembled Configuration Using the
ASM Option
FRF component 10: FRF (COMPID = 10 COMPNAME = COMP10 CONNPTS = 100 OP2 = 25)
FRF component 20: FRF (COMPID = 20 COMPNAME = COMP20 CONNPTS = 200 OP2 = 26)
FRF component 30: FRF (COMPID = 30 COMPNAME = COMP30 CONNPTS = 300 OP2 = 27)
FBA Job
• File Management Section (FMS) Requirement
ASSIGN INPUTT2 = ‘frfgen10_op2’ UNIT = 25
ASSIGN INPUTT2 = ‘frfgen20_op2’ UNIT = 26
ASSIGN INPUTT2 = ‘frfgen30_op2’ UNIT = 27
• Case Control Requirement
FRF (ASM ASMOUT = ALL)
The ASMOUT = ALL request gives output from the FBA process not only for FRF
components 10, 20 and 30, but also for the assembled configuration as a separate entity
(component 0) as indicated in Remark 10.
• Bulk Data Requirement
The following INCLUDEs are required.
INCLUDE ‘frfgen10.asm’
INCLUDE ‘frfgen20.asm’
INCLUDE ‘frfgen30.asm’
Example 4. Generate FRFs for Components 10 and 20 Using the DB Option and Subsequently
Assemble their FRFs with Those of Component 30 Using the DB and GENASM Options to Obtain
the FRFs of the Assembled Configuration.
FRF Generation Jobs
• Case Control Requirement
FRF component 10: FRF (COMPID = 10 COMPNAME = COMP10 CONNPTS = 100)
FRF component 20: FRF (COMPID = 20 COMPNAME = COMP20 CONNPTS = 200)
For these jobs, scr = no should be specified on the Nastran job command line to ensure
that the databases are saved at the end of the jobs.
These jobs automatically generate .asm files for subsequent use by the FBA job.
Combined FRF Generation and FBA Job
• File Management Section (FMS) Requirement
ASSIGN dbname10 = ‘frfgen10.MASTER’
ASSIGN dbname20 = ‘frfgen20.MASTER’
Main Index
396 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 4. Generate FRFs for Components 10 and 20 Using the DB Option and Subsequently
Assemble their FRFs with Those of Component 30 Using the DB and GENASM Options to Obtain
the FRFs of the Assembled Configuration.
DBLOCATE DATABLK=(FRFDB) LOGICAL=dbname10
DBLOCATE DATABLK=(FRFDB) LOGICAL=dbname20
(Note: All data blocks stored on the databases from the FRF generation runs have the
same common name of FRFDB.)
For this job, scr = no should be specified on the Nastran job command line to ensure
that the database for FRF component 30 is saved for subsequent use by the FBA process.
• Case Control Requirement
FRF (GENASM COMPID = 30 COMPNAME = COMP30 CONNPTS = 300)
• Bulk Data Requirement
The following INCLUDEs are required.
INCLUDE ‘frfgen10.asm’
INCLUDE ‘frfgen20.asm’
Main Index
CHAPTER 5 397
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 5. Generate FRFs for Components 10 and 20 Using the OP2 Option and Subsequently
Assemble their FRFs with Those of Component 30 Using the OP2 and GENASM Options to Obtain
the FRFs of the Assembled Configuration.
FRF Generation Jobs
• File Management Section (FMS) Requirement
ASSIGN OUTPUT2 = ‘frfgen10_op2’ UNIT = 25 DELETE
ASSIGN OUTPUT2 = ‘frfgen20_op2’ UNIT = 26 DELETE
• Case Control Requirement
FRF component 10: FRF (COMPID = 10 COMPNAME = COMP10 CONNPTS = 100 OP2 = 25)
FRF component 20: FRF (COMPID = 20 COMPNAME = COMP20 CONNPTS = 200 OP2 = 26)
For these jobs, scr = yes may be specified on the Nastran job command line since there
is no need for the databases to be saved at the end of the jobs.
These jobs automatically generate .asm files for subsequent use by the FBA job.
Combined FRF Generation and FBA Job
• File Management Section (FMS) Requirement
ASSIGN INPUTT2 = ‘frfgen10_op2’ UNIT = 25
ASSIGN INPUTT2 = ‘frfgen20_op2’ UNIT = 26
ASSIGN OUTPUT2 = ‘frfgen30_op2’ UNIT = 27 DELETE
• Case Control Requirement
FRF (GENASM COMPID = 30 COMPNAME = COMP30 CONNPTS = 300 OP2 = 27)
• Bulk Data Requirement
The following INCLUDEs are required.
INCLUDE ‘frfgen10.asm’
INCLUDE ‘frfgen20.asm’
Main Index
398 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 6. Generate FRFs for Components 10 and 20 Using the OP2 Option and Subsequently
Assemble their FRFs with Those of Test FRF Component 40 Using the ASM Option to Obtain the
FRFs of the Assembled Configuration.
FRF Generation Jobs
• File Management Section (FMS) Requirement
ASSIGN OUTPUT2 = ‘frfgen10_op2’ UNIT = 25 DELETE
ASSIGN OUTPUT2 = ‘frfgen20_op2’ UNIT = 26 DELETE
• Case Control Requirement
FRF component 10: FRF (COMPID = 10 COMPNAME = COMP10 CONNPTS = 100 OP2 = 25)
FRF component 20: FRF (COMPID = 20 COMPNAME = COMP20 CONNPTS = 200 OP2 = 26)
For these jobs, scr = yes may be specified on the Nastran job command line since there
is no need for the databases to be saved at the end of the jobs.
These jobs automatically generate .asm files for subsequent use by the FBA job.
FBA Job
• File Management Section (FMS) Requirement
ASSIGN INPUTT2 = ‘frfgen10_op2’ UNIT = 25
ASSIGN INPUTT2 = ‘frfgen20_op2’ UNIT = 26
ASSIGN UNVFILE = ‘frfgen40_unv’ UNIT = 28 $ Universal File
• Case Control Requirement
FRF (ASM)
• Bulk Data Requirement
FRFCOMP,40,TSTCMP40,UF,28
The following INCLUDEs are also required.
INCLUDE ‘frfgen10.asm’
INCLUDE ‘frfgen20.asm’
Main Index
CHAPTER 5 399
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 7. Generate FRFs for Components 1 through 5 Using the OP2 Option
File Management Section (FMS) Requirement
FRF Component 1:ASSIGN OUTPUT2 = 'fuselage_op2' UNIT=25 DELETE
FRF Component 2:ASSIGN OUTPUT2 = 'hor_tail_op2' UNIT=26 DELETE
FRF Component 3:ASSIGN OUTPUT2 = 'ver_tail_op2' UNIT=27 DELETE
FRF Component 4:ASSIGN OUTPUT2 = 'ib_wings_op2' UNIT=28 DELETE
FRF Component 5:ASSIGN OUTPUT2 = 'ob_wings_op2' UNIT=29 DELETE
Case Control Requirement
FRF Component 1:FRF (COMPID = 1 COMPNAME = FUSELAGE CONNPTS =
1000 OP2=25)
FRF Component 2:FRF (COMPID = 2 COMPNAME = HOR_TAIL CONNPTS =
1000 OP2=26)
FRF Component 3:FRF (COMPID = 3 COMPNAME = VER_TAIL CONNPTS =
1000 OP2=27)
FRF Component 4:FRF (COMPID = 4 COMPNAME = IB_WINGS CONNPTS =
1000 OP2=28)
FRF Component 5:FRF (COMPID = 5 COMPNAME = OB_WINGS CONNPTS
= 1000 OP2=29)
These jobs automatically generate .asm files for subsequent use by the FBA process.
For these jobs, scr = yes may be specified on the Nastran job command lines since there is no need
for the databases to be saved at the end of the jobs.
Example 8. Generate ICFs on the Database for All Five FRF Components of Example 7 (Step 1 of
Two-Step Process)
File Management Section (FMS) Requirement
ASSIGN INPUTT2 = ‘fuselage_op2’ UNIT=25
ASSIGN INPUTT2 = ‘hor_tail_op2’ UNIT=26
ASSIGN INPUTT2 = ‘ver_tail_op2’ UNIT=27
ASSIGN INPUTT2 = ‘ib_wings_op2’ UNIT=28
ASSIGN INPUTT2 = ‘ob_wings_op2’ UNIT=29
Case Control Requirement
Main Index
400 MSC Nastran Quick Reference Guide
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 8. Generate ICFs on the Database for All Five FRF Components of Example 7 (Step 1 of
Two-Step Process)
FRF (ASM ICFGEN = ALL)
Bulk Data Requirement
INCLUDE 'fuselage.asm'
INCLUDE 'hor_tail.asm'
INCLUDE 'ver_tail.asm'
INCLUDE 'ib_wings.asm'
INCLUDE 'ob_wings.asm'
For this job, scr = no should be specified on the Nastran job command line since the database
containing the ICF information needs to be saved for use in a subsequent FBA job (Example 9).
Example 9. Use ICFs of Example 8 for An Assembly Configuration Consisting of FRF
Components 1, 4 and 5 (Step 2 of Two-Step Process)
File Management Section (FMS) Requirement
ASSIGN INPUTT2 = 'fuselage_op2' UNIT=25
ASSIGN INPUTT2 = 'ib_wings_op2' UNIT=28
ASSIGN INPUTT2 = 'ob_wings_op2' UNIT=29
ASSIGN ICFDATA = 'example8.MASTER'
DBLOCATE (DATABLK = ICFDB) LOGICAL = ICFDATA
Case Control Requirement
SET 100 = 1,4,5
FRF (ASM ICFUSE = 100)
Bulk Data Requirement
INCLUDE 'fuselage.asm'
INCLUDE 'ib_wings.asm'
INCLUDE 'ob_wings.asm'
For this job, scr = yes may be specified on the Nastran job command line since there is no need for
the database to be saved at the end of the job.
Main Index
CHAPTER 5 401
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification
Example 10. Generate ICFs on an OUTPUT2 File for FRF Components 1, 2 and 3
of Example 7 (Step 1 of Two-Step Process)
File Management Section (FMS) Requirement
ASSIGN INPUTT2 = 'fuselage_op2' UNIT=25
ASSIGN INPUTT2 = 'hor_tail_op2' UNIT=26
ASSIGN INPUTT2 = 'ver_tail_op2' UNIT=27
ASSIGN INPUTT2 = 'ib_wings_op2' UNIT=28
ASSIGN INPUTT2 = 'ob_wings_op2' UNIT=29
ASSIGN OUTPUT2 = 'icf123_op2' UNIT=33 DELETE
Case Control Requirement
SET 100 = 1,2,3
FRF (ASM ICFGEN = 100 ICFOP2 = 33)
Bulk Data Requirement
INCLUDE 'fuselage.asm'
INCLUDE 'hor_tail.asm'
INCLUDE 'ver_tail.asm'
INCLUDE 'ib_wings.asm'
INCLUDE 'ob_wings.asm'
For this job, scr = yes may be specified on the Nastran job command line since there is no need for
the database to be saved at the end of the job.
Main Index
402 MSC Nastran Quick Reference Guide
Grid Point Force Output Request
GPFORCE (Case) Grid Point Force Output Request
Requests grid point force balance at selected grid points.
Note that GPFORCE is not supported in NLPERF SOL 400.
Format:
GE
G
PRINT PUNCH REAL or IMAG B
GPFORCE = ALL
PLOT PHASE DAMP n
M
ALLDLDS
Examples:
GPFORCE=ALL
GPFORCE=17
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 files can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output. See Remark 14.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees. See Remarks 13. and 14.
GE Element appropriate element structural GEi value contribution of force K4 × Uc
output in addition to the standard elastic force output.
G Element appropriate element structural global G value contribution of force K × Uc
output in addition to the standard elastic force output.
B Element appropriate element viscous damping contribution of force B × i × × Uc
output in addition to the standard elastic force output.
Main Index
CHAPTER 5 403
Grid Point Force Output Request
Describer Meaning
DAMP Element appropriate GE, B, and G will be explicitly output in addition to explicit
current elastic force output.
M Element appropriate element mass contribution of force M × × Uc output in
addition to the standard elastic force output.
ALLDLDS Element appropriate GE, B, G, and M will be output in addition to the standard
elastic force output.
ALL Grid point force balance for all grid points will be output.
n Set identification number of a previously appearing SET command. Only grid
points with identification numbers that appear on this SET command will be
included in the grid point force balance output (Integer >0).
Remarks:
1. The printing of the grid point forces will be suppressed if PARAM,NOGPF,-1 appears in the Bulk
Data.
2. The Bulk Data entry PARAM,NOELOF,+1 will cause the output of the grid point forces to be
aligned with the edges of the two-dimensional elements. The default value of -1 will suppress this
output. See Remark 4.
3. The Bulk Data entry PARAM,NOELOP,+1 will cause the output of the sum of the forces parallel to
the edges of adjacent elements. The default value of -1 will suppress this output. See Remarks 4. and
10.
4. The output of grid point forces aligned with the edges of elements is available for the following
elements: CBAR, CBEAM, CONROD, CQUAD4, CROD, CSHEAR, CTRIA3 and CTUBE.
The positive direction for grid point forces aligned with the edges of elements is from the reference
point to the load point as indicated on the printed output. See Remark 10.
5. The grid point force balance is computed from linear and nonlinear elements, and includes the sum
of applied loads, contact force, thermal loads, MPC forces, rigid elements, general elements, DMIG
entries and SPC forces. Effects not accounted for include those from mass elements in dynamic
analysis (inertia loads), slideline force contributions, and boundary loads from upstream
superelements. These effects may lead to an apparent lack of equilibrium at the grid point level. The
following table summarizes those effects that are considered and those effects that are ignored in the
calculation of grid point forces in the global coordinate system:
Main Index
404 MSC Nastran Quick Reference Guide
Grid Point Force Output Request
Contributions Included Contributions Ignored
Applied Loads DMI Forces
SPC Forces Boundary Loads from Upstream Superelements
Element Elastic Forces Forces on elements with geometric or material nonlinear
properties during normal modes analysis in SOL 106;
also called linear perturbation analysis.
GENEL Forces Connector elements CFAST, CSEAM, and CWELD.
DMIG Referenced by K2GG Case
Control command
Thermal Loads
MPC and Rigid Element Forces
Contact Forces
6. Only the element elastic forces are included when the grid point forces are aligned with the edges of
elements. See Remark 10.
7. In inertia relief analysis, the SPCFORCE and applied load output includes both the effect of inertial
loads and applied loads.
8. When pressure loads are applied, the GPFDR module uses the discrete load vector and does not
include any distributed effects.
9. GPFORCE is not available in SOLs 107,110,128,129,144,145,146,153, and 159. For SOLs 108
and 111, if the only frequency dependency is associated with the CBUSH, CELAS1, CELAS3,
CDAMP1, CDAMP3, or (PARAM, SHLDAMP DIFF), or if any PBUSH has a GEi value other
than GE1, then PARAM,BUSHNM,YES (Default) must be used. GPFORCE, for any solution
sequence, does not include forces from boundary superelements. The unbalance represents the forces
from adjacent superelements.
10. Grid point force output is available for nonlinear static analysis for SOLs 106 and 400. SOL106 with
thermal loading does not back out the thermal load so result will not sum to zero, this is a limitation
of SOL106. Contributions from slideline elements are ignored. PARAM,NOELOF and
PARAM,NOELOP are not supported in nonlinear and Remarks 2., 3., 4., and 6. do not apply.
11. The usages of REPCASE and OMODES Case Control directives is not supported for ESE, EKE,
EDE and GPFO output selections and should not be used.
12. The (GE, G, B, DAMP, M, and ALLDLDS) are only meaningful in SOL108, SOL111 or
ANALYSIS=DFREQ or MFREQ analysis. Frequency response CYCLIC SYMMETRY ANALYSIS
is not supported.
Main Index
CHAPTER 5 405
Grid Point Force Output Request
Elements and features Not supported
(These elements will be ignored in the GPFORCE Calculations)
ELEMENT NAME ANALYSIS
CDUM3-7 User Defined Element
Fluid
CHEXA (CHEXPR) PSOLID with FCTN=FLUID, PORO, or PSLDSHL
CPENTA (CPENPR) PSOLID with FCTN=FLUID, PORO, or PSLDSHL
CTETRA (CTETPR) PSOLID with FCTN=FLUID, PORO, or PSLDSHL
CPYRAM (CPYRPR) PSOLID with FCTN=FLUID, PORO, or PSLDSHL
CAABSF Acoustic Absorber Element
Axisymmetry
CTRIAX6
SOL400 elements associated with PLPLANE
QUAD4FD, QUADFD, Plane strain elements
QUADX4FD, QUADXFD,
TRIA3FD, TRIAFD,
TRIAX3FD, TRIAXFD
Structures
CBUSH2D Rotor Dynamic element
CHACAB Acoustic Absorber element
CHACBR Acoustic Barrier Element
Unsupported elements will appear in the GPFORCE output with incomplete load calculations.
Thus, grids associated with them, in general, will not sum to zero.
13. In general, for frequency response, the “*totals*” rows will not be zero, except when ALLDLDS is
chosen. Also if “PHASE” is also chosen, only the first row of “*TOTALS*” will be zero.
SOL111 and SOL200/SOL400 with ANALYSIS=MFREQ, by their nature, introduce noise into the
solution. As a result, some “*totals*” may have poor zeros. This is especially true when heavy structural
damping is present. The reason is that for structural damping, residual vectors are not computed.
For frequency dependent elements using master frequencies, for forcing frequencies not at the master
frequencies, the interpolation for the solution vector is done on the KGG, K4GG, etc., matrices;
while, for GPFORCE, the interpolations are done on the individual element stiffness matrices and
the individual values of GE appearing on the MATiF entries. As a result, for an interpolated result,
far from its bounding master frequencies, with ALLDLDS, the totals may be several orders higher
than results when the interpolated results have tighter bounding master frequencies.
For frequency dependent elements, the F-OF-MPC, that include both Nastran MPC entry results
and RIGID element results, may be in error. This will cause the “*totals*” to show very large values.
Main Index
406 MSC Nastran Quick Reference Guide
Grid Point Force Output Request
To avoid this, it is recommended that these types of constraints do not touch grids associated with
frequency dependent elements. The reason for this, is that the MPC/RBEi forces of constraint are
currently based on the nominal values of element properties.
For modal damping forces, the 'physical' damping matrix that is calculated from the modal damping
is simply a damping matrix which, when converted to modal coordinates, gives the modal damping.
There is no guarantee that it is 'physically correct'. Hence modal damping may not give good zeros
for “*TOTALS”* for GPFORCE output
For SOL108, SOL111, SOL200 and SOL400 for ANALYSIS=DFREQ or MFREQ with frequency
dependent materials, the contact stiffness is computed using nominal material properties and is not
frequency dependent. Hence, on frequency dependent grids, contact force will reflect the nominal
stiffness and not an updated stiffness based on frequency, thus contact may not give good zeros for
“*TOTALS”* for GPFORCE output on frequency dependent grids.
14. For PRINT and PUNCH options, when PHASE is chosen, the F06 and PCH files will be in
magnitude-phase format. However, in any analysis that involves complex numbers, any and all of the
HDF5 output is automatically converted to real-imaginary format.
Main Index
CHAPTER 5 407
Grid Point Force Output Request
15. For frequency response, the GPFORCE calculations are:
GPFORCE Calculations
F = KELM × (UGR+UGI) - standard elastic force contribution at the grid
FGE = i × GEVAL × GEFACT × KELM4 × (UGR+UGI) - structural damping force contribution
at the grid
FB = BELM × i × × (UGR+UGI) - viscous damping force contribution at the grid
FG = i × G × KELM × (UGR+UGI) - global G/GF - global damping force contribution at the grid
FM = WTMASS × MELM × 2 × (UGR + UGI) - inertia force contribution at the grid.
PS2SC = - KS2Sgg × (UGR+UGI)
GPS2SC = - i × G × KS2Sgg × (UGR+UGI)
KELM - an element stiffness matrix
KELM4 - an element structural damping matrix
BELM - an element viscous damping matrix
MELM - an element mass matrix
KS2Sgg - segment to segment contact stiffness
UGR - real displacement at the grid
UGI - imaginary displacement at the grid
= 2 f where f is the current forcing frequency.
i= –1
Main Index
408 MSC Nastran Quick Reference Guide
Grid Point Force Output Request
GPFORCE Calculations
Depending on the element type, GEVAL is determined from a MATi entry or a PROPERTY entry.
For elements referring to extended damping on MAT2 or MAT9 entries, GEVAL=1.0 and the
KELM4 contains the cumulative results.
When frequency dependent material or properties are evoked, when a frequency is between master
frequencies the element forces will be interpolated based on MFREQUENCY case control,
LINEAR or LOG10.
Main Index
CHAPTER 5 409
Grid Point Force Output Request
GPFORCE Calculations
The various loads appear in the SOURCE column of the GPFORCE output as:
ELEMENT Corresponds to F the standard elastic force contribution at the grid.
NAME
F-OF-G Corresponds to FG the global damping force contribution at the grid.
F-OF-GE Corresponds to FGE the structural damping force contribution at the grid.
F-OF-B Corresponds to FB the viscous damping force contribution at the grid.
F-OF-M Corresponds to FM the inertia force contribution at the grid.
Special “Elements”
GENEL Corresponds to Non-frequency dependent standard elastic force contribution
at the grid.
K2GG Corresponds to Non-frequency dependent standard elastic force contribution
at the grid.
K42GG Corresponds to Non-frequency dependent F-OF-GE at the grid.
B2GG Corresponds to Non-frequency dependent F-OF-B at the grid.
M2GG Corresponds to Non-frequency dependent F-OF-M at the grid.
The above user supplied matrices are displayed using the user supplied naming convention.
SDAMP, RSDAMP, and Rayleigh damping
F-OF-SDP Corresponds to Non-forcing frequency dependent Modal damping at the
grid. PARAM, KDAMP, 1 (Default)
F-OF-K4D Corresponds to Non-forcing frequency dependent Modal damping at the
grid. PARAM, KDAMP, -1
F-OF-RAY Corresponds to Non-forcing frequency dependent Rayleigh damping at the
grid.
GEFACT (see Bulk Data entry DAMPING, default=1.0) effect appears as a scaling to F-OF-GE
F-OF-SDP, F-OF-K4D, and F-OF-RAY output is controlled by the appearance of the
GPFORCE key words: GE, DAMP or ALLDLDS.
Segment to Segment Contact
F-OF-S2C Corresponds to Non-frequency dependent segment to segment contact.
F-OF-GS2 Corresponds to Non-frequency dependent segment to segment contact global
damping.
F-OF-S2C and F-OF-GS2 output is controlled by the appearance of the GPFORCE key words:
ALLDLDS.
The remaining source entries: APP-LOAD, F-OF-SPC, F-OF-MPC remain the same as in statics.
Main Index
410 MSC Nastran Quick Reference Guide
Grid Point Kinetic Energy Output Request
GPKE (Case) Grid Point Kinetic Energy Output Request
Requests the output of the kinetic energy at selected grid points in normal modes analysis only.
Format:
ALL
PRINT
GPKE PUNCH THRESH = e = n
NOPRINT
NONE
Examples:
GPKE=ALL
GPKE (PRINT, PUNCH)=19
Describer Meaning
PRINT The printer will be the output medium.
NOPRINT Generates, but does not print, grid point kinetic energy output.
PUNCH The punch file will be the output medium.
e Minimum energy threshold. Only energies above this value will be printed and/or punched.
ALL Grid point kinetic energy for all grid points will be output.
n Set identification number of a previously appearing SET command. Only grid points with
identification numbers that appear on this SET command will be included in output
(Integer > 0).
NONE Grid point kinetic energy for no points will be output.
Remarks:
1. Grid point kinetic energy is only available for normal modes analysis.
2. Both PRINT and PUNCH may be requested.
3. GPKE=NONE overrides an overall output request.
4. For models using the lumped mass formulation, the grid point kinetic energy can be used to examine
the distribution of kinetic energy among the grid points. It is computed as:
mass mass
Ek = g M gg g
g
mass
where g represents the mass-normalized eigenvectors so that the total grid point kinetic energy
is scaled to be unity. Note that the operator indicates term-wise matrix multiplication.
Main Index
CHAPTER 5 411
Grid Point Kinetic Energy Output Request
5. The grid point kinetic energy output has limited meaning for a coupled mass formulation. Since this
mass formulation produces a coupling of mass across grid points, the sharing of kinetic energy among
grid points can occur. In general, this obscures the meaning of the computation as a means of
identifying important model parameters to control modal behavior.
Main Index
412 MSC Nastran Quick Reference Guide
Composites Ply Results Sorted Output
GPRSORT (Case) Composites Ply Results Sorted Output
Request sorted output of composites ply results (stress, strain, and failure indices) by global ply ID for a given
element set.
Format:
ALL
GPRSORT =
n
Examples:
GPRSORT=ALL
GPRSORT=22
Describer Meaning
ALL All composite elements referencing a PCOMPG property entry type. See Remarks
1. and 2.
n Set identification number of a previously appearing SET command.
Remarks:
1. Composite element output will be sorted by global ply ID and element ID. Note that this sorted
output is only available for composite elements referencing a PCOMPG property entry. Global ply
IDs can only be specified on the PCOMPG entry.
2. Composite elements referencing the PCOMP property entry will be excluded from the sorted output.
Main Index
CHAPTER 5 413
Grid Point Stress Discontinuity Output Request
GPSDCON (Case) Grid Point Stress Discontinuity Output Request
Requests mesh stress discontinuities based on grid point stresses.
Format:
GPSDCON PRINT, PUNCH = ALL
PLOT n
Examples:
GPSDCON=ALL
GPSDCON=19
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Stress discontinuity requests for all SURFACE and VOLUME commands defined
in the OUTPUT(POST) Section will be output.
n Set identification number of a previously appearing SET command. Only surfaces
and volumes with identification numbers that appear on this SET command will
be included in the stress discontinuity output request (Integer > 0).
NONE No grid point stress discontinuity output.
Remarks:
1. This output is available in linear static analysis SOLs 101 and 144 only. Output will be presented for
each surface or volume as a tabular listing of stress discontinuities for each subcase.
2. Only elements used to define the surface or volume are output. See the description of the SURFACE
or VOLUME commands.
3. Element stress output (STRESS) must be requested for elements referenced on SURFACE and
VOLUME commands. Also, the GPSTRESS and STRFIELD commands must be present for
printed output.
Main Index
414 MSC Nastran Quick Reference Guide
Grid Point Strain Output Request
GPSTRAIN (Case) Grid Point Strain Output Request
Requests grid point strains.
Format:
ALL
PRINT, PUNCH
GPSTRAIN = n
PLOT
NONE
Examples:
GPSTRAIN=ALL
GPSTRAIN=19
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Grid point strain requests for all SURFACE and VOLUME commands defined in
the OUTPUT(POST) Section will be output.
n Set identification number of a previously appearing SET command. Only surfaces
and volumes with identification numbers that appear on this SET command will
be included in the grid point strain output request (Integer > 0).
NONE No grid point strain output.
Remarks:
1. For statics, normal modes, and transient analysis, output will be presented for each surface or volume
as a tabular listing of grid point strains for each load, eigenvalue, and time step. (See Remark 1 under
DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.)
2. Only grid points connected to elements used to define the surface or volume are output. See the
description of the SURFACE or VOLUME commands.
3. Element strain output (STRAIN) must be requested for elements referenced on SURFACE and
VOLUME commands.
Main Index
CHAPTER 5 415
Grid Point Strain Output Request
4. In nonlinear transient analysis, grid point strains are computed only if parameter LGDISP is -1,
which is the default, and only for elements with linear material properties.
5. For the postprocessing of grid point strains using the .xdb file or the computation of mesh strain
discontinuities, the STRFIELD command must also be specified.
Main Index
416 MSC Nastran Quick Reference Guide
Grid Point Stress Output Request
GPSTRESS (Case) Grid Point Stress Output Request
Requests grid point stresses.
Format:
ALL
PRINT, PUNCH
GPSTRESS = n
PLOT
NONE
Examples:
GPSTRESS=ALL
GPSTRESS=19
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or X X*
(blank) X X*
PUNCH X*
PLOT
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Grid point stress requests for all SURFACE and VOLUME commands defined in the
OUTPUT(POST) Section will be output.
n Set identification number of a previously appearing SET command. Only surfaces and
volumes with identification numbers that appear on this SET command will be
included in the grid point stress output request (Integer > 0).
NONE No grid point stress output.
Remarks:
1. For statics, normal modes, and transient analysis, output will be presented for each surface or volume
as a tabular listing of grid point stresses for each load, eigenvalue, and timestep. (See Remark 1 under
DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.)
2. Only grid points connected to elements used to define the surface or volume are output. See the
description of the SURFACE or VOLUME commands.
Main Index
CHAPTER 5 417
Grid Point Stress Output Request
3. Element stress output (STRESS) must be requested for elements referenced on SURFACE and
VOLUME commands.
4. For the postprocessing of grid point stresses using the .xdb file or the computation of mesh stress
discontinuities, the STRFIELD command must also be specified.
5. Grid point stress is not output for midside nodes.
Main Index
418 MSC Nastran Quick Reference Guide
Rigid Body Motion Grounding Check
GROUNDCHECK (Case) Rigid Body Motion Grounding Check
Perform grounding check analysis on the stiffness matrix to expose unintentional constraints by moving the
model rigidly.
Format:
( PRINT PUNCH, SET = ( G, N, N + AUTOSPC, F, A )
NOPRINT ALL
GROUNDCHECK GRID = gid, THRESH = e
DATAREC = YES RTHRESH = r )
NO
= YES
NO
Examples:
GROUNDCHECK=YES
GROUNDCHECK(GRID=12,SET=(G,N,A),THRESH=1.E-5,DATAREC=YES)=YES
Describer Meaning
PRINT Write output to the print file. (Default)
NOPRINT Do not write output to the print file.
PUNCH Write output to the punch file.
SET Selects degree-of-freedom set(s) (Default: SET=G).
gid Reference grid point for the calculation of the rigid body motion.
e Maximum strain energy which passes the check. The default value is computed
by dividing the largest term in the stiffness matrix by 1.E10.
DATAREC Requests data recovery of grounding forces (Default: DATAREC=NO).
r Grounding forces which are larger than r percent of the largest grounding force
will be printed if DATAREC=YES (Default = .10; 0. < r < 1.0).
Remarks:
1. GROUNDCHECK must be specified above the subcase level.
2. SET=N+AUTOSPC (check the N-set stiffness, including the effect of PARAM,AUTOSPC) uses the
stiffness matrix for the n-set, with the rows corresponding to degrees-of-freedom constrained by the
PARAM,AUTOSPC operation zeroed out. If AUTOSPC was not performed, then this check is
redundant with respect to SET=N.
Main Index
CHAPTER 5 419
Rigid Body Motion Grounding Check
3. If DATAREC=YES, GROUNDCHECK FORCES will be printed in the displacement coordinate
system of the associated GRID points.
4. For CBEAM/CBEAM3, it is recommended to use SPOINT ID for warping DOFs. Use of GRID ID
for warping DOFs may cause one or more directions to fail the rigid body check.
5. If Lagrange multipliers are present via RIGID=LAGRAN or LGELIM then for degree-of-freedom
sets N, N+AUTOSPC, F, and A the check will be performed on degree-of-freedom sets NL,
NL+AUTOSPC, FL, and AL. The output will also be labeled accordingly.
Main Index
420 MSC Nastran Quick Reference Guide
Aerodynamic Gust Load Requests
GUST (Case) Aerodynamic Gust Load Requests
Selects the gust field in an aeroelastic response problem.
Format:
GUST=n
Example:
GUST=73
Describer Meaning
n Set identification of a GUST Bulk Data entry (Integer > 0).
Remark:
1. The choice of transient or frequency response GUST depends upon the type of TLOAD or RLOAD
referenced on the selected GUST entry.
Main Index
CHAPTER 5 421
Eigenvector Output Request in SOLs 200 and 400
GVECTOR (Case) Eigenvector Output Request in SOLs 200 and 400
Requests the form and type of eigenvector output in SOLs 200 and 400. For other solutions use
DISPLACEMENT (Case)
Format:
ALL
PRINT,PUNCH
GVECTOR( ) = n
PLOT
NONE
Examples:
GVECTOR=ALL
GVECTOR(PUNCH)=NONE
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Eigenvectors for all points will be output.
NONE Eigenvectors for no points will be output.
n Set identification of a previously appearing SET command. Only displacements
of points with identification numbers that appear on this SET command will be
output (Integer > 0).
Remarks:
1. GVECTOR=NONE overrides an overall output request.
2. Output will be presented as a tabular listing of grid points for each eigenvector.
3. GVECTOR is intended to specified in subcases with ANALYSIS=MFREQ, MTRAN, MCEIG,
FLUTTER, and SAERO.
Main Index
422 MSC Nastran Quick Reference Guide
Mesh Adaptivity Activation and Control
HADAPT (Case) Mesh Adaptivity Activation and Control
Specifies Mesh adaptivity control parameters in SOLs 101 and 400.
Note that HADAPT is not supported in NLPERF SOL 400.
Format:
HADAPT=N
Example:
HADAPT=1
Describer Meaning
N Identification number for a HADAPTL Bulk Data entry (Integer > 0).
Remarks:
1. The HADAPT command can be used only in SOL 101 or SOL 400 with ANALYSIS=STATICS.
2. In SOL 101, with NO SUPERELEMENTS, the HADAPT command may appear either above all
SUBCASEs or within specific SUBCASEs. In the last scenario, only stresses on the solution
corresponding to the specific SUBCASE where the HADAPT command has been placed will be used
to compute error indicators should the user requests an error indicator based refinement criterion (see
Bulk Data entries, HADACRI and HADAPTL). If superelements are present, then the HADAPT command
should appear only in Residual Superelement (SE0) SUBCASE structure.
3. In SOL 400, the HADAPT command can only be placed on a Linear static structural analysis
SUBCASE (ANALYSIS=STATICS) either above all STEPS or within each single STEP. All STEPs
must be Linear Static structural STEPS (ANALYSIS=STATICS). In other words an adaptive meshing
linear analysis cannot be chained with any other analysis type.
4. HADAPT remeshing should only be performed on lower order elements.
Main Index
CHAPTER 5 423
Harmonic Analysis or Printout Control
HARMONICS (Case) Harmonic Analysis or Printout Control
Controls the number of harmonics output in axisymmetric shell or axisymmetric fluid problems; controls the
number of harmonics to be used for analysis in cyclic symmetry problems.
Format for Axisymmetric Problems:
ALL
HARMONICS = NONE
h
Format for Cyclic Symmetric Problems:
HARMONICS = ALL
n
Examples:
HARMONICS=ALL
HARMONICS=32
Describer Meaning
ALL All harmonics will be output in the case of axisymmetric shell or axisymmetric fluid
problems. All harmonics will be used for analysis in cyclic symmetry problems.
NONE No harmonics will be output. This option is not available for use in cyclic symmetry
problems.
h Available harmonics up to and including harmonic h will be output in the case of
axisymmetric shell or axisymmetric fluid problems (Integer > 0).
n Harmonics specified in SET n will be used for analysis in cyclic symmetry problems
(Integer > 0).
Remarks:
1. If no HARMONICS command is present in the Case Control Section for axisymmetric shell or fluid
problems, printed output is prepared only for the zero harmonic.
2. This command must be present in cyclic symmetry problems with HARMONICS=ALL or n;
otherwise, the program will abort without performing any analysis.
3. In cyclic symmetry analysis, n must be defined as a set of integers on a SET command.
Main Index
424 MSC Nastran Quick Reference Guide
Modules Dedicated and Appended HDF5 Output Control
HDF5DA (Case) Modules Dedicated and Appended HDF5 Output Control
This entry will allow a specific MSC Nastran Module to receive dedicated HDF5 output files. These HDF5
files may exist, i.e., from a previous Nastran run. If so, then new output will be appended. All solution
sequences which support Nastran Modules (i.e., SOLs 101, 103, 105 through 112, and 400) support the new
HDF5DA Case Control command.
Format:
0
HDF5DA = – 1
n
Example:
HDF5DA = 17
Describer Meaning
0 To enable a single comprehensive.h5 output file (for all modules together). This
is the default (same as if the HDF5DA Case Control is not present).
-1 To enable separate.h5 output files (one per each module). See Remark 3.
n Identification number of an HDF5DA Bulk Data entry, specifying module
configuration and .h5 file names. (Integer > 0)
Remarks:
1. This is only valid when MODULEs are present. It is ignored if there's no BEGIN (BULK)
MODULE.
2. This case control must be present for any dedicated HDF5 and must be above or in the first subcase
3. When HDF5DA = -1, the dedicated HDF5 output file for each module is named with job filename
along with the module ID (separated by an underscore), as shown:
Jobname_ModuleID.h5
4. For n > 0, the Bulk Data entry HDF5DA is used to identify module configuration and file names.
HDF5DA entry must be present in the primary BEGIN BULK (e.g., MODULE 0).
5. This command does not support the 'intermediate' nonlinear solution output in HDF5 files at each
solution output interval (activated by the NLOPRM OUTCTRL=INTERM).
6. If this command is not present or HDF5DA=0 is specified, then HDF5 output for all modules goes
into a single .h5 file, and its properties are controlled by the HDF5OUT bulk data entry.
7. 'MDLPRM, HDF5, value' and any of its variants are forbidden.
Main Index
CHAPTER 5 425
Heat Transfer Rate of Change of Enthalpy Output Request
HDOT (Case) Heat Transfer Rate of Change of Enthalpy Output Request
Requests form of rate of change of enthalpy vector output in transient heat transfer analysis (SOL 159).
Format:
ALL
SORT1 PRINT, PUNCH
HDOT ( ) = n
SORT2 PLOT
NONE
Example:
HDOT=5
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each time.
SORT2 Output will be presented as a tabular listing of time for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Rate of change of enthalpy for all points will be output.
NONE Rate of change of enthalpy for no points will be output.
n Set identification of previously appearing SET command. Only rates of change of
enthalpy for points with identification numbers that appear on this SET
command will be output (Integer > 0).
Remark:
1. HDOT=NONE is used to override a previous HDOT=n or HDOT=ALL command.
Main Index
426 MSC Nastran Quick Reference Guide
Harmonic Output Request in Cyclic Symmetry Problems
HOUTPUT (Case) Harmonic Output Request in Cyclic Symmetry Problems
Requests harmonic output in cyclic symmetry problems.
Format:
HOUTPUT C, S, C*, S* = ALL
K
Examples:
HOUTPUT=ALL
HOUTPUT(C,S)=5
Describer Meaning
C, S, C*, S* Harmonic coefficients. See Remark 4.
ALL All harmonics will be output.
k Set identification number of harmonics for output (Integer > 0).
Remarks:
1. Set k must be defined on a SET command, and output will be computed for all available harmonics
in SET k.
2. HOUTPUT=ALL requests output for all harmonics specified on the HARMONICS command.
3. Either the HOUTPUT or NOUTPUT command is required to obtain data recovery in cyclic
symmetry analysis.
4. C and S correspond to the cosine and sine coefficients when the STYPE field is ROT or AXI on the
CYSYM Bulk Data entry.
C, S, C*, and S* correspond to the cosine symmetric, sine symmetric, cosine antisymmetric, and sine
antisymmetric coefficients, respectively, when the STYPE field is DIH on the CYSYM Bulk Data
entry.
Main Index
CHAPTER 5 427
Elemental Heat Flow Output Request
HTFLOW (Case) Elemental Heat Flow Output Request
Requests heat flow output at selected structural elements.
Format:
HTFLOW PRINT, PUNCH = ALL
NOPRINT n
Example:
HTFLOW = ALL
HTFLOW = 15
Describer Meaning
PRINT The printer will be the output medium.
NOPRINT Generate, but do not print out, the output.
PUNCH The punch file will be the output medium.
ALL Heat flow for all structural elements will be output.
n Set identification of previously appearing SET command. Only structural
elements with identification numbers that appear on this SET command will be
included in the heat flow output (Integer > 0).
Remarks:
1. Elemental heat flow output is available for steady state thermal analysis (SOL 101 and SOL 153) and
transient thermal analysis (SOL 159).
2. Heat flow is computed from the applied heat loads and the effect of convection and radiation heat
transfer on boundary elements (CHBDYE, CHBDYG, and CHBDYP).
3. See Remarks 6.-8. of the descriptions of CHBDYE Bulk Data for the side conventions of solid
elements, shell elements, and line elements.
Main Index
428 MSC Nastran Quick Reference Guide
Transient Analysis Initial Condition Set Selection
IC (Case) Transient Analysis Initial Condition Set Selection
Selects the initial conditions for transient analysis (SOLs 109, 112, 129, 159 and 400).
Format:
PHYSICAL
IC MODAL = n
STATSUB[,DIFFK]
Examples:
IC = 10
IC(PHYSICAL) = 100
IC(MODAL) = 200
IC(STATSUB) = 1000
IC(STATSUB,DIFFK) = 2000
Describer Meaning
PHYSICAL The TIC Bulk Data entries selected by set n define initial conditions for coordinates
involving grid, scalar, and extra points (Default).
MODAL The TIC Bulk Data entries selected by set n define initial conditions for modal
coordinates and extra points. See Remark 3.
STATSUB Use the solution of the static analysis subcase n as the initial condition. See Remark 4.
DIFFK Include the effects of differential stiffness in the solution. See Remarks 4. and 5.
n For the PHYSICAL (Default) and MODAL options, n is the set identification
number of TIC Bulk Data entries for structural analysis (SOLs 109, 112 and 129) or
TEMP and TEMPD entries for heat transfer analysis (SOLs 159 and 400). For the
STATSUB option, n is the ID of a static analysis subcase (Integer > 0).
Remarks:
1. For structural analysis, TIC entries will not be used (therefore, no initial conditions) unless selected
in the Case Control Section.
2. Only the PHYSICAL option (Default) may be specified in heat transfer analysis (SOL 159 and SOL
400 ). The initial temperature of a point should be equal to its boundary temperature at time = 0. For
SOL 400 transient thermal analysis, the boundary temperature at time = 0 takes precedence over the
initial temperature if both temperatures are not identical.
3. IC(MODAL) may be specified only in modal transient analysis (SOL 112).
4. IC(STATSUB) and IC(STATSUB,DIFFK) cannot be specified together in the same run. This will
cause FATAL and stop the execution.
5. The DIFFK keyword is meaningful only when used in conjunction with the STATSUB keyword.
6. The following examples illustrate the usage of the various options of the IC Case Control command.
Main Index
CHAPTER 5 429
Transient Analysis Initial Condition Set Selection
Example (a)
$ SPECIFY INITIAL CONDITIONS FOR PHYSICAL COORDINATES
$ IN SOL 109 OR SOL 112
IC(PHYSICAL) = 100
or
IC = 100
Example (b)
$ SPECIFY INITIAL CONDITIONS FOR MODAL COORDINATES
$ IN SOL 112
IC(MODAL) = 200
Example (c)
$ SPECIFY STATIC SOLUTION AS INITIAL CONDITION
$ IN SOL 109 OR SOL 112
$ (DIFFERENTIAL STIFFNESS EFFECT NOT INCLUDED)
SUBCASE 10 $ STATIC ANALYSIS
LOAD = 100
SUBCASE 20 $ TRANSIENT ANALYSIS
IC(STATSUB) = 10 $ POINTS TO STATIC ANALYSIS SUBCASE ID
Example (d)
$ SPECIFY STATIC SOLUTION AS INITIAL CONDITION
$ IN SOL 109 OR SOL 112
$ (DIFFERENTIAL STIFFNESS EFFECT INCLUDED
SUBCASE 100 $ STATIC ANALYSIS
LOAD = 1000
SUBCASE 200 $ TRANSIENT ANALYSIS
IC(STATSUB,DIFFK) = 100 $ POINTS TO STATIC ANALYSIS SUBCASE ID
7. In thermal chaining analysis, this command will be ignored if the transient thermal analysis is not
specified as the first step of a model.
Main Index
430 MSC Nastran Quick Reference Guide
Inter-Component Forces (ICF) Output Request
ICF (Case) Inter-Component Forces (ICF) Output Request
Requests the form and type of inter-component force (ICF) vector output from an FBA job.
Format:
ALL
PHYSICAL PRINT, PUNCH REAL or IMAG
ICF = n
MODAL PLOT PHASE
NONE
Examples:
ICF = 5
ICF (SORT2, PRINT, PUNCH, IMAG) = ALL
ICF (SORT2) = 20
ICF = ALL
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each frequency. See
Remarks 1. through 4.
SORT2 Output will be presented as a tabular listing of frequency for each grid point. See
Remarks 1., 3. and 5.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or X X*
(blank) X X*
PUNCH X*
PLOT
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
ALL ICFs for all points will be output. See Remarks 1. through 5.
Main Index
CHAPTER 5 431
Inter-Component Forces (ICF) Output Request
Describer Meaning
n Set identification of a previously appearing SET command. Only ICFs for points with
identification numbers that appear on this SET command will be output (Integer > 0).
See Remarks 1. through 6.
NONE ICFs for no points will be output.
Remarks:
1. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2. In the SORT1
format, only nonzero values will be output.
2. In SORT1 format, ICFs recovered at consecutively numbered scalar points are printed in groups of
six (sextets) per line of output. However, if a scalar point is not consecutively numbered, it will begin
a new sextet on a new line of output. If a sextet can be formed and all values are zero, then the line
will not be printed. If a sextet cannot be formed, then zero values may be output.
3. ICFs are defined only for the connection points of FRF components in an FBA job and are regarded
as null for non-connection points of FRF components. Therefore, ICF output is meaningful only for
the connection points of FRF components in an FBA job.
4. In SORT1 format, ICF output is ignored for non-connection points and will be output for the
requested connection points of FRF components only if their ICFs are non-null.
5. In SORT2 format, ICF output is honored for all requested connection and non-connection points
of FRF components even if their ICFs are null.
6. ICF output request is ignored for undefined points.
Main Index
432 MSC Nastran Quick Reference Guide
Select Geometric Imperfection
IMPERFECT (Case) Select Geometric Imperfection
Select geometric imperfection cases in SOL 400.
Note that IMPERFECT is not supported in NLPERF SOL 400.
Format:
IMPERFECT = n
Example:
IMPERFECT = 5
Describer Meaning
n Identification number of an IMPGEOM or IMPCASE bulk data entry.
Remark:
1. This command must be above all subcases.
Main Index
CHAPTER 5 433
Insert External File
INCLUDE (Case) Insert External File
Inserts an external file into the input file. The INCLUDE statement may appear anywhere within the input
data file.
Format:
INCLUDE ’filename’
Example:
The following INCLUDE statement is used to obtain the Bulk Data from another file called
MYCASE.DATA:
SOL 101
CEND
TITLE = STATIC ANALYSIS
LOAD = 100
INCLUDE ’MYCASE.DATA’
BEGIN BULK
ENDDATA
Describer Meaning
filename Physical filename of the external file to be inserted. The user must supply the
name according to installation or machine requirements. It is recommended that
the filename be enclosed by single right-hand quotation marks ( ’).
Remarks:
1. INCLUDE statements may be nested; that is, INCLUDE statements may appear inside the external
file. The nested depth level must not be greater than 10.
2. The total length of any line in an INCLUDE statement must not exceed 72 characters. Long file
names may be split across multiple lines. For example, the file:
/dir123/dir456/dir789/filename.dat
may be included with the following input:
INCLUDE ‘/dir123
/dir456
/dir789/filename.dat’
3. See the for more examples.
Main Index
434 MSC Nastran Quick Reference Guide
Acoustic Intensity Output Request
INTENSITY (Case) Acoustic Intensity Output Request
Requests output of acoustic intensity on wetted surface. SOLs 108 and 111 or SOL 200 with
ANALYSIS = DFREQ or MFREQ.
Format:
ALL
INTENSITY SORT1 PRINT,PUNCH = n
SORT2 PLOT
NONE
Describer Meaning
SORT1 Output will be presented as tabular listing of grid points for each excitation frequency
(Default).
SORT2 Output will be presented as tabular listing of excitation frequencies for each grid
point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Intensities will be computed for all grid points of the wetted surface.
n Set identification of a previously defined set of grid points. Intensities will be
computed for the grid points in this set only.
NONE Acoustic intensities will not be processed.
Remarks:
1. INTENSITY = NONE overrides an overall request.
2. This Case Control command can be used in SOL 108 and SOL 111 only.
Main Index
CHAPTER 5 435
Nonlinear Inertia Relief Selection (SOL 400 only)
IRLOAD (Case) Nonlinear Inertia Relief Selection (SOL 400 only)
Selects nonlinear inertia relief set for SOL 400.
Note that IRLOAD is not supported in NLPERF SOL 400.
Format: IRLOAD= QLINEAR
NONE
Example:
IRLOAD=QLINEAR
Describer Meaning
QLINEAR Inertia Load Calculation with small displacement (Quasi-Linear) is activated in SOL
400.
NONE No Inertia Relief (Default)
Remark:
1. This command is active only in SOL 400 with ANALYSIS=NLSTATIC and its use requires a set of
STATIC supports that constrain all six rigid body motions.
2. IRLOAD=QLINEAR, which has to be applied above to all SUBCASES, is a global case control
command and activates the inertia load calculations in SOL 400 for all applied static loads. In
nonlinear static analyses (ANALYSIS=NLSTAT), it also activates the inertia relief analysis with small
displacement. When IRLOAD=QLINEAR with large displacement (PARAM,LGDISP,1), a fatal
error message will be issued. Also superelements in conjunction with IRLOAD=QLINEAR will cause
a fatal error.
IRLOAD=NONE (default) deactivates the inertia load calculations.
3. IRLOAD=QLINEAR is ignored by perturbation analyses in SOL 400.
Main Index
436 MSC Nastran Quick Reference Guide
Direct Input Stiffness Matrix Selection
K2GG (Case) Direct Input Stiffness Matrix Selection
Selects direct input stiffness matrix or matrices.
Format:
K2GG=name
Example:
K2GG = KDMIG
K2GG = KDMIG1, KDMIG2, KDMIG3
K2GG = 1.25*KDMIG1, 1.0*KDMIG2, 0.82*KDMIG3
SET 100 = K2, K3, K4
K2GG = 100
Describer Meaning
2
name Name of a K gg matrix that is input on the DMIG Bulk Data entry, or name
list with or without factors. See Remark 6. (Character).
Remarks:
1. DMIG matrices will not be used unless selected.
2. Terms are added to the stiffness matrix before any constraints are applied.
3. The matrix must be symmetric and field 4 on the DMIG,name Bulk Data entry must contain the
integer 6.
4. A scale factor may be applied to this input using the PARAM, CK2 entry. See Parameters.
5. The matrices are additive if multiple matrices are referenced on the K2GG command.
6. The formats of the name list:
a. Names without factor.
Names separated by comma or blank.
b. Names with factors.
Each entry in the list consists of a factor, followed by a star, followed by a name. The entries are
separated by commas or blanks. The factors are real numbers. Each name must be paired with a
factor including 1.0.
7. If there are multiple subcases in the analysis. the K2GG command must appear above the first subcase
or in the first subcase. K2GG requests in the second and subsequent subcases will be ignored. For
superelements. it should occur in the first subcase for the appropriate superelement.
Main Index
CHAPTER 5 437
Direct Input Stiffness Matrix Selection
K2PP (Case) Direct Input Stiffness Matrix Selection
Selects direct input stiffness matrix or matrices, which are not included in normal modes.
Format:
K2PP=name
Example:
K2PP = KDMIG
K2PP = KDMIG1, KDMIG2, KDMIG3
K2PP = 5.06*KDMIG1, 1.0*KDMIG2, 0.85*KDMIG3
K2PP = (1.25, 0.5) *KDMIG1, (1.0,0.0) *KDMIG2, (0.82, -2.2) *KDMIG3
Describer Meaning
2
name Name of a K pp matrix that is input on the DMIG or DMlAX Bulk Data entry,
or name list with or without factors. See Remark 6.
Remarks:
1. DMIG and DMIAX entries will not be used unless selected by the K2PP command.
2. The matrix must be square or symmetric, and field 4 on the DMIG,name Bulk Data entry must
contain a 1 or 6.
3. It is recommended that PARAM,AUTOSPC,NO be specified. See the Constraint and Mechanism
Problem Identification in SubDMAP SEKR in the MSC Nastran Reference Guide.
4. K2PP matrices are used only in dynamic response problems. They are not used in normal modes.
5. The matrices are additive if multiple matrices are referenced on the K2PP Case Control command.
6. The formats of the name list:
a. Names without factor
Names separated by comma or blank.
b. Names with factors.
Each entry in the list consists of a factor, followed by a star, followed by a name. The entries are
separated by commas or blanks. The factors are either all real numbers, or all complex numbers
in the form of two real numbers separated by a comma, within parentheses, as shown in the
preceding example. The first real number of the pair is the real part, and the second is the
imaginary part. Either part may be zero or blank, but not both. Mixed real numbers and complex
numbers are not allowed. Each name must be paired with a factor including 1.0 for real and (1.0,
0.0) for complex.
Main Index
438 MSC Nastran Quick Reference Guide
Direct Input Stiffness Element Damping Selection
K42GG (Case) Direct Input Stiffness Element Damping Selection
Selects direct input structural element damping matrix or matrices.
Format:
K42GG=name
Example:
K42GG = KDMIG
K42GG = KDMIG1, KDMIG2, KDMIG3
K42GG = 2.03*KDMIG1, 0.84*KDMIG2
Describer Meaning
2
name Name of a K4 gg matrix that is input on the DMIG Bulk Data entry, or name
list with or without factors. See Remark 4.
Remarks:
1. DMIG matrices will not be used unless selected.
2. Terms are added to the structural element damping matrix before any constraints are applied.
3. The matrix must be symmetric, and field 4 on the DMIG,name Bulk Data entry must contain the
integer 6.
4. The formats of the name list:
a. Names without factor.
Names separated by comma or blank.
b. Names with factors.
Each entry in the list consists of a factor, followed by a star, followed by a name. The entries are
separated by commas or blanks. The factors are real numbers. Each name must be paired with a
factor including 1.0.
5. If there are multiple subcases in the analysis. the K42GG command must appear above the first
subcase or in the first subcase. K42GG requests in the second and subsequent subcases will be
ignored. For superelements. it should occur in the first subcase for the appropriate superelement.
Main Index
CHAPTER 5 439
Output Label
LABEL (Case) Output Label
Defines a character string that will appear on the third heading line of each page of printer output.
Format:
LABEL=label
Example:
LABEL=DEMONSTRATION PROBLEM
Describer Meaning
label Any character string.
Remarks:
1. LABEL appearing at the subcase level will label output for that subcase only.
2. LABEL appearing before all subcases will label any outputs that are not subcase-dependent.
3. If no LABEL command is supplied, the label line will be blank.
4. LABEL information is also placed on plotter output, as applicable. Only the first 65 characters will
appear.
Main Index
440 MSC Nastran Quick Reference Guide
Label assigned to a subcase (static load case) in the external superelement creation run
LDLABEL (Case) Label assigned to a subcase (static load case) in the external superelement creation
run
Assigns a character string to an external superelement creation run's subcase in order to identify the static load
in the assembly run.
Format:
LDLABEL [=load_label]
Example:
LDLABEL
LDLABEL=GRAVITY LOAD ON THE OUTBOARD NACELLE
Describer Meaning
load_label Any character string.
Remarks:
1. The LDLABEL command is used only when the EXTSEOUT command is specified.
2. If the LDLABEL is specified in any subcase but not all subcases then the following defaults will be
applied to those subcases without LDLABEL in the following order:
a. LABEL inside the subcase
b. If no LABEL, then SUBTITLE inside the subcase
c. If no SUBTITLE, then TITLE inside the subcase
If it is desired that the default logic is to be applied to all subcases then specify LDLABEL with no
argument above all subcases.
3. If the same load_label is specified in more than one SUBCASE then a User Warning Message will be
issued.
4. Load_label may be referenced on the SELOAD Bulk Data entry.
Main Index
CHAPTER 5 441
Maximum Lines Per Printed Page
LINE (Case) Maximum Lines Per Printed Page
Defines the maximum number of output lines per printed page.
Format:
LINE=n
Example:
LINE=35
Describer Meaning
n Maximum number of output lines per page (Integer > 0; Default = 50).
Remarks:
1. For 11 inch paper, 50 lines per page is recommended; for 8-1/2 inch paper, 35 lines per page is
recommended.
2. The NASTRAN statement keyword NLINES may also be used to set this value. See the NLINES (9)
Nastran Statement.
Main Index
442 MSC Nastran Quick Reference Guide
External Static Load Set Selection
LOAD (Case) External Static Load Set Selection
Selects an external static load set.
Format:
LOAD=n
Example:
LOAD=15
Describer Meaning
n Set identification of at least one external load Bulk Data entry. The set
identification must appear on at least one ACCEL, ACCEL1, FORCE, FORCE1,
FORCE2, FORCEAX, GRAV, LOAD, MOMAX, MOMENT, MOMENT1,
MOMENT2, MPCD, PLOAD, PLOAD1, PLOAD2, PLOAD4, PLOADB3,
PLOADX, QVOL, QVECT, QHBDY, QBDY1, QBDY2, QBDY3, PRESAX,
RFORCE, SPCD, or SLOAD entry (Integer > 0).
Remarks:
1. A GRAV entry cannot have the same set identification number as any of the other loading entry types.
Apply a gravity load along with other static loads, a LOAD Bulk Data entry must be used.
2. LOAD is only applicable in linear and nonlinear statics, inertia relief, differential stiffness, buckling,
and heat transfer analyses.
3. The total load applied will be the sum of external (LOAD), thermal (TEMP(LOAD)), element
deformation (DEFORM), and constrained displacement (SPC) loads.
4. Static, thermal, and element deformation loads should have unique set identification numbers.
Main Index
CHAPTER 5 443
Name to be Associated with a SUBCASE in PAA
LOADNAME (Case) Name to be Associated with a SUBCASE in PAA
Provides a name to be associated with a loading condition.
Format:
LOADNAME = load_name
Example:
LOADNAME = GRAVITY LOAD ON OUTBOARD NACELLEL
Describer Meaning
Load_name Character string (up to 64 characters long) providing a user-defined name for a
loading in PAA.
Remark:
1. This command is used only in PAA and provides a user-defined name for a loading condition.
2. LOADNAMEs may be used to combine loads in a COMBINE or SOLVE PAA run using a
LOADCNAM Bulk Data entry.
3. The LOADNAME command is ignored in non-PAA applications
Main Index
444 MSC Nastran Quick Reference Guide
Static Load Set Selection
LOADSET (Case) Static Load Set Selection
Selects a sequence of static load sets to be applied to the structural model. The load sets may be referenced by
dynamic load commands.
Format:
LOADSET=n
Example:
LOADSET=100
Describer Meaning
n Set identification number of at least one LSEQ Bulk Data entry. (Integer > 0)
Remarks:
1. When used in superelement analysis, this command must be used for all superelements. The number
of static load vectors created for each superelement depends upon the type of analysis. In static
analysis, the number of vectors created is equal to the number of unique EXCITEIDs on all LSEQ
entries in the Bulk Data; in dynamic analysis, the number of vectors created is equal to the number
of unique EXCITEIDs on all RLOAD1, RLOAD2, TLOAD1, TLOAD2 and ACSRCE entries in
the Bulk Data.
2. When the LOADSET command is used in superelement statics, the residual structure should have as
many loading conditions as the number of unique EXCITEID sets defined on all LSEQ entries. The
subcases after the first should contain only SUBTITLE and LABEL information, and residual
structure output requests. SUBTITLE and LABEL information for all superelements will be obtained
from the residual structure.
3. When multiple subcases are specified in the dynamic solution sequences (SOLs 108, 109, 111, 112,
118, 146), the LOADSET must appear in the first subcase or above all subcases. In SOL 200 with
ANALYSIS=DFREQ, MFREQ, or MTRAN, a different LOADSET may be specified in the first
subcase pertaining to each ANALYSIS command.
4. In SOL 101, the design sensitivity output will identify all expanded subcases by a sequence of unique
integers beginning with n.
5. In the nonlinear static solution sequences (SOLs 106 and 153), the LOADSET must appear above
all subcases and only one LOADSET may be specified.
6. Only one LOADSET command is allowed per superelement and it must be specified in the
superelement’s first subcase.
7. It is no longer necessary to employ LOADSET/LSEQ data to specify static loading data for use in
dynamic analysis. In the absence of a LOADSET Case Control command, all static loads whose load
set IDs match the EXCITEIDs on all RLOAD1, RLOAD2, TLOAD1, TLOAD2, and ACSRCE
Bulk Data entries are automatically processed.
Main Index
CHAPTER 5 445
Static Load Set Selection
8. . If you use the LOADSET command in a static analysis, the loading matrix will be generated
corresponding to, and in ascending order of, the EXCITEID's on the referenced LSEQ entries. Any
LOAD commands within subcases will be ignored.
9. Use of the LOADSET/LSEQ should be avoided as it is an obsolete entry and is never needed and is
only documented for legacy code. Some new features such as SUBSTEP do not support it and will
issue a fatal message.
Main Index
446 MSC Nastran Quick Reference Guide
Direct Input Mass Matrix Selection
M2GG (Case) Direct Input Mass Matrix Selection
Selects direct input mass matrix or matrices.
Format:
M2GG=name
Example:
M2GG = MDMIG
M2GG = MDMIG1, MDMIG2, MDMIG3
M2GG = 1.25*MDMIG1, 1.0*MDMIG2, 0.82*MDMIG3
SET 200 = M1, M2
M2GG = 200
Describer Meaning
2
name Name of a M gg matrix that is input on the DMIG Bulk Data entry, or name
list with or without factors see Remark 6. (Character).
Remarks:
1. DMIG matrices will not be used unless selected.
2. Terms are added to the mass matrix before any constraints are applied.
3. The matrix must be symmetric, and field 4 on the DMIG, name entry must contain a 6.
4. M2GG input is not affected by PARAM,WTMASS. M2GG input must either be in consistent mass
units or PARAM,CM2 may be used.
5. The matrices are additive if multiple matrices are referenced on the M2GG command.
6. The formats of the name list:
a. Names without factor.
Names separated by comma or blank.
b. Names with factors.
Each entry in the list consists of a factor, followed by a star, followed by a name. The entries are
separated by commas or blanks. The factors are real numbers. Each name must be paired with a
factor including 1.0.
7. If there are multiple subcases in the analysis. the M2GG command must appear above the first
subcase or in the first subcase. M2GG requests in the second and subsequent subcases will be ignored.
For superelements. it should occur in the first subcase for the appropriate superelement.
Main Index
CHAPTER 5 447
Direct Input Mass Matrix Selection
M2PP (Case) Direct Input Mass Matrix Selection
Selects direct input mass matrix or matrices, which are not included in normal modes.
Format:
M2PP=name
Example:
M2PP = MDMIG
M2PP = MDMIG1, MDMIG2, MDMIG3
M2PP = 5.06*MDMIG1, 1.0*MDMIG2, 0.85*MDMIG3
M2PP = (1.25, 0.5) *MDMIG1, (1.0, 0.0) *MDMIG2, (0.82, -2.2) *MDMIG3
Describer Meaning
2
name Name of a M pp matrix that is input on the DMIG or DMIAX Bulk Data
entry, or name list with or without factors, see Remark 7. (Character).
Remarks:
1. DMIG and DMIAX entries will not be used unless selected by the M2PP input.
2. M2PP input is not affected by PARAM,WTMASS. M2PP input must be in consistent mass units.
3. The matrix must be square or symmetric, and field 4 on the DMIG, name entry must contain a 1 or 6.
4. It is recommended that PARAM,AUTOSPC,NO be specified. See Constraint and Mechanism Problem
Identification in SubDMAP SEKR in the MSC Nastran Reference Guide.
5. M2PP matrices are used only in dynamic response problems. They are not used in normal modes
problems.
6. The matrices are additive if multiple matrices are referenced on the M2PP command.
7. The formats of the name list:
a. Names without factor
Names separated by comma or blank.
b. Names with factors.
Each entry in the list consists of a factors followed by a star, followed by a name. The entries are
separated by commas or blanks. The factors are either all real numbers, or all complex numbers
in the form of two real numbers, separated by a comma, within parenthesis as shown in the
preceding example. The first real number of the pair is the real part, and the second is
the imaginary part. Either part may be zero or blank, but not both. Mixed real numbers and
complex numbers are not allowed. Each name must be with a factor including 1.0 for real and
(1.0, 0.0) for complex.
Main Index
448 MSC Nastran Quick Reference Guide
Perform mode mapping between two runs
MAPMODES (Case) Perform mode mapping between two runs
Instructs MSC Nastran to either write the modes from the current run to an op2 file or map the modes from
the current run to those from a prior run.
Format:
BASELINE
MAPMODES = UNITNO
MAPPING
Example:
MAPMODES(BASELINE) = 50
MAPMODES(MAPPING) = 51
Describer Meaning
BASELINE The current run is a baseline run and the modes from this run will be written using
OUTPUT2 to UNITNO.
MAPPING The current run will perform mode-mapping using the modes written using
OUTPUT2 to UNITNO in a previous run.
UNITNO Unit number of an OUTPUT2 or INPUTT2 file assigned to the current run.
Remarks:
1. Mode mapping is performed in two steps. In the initial (BASELINE) run, the mode shapes and
eigenvalue table are written to an OUTPUT2 file. Otherwise, processing in the baseline run is
unchanged, except that the CLEANVEC parameter is automatically set to YES to make the
eigenvectors from repeated roots 'clean' and repeatable.
2. In the second step, the eigenvalue problem is solved, then the baseline modes are read in from
UNITNO and cross-orthogonality is used to map the new modes into the same order as the baseline
modes. Once again the CLEANVEC parameter is set to YES in this run to make the eigenvectors for
repeated roots 'clean'.
3. Two parameters are used in the cross-orthogonality, MINORTHO (default=0.9) and MINORTHR
(default = 0.7). These are the criteria used in the mode-mapping. In the original modes, the cross-
orthogonality between a baseline mode and new mode must be greater than or equal to
MINORTHO in order for the mapping to occur. Residual vectors are not real modes, so the cross-
orthogonality requirement on those is MINORTHR.
4. If the mode mapping fails, the run will terminate with a fatal message containing the values of cross
orthogonality calculated which could help guide MINORTHO and MINORTHR parameters
choices.
Main Index
CHAPTER 5 449
Perform mode mapping between two runs
5. If the mode mapping succeeds, an additional eigenvalue summary table will be printed with the
subheading AFTER MODE MAPPING HAS BEEN PERFORMED. In this table, the MODE NO
is the mode number in the baseline run and the EXTRACTION ORDER is the mode number in the
mapping run. Note that the natural frequencies of the modes may not be in ascending order, as it is
possible that the mode order may change with model changes.
Main Index
450 MSC Nastran Quick Reference Guide
Mass Combination Selection
MASSSET (Case) Mass Combination Selection
Selection of a mass combination in multiple mass combination analysis (MMC). This case control
command can be used in various solutions sequences SOLs 101, 103, 107-112, 144-146, 200 and 400.
Format:
MASSSET = n
Example:
MASSSET = 11
Describer Meaning
n Set ID of a MASSSET bulk data entry (Integer > 0).
Remarks:
1. Using a particular mass combination in analysis only requires referencing the mass combinations ID
in MASSSET case control at the subcase level (or at step level in Sol 400). If no MASSSET is defined
in the subcase then (like traditional non MMC analysis) the base mass is used as the mass for that
subcase. Example for selecting mass combinations at the subcase level:
SUBCASE 101
...
MASSSET = 11 $
...
SUBCASE 102
...
MASSSET = 12 $
2. The MASSSET bulk data entry defines a linear combination of incremental/base mass cases to form
the subcase-dependent mass. The bulk data for the incremental mass case is preceded by “BEGIN
MASSID=yyy”, where yyy > 0 is the integer ID of the mass increment case. The only data that will
be used from the incremental mass bulk data section is element connections and element mass
properties including materials (Parameters and grid data included in the incremental mass section will
be ignored). The incremental mass will be computed based on the grid data supplied in the base mass
bulk data section and the element properties supplied in the incremental mass section. Typically the
user will construct the incremental mass by adding concentrated masses (e.g. CONM2, CMASS1
etc.) or by changing the material or element properties of the set of elements defined in incremental
mass bulk data section.
BEGIN massid=101 label='mass increment using conm2s'
BEGIN massid=102 label='mass increment using materials'
3. If Part SE are used in the model, mass increment related to these SEs can be specified in a separate
bulk data section, “BEGIN SUPER=zzz MASSID=yyy”, where zzz > 0 is the Superelement ID and
yyy is the mass increment ID.
BEGIN SUPER=2 massid=101 label='mass increment using conm2s'
Main Index
CHAPTER 5 451
Redefine the MASTER Subcase
MASTER (Case) Redefine the MASTER Subcase
Allows the redefinition of a MASTER subcase.
Format:
SUBCASE n
MASTER
Example:
SUBCASE 10
MASTER
Describer Meaning
n
Remarks:
1. All commands in a MASTER subcase apply to the following subcases until a new MASTER subcase
is defined.
2. Suppose that superelement 10 has SPC set 10, MPC set 10, and LOAD sets 101 and 102. Suppose
also that superelement 20 has SPC set 20, MPC set 20, and LOAD sets 201 and 202. Then the
following Case Control setup specifies the required subcase structure:
TITLE = MY MODEL
DISP = ALL
SEALL = ALL
SUBCASE 101
MASTER
SPC = 10
MPC = 10
SUPER = 10, 1
LOAD = 101
LABEL = SUPER 10
ESE = ALL
SUBCASE 102
LOAD = 102
SUPER = 10, 2
SUBCASE 201
MASTER
SPC = 20
MPC = 20
SUPER = 20, 1
LOAD = 201
LABEL = SUPER 20
SUBCASE 202
LOAD = 202
SUPER = 20, 2
Main Index
452 MSC Nastran Quick Reference Guide
Redefine the MASTER Subcase
3. MASTER may also be used advantageously in multiple boundary condition Case Control setups.
Suppose that constraint sets 10 and 20 are to be solved with three loading conditions each: 1, 2, and
3; and 4, 5, and 6, respectively. The following Case Control Section may be used:
TITLE = MULTIPLE BOUNDARY CONDITIONS
DISP = ALL
SYM 1
MASTER
SPC = 10
LOAD = 1
SYM 2
LOAD = 2
SYM 3
LOAD = 3
SYM 4
MASTER
SPC = 20
LOAD = 4
SYM 5
LOAD = 5
SYM 6
LOAD = 6
SYMCOM 10
SYMSEQ = 1., 1., 1., -1., -1., -1.
SYMCOM 20
SYMSEQ = -1., -1., -1., 1., 1., 1.
4. The MASTER command must appear immediately after a SUBCASE or SYM command.
Main Index
CHAPTER 5 453
Maximum Number of Output Lines
MAXLINES (Case) Maximum Number of Output Lines
Sets the maximum number of output lines.
Format:
MAXLINES=n
Example:
MAXLINES=150000
Describer Meaning
n Maximum number of output lines allowed (Integer > 0; Default = 999999999).
Remarks:
1. If MAXLINES is exceeded, the program will terminate.
2. MAXLINES may also be specified on the NASTRAN statement with SYSTEM(14). See the MAXLINES
(14).
3. The code counts the number of pages and assumes that the number of lines output is the number of
lines allowed per page, specified by the “LINES” command, times the number of pages.
Main Index
454 MSC Nastran Quick Reference Guide
MAXMIN Survey Output Request (old form)
MAXMIN (Case) MAXMIN Survey Output Request (old form)
Specifies options for max/min surveys of certain output data associated with grid points.
Format:
MAX
GLOBAL ALL
BOTH
MAXMIN = num CID = BASIC oplist,COMP = list = n
MIN
VMAG cid NONE
Example:
MAXMIN (BOTH=10,CID=1000,DISP,COMP=T1/T3)=501
Describer Meaning
MAX Specifies that only maximum values are to be output. See Remark 1.
MIN Specifies that only minimum values are to be output. See Remark 1.
BOTH Specifies that both maximum and minimum values are to be output. See Remark
1.
VMAG Specifies that vector magnitude resultants are to be output. See Remark 2.
num Specifies the maximum number of values that will be output. See Remark 3.
(Integer > 0, Default = 5).
CID Specifies the coordinate system frame of reference in which the max/min values
will be output. See Remarks 1. and 3.
GLOBAL Requests output in the global coordinate system frame of reference.
BASIC Requests output in the basic coordinate system frame of reference.
cid Requests output in the local coordinate system defined by cid (Integer > 0).
oplist Specifies a list of one or more standard Case Control commands for which
max/min results are to be produced. The list may include any of DISP,SPCF,
OLOAD,MPCF,VELO,ACCE, or ALL. See Remark 6 (Character, no Default).
list Specifies a list of grid point degree of freedom component directions that will be
included in the max/min survey output. The components are separated by slashes
and are selected from T1, T2, T3, R1, R2, and R3. See Remarks 4. and 5.
(Character, Default=/T1/T2/T3/R1/R2/R3).
ALL MAXMIN survey results for all points will be output.
NONE MAXMIN survey results for no points will be output.
n Set identification of a previously appearing SET command. The max/min results
survey will be output only for the points specified SET n (Integer > 0).
Main Index
CHAPTER 5 455
MAXMIN Survey Output Request (old form)
Remarks:
1. The MAXMIN command produces an algebraically ascending sorted list of the output quantities
specified for all of the points in the selected set. MAX refers to the largest magnitude positive values,
while MIN refers to the largest magnitude negative values. The output format is similar to that of
displacement output. All components will be output for a grid point, and the order of the grid points
will be in sort on the particular component that was surveyed. The output title contains the
identification number of the set of points participating in the max/min output, the coordinate system
frame of reference, the number of MAX and MIN values output, and the component that was
surveyed. When the output being surveyed is in the global output coordinate system reference frame,
and BASIC or a local output coordinate system is specified as cid, both the sorted system output and
the original reference system output are displayed for the grid point if these systems are different.
2. Vector magnitude results are computed for both translations and rotations and are displayed under
the T1 and R1 column headings. The presence of the COMP keyword is ignored.
3. The default value of 5 generates a minimum of 10 output lines for the BOTH option. There will be
5 maximum values and 5 minimum values produced. In addition, if coordinate system are involved,
both surveyed and original data will be output. This could result in as many as 10 more lines of output
for each surveyed component.
4. Multiple MAXMIN commands may be specified for a subcase. This permits different output
quantities to have different MAXMIN specification within a subcase. For example,
SET 501=1,3,5,7 THRU 99, 1001, 2001
MAXMIN (DISP, COMP=T3) = 501
MAXMIN (SPCF, COMP=T1/R3) = ALL
5. Scalar point output is included only if component T1 is included in the list.
6. MAXMIN output will only be generated for items in the oplist when there is an associated Case
Control command present. For example, a DISP Case Control command must be present in order
for the MAXMIN(DISP) = ALL command to produce output. Use of ALL keywords for the oplist
requests MAXMIN output for all output commands acceptable to MAXMIN that are present in Case
control Section.
Main Index
456 MSC Nastran Quick Reference Guide
Requests Output of Maximums and Minimums in Data Recovery (new form)
MAXMIN (Case) Requests Output of Maximums and Minimums in Data Recovery (new form)
Requests the output of maximums and minimums in data recovery.
Format:
GRID
PRINT, PUNCH VONMISES
MAXMIN ELEM
NOPRINT MAXS or SHEAR
BOTH
CENTER
ALL
CUBIC STRCUR = n
SGAGE FIBER
NONE
CORNER or BILIN
Example:
MAXMIN(GRID) = 12
MAXMIN(ELEM) = ALL
MAXMIN = NONE
Describer Meaning
GRID Indicates the request is applied to grid points.
ELEM Indicates the request is applied to elements.
BOTH Indicates the request is applied to both elements and grid points (Default).
PRINT Compute and write the output to the .f06 file (Default).
PUNCH Compute and write output to the punch file.
NOPRINT Compute but do not write out the results.
ALL Max/min results will be reported for all elements.
n Set identification number. The referenced SET command defines a set of elements
or grid points to be monitored.
NONE Max/min results will not be reported.
VONMISES von Mises stress/strains are output.
MAXS or Maximum shear stress/strains are output.
SHEAR
STRCUR Strain at the reference plane and curvatures are output for plate elements.
FIBER Stress/Strain at locations Z1, Z2 are computed for plate elements.
CENTER Output CQUAD4 stress/strains at the center only.
Main Index
CHAPTER 5 457
Requests Output of Maximums and Minimums in Data Recovery (new form)
Describer Meaning
CORNER or Output CQUAD4 element stress/strains at the center and grid points using strain
BILIN gage approach with bilinear extrapolation.
SGAGE Output CQUAD4 element stress/strains at center and grid points using strain
gage approach.
CUBIC Output CQUAD4 element stress/strains at center and grid points using cubic
bending correction.
Remarks:
1. MAXMIN is not allowed in REPCASE, but is allowed in SUBCOM and SYMCOM.
2. The OTIME command may be used to limit the time span of monitoring.
3. No corresponding output request such as DISP, STRESS, etc., is required (Except for STRAIN).
Also, SET=n may request more elements or grid points for monitoring than is requested by Outputs.
Currently for strain the output request STRAIN=n is required where n can reference any element. If
strain at fibers is requested then, then STRAIN (FIBER) = n is required.
The output is comprised of two parts: (1) a summary of the maximum/minimum values and the times
they occur, and (2) the associated output for all components of the element or grid. The first part is
always output, and the second part is only output if the FULL describer is specified on the
MAXMIN(DEF) Case Control command. See the next section for a description of the new Case
Control commands. Here are sample Case Control commands for the output of maximum von Mises
stresses using the BRIEF option:
MAXMIN(DEF) STRESS QUAD4 SMAX1 ABSOLUTE(5) BRIEF
SET 100=4
MAXMIN(ELEM)=4
4. See DISPLACEMENT, STRESS, or STRAIN Case Control commands for additional keyword
implications.
Main Index
458 MSC Nastran Quick Reference Guide
Defines Parameters for Monitoring Maximums and Minimums (new form)
MAXMIN(DEF) (Case) Defines Parameters for Monitoring Maximums and Minimums (new form)
Defines parameters and output options for the monitoring of maximums and minimums in data recovery.
MAXMIN(DEF) must be specified above all subcases. The MAXMIN(ELEM) and/or MAXMIN(GRID)
Case Control command is then required to print the max/min results.
Format for Grid Point Output:
MAXMIN DEF DISP, VELO, ACCE, MPCF, SPCF, OLOAD
T1 T2 T3 R1 R2 R3 MAGT MAGR
ABSOLUTE(p) MINALG(q) MAXALG(r) BRIEF
RMS ,
ALL(p) FULL
GLOBAL
CID = BASIC
cid
Format for element output:
STRESS
MAXMIN DEF STRAIN eltype1 , eltype2,...
FORCE
CENTER
/ ALL
comp1 comp2... ,
GROUP
ENDS
ABSOLUTE(p) MINALG(q) MAXALG(r) BRIEF
RMS
ALL(p) FULL
Examples:
MAXMIN(DEF) stress (quad4,smax1) MAXA=5
MAXMIN(DEF) disp T1 T2 T3 MAGT RMS FULL
MAXMIN(DEF) DISP VELO ACCE T1 T2 T3 R1 R2 R3 MAGT MAGR,
MAXMIN(DEF) STRESS HEXA P1/ALL P2/ALL P3/ALL OCT/ALL,
MAXMIN(DEF) STRESS QUAD4 SMJRP1 SMNRP1 tMAX1,
MAXMIN(DEF) STRESS BEAM SXC SXD SXE SXF SMAX SMIN,
MAXMIN(DEF) STRESS BAR AS SX1A SX2A SX3A SX4A BMAXA BMINA,
MAXMIN(DEF) STRESS ROD AS ABSO=1 RMS FULL
Main Index
CHAPTER 5 459
Defines Parameters for Monitoring Maximums and Minimums (new form)
MAXMIN(DEF) STRESS ELAS1 S ABSO=1 RMS FULL
Describer Meaning
DISP, VELO, etc. (grid point Type of result to be monitored.
output)
STRESS, etc. (element output)
T1, T2, etc. Name of the grid point component to be monitored.
MAGT Specifies the magnitude of the translational components are to be
monitored.
MAGR Specifies the magnitude of the rotational components are to be
monitored
eltype1 eltype2 … Name of the element type(s) to be monitored. At least one element type
must be present. All elements designations are generic and the "C",
designation Connections, should be dropped. The exceptions for this are
the CONROD and CONV element types. See remark 10.
comp1 comp2… Name of the element component(s) to be monitored; e.g., etmax1 for
max shear strain in the Z1 plane. The component names are defined in
the Nastran Data Definition Language (NDDL). Also, the item codes
from Item Codes may be used.
ABSOLUTE(p) Print out the top p absolute values (Default for p is 5).
MINALG(q) Print out the bottom q minimum algebraic values (Default for q is 5).
MAXALG(r) Print out the top r maximum algebraic values (Default for r is 5).
ALL(p) Print out all options: ABSOLUTE, MINALG, and MAXALG. (Default
for p is 5).
BRIEF Print out only the maxmin results (Default).
FULL Print out the maxmin results followed by the standard data recovery
format for the elements and grids at the retained set of the maximum or
minimum occurrences.
GLOBAL Selects the global coordinate system (see CD on the GRID entry) for
monitoring grid point results.
BASIC Selects the basic coordinate system for monitoring grid point results
(Default).
cid Specifies a coordinate system ID for a system defined on a CORDij entry
for monitoring grid point results.
RMS Print out the root-mean-square value of each maximum or minimum
value requested by ABSOLUTE, MIN, or MAX over all time steps.
CENTER Component selector when element allows for component name to occur
in multiple places (Default).
ALL Selects all locations in an element where multiple locations exist.
Main Index
460 MSC Nastran Quick Reference Guide
Defines Parameters for Monitoring Maximums and Minimums (new form)
Describer Meaning
GROUP Reduces all occurrences of a component name to a single value before the
action is performed.
ENDS Selects the ends of a BEAM element ignoring intermediate stations.
Remarks:
1. MAXMIN(DEF) must be specified above all subcases, but this is not sufficient to request monitoring
of maximums and minimums. The MAXMIN command must also be specified above or inside
subcases.
2. MAXMIN(DEF) may be specified more than once.
3. Multiple element types may be grouped together, if the same component name is to be monitored
across those types, by enclosing the element types in parentheses. This grouping does not combine
the element types during processing. Each type and component action is performed in class.
4. Multiple component names may be compared collectively to the current maximum (or minimum),
but only the maximum (or minimum) component in the group will be reported in the output. This
is requested by enclosing the component names in parentheses.
5. Grid point component output is always converted to the basic coordinate system for monitoring
when processing “sort1”. The global system is the default when processing in “sort2”.
6. Results for layers in composite elements, or intermediate stations in CBAR and CBEAM elements,
are not supported.
7. Only real data recovery is supported.
8. When no MINA, MAXA, or ABSO keyword is supplied, the default values of p, q, and s will be 5.
When any keyword is supplied, the other unreferenced keyword values will be set to zero, and no
output will be created.
9. The component action keywords of CENTER, ALL, GROUP, and ENDS can only be applied to
component names defined in the NDDL and occur at multiple places in element data recovery. They
cannot be used with Item Codes.
10. Specify QUAD4C and TRIA3C for corner stresses of CQUAD4 and CTRIA3 elements when a
CUBIC, SGAGE, BILIN or CORNER option is specified on the STRESS/STRAIN output request.
11. MAXMIN data output to the .op2 and .xdb files are not supported.
12. SORT1 and SORT2 output Case Control options (such as DISP(SORT2)=ALL), cause MAXMIN
to behave differently.
• SORT1 is only supported in SOLs 101, 103, 105, and 109. For each static loadcase, mode
buckling eigenvalue, or time step, all the grids or elements will be searched for maximums and
minimums.
• SORT2 is only supported in SOL 112. For each selected grid or element, all the time steps will
be searched for maximums and minimums.
Main Index
CHAPTER 5 461
Modal Contribution Fractions Output Request
MCFRACTION (Case) Modal Contribution Fractions Output Request
Requests the form and type of modal contribution fraction output.
Format:
MCFRACTION STRUCTURE PRINT, PUNCH REAL or IMAG SORT = sorttype
PLOT PHASE
FRACTION ALL
FRACTION 0.001
KEY = ITEMS = ALL SOLUTION = m FILTER =
sortitem fratio
(itemlist) NONE
ALL
12
NULL = = n
ipowr
NONE
Example:
SET 1001 = 10.0, 20.0, 100.0
SET 2001 = 716/T3, 809/T3, 412/T1
MCFRACTION (STRUCTURE,PRINT,PUNCH,ITEM=FRACTION,
SORT=ABSD,KEY=PROJECTION,SOLUTION=1001)=2001
MCFRACTION (ITEMS=(FRACTION,PROJECTION),FILTER=0.01)=2001
Describer Meaning
STRUCTURE Request pertains to structure points only.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output.
PHASE Requests polar format (magnitude and phase) of complex output.
Main Index
462 MSC Nastran Quick Reference Guide
Modal Contribution Fractions Output Request
Describer Meaning
SORT Keyword selecting one of the sort type options. Default is to produced output in
increasing natural mode number order.
sorttype One of the following modal contribution fraction output sorting options:
ABSA - output will be sorted by absolute value in ascending order.
ABSD - output will be sorted by absolute value in descending order.
ALGA - output will be sorted algebraically in ascending order.
ALGD - output will be sorted algebraically in descending order.
KEY Keyword selecting a sorting operation key quantity.
sortitem Item from the item list table on which the SORT operation is performed. (Default
is FRACTION.)
ITEMS Keyword specifying data selection options.
itemlist One (or more) of the following modal contribution fraction output items. If more
than one item is selected, the list must be enclosed in parentheses:
Item Identifier Description
RESPONSE Each mode’s response at each degree of freedom is selected.
PROJECTION Projection of modal response on solution.
FRACTION Fraction of total displacement per mode (PROJECTION divided by total).
SCALED Scaled magnitude (PROJECTION divided by largest magnitude of modal response).
MODEDISP Modal displacements (complex solution at each DOF by mode number).
MODERESP Modal response for each mode (polar format with respect to total displacement).
SOLUTION Keyword specifying the output solution time step, forcing frequency, or complex
eigenvalue selections for which modal fractions will be generated (Default = ALL).
m Results for solutions in SET m will be output.
FILTER Keyword specifying the value of the printed output data filter.
fratio Value of output filter ratio (Default = 0.001).
NULL Keyword specifying the power of ten used to detect a null response quantity.
ipowr The power of ten used to detect a null response quantity (Default = 12).
n Results for grid point components in SET n will be output.
ALL Results for all solutions and/or grid point components will be output.
NONE No modal contribution fractions will be output.
Main Index
CHAPTER 5 463
Modal Contribution Fractions Output Request
Remarks:
1. The MCFRACTION Case Control command is useful in modal frequency response (SOL 111),
modal transient response (SOL 112), and modal complex eigenvalue analysis (SOL 110) solution
sequences only. If superelements are used, its use is restricted to residual structure data recovery
operations only. MCFRACTION is not supported in SOL 200 or 400.
2. Printed output includes results for all of the data items described in the itemlist table.
3. Punched output includes results for only the data items selected by the ITEMS keyword.
4. Modal contribution fractions are sorted by increasing order of mode number unless the SORT
keywords specifies a particular sorting order. If a sorting order is specified, the KEY keyword selects
the particular data item in the printed results tabular output listing that is sorted. When MODEDISP
is selected, the magnitude is sorted. When MODERESP is selected, the real portion of the response
is sorted.
5. The SOLUTION keyword can be used to select a subset of the solutions available. If SET m is
specified, the items in the SET list are forcing frequency values, time step values, or complex
eigenvalue mode numbers, depending upon the solution sequence used.
6. The FILTER keyword specifies a filter ratio value that is used to limit the amount of printed output
produced. It applies to the data item selected by the KEY keyword if it is specified. If no KEY keyword
is present, the default value od KEY=FRACTION will be used. The maximum value for the selected
data item across all natural modes is determined. If the ratio of the data item value to the maximum
data item value is less than fratio for any natural mode, no output for that natural mode is produced.
– ipowr
7. If the magnitude of the total response at a selected grid pint component is less than 1.0 10 ,
no modal contribution fraction output is generated for that degree of freedom. If ipowr is not in the
range of 1 to 31, the default value of 12 is used for ipowr, producing a null response threshold of
– 12
1.0 10 .
8. For modal transient response solution sequences, response quantities are real numbers. There are no
imaginary terms. Therefore, polar representations of the data has no meaning. Furthermore,
projections of responses onto the total response are simply the individual modal contribution to the
total response at a degree of freedom. Thus, the only items available for output are the individual
modal response magnitude (PROJECTION), the modal fraction (FRACTION), and the scaled
response magnitude (SCALED). Selection of any of the other items from the itemlist table causes
selection of the modal response magnitude (PROJECTION) item.
9. A request of MCFRACTION output for a SET that contains no degrees-of-freedom in the analysis
set, will result in the message: “SYSTEM WARNING MESSAGE 2001 (MCFRAC)”
Main Index
464 MSC Nastran Quick Reference Guide
Set Definition for Modules Data Recovery
MDSET (Case) Set Definition for Modules Data Recovery
Define sets that associate module ID with the entity (element and grid) ID and are referenced by data
recovery commands like DISP, STRESS, etc.
Format:
MDSET n = { h1 [h2 h3 h4 [THRU h5 [EXCEPT h6 …] ] … }{ m1/i11 i12 i13 … [m2/i21
i22 i23 … i24 [THRU i25 [EXCEPT i26 …] … ] }
Examples:
MDSET 1 = 1/1 2/3 3/2 5/6
MDSET 100 = 14/ALL
MDSET 4 = 0/17 13/12 0/34 THRU 45 87/1 THRU 100
MDSET 48 = 17 807/1 THRU 100 EXCEPT 55
MDSET 615 = 43/75 62 107 26
Describer Meaning
n Set identification number. MDSETs specified under a SUBCASE command are
recognized for that SUBCASE only (Integer > 0).
hi Element or grid identification number whose results will be computed for all modules.
MDSET has two sections, which are divided at the beginning of the first module/entity
pair. Every entity specified before the first pair is assigned to all modules and every entity
after is assigned to a specific module. The first section uses the same format as the SET
command. (Integer>0 or “ALL”)
mi Module identification number (Integer>0)
iij Element or grid identification number whose results will be computed only for module
mi. (Integer>0 or “ALL”)
i24 THRU i25 Range of element or grid identification numbers (Integer>0 and i25> i24)
EXCEPT Element or grid identification numbers following EXCEPT will be deleted from the set
if they are in the range of the set defined by the preceding
THRU. An EXCEPT list may not include a THRU list or ALL.
ALL All elements or grids in the module.
Remarks:
1. An MDSET command may be more than one physical line. A comma at the end of a physical line
signifies a continuation line follows. Commas may not end a set. THRU may not be used for
continuation. Place a number after the THRU.
2. The element or grid identification numbers following EXCEPT within the range of the THRU must
be in ascending order.
Main Index
CHAPTER 5 465
Set Definition for Modules Data Recovery
3. MDSET may only be used when Modules exist. If there are no Modules, then the program will issue
a User Fatal Message.
4. The members in a SET and MDSET command with the same set ID will be merged. If there are
duplicate set IDs and just ALL is specified on either MDSET or SET, then ALL overrides the other
set without ALL.
5. MDSET is supported in the following solution sequences: 101, 103, 105, 107 through 112, 200
(analysis only), and 400.
6. MDSET may be referenced by these commands only:
DISP MAXMIN PACCELERATION
SPCF GPKE
FORCE MPRESS
STRAIN EKE
MPCF EDE
STRESS VELOCITY
ESE ACCELERATION
GPFORCE SDISPLACEMENT
NLLOAD SVELOCITY
NLSTRESS SACCELERATION
OLOAD SVECTOR
Main Index
466 MSC Nastran Quick Reference Guide
Modal Effective Mass Output Request
MEFFMASS (Case) Modal Effective Mass Output Request
Requests the output of the modal effective mass, participation factors, and modal effective mass fractions in
normal modes analysis.
Format:
SUMMARY, PARTFAC,
MEFFMASS PRINT PUNCH GRID = gid, = YES
MEFFM, MEFFW,
NOPRINT NOPUNCH NO
FRACSUM, ALL
Examples:
MEFFMASS
MEFFMASS(GRID=12, SUMMARY, PARTFAC)
Describer Meaning
PRINT Write output to the print file (Default).
NOPRINT Do not write output to the print file.
PUNCH Write output to the punch file.
NOPUNCH Do not write output to the punch file (Default).
gid Reference a grid point for the calculation of the rigid body mass matrix. The
default is the origin of the basic coordinate system.
SUMMARY Requests calculation of the total effective mass fraction, modal effective mass
matrix, and the rigid body mass matrix (Default).
PARTFAC Requests calculation of modal participation factors.
MEFFM Requests calculation of the modal effective mass in units of mass.
MEFFW Requests calculation of the modal effective mass in units of weight.
FRACSUM Requests calculation of the modal effective mass fraction.
Remarks:
1. The SUMMARY describer produces three outputs:
T
a. Modal effective mass matrix m
where:
1 T
= Modal participation factors: m M aa D ar .
m = Generalized mass matrix.
= Eigenvectors.
Main Index
CHAPTER 5 467
Modal Effective Mass Output Request
M aa = Mass marix reduced to the a-set (g-set for superelements).
D ar = Rigid body transformation matrix with respect to the a-set.
T
b. A-set rigid body mass matrix: D ar M aa D ar . For superelement this is computed at the g-
set
c. Total effective mass Fraction: i.e., diagonal elements of the modal effective mass matrix divided
by the rigid body mass matrix.
2. The PARTFAC describer outputs the modal participation factors table .
2
3. The MEFFM describer outputs the modal effective mass table , the term-wise square of the modal
participation factors table.
4. The MEFFW describer outputs the modal effective weight table; i.e., the modal effective mass divided
by PARAM, WTMASS.
5. The FRACSUM describer outputs the modal effective mass fraction table; i.e., the generalized mass
matrix (diagonal term) multiplied by the modal effective mass divided by the rigid body mass matrix
(diagonal term).
6. For superelements, the MEFFMASS Case Control command uses the residual structure eigenvalues
and eigenvectors, by default. If, however, PARAM, FIXEDB, -1 is specified, then the MEFFMASS
Case Control command uses the component mode eigenvalues and eigenvectors.
Main Index
468 MSC Nastran Quick Reference Guide
Real Eigenvalue Extraction Method Selection
METHOD (Case) Real Eigenvalue Extraction Method Selection
Selects the real eigenvalue extraction parameters.
Format:
BOTH
STRUCTURE
METHOD FLUID =n
COUPLED
SYMCOUP
Examples:
METHOD=33
METHOD(FLUID)=34
METHOD(COUPLED)=100
METHOD(SYMCOUP)=200
Describer Meaning
BOTH The referenced EIGR or EIGRL Bulk Data entry will be applied to both the
structure and the fluid portion of the model (Default).
STRUCTURE The referenced EIGR or EIGRL Bulk Data entry is applied to the structural or fluid
or FLUID portion of the model.
COUPLED The referenced EIGR or EIGRL Bulk Data entry is applied to the structural and
fluid coupled system of the model using subspace iteration method.
SYMCOUP The referenced EIGR or EIGRL Bulk Data entry is applied to the structural and
fluid coupled system of the model using Lanczos Method.
n Set identification number of an EIGR or EIGRL Bulk Data entry for normal modes
or modal formulation, or an EIGB or EIGRL entry for buckling (Integer > 0).
Remarks:
1. An eigenvalue extraction method must be selected when extracting real eigenvalues.
2. If the set identification number selected is present on both EIGRL and EIGR and/or EIGB entries,
the EIGRL entry will be used.
3. METHOD(FLUID) and METHOD(STRUCTURE) permits a different request of EIGR or
EIGRL for the fluid portion of the model in coupled fluid-structural analysis.
• If METHOD(STRUCTURE) or METHOD(FLUID) is also specified, then they will override
the METHOD(BOTH) selection.
Main Index
CHAPTER 5 469
Real Eigenvalue Extraction Method Selection
• The METHOD(FLUID) and METHOD(STRUCTURE) may be specified simultaneously in
the same subcase for the residual structure only. Do not specify METHOD(FLUID) in a
superelement subcase even if the superelement contains fluid elements.
• The auto-omit feature (see Real Eigenvalue Analysis in SubDMAPs SEMR3 and MODERS in the MSC
Nastran Reference Guide) is not recommended. Therefore, only those methods of eigenvalue
extraction that can process a singular mass matrix should be used; e.g., the EIGRL entry, or
MGIV and MHOU on the EIGR entry.
4. METHOD(COUPLED) is only used for fluid-structure coupled problem. The corresponding
EIGRL or EIGR requires either the frequency range of interest or ND (number of roots desired)
entry. The real coupled modes computation with METHOD(COUPLED) is done with Subspace
iteration method. METHOD(COUPLED) is recommended for heavy fluid (like liquids) model.
When it is applied to the light fluid model, it might require more coupled modes to get the correct
result. Real coupled method is also supported in SOL 103, SOL 111, SOL 112, SOL 200
(ANALYSIS) and SOL 400 (ANALYSIS=LINEAR). When METHOD(COUPLED) is used with
both METHOD(STRUCTURE) and METHOD(FLUID), real coupled modes computation using
Subspace iteration method will use structural and fluid modes for the initial guess of coupled modes
computation. This might help to reduce the number of iterations for real coupled modes
computation.
5. METHOD(SYMCOUP) is also used only for fluid-structure coupled system. The corresponding
EIGRL or EIGR requires either the frequency range of interest or ND (number of roots desired)
entry. The real coupled modes computation with METHOD(SYMCOUP) is done with Lanczos
method. Same as METHOD(COUPLED), METHOD(SYMCOUP) is recommended for heavy
fluid model and is supported in SOL 103, SOL 111, SOL 112, and SOL200/400(LINEAR).
Main Index
470 MSC Nastran Quick Reference Guide
Fluid Boundary Element Selection
MFLUID (Case) Fluid Boundary Element Selection
Selects the MFLUID Bulk Data entries to be used to specify the fluid-structure interface.
Format:
MFLUID = n
Example:
MFLUID = 919
Describer Meaning
n Set identification number of one or more MFLUID Bulk Data entries (Integer > 0).
Remark:
1. For additional discussion, see Coupled Fluid-Structure Analysis in the MSC Nastran Dynamic Analysis
User’s Guide.
2. Use parameter PARAM,VMOPT controls how the virtual mass is processed.
3. Virtual mass is not supported with the following features:
a. Cyclic symmetry analysis (SOLs 114, 115, 116 and 118)
b. ADAMS MNF generation (ADAMSMNF Case Control command)
c. AVL/EXCITETM generation (AVLEXB Case Control command). Note that virtual mass can be
supported for AVL/Excite by using the MASINVAR=NONE option on the AVLEXB case
control command.
Main Index
CHAPTER 5 471
Master Frequency Set Selection Frequency Response
MFREQUENCY (Case) Master Frequency Set Selection Frequency Response
Selects the set of forcing frequencies to be used in frequency analysis as master frequencies for K, B, and K4
matrix generation at each master frequency, in frequency dependent analysis.
Format:
AUTO
Linear NOAUTO
MFREQUENCY , TOL = 0.1 =
Log10
n
Example:
MFREQ (TOL=.15) Nastran will generate a master frequency list with TOL=.15
Describer Meaning
Linear Linear interpolation will be used between master frequencies to compute K, B, and
K4 matrices found on selected Case Control FREQ entry. (Character, Default)
Log10 Log interpolation will be used between master frequencies to compute K, B, and K4
matrices found on selected FREQ entry. (Character)
TOL For the default option AUTO, for frequency dependent TABLEDi entries associated
with the presence of any MAT1F, MAT2F, MAT8F, MAT9F entries or the combined
presence of any MAT1F, MAT2F, MAT8F, MAT9F entries and any PBUSHT,
PELAST, PDAMPT entries a master frequency will be selected whenever there is a
TOL jump in any table value. A TOL=0.0 is the same as NOAUTO. (Real ≥0.0)
AUTO For frequency dependent analysis associated with the presence of any MAT1F,
MAT2F, MAT8F, MAT9F entries or the combined presence of any MAT1F,
MAT2F, MAT8F, MAT9F entries and any PBUSHT, PELAST, PDAMPT entries,
Nastran will automatically, depending on associated frequency dependent TABLEDi
entries and the required Case Control FREQ=m entry, generate a series of master
frequencies. (Character, Default).
If the user has supplied a Case Control MFREQ entry pointing to a FREQ, FREQ1,
or FREQ2 bulk data entry, Nastran will use the user supplied entry and its associated
frequency list.
NOAUTO If the user has not supplied a MFREQ Case Control entry and the analysis meets the
requirements of AUTO above, then NOAUTO will prevent the generation of master
frequencies. In this case, the required Case Control FREQ will be used for all
frequencies. And all frequencies are considered master frequencies. (Character)
n Set identification number of FREQ, FREQ1, and FREQ2 Bulk Data entries.
(Integer > 0)
Main Index
472 MSC Nastran Quick Reference Guide
Master Frequency Set Selection Frequency Response
Remark:
1. Both direct frequency and modal frequency allow, through MAT1F, MAT2F, MAT8F, MAT9F,
and PBUSHT, PELAST, PDAMPT entries frequency dependent analysis. The presence of any active
MAT1F, MAT2F, MAT8F, or MAT9F entry or the combined presence of any MAT1F, MAT2F,
MAT8F, MAT9F entries and any PBUSHT, PELAST, PDAMPT entries a master frequency will
initiate the master frequency feature in frequency analysis.
2. MFREQ should be above or in the first subcase.
3. The K, B, and K4 matrices, at master frequencies, are formed in the standard way, using material and
property values at the associated current master frequency.
4. For frequencies selected between master frequencies, interpolation of the K, B, and, K4 matrices are
performed. These interpolated frequencies are selected using the required Case Control FREQ=m
entry.
5. Interpolation between master frequencies Klm and K2m is Kij = (d2 Klmij + d1 K2mij)/(d1 + d2) where.
For Linear:
d1 = (f-f1); d2 = (f2 – f)
For Log10:
d1 = (log10(f) – log10(f1)); d2 = (log10(f2) – log10(f))
6. For master frequencies there is full displacement, velocity, acceleration type data recovery as well as
full element force and stress type data recovery.
7. For interpolated frequencies, there is only a-set or h-set (modal) displacement, velocity, acceleration
type data recovery. Because, the solution of interpolated frequencies is based on interpolated K, B,
and K4, the element stress and force data will be less accurate as the interpolated frequency gets farther
from a master frequency. This is also true for fluid data recovery such as Panel Participation Factors.
If accurate element results are required at specific frequencies, then MFREQ=n should be used to
define Master frequencies. If accurate element results are required at all frequencies, then the user
should either set MFREQ to the same set as defined on the Case Control Command FREQ=n or set
MFREQ=NOAUTO.
8. For modal frequency analysis, associated with master frequencies, residual vector methods for viscous
and structural damping have been greatly enhanced and orthogonalization techniques are employed
which require the removal of free – free modes. For this reason the structure must be statically
constrained with the use of SUPORT entries. Case Control selectable SUPORT1 entries may also be
used.
9. For preloading (STATSUB), with the presence of any MAT1F, MAT2F, MAT8F, MAT9F entries
or the combined presence of any MAT1F, MAT2F, MAT8F, MAT9F entries and any PBUSHT,
PELAST, PDAMPT entries, a fatal message will be issued.
*** USER FATAL MESSAGE 22711 (MTMD56)
FREQUENCY case control command missing for frequency response analysis.
STATSUB static loading is not currently supported for frequency dependent material/property.
Main Index
CHAPTER 5 473
Master Frequency Set Selection Frequency Response
10. PARAM, NMNLFRQ, REAL (Default=0.0) allows users to select material or property values for
frequency dependent materials or properties at a desired frequency other than the “nominal” values
specified on the MATi or PBUSH, PCOMP, PCOMPG, PDAMP, or PELAS entries. These values
are used in determining the eigenvalue solution used in the modal frequency analysis.
11. If a user supplies a FREQ, FREQ1, or FREQ2 entry with a 0.0 value of forcing frequency the
following message will be issued:
*** USER WARNING MESSAGE 22714 (SUBDMAP MFREQRS)
Forcing frequency value of 0.0 detected, nominal (initial) material properties used.
The rational for this selection is that 0.0 Hz is a static solution and SOL 101 would use material
nominal.
12. Some examples of interaction between MFREQ=AUTO and an always required FREQ=m and
interpolated values are as follows:
If frequency dependent TABLEDi entries associated with the presence of any MAT1F, MAT2F,
MAT8F, MAT9F entries or the combined presence of any MAT1F, MAT2F, MAT8F, MAT9F
entries and any PBUSHT, PELAST, PDAMPT entries are detected, and the user has not specified
any MFREQ Case Control entries, then Nastran will automatically scan the TABLEDi entries.
Nastran does this by using the required FREQ=m entry and for any TABLEDi where there is a TOL
jump between two consecutive FREQ=m frequencies determining a “Master frequency”.
SOL111
CEND
FREQ = 10 Required
...
BEGIN BULK
FREQ1, 10, 10.0, 5.0, 78
...
MAT1, 2, 35.46, , .49, 1.1-9
MAT1F, 2, 101, 103, 102 All 3 Tables for E, G, NU
required.
...
TABLED1, 101,
,.01, 7.3941, 50., 18.017, 100., 24.386, 200., 35.46,
,300., 44.45, 400., 51.264, 500., 56.321, ENDT
TABLED1, 102
,.01, 0.49, 1000., 0.49, ENDT
TABLED1, 103
,.01, 2.481, 50., 6.076, 100., 8.1832, 200., 11.899
,300., 14.916, 400., 17.203, 500., 18.90, ENDT
TABLED1, 200 Based on say an active PBUSHT entry.
,.01, 0.4, 50., 0.65, 100., 0.78,200., 0.92
,300., 0.99, 400., 1.03, 500., 1.07, endt
Internally Nastran Generates in Case Control:
MFREQ=11
Internally Nastran Generates in “Bulk Data”:
FREQ, 11, 10., 15., 20., 30., 40., 50., 65.,
,85., 105., 130., 160., 190., 230., 275., 330.,
,400.
Main Index
474 MSC Nastran Quick Reference Guide
Master Frequency Set Selection Frequency Response
Where for the above, Nastran has based on the user supplied FREQ=10 Case Control entry, scanned
all the active user supplied TABLEDi entries, and whenever there is a jump in table value of 10%
(default TOL), it creates an entry into the master frequency list MFREQ=11.
MFREQ will issue the message:
***AUTOMATIC MASTER FREQUENCY LIST HAS BEEN SELECTED FOR
SUBCASE ID 1:
FREQ, 11, 10., 15., 20., 30., 40., 50., 65.,
,85., 105., 130., 160., 190., 230., 275., 330.,
,400.
Main Index
CHAPTER 5 475
Modal Kinetic Energy Request
MODALKE (Case) Modal Kinetic Energy Request
Requests a modal kinetic energy calculation and specifies the output form.
Format:
MODE
SORT1 PRINT REAL or IMAG
MODALKE ( PUNCH ESORT = ASCEND
SORT2 NOPRINT PHASE
DESCEND
ALL
TIME ALL AVERAGE
THRESH = e = AMPLITUDE ) = n
FREQ r
PEAK NONE
Examples:
MODALKE= ALL
SET 200= 1, 3, 4, 5, 7
MODALKE(ESORT=DESCEND,THRESH=.001)= 200
Describer Meaning
SORT1 Output will be presented as a tabular listing of modes for each frequency or time
step.
SORT2 Output will be presented as a tabular listing of frequencies or time steps for each
mode.
PRINT Write the results to the .f06 file (Default).
NOPRINT Do not write the results to the .f06 file.
PUNCH Write the results to the punch (.f07) file.
ESORT Present the modal energies sorted by mode number, ascending energy value or
descending energy value (Default is MODE)
THRESH Write out only those energies greater than e (Default = 0.001).
TIME or FREQ Compute energies at all time steps, or frequencies, or the set of frequencies defined
by SET r (Default = ALL).
AVERAGE Requests average energy in frequency response analysis only (Default).
AMPLITUDE Requests amplitude of energy in frequency response analysis only.
PEAK Requests peak energy for frequency response analysis only. PEAK is the sum of
AVERAGE and AMPLITUDE.
ALL, n, NONE Compute modal energies for (1) all modes, (2) the modes defined on SET n, or (3)
no modes.
Main Index
476 MSC Nastran Quick Reference Guide
Modal Kinetic Energy Request
Remarks:
1. Modal kinetic energy calculations will be limited to SOLs 112 (modal transient response) and 111
(modal frequency response).
2. The MODES describer selects from the set of the modes selected by the combination of the Case
Control command MODESELECT, and user parameters PARAM,LMODES; PARAM,LFREQ;
PARAM,HFREQ. If a mode is selected outside this set, a User Warning Message is issued.
3. The TIME (or FREQ) describer selects from the set of the time steps (or forcing frequencies) selected
by the OTIME (or OFREQ) Case Control command. If a time or frequency is selected outside this
set, a User Warning Message is issued.
4. For frequency response analysis, the energy may be output as real or complex values. When REAL is
specified, the output will be one of AVERAGE, AMPLITUDE or PEAK energy. (See Remark 4. of
the EKE Case Control Command for a definition of these terms.) When IMAG or PHASE is
specified, the output will be complex energy values.
Output Format:
The output formats for complex energy in frequency response analysis follow.
For SORT1 option:
FREQUENCY = 2.100000E+01
M O D A L K I N E T I C E N E R G Y
(REAL/IMAGINARY)
MODE NUMBER ACTUAL NORMALIZED FRACTIONAL
1 1.171343E-04 1.409326E-02 1.065749E-02
0.0 0.0 0.0
2 2.049217E-05 2.465558E-03 1.864483E-03
0.0 0.0 0.0
3 5.175167E-04 6.226612E-02 4.708635E-02
0.0 0.0 0.0
4 1.732168E-05 2.084095E-03 1.576016E-03
0.0 0.0 0.0
This format repeats for each frequency.
For SORT2 option:
MODE NUMBER = 1
M O D A L K I N E T I C E N E R G Y
(MAGNITUDE/PHASE)
FREQUENCY ACTUAL NORMALIZED FRACTIONAL
1.000000E+00 8.147644E-04 1.000000E+00 9.924866E-01
0.0 0.0 0.0
2.000000E+00 4.066132E-03 1.000000E+00 9.936857E-01
0.0 0.0 0.0
3.000000E+00 1.411670E-02 1.000000E+00 9.955440E-01
0.0 0.0 0.0
This format repeats for each mode number.
The output formats for AVERAGE energy in frequency response analysis follow. The particular type
(AVERAGE, AMPLITUDE or PEAK) is identified in the output title.
Main Index
CHAPTER 5 477
Modal Kinetic Energy Request
For SORT1 option:
FREQUENCY = 2.100000E+01
M O D A L K I N E T I C E N E R G Y ( A V E R A G E )
MODE NUMBER ACTUAL NORMALIZED FRACTIONAL
1 5.856715E-05 1.409326E-02 1.065749E-02
2 1.024608E-05 2.465558E-03 1.864483E-03
3 2.587583E-04 6.226612E-02 4.708635E-02
4 8.660840E-06 2.084095E-03 1.576016E-03
This format repeats for each frequency.
For SORT2 option:
MODE NUMBER = 1
M O D A L K I N E T I C E N E R G Y ( A V E R A G E )
FREQUENCY ACTUAL NORMALIZED FRACTIONAL
1.000000E+00 4.073822E-04 1.000000E+00 9.924866E-01
2.000000E+00 2.033066E-03 1.000000E+00 9.936857E-01
3.000000E+00 7.058351E-03 1.000000E+00 9.955440E-01
4.000000E+00 2.872413E-02 1.000000E+00 9.977741E-01
This format repeats for each mode number.
The output formats for transient response analysis follow.
For SORT1 option:
TIME STEP = 1.000000E+00
M O D A L K I N E T I C E N E R G Y
MODE NUMBER ACTUAL NORMALIZED FRACTIONAL
1 1.483182E-02 3.610759E-01 2.316040E-01
2 4.107675E-02 1.000000E+00 6.414274E-01
3 2.165481E-04 5.271792E-03 3.381472E-03
4 1.387959E-05 3.378941E-04 2.167345E-04
This format repeats for each time step.
For SORT2 option:
MODE NUMBER = 2
M O D A L K I N E T I C E N E R G Y
TIME STEP ACTUAL NORMALIZED FRACTIONAL
0.000000E+00 0.0 0.0 0.0
9.999999E-02 2.512383E-03 1.000000E+00 9.420497E-01
2.000000E-01 8.475699E-03 1.000000E+00 9.566881E-01
3.000000E-01 1.415435E-02 1.000000E+00 9.568216E-01
This format repeats for each mode number.
Processing:
Modal kinetic energy is calculated using the following relations:
For transient analysis,
Main Index
478 MSC Nastran Quick Reference Guide
Modal Kinetic Energy Request
1 T
Actual KE = --- u· h M hh u· h
2
For frequency response analysis,
1 T 2
Actual KE = --- u h diag i M hh u h
2
where i is the excitation frequency and output is complex. See Remark 4 of the EKE (Case) Case Control
command for energy calculation relations when output is real.
[Normalized Kinetic Energy] = norm[Actual Kinetic Energy], normalized per column.
T
[Fractional Kinetic Energy] = [Normalized Kinetic Energy]/[diagonal 1.0 [Normalized
Kinetic Energy]]], term-by-term division.
Main Index
CHAPTER 5 479
Modal Strain Energy Request
MODALSE (Case) Modal Strain Energy Request
Requests modal strain energy calculation and specifies the output form.
Format:
MODE
SORT1 PRINT REAL or IMAG
MODALSE ( PUNCH ESORT = ASCEND
SORT2 NOPRINT PHASE
DESCEND
ALL
TIME ALL AVERAGE
THRESH = e = AMPLITUDE ) = n
FREQ r
PEAK NONE
Examples:
MODALSE= ALL
SET 100= 1, 3, 4, 5, 7
MODALSE(ESORT=ASCEND,THRESH=.0001)= 100
Describer Meaning
SORT1 Output will be presented as a tabular listing of modes for each frequency or time
step.
SORT2 Output will be presented as a tabular listing of frequencies or time steps for each
mode.
PRINT Write the results to the .f06 file (Default).
NOPRINT Do not write the results to the .f06 file.
PUNCH Write the results to the punch (.f07) file.
ESORT Present the modal energies sorted by mode number, ascending energy value or
descending energy value (Default is MODE).
THRESH Write out only those energies greater than e (Default = 0.001).
TIME or FREQ Compute energies at all time steps or frequencies or the set of frequencies defined
by SET r (Default = ALL).
AVERAGE Requests average energy in frequency response analysis only (Default).
AMPLITUDE Requests amplitude of energy in frequency response analysis only.
PEAK Requests peak energy for frequency response analysis only. PEAK is the sum of
AVERAGE and AMPLITUDE.
ALL, n, NONE Compute modal energies for all modes, the modes defined on SET n, or (3) no
modes.
Main Index
480 MSC Nastran Quick Reference Guide
Modal Strain Energy Request
Remarks:
1. Modal strain energy calculations will be limited to SOLs 112 (modal transient response) and 111
(modal frequency response).
2. The MODES describer selects from the set of the modes prescribed by the combination of Case
Control command MODESELECT, and user parameters PARAM,LMODES; PARAM,LFREQ;
and PARAM,HFREQ. If a mode is selected outside this set, a User Warning Message is issued.
3. The TIME (or FREQ) describer selects from the set of the time steps (or forcing frequencies)
prescribed by the OTIME (or OFREQ) Case Control command. If a time or frequency is selected
outside this set, a User Warning Message is issued.
4. For frequency response analysis, the energy may be output as real or complex values. When REAL is
specified, the output will be one of AVERAGE, AMPLITUDE or PEAK energy. (See Remark 4 of
the ESE Case Control Command for a definition of these terms.) When IMAG or PHASE is
specified, the output will be complex energy values.
Output Format:
The output formats for complex energy in frequency response analysis follow.
For SORT1 option:
FREQUENCY = 2.100000E+01
M O D A L S T R A I N E N E R G Y
(REAL/IMAGINARY)
MODE NUMBER ACTUAL NORMALIZED FRACTIONAL
1 1.171343E-04 1.409326E-02 1.065749E-02
0.0 0.0 0.0
2 2.049217E-05 2.465558E-03 1.864483E-03
0.0 0.0 0.0
3 5.175167E-04 6.226612E-02 4.708635E-02
0.0 0.0 0.0
4 1.732168E-05 2.084095E-03 1.576016E-03
0.0 0.0 0.0
This format repeats for each frequency.
For SORT2 option:
MODE NUMBER = 1
M O D A L S T R A I N E N E R G Y
(MAGNITUDE/PHASE)
FREQUENCY ACTUAL NORMALIZED FRACTIONAL
1.000000E+00 8.147644E-04 1.000000E+00 9.924866E-01
0.0 0.0 0.0
2.000000E+00 4.066132E-03 1.000000E+00 9.936857E-01
0.0 0.0 0.0
3.000000E+00 1.411670E-02 1.000000E+00 9.955440E-01
0.0 0.0 0.0
This format repeats for each mode number.
The output formats for AVERAGE energy in frequency response analysis follow. The particular type
(AVERAGE, AMPLITUDE or PEAK) is identified in the output title.
Main Index
CHAPTER 5 481
Modal Strain Energy Request
For SORT1 option:
FREQUENCY = 2.100000E+01
M O D A L S T R A I N E N E R G Y ( A V E R A G E )
MODE NUMBER ACTUAL NORMALIZED FRACTIONAL
1 5.856715E-05 1.409326E-02 1.065749E-02
2 1.024608E-05 2.465558E-03 1.864483E-03
3 2.587583E-04 6.226612E-02 4.708635E-02
4 8.660840E-06 2.084095E-03 1.576016E-03
This format repeats for each frequency.
For SORT2 option:
MODE NUMBER = 1
M O D A L S T R A I N E N E R G Y ( A V E R A G E )
FREQUENCY ACTUAL NORMALIZED FRACTIONAL
1.000000E+00 4.073822E-04 1.000000E+00 9.924866E-01
2.000000E+00 2.033066E-03 1.000000E+00 9.936857E-01
3.000000E+00 7.058351E-03 1.000000E+00 9.955440E-01
4.000000E+00 2.872413E-02 1.000000E+00 9.977741E-01
This format repeats for each mode number.
The output formats for transient response analysis follow.
For SORT1 option:
TIME STEP = 1.000000E+00
M O D A L S T R A I N E N E R G Y
MODE NUMBER ACTUAL NORMALIZED FRACTIONAL
1 1.483182E-02 3.610759E-01 2.316040E-01
2 4.107675E-02 1.000000E+00 6.414274E-01
3 2.165481E-04 5.271792E-03 3.381472E-03
4 1.387959E-05 3.378941E-04 2.167345E-04
This format repeats for each time step.
For SORT2 option:
MODE NUMBER = 2
M O D A L S T R A I N E N E R G Y
TIME STEP ACTUAL NORMALIZED FRACTIONAL
0.000000E+00 0.0 0.0 0.0
9.999999E-02 2.512383E-03 1.000000E+00 9.420497E-01
2.000000E-01 8.475699E-03 1.000000E+00 9.566881E-01
3.000000E-01 1.415435E-02 1.000000E+00 9.568216E-01
This format repeats for each mode number.
Processing:
Modal strain energy is calculated using the following relations:
Main Index
482 MSC Nastran Quick Reference Guide
Modal Strain Energy Request
1 T
Actual SE = --- u h K hh u h
2
For frequency response analysis real output, see Remark 4 of the ESE (Case)Case Control command for energy
calculation relations.
[Normalized Strain Energy] = norm[Actual Strain Energy], normalized per column.
[Fractional Strain Energy] = T
[Normalized Strain Energy]/[diagonal 1.0 [Normalized
Strain Energy]]], term-by-term division.
Main Index
CHAPTER 5 483
Subcase Repeater
MODES (Case) Subcase Repeater
Repeats a subcase.
Format:
MODES=n
Example:
MODES=3
Describer Meaning
n Number of times the subcase is to be repeated (Integer > 0).
Remarks:
1. This Case Control command can be illustrated by an example. Suppose stress output is desired for
the first five modes only, and displacements for the next two modes, and forces for the remaining
modes. The following example would accomplish this:
SUBCASE 1 $ FOR MODES 1 THRU 5
MODES = 5
STRESS = ALL
SUBCASE 6 $ FOR MODES 6 AND 7
DISPLACEMENTS = ALL
MODES = 2
SUBCASE 8 $ FOR MODE 8 AND REMAINING MODES
FORCE = ALL
2. This command causes the results for each mode to be considered as a separate, successively numbered
subcase, beginning with the subcase number containing the MODES command. In the preceding
example, this means that subcases 1, 2, 3, etc. are assigned to modes 1, 2, 3, etc., respectively.
3. If this command is not used, eigenvalue results are considered to be a part of a single subcase.
Therefore, any output requests for the single subcase will apply for all eigenvalues.
4. All eigenvectors with mode numbers greater than the number of subcases defined in the Case Control
Section are printed with the descriptors of the last subcase. For example, to suppress all printout for
modes beyond the first three, the following Case Control commands could be used:
SUBCASE 1
MODES = 3
DISPLACEMENTS = ALL
SUBCASE 4
DISPLACEMENTS = NONE
BEGIN BULK
5. This command may be of no use in non-eigenvalue analysis and may cause data recovery processing
to be repeated.
Main Index
484 MSC Nastran Quick Reference Guide
Computed Mode Selection
MODESELECT (Case) Computed Mode Selection
Selects a subset of the computed modes for inclusion or exclusion in modal dynamic analysis.
Format:
Mode selection based on arbitrary mode numbers:
STRUCTURE
MODESELECT = n
FLUID
Alternate Format 1:
Mode selection based on number of lowest modes:
STRUCTURE
MODESELECT LMODES = lm
FLUID
Alternate Format 2:
Mode selection based on range of mode numbers:
STRUCTURE
MODESELECT LMODENM = lom HMODENM = him
FLUID
Alternate Format 3:
Mode selection based on frequency range:
STRUCTURE
MODESELECT LFREQ = lof HFREQ = hif UNCONSET = m
FLUID
Alternate Format 4:
Mode selection based on modal effective mass fraction (MEFFMFRA) criteria:
STRUCTURE
T1FR = t1fr T2FR = t2fr T3FR = t3fr
FLUID
R1FR = r1fr R2FR = r2fr R3FR = r3fr
MODESELECT
SUM
ALLFR = allfr UNCONSET = m ANYMIN
ALLMIN
See Remark 14. for examples illustrating the use of the preceding formats.
Main Index
CHAPTER 5 485
Computed Mode Selection
Describer Meaning
STRUCTURE References computed modes of the structure (Default).
FLUID References computed modes of the fluid.
n>0 Set identification of a previously appearing SET command. ONLY those modes
whose mode numbers are in SET n will be included in the analysis. If SET n is not
defined, then ONLY mode n will be included in the analysis (Integer).
n<0 |n| refers to the set identification of a previously appearing SET command. The
modes whose mode numbers are in SET |n| will be EXCLUDED from the analysis.
If SET |n| is not defined, then mode |n| will be EXCLUDED from the analysis
(Integer).
lm Number of lowest modes that are to included. (Integer > 0).
lom Lower limit of the mode number range for selecting the modes. See Remark 5.
(Integer > 0).
him Upper limit of the mode number range for selecting the modes. See Remark 5.
(Integer > lom > 0).
lof Lower limit of the frequency range for selecting the modes. See Remark 6. (Real >
0.0).
hif Upper limit of the frequency range for selecting the modes. See Remark 6. (Real > lof
> 0.0).
UNCONSET Specifies a single mode or a set of modes for unconditional inclusion or exclusion,
regardless of the selection criterion, and regardless of the inclusion or exclusion of
other modes.
m>0 Set identification of a previously appearing SET command. Modes whose mode
numbers are in SET m will be included in the analysis, regardless of the selection
criterion, and regardless of the inclusion or exclusion of other modes. If SET m is not
defined, then mode m will be included in the analysis, regardless of the selection
criterion, and regardless of the inclusion or exclusion of other modes (Integer).
m<0 |m| refers to the set identification of a previously appearing SET command. Modes
whose mode numbers are in SET |m| will be excluded from the analysis, regardless of
the selection criterion and regardless of the inclusion or exclusion of other modes. If
SET |m| is not defined, then mode |m| will be excluded from the analysis, regardless
of the selection criterion and regardless of the inclusion or exclusion of other modes
(Integer).
TiFR / RiFR Flags explicitly listing components whose modal effective mass fraction
(MEFFMFRA) values are to be considered for mode selection.
tifr / rifr Threshold values for the listed TiFR / RiFR components. See Remark 8. (0.0 < Real
< 1.0).
ALLFR Flag indicating that the MEFFMFRA values of components not explicitly listed by
the TiFR / RiFR flags are also to be considered for mode selection.
Main Index
486 MSC Nastran Quick Reference Guide
Computed Mode Selection
Describer Meaning
allfr Threshold value for components not explicitly listed by the TiFR / RiFR flags. See
Remark 8. (0.0 < Real < 1.0).
SUM For each specified component, the modes are selected as follows:
The modes are first sorted in descending order of the corresponding MEFFMFRA
values. Then, starting from the first mode in this sorted list, the modes are selected
until the sum of corresponding MEFFMFRA values equals or just exceeds the
threshold value for that component (Default).
ANYMIN Any mode whose MEFFMFRA value for any specified component equals or exceeds
the threshold value for that component will be selected.
ALLMIN Any mode whose MEFFMFRA values for all of the specified components equal or
exceed the corresponding threshold values for those components will be selected.
Remarks:
1. This command is meaningful only in modal dynamic analysis (SOLs 110, 111, 112, 145, 146, and
200). It is ignored in all other analyses.
2. Only one MODESELECT command is allowed for the structure and only one MODESELECT
command is allowed for the fluid and these should be specified above the subcase level.
3. The various formats of this command may not be combined.
4. The computed modes used for mode selection include the augmented modes (if any) resulting from
residual vector calculations.
5. If LMODENM is specified without HMODENM, a default value of 10000000 (ten million) is
assumed for HMODENM. If HMODENM is specified without LMODENM, a default value of 1
is assumed for LMODENM.
6. If LFREQ is specified without HFREQ, a default value of 1.0E+30 is assumed for HFREQ. If
HFREQ is specified without LFREQ, a default value of 0.0 is assumed for LFREQ.
7. If the format involving the MEFFMFRA criteria is employed, it is not necessary to specify a
MEFFMASS Case Control command or, even if such a command is specified, to explicitly request
the calculation of the modal effective mass fractions. In the absence of such a command or request,
the program will automatically perform the necessary calculations internally to ensure that the
required modal effective mass fractions are computed.
8. If the T1FR / R1FR / ALLFR keywords are specified without the corresponding tifr / r1fr / allfr
threshold values, then a default value of 0.95 (that is, 95%) is assumed for these threshold values. If
the selection criterion is SUM, and a default value of 0.05 (that is, 5%) is assumed if the selection
criterion is ANYMIN or ALLMIN.
9. The modal effective mass for a given mode is a measure of how much mass is associated with that
mode, and indicates the sensitivity of that mode to base excitation. Modal effective mass is
meaningful only for fixed base modes. If a structure is not restrained, all the modal effective mass will
be associated with its rigid body modes.
Main Index
CHAPTER 5 487
Computed Mode Selection
10. When the MODESELECT Case Control command is used in conjunction with the parameters
LMODES/LMODESFL, LFREQ/LFREQFL, and HFREQ/HFREQFL, the hierarchy of their
usage is as follows:
a. If there is a MODESELECT Case Control command, it takes precedence over the parameters
LMODES/LMODESFL, LFREQ/LFREQFL, and HFREQ/HFREQFL. (It does not matter
whether these parameters are defined directly via PARAM entries, or indirectly using the
FLSFSEL Case Control command.)
b. If there is no MODESELECT Case Control command, then parameter LMODES/LMODESFL
takes precedence over parameters LFREQ/LFREQFL and HFREQ/HFREQFL. In this case, the
number of lowest modes specified by LMODES/LMODESFL will be included in the modal
dynamic analysis.
c. If there is no MODESELECT Case Control command and no LMODES/LMODESFL
parameter, then parameters LFREQ/LFREQFL and HFREQ/HFREQFL are honored. In this
case, all of the computed modes whose frequencies are in the range specified by
LFREQ/LFREQFL and HFREQ/HFREQFL will be included in the modal dynamic analysis.
d. If there is no MODESELECT Case Control command and no LMODES/LMODESFL,
LFREQ/LFREQFL, or HFREQ/HFREQFL parameter, then all of the computed modes will be
included in the modal dynamic analysis.
11. If a subset of the computed modes is selected for subsequent use in the modal dynamic analysis, the
user is informed of this by a User Information Message. Also, a new eigenvalue table indicating the
actual modes selected for the analysis is output. If the user has employed a MODESELECT
command involving the MEFFMFRA criteria, the modal effective mass fractions for the selected
modes are also output.
12. If the mode selection criterion results in no modes being selected for subsequent use in the modal
dynamic analysis, the program terminates the job with a fatal message indicating that no modal
formulation is possible.
13. If the use of the MODESELECT command results in the selection of all of the computed modes for
subsequent use, the user is informed of this by a User Information Message.
14. The following examples illustrate the use of the various formats of the MODESELECT command
described above.
Examples Illustrating Mode Selection Based on Arbitrary Mode Numbers:
$ INCLUDE ONLY STRUCTURE MODES 7, 9 AND 12 IN THE ANALYSIS
SET 100 = 7,9,12
MODESELECT = 100
$ EXCLUDE FLUID MODES 5 AND 6 FROM THE ANALYSIS
SET 200 = 5,6
MODESELECT (FLUID)= -200
$ EXCLUDE STRUCTURE MODE 5 FROM THE ANALYSIS
MODESELECT = -5 $ (SET 5 NOT DEFINED)
Main Index
488 MSC Nastran Quick Reference Guide
Computed Mode Selection
Examples Illustrating Mode Selection Based on Number of Lowest Modes:
$ INCLUDE THE LOWEST 10 STRUCTURE MODES IN THE ANALYSIS
MODESELECT (LMODES = 10)
$ INCLUDE THE LOWEST 5 FLUID MODES IN THE ANALYSIS
MODESELECT (FLUID LMODES = 5)
Examples Illustrating Mode Selection Based on Range of Mode Numbers:
$ INCLUDE ONLY STRUCTURE MODES 10 THRU 20 IN THE ANALYSIS
MODESELECT (LMODENM = 10 HMODENM = 20)
$ INCLUDE ALL STRUCTURE MODES HIGHER THAN THE 6th MODE
$ IN THE ANALYSIS
MODESELECT (LMODENM = 7)
$ INCLUDE THE LOWEST 10 FLUID MODES IN THE ANALYSIS
MODESELECT (FLUID HMODENM = 10)
Examples Illustrating Mode Selection Based on Frequency Range:
$ INCLUDE ALL STRUCTURE MODES WITH CYCLIC FREQUENCIES
$ IN THE RANGE OF 0.1 HZ. TO 100.0 HZ. IN THE ANALYSIS
MODESELECT (LFREQ = 0.1 HFREQ = 100.0)
$ INCLUDE ALL STRUCTURE MODES WITH CYCLIC FREQUENCIES
$ EQUAL TO OR BELOW 50.0 HZ., BUT INCLUDE THE 10th AND 11th
$ MODES REGARDLESS OF THEIR CYCLIC FREQUENCIES
SET 1000 = 10, 11
MODESELECT (HFREQ = 50.0 UNCONSET = 1000)
$ INCLUDE ALL STRUCTURE MODES WITH CYCLIC FREQUENCIES
$ EQUAL TO OR ABOVE 5.0 HZ., BUT EXCLUDE THE 6 MODE
$ REGARDLESS OF ITS CYCLIC FREQUENCY
MODESELECT (LFREQ = 5.0 UNCONSET = -6) $ SET 6 NOT DEFINED
Examples Illustrating Mode Selection Based on Modal Effective Mass Fraction (MEFFMFRA)
Criteria:
MODESELECT (T3FR)
The default selection criterion of SUM is assumed, and a default value of 0.95 (95%) is therefore assumed
for the threshold value for component T3.
As many modes with the highest MEFFMFRA(T3) values as possible, such that the sum of the values is equal
to or just exceeds 0.95, will be selected.
MODESELECT (T1FR = 0.90 T2FR R3FR = 0.85)
The default selection criterion of SUM is assumed, and a default value of 0.95 (95%) is therefore assumed
for the threshold value for component T2.
As many modes with the highest MEFFMFRA(T1) values as possible, such that the sum of the values is equal
to or just exceeds 0.90, will be selected.
Similarly, as many modes with the highest MEFFMFRA(T2) values as possible, such that the sum of those
values is equal to or just exceeds 0.95, will be selected.
Main Index
CHAPTER 5 489
Computed Mode Selection
As many modes with the highest MEFFMFRA(R3) values as possible, such that the sum of those values is
equal to or just exceeds 0.85, will be selected.
MODESELECT (T1FR T3FR = 0.10 UNCONSET = -6 ANYMIN)
$ SET 6 NOT DEFINED
Since the selection criterion is specified as ANYMIN, a default value of 0.05 (5%) is assumed for the
threshold value for component T1.
All modes, excluding mode 6, whose:
MEFFMFRA(T1) values are equal to or greater than 0.05 OR
MEFFMFRA(T3) values are equal to or greater than 0.10
will be selected.
SET 1000 = 20, 30
MODESELECT (T2FR = 0.1 R3FR = 0.15 ALLFR UNCONSET = 1000 ALLMIN)
The ALLFR flag indicates that the T1, T3, R1, and R2 components which are not explicitly specified above
must also be considered in mode selection. Since the selection criterion is specified as ALLMIN, a default
value of 0.05 (5%) is assumed for the threshold value for these components.
All modes whose:
MEFFMFRA(T1) values equal or exceed 0.05 AND
MEFFMFRA(T2) values equal or exceed 0.10 AND
MEFFMFRA(T3) values equal or exceed 0.05 AND
MEFFMFRA(R1) values equal or exceed 0.05 AND
MEFFMFRA(R2) values equal or exceed 0.05 AND
MEFFMFRA(R3) values equal or exceed 0.15
will be selected.
Modes 20 and 30 will be selected regardless of their MEFFMFRA values.
Main Index
490 MSC Nastran Quick Reference Guide
Mode Tracking Request
MODTRAK (Case) Mode Tracking Request
Selects mode tracking options in design optimization (SOL 200).
Format:
MODTRAK = n
Example:
MODTRAK=100
Describer Meaning
n Set identification of a MODTRAK Bulk Data entry (Integer > 0).
Remark:
1. Selection of a MODTRAK Bulk Data entry with the MODTRAK Case Control command activates
mode tracking for the current subcase. This request is limited to normal modes subcases
(ANALYSIS=MODES) in design optimization (SOL 200).
MONCARL (Case) Control for Monte-Carlo simulation
Control for Monte-Carlo simulation using the non-parametric variability method (NPVM). This Case
Control command can be used in SOL 111 only.
Format:
MONCARL([NSAMPLE=m],[SEED=k],[OFFD= r])= n
Example:
MONCARL(NSAMPLE=100)=5
Describer Meaning
NSAMPLE = m Specifies the number of random samples, m ( Integer >=0, Default = 0).
SEED = k Specifies the random number generator seed, k (Integer > 0, Default = 777).
OFFD = r Specifies the scale factor for off-diagonal entries of the random matrix, r (Real,
Default = 1.0).
n Set identification number of a MONCARL Bulk Data entry (Integer > 0).
Remarks:
1. Only one MONCARL command may appear in the Case Control Section and should appear above
all SUBCASE commands.
Main Index
CHAPTER 5 491
Control for Monte-Carlo simulation
2. Keeping in mind the size and the naively parallel nature of Monte-Carlo problem typical simulation
would be run in a parallel mode. The parallel DMP simulation is restricted to Multi-Master mode in
order to get a good scalable performance. Multi-Master mode can be specified using
"RUNOPT=MULTIPAR", in "DOMAINSOLVER" Executive Control statement, e.g.:
DOMAINSOLVER ACMS (PARTOPT=DOF, RUNOPT=MULTIPAR)
3. Running the Monte-Carlo simulation in Nastran would result in a concatenated OP2, HDF5 and
PCH file containing the response results of each random sample of Monte-Carlo simulation. Each
random sample would appear as a unique subcase in the OP2, HDF5 and PCH file.
4. PLT Viewer (provided with Nastran) can be used to read the result of Monte-Carlo simulation to
generate meaningful response statistics. Currently the PLT Viewer can only read HDF5 and “PCH
files in SORT 1 format” (not OP2).
5. HDF5 is the recommended output method for reading into PLT Viewer. Use HDF5OUT entry
(preferred from V2022.2) or NASTRAN system cell (702) HDF5=1 to request HDF5 output.
Main Index
492 MSC Nastran Quick Reference Guide
Print Selection for Monitor Data
MONITOR (Case) Print Selection for Monitor Data
Specifies options in the printing of monitor data.
Note that MONITOR is not supported in NLPERF SOL 400.
Format:
REAL or IMAG ALL
MONITOR NODSP1 NOPNT1 NOPNT2 NOPNT3 =
PHASE NONE
Example:
MONITOR(PHASE,NOPNT1)=ALL
MONITOR(IMAG,NODSP1)=ALL
Describer Meaning
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output (Default).
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is
in degrees.
NODSP1 Do not include MONDSP1 results in the MONITOR point prints (default is to
provide these prints).
NOPNT1 Do not include MONPNT1 results in the MONITOR point prints (default is to
provide these prints).
NOPNT2 Do not include MONPNT2 results in the MONITOR point prints (default is to
provide these prints).
NOPNT3 Do not include MONPNT3 results in the MONITOR point prints (default is to
provide these prints).
ALL Print all monitor point results, except for those deselected.
NONE Do not print monitor point results
Remarks:
1. The MONITOR command is required in order to obtain MONITOR results in the printed output
in SOLs 101, 103, 108, 109, 111, 112, 146, 200 and 400 (ANALYSIS = NLSTAT or NLTRAN).
2. SOL 144 does not require the MONITOR command and is ignored.
3. The MONITOR command should be above the subcase level or in the first subcase (above the step
level for SOL 400). MONITOR commands in subcases subsequent to the first one or in any steps for
SOL 400 are ignored.
4. MONPNT1 is not applicable in SOL 103.
Main Index
CHAPTER 5 493
Print Selection for Monitor Data
5. The MONITOR command is not required for SOL 144 except in the special case of MONPNT3
with any exclusion flags other than SMAD. Monitor points with exclusion flags require special
processing of the GRID point force data and are not recommended because of the potential excessive
cost.
6. Results for dynamic solutions (SOLs 108, 109, 111, 112, 146 and 400 with NLTRAN) will be in
SORT2 format. All other solutions will be in SORT1 format.
Output Format:
In frequency response analysis, there is no output format of complex energy.
For SOLS 101, 103, and 144 - SORT1:
S T R U C T U R A L I N T E G R A T E D F R E E B O D Y M O N I T O R P O I N T L O A D S (MONPNT3)
MONITOR POINT NAME = FORCSM1 SUBCASE NO. 1
LABEL = SUMMATION OF FORCES AT GRID 9
CP = 0 X = 8.00000E+01 Y = 0.00000E+00 Z = 0.00000E+00
AXIS REST. APPLIED
---- -------------
CX 1.600000E+01
CY 1.600000E+01
CZ 1.600000E+01
CMX 0.000000E+00
CMY -3.200000E+02
CMZ 3.200000E+02
This format repeats for each monitor point and repeats for each subcase or mode.
SOLs 108, 109, 111, 112 and 146 - SORT2:
S T R U C T U R A L I N T E G R A T E D F R E E B O D Y M O N I T O R P O I N T L O A D S (MONPNT3)
MONITOR POINT NAME = FORCSM1 COMPONENT = CX SUBCASE NO. 1
LABEL = SUMMATION OF FORCES AT GRID 9
CP = 0 X = 8.000000E+01 Y = 0.000000E+00 Z = 0.000000E+00
TIME STEP RESULTANT
------------ ------------
0.000000E+00 0.000000E+00
1.000000E-02 7.692307E-01
2.000000E-02 1.301775E+00
3.000000E-02 1.137915E+00
4.000000E-02 6.557894E-01
5.000000E-02 9.679956E-01
6.000000E-02 1.354058E+00
7.000000E-02 9.230635E-01
8.000000E-02 6.696146E-01
9.000000E-02 1.178594E+00
9.999999E-02 1.275434E+00
This format repeats for each monitor point.
Main Index
494 MSC Nastran Quick Reference Guide
Multipoint Constraint Set Selection
MPC (Case) Multipoint Constraint Set Selection
Selects a multipoint constraint set.
Format:
MPC = n
Example:
MPC=17
Describer Meaning
n Set identification number of a multipoint constraint set. This set identification
number must appear on at least one MPC or MPCADD Bulk Data entry
(Integer > 0).
Remarks:
1. In cyclic symmetry analysis, this command must appear above the first subcase command.
2. Multiple boundary conditions (MPC sets) are not allowed in superelement analysis. If more than one
MPC set is specified per superelement (including the residual), then the second and subsequent sets
will be ignored.
3. In addition to select MPC/MPCADD bulk data entries, MPC=n can also be used to select a group
of rigid elements for the analysis via SET3,n bulk data entry with RBEin or RBEex in DES field of
SET3 bulk data entry.
4. SET3,n is not needed if ALL rigid elements in the model are to be utilized.
5. Rigid element set section is supported in SOL 400 if 'RIGID=LINEAR' is present in case control
deck.
Main Index
CHAPTER 5 495
Multipoint Forces of Constraint Output Request
MPCFORCES (Case) Multipoint Forces of Constraint Output Request
Requests the form and type of multipoint force of constraint vector output.
Format:
SORT1 PRINT PUNCH REAL or IMAG PSDF,ATOC,CRMS
MPCFORCES ( ,
SORT2 PLOT PHASE or RALL
ALL
RPRINT
RPUNCH , CID ) = n
NORPRINT
NONE
Examples:
MPCFORCES=5
MPCFORCES(SORT2, PUNCH, PRINT, IMAG)=ALL
MPCFORCES(PHASE)=NONE
MPCFORCES(SORT2, PRINT,PSDF, CRMS, RPUNCH)=20
MPCFORCES(PRINT, RALL, NORPRINT)=ALL
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load,
frequency, eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid
point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAGE Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output
is in degrees.
Main Index
496 MSC Nastran Quick Reference Guide
Multipoint Forces of Constraint Output Request
Describer Meaning
PSDF Requests that the power spectral density function be calculated and stored in
the database for random analysis postprocessing. Request must be made above
the subcase level, and RANDOM must be selected in the Case Control Section.
See Remark 8.
ATOC Requests the autocorrelation function be calculated and stored in the database
for random analysis postprocessing. Request must be made above the subcase
level, and RANDOM must be selected in the Case Control Section. See
Remark 8.
CRMS Requests the cumulative root mean square function be calculated for random
analysis postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in the Case Control Section. See Remark 8.
RALL Requests all of PSDF, ATOC, and CRMS be calculated for random analysis
post-processing. Request must be made above the subcase level, and
RANDOM must be selected in the Case Control Section. See Remark 8.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
RPUNCH Writes random analysis results in the punch file.
CID Request the printing of output coordinate system ID in printed output file
(.f06) file.
ALL Multipoint forces of constraint for all points will be output. See Remarks 2.
and 5.
NONE Multipoint forces of constraint for no points will be output.
n Set identification of a previously appearing SET command. Only multipoint
constraint forces for points with identification numbers that appear on this SET
command will be output (Integer > 0).
Remarks:
1. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2. In the SORT1
format, only nonzero values will be output.
2. In a statics problem, a request for SORT2 causes loads at all points (zero and nonzero) to be output.
3. MPCFORCES=NONE overrides an overall output request.
4. In SORT1 format, MPCFORCEs recovered at consecutively numbered scalar points are printed in
groups of six (sextets) per line of output. However, if a scalar point is not consecutively numbered,
then it will begin a new sextet on a new line of output. If a sextet can be formed and all values are
zero, the line will not be printed. If a sextet cannot be formed, then zero values may be output.
5. MPCFORCE results are output in the global coordinate system (see field CD on the GRID Bulk
Data entry).
Main Index
CHAPTER 5 497
Multipoint Forces of Constraint Output Request
6. MPCFORCE results due to linear elements only are available in SOL 129 with MDLPRM,
MPCF129, 1.
7. In inertia relief analysis, the MPCFORCE output includes both the effects of applied and inertial
loads.
8. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
9. Note that the CID keyword affects only grid point related output, such as DISPlacement, VELO,
ACCE, OLOAD, SPCForce and MPCF. In addition, the CID keyword needs to appear only once
in a grid related output request anywhere in the Case Control Section to turn on the printing
algorithm.
Main Index
498 MSC Nastran Quick Reference Guide
Fluid Pressure Output Request
MPRES (Case) Fluid Pressure Output Request
Requests the pressure for selected wetted surface elements when virtual mass (MFLUID) is used.
Format:
ALL
PRINT, PUNCH REAL or IMAG
MPRES ( ) = n
PLOT PHASE
NONE
Examples:
MPRES=5
MPRES(IMAG)=ALL
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in
Bulk Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being
deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output
is in degrees.
ALL Fluid pressures for all elements will be output.
NONE Fluid pressures for no elements will be output.
n Set identification number of a previously appearing SET command. Only fluid
pressures for elements in this set will be output (Integer >0).
Remark:
1. If PARAM,SPARSEDR,NO is specified, then PARAM,DDRMM,-1 is also required in the modal
solution sequences (SOLs 111, 112, 146, and 200).
Main Index
CHAPTER 5 499
SOL128 Nonlinear iteration output request
NHRMITR (Case) SOL128 Nonlinear iteration output request
Selects set for nonlinear harmonic analysis iterative displacement and nonlinear load outputs.
Format:
none none
NHRMITR DISP = ---------------- NLLOAD = ----------------
setdof setdof
Examples:
set 30=200/t2,200/t3,200/r1,200/r2,500/t2,500/t3,500/r1
set 20=200/t2,200/t3,500/t2,500/t3
NHRMITR DISP=30, NLLOAD=30
NHRMITR DISP=30
NHRMITR NLLOAD=30
Describer Meaning
DISP Requests displacement outputs for selected set of grids and its dofs at end of
each iteration.
NLLOAD Requests nonlinear load outputs for selected set of grids and its dofs at end of
each iteration.
Remark:
1. The outputs will be in CSV file format only.
2. DISP and NLLOAD requests will create individual CSV file.
3. The file name will be jobname_disp.csv and jobname_nlload.csv
Main Index
500 MSC Nastran Quick Reference Guide
Nonlinear Buckling Request
NLBUCK (Case) Nonlinear Buckling Request
Perform a nonlinear buckling analysis in SOL 400.
Note that NLBUCK is not supported in NLPERF SOL 400.
Format:
END
NLBUCK = ALL
r
Examples:
NLBUCK
NLBUCK=END
NLBUCK=ALL
NLBUCK=0.3
Describer Meaning
END At the end of the step an eigenvalue projection is made to predict the buckled
load (Default).
ALL After each converged load increment within the step an eigenvalue projection is
made to predict the buckled load.
r After every multiple of r load step an eigenvalue projection is made to predict
the buckled load. Buckling will also be computed at the final load increment. A
tolerance of 1.E-6 is used to determine the load step's closeness to r. (Real)
Remark:
1. The eigenvalue projection is only attempted after the first two converged load increments in order for
there to be at least two tangent stiffness matrices for the projection.
2. NLBUCK may be specified in any STEP or SUBCASE along with an NLSTEP command. The
NLPARM command is not allowed with NLBUCK.
3. In order to obtain the most accurate value for critical buckling factor, the user must set NO=1 on the
NLSTEP entry. Specifying PARAM,LGDISP>0 is also recommended.
4. In addition to NLBUCK, a METHOD Case Control command may be specified to reference an
EIGB, EIGR or EIGRL Bulk Data entry, or if asymmetric follower stiffness exists then a
CMETHOD Case Control command may be specified to reference an EIGC entry. The EIGx entries
should request the computation of at least the first mode. If no METHOD/CMETHOD command
Main Index
CHAPTER 5 501
Nonlinear Buckling Request
is present, a minimum of two eigenvalues are extracted for the buckling projection using an eigenvalue
extraction method appropriate for the form of the tangent stiffness (symmetric or asymmetric). For
manual control of follower stiffness symmetry see the description of user PARAMeters FOLLOWK
and FKSYMFAC.
5. If NLBUCK=0.3 and the TOTTIME on the NLSTEP Buck Data entry is 1.0 then the buckling will
be computed at load steps 0.3, 0.6, 0.9, and 1.0. Also, if the load factor is not a multiple of r then
the next load factor will be used; for example, if TOTIME=1.0 and there are 50 load increments and
r=.45 then buckling will be computed at load factors 0.46, 0.90, and 1.0.
6. There are three methods of eigenvalue extraction available for nonlinear buckling—Lanczos (EIGRL
or EIGR entry with METHOD=LAN), enhanced inverse power method (EIGB entry with
METHOD=SINV), and complex (EIGC entry) for unsymmetric stiffness due to follower stiffness.
a. If no METHOD and no CMETHOD command is specified, then the program will
automatically attempt to compute two modes (ND=2) with an unspecified eigenvalue range (F1
and F2) using the real Lanczos method if the stiffness matrix is symmetric or the complex Lanczos
method if the stiffness matrix is unsymmetric.
b. The Lanczos method is recommended in most cases especially in finding the lowest mode.
c. If no modes can be found with no eigenvalue range was specified, then it is highly recommended
that a range (L1 and L2 on EIGB, F1 and F2 on EIGR, and V1 and V2 on EIGRL) be specified.
d. If higher modes are desired, then the enhanced inverse power method is recommended with a
narrow eigenvalue range specified for L1 and L2 on the EIGB entry.
e. If a METHOD command is specified but the stiffness is unsymmetric then User Warning
Message 9430 will be issued.
7. Guidelines and limitations:
a. NLPARM Case Control command is not permitted in a nonlinear buckling step. NLSTEP must
be specified in the nonlinear buckling step and KMETHOD=PFNT (default) is strongly
recommended along with NO=1 for FIXED time stepping or INTOUT=YES for ADAPT time
stepping. If KMETHOD=ITER then KSTEP=1 is strongly recommended.
b. It is strongly recommended that PARAM,LGDISP,1 is specified.
c. It is strongly recommended to specify an eigenvalue range on the EIGR, EIGRL, EIGB, and
EIGC Bulk Data entries. But with NLBUCK=ALL it may be difficult to define a range for all load
increments.
d. When using NLBUCK in contact analysis with general glued or touching contact, it should be
noted that if contact status changes between the increment in which nonlinear buckling is
calculated and its previous increment, the result of NLBUCK may be not reliable
Main Index
502 MSC Nastran Quick Reference Guide
Nonlinear Harmonic Analysis Parameter Selection
NLHARM (Case) Nonlinear Harmonic Analysis Parameter Selection
Selects the parameters used for nonlinear harmonic response analysis.
Format:
NLHARM = n
Example:
NLHARM = 79
Describer Meaning
n Set identification of NLHARM Bulk Data entry. (Integer > 0)
Remarks:
1. This entry references the NLHARM Bulk Data entry which defines the number of subharmonics and
harmonics to be used in the analysis as well as referencing the excitation frequency specification.
2. Gyroscopic terms are included if the RGYRO Case Control command and Bulk Data entry are
specified. If gyroscopic terms are desired, the user must specify the constant rooter speed (ASYNC
option) for the reference rotor.
Main Index
CHAPTER 5 503
Nonlinear Initial Condition or Preload
NLIC (Case) Nonlinear Initial Condition or Preload
Selects a previously executed load increment as the initial conditions or preload for a nonlinear or
perturbation STEP in SOL 400.
Note that NLIC is not supported in NLPERF SOL 400.
Format:
NLIC SUBCASE i STEP j LOADFACT T = tol f
TIME NEAR
Example:
NLIC SUBCASE 100 STEP 10 LOADFACT 0.8
NLIC SUBCASE 100 STEP 10 LOADFACT (t=0.01) 0.66
NLIC STEP 10 TIME 12.0
NLIC TIME NEAR 7.8
Describer Meaning
SUBCASE Keyword to select the SUBCASE ID
i Specifies the identification number of a previously executed subcase. (Integer > 0;
Default is the subcase where the current NLIC is located).
STEP Keyword to select the STEP ID.
j Specifies the identification number of a previously executed STEP (Integer > 0,
Default is the last STEP).
LOADFACT Keyword to select load factor or time. Both keywords are equivalent.
TIME
f Specifies the load factor of a previously executed load increment in linear or
nonlinear static analysis (Real > 0.0, see Remark 3 for default).
T Keyword to select the tolerance.
NEAR Keyword for the nearest load factor or time to f.
tol Specified the load factor or time tolerance to f. (Real > 0.0; Default = 1.0E-06)
Remarks:
1. The NLIC command can only point to a load increment whose output flag is on - an available restart
point in the static analysis. If NLIC is not pointing to an available restart point, a fatal error will be
issued and the job will be terminated.
2. The NLIC can be used in nonlinear static, nonlinear transient and perturbation analysis. If
SUBCASE referred in NLIC is not the current SUBCASE, this usage is not recommended. The
system(779) = 1 may be used to avoid this usage, which stops the job in this case.
Main Index
504 MSC Nastran Quick Reference Guide
Nonlinear Initial Condition or Preload
3. For nonlinear transient analysis (ANALYSIS=NLTRAN), NLIC can only appear in the first transient
analysis STEP in a SUBCASE. (Note that the first transient analysis step may not be the first step of
subcase.) Otherwise, it will be ignored and a warning message will be issued.
4. For linear perturbation analysis, NLIC must point to a previous NLSTATIC step in the same
SUBCASE.
5. If NLIC is specified without any of the keywords, or NLIC is not present in a nonlinear STEP or
perturbation STEP, the initial condition or PRELOAD is taken from the last available restart point
in the immediate previous static step.
6. In the same nonlinear transient step, NLIC cannot appear together with the IC Case Control
command. A fatal error message will be issued if NLIC and IC appear in the same step. Please note
that IC is meaningful only in the first STEP of a SUBCASE, and the step is a nonlinear transient
analysis.
7. When Keyword NEAR is used, the search for the nearest load factor or time is limited inside the
specified SUBCASE i STEP j.
8. NLIC can be used in SOL 400 only.
9. If NLIC is used with ANALYSIS=NLSTATIC it may cause convergence problems. If NLIC is used
across different subcases: the initial conditions, the deformation, the strains, the stresses, etc., are
carried over between Subcases. However, the load is NOT carried over. This can cause an unbalanced
load condition that may cause convergence problems.
Main Index
CHAPTER 5 505
Nonlinear Load Output Request
NLLOAD (Case) Nonlinear Load Output Request
Requests the form and type of nonlinear load output for transient problems.
Format:
ALL
NLLOAD PRINT, PUNCH = n
NONE
Example:
NLLOAD=ALL
Describer Meaning
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
ALL Nonlinear loads for all solution points will be output.
NONE Nonlinear loads will not be output.
n Set identification of a previously appearing SET command. Only nonlinear loads for
points with identification numbers that appear on this SET command will be output
(Integer > 0).
Remarks:
1. Nonlinear loads are output only in the solution (d or h) set.
2. The output is available in SORT2 format only.
3. Both PRINT and PUNCH may be used.
4. NLLOAD=NONE allows overriding an overall output request.
Main Index
506 MSC Nastran Quick Reference Guide
Nonlinear Regular and Debug Output Control Parameters - SOL 400
NLOPRM (Case) Nonlinear Regular and Debug Output Control Parameters - SOL 400
Controls MSC Nastran nonlinear solution output, debug printout, debug POST and punch-out of contact
constraints of MPC and MPCY Bulk Data entries.
For its usage in NLPERF SOL 400, refer to NLOPRM (CASE) in the Ap. C: NLPERF SOL 400.
Format:
NLOPRM = OUTCTRL = STD,SOLUTION,INTERM
NONE
N3DBAS
NLDBG = N3DMED
NLBASIC,NRDBG,ADVDBG,
N3DADV
N3DSUM
NONE
LTIME NONE
DBGPOST = LSTEP MPCPCH = BEGN,OTIME,STEP
LSUBC YBEGN,YOTIME,YSTEP
ALL
DELIMIT= No
Yes
No
GRIDINF= MAXGRID
GID
Example(s):
NLOPRM OUTCTRL=STD,SOLUTION DBGPOST=LTIME
NLOPRM OUTCTRL=(SOLUTION,INTERM), MPCPCH=(OTIME,STEP)
Describer Meaning
OUTCTRL Selects one or more following nonlinear solution output options
STD Standard Nastran output (Default)
SOLUTION Solution set output which does not include solutions for superelements
Main Index
CHAPTER 5 507
Nonlinear Regular and Debug Output Control Parameters - SOL 400
Describer Meaning
INTERM Intermediate nonlinear solution output in OP2 and HDF5 files, at each
solution output interval, set by the user through nonlinear solution
controls, such as NLPARM.
NLDBG Keyword selecting one or more debug printout options
NONE No debug print output (Default)
NLBASIC Basic nonlinear information printout
NRDBG Newton-Raphson iteration information printout
ADVDBG Advance nonlinear debug printout
N3DBASE For 3D contact, it requests to print out the error tolerance of each
contact body in the F06 file.
N3DMED For 3D contact, it requests to print out the summary table of all contact
parameters, in addition to the printout by N3DBAS, in the .f06 file.
N3DADV For 3D contact, it requests to print out the body contact information in
long form, in addition to the printouts by both N3DBAS and
N3DMED, in the F06 file.
N3DSUM For 3D Contact, it simplifies body contact information in N3DADV.
DBGPOST Selects one of the following debug POST options
NONE No output (Default)
LTIME To output all iterations in the last load or time increment
LSTEP To output all iterations in the last STEP
LSUBC To output all iterations in the last SUBCASE
ALL To output all iterations
MPCPCH Selects one or more following options to punch out contact constraint equations in terms
of MPC or MPCY Bulk Data entries in Nastran PCH file. This is not available for
segment-to-segment contact.
NONE No MPC or MPCY punch output (Default)
BEGN MPC punch in the beginning of the very first iteration
OTIME MPC punch at every user requested output step
STEP MPC punch at the end of each load case, such as SUBSTEP, STEP and
SUBCASE
YBEGN MPCY punch in the beginning of the very first iteration
YOTIME MPCY punch at every user requested output step
YSTEP MPCY punch at the end of each load case, such as SUBSTEP, STEP
and SUBCASE)
DELIMIT Select output of delimiter for subcases, steps, increments, and iterations.
Main Index
508 MSC Nastran Quick Reference Guide
Nonlinear Regular and Debug Output Control Parameters - SOL 400
Describer Meaning
No No output (default)
Yes Select output
GRIDINF Select output of grid point information (1) displacements of the grid; (2) EID: element
ID connected to this grid; (3) PID: property ID of relevant elements; (4) ID of contact
body which the grid belongs to; and, (5) if the grid locates on the surface of contact body.
No No output (default)
MAXGRID Output information of grid which has maximum displacement
component
GID Output information of grid which user specifies
Remarks:
1. This Case Control command is used to better control nonlinear solution output during solution
process, to provide MSC users a direct access to nonlinear solutions even the job is still running, to
give the users some tools to debug the nonlinear solution process and gain some insight of nonlinear
solution procedure, and to allow users to print out MPC and MPCY equations from contact
constraints before and during solution process.
2. OUTCTRL=SOLUTION is designed to debug nonlinear analysis which may fail during the analysis.
For other selections, some results such as displacement, SPC force, and so on, are written into F06
file only after the analysis is finished completely. This is helpful for user to understand the nonlinear
analysis when job is terminated abnormally. With OUTCTRL=SOLUTION, only part of the results
will be output. Availability of output request for debugging purposes are summarized at the following
table.
Output Request OP2 F06
BOUTPUT NO YES
DISPLACEMENT YES YES
GPFORCE NO NO
MPCFORCES YES YES
NLSTRESS NO YES
OLOAD YES YES
SPCFORCES YES YES
STRESS NO NO
STRAIN NO NO
Main Index
CHAPTER 5 509
Nonlinear Regular and Debug Output Control Parameters - SOL 400
Please note that OP2 file only includes the results at the end time of every load step, instead of the
user-specified output intervals assigned in NLSTEP or NLPARM. It is recommended to use
OUTCTRL=SOLUTION,INTERM to get nonlinear solutions in both F06 and intermediate OP2
files for debugging purposes.
3. For OUTCTRL = INTERM, the intermediate ouptut is only available in OP2 file. GPFORCE is not
available in intermediate OP2 files and can be obtained by OUCTRL=STD.
4. For NLDBG, all nonlinear information is printed out in only F06 file.
5. For DBGPOST, all nonlinear information is printed out in the MASTER/DBALL.
6. For MPCPCH, it is a punch output that MPC and MPCY requests cannot be mixed.
7. In MPCPCH punch output, it is restricted that SID=1 for a general contact and SID=2 for the glued
contact.
8. When using MPCPCH for the permanent glued contact, user may specify any keyword of BEGN,
STEP and OTIME to punch output MPC type of constraints, or any keyword of YBEGN, YSTEP
and YOTIME to punch out MPCY type of constraints.
9. The output to the file is also influenced by the NLPACK Param. For example, one NLTRAN analysis
has NLSTEP as:
NLSTEP,900,0.2
,fixed,2000,20
,mech,u
It has total 2000 increments, and is asked output every 20 increments. Therefore, total output is 100
time step. In NASTRAN, default value of NLPACK is 100, in this model, therefore, NASTRAN will
write the results to OP2 after collecting 100 output, i.e., this model will write results to OP2 only one
time. With "intermediate output request, you will have only one OP2 file.
If NLPACK=1, NASTRAN will write results to OP2 for every output request. In this model,
NASTRAN will write results to OP2 for every output request, i.e., writing 100 times in this model.
With "intermediate output request, you will have 100 OP2 files.
If NLPACK=2, NASTRAN will write results to OP2 for every two output requests. In this model,
NASTRAN will write results to OP2 for every two output request, i.e., writing 50 times in this model.
With "intermediate output request, you will have 50 OP2 files.
10. MPCPCH is not supported in thermal contact with DQNEAR because MPC constraints do not
apply to the near thermal contact behavior.
Main Index
510 MSC Nastran Quick Reference Guide
Nonlinear Static Analysis Parameter Selection
NLPARM (Case) Nonlinear Static Analysis Parameter Selection
Selects the parameters used for nonlinear static analysis.
Format:
NLPARM = n
Example:
NLPARM=10
Describer Meaning
n Set identification of NLPARM and NLPCI Bulk Data entries (Integer > 0).
Remarks:
1. NLPARM and NLPCI Bulk Data entries will not be used unless selected.
2. NLPARM may appear above or within a subcase.
3. If NLSTEP specified, NLPARM command will be ignored.
Main Index
CHAPTER 5 511
Nonlinear Restart Request
NLRESTART (Case) Nonlinear Restart Request
Request a RESTART execution at a specified point for SOL 400.
Please note that when running NLRESTART with Advanced Nonlinear Element, the Data Blocks for
Advanced Nonlinear Element must be saved in the corresponding cold start run with the proper DBSAVE,
NLPACK, and INTOUT. See Remark 12.
Format:
NLRESTART SUBCASE i STEP j , LOADFAC f OVERRIDE
TIME t
Example:
NLRESTART SUBCASE 1, STEP 2, LOADFAC 0.3
Describer Meaning
i Specifies the identification number of a previously executed SUBCASE (Integer;
Default is the first SUBCASE).
j Specifies the identification number of a previously executed STEP (Integer; Default
is the first STEP).
f Specified the load factor of a previously executed load increment in nonlinear static
analysis (Real; 0.0 < f < 1.0; Default = 1.0).
t Specified the time of a previously executed time step in nonlinear transient analysis
(Real; t 0 t t n , where t 0 is the initial time of STEP j, and t n is the last time of
STEP j; Default = t n ).
OVERRIDE To force the run to continue even though there are fundamental changes to the
model's geometry, properties, and/or connectivity. In general, NLRESTART does
not allow changes to the model's geometry, properties, or connectivity and UFM
9424 will be issued if a change is detected. Please be cautious in using OVERRIDE
because the model changes may result in wrong answers and/or a fatal termination
and, therefore, is not recommended in all cases.
Remarks:
1. The NLRESTART command can be used in SOL 400 (NONLIN) only.
2. The NLRESTART command must appear before any SUBCASE command.
3. To perform a restart, the data base for the original run must be made available by using the ASSIGN
File Management statement or other equivalent method.
Main Index
512 MSC Nastran Quick Reference Guide
Nonlinear Restart Request
4. The restart run can only be executed at a load increment (or time step) whose output flag is on an
available restart point. (See the field INTOUT on the NLPARM Bulk Data entry, and NO on ).
When a user-specified restart point is not available, the closest previous restart point that is available
will be applied automatically.
5. If only NLRESTART is specified, a restart begins from the last available restart point in the previous
run. Otherwise, at lease one set of the SUBCASE i, STEP j, or LOADFC f (or TIME t) must be
specified.
6. In static analysis, f is reset to 0.0 when f < 0.0, and it makes the restart begin from the beginning of
STEP j. f is reset to 1.0 when f > 1.0, which makes the restart begin from the beginning of the next
STEP (after STEP j).
7. In transient analysis, t is reset to t 0 when t < t 0 , and it makes the restart begin from the beginning
of STEP j. t is reset to t n when t > t n , which makes the restart begin from the beginning of the next
STEP (after STEP j).
8. The NLRESTART Case Control command must contain all of the commands used in the original
execution up to the point where the restart is requested.
9. All data contained on the database from the restart point will be deleted when the restart begins.
10. When using NLRESTART, its corresponding COLD START input model should not use
"PARAM,DBALL,SCRATCH", which will remove the database required for NLRESTART after
completion of COLD START run.
11. NLRESTART is used for Nonlinear Restart Request. The restart step must be a nonlinear analysis,
NLSTAT or NLTRAN. NLRESTART from perturbation step or thermal analysis step is not
supported in SOL400.
12. DBSAVE in the Case Control Section is used to control saving of datablocks of advanced nonlinear
elements for static and transient nonlinear analysis in SOL 400.
-1 No datablocks of advanced nonlinear elements is saved
0 Saving datablocks of advanced nonlinear elements at the end of each loadcase
(default)
>0 Saving datablocks of advanced nonlinear elements at the every nth output request
of results
In DBSAVE=0, NLRESTART may start at the end of the loadcase (load step) for advanced nonlinear
elements. If DBSAVE=n (>0), NLRESTART may start at the every INTOUT* n th output point.
For NLTRAN analysis in SOL 400, the output to the file, i.e., NLRESTART usage, is also influenced
by the NLPACK Param. For example, one NLTRAN analysis has NLSTEP as:
NLSTEP, 900, 0.2
,fixed, 2000, 20
,mech, u
Main Index
CHAPTER 5 513
Nonlinear Restart Request
It has total 2000 increments, and is asked output every 20 increments. Therefore, total output is 100
time step. In NASTRAN, default value of NLPACK is 100, in this model, therefore, NASTRAN will
write the results to OP2 after collecting 100 output, i.e., this model will write results to OP2 only one
time. With intermediate output request, you will have only one OP2 file.
If NLPACK=1, NASTRAN will write results to OP2 for every output request. In this model,
NASTRAN will write results to OP2 for every output request, i.e., writing 100 times in this model.
With intermediate output request, you will have 100 OP2 files.
If NLPACK=2, NASTRAN will write results to OP2 for every two output requests. In this model,
NASTRAN will write results to OP2 for every two output request, i.e., writing 50 times in this model.
With intermediate output request, you will have 50 OP2 files.
Similarly, NLRESTART can be started at those output points ONLY.
13. When NLRESTART is used with Advanced Nonlinear Elements in a linear perturbation analysis, if
the cold start run is not a linear perturbation analysis itself, then MDLPRM,NLRSTRTM,1 must be
used in the cold start run to allow proper memory allocation between the two runs.
Main Index
514 MSC Nastran Quick Reference Guide
Nonlinear Control Parameters for Mechanical, Thermal, and Coupled Analysis Selection
NLSTEP (Case) Nonlinear Control Parameters for Mechanical, Thermal, and Coupled Analysis
Selection
Selects integration and output time steps for static and transient nonlinear analysis in SOL 400.
Format:
NLSTEP=n
Example:
NLSTEP=10
SUBSTEP=1
ANALYSIS=HSTAT
SUBSTEP=2
ANALYSIS=NLSTAT
Describer Meaning
n Identification number of a NLSTEP Bulk Data entry. (Integer > 0).
Remarks:
1. An NLSTEP entry can be selected to execute a nonlinear static or nonlinear transient analysis in
SOL 400. A NLSTEP is used in lieu of a NLPARM or both.
2. If a NLSTEP is present anywhere in a SUBCASE, then any NLPARM or entries in the SUBCASE
will be ignored.
3. When used for coupled analysis, the NLSTEP must be above the first SUBSTEP command. A single
NLSTEP entry is used for all SUBSTEPs of the STEP. (See the above example for use with coupled
analysis.)
4. NLSTEP command is only supported in SOL 101 linear contact analysis and SOL 400. If NLSTEP
specified, TSTEP/NLPARM command will be ignored.
Main Index
CHAPTER 5 515
Nonlinear Element Stress Output Request
NLSTRESS (Case) Nonlinear Element Stress Output Request
Requests the form and type of nonlinear element stress output in SOLs 106 and 400.
Format:
ALL
SORT1 PRINT, PUNCH
NLSTRESS ( NLOUT = m ) = n
SORT2 PLOT
See Remark 3
Examples:
NLSTRESS=5
NLSTRESS (SORT1,PRINT,PUNCH,PHASE)=15
NLSTRESS(PLOT)=ALL
NLSTRESS(NLOUT=23)=ALL
Describer Meaning
SORT1 Output will be presented as a tabular listing of elements for each load.
SORT2 Output will be presented as a tabular listing of load for each element type.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Stresses for all nonlinear elements will be output.
n Set identification of a previously appearing SET command. Only stresses for elements
with identification numbers that appear on this SET command will be output
(Integer > 0).
NONE No nonlinear element stress will be output (Default).
NLOUT For SOL 400 only. Allows the selection of additional types of nonlinear output.
m Identification of a NLOUT Bulk Data entry. (Integer > 0)
Main Index
516 MSC Nastran Quick Reference Guide
Nonlinear Element Stress Output Request
Remarks:
1. ALL should not be used in a transient problem due to potentially excessive output.
2. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
3. If there is a stress request, the default output set is that of the STRESS request.
4. For NLTRAN analysis, NLSTRESS does not support SORT1 selection.
Main Index
CHAPTER 5 517
Nonlinear Dynamic Load Set Selection
NONLINEAR (Case) Nonlinear Dynamic Load Set Selection
Selects nonlinear dynamic load set for transient response or nonlinear harmonic response problems.
Format:
NONLINEAR = n
Example:
NONLINEAR=75
Describer Meaning
n Set identification of NOLINi, NLRGAPor NLRSFD Bulk Data entry (Integer > 0).
Remark:
1. Nonlinear force Bulk Data entries (NOLINi, NLBSH3D, NLRGAP or NLRSFD) will be ignored
unless selected in the Case Control Section.
2. At least one degree of freedom must be defined on a nonlinear force entry and called up by the
NONLINEAR Case Control command in nonlinear harmonic response.
Main Index
518 MSC Nastran Quick Reference Guide
Normal Output Request in Cyclic Symmetry Problems
NOUTPUT (Case) Normal Output Request in Cyclic Symmetry Problems
Requests physical output in cyclic symmetry problems.
Format:
NOUTPUT k, R = ALL
L m
Examples:
NOUTPUT (R)=ALL
NOUTPUT (2)=5
NOUTPUT (4,L)=10
Describer Meaning
ALL Output for all segments is desired.
m Output for segments specified in SET m is desired (Integer > 0).
k Used in eigenvalue analysis to request eigenvector and internal force output for
harmonics specified in SET k (Integer > 0).
R, L Output for only the right- or left-half of segments specified as ALL or in SET m.
R and L are used in dihedral symmetry only.
Remarks:
1. Sets k and m are defined on SET commands.
2. In cyclic symmetry analysis, this command, or the HOUTPUT command, is required to obtain data
recovery.
Main Index
CHAPTER 5 519
Selects Nonstructural Mass Set Entries
NSM (Case) Selects Nonstructural Mass Set Entries
Selects nonstructural mass (NSM) set for mass generation.
Format:
NSM = n
Example:
NSM = 5
Describer Meaning
n Set identification number of a nonstructural mass that appears on a NSM, NSML,
NSM1, NSML1, or NSMADD Bulk Data entry (Integer > 0).
Remark:
1. Different NSM sets may be selected for superelements and residuals but within a superelement or
residual it may not change within the subcase structure.
Main Index
520 MSC Nastran Quick Reference Guide
Velocity Normal Output Request
NVELOCITY (Case) Velocity Normal Output Request
Request output of velocity normal for structural grids in SOLs 108 and 111 only.
Format:
ALL
REAL or IMAG
NVELOCITY[ SORT1 PRINT, PUNCH , ,ERP]= n
SORT2 PLOT PHASE
NONE
NVELOCITY(PLOT,ERP) = ALL
Describer Meaning
SORT1 Output will be presented as tabular listing of grid points for each excitation
frequency (Default).
SORT2 Output will be presented as tabular listing of excitation frequencies for each grid
point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAGE yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is
In degrees.
ERP Flag to accept ERP set convention.
ALL Velocity normal will be computed for all surface structural grid points.
n Set identification of a previously defined set of grid points. Velocity Normal will
be computed for the grid points in this set only.
NONE Velocity normal will not be processed.
Main Index
CHAPTER 5 521
Velocity Normal Output Request
Remarks:
1. NVELOCITY = NONE overrides an overall request.
2. The PLOT option is used if results are requested for post-processing but no printed or punched
output is desired.
3. Even with NVELOCITY=all, Velocity Normal will be computed only for structural grids at the
surface of the model. Fluid grids, if exist, are not included in NVELOCITY output.
4. With ERP flag in NVELOCITY command, structural grids of all ERPPNL will be considered as
candidates for NVELOCITY output and subjected to further screening of NVELOCITY set.
5. For 3D model, ERPPNL points to SET3 with all PSOLID IDs in the model is the easiest way to
compute NVELOCITY of structural surface GRIDs.
6. This Case Control command can be used in SOL 108 and SOL 111 only
Main Index
522 MSC Nastran Quick Reference Guide
ODS Output Frequency Set
ODSFREQ (Case) ODS Output Frequency Set
Selects a set of excitation frequencies for Operational Deflection Shape (ODS) output.
Format:
fsid
ODSFREQ =
PEAK
Examples:
ODSFREQ=101
ODSFREQ=PEAK
Describer Meaning
fsid Set identification of a previously appearing SET command, which specifies a list
of excitation frequencies for ODS output. See Remark 1. (Integer > 0).
PEAK Requests ODS output at peak frequencies found by PEAKOUT Case Control
command. See Remark 2. (Character).
Remarks:
1. The frequencies in the predefined set, fsid, must be one of excitation frequencies.
2. Peak frequency search is controlled by Case Control command, PEAKOUT, which is activated by
ODSFREQ=PEAK.
Main Index
CHAPTER 5 523
Output Frequency Set
OFREQUENCY (Case) Output Frequency Set
Selects a set of frequencies for output requests.
Format:
OFREQUENCY = ALL
n
Examples:
OFREQUENCY=ALL
OFREQUENCY=15
Describer Meaning
ALL Output for all frequencies will be computed.
n Set identification of a previously appearing SET command. Output for
frequencies closest to those given on this SET command will be output
(Integer > 0).
Remarks:
1. In real eigenvalue, buckling, and complex eigenvalue analyses, the OMODES Case Control
command allows for an alternate way of selecting the modes to be output based on their mode
numbers. In these cases, if both the OMODES and OFREQUENCY requests appear, the OMODES
request takes precedence.
2. If this command is not specified in the Case Control Section (or, in the case of real eigenvalue,
buckling, and complex eigenvalue analyses, if neither the OMODES nor the OFREQUENCY
request is specified), then output will be generated for all frequencies.
3. The number of solutions selected will always be equal to the number of quantities in the selected set.
The closest values are used.
4. In flutter analysis (SOL 145), the selected set refers to the imaginary part of the complex eigenvalues.
The physical interpretation of this quantity depends on the method of flutter analysis as follows:
• K- or KE-method: velocity (input units).
• PK-method: frequency.
5. In aeroelastic response analysis (SOL 146) with RLOAD selection, the selected set refers to the
frequency (cycles per unit time).
6. In complex eigenvalue analysis (SOLs 107 and 110), the selected set refers to the imaginary part of
the complex eigenvalues.
7. If this command is specified in more than one subcase, then it is recommended that the first subcase
contain OFREQ=ALL, and that subsequent subcases contain OFREQ = n. Also, data recovery
requests should be specified only in the subsequent subcases. For example:
Main Index
524 MSC Nastran Quick Reference Guide
Output Frequency Set
SUBCASE 1
OFREQ = ALL $ 0.0 through 0.5
SUBCASE 2
SET 10 = 0.0 0.1 0.3
OFREQ = 10
DISP = ALL
SUBCASE3
SET 20 = 0.4 0.5
OFREQ = 20
STRESS = ALL
Main Index
CHAPTER 5 525
Request Output of Imperfection
OIMPERFECT (Case) Request Output of Imperfection
Request output imperfection vectors in SOL 400. Imperfection vectors are coordinate variations applied on
grid points to express geometric imperfection.
Format:
ALL
PRINT, PUNCH
OIMPERFECT GEOM = n
PLOT
NONE
Examples:
OIMPERFECT(GEOM) = 5
OIMPERFECT(PLOT)=ALL
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
GEOM To output grid points with updated coordinates in punch file.
ALL Imperfection vectors for all points will be output.
n Set identification of a previously appearing SET command. Only imperfection
vectors of points with identification numbers that appear on this SET command
will be output.
NONE Imperfection vectors for no points will be output.
Remark:
1. This command must be above all subcases.
Main Index
526 MSC Nastran Quick Reference Guide
Applied Load Output Request
OLOAD (Case) Applied Load Output Request
Requests the form and type of applied load vector output.
Format:
SORT1 PRINT PUNCH REAL or IMAG PSDF,ATOC,CRMS
OLOAD ( ,
SORT2 PLOT PHASE or RALL
ALL
RPRINT
RPUNCH , CID ) = n
NORPRINT
NONE
Examples:
OLOAD=ALL
OLOAD(SORT1, PHASE)=5
OLOAD(SORT2, PRINT, PSDF, CRMS, RPUNCH=20
OLOAD(PRINT, RALL, NORPRINT)=ALL
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load,
frequency, eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid
point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase
output is in degrees.
Main Index
CHAPTER 5 527
Applied Load Output Request
Describer Meaning
PSDF Requests the power spectral density function be calculated and stored in the
database for random analysis postprocessing. Request must be made above the
subcase level, and RANDOM must be selected in Case Control. See Remark
10.
ATOC Requests the autocorrelation function be calculated and stored in the database
for random analysis postprocessing. Request must be made above the subcase
level, and RANDOM must be selected in Case Control. See Remark 10.
CRMS Requests the cumulative root mean square function be calculated for random
analysis postprocessing. Request must be made above the subcase level and
RANDOM must be selected in the Case Control Section. See Remark 10.
RALL Requests all of PSDF, ATOC, and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in the Case Control. See Remark 10.
RPRINT Writes random analysis results to the print file (Default).
NORPRINT Disables the writing of random analysis results to the print file.
RPUNCH Writes random analysis results to the punch file.
CID Requests printing of output coordinate system ID to printed output file
(.f06).
ALL Applied loads for all points will be output. See Remarks 1. and 7.
NONE Applied load for no points will be output.
n Set identification of a previously appearing SET command. Only loads on
points with identification numbers that appear on this SET command will be
output (Integer > 0).
Remarks:
1. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2. In the SORT1
format, only nonzero values will be output.
2. In a statics problem, a request for SORT2 causes loads at all requested points (zero and nonzero) to
be output.
3. OLOAD=NONE overrides an overall output request.
4. In the statics superelement solution sequences, and in the dynamics solution sequences (SOLs 107
through 112, 118, 145, 146, and 200). OLOADs are available for superelements and the residual
structure. Only externally applied loads are printed. Loads transmitted from upstream superelements
are not printed. Transmitted loads can be obtained with GPFORCE requests.
In the nonlinear transient analysis solution sequences (SOLs 129 and 159), OLOADs are available
only for residual structure points and include loads transmitted by upstream superelements.
Main Index
528 MSC Nastran Quick Reference Guide
Applied Load Output Request
5. In nonlinear analyses SOL 106 and 129, OLOAD output will not reflect changes due to follower
forces. But SOL 400 OLOAD output reflects the follower force change correctly. Notes, in SOL 400,
the first OLOAD output before starting nonlinear iteration process, only reflects total non-follower
force without thermal load and follower force.
6. Loads generated by the SPCD Bulk Data entry do not appear in OLOAD output.
7. In SORT1 format, OLOADs recovered at consecutively numbered scalar points are printed in groups
of six (sextets) per line of output. However, if a scalar point is not consecutively numbered, it will
begin a new sextet on a new line of output. If a sextet can be formed and it is zero, then the line will
not be printed. If a sextet cannot be formed, then zero values may be output.
8. OLOAD results are output in the global coordinate system (see field CD on the GRID Bulk Data
entry).
9. In static inertia relief analysis, the OLOAD output includes both the inertia loads and applied loads.
10. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
11. Note that the CID keyword affects only grid point related output, such as DISP, VELO, ACCE,
OLOAD, SPCF and MPCF. In addition, CID the keyword needs to appear only once in a grid point
related output request anywhere in the Case Control Section to turn on the printing algorithm.
Main Index
CHAPTER 5 529
Output Modes Set
OMODES (Case) Output Modes Set
Selects a set of modes for output requests.
Format:
ALL
OMODES =
n
Examples:
OMODES = ALL
OMODES = 20
Describer Meaning
ALL Output for all extracted modes will be computed (Default).
n Set identification of a previously appearing SET command. Output for those
extracted modes appearing on this SET command will be computed.
Remarks:
1. This command is valid only in SOLs 103, 105, 107, 110, 111, 112, 145, 146, 200 and 400. It is
ignored in all other analyses.
2. In contrast to the OFREQENCY Case Control command, which provides an alternate way of
selecting the modes to be output based on their frequencies, the OMODES command allows mode
selection based on integer mode ID. For example:
SUBCASE 10
…
SET 11 = 1,3,5,7
OMODES = 11
DISP = ALL
…
SUBCASE 20
…
SET 21 = 25., 28., 31.
OFREQ = 21
DISP = ALL
…
3. If both the OMODES and the OFREQUENCY requests appear, the OMODES request takes
precedence.
4. If neither the OMODES nor the OFREQUENCY request is specified, output will be generated for
all modes.
5. Note that the OMODES command has no effect on the number of modes computed. It only selects
a subset of the computed modes for which output is to be generated.
Main Index
530 MSC Nastran Quick Reference Guide
Output Modes Set
6. In superelement analysis, the set definition, using an OMODES command, for an upstream
superelement, will not be recognized unless a similar request appears for its downstream neighbor.
The downstream request should either be comprised of the union of all upstream requests, or left
blank, as the OMODES default is ALL. Note that the program does not check to see if this condition
is satisfied.
7. If OMODES is used in conjunction with a FATIGUE case control command, the OMODES request
must be for contiguous modes from 1 through n and the FTGLOAD bulk data entries cannot invoke
modes greater than n.
8. OMODES is intended to be specified above all subcases or in the first subcase. In SOLs 200 and 400,
the first subcase would be the first subcase with ANALYSIS=MODES, MTRAN, MFREQ, MCEIG,
SEAERO, and FLUTTER. See the MODES command to allow different output requests for
individual modes.
Main Index
CHAPTER 5 531
Output Time Set
OTIME (Case) Output Time Set
Selects a set of times for output requests.
Format:
OTIME = ALL
n
Examples:
OTIME =ALL
OTIME =15
Describer Meaning
ALL Output for all times will be computed.
n Set identification number of a previously appearing SET command. Output for
times closest to those given on this SET command will be computed (Integer > 0).
Remarks:
1. If the OTIME command is not supplied in the Case Control Section, then output for all times will
be computed.
2. This command is particularly useful for requesting a subset of the output (e.g., stresses only at peak
times, etc.).
3. This command can be used in conjunction with the MODACC module to limit the times for which
modal acceleration computations are performed.
4. If this command is specified in more than one subcase in the modal solution sequences, then it is
recommended that the first subcase contain OTIME=ALL, and that subsequent subcases contain
OTIME=n. Also, data recovery requests should be specified only in the subsequent subcases. For
example:
SUBCASE 1
OTIME ALL
SUBCASE 2
OTIME = 10
SET 10 = . . .
DISP = ALL
SUBCASE 3
OTIME = 20
SET 20 = . . .
STRESS = ALL
5. The OTIME command is not effective in nonlinear transient analysis (SOL 129) or in SOL 400,
ANALYSIS=NLTRAN. However, the OTIME command can be used in the nonlinear transient
thermal analysis (SOL 159) and in SOL400, ANALYS IS=HTRAN to limit the output to specified
output times.
Main Index
532 MSC Nastran Quick Reference Guide
Output Time Set
6. In superelement analysis, the set definition, using an OTIME command for an upstream
superelement, will not be recognized unless a similar request appears for its downstream neighbor.
The downstream request should either be comprised of the union of all upstream requests, or left
blank, as the OTIME default is ALL. Note that the program does not check to see if this condition
is satisfied.
Main Index
CHAPTER 5 533
Case Control Delimiter
OUTPUT (Case) Case Control Delimiter
Delimits the various types of commands for the structure plotter, curve plotter, grid point stress.
Format:
PLOT
OUTPUT ( POST )
XYOUT
XYPLOT
Examples:
OUTPUT(POST)
OUTPUT(PLOT)
OUTPUT(XYOUT)
Describer Meaning
PLOT Beginning of the structure plotter request. This command must precede all structure
plotter control commands. Plotter commands are described in OUTPUT(PLOT) Commands.
POST Beginning of grid point stress SURFACE and VOLUME commands. This command
must precede all SURFACE and VOLUME commands. These commands are
described in OUTPUT(PLOT) Commands.
XYOUT or Beginning of curve plotter request. This command must precede all curve plotter
XYPLOT control commands. XYPLOT and XYOUT are equivalent. Curve plotter commands
are described in X-Y PLOT Commands.
Remarks:
1. The structure plotter request OUTPUT(PLOT), the curve plotter request OUTPUT(XYOUT or
XYPLOT), and the grid point stress requests (OUTPUT(POST)) must follow the standard Case
Control commands.
2. If OUTPUT is specified without a describer, then the subsequent commands are standard Case
Control commands.
3. Case Control commands specified after OUTPUT(POST) are SURFACE and VOLUME.
4. This command must appear at the end of normal Case Control just above the Begin Bulk Command.
Any Case Control command, controlling, say, selection and flow of the MSC Nastran run such as
TEMP(LOAD), that occurs after this entry, will be ignored.
5. OUTPUT(XYPLOT) requests forces SORT2 and overrides SORT1 requests.
Main Index
534 MSC Nastran Quick Reference Guide
Direct Input Load Matrix Selection
P2G (Case) Direct Input Load Matrix Selection
Selects direct input load matrices.
Format:
P2G=name
Example:
P2G = LDMIG
P2G = LDMIG1, LDMIG2, LDMIG3
SET 100 = LDMIG, L1, L8
P2G = 100
P2G = 1.25*LDMIG1, 1.0*LDMIG2, 0.82*LDMIG3
Describer Meaning
2
name Name of a P g matrix to be input on the DMIG Bulk Data entry, or name list
with or without factors. See Remark 4. (Character).
Remarks:
1. Terms are added to the load matrix before any constraints are applied.
2. The matrix must be columnar in form (e.g., Field 4 on DMIG entry, IFO, must contain the integer
9.)
3. A scale factor may be applied to this input using the user parameter PARAM,CP2. See Parameters.
4. The formats of the name list:
a. Names without factor.
Names separated by a comma or blank.
b. Names with factors.
Each entry in the list consists of a factor, followed by a star, followed by a name. The entries are
separated by a comma or blank. The factors are real numbers. Each name must be paired with a
factor including 1.0.
5. SOL 101: P2G should be selected above all subcase. The number of columns specified for NCOL on
the DMIG Bulk Data entry must equal the number of subcases.
SOL 106 and SOL 400: There are two choices. P2G may be selected in every subcase (or step in SOL
400), with NCOL=1. Otherwise, P2G may be selected above the subcases and PARAM,CP2 selected
in every subcase.
Main Index
CHAPTER 5 535
Particle Acceleration Output Request for SOL 108/111
PACCELERATION (Case) Particle Acceleration Output Request for SOL 108/111
Request the form and frequency steps of particle acceleration output.
Format:
REAL or IMAG
PACCELERATION PRINT, PUNCH SOLUTION = ALL =
PLOT PHASE setf
ALL
setg
NONE
Example:
PACCELERATION = ALL
SET 20 = 104 THRU 204, 1005 THRU 1901
SET 50 = 105.0, 250.0, 310.0
PACCE (PUNCH, SOLUTION=50) = 20
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary). Use of either REAL or IMAG
yields the same output.
PHASE Requests polar format (magnitude and phase). Phase output is in degrees.
SOLUTION Selects a set of excitation frequencies for which the particle accelerations will be
processed. The default is all excitation frequencies. See Remark 3.
setf Set identification of excitation frequencies.
setg Set identification of grid points on wetted surface. See Remark 2.
Main Index
536 MSC Nastran Quick Reference Guide
Particle Acceleration Output Request for SOL 108/111
Remarks:
1. This entry will be available only for fluid-structure coupling problem. The particle acceleration is
input force vector to each domain via wetted surface in frequency response analysis.
2. Both fluid and structure grid points can be selected. The particle accelerations of the grid points not
on wetted surface will be zero.
3. The selected frequency must be part of the excitation frequencies. If not, the nearest excitation
frequency will be selected.
4. Only SORT1 form is supported.
Main Index
CHAPTER 5 537
Page Eject
PAGE (Case) Page Eject
Causes a page eject in the echo of the Case Control Section.
Format:
PAGE
Example:
PAGE
Remarks:
1. PAGE appears in the printed echo prior to the page eject.
2. PAGE is used to control paging in large Case Control Sections.
Main Index
538 MSC Nastran Quick Reference Guide
Parameter Specification
PARAM (Case) Parameter Specification
Specifies values for parameters. Parameters are described in Parameters.
Format:
PARAM,n,V1,V2
Examples:
PARAM,GRDPNT,0
PARAM,K6ROT,1.0
Describer Meaning
n Parameter name (one to eight alphanumeric characters, the first of which is
alphabetic).
V1, V2 Parameter value based on parameter type, as follows:
Type V1 V2
Integer Integer Blank
Real, single precision Real Blank
Character Character Blank
Real, double precision Real, Double Precision Blank
Complex, single precision Real or Blank Real or Blank
Complex, double precision Real, Double Precision Real, Double Precision
Remarks:
1. The PARAM command is normally used in the Bulk Data Section and is described in the Bulk Data
Entries.
2. The parameter values that may be defined in the Case Control Section are described in Parameters.
Case Control PARAM commands in user-written DMAPs requires the use of the PVT module,
described in the MSC Nastran DMAP Programmer’s Guide.
Main Index
CHAPTER 5 539
Partitioning Vector Specifications
PARTN (Case) Partitioning Vector Specifications
Specifies a list of grid point identification numbers that will be partitioned with the DMAP module
MATMOD (Option 17).
Format:
PARTN=n
Example:
PARTN=10
Describer Meaning
n Set identification number of a previously appearing SET command (Integer > 0).
Remarks:
1. The PARTN command and the DMAP module MATMOD provide a convenient method for
building a partitioning vector for use in DMAP modules such as PARTN and MERGE.
2. The PARTN command is no longer applicable to coupled fluid-structure analysis. It has been
replaced by the FSLPOUT command.
Main Index
540 MSC Nastran Quick Reference Guide
Control peaks identification process for frequency response analysis
PEAKOUT (Case) Control peaks identification process for frequency response analysis
Format:
PEAKOUT NPEAK = P NEAR = q LFREQ = r HFREQ = s
DISP NONE
RTYPE= VELO PSCALE = DB PEAKFRFF=setdoff, PEAKFRFS=setdofs
ACCE DBA
Example:
SET 10=1000,2000
SET 20=100/T2,200/T3
PEAKOUT NPEAK=4, NEAR=2.0, LFREQ=10.0, HFREQ=200.0, RTYPE=DISP,
PSCALE=DBA,PEAKFRFF=10, PEAKFRFS=20
Describer Meaning
NPEAK Requests the desired number of peaks to extract. See remark 2. (Integer, Default=5).
NEAR Minimum allowed frequency between two peaks. If two peaks are closer than this value,
the lower frequency peak will be ignored. (Real, Default=0.01 Hz)
LFREQ Lowest frequency used in peak identification. (Real, Default=lowest forcing frequency or
0.0 Hz)
HFREQ Highest frequency used in peak identification. (Real, Default=highest forcing frequency
or 1.0e10 Hz)
RTYPE Results type for peak identification in structural domain. (Default=DISP)
PSCALE Scaling method for acoustic pressure results in fluid domain. See remark 3.
(Default=NONE)
PEAKFRFF Activates the peak frequency search on the responses at fluid degrees of freedom by
PEAKOUT. See Remark 7.
setdoff Identifier of a pre-defined set of fluid degrees of freedom where the peak frequencies are
searched for. (Integer > 0).
PEAKFRFS Activates the peak frequency search on the responses at structural degrees of freedom by
PEAKOUT. See Remark 7.
setdofs Identifier of a pre-defined set of structural degrees of freedom where the peak frequencies
are searched for. (Integer > 0).
Main Index
CHAPTER 5 541
Control peaks identification process for frequency response analysis
Remarks:
1. This command is meaningful only in frequency response analysis (SOLs 108 and 111) and SOL 200
with DFREQ and MFREQ. It is ignored in all other analyses.
2. The actual number of peaks found may be fewer than the desired number.
3. When requesting dB or dBA, the parameter PREFDB is used as a reference pressure for dB
calculation, see ACOUT parameter.
4. If non sparse data recovery is requested using PARAM,SPARSEDR,NO, then also
PARAM,DDRMM,-1 is required. Sparse Data recovery is default.
5. External super elements are not supported
6. PARAM, PTHRES can be used to request the PEAKOUT result that exceeds a prescribed frequency-
dependent threshold value. Refer the User Parameter Description of PTHRES for more details.
7. PEAKFRFF and PEAKFRFS are used for peak frequency search.
Main Index
542 MSC Nastran Quick Reference Guide
Acoustic Grid Participation Factor Output Request
PFGRID (Case) Acoustic Grid Participation Factor Output Request
Requests the form and type of acoustic grid participation factor output.
Format:
PFGRID ( PRINT, PUNCH REAL or IMAG GRIDS = ALL
PLOT PHASE setg
ALL
setf
SOLUTION = ) = setdof
PEAK NONE
NONE
Example:
SET 10 = 11217
SET 20 = 25., 30., 35.
PFGRID(PHASE, SOLUTION=20) = 10
SET 40 = 11217
PEAKOUT NPEAK=4, NEAR=2.0,
PFGRID(PLOT, PHASE, SOLUTION=PEAK) = 40
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Real and imaginary part of complex results will be output (Default).
PHASE Magnitude and phase of complex results will be output.
GRIDS Keyword selecting the structural grid points of the fluid-structure boundary to
be processed for grid point participation. Default is ALL.
setg Set containing explicit structural grid IDs of the fluid-structure boundary, for
which grid point participation factors will be computed.
Main Index
CHAPTER 5 543
Acoustic Grid Participation Factor Output Request
Describer Meaning
SOLUTION Keyword selecting a set of excitation frequencies for which the participation
factors will be processed. Default is all excitation frequencies. PEAK activates the
PEAKOUT automatic peak frequency extraction. See PEAKOUT Case Control
Command for detailed description of PEAK parameters.
setf Identifier of a set of excitation frequencies.
setdof Set containing explicit fluid grid IDs, for fluid grids to be processed in
computing the structural grid point participation factors. There will be a set,
defined by GRIDS, of structural grid point participation factors for each grid of
setdof for each selected frequency.
Remarks:
1. All PFMODE(FLUID), PFPANEL(FLUID), and PFGRID Case Control commands must reference
the same set of fluid grid IDs.
2. Acoustic grid participation factors are available in a coupled frequency response analysis (SOL 108
and SOL 111).
3. The SOLUTION keyword can be used to select a subset of solutions available. If set setf is specified,
the items in the set are excitation frequencies.
Main Index
544 MSC Nastran Quick Reference Guide
Modal Participation Factor (MPF) Output Request
PFMODE (Case) Modal Participation Factor (MPF) Output Request
Requests the form and type of modal participation factor (MPF) output.
Format:
PFMODE ( STRUCTURE PRINT, PUNCH PRTMSG
FLUID PLOT
ALL
SORT = sorttype KEY = sortitem ITEMS =
itemlist
ALL ALL
FLUIDMP = m f STRUCTMP = m s
NONE NONE
ALL
ALL
setf
PANELMP = setp SOLUTION = FILTER = fratio
PEAK
NONE NONE
setdof
NULL = ipower =
NONE
Examples:
SET 20 = 11/T3, 33/T3, 55/T3
SET 30 = 420., 640., 660.
PFMODE(STRUCTURE, SOLUTION = 30, FILTER = 0.01, SORT = ABSD) = 20
SET 40 = 1222, 1223
SET 50 = 10., 12.
PFMODE(FLUID, STRUCTMP=ALL, PANELMP=ALL, SOLUTION=50, SORT=ABSD) = 40
PEAKOUT NPEAK=4, NEAR=2.0,
PFMODE(FLUID, STRUCTMP=ALL, PANELMP=ALL, SOLUTION=PEAK) = 40
Describer Meaning
STRUCTURE Requests output of MPFs for the response of structural degrees of freedom. See
Remark 8. (Default).
FLUID Requests output of MPFs for the response of acoustic grid points (one degree of
freedom per point). See Remark 9.
Main Index
CHAPTER 5 545
Modal Participation Factor (MPF) Output Request
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
PRTMSG Request generation of diagnostic messages for badly-defined output sets during
PF computations. These badly defined sets generally produce no output. See
Remark 15..
SORT Keyword selecting the sort type. Default is sorting by increasing natural mode
number. See Remark 7.
sorttype Sort option:
ABSA output will be sorted by absolute value in ascending order.
ABSD output will be sorted by absolute value in descending order.
ALGA output will be sorted by algebraic value in ascending order.
ALGD output will be sorted by algebraic value in descending order.
KEY Keyword selecting the output item to be used for sorting; default is FRACTION.
See Remark 7.
sortitem Item from the item list, see the following table, on which the sort operation is
performed.
ITEMS Keyword specifying data selected for output to the .pch file
itemlist One or more of the items in the following table:
Main Index
546 MSC Nastran Quick Reference Guide
Modal Participation Factor (MPF) Output Request
Table 5-1 Item List Table
Item Identifier Description
RESPONSE Modal participation factor.
PROJECTION Projected modal participation factor.
FRACTION Normalized projected modal participation factor.
SCALED Projected modal participation factor divided by largest
magnitude of all modal participation factors.
MODEDISP Real and imaginary part of modal participation factors. See
Remark 7.
MODERESP Magnitude and phase relative to total response of modal
participation factors. See Remark 7.
If more than one item is selected, the list must be enclosed in parentheses.
FLUIDMP Keyword to select output of fluid MPFs. See Remarks 2. and 9.
mf Number of lowest fluid modes for which MPFs will be computed. See Remark
9.
STRUCTMP Keyword to select output of structural MPFs. See Remarks 8. and 9.
ms Number of lowest structural modes for which MPFs will be computed. See
Remarks 8. and 9.
PANELMP Keyword to select output of panel MPFs. See Remark 2.
setp Identifier of a set of panels.
SOLUTION Selects a set of excitation frequencies for which MPFs will be processed. Default
is all excitation frequencies. PEAK activates the PEAKOUT automatic peak
frequency extraction. See PEAKOUT Case Control Command for detailed
description of PEAK parameters. See Remark 10.
setf Identifier of a set of excitation frequencies. See Remark 10.
FILTER Keyword specifying the value of a filter to be applied to the printed output. See
Remark 11.
fratio Filter value (Default is 0.001). See Remark 11.
NULL Keyword specifying the power of ten used to detect a null response. See Remark
12.
ipower Power of ten used to detect a null response (Default is 12). See Remark 12.
setdof Identifier of a set of structural degrees of freedom or acoustic grid points (one
degree of freedom per point) for which MPFs are to be processed. See Remark 3.
Main Index
CHAPTER 5 547
Modal Participation Factor (MPF) Output Request
Remarks:
1. All PFMODE(FLUID), PFPANEL(FLUID), and PFGRID Case Control commands must reference
the same set of fluid grid IDs.
2. Keywords FLUIDMP and PANELMP are only valid if FLUID is specified.
3. If STRUCTURE is specified, setdof must reference a set of structural degrees of freedom. If FLUID
is specified, setdof must reference a set of acoustic grid points.
4. Acoustic MPFs are available in modal frequency response analysis (SOL 111, (SOL200, SOL400
ANALYSIS=MFREQ)) only.
5. Printed output includes results for ALL the data items described in the Item List Table.
6. Punched output includes results for only the data items selected by the ITEMS keyword.
7. MPFs are sorted by increasing order of mode number unless the SORT keyword specifies a different
sorting order. If a sorting order is specified, the KEY keyword selects the item that is used for sorting.
When MODEDISP is selected, sorting is based on the magnitude. When MODERESP is selected,
sorting is based on the real part.
8. The STRUCTURE option selects MPF calculations for structural degrees of freedom. The
STRUCTMP value defines the number of lowest structural modes used in final output preparation
prior to any filtering. The default is ALL. If STRUCTMP=NONE, no structural MPF is generated.
9. The FLUID option selects MPF calculations for acoustic grid points (one degree of freedom per
point). The STRUCTMP value defines the number of lowest structural modes used in final output
preparation of acoustic structure MPFs prior to any filtering. The default is NONE. The FLUIDMP
value defines the number of lowest fluid modes used in final output preparation of acoustic fluid
MPFs prior to any filtering. The default is NONE.
10. The SOLUTION keyword can be used to select a subset of solutions available. If setf is specified, the
items in the set are excitation frequencies.
11. The filter is applied to the real part of the normalized projected participation factors. Only
participation factors that pass the filter are output.
12. If the magnitude of the total response at a selected response degree of freedom is less than
10-ipowr, then no MPFs are processed. If ipower is not in the range of 1 to 31, the default of 12 is used.
13. Acoustic panel MPFs are normalized using the panel response instead of the total response.
14. If present, only the output of acoustic structural MPFs will include the load participation factor. The
load participation factor has a mode number of 0 and a resonance frequency of 0. Structural MPFs
will not include the load participation factor.
15. Output sets that define no valid model degrees of freedom for data recovery produce no PF output.
This condition is usually discovered prior to actual computations and an informational message is
generated. Occasionally, when multiple subcases are involved and one of the subcases references an
invalid set, the PF calculations are still performed for any valid combinations. PRTMSG can be used
to aid in identification of invalid set data under these conditions.
Main Index
548 MSC Nastran Quick Reference Guide
Acoustic Panel Participation Factor Output Request
PFPANEL (Case) Acoustic Panel Participation Factor Output Request
Requests the form and type of acoustic panel participation factor output.
Format:
FLUID PRINT, PUNCH PRTMSG REAL or IMAG
PFPANEL (
STRUCTURE PLOT PHASE
ALL
PANEL = ALL SORT = sorttype KEY = sortitem ITEMS =
setp itemlist
ALL
setf
SOLUTION = FILTER = fratio NULL = ipower
PEAK
NONE
setdof
=
NONE
Example:
SET 10 = 10., 12.
SET 20 = 1222, 1223
PFPANEL (SOLUTION=10, FILTER=0.01, SORT=ABSD) = 20
SET 30 = 5001/T2, 6502/T3
PFPANEL (STRUCTURE, SOLUTION=10) = 30
SET 40 = 11217
PEAKOUT NPEAK=4, NEAR=2.0,
PFPANEL(SOLUTION=PEAK, FILTER=0.01, SORT=ABSD) = 40
Describer Meaning
FLUID Request output of MPFs for the response of acoustic grid points (one degree of
freedom per point). See Remark 11. (Default)
STRUCTURE Request output of MPFs for the response of structure degrees of freedom. See
Remark 12.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
Main Index
CHAPTER 5 549
Acoustic Panel Participation Factor Output Request
Describer Meaning
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
PRTMSG Request generation of diagnostic messages for badly-defined output sets during
PF computations. These badly defined sets generally produce no output. See
Remark 12..
REAL or IMAG Real and imaginary part of complex results will be output (Default).
PHASE Magnitude and phase of complex results will be output.
PANEL Keyword to select the panels to be processed; default is all panels.
setp Identifier of a set of panels containing the names of the panels, defined on the
PANEL Bulk Data Entry, to be processed.
SORT Keyword selecting the sort type. Default is alphabetic sorting by panel name.
sorttype Sort option:
ABSA Output will be sorted by absolute value in ascending order.
ABSD Output will be sorted by absolute value in descending order.
ALGA Output will be sorted by algebraic value in ascending order.
ALGD Output will be sorted by algebraic value in descending order.
KEY Keyword selecting the output item to be used for sorting; default is
FRACTION.
sortitem Item from the item list, see the following table, on which the sort operation is
performed.
ITEMS Keyword specifying data selected for output to the .pch file.
itemlist One or more of the items in the following table:
Table 5-2 Item List Table
Item Identifier Description
RESPONSE Modal participation factor.
PROJECTION Projected modal participation factor.
Main Index
550 MSC Nastran Quick Reference Guide
Acoustic Panel Participation Factor Output Request
Table 5-2 Item List Table
Item Identifier Description
FRACTION Normalized projected modal participation factor.
SCALED Projected modal participation factor divided by largest
magnitude of all modal participation factors.
MODEDISP Real and imaginary part of modal participation factors.
MODERESP Magnitude and phase relative to total response of modal
participation factors.
If more than one item is selected, the list must be enclosed in parentheses.
SOLUTION Keyword selecting a set of excitation frequencies for which the participation
factors will be processed. Default is all excitation frequencies. PEAK activates
the PEAKOUT automatic peak frequency extraction. See PEAKOUT Case
Control Command for detailed description of PEAK parameters.
setf Identifier of a set of excitation frequencies.
FILTER Keyword specifying the value of a filter to be applied to the printed output.
fratio Filter value (Default is 0.001), see Remark 7.
NULL Keyword specifying the power of ten used to detect a null response, see Remark
8.
ipower Power of ten used to detect a null response (Default is 12), see Remark 8.
setdof Identifier of a set of fluid degrees of freedom for which the participation factors
are to be processed.
Remarks:
1. All PFMODE(FLUID), PFPANEL(FLUID), and PFGRID Case Control commands must reference
the same set of fluid grid IDs.
2. Acoustic panel participation factors are available in a coupled frequency response analysis (SOL 108
and SOL 111).
3. Printed output includes results for all the data items described in the itemlist table.
4. Punched output includes results for only the data items selected by the ITEMS keyword.
5. Panel participation factors are alphabetically sorted by panel names unless the SORT keyword
specifies a different sorting order. If a sorting order is specified, the KEY keyword selects the item that
is used for sorting. When MODEDISP is selected, sorting is based on the magnitude. When
MODERESP is selected, sorting is based on the real part.
6. The SOLUTION keyword can be used to select a subset of solutions available. If set setf is specified,
the items in the set are excitation frequencies.
7. The filter is applied to the real part of the normalized projected participation factors. Only
participation factors that pass the filter are output.
Main Index
CHAPTER 5 551
Acoustic Panel Participation Factor Output Request
8. If the magnitude of the total response at a selected response degree of freedom is less than
10-ipowr, then no modal participation factors are processed. If ipower is not in the range of 1 to 31,
the default of 12 is used.
9. If present, output includes the load participation factor. The panel name of the load participation
factors is –LOAD-.
10. The FLUID option selects panel PF calculation for acoustic grid points (one degree of freedom per
point) and setdof should be identification numbers.
11. The STRUCTURE option selects panel PF calculation for structure grid points and setdof should be
identification numbers and component codes.
12. Output sets that define no valid model degrees of freedom for data recovery produce no PF output.
This condition is usually discovered prior to actual computations and an informational is generated.
Occasionally, when multiple subcases are involved and one of the subcases references an invalid set,
the PF calculations are still performed for any valid combinations. PRTMSG can be used to aid in
identification of invalid set data under these conditions.
Main Index
552 MSC Nastran Quick Reference Guide
Plotter Identification
PLOTID (Case) Plotter Identification
Defines a character string that will appear on the first frame of any plotter output.
Format:
PLOTID=title
Example:
PLOTID=BLDG. 125 BOX 91
Describer Meaning
title Any character string.
Remarks:
1. PLOTID must appear before the OUTPUT(PLOT) or OUTPUT(XYOUT) Case Control
commands.
2. The presence of PLOTID causes a special header frame to be plotted, with the supplied identification
plotted several times. The header frame allows plotter output to be identified easily.
3. If no PLOTID command appears, no ID frame will be plotted.
4. The PLOTID header frame will not be generated for the table plotters.
Main Index
CHAPTER 5 553
Postprocessor Data Specifications
POST (Case) Postprocessor Data Specifications
Controls selection of data to be output for postprocessing functions via the OUTPUT2 module interface for
selected commercial postprocessor products.
Format:
POST TOFILE furn ppname ENHOP2 oplist
TOCASE filename
Examples:
POST PATRAN TOFILE 51 NOSTRESS
POST TOFILE SUBCASE8
POST TOCASE SUFNAME1
Describer Meaning
TOFILE Keyword to specify the destiny of .op2 output files (No default if it appears above
all subcases).
TOCASE Keyword to specify the destiny of subcase results to user-defined .f06 output files.
(No default if it appears above all subcases.)
furn Fortran file unit reference number where data will be written (Integer > 0).
filename Suffix filename (see Remark 8., 9. and 11.) (Char8)
ppname Name of the target post-processor program for TOFILE option (Default =
PATRAN).
ENHOP2 If ppname='PATRAN' then request enhanced op2 format-same as with
PARAM,POST,1. The enhanced op2 format includes Nastran version information
and qualifier values.
oplist Names of output items to be processed.
Remarks:
1. The POST Case Control command controls the placement of output data on external FORTRAN
files for use by commercial postprocessors. Use of the POST command generates the proper value for
the POST DMAP parameter associated with the particular postprocessor. All of the other parameter
controls related to the POST DMAP parameter remain in effect, and are described in Parameters, 807.
The products supported are identified in the following table. PATRAN is the default postprocessor
name used for ppname. DBC output (POST=0) cannot be controlled by the POST command.
Main Index
554 MSC Nastran Quick Reference Guide
Postprocessor Data Specifications
ppname Product PARAM,POST,Value
PATRAN MSC Patran V3 -1
PATRAN with ENHOP2 MSC Patran V3 +1
SDRC Siemens I-DEAS -2
NF MSC/LMS NF -4
FEMTOOLS DDS/FemTools -5
UNIGRAHICS Siemens/Unigraphics -6
2. The TOFILE describer is followed by the specification of either a FORTRAN unit reference number,
or a file name associated with the external file that receives the output data. If a FORTRAN unit
number is used, the file must be associated with it via the ASSIGN File Management Statement. If
POST appears above all subcases, TOFILE must be used to specify either a FORTRAN unit reference
number or a file name. The default value of TOFILE, which appears under a subcase, will inherit
from the value given in the POST above all subcases. If the unit reference number is associated with
a form=formatted file, changes in unit numbers across subcases are not allowed.
3. The data that can be controlled for each postprocessor product is limited, and is identified under the
description of the POST and related DMAP parameters as described in Parameters, 807. The keywords
that can be used for the oplist options are shown in the following table. If an output item supported
by a particular postprocessor is described in Parameters, 807 but is not listed here, then the POST
command cannot be used to control its output to the external file.
Output Item oplist Keyword Case Command
Displacements [NO]DISPLACE DISP
Forces of single point constraint [NO]SPCFORCE SPCFORCE
Element forces [NO]FORCES ELFO/FORCE
Element stresses [NO]STRESS ELST/STRESS
Element strain energy [NO]ESE ESE
Grid point force balance [NO]GPFORCE GPFORCE
Stress at grid points [NO]GPSIGMA STRESS
Strain/curvature at grid points [NO]GPEPSILON STRAIN
Composite element failure indices [NO]PLYFAILURE STRESS
Element kinetic energy [NO]EKE EKE
Element energy loss [NO]EDE EDE
Multi-point constraint forces [NO]MPCFORCE MPCFORCE
Composite lamina stresses [NO]PLYSIGMA STRESS
Composite lamina strains [NO]PLYEPSILON STRAIN
Main Index
CHAPTER 5 555
Postprocessor Data Specifications
Output Item oplist Keyword Case Command
Element strains [NO]STRAIN STRAIN
Grid point stresses [NO]GPSTRESS GPSTRESS
Grid point strains [NO]GPSTRAIN GPSTRAIN
Applied loads [NO]LOAD OLOAD
No items to be output NONE ----------------
Structure mode participation factors [NO]SMPF PFMODE
4. Output data items must have been generated via the appropriate Case Control command for the data
to be available for postprocessing options. For example, the specification of SPCF in the oplist of the
POST command will not produce forces of single point constraint on the POST output file unless
there is a SPCF Case Control command present. Refer to the tables under the POST parameter
description in Parameters, 807 for a list of the output items supported by each postprocessor.
5. Any data generated by a Case Control command is automatically included in the oplist of the POST
command. If output data is not wanted for a particular case, then the characters “NO” should be the
first two characters of the keyword in the oplist. For example, NODISP specifies that displacements
are not to be posted to the output file, even though they have been requested via the DISP Case
Control command. Alternatively, the related POST parameters may be used. For example, to avoid
outputting any displacements whatsoever to the .op2 file, use a PARAM, OUG, NO Bulk Data entry.
6. Certain data (e.g., geometry) is always generated and is not dependent upon the presence of a Case
Control command in the input data. The POST command affects the placement of this data on the
external file only insofar as the selection of the postprocessor defines the value of the POST DMAP
parameter value. The actions described in Parameters, 807 under the POST parameter description will
prevail for the particular value of POST associated with the selected postprocessor. The primary
purpose of the POST command is to give the user more control over subcase-dependent output data
being stored on the external OUTPUT2 file.
7. If a POST command is present within any subcase, a POST command must also be present above
the subcase level. The placement of the POST command above the subcase level causes a cumulative
effect on POST commands in subsequent subcases. Any options specified above the subcase level
propagate down into the POST command within a subsequent subcase. Thus, if a POST command
specifies NODISP (no displacement output wanted) above the subcase level, then a POST command
with the DISP option would be required within a subcase to generate any output to the OUTPUT2
file for displacements. This also implies that changing the OUTPUT2 file unit reference number with
the TOFILE option in a subcase causes all output quantities currently scheduled for output to be
switched to the new unit number, not just those in the oplist for the current POST command.
8. When the name of an output file is specified by keyword TOFILE, the ASSIGN statement in the File
Management Section (FMS) can be used to specify the full path of its root name. The logical-keyword
for the root name is OUTPUT2F. The default root name is the Nastran job name. FORTRAN unit
reference number 19 has been reserved by Nastran for OUTPUT2F, although the user can assign
other FORTRAN unit number to it. The full file name is in the form of <root name>.<suffix
filename>.
Main Index
556 MSC Nastran Quick Reference Guide
Postprocessor Data Specifications
9. When the name of an output file is specified by keyword TOCASE, the ASSIGN statement in the
File Management Section can be used to specify the full path of its root name. The logical-keyword
for the root name is OPCASE. The default root name is the Nastran job name. FORTRAN unit
reference number 22 has been reserved by Nastran for OPCASE, although the user can assign other
FORTRAN unit numbers to it. The full file name is in the form of <root name>.<suffix filename>.
Also, ppname and oplist are not required. If ppname and oplist are specified, they will be ignored.
Suffix filename must be specified with keyword TOCASE.
10. POST commands using TOCASE for structure mode participation factor output (SMPF) are not
supported and will be ignored.
11. The TOFILE option lets you control the output results (per the table in Remark 3) that are placed
on the specified file in OP2 format. The "POST TOFILE SUBASE8" example directs output to the
file named <root name>.subcase8.op2. The TOCASE option directs standard printed output
requested for a subcase to the specified file in .f06 format. The "POST TOCASE SUFNAM1"
example directs output to the file named <root name>.sufnam1.f06. The TOCASE and TOFILE
describers are independent of one another. POST commands using each describer may be present in
a subcase to specify different output destinations for both .op2 and .f06 outputs at the same time. For
both the TOCASE and TOFILE options, the resulting file name will not have the .op2 or the .f06
file extension automatically appended if the file suffix name contains a period (".").
12. The TOCASE keyword is not supported for printout in the f06 file coming from X-Y Plot
commands.
Main Index
CHAPTER 5 557
Pressure Output Request
PRESSURE (Case) Pressure Output Request
Requests form and type of pressure output. Analogous to the DISPLACEMENT Case Control command.
See the description of the DISPLACEMENT Case Control command, DISPLACEMENT (Case).
Main Index
558 MSC Nastran Quick Reference Guide
Random Analysis Set Selection
RANDOM (Case) Random Analysis Set Selection
Selects the RANDPS and RANDT1 Bulk Data entries to be used in random analysis.
Format:
RANDOM = n
i
Examples:
RANDOM=177
SET 10=100 110 120
RANDOM=10
Describer Meaning
n Set identification number of a previously appearing SET command, which in turn
references multiple RANDPS/RANDT1 Bulk Data entries with different set
identification numbers.
i Set identification number of RANDPS and RANDT1 Bulk Data entries to be
used in random analysis (Integer > 0).
Remarks:
1. RANDOM must select RANDPS Bulk Data entries to perform random analysis.
2. RANDOM must appear in the first subcase of the current loop. RANDPS Bulk Data entries may not
reference subcases in a different loop. Loops are defined by a change in the FREQUENCY command,
or changes in the K2PP, M2PP, or B2PP commands.
3. If RANDPS entries are used in a superelement analysis, the RANDOM command may be specified
above the subcase level if a condensed subcase structure (SUPER=ALL) is used. If a condensed subcase
structure is not used, then a unique RANDOM selection of a unique RANDPS entry must be
specified within each of the desired superelement subcases.
4. If a SET is referenced by n, then the SET identification number must be unique with respect to all
RANDPS/RANDT1 set identification numbers.
Main Index
CHAPTER 5 559
Control for EXCLUSIVE Random Result, PSDF, Output to HDF5 and/or OP2
RANDOUT (Case) Control for EXCLUSIVE Random Result, PSDF, Output to HDF5 and/or OP2
Control for exclusive random result, PSDF, output, to HDF5 and/or OP2
Format:
BOTH
YES
RANDOUT PSDF HDF5 =
NO
OP2
Examples:
RANDOUT= YES
RANDOUT (PSDF, HDF5) = YES
RANDOUT= NO
Describer Meaning
PSDF Requests only PSDF result output to HDF5 and/or OP2 (Default).
BOTH Both HDF5 and OP2 will only output random result, PSDF (Default).
HDF5 HDF5 will only output random result, PSDF. OP2 will output all results.
OP2 OP2 will only output random results. HDF5 will output all results.
NO No request on exclusive random result, PSDF, output to HDF5 and/or OP2
YES Requests to exclusively output random result, PSDF, to HDF5 and/or OP2.
Remarks:
1. Case Control command, RANDOUT, is used to exclude all non-random results as well as random
results other than PSDF, from HDF5 or OP2 database to reduce the file size for large models with
random analysis.
2. If used, RANDOUT must be placed above all SUBCASE's. It overrides all Case Control commands,
such as DISP, VELO, ACCEL, STRESS, STRAIN, FORCE, and so on, which may have some
request on random results.
Main Index
560 MSC Nastran Quick Reference Guide
Cross-Power Spectral Density and Cross-Correlation Function Output Request
RCROSS (Case) Cross-Power Spectral Density and Cross-Correlation Function Output Request
Requests computation and output of cross-power spectral density and cross-correlation functions in random
analysis.
Format:
RCROSS ( REAL or IMAG PRINT PUNCH PSDF, CORF, RALL = n
PHASE NOPRINT
Example:
RCROSS(PHASE, PSDF, CORF) = 10
RCROSS(RALL, NOPRINT, PUNCH) = 20
RCROSS = 30
Describer Meaning
REAL or IMAG Requests rectangular format (real and imaginary) of complex output for cross-
power spectral density function. Use of either REAL or IMAG yields the same
output (Default).
PHASE Requests polar format (magnitude and phase) of complex output for cross-power
spectral density function. Phase output is in degrees.
PRINT Write output to print file (Default).
NOPRINT Do not write output to print file.
PUNCH Write output to punch file.
PSDF Requests the cross-power spectral density function be calculated and output for
random analysis postprocessing (Default).
CORF Requests the cross-correlation function be calculated and output for random
analysis postprocessing.
RALL Requests both the cross-power spectral density function and cross-correlation
function be calculated and output for random analysis postprocessing.
n Identification number of the RCROSS Bulk Data entry to be used in random
analysis (Integer > 0).
Remarks:
1. Case Control command RCROSS must be used along with Case Control command RANDOM. See
Remarks under the RANDOM (Case) Case Control command description.
Main Index
CHAPTER 5 561
Cross-Power Spectral Density and Cross-Correlation Function Output Request
2. Response quantities such as DISPLACEMENT, STRESS, and FORCE must be requested by
corresponding Case Control commands in order to compute cross-power spectral density and cross-
correlation functions between the two response quantities specified by the RCROSS Bulk Data entry.
It is recommended that those requests be put above the subcase level to avoid the situation that some
response quantities are missing when it comes to the random analysis postprocessing.
3. The response quantities must belong to the same superelement. The cross-power spectral density and
cross-correlation functions between the two responses, which belong to the different superelements,
are not supported.
Main Index
562 MSC Nastran Quick Reference Guide
Relative Displacement Output Request
RELDISP (Case) Relative Displacement Output Request
Requests the form and type of relative displacement output with respect to a structural grid point in SOL
101, 103, 105, 108, 109, 111, 112, 200 and SOL 400 only.
Format:
ALL
SORT1 PRINT PUNCH REAL or IMAG
RELDISP REFSET = m = NONE
SORT2 PLOT PHASE
n
Example:
RELDISP(REAL, PUNCH, PRINT,REFSET=10)=20
RELDISP(REFSET=10)=20
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each frequency.
SORT2 Output will be presented as a tabular listing of frequency for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with "PARAM,POST, X" (or the POST Case Control
command), while the .h5 binary database file will be generated with "MDLPRM,HDF5, X" specified in
Bulk Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REFSET (=m) Set number of the previously appearing SET command having Reference
Structural Grid ID present in the main bulk data w.r.t relative displacement is
requested.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is
in degrees.
ALL Relative displacement for all points will be output. See Remarks 2.
Main Index
CHAPTER 5 563
Relative Displacement Output Request
Describer Meaning
NONE No relative displacement will be output
n Set identification of a previously appearing SET command. Only relative
displacements of points with identification numbers that appear on this SET
command will be output. (Integer >0).
Remarks:
1. RELDISP is available for SOL 101, 103, 105, 108, 109, 111, 112, 200 and SOL400 only.
2. RELDISP can be requested against only one grid for all the different subcases. The reference set
should be same for all the subcases.
3. REFSET entry needs to be defined for getting the relative displacement.
4. See Remark 1. under DISPLACEMENT (Case), for a discussion of SORT1 and SORT2.
5. RELDISP (refset =m) =NONE suppresses the generation of relative displacement output.
6. Relative Displacement between two grids is the algebraic difference of the displacement of both the
grids.
7. S points or E points are not supported as reference point against which relative displacement can be
calculated.
8. For superelements, the reference grid can be only in residual structure and relative displacement
output can be requested for residual structure only.
9. The reference set grid should be a structural grid only with respect to which the relative displacement
is requested.
10. The reference set grid should be present in the main bulk data section only.
Main Index
564 MSC Nastran Quick Reference Guide
Repeat Output Subcase Delimiter
REPCASE (Case) Repeat Output Subcase Delimiter
Delimits and identifies a repeated output subcase.
Format:
REPCASE=n
Example:
REPCASE=137
Describer Meaning
n Subcase identification number. (Integer > 1)
Remarks:
1. n must be strictly increasing (i.e., must be greater than all previous subcase identification numbers).
2. REPCASE defines a subcase that is used to make additional output requests for the previous real
subcase. This command is required because multiple output requests for the same item are not
permitted in the same subcase.
3. One or more repeated subcases (REPCASEs) must immediately follow the subcase (SUBCASE) to
which they refer.
4. REPCASE may be used only in statics and normal modes analysis. In normal modes analysis, output
for only one mode is obtained. This output corresponds to the SUBCASE preceding the REPCASE.
5. If the referenced subcases contain thermal loads or element deformations, the user must define the
temperature field in the REPCASE with a TEMP(LOAD) Case Control command, or the element
deformation state with a DEFORM command.
6. Repcase is not applicable to SOLs 400 and 700.
Main Index
CHAPTER 5 565
Controls Residual Vectors
RESVEC (Case) Controls Residual Vectors
Specifies options for and calculation of residual vectors.
Format:
RESVEC INRLOD APPLOD ADJLOD RVDOF DAMPLOD DYNRSP =
NOINRL NOAPPL NOADJLOD NORVDO NODAMP NODYNRSP
SYSTEM/NOSYSTEM
COMPONENT/NOCOMPONENT
BOTH or YES
NO
RESVEC FLUID = YES|NO
Examples:
RESVEC=SYSTEM
RESVEC(NOINRL)=COMPONENT
RESVEC=NO
RESVEC(FLUID)=NO
Describer Meaning
INRLOD/ Controls calculation of residual vectors based on inertial forces due to rigid-
NOINRL body motion (Default =INRLOD).
APPLOD/ Controls calculation of residual vectors based on applied loads (Default =
NOAPPL APPLOD).
ADJLOD/ Controls calculation of residual vectors based on adjoint load vectors
NOADJLOD (SOL 200 only; Default = ADJLOD).
RVDOF/ Controls calculation of residual vectors based on RVDOFi entries (Default =
NORVDOF RVDOF).
DAMPLOD/ Controls calculation of residual vectors based on viscous damping (Default =
NODAMP DAMPLOD).
DYNRSP/ Controls whether the residual vectors will be allowed to respond dynamically
NODYNRSP in the modal transient or frequency response solution. See Remark 5. (Default
= DYNRSP).
SYSTEM/ Controls calculation of residual vectors for system (a-set) modes. For
NOSYSTEM NOSYSTEM, describers inside the parentheses are ignored. See Remark 2. for
default.
COMPONENT/ Controls calculation of residual vectors for component (superelement or o-
NOCOMPONENT set) modes. For NOCOMPONENT, describers inside the parentheses are
ignored. See Remark 2. for default.
Main Index
566 MSC Nastran Quick Reference Guide
Controls Residual Vectors
Describer Meaning
BOTH or YES Requests calculation of residual vectors for both system modes and
component modes. See Remark 2. for default.
NO Turns off calculation of residual vectors for both system and component
modes, and describers inside the parentheses are ignored. See Remark 2. for
default.
FLUID Requests residual vector calculation for the fluid model (Default = YES).
Remarks:
1. RESVEC=SYSTEM/NOSYSTEM and RESVEC=COMPONENT/NOCOMPONENT may be
specified in the same subcase.
2. RESVEC=BOTH is the default in all solution sequences except SOLs 103, 106, (with
PARAM,NMLOOP), and 115, wherein RESVEC=COMPONENT is the default.
3. If the RESVEC command is specified then the user parameters PARAM,RESVEC and
PARAM,RESVINER are ignored.
4. The lower frequency cutoff on the EIGR or EIGRL Bulk Data entries should be left blank or set to
a value below the minimum frequency. Residual vectors may not be calculated if all modes below the
maximum frequency cutoff are not determined. If low frequency modes are to be excluded from the
analysis, use the MODESELECT Case Control command or PARAM,LFREQ.
5. Caution needs to be exercised when allowing the residual vectors to respond dynamically in a modal
solution. The best approach is to always include enough normal modes to capture the dynamics of
the problem, and rely on the residual vectors to help account for the influence of the truncated modes
on the quasistatic portion of the response. This is not the default setting for this capability. When
choosing to allow the residual vectors to respond dynamically, it is important to be aware of the
frequency content of the excitation, as it will have the ability to excite these augmentation modes. If
this is undesirable, then the forcing function should be filtered in advance to remove any undesired
frequency content, or specify the NODYNRSP keyword.
6. Residual vectors are normalized with respect to MASS if possible. Massless residual vectors are
normalized with respect to STIFFNESS. Residual vectors are not normalized by the requested
method of the NORM field of the selected EIGR or EIGRL entry.
7. The maximum number of applied loads that may be used for residual vector calculations is controlled
by PARAM,MAXAPL. Note that if the number of applied loads is large, the cost can become
prohibitive. If the number of applies loads exceeds MAXAPL, residual vectors are disabled.
Main Index
CHAPTER 5 567
Activates Gyroscopic Effects and Selects RGYRO or UNBALNC Entries
RGYRO (Case) Activates Gyroscopic Effects and Selects RGYRO or UNBALNC Entries
The RGYRO Case Control command activates the rotodynamics capability, and selects the RGYRO Bulk
Data entry for use in complex modes, frequency response, and static analysis. For transient response, the
RGYRO command selects the UNBALNC Bulk Data entry. If the UNBALNC entry is not required, setting
RGYRO to YES will include the gyroscopic effects in the transient response calculation. Setting RGYRO to
NO will deactivate gyroscopic effects in all solutions.
Note that RGYRO is not supported in NLPERF SOL 400.
Format:
For complex modes, frequency response, and static analysis:
RGYRO = n or YES/NO
Examples:
RGYRO = 100
For Transient Response:
RGYRO = YES
or
RGYRO = 200
Main Index
568 MSC Nastran Quick Reference Guide
Rigid Element Method
RIGID (Case) Rigid Element Method
Selects rigid elements processing method for RBAR, RBAR1, RJOINT, RROD, RTRPLT, RTRPLT1,
RBE1, RBE2, and RBE3.
Format:
LINEAR
RIGID = LAGRAN
LGELIM
Example:
RIGID=LAGRAN
Describer Meaning
LINEAR Selects the linear elimination method.
LAGRAN Selects the Lagrange multiplier method.
LGELIM Selects the Lagrange multiplier method with elimination.
Remarks:
1. The RIGID command must be above the SUBCASE level.
2. The RIGID command can be used in SOLs 101, 103, 105, and 400 only. For all other solution
sequences, only RIGID=LINEAR is available.
3. If the RIGID command is not specified in the Case Control Section, RIGID=LINEAR is used for all
solution sequences except SOL 400. For SOL 400, RIGID=LAGRAN is used. If the RIGID
command is specified, the full command must be specified, including the right hand side.
4. RIGID=LGELIM is not available for SOL 400.
5. LINEAR processing will not compute thermal loads. Also, for SOLs 103 and 105, LINEAR
processing will not compute differential stiffness. In order to compute thermal load or differential
stiffness, the LAGRAN or LGELIM methods must be used.
6. For SOL 400, the LINEAR rigid elements are valid for small rotation only. The LAGRAN method
is valid for both small and large rotation (parameter LGDISP=1).
7. For the LINEAR method, the dependent DOFs are eliminated and placed in the mp-set. For the
LAGRAN method, both independent and dependent DOFs are placed in the l-set. Lagrange
multiplier DOFs are created internally for the dependent DOFs and placed in l-set. For the LGELIM
method, the LAGRAN rigid elements are created first. Then, both the Lagrange DOFs and the
dependent DOFs are eliminated, and the dependent DOFs are placed in the mr-set. Both the mp-set
and mr-set are subsets of the m-set. See Degree-of-Freedom Set Definitions.
Main Index
CHAPTER 5 569
Rigid Element Method
8. Between LAGRAN and LGELIM, LAGRAN is the preferred method. LGELIM is a backup method
if difficulty is encountered using the LAGRAN method.
9. The parameters LMFACT and PENFN can be used as scale factor and penalty function, respectively,
for the LAGRAN method of processing.
10. In a SOL 400 analysis with CWELD, CFAST, and/or CSEAM elements Nastran internally creates
RBE3 elements. These internal RBE3 elements respond in the same way to the RIGID command as
any other rigid body elements that may have been defined in the model. Therefore the RIGID
command also has an effect on the behavior of CWELD and CFAST elements in a SOL 400 analysis.
For "ANALYSIS=NLSTAT" or "ANALYSIS=NLTRAN", the generated RBE3 constraints become
Lagrange elements and will undergo large rotation. For "ANALYSIS=NLTRAN" with initial
conditions (IC=n) in case control that cause large initial stresses in the structure at time t=0, the case
control entry RIGID needs to have the value "RIGID=LINEAR." If "PARAM, OLDWELD, YES"
is specified, the CSEAM is considered a linear element.
11. For external superelements, both the Case Control Command EXTSEOUT and the PARAM,
EXTOUT, REQUIRE a value of RIGID=LINEAR (the default for non SOL400 solution sequences)
when running non SOL 400 jobs.
12. When creating superelements in SOL 400, RIGID=LAGRAN produces incorrect answers, RIGID-
LINEAR should be used or put the rigid elements into the residual.
13. When RIGID=LAGRAN is used, one may observe SWM 4968, indicating negative terms on
multiple DOF which is due to the Lagrange multiplier. This message may be ignored and an accurate
solution will be obtained.
14. When RIGID=LAGRAN is used, the CASI iterative solver may fail to converge or terminate, one
should switch to a direct solver.
15. For the Lagrange method, the thermal expansion effect will be computed, if user supplies the thermal
expansion coefficient ALPHA, and the thermal load is requested by the TEMPERATURE(INITIAL)
and TEMPERATURE(LOAD) Case Control commands. The average temperature of the connected
grid points is used as the temperature of the rigid body element. In this case, for the Lagrange method,
PARAM, BAILOUT, -1 is activated within the solver.
16. For coupled thermal-mechanical analysis, only RIGID=LINEAR is available.
Main Index
570 MSC Nastran Quick Reference Guide
Specifying rotor initial deformation and requesting outputs of initial deformation
ROTBENT (Case) Specifying rotor initial deformation and requesting outputs of initial deformation
Specifies rotor the initial deformation (kink and offset) parameters.
Requests bent rotor initial deformation and added constraints, such as SPOINTs, MPCs, SPCs and SPCDs
due to ROTBENT data bulk entry.
Format:
PRINT PUNCH
ROTBENT = n
PLOT
Example:
ROTBENT = 10
ROTBENT (PRINT)= 10
ROTBENT (PUNCH) = 10
ROTBENT (PRINT, PLOT, PUNCH) = 10
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
n Identification number in Bulk Data ROTBENT Entry (Integer >0).
Remarks:
1. ROTBENT option is only supported for SOL400 analysis. ROTBENT analysis will require 2 step
analysis, with step 1 being NLSTATIC and step 2 being rotordynamics analysis.
Main Index
CHAPTER 5 571
Rotor Modal Strain and Kinetic Energies Output Request
ROTSEKE (Case) Rotor Modal Strain and Kinetic Energies Output Request
Requests rotor modal strain and kinetic energies at selected rotors and sort method.
Format:
ALL
PRINT PUNCH MODE
ROTSEKE = NONE
PLOT ROTOR
n
Examples:
SET 50 = 10, 20, 25 — Rotor ID set
ROTSEKE = 50
ROTSEKE (PLOT, MODE) = 50
ROTSEKE (PUNCH, MODE) = ALL
ROTSEKE (PRINT, PUNCH, ROTOR] = 50
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X** X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously.
** Rotor kinetic and strain energies .f06 in the output file will NOT be generated with
PARAM,ROTSEKE, X, specified in Bulk Data Section, and an UFM will be printed. PARAM,ROTSEKE
has been removed from MSC NASTRAN release 2021.3
MODE or (blank) Output will be presented as a tabular listing by mode number.
ROTOR Output will be presented as a tabular listing by rotor ID according to SET n.
All Rotor energies for all rotors will be output.
n Set identification number of a previously appearing SET command. Only rotor
IDs that appear on this SET command will be included in the rotor energies
output (Integer >0).
Main Index
572 MSC Nastran Quick Reference Guide
Rotor Modal Strain and Kinetic Energies Output Request
Remarks:
1. ROTSEKE is only available for direct or modal complex eigenvalue analysis in
SOLs 107/110/200/400.
2. For a model with one rotor only, the strain and kinetic energy percentages will always be 100%.
3. Mode type identification is only for line rotor (ROTORG), and the meaning of two-character mode
types are:
FW - Forward Whirl
FP - Partial Forward Whirl
BW - Backward Whirl
BP - Partial Backward Whirl
AX - Axial Mode
TR - Torsion Mode
BE - Pure Bending Mode
MX - Mixed Whirl Mode
NA - Unidentified
XX - Other (static rotor, or 2D/3D rotor)
Main Index
CHAPTER 5 573
Specifying Damping for the Residual Structure
RSDAMP (Case) Specifying Damping for the Residual Structure
Requests parameter and hybrid damping for the residual structure.
Format:
STRUCTURE
RSDAMP FLUID = n
BOTH
Example:
RSDAMP(STRUCTURE,FLUID, or BOTH) = n
Describer Meaning
n Identification number of a DAMPING Bulk Data entry (Integer > 0).
Remarks:
1. For modal solutions, this entry adds to the modal damping that may be specified by the SDAMPING
Case Control command.
2. This command can be different in each residual structure subcase.
Main Index
574 MSC Nastran Quick Reference Guide
Solution Set Acceleration Output Request
SACCELERATION (Case) Solution Set Acceleration Output Request
Requests the form and type of solution set acceleration output.
Format:
ALL
SORT1 REAL or IMAG
SACCELERATION ( PRINT, PUNCH, ) = n
SORT2 PHASE
NONE
Examples:
SACCELERATION=ALL
SACCELERATION(PUNCH,IMAG)=142
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load,
frequency, eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid
point (or mode number).
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output
is in degrees.
ALL Acceleration for all solution set points (modes) will be output.
NONE Acceleration for no solution set points (modes) will be output.
n Set identification number of a previously appearing SET command. Only
accelerations of points with identification numbers that appear on this SET
command will be output (Integer > 0).
Remarks:
1. Acceleration output is only available for transient and frequency response problems.
2. The defaults for SORT1 and SORT2 depend on the type of analysis, and are discussed in Remark 1
under the DISPLACEMENT (Case) Case Control command. If SORT1 is selected for any of the
commands SACC, SDIS, and SVEL, then the remaining commands will also be SORT1.
3. SACCELERATION=NONE allows an overall output request to be overridden.
Main Index
CHAPTER 5 575
Solution Set Acceleration Output Request
4. In modal frequency and transient analyses with both structural and fluid modes, the solution set
output request results in separate outputs for structural and fluid modal solutions. The first set is for
the structural modal solution and the second set is for the fluid.
Main Index
576 MSC Nastran Quick Reference Guide
Structural Damping Selection
SDAMPING (Case) Structural Damping Selection
Requests modal damping as a function of natural frequency in modal solutions or viscoelastic materials as a
function of frequency in direct frequency response analysis.
Format:
STRUCTURE
SDAMPING FLUID = n
COUPLED
Example:
SDAMPING=77
SDAMPING(COUPLED)=100
Describer Meaning
STRUCTURE Modal damping is requested for the structural or fluid portion of the model.
or FLUID
COUPLED Modal damping is requested for the structure and fluid coupled portion of the
model.
n Set identification number of a TABDMP1 or TABLEDi Bulk Data entry
(Integer>0).
Remarks:
1. In the modal solutions (e.g., SOLs 110, 111, 112, 145, 146, and 200), SDAMPING must reference
a TABDMP1 entry.
2. In direct frequency response analysis (e.g., SOL 108) or nonlinear harmonic analysis (e.g., SOL 128),
SDAMPING must reference a TABLEDi entry which defines viscoelastic (frequency-dependent)
material properties. See Viscoelastic Material Properties in the MSC Nastran Dynamic Analysis User’s
Guide. TABLEDi,n and TABLEDi,n+1 must be specified in the Bulk Data to define the complex
moduli of the viscoelastic materials.
3. When SDAMPING is defined for a superelement, PARAM,SESDAMP must be placed either in the
SUBCASE for the superelement or in the superelement’s BEGIN SUPER section in order to activate
the modal damping for the superelement. The default for superelements is to place all boundary
points in the B set; in this case, PARAM,SESDAMP,AUG is recommended. Alternatively, place all
boundary points in the C set and set PARAM,SESDAMP,YES.
4. When SDAMPING is used during FRF component generation, PARAM,KDAMP,-1 is
recommended in order to place the modal damping terms in the imaginary part of the stiffness matrix.
The default for KDAMP is 0, which places the modal damping terms in the damping matrix, leading
to a marginally under or over damped response. When hybrid damping is used during FRF
component generation, it is recommended to set the KDAMP field to YES on the HYBDAMP entry.
Main Index
CHAPTER 5 577
Structural Damping Selection
5. When SDAMPING is used with METHOD(COUPLED), SDAMPING(COUPLED) should be
used. For the real coupled mode computation, structural modes and fluid modes are not separated.
So SDAMPING(STRUCTURE) or SDAMPING(FLUID) cannot be used properly. When
SDAMPING(STRUCTURE/FLUID) is used with METHOD(COUPLED), it returns fatal out.
Main Index
578 MSC Nastran Quick Reference Guide
Solution Set Displacement Output Request
SDISPLACEMENT (Case) Solution Set Displacement Output Request
Requests the form and type of solution set displacement output.
Format:
ALL
SORT1 REAL or IMAG
SDISPLACEMENT ( PRINT, PUNCH, ) = n
SORT2 PHASE
NONE
Examples:
SDISPLACEMENT=ALL
SDISPLACEMENT(SORT2,PUNCH,PHASE)=NONE
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load,
frequency, eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid
point (or mode number).
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase
output is in degrees.
ALL Displacements for all solution set points (modes) will be output.
NONE Displacements for no solution set points (modes) will be output.
n Set identification number of a previously appearing SET command. Only
displacements on points with identification numbers that appear on this SET
command will be output (Integer > 0).
Remarks:
1. The defaults for SORT1 and SORT2 depend on the type of analysis, and is discussed in Remark 1
under the DISPLACEMENT (Case) Case Control command. If SORT1 is selected for any of the
commands SACC, SDIS, and SVEL then the remaining commands will also be SORT1.
2. SDISPLACEMENT=NONE allows an overall output request to be overridden.
3. The SDISPLACEMENT command is required to output normalized complex eigenvectors.
Main Index
CHAPTER 5 579
Solution Set Displacement Output Request
4. In modal frequency and transient analyses with both structural and fluid modes, the solution set
output request results in separate outputs for structural and fluid modal solutions. The first set is for
the structural modal solution and the second set is for the fluid.
Main Index
580 MSC Nastran Quick Reference Guide
Superelement Generation and Assembly
SEALL (Case) Superelement Generation and Assembly
Specifies the superelement identification numbers of Phase 1 processing in which all matrices and loads are
generated and assembled. Controls execution of the solution sequence.
Format:
ALL
SEALL = n
i
Examples:
SEALL=ALL
SEALL=7
Describer Meaning
ALL Generate and assemble all superelements.
n Set identification number of a previously appearing SET command. Only
superelements with identification numbers that appear on this SET command will be
generated and assembled (Integer > 0).
i Identification number of a single superelement that will be generated and assembled
(Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number of the residual structure, and can only appear as a member of a
SET.
3. For a further discussion of this command, see Superelement Analysis in the MSC Nastran Reference
Guide.
4. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
5. This command combines, in one command, the functions of the SEMG, SELG, SEKR, SELR, and
SEMR commands.
6. This command does not control superelement data recovery (Phase 3). See the SEDR (Case) Case
Control command description.
7. SEALL=ALL is the default but can be overridden by specifying any of the following Phase 1
commands: SEALL, SEMG, SELG, SEKR, SELR, or SEMR.
Main Index
CHAPTER 5 581
Specifying Damping for Superelements
SEDAMP (Case) Specifying Damping for Superelements
Requests parameter and hybrid damping for superelements.
Format:
SEDAMP=n
Example:
Describer Meaning
n Identification number of a DAMPING Bulk Data entry (Integer > 0).
Remarks:
1. This command adds to the modal damping that may be specified by the Case Control command
SDAMPING, used in conjunction with PARAM,SESDAMP,YES.
2. Multiple SEDAMP requests per superelement are not allowed. If more than one SEDAMP request is
specified per superelement, the second and subsequent requests will be ignored.
Main Index
582 MSC Nastran Quick Reference Guide
Superelement Data Recovery
SEDR (Case) Superelement Data Recovery
Specifies the superelement identification numbers for which data recovery will be performed.
Format:
ALL
SEDR = n
i
Examples:
SEDR=ALL
SEDR=7
Describer Meaning
ALL Performs data recovery for all superelements.
n Set identification number of a previously appearing SET command. Data recovery will
be performed for superelements with identification numbers that appear on this SET
command (Integer > 0).
i Identification number of a single superelement for which data recovery will be
performed (Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number for the residual structure, and can only appear as a member of
a SET.
3. For a further discussion of this command, see Superelement Analysis in the MSC Nastran Reference
Guide.
4. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
5. If this command is not present, data recovery is performed for all superelements for which there are
output requests (i.e., the default for this command is SEDR=ALL).
6. The presence of the EXTDROUT Case Control command or the user PARAMeter EXTDROUT
forces SEDR=ALL.
Main Index
CHAPTER 5 583
Superelement Design Variable Processing
SEDV (Case) Superelement Design Variable Processing
Specifies the superelement identification numbers for which the design variables will be processed.
Format:
ALL
SEDV = n
i
Examples:
SEDV=ALL
SEDV=18
Describer Meaning
ALL Requests design variable processing for all superelements. This is the default value if
SEDV is missing in the file.
n Set identification number of a previously appearing SET command. Design variable
processing will be performed for superelements with identification numbers that
appear on this SET command (Integer > 0).
i Identification number of a single superelement for which design variable processing
will be performed (Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number of the residual structure, and can only appear as a member of a
SET.
3. For a further discussion of superelement sensitivity analysis, see the MSC.Nastran Design Sensitivity
and Optimization User’s Guide.
4. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
5. If both the SEDV and SERESP commands are not present, then the design variable processing and
design sensitivity matrix generation will be performed for all superelements.
Main Index
584 MSC Nastran Quick Reference Guide
Superelement Matrix and Load Assembly Exclusion
SEEXCLUDE (Case) Superelement Matrix and Load Assembly Exclusion
Specifies the superelement identification numbers for which all matrices and loads will not be assembled into
the downstream superelement.
Format:
ALL
SEEXCLUDE = n
i
Examples:
SEEXCLUDE=ALL
SEEXCLUDE=18
Describer Meaning
ALL All upstream superelements will be excluded.
n Set identification number of a previously appearing SET command. Only those
superelements with identification numbers that appear on this SET command will
be excluded (Integer > 0).
i Identification number of a single superelement for which matrices will be excluded
(Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
3. This command is not meaningful when applied to the residual structure.
4. For a further discussion of this command, see the MSC Nastran Handbook for Superelement Analysis.
5. If the SEEXCLUDE command is specified in a restart of SOLs 101 through 200, then
PARAM,SERST,MANUAL must be specified. Also, the SEKR command must be specified for the
superelement immediately downstream from the excluded superelement. For example, if
superelement 10 is excluded in the following superelement tree:
,
10 20
30 40
0
then the user must specify the following commands in the Case Control Section:
SEKR = 30
Main Index
CHAPTER 5 585
Superelement Matrix and Load Assembly Exclusion
PARAM,SERST,MANUAL
Main Index
586 MSC Nastran Quick Reference Guide
Final Superelement for Assembly
SEFINAL (Case) Final Superelement for Assembly
Specifies the superelement identification number for the final superelement to be assembled.
Format:
SEFINAL = n
i
Example:
SEFINAL=14
Describer Meaning
n Set identification of a previously appearing SET command. Each superelement
identification number appearing on the SET command must belong to a disjoint
model (Integer > 0).
i Identification number of the final superelement to be assembled (Integer > 0).
Remarks:
1. If this command is not present, the program selects the order of the superelements for assembly
operations.
2. This command, if present, must be located before the first SUBCASE command.
3. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
4. This command can be used on restarts to ensure that minor modeling changes do not also change the
processing order. For this usage, inspect the SEMAP table to determine which superelements were
final superelements on the prior run.
5. See the MSC Nastran Handbook for Superelement Analysis for a further discussion of this command.
Main Index
CHAPTER 5 587
Superelement Stiffness Matrix Assembly and Reduction
SEKREDUCE (Case) Superelement Stiffness Matrix Assembly and Reduction
Specifies the superelement identification numbers for which stiffness matrices are assembled and reduced.
Format:
ALL
SEKREDUCE = n
i
Examples:
SEKREDUCE=ALL
SEKREDUCE=9
Describer Meaning
ALL Assembles and reduces matrices for all superelements.
n Set identification number of a previously appearing SET command. Matrices will
only be assembled for superelements with identification numbers that appear on this
SET command (Integer > 0).
i Identification number of a single superelement for which the stiffness matrix will be
assembled and reduced (Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number for the residual structure, and can only appear as a member of
a SET.
3. For a further discussion of this command, see Superelement Analysis in the MSC Nastran Reference
Guide.
4. SEKREDUCE is an alternate form, and is entirely equivalent to the obsolete command
SEMASSEMBLE.
5. SEALL=ALL is the default, but can be overridden by specifying any of the following Phase 1
commands: SEALL, SEMG, SELG, SEKR, SELR, or SEMR.
Main Index
588 MSC Nastran Quick Reference Guide
Superelement Load Generation
SELGENERATE (Case) Superelement Load Generation
Specifies the superelement identification numbers for which static loads will be generated.
Format:
ALL
SELGENERATE = n
i
Examples:
SELGENERATE=ALL
SELGENERATE=18
Describer Meaning
ALL Generates static loads for all superelements.
n Set identification number of a previously appearing SET command. Static load
matrices will only be generated for superelements with identification numbers that
appear on this SET command (Integer > 0).
i Identification number of a single superelement for which load matrices will be
generated (Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number of the residual structure, and can only appear as a member of a
SET.
3. For a further discussion of this command, see Superelement Analysis in the MSC Nastran Reference
Guide.
4. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
5. SEALL=ALL is the default, but can be overridden by specifying any of the following Phase 1
commands: SEALL, SEMG, SELG, SEKR, SELR, or SEMR.
Main Index
CHAPTER 5 589
Superelement Load Assembly and Reduction
SELREDUCE (Case) Superelement Load Assembly and Reduction
Specifies the superelement identification numbers for which the static load matrices will be assembled and
reduced.
Format:
ALL
SELREDUCE = n
i
Examples:
SELREDUCE=ALL
SELREDUCE=9
Describer Meaning
ALL Assembles and reduces matrices for all superelements.
n Set identification number of a previously appearing SET command. Matrices will
be assembled only for superelements with identification numbers that appear on
this SET command (Integer > 0).
i Identification number of a single superelement for which the load matrices will be
assembled and reduced (Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number for the residual structure, and can only be appear as a member
of a SET.
3. For a further discussion of this command, see Superelement Analysis in the MSC Nastran Reference
Guide.
4. This command is used on restarts to selectively assemble and reduce load matrices.
5. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
6. In superelement static analysis, SELREDUCE is equivalent to SELASSEMBLE.
7. In dynamic analysis, SELASSEMBLE combines the functions of SELREDUCE and SEMREDUCE.
8. SEALL=ALL is the default, but can be overridden by specifying and of the following Phase 1
commands: SEALL, SEMG, SELG, SEKR, SELR, or SEMR.
Main Index
590 MSC Nastran Quick Reference Guide
Superelement Matrix Generation
SEMGENERATE (Case) Superelement Matrix Generation
Specifies the superelement identification numbers for which stiffness, mass, and damping matrices will be
generated.
Format:
ALL
SEMGENERATE = n
i
Examples:
SEMGENERATE=ALL
SEMGENERATE=7
Describer Meaning
ALL Generates structural matrices for all superelements.
n Set identification number of a previously appearing SET command. Structural
matrices will only be generated for superelements with identification numbers that
appear on this SET command (Integer > 0).
i Identification number of a single superelement for which structural matrices will be
generated (Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number for the residual structure, and can only appear as a member of
a SET.
3. For a further discussion of this command, see Superelement Analysis in the MSC Nastran Reference
Guide.
4. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
5. SEALL=ALL is the default, in the structured SOLs 101 through 200. This default can be overridden
by specifying any of the following Phase 1 commands: SEALL, SEMG, SELG, SEKR, SELR, or
SEMR.
Main Index
CHAPTER 5 591
Superelement Mass and Damping Assembly and Reduction
SEMREDUCE (Case) Superelement Mass and Damping Assembly and Reduction
Specifies the superelement identification numbers for which the mass and damping matrices will be
assembled and reduced. In buckling analysis, the differential stiffness matrices will be assembled and reduced.
Format:
ALL
SEMREDUCE = n
i
Examples:
SEMREDUCE=ALL
SEMREDUCE=9
Describer Meaning
ALL Assembles and reduces matrices for all superelements.
n Set identification number of a previously appearing SET command. Matrices will
only be assembled for superelements with identification numbers that appear on this
SET command (Integer > 0).
i Identification number of a single superelement for which the load matrices or the
mass and damping matrices will be assembled and reduced (Integer > 0).
Remarks:
1. This command, if present, must be located before the first SUBCASE command.
2. Zero (0) is the identification number for the residual structure, and can only appear as a member of
a set.
3. This command is used on restart to selectively assemble and reduce mass and damping matrices. For
a further discussion of this command, see Superelement Analysis in the MSC Nastran Reference Guide.
4. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
5. In dynamic analysis, SELASSEMBLE combines the functions of SELREDUCE and SEMREDUCE.
6. This command has no function in static analysis.
7. SEALL=ALL is the default but can be overridden by specifying any of the following Phase 1
commands: SEALL, SEMG, SELG, SEKR, SELR, or SEMR.
Main Index
592 MSC Nastran Quick Reference Guide
Superelement Response Sensitivity
SERESP (Case) Superelement Response Sensitivity
Specifies the superelement identification numbers for which the design sensitivity matrices will be generated.
Format:
ALL
SERESP = n
i
Examples:
SERESP=ALL
SERESP=18
Describer Meaning
ALL Requests design sensitivity matrix generation for all superelements. This is the
default value if SERESP is missing.
n Set identification number of a previously appearing SET command. Design
sensitivity matrices will be generated for superelements with identification
numbers that appear on this SET command (Integer > 0).
i Identification number of a single superelement for which the design sensitivity
matrix will be generated.
Remarks:
1. This command, if present, then it must be located before the first SUBCASE command.
2. Zero (0) is the identification number of the residual structure, and can only appear as a member of a
SET.
3. For a further discussion of this command, see the MSC Nastran Reference Guide.
4. If i is used, the superelement identification number must be unique with respect to any SET
identification numbers used.
5. If both the SEDV and SERESP commands are not present, then the design variable processing and
design sensitivity matrix generation will be performed for all superelements.
Main Index
CHAPTER 5 593
Set Definition, General Form
SET (Case) Set Definition, General Form
Sets are used to define the following lists:
1. Identification numbers (point, element, or superelement) for processing and output requests.
2. Frequencies for which output will be printed in frequency response problems, or times for transient
response, using the OFREQ and OTIME commands, respectively.
3. Surface or volume identification numbers to be used in GPSTRESS or STRFIELD commands.
4. DRESP1 entries that are used in the spanning of subcases.
5. Grid point number and component type code to be used by the MCFRACTION command.
6. Trim component (TRMC) identification numbers and set identification numbers to be used by the
TDISPLACEMENT, TVELOCITY, and TACCELERATION commands.
Formats:
SET n = i 1 ,i 2 i 3 THRU i 4 EXCEPT i 5 i 6 i 7 i 8 THRU i 9
SET n = r 1 ,r 2 r 3 r 4
SET n = ALL
SET n = i 1 c 1 ,i 2 c 2 i 3 c 3 i 4 c 4
SET n = t 1 s 1 ,t 2 s 2 t 3 s 3 t 4 s 4
SET n = l 1 l 2 l 3
Examples:
SET 77=5
SET 88=5, 6, 7, 8, 9, 10 THRU 55 EXCEPT 15, 16, 77, 78, 79, 100 THRU 300
SET 99=1 THRU 100000
SET 101=1.0, 2.0, 3.0
SET 105=1.009, 10.2, 13.4, 14.0, 15.0
SET 1001=101/T1, 501/T3, 991/R3
SET 17 = 3/103, 5/0, 12/ALL
SET 2001=M1,M2
Describer Meaning
n Set identification number. Any set may be redefined by reassigning its identification
number. SETs specified under a SUBCASE command are recognized for that
SUBCASE only (Integer > 0).
i 1 c 1 Grid point identification numbers and component codes. The c values must be of
T1, T2, T3, R1, R2 or R3.
t 1 t 2 , etc. Trim component (TRMC) identification numbers.
Main Index
594 MSC Nastran Quick Reference Guide
Set Definition, General Form
Describer Meaning
l 1 l 2 , etc. Identification names of literals used for matrix or group selection.
s 1 s 2 , etc. Set identification numbers of previously defined SETs.
i 1 i 2 , etc. Identification numbers. If no such identification number exists, the request is
ignored (Integer > 0).
i 3 THRUi 4 Identification numbers i 4 i 3 (Integer>0).
EXCEPT Set identification numbers following EXCEPT will be deleted from output list as
long as they are in the range of the set defined by the immediately preceding THRU.
An EXCEPT list may not include a THRU list or ALL.
r 1 r 2 , etc. Frequencies or times for output. The nearest solution frequency or time will be
output. EXCEPT and THRU cannot be used. If an OFREQ or OTIME command
references the set then the values must be listed in ascending sequences,
r 1 r 2 r 3 r 4 ...etc., otherwise some output may be missing. If an OFREQ or
OTIME command is not present, all frequencies or times will be output (Real >
0.0).
ALL All members of the set will be processed.
Remarks:
1. A SET command may be more than one physical command. A comma at the end of a physical
command signifies a continuation command. Commas may not end a set. THRU may not be used
for continuation. Place a number after the THRU.
2. Set identification numbers following EXCEPT within the range of the THRU must be in ascending
order.
3. In SET 88 above, the numbers 77, 78, etc., are included in the set because they are outside the prior
THRU range.
4. SET commands using the grid point/component code format cannot contain THRU. SETs using
this format should be selected only by the MCFRACTION, PFPANEL, PFMODE and PEAKOUT
PEAKFRFS Case Control command.
5. SET commands using literals apply only to direct matrix input such as K2PP, etc. or FLSPOUT panel
grouping.
6. SET commands using the trim component/set format cannot contain THRU or EXCEPT and may
be selected only by the TDISPLACEMENT, TVELOCITY, and TACCELERATION commands.
Main Index
CHAPTER 5 595
Process Set Definition
SETP (Case) Process Set Definition
Process sets are used to define lists of SET identifications to be processed individually for data recovery:
Formats:
SETP n = i 1 i 2 i 3 THRU i 4 EXCEPT i 5 i 6 i 7 i 8 THRU i 9
Examples:
SETP 77=5, 6
SETP 88=5, 6, 7, 8, 9, 10 THRU 55
Describer Meaning
n SETP identification number. Any SETP may be redefined by reassigning its
identification number. SETPs specified under a SUBCASE command are recognized
for that SUBCASE only (Integer > 0).
i1, i2, ...., in SET identification numbers i1, i2, etc. If no such identification number exists, the
request is ignored (Integer > 0).
EXCEPT Set identification numbers following EXCEPT will be deleted from output list as
long as they are in the range of the set defined by the immediately preceding THRU.
An EXCEPT list may not include a THRU list or ALL.
Remarks:
1. A SETP command may be more than one physical command. A comma at the end of a physical
command signifies a continuation command. Commas may not end a set. THRU may not be used
for continuation—place a number after the THRU.
2. Set identification numbers following EXCEPT,k within the range of the THRU, must be in
ascending order.
3. SETP usage is limited to the EDE, EKE and ESE Case Control commands.
Main Index
596 MSC Nastran Quick Reference Guide
Case Control Processing Delimiter
SETS DEFINITION (Case) Case Control Processing Delimiter
Delimites the various type of commands under grid point stress. This command is synonymous with
OUTPUT(POST).
Format:
SETS DEFINITION
Example:
SETS DEFINITION
Remark:
1. Either SETS DEFINTIION or OUTPUT(POST) may be specified, but not both.
Main Index
CHAPTER 5 597
Case Control Processing Delimiter
SKIP (Case) Case Control Processing Delimiter
Activates or deactivates the execution of subsequent commands in Case Control (including plot commands).
Format:
SKIP ON
OFF
Example:
SKIPOFF
Remarks:
1. SKIPON and SKIPOFF commands may appear as many times as needed in the Case Control
Section.
2. Commands that are skipped will be printed.
3. SKIPON ignores subsequent commands until either a SKIPOFF or BEGIN BULK command is
encountered. This allows the user to omit requests without deleting them from the data. In the
following example, plot commands will be skipped.
TITLE=EXAMPLE
SPC=5
LOAD=6
SKIPON$SKIP PLOT REQUEST
OUTPUT (PLOT)
SET 1 INCLUDE ALL
FIND
PLOT
BEGIN BULK
Main Index
598 MSC Nastran Quick Reference Guide
PSHELL entries listed on this entry will have MID2-MID4 fields removed
SLDSKIN (Case) PSHELL entries listed on this entry will have MID2-MID4 fields removed
Requests that PSHELL entries listed on this entry, when the THICKNESS ≤ TOL have their MID2 through
MID4 fields removed; thus, converting the elements membrane elements.
Format:
ALL
SLDSKIN TOL = n
NONE
Example:
SLDSKIN = 5
Describer Meaning
TOL For any PSHELL identified on this entry, the MID2 through MID4 fields will be set
to blank, only if the T value is ≤ TOL value. (Real ≥ 0.0; Default=1.E-3).
ALL ALL PSHELL entries are to have their MID2-MID4 fields removed provided their T
value is ≤ TOL value. (Character).
n ID of SET3 bulk data entry pointing to a list of properties to have MID2-MID4
removed from their PSHELL entries provided their T value is ≤TOL value.
(Integer>0)
NONE Default leave PSHELL entries alone. (Character, Default).
Remarks:
1. This entry must be placed above the first Subcase.
2. This entry is primarily for use with solid elements skinned with thin shell structures to recover surface
stress under membrane action.
3. Extreme caution should be exercised in the use of this entry.
4. If a SET3 entry is specified that cannot be found the following User Fatal is issued:
*** USER FATAL MESSAGE 9306 (SLDSKIN)
SET ID x ON THE SLDSKIN CASE CONTROL COMMAND REFERS TO A NON-EXISTENT
SET3 ENTRY
Main Index
CHAPTER 5 599
Iterative Solver Method Selection
SMETHOD (Case) Iterative Solver Method Selection
Selects iterative solver method and parameters.
Note that SMETHOD is not supported in NLPERF SOL 400.
Format:
ELEMENT
SMETHOD n
MATRIX
Example:
SMETHOD = ELEMENT $ selects element-based iterative solver defaults.
SMETHOD = MATRIX $ selects matrix based iterative solver defaults.
SMETHOD = 1000 $ specifies ID of ITER Bulk Data entry to select
iterative.
Describer Meaning
ELEMENT Selects the element-based iterative solver with default control values.
MATRIX Selects the matrix-based iterative solver with default control values.
n Sets identification of an ITER Bulk Data entry (Integer > 0).
Remarks:
1. The matrix-based iterative solver is available in SOLs 101, 106, 108, 111, 153, and 400 and allows
use of all features.
2. The element-based iterative solver is only available in SOLs 101, 200 and 400. SMETHOD must be
placed above all SUBCASEs in this case. It is intended primarily for very large solid element models.
See the ITER Bulk Data entry for a list of restrictions in addition to details on setting the convergence
parameter epsilon.
3. The element-based iterative solver can be used with SMP by setting smp=number on the command
line. Please refer to smp of this manual for correct usage.
4. GPGPU devices are not supported for iterative methods.
Main Index
600 MSC Nastran Quick Reference Guide
Solution ID Selection
SOLUTION (Case) Solution ID Selection
Selects the solution ID for a 3rd step external superelement data recovery restart in SOL 400.
Format:
SOLUTION = n
Example:
SOLUTION=10
Describer Meaning
n Solution identification number.
Remarks:
1. SOLUTION command is used only in SOL 400 for 3rd step external superelement data recovery
restart.
2. See Remark 8. under EXTDRIN Case Control command’s description for a further explanation and
example.
Main Index
CHAPTER 5 601
Single Point Constraint Set Selection
SPC (Case) Single Point Constraint Set Selection
Selects a single point constraint set to be applied.
Format:
SPC = n
Example:
SPC=10
Describer Meaning
n Set identification number of a single-point constraint that appears on an SPC,
SPC1, SPC2 (SOL 700), FRFSPC1 (in FRF Based Assembly or FBA process) or
SPCADD Bulk Data entry (Integer > 0).
Remarks:
1. In cyclic symmetry analysis, this command must appear above the first SUBCASE command.
2. Multiple boundary conditions are only supported in SOLs 101, 103, 105, 145, and 200. Multiple
boundary conditions are not allowed for upstream superelements. The BC command must be
specified to define multiple boundary conditions for the residual structure in SOLs 103, 105, 145,
and 200.
Main Index
602 MSC Nastran Quick Reference Guide
Single Point Forces of Constraint Output Request
SPCFORCES (Case) Single Point Forces of Constraint Output Request
Requests the form and type of single point force of constraint vector output.
Format:
SPCFORCES ( SORT1 PRINT, PUNCH REAL or NOZPRINT PSDF, ATOC, CRMS ,
SORT2 PLOT PHASE or RALL
ALL
RPRINT
RPUNCH CID ) = n
NORPRINT
NONE
Examples:
SPCFORCES = 5
SPCFORCES(SORT2, PUNCH, PRINT, IMAG) = ALL
SPCFORCES(PHASE) = NONE
SPCFORCES(SORT2, PRINT, PSDF, CRMS, RPUNCH)=20
SPCFORCES(PRINT, RALL, NORPRINT)=ALL
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load, frequency,
eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid
point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is
in degrees.
Main Index
CHAPTER 5 603
Single Point Forces of Constraint Output Request
Describer Meaning
NOZPRINT Print only nonzero SPC forces appearing in SORT2 output. This keyword does
not affect SORT1 output.
PSDF Requests the power spectral density function be calculated and stored in the
database for random analysis postprocessing. The request must be made above the
subcase level, and RANDOM must be selected in Case Control. See Remark 9.
ATOC Requests the autocorrelation function be calculated and stored in the database for
random analysis postprocessing. Request must be made above the subcase level,
and RANDOM must be selected in Case Control. See Remark 9.
CRMS Requests the cumulative root mean square function be calculated for random
analysis postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in Case Control. See Remark 9.
RALL Requests all of PSDF, ATOC, and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM
must be selected in Case Control. See Remark 9.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
PRUNCH Writes random analysis results in the punch file.
CID Request to print output coordinate system ID in printed output file (.f06).
ALL Single point forces of constraint for all points will be output. See Remarks 1. and 4.
NONE Single point forces of constraint for no points will be output.
n Set identification of a previously appearing SET command. Only single point
constraint forces for points with identification numbers that appear on this SET
command will be output (Integer > 0).
Remarks:
1. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2. In the SORT1
format, only nonzero values will be output.
2. In a statics problem, a request for SORT2 causes loads at all points (zero and nonzero) to be output.
3. SPCFORCES=NONE overrides an overall output request.
4. In SORT1 format, SPCFORCES recovered at consecutively numbered scalar points are printed in
groups of six (sextets) per line of output. However, if a scalar point is not consecutively numbered, it
will begin a new sextet on a new line of output. If a sextet can be formed and all values are zero, then
the line will not be printed. If a sextet cannot be formed, then zero values may be output.
5. SPCFORCES results are output in the global coordinate system (see field CD on the GRID Bulk
Data entry).
6. In SOLs 129 and 159, SPCFORCES results do not include the effects of mass and damping elements.
Main Index
604 MSC Nastran Quick Reference Guide
Single Point Forces of Constraint Output Request
7. In all solution sequences except SOLs 129 and 159, SPCFORCES results do include the effects of
mass and damping, except damping selected by the SDAMPING Case Control command.
PARAM,DYNSPCF,OLD may be specified to obtain SPCFORCES results, which do not include
mass and damping effects.
8. In inertia relief analysis in SOLs 101 and 200, the SPCFORCE output includes both the effects due
to inertial loads and applied loads.
9. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
10. Note that the CID keyword affects only grid point related output such as DISP, VELO, ACCE,
OLOAD, SPCF and MPCF. In addition, the CID keyword needs to appear only once in a grid-
related output command, anywhere in the Case Control Section, to turn on the printing algorithm.
11. For axisymmetric elements, SPCFORCES results are obtained by integrating over 1 radian of the
circumference. Before 2012 release, it is total reaction over the whole circumference.
Main Index
CHAPTER 5 605
Export of Spline Matrix
SPLINOUT (Case) Export of Spline Matrix
Requests output of the spline matrix for external use.
Format:
BOTH
SPLINOUT DISP OP2 = unit
DMIPCH
FORCE
Examples:
Describer Meaning
BOTH Requests output of the force and displacement splines (Default).
DISP Requests output of only the displacement splines.
FORCE Requests output of only the force splines.
OP2 Requests output to an .op2 file
unit Unit the .op2 file is assigned to
DMIPCH Requests output to a .pch file.
Remarks:
1. Matrices are output in external sort.
2. If displacement and force splines are identical, only displacement splines are output.
3. Option FACTORS is only allowed together with option OP2.
4. If OP2 = unit is specified, a table relating the matrix columns to structural degrees of freedom, and
the matrix rows to aerodynamic degrees of freedom, will be written to the .op2 file.
5. If OP2 = unit is specified, an appropriate ASSIGN OP2 statement must be present in the File
Management Section for this unit.
6. If DMIPCH is specified, DMI entries are written to the.pch file.
Main Index
606 MSC Nastran Quick Reference Guide
Static Solution Selection for Differential Stiffness
STATSUB (Case) Static Solution Selection for Differential Stiffness
Selects the static solution to use in forming the differential stiffness for static analysis, buckling analysis,
normal modes, complex eigenvalue, frequency response and transient response analysis.
Format:
BUCKLING
STATSUB ( ) = n
PRELOAD
Examples:
STATSUB=23
STAT=4
STATSUB(PREL)=7
Describer Meaning
BUCKLING Subcase ID number corresponding to static subcase of buckling or varying load (Default
in buckling analysis).
PRELOAD Subcase ID number corresponding to static subcase of preload or constant load (Default
in dynamic analysis).
n Subcase identification number of a prior subcase specified for static analysis (Integer > 0).
Remarks:
1. STATSUB may be used in SOLs 101,103, 105, 107 through 112, 115, 116, 200 and SOL 400
(ANALYSIS = BUCKLING only in SOL 200 and SOL 400).
2. STATSUB must be specified in the same subcase that contains the METHOD selection for buckling
or normal modes, CMETHOD for complex eigenvalue analysis, TSTEP for transient response, and
FREQ for frequency response.
3. In SOL 105, if it is intended that results from the first static subcase are used to compute the
differential stiffness, then the STATSUB command is not required. That is, the default for
STATSUB is the first static subcase identification. In SOLs 101, 103 and 107 through 112, 115, and
116, STATSUB must reference a separate static subcase.
4. In dynamic analysis, only one STATSUB command may be specified in each dynamic subcase. In
buckling analysis with a preload, both STATSUB (BUCKLING) and STATSUB(PRELOAD) must
be specified in each buckling subcase. STATSUB(PRELOAD) is not supported in SOL 200 or SOL
400. Buckling Analysis with a preload is not supported in SOL 200 and SOL 400.
5. In dynamic analysis, any subcase that does not contain a CMETHOD command in SOLs 107 and
110, a FREQUENCY command in SOLs 108 and 111, and a TSTEP command in SOLs 109 and
112, will be treated as a static subcase.
6. SOL 200 supports linear buckling analysis only, but do not support post-buckling (nonlinear
buckling analysis)
Main Index
CHAPTER 5 607
Static Solution Selection for Differential Stiffness
7. In versions prior to 2018, if it was desired to have a dynamic subcase with the effects of preload and
another subcase without the effects of preload, then a static subcase with null load was required and
its ID was referenced by STATSUB in the dynamic subcase without the effects of preload. In version
2018, STATSUB in the dynamic subcase without the effects of preload is no longer required. If the
STATSUB is not removed and still references the static subcase with null load, then User Fatal
Message 9244 will be issued.
Main Index
608 MSC Nastran Quick Reference Guide
Step Delimiter
STEP (Case) Step Delimiter
Delimits and identifies a nonlinear analysis step for SOL 400.
For its usage in NLPERF SOL 400, refer to STEP (CASE) in the Ap. C: NLPERF SOL 400.
Format:
STEP=n
Examples:
STEP=10
Describer Meaning
n Step identification number (Integer > 0).
Remarks:
1. The STEP command can only be used in nonlinear solution sequence SOL 400 (NONLIN).
2. The STEP command is to be used below the SUBCASE Case Control command. If no SUBCASE
is specified, MSC Nastran creates a default SUBCASE 1.
3. The STEP identification number n in a SUBCASE must be in increasing order, and less than
9999999.
4. The following example illustrates a typical application of SUBCASE and STEP:
SUBCASE 1
STEP 1
LOAD = 1
STEP 2
LOAD = 2
SUBCASE 2
STEP 10
LOAD = 10
STEP 20
LOAD = 20
5. The solutions of all SUBCASEs are independent of each other. However, the solution of any STEP
is a continuation of the solution of the previous STEP.
Main Index
CHAPTER 5 609
Randomization of Model Parameters
STOCHASTICS (Case) Randomization of Model Parameters
Request randomization of all or selected subsets of model parameters.
Note that STOCHASTICS is not supported in NLPERF SOL 400.
Format:
STOCHASTICS = ALL
n
Examples:
STOCHASTICS=10
Describer Meaning
ALL All real values of C-entries, M-entries, P-entries, loading entries, and SPCD entries
are to be randomized.
n Set identification number of a STOCHAS Bulk Data entry (Integer > 0).
Remarks:
1. Only one STOCHASTICS command may appear in the Case Control Section and should appear
above all SUBCASE commands.
2. The STOCHASTICS = n command may be used to request randomizing a set of analysis model
parameters with user specified statistics. (See Remark 1 of the STOCHAS Bulk Data entry.)
3. The default (STOCHASTICS = all) randomizes all scalar analysis model parameters that are real
values on the C-entries, M-Entries, P-entries, all loading entries, and SPCD entries with default
coefficients of variance (0.05) and multipliers of standard deviations (m=3.).
4. This command will only invoke a single Nastran randomization run. Separate runs can be submitted
to achieve different randomizations.
Main Index
610 MSC Nastran Quick Reference Guide
Element Strain Output Request
STRAIN (Case) Element Strain Output Request
Requests the form and type of strain output.
Format:
NONE
SORT1 PRINT, PUNCH PRINT, PUNCH
STRAIN ( ODS = sid
SORT2 PLOT PLOT
ALL
REAL or IMAG VONMISES STRCUR
PHASE MAXS or SHEAR FIBER
CENTER
CORNER or BILIN PSDF, ATOC, CRMS RPRINT
RPUNCH ) =
SGAGE or RALL NORPRINT
CUBIC
ALL
n
NONE
Examples:
STRAIN=5
STRAIN(CORNER)=ALL
STRAIN(PRINT,PHASE)=15
STRAIN(PLOT)=ALL
STRAIN(PRINT, PSDF, CRMS, RPUNCH)=20
STRAIN(PRINT, RALL,NORPRINT)=ALL
STRAIN (CORNER, PUNCH, ODS(PLOT)=ALL) = 100
Describer Meaning
SORT1 Output will be presented as a tabular listing of elements for each load, frequency,
eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each element.
Main Index
CHAPTER 5 611
Element Strain Output Request
Describer Meaning
PRINT or (blank) Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PUNCH X X*
PLOT X X*
X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ODS Requests Operational Deflection Shape (ODS) element strain output. See Remark
12.
sid Set identification of a previously appearing SET command. Only element strains
in elements that appear on this SET command will be output as ODS element
strains (Integer > 0).
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is
in degrees.
PSDF Requests the power spectral density function be calculated and stored in the
database for random analysis postprocessing. The request must be made above the
subcase level, and RANDOM must be selected in Case Control. See Remark 9.
ATOC Requests the autocorrelation function be calculated and stored in the database for
random analysis postprocessing. The request must be made above the subcase
level, and RANDOM must be selected in Case Control. See Remark 9.
CRMS Requests the cumulative root mean square function to be calculated for random
analysis postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in Case Control. See Remark 9.
RALL Requests all of PSDF, ATOC, and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM
must be selected in Case Control. See Remark 9.
VONMISES von Mises strains are output.
MAXS or Maximum shear strains are output.
SHEAR
STRCUR Strain at the reference plane and curvatures are output for plate elements.
FIBER Strain at locations Z1, Z2 are computed for plate elements.
CENTER Output CQUAD4 element strains at the center only.
CORNER or Output CQUAD4 element strains at the center and grid points. Using strain gage
BILIN approach with bilinear extrapolation.
Main Index
612 MSC Nastran Quick Reference Guide
Element Strain Output Request
Describer Meaning
SGAGE Output CQUAD4 element strains at center and grid points using strain gage
approach.
CUBIC Output CQUAD4 element strains at center and grid points using cubic bending
correction.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
RPUNCH Writes random analysis results in the punch file.
ALL Strain for all elements will be output.
n Set identification of a previously appearing SET command. Only strain for
elements with identification numbers that appear on this SET command will be
output (Integer > 0).
NONE No element strain will be output.
Remarks:
1. Fully accurate nonlinear strains for nonlinear elements are requested by the STRESS command and
appear in the nonlinear stress output. In SOLs 106 and 129, if LGDISP > 0 the center, and if
requested for CQUAD4 the corner, strains are computed from the displacements alone and are only
approximate. If LGDISP = -1 and material nonlinear then no STRAIN output will be created. In
SOL 400, if enhanced material options are used, the computed strains are accurate and in this case a
CQUAD4 corner request is ignored.
2. In SOLs 106 and 129, the STRAIN request pertains only to linear elements and only if the parameter
LGDISP is -1, which is the default. Nonlinear strains for nonlinear elements are requested by the
STRESS command and appear in the nonlinear stress output.
3. STRAIN=NONE overrides an overall output request.
4. Definitions of stress, strain, curvature, and output locations are given in the Structural Elements in the
MSC Nastran Reference Guide.
5. If the STRCUR option is selected, the values of Z1 will be set to 0.0. and Z2 will be set to -1.0 on
the output.
6. The VONMISES, MAXS, and SHEAR options are ignored in the complex eigenvalue and frequency
response solution sequences.
7. The options CENTER, CORNER, CUBIC, SGAGE, and BILIN are recognized only in the first
subcase, and determine the option to be used in all subsequent subcases with the STRESS, STRAIN,
and FORCE commands. (In superelement analysis, the first subcase refers to the first subcase of each
superelement. Therefore, it is recommended that these options be specified above all subcases.)
Consequently, options specified in subcases other than the first subcase will be ignored. See also
Remark 8 under the FORCE (Case) Case Control command for further discussion.
The above options apply only to the CQUAD4 element. Other elements such as the CTRIA3 are at
center only while CQUAD8 is at center plus corner. Solid elements put strain results out at the center
plus corners. User should refer to the MSC Nastran Linear Static Analysis User’s Guide.
Main Index
CHAPTER 5 613
Element Strain Output Request
8. See Remark 1 under the DISPLACEMENT (Case) Case Control command for a discussion of SORT1 and
SORT2.
9. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
10. Random response for complex strain in composites plates or shells, and layered solid composites and
layered solid shell composites will be available for each ply.
11. Element type CBEAM3 is not supported for random response.
12. ODS request must work with Case Control command, ODSFREQ, which specifies a selection of the
excitation frequencies for ODS output.
Main Index
614 MSC Nastran Quick Reference Guide
Element Stress Output Request
STRESS (Case) Element Stress Output Request
Requests the form and type of element stress output. Note: ELSTRESS is an equivalent command.
Format:
NONE
SORT1 PRINT, PUNCH PRINT, PUNCH
STRESS ( ODS = sid
SORT2 PLOT PLOT
ALL
REAL or IMAG VONMISES
PHASE MAXS or SHEAR
CENTER
CUBIC RPRINT
PSDF, ATOC, CRMS RPUNCH ) =
SGAGE or RALL NORPRINT
CORNER or BILIN
ALL
n
NONE
Examples:
STRESS=5
STRESS(CORNER)=ALL
STRESS (SORT1,PRINT,PUNCH,PHASE)=15
STRESS(PLOT)=ALL
STRESS(PRINT, PSDF, CRMS, RPUNCH)=20
STRESS(PRINT, RALL, NORPRINT)=ALL
STRESS (CORNER, PUNCH, ODS(PLOT)=ALL) = 100
Describer Meaning
SORT1 Output will be presented as a tabular listing of elements for each load,
frequency, eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each
element type.
Main Index
CHAPTER 5 615
Element Stress Output Request
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in
Bulk Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being
deprecated.
ODS Requests Operational Deflection Shape (ODS) element stress output. See
Remark 14.
sid Set identification of a previously appearing SET command. Only element
stresses in elements that appear on this SET command will be output as ODS
element stresses (Integer > 0).
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output
is in degrees.
PSDF Requests the power spectral density function be calculated and stored in the
database for random analysis postprocessing. Request must be made above the
subcase level, and RANDOM must be selected in Case Control. See Remark 11.
ATOC Requests the autocorrelation function be calculated and stored in the database
for random analysis postprocessing. Request must be made above the subcase
level, and RANDOM must be selected in Case Control. See Remark 11.
CRMS Requests the cumulative root mean square function be calculated for random
analysis postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in Case Control. See Remark 11.
RALL Requests all of PSDF, ATOC, and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM
must be selected in Case Control. See Remark 11.
VONMISES Requests von Mises stresses.
MAXS or Requests maximum shear in the plane for shell elements and octahedral stress
SHEAR for solid elements.
Main Index
616 MSC Nastran Quick Reference Guide
Element Stress Output Request
Describer Meaning
CENTER Requests CQUAD4, CQUADR and CTRIAR element stresses at the center
only. The default for CQUAD4 is CENTER. The default for CQUADR and
CTRIAR is CORNER.
CUBIC Requests CQUAD4 element stresses at the center and grid points using strain
gage approach with cubic bending correction.
SGAGE Requests CQUAD4 element stresses at center and grid points using strain gage
approach.
CORNER or Requests CQUAD4, CQUADR. and CTRIAR element stresses at center and
BILIN grid points using bilinear extrapolation.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
RPUNCH Writes random analysis results in the punch file.
ALL Stresses for all elements will be output.
n Set identification of a previously appearing SET command. Only stresses for
elements with identification numbers that appear on this SET command will be
output (Integer > 0).
NONE No element stress will be output.
Remarks:
1. ALL should not be used in a transient problem due to excessive output.
2. See Remark 1 under the DISPLACEMENT (Case) Case Control command description for a discussion of
SORT1 and SORT2.
3. ELSTRESS is an alternate form and is equivalent to STRESS.
4. STRESS=NONE overrides an overall output request.
5. Prior to MSC Nastran 2014, in nonlinear analysis, the nonlinear stresses will still be printed unless
NLSTRESS(PLOT) is specified.
6. The VONMISES option is ignored for ply stresses.
7. The VONMISES, MAXS, and SHEAR options are ignored in the complex eigenvalue and frequency
response solution sequences.
8. The options CENTER, CORNER, CUBIC, SGAGE, and BILIN are recognized only in the first
subcase, and determine the option to be used in all subsequent subcases with the STRESS, STRAIN,
and FORCE commands. (In superelement analysis, the first subcase refers to the first subcase of each
superelement. Therefore, it is recommended that these options be specified above all subcases.)
Consequently, options specified in subcases other than the first subcase will be ignored. See also
Remark 8 under the FORCE (Case) Case Control command for further discussion.
The above options apply only to the CQUAD4 element. Other elements such as the CTRIA3 are at
center only while CQUAD8 is at center plus corner. Solid elements put stress results out at the center
plus corners. User should refer to the MSC Nastran Linear Static Analysis User’s Guide.
Main Index
CHAPTER 5 617
Element Stress Output Request
9. For composite ply output, the grid point option for CQUAD4 elements will be reset to the default
option (CENTER).
10. MAXS for shell elements is not an equivalent stress.
11. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
12. Random response for complex stress in composites plates or shells, and layered solid composites and
layered solid shell composites will be available for each ply.
13. Element type CBEAM3 is not supported for random response.
14. ODS request must work with Case Control command, ODSFREQ, which specifies a selection of the
excitation frequencies for ODS output.
15. Element type CPYRAM is not supported for random response.
16. Composite stresses/failure indices are not computed in SOL101 if STRESS(SORT2) is used.
Main Index
618 MSC Nastran Quick Reference Guide
Grid Point Stress Output Request
STRFIELD (Case) Grid Point Stress Output Request
Requests the computation of grid point stresses for graphical postprocessing and mesh stress discontinuities.
Format:
STRFIELD = ALL
n
Examples:
STRFIELD=ALL
STRFIELD=21
Describer Meaning
ALL Grid point stress requests for all surfaces and volumes defined in the
OUTPUT(POST) Section will be saved for postprocessing.
n Set identification number of a previously appearing SET command. Only surfaces
and volumes with identification numbers that appear on this SET command, and
in the OUTPUT(POST) Section, will be included in the grid point stress output
request for postprocessing (Integer > 0).
Remarks:
1. The STRFIELD command is required for the graphical display of grid point stresses in postprocessors
that use the .xdb file (PARAM,POST,0), or when the GPSDCON or ELSDCON commands are
specified, and does not provide printed output. The GPSTRESS command can be used to obtain
printed output.
2. Only grid points connected to elements used to define the surface or volume are output. See the
SURFACE and VOLUME Case Control commands.
3. Element stress output (STRESS) must be requested for elements referenced on requested SURFACE
and VOLUME Case Control commands.
4. In nonlinear static and transient analysis, grid point stresses are computed only if parameter LGDISP
is -1, which is the default. Also, in nonlinear transient analysis, grid point stresses are computed only
for elements with linear material properties.
Main Index
CHAPTER 5 619
Subcase Delimiter
SUBCASE (Case) Subcase Delimiter
Delimits and identifies a subcase.
For its usage in NLPERF SOL 400, refer to SUBCASE (CASE) in the Ap. C: NLPERF SOL 400.
Format:
SUBCASE=n
Example:
SUBCASE=101
Describer Meaning
n Subcase identification number (9999999 > Integer > 0).
Remarks:
1. The subcase identification number, n, must be greater than all previous subcase identification
numbers.
2. Plot requests and RANDPS requests refer to n.
3. See the MODES Case Control command for use of this command in normal modes analysis.
4. If a comment follows n, then the first few characters of the comment will appear in the subcase label
in the upper right-hand corner of the output.
5. Note that in nonlinear statics (SOL106/129), SUBCASE's are not stand-alone solutions like in other
solution sequences. They act as a load-progression, and the ending conditions of one SUBCASE
become the initial conditions of the next SUBCASE.
Main Index
620 MSC Nastran Quick Reference Guide
Combination Subcase Delimiter
SUBCOM (Case) Combination Subcase Delimiter
Delimits and identifies a combination subcase.
Format:
SUBCOM = n
Example:
SUBCOM = 125
Describer Meaning
n Subcase identification number (Integer > 2).
Remarks:
1. The subcase identification number, n, must be greater than all previous subcase identification
numbers.
2. A SUBSEQ command must follow this command.
3. SUBCOM may only be used in SOL 101 (statics) or SOL 144 (static aeroelasticity) and in SOL 200
with ANALYSIS=STATICS or ANALYSIS=SAERO.
4. Output requests above the subcase level will be used.
5. If the referenced subcases contain thermal loads or element deformations, the user must define the
temperature field in the SUBCOM with a TEMP(LOAD) command, or the element deformations
with a DEFORM command.
6. SUBCOMs may be specified in superelement analysis with the following recommendations:
a. For each superelement, specify its SUBCASE(s) consecutively, directly followed by its
SUBCOM(s).
b. Specify a SUPER command with a new load sequence number under each SUBCOM command.
The following example demonstrates a model with one superelement and one load combination:
SUBCASE 101
SUPER=1,1
LOAD=100
SUBCASE 102
SUPER=1,2
LOAD=200
SUBCOM 110
LABEL=COMBINE SUBCASES 101 AND 102
SUPER=1,3
SUBSEQ=1.,1.
SUBCASE 1001
SUBCASE 1002
SUBCOM 1010
LABEL=COMBINE SUBCASES 1001 AND 1002
SUBSEQ=1.,1.
Main Index
CHAPTER 5 621
Combination Subcase Delimiter
7. For static aeroelasticity, only the displacement/element responses are combined. Trim, stability
derivative and monitor point results are not combined.
8. SUBCOMs are not allowed in external superelement creation runs and are ignored in external
superelement data recovery in assembly runs.
9. For SOL 200, a compliance response is not combined. SUBCASE/DRSPAN must be used for
combining compliance response.
Main Index
622 MSC Nastran Quick Reference Guide
Subcase Sequence Coefficients
SUBSEQ (Case) Subcase Sequence Coefficients
Gives the coefficients for forming a linear combination of the previous subcases.
Format:
SUBSEQ=R1 [, R2, R3, ..., Rn]
Example:
SUBSEQ=1.0, -1 .0, 0.0, 2.0
Describer Meaning
Ri Coefficients of the previously occurring subcases. See Remark 4. (Real).
Remarks:
1. The SUBSEQ command can only appear after a SUBCOM command.
2. SUBSEQ may be only used in SOL 101 (statics) or SOL 144 (static aeroelasticity) and in SOL 200
with ANALYSIS=STATICS or ANALYSIS=SAERO.
3. This command list is limited to a maximum of 200 numbers.
4. R1 to Rn refer to the immediately preceding subcases. In other words, Rn is applied to the most
recently appearing subcase, R(n - 1) is applied to the second most recently appearing subcase, and so
on. The embedded comments ($) describe the following example:
DISPL = ALL
SUBCASE 1
SUBCASE 2
SUBCOM 3
SUBSEQ = 1.0, -1.0 $ SUBCASE 1 - SUBCASE 2
SUBCASE 11
SUBCASE 12
SUBCOM 13
SUBSEQ = 0.0, 0.0, 1.0, -1 .0 $ SUBCASE 11 - SUBCASE 12
or
SUBSEQ = 1.0, - 1.0 $ EQUIVALENT TO PRECEDING COMMAND. USE ONLY
ONE.
Main Index
CHAPTER 5 623
Subcase Factors for Combination
SUBSEQ1 (Case) Subcase Factors for Combination
Gives the factors for linear combination of a specific group of SUBCASEs.
Format:
SUBSEQ1= s0, s1, sub1, s2, sub2, [sn, subn]
Example:
SUBSEQ1= 1.0, 1.0, 101, -1.0, 102
Describer Meaning
S0 Factor for all SUBCASEs involved. (No default; Real<>0.).
Sn Factor applicable to SUBn only (Real; No default).
SUBn SUBCASE ID (No default; Integer>0).
Remarks:
1. The SUBSEQ1 command can only appear after a SUBCOM command.
2. SUBSEQ1 may only be used in SOL 101 (Statics) or SOL 144 (Static Aeroelasticity) and in SOL 200
with ANALYSIS=STATIC or ANALYSIS=SAERO.
3. SUBSEQ1 and SUBSEQ are mutually exclusive and can't both appear under a SUBCOM.
4. S0, S1 and SUB1are required input for SUBSEQ1. S2,SUB2 to Sn,SUBn pair are optional.
Main Index
624 MSC Nastran Quick Reference Guide
SUBSTEP Delimiter
SUBSTEP (Case) SUBSTEP Delimiter
Delimites and identifies a nonlinear analysis SUBSTEP for COUPLED analysis in SOL 400.
Format:
SUBSTEP=n
Examples:
STEP=50
NLSTEP=10
SUBSTEP=1
ANALYSIS=HSTAT
SUBSTEP=2
ANALYSIS=NLSTAT
Describer Meaning
n Substep identification number. (Integer > 0)
Remarks:
1. The SUBSTEP command can only be used in nonlinear solution sequence SOL 400 (NONLIN).
2. The SUBSTEP command can only be used in a STEP command.
3. When used in a STEP command two or more SUBSTEP commands must occur.
4. Each SUBSTEP must contain a unique ANALYSIS=type statement. Currently there is a limitation of
only two SUBSTEPs per STEP with the following options:
• ANALYSIS=HSTAT for the first SUBSTEP and ANALYSIS=NLSTAT for the second
SUBSTEP.
• ANALYSIS=HTRAN for the first SUBSTEP and ANALYSIS=NLTRAN for the second
SUBSTEP
• ANALYSIS=HTRAN for the first SUBSTEP and ANALYSIS=NLSTAT for the second
SUBSTEP
• ANALYSIS=HSTAT for the first SUBSTEP and ANALYSIS=NLTRAN for the second
SUBSTEP
5. Within a STEP the SUBSTEP identification number n must be in increasing order and not greater
then 9999999.
6. The following example illustrates a typical application of SUBCASE, STEP, and SUBSTEPs
Subcase 100
STEP 10
STRESS= ALL
NLSTRESS=ALL
SET 1456 = list
NLSTEP=84
SubSTEP 1
Main Index
CHAPTER 5 625
SUBSTEP Delimiter
ANALYSIS=HSTAT
THERMAL=ALL
FLUX=ALL
SPC=35
LOAD=11
SubSTEP 2
ANALYSIS=NLSTAT
SPC=2
LOAD=110
DISP(PLOT)=1456
7. The solutions of all SUBCASEs are independent of each other. The solution of any STEP is a
continuation of the solution of the previous STEP. The solutions of the SUBSTEPs occur simultaneously
within a STEP.
8. In coupled analysis, TEMP(LOAD)=m will be ignored as the temperature loading from the thermal
substep is automatically transferred to the mechanical substep. Note that in this multi-physics
coupled framework, both the heat transfer and structural physics are executed on the same mesh with
the same time steps.
9. In coupled analysis, TEMP(INIT)=n will be honored. It should be noted that when a thermo-
mechanical static analysis is defined, TEMP(INIT) defines the initial temperature for both the
thermal and mechanical substeps. Note that when a transient thermal-static mechanical analysis is
define, IC=n should be used to define the initial temperature for the thermal substep and
TEMP(INIT)=n (the same ID n) should be used to define the initial temperature for the structural
substep. Then an initial thermal strain is defined as:
T = A T T – TREF – A T o T o – TREF
where T o comes from TEMP(INIT) and TREF comes from the material entry.
10. The LOADSET Case Control Command is not allowed with this command. All dynamic loading
must be applied through the use of the DLOAD Case Control command.
11. For coupled analysis, i.e., when two or more sub-steps are defined, a single Bulk Data entry NLSTEP
must be included in the STEP command containing the SUBSTEP commands. It must occur above
or in the STEP command and above the first SUBSTEP command.
The loads and constraints can be independently defined for each physics under the relevant
SUBSTEP. The commands that are normally used for single physics are applicable. For, e.g., for a
HTRAN-NLSTAT coupled analysis, DLOAD should be used n the HTRAN substep while LOAD
should be used in the NLSTAT substep.
12. Any case control command will apply to all SUBSTEPs when and only when it is above all the
SUBSTEPs of the STEP.
Main Index
626 MSC Nastran Quick Reference Guide
Output Subtitle
SUBTITLE (Case) Output Subtitle
Defines a subtitle that will appear on the second heading line of each page of printer output.
Format:
SUBTITLE=subtitle
Example:
SUBTITLE=PROBLEM NO. 5-1A
Describer Meaning
subtitle Any character string.
Remarks:
1. SUBTITLE appearing under a SUBCASE command will appear in the output for that subcase only.
2. SUBTITLE appearing before all SUBCASE commands will appear in the output for all subcases
except those in Remark 1.
3. If no SUBTITLE command is present, the subtitle line will be blank.
4. The subtitle also appears on plotter output.
Main Index
CHAPTER 5 627
Superelement Subcase Assignment
SUPER (Case) Superelement Subcase Assignment
Assigns a subcase(s) to a superelement or set of superelements.
Format:
ALL
SUPER = n
l
i
Examples:
SUPER=17, 3
SUPER=15
SUPER=ALL
Describer Meaning
i Superelement identification number (Integer ≥ 0).
ALL The subcase is assigned to all superelements and all loading conditions (Default).
n Set identification number of a previously appearing SET command. The subcase is assigned
to all superelements with identification numbers that appear on this SET command
(Integer > 0).
l Load sequence number (Integer > 0; Default=1).
Remarks:
1. All subcases with requests for specific superelement(s) must contain the SUPER command. If no
SUPER command is specified in the Case Control Section, then all subcases will be assigned to all
superelements; i.e., SUPER=ALL is the default.
2. All subcases associated with superelements must precede those for the residual structure except when
SUPER=ALL or SUPER=n and the selected set includes the residual structure.
3. The load sequence number is only used in static analysis and frequency response analysis when there
are multiple loading conditions. Also, the residual structure must have a subcase specified for each
unique load condition. This is required because the number of residual structure subcases is used to
determine the number of load conditions for all superelements.
4. The load sequence number is associated with the order of the subcases for the residual structure; i.e.,
the third loading condition is associated with the third subcase for the residual structure.
5. Subcases are required for superelements when there is a load, constraint, or output request.
6. If a set is referenced by n, then the SET identification number must be unique with respect to any
superelement identification numbers. In addition, the same sets must be used for all loading
conditions.
Main Index
628 MSC Nastran Quick Reference Guide
Superelement Subcase Assignment
7. If the ALL option is used, it must be used for all loading conditions.
8. If there are no superelements in the model then the SUPER command will be ignored except in 3-
step external superelement data recovery restarts in SOL 400. See Remarks 9 and 10 under the
EXTDRIN Case Control command description.
Main Index
CHAPTER 5 629
Fictitious Support Set Selection
SUPORT1 (Case) Fictitious Support Set Selection
Selects the fictitious support set (SUPORT1 only) to be applied to the model.
Format:
SUPORT1=n
Examples:
SUPORT1=15
SUPO=4
Describer Meaning
n Set identification of fictitious support set defined on the SUPORT1 Bulk Data
entry. See Remark 1. (Integer > 0).
Remarks:
1. SUPORT1 Bulk Data entry will not be used unless selected in the Case Control Section by the
SUPORT1 command.
2. SUPORT entries will be applied in all subcases without using a Case Control Command to select
them.
Main Index
630 MSC Nastran Quick Reference Guide
Solution Set Eigenvector Output Request
SVECTOR (Case) Solution Set Eigenvector Output Request
Requests the form and type of solution set eigenvector output.
Format:
ALL
PRINT,PUNCH
SVECTOR( ) = n
PLOT
NONE
Examples:
SVECTOR=ALL
SVECTOR(PUNCH)=NONE
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Displacements for all points (modes) will be output.
NONE Displacements for no points (modes) will be output.
n Set identification of a previously appearing SET command. Only displacements
of points with identification numbers that appear on this SET command will be
output (Integer > 0).
Remarks:
1. SVECTOR=NONE overrides an overall output request.
2. Output will be presented as a tabular listing of grid points for each eigenvector.
Main Index
CHAPTER 5 631
Solution Set Velocity Output Request
SVELOCITY (Case) Solution Set Velocity Output Request
Requests the form and type of solution set velocity output.
Format:
ALL
SORT1 REAL or IMAG
SVELOCITY ( PRINT, PUNCH ) = n
SORT2 PHASE
NONE
Examples:
SVELOCITY=5
SVELOCITY(SORT2,PUNCH,PRINT,PHASE)=ALL
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load,
frequency, eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid
point (or mode number).
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output
is in degrees.
ALL Velocity for all solution points (modes) will be output.
NONE Velocity for no solution points (modes) will be output.
n Set identification of a previously appearing SET command. Only velocities of
points with identification numbers that appear on this SET command will be
output (Integer > 0).
Remarks:
1. Velocity output is only available for transient and frequency response problems.
2. The defaults for SORT1 and SORT2 depend on the type of analysis, and is discussed in Remark 1
under the DISPLACEMENT (Case) Case Control command. If SORT1 is selected for any of the
commands SACC, SDIS, and SVEL, then the remaining commands will also be SORT1.
3. SVELOCITY=NONE overrides an overall output request.
Main Index
632 MSC Nastran Quick Reference Guide
Solution Set Velocity Output Request
4. In modal frequency and transient analyses with both structural and fluid modes, the solution set
output request results in separate outputs for structural and fluid modal solutions. The first set is for
the structural modal solution and the second set is for the fluid.
Main Index
CHAPTER 5 633
Symmetry Subcase Delimiter
SYM (Case) Symmetry Subcase Delimiter
Delimits and identifies a symmetry subcase.
Format:
SYM=n
Example:
SYM=123
Describer Meaning
n Subcase identification number (Integer > 0).
Remarks:
1. The subcase identification number n must be greater than all previous subcase identification
numbers.
2. Plot commands should refer to n.
3. Overall output commands will not propagate into a SYM subcase (i.e., any output desired must be
requested within the subcase).
4. SYM may only be used in statics or inertia relief problems.
Main Index
634 MSC Nastran Quick Reference Guide
Symmetry Combination Subcase Delimiter
SYMCOM (Case) Symmetry Combination Subcase Delimiter
Delimits and identifies a symmetry combination subcase.
Format:
SYMCOM=n
Example:
SYMCOM=123
Describer Meaning
n Subcase identification number (Integer > 2).
Remarks:
1. The subcase identification number n must be greater than all previous subcase identification
numbers.
2. SYMCOM may only be used in statics problems.
3. If the referenced subcases contain thermal loads or element deformations, the user must define the
temperature field in the SYMCOM by use of a TEMP(LOAD) command, or the element
deformations by a DEFORM command.
4. An alternate command is the SUBCOM command.
5. SYMCOMs may be specified in superelement analysis with the following recommendations:
a. For each superelement, specify its SUBCASEs consecutively, directly followed by its
SYMCOM(s).
b. Specify a SUPER command with a new load sequence number under each SYMCOM command.
The following example represents a model with one superelement and one load combination:
SUBCASE 101
SUPER=1,1
LOAD=100
SUBCASE 102
SUPER=1,2
LOAD=200
SYMCOM 110
LABEL=COMBINE SUBCASES 101 AND 102
SUPER=1,3
SYMSEQ=1.,1.
SUBCASE 1001
SUBCASE 1002
SYMCOM 1010
LABEL=COMBINE SUBCASES 1001 AND 1002
SYMSEQ=1.,1.
Main Index
CHAPTER 5 635
Symmetry Sequence Coefficients
SYMSEQ (Case) Symmetry Sequence Coefficients
Specifies the coefficients for combining symmetry subcases into the total structure.
Format:
SYMSEQ=R1 [,R2,R3,..., Rn]
Example:
SYMSEQ=1.0, -2.0, 3.0, 4.0
Describer Meaning
Ri Coefficients of the previously occurring n SYM subcases. (Real)
Remarks:
1. SYMSEQ may only appear after a SYMCOM command.
2. The default value for the coefficients is 1.0 if no SYMSEQ command appears.
3. SYMSEQ may only be used in static analysis or inertia relief.
4. Ri is limited to a maximum of 200 numbers.
Main Index
636 MSC Nastran Quick Reference Guide
Acceleration Output Request for trim components, TRMC
TACCELERATION (Case) Acceleration Output Request for trim components, TRMC
Requests the form and type of acceleration output for TRMC.
Format:
ALL
SORT1 PRINT,PUNCH REAL or IMAG
TACCELERATION ( = n
SORT2 PLOT PHASE
NONE
Example:
SET 20 = 3/103, 5/0, 12/ALL $
TACCELERATION=ALL
TACC(REAL, PUNCH, PRINT)=20
TACCE=20
TACCELE(SORT2, PRINT)=20
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load and
frequency.
SORT2 Output will be presented as a tabular listing of frequency for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
ALL TRMC acceleration for all points of all TRMCs will be output. See Remarks 2.
Main Index
CHAPTER 5 637
Acceleration Output Request for trim components, TRMC
Describer Meaning
NONE No TRMC acceleration will be output.
n Set identification of a previously appearing SET command. Only points with
identification numbers that appear on this SET command will be output (Integer >
0). SET 20 in above examples section is to request SET 103(not present) for TRMC
3, none for TRMC 5 and ALL for TRMC 12.
Remarks:
1. Refrain from using ALL which may produce voluminous output.
2. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
3. TACC=NONE suppresses the generation of TRMC acceleration output.
4. TACCELERATION is supported only with PARAM,TRMBIM,PHYSICAL
5. TACCELERATION is available for PEM jobs of SOL 111 and SOL 200 with
ANALYSIS=MFREQ. Note that TACCELERATION is available for output only and cannot be
utilized as design response.
6. For restart PEM job, TACCE request must remain the same as cold start PEM job.
Main Index
638 MSC Nastran Quick Reference Guide
Displacement Output Request for trim components, TRMC
TDISPLACEMENT (Case) Displacement Output Request for trim components, TRMC
Requests the form and type of displacement output for TRMC.
Format:
ALL
SORT1 PRINT,PUNCH REAL or IMAG
TDISPLACEMENT ( = n
SORT2 PLOT PHASE
NONE
Example:
SET 20 = 3/103, 5/0, 12/ALL $
TDISPLACEMENT=ALL
TDIS(REAL, PUNCH, PRINT)=20
TDISP=20
TDISPLACE(SORT2, PRINT)=20
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load and
frequency.
SORT2 Output will be presented as a tabular listing of frequency for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
ALL TRMC displacement for all points of all TRMCs will be output. See Remarks 2.
Main Index
CHAPTER 5 639
Displacement Output Request for trim components, TRMC
Describer Meaning
NONE No TRMC displacement will be output.
n Set identification of a previously appearing SET command. Only points with
identification numbers that appear on this SET command will be output (Integer >
0). SET 20 in above examples section is to request SET 103(not present) for TRMC
3, none for TRMC 5 and ALL for TRMC 12.
Remarks:
1. Refrain from using ALL which may produce voluminous output.
2. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
3. TDISP=NONE suppresses the generation of TRMC displacement output.
4. TDISPLACEMENT is supported only with PARAM,TRMBIM,PHYSICAL
5. TDISPLACEMENT is available for PEM jobs of SOL 111 and SOL 200 with ANALYSIS=MFREQ.
Note that TDISPLACEMENT is available for output only and cannot be utilized as design response.
6. For each grid in a TRMC, it has 3 or 6 DOFs for solid phase and 1 DOF for fluid phase.
TDISPLAMENT output results for both solid phase DOFs and fluid phase DOF.
7. The 3 DOFs of solid phase takes T1, T2 and T3 locations of a regular 6 DOFs structural grid and
set R1, R2 and R3 locations to 0.0. The 1 DOF of fluid phase is reported as acoustic pressure.
8. For restart PEM job, TDISP request must remain the same as cold start PEM job.
Main Index
640 MSC Nastran Quick Reference Guide
Temperature Set Selection
TEMPERATURE (Case) Temperature Set Selection
Selects the temperature set to be used in either material property calculations or thermal loading in heat
transfer and structural analysis.
Format:
INITIAL
TEMPERATURE MATERIAL HSUBCASE = i HSTEP = j HTIME = t
LOAD
ALL
BOTH
GRID
,VERIFY= ELEMENT = n
BOTH
NONE
Examples:
TEMPERATURE(LOAD)=15
TEMPERATURE(MATERIAL)=7
TEMPERATURE=7
TEMPERATURE(LOAD,HSUBCASE=20,HTIME=12.0)=39
Describer Meaning
MATERIAL The selected temperature set will be used to determine temperature-dependent material
properties indicated on MATTi Bulk Data entries. See Remarks 6., 7., and 8.
LOAD The selected temperature set will be used to determine an equivalent static load and to
update material properties in a nonlinear analysis. See Remarks 2., 5., 6., 7. and 13.
BOTH Both MATERIAL and LOAD will use the same temperature set.
n Set identification number of TEMP, TEMPD, TEMPP1,TEMPB3, TEMPRB, or
TEMPAX Bulk Data entries (Integer > 0).
INITIAL The selected temperature table will be used to determine initial temperature distribution
in nonlinear static analysis. See Remarks 4., 6., 7., 8., 9., and 12.
HSUBCASE Specifies a SUBCASE executed in the selected thermal job. See Remark 13.
i Identification number of a SUBCASE executed in the selected thermal job. (Integer > 0,
Default = 0 is the first SUBCASE) See Remark 13.
HSTEP Specifies a STEP executed in the selected thermal job. See Remark 13.
j Identification number of a STEP executed in the selected thermal job. (Integer > 0,
Default = 0 is the first STEP) See Remark 13.
Main Index
CHAPTER 5 641
Temperature Set Selection
Describer Meaning
HTIME Specifies the time of a time step executed in the selected nonlinear transient thermal job.
See Remark 13.
t Time of a time step executed in the selected nonlinear transient thermal job. (Real > 0.0,
Default is the last time of the specified SUBCASE and/or STEP) See Remark 13.
ALL Selects all time steps executed in the selected nonlinear transient thermal job. See
Remark 13.
VERIFY Output temperature verification data output requested
GRID Output grid temperature verification data
ELEMENT Output element temperature verification data
BOTH Output both grid and element temperature verification data
NONE Do not output any verification data
Remarks:
1. In linear analysis, only one TEMP(MATE) may be made in any problem and should be specified
above the subcase level. If there are multiple subcase and TEMP(MATE) is not above the first
subcase, then it must appear in the last subcase or it will be ignored. See also Remarks 6. and 7.
2. The total load applied will be the sum of external (LOAD command), thermal (TEMP(LOAD)
command), element deformation (DEFORM command), and constrained displacement (SPC
command) loads.
3. Static, thermal, and element deformation loads should have unique set identification numbers.
4. INITIAL is used in steady state heat transfer analysis for conduction material properties, and provides
starting values for iteration. In structural analysis, TEMP(INIT) is used to specify an initial
temperature. It may appear above or in the first subcase. In SOL 400, it may appear above or in the
first STEP.
5. In superelement data recovery restarts, TEMPERATURE(LOAD) requests must be respecified in the
Case Control Section.
6. In linear static analysis, temperature strains are calculated by
T = A(T0) (T - T0)
where A(T0) is the thermal expansion coefficient defined on the MATi Bulk Data entries, T is the
load temperature defined with TEMPERATURE(LOAD), and T0 is the initial temperature defined
as follows. The following rules apply for TEMPERATURE(INITIAL),
TEMPERATURE(MATERIAL), and TREF on the MATi entries:
a. If TEMPERATURE(INITIAL) and TREF are specified, then the TEMPERATURE(INITIAL)
set will be used as the initial temperature to calculate both the loads and the material properties.
b. If TEMPERATURE(MATERIAL) and TREF are specified, then TREF will be used as the initial
temperature in calculating the load and the TEMPERATURE(MATERIAL) set will be used for
the calculation of material properties.
Main Index
642 MSC Nastran Quick Reference Guide
Temperature Set Selection
c. If neither TEMPERATURE(INITIAL), TEMPERATURE(MATERIAL), nor
TEMPERATURE(BOTH) is present, TREF will be used to calculate both the load and the
material properties and will be obtained from the MATi entry. The MATTi is not used in this
case.
7. In nonlinear static analysis, temperature strains are calculated with
T = A(T) (T - TREF) - A(T0) (T0 - TREF)
where A(T) is the thermal expansion coefficient defined on the MATi Bulk Data entries, T is the load
temperature defined with TEMPERATURE(LOAD), and T0 is the initial temperature defined with
TEMPERATURE(INITIAL). The following rules apply:
a. The specification of TEMPERATURE(MATERIAL) or TEMPERATURE(BOTH) will cause a
fatal error.
b. If a subcase does not contain a TEMPERATURE(LOAD) request, then the thermal load set will
default to the TEMPERATURE(INITIAL) set.
c. TEMPERATURE(LOAD) will also cause the update of temperature-dependent material
properties due to the temperatures selected in the thermal load set. Temperature-dependent
material properties are specified with MATi, MATTi, MATS1, and/or TABLEST Bulk Data
entries.
d. If TREF and TEMPERATURE(INITIAL) are specified, then the TEMPERATURE(INITIAL)
set will be used as the initial temperature to calculate both the loads and the material properties.
Both are used in the definition of thermal strain.
e. For composite elements, with associated MATTi entries, PARAM, COMPMATT, YES is
recommended to ensure that the temperature-dependent properties are updated and smeared at
the current temperature for each load step. Furthermore, for composite elements, if the
coefficients of thermal expansion, on the resulting smeared MAT2 entries, corresponding to the
MID4 field on the resulting PSHELL entry are to be used for nonlinear thermal strain
computations, PARAM, COMPMATT, YES must be present if out of plane thermal bending is
deemed important.
8. TEMPERATURE(MATERIAL) and TEMPERATURE(INITIAL) cannot be specified
simultaneously in the same run.
9. TEMP(INIT) is not used with TEMPAX.
10. Temperature loads cause incorrect element forces and stresses in all the dynamic analysis except SOL
400 nonlinear transient analysis with the elements having nonlinear capability.
It should be noted that:
a. For nonlinear dynamics analysis with SOL 400, TEMPERATURE/THERMAL load can't be
applied by TEMP/DLOAD (Case Control) and TEMPD/TLOADi (Bulk Data), this load should
be applied by TEMP(Case Control) and TTEMP(Bulk Data);
b. For pure linear analysis with SOL 400, the TEMP/DLOAD (Case Control) and
TEMPD/TLOADi (Bulk Data) has to be used to apply the temperature load.
Main Index
CHAPTER 5 643
Temperature Set Selection
11. In linear analysis, TEMPERATURE(MATERIAL) is not supported for hyperelastic elements
(MATHP). TEMP(INIT) must be placed above the subcase level, and TEMP(LOAD) placed within
the subcase.
12. For layered composites, neither the TREF specified on the material entries, nor TEMP(INIT) nor
TEMP(MATE) are used to determine ply reference temperature. The TREF on the PCOMP or
PCOMPG entries is used for all plies of the element. This is true for both linear and nonlinear
analysis. If TEMP(INIT) is defined, the TREF on the PCOMP or PCOMPG entries is only used for
determining the material properties and TEMP(INIT) is used for thermal strains. If TEMP(INIT) is
not defined, the TREF on the PCOMP or PCOMPG entries is used for determining the material
properties and thermal strains.
13. For TEMPERATURE(LOAD) requests in SOL 400, HSUBCASE, HSTEP, and HTIME are used
to retrieve the temperature results from an existing thermal database. This feature allows user to select
either steady state or transient thermal results for nonlinear structural analysis, with the flexibility of
different time steps and dissimilar mesh sizes between thermal and structural runs. The following
rules apply for using this capability:
• HSUBCASE, HSTEP, and HTIME keywords must follow a LOAD keyword.
• Although all three keywords have default values, at lease one keyword must exist to apply this
uncoupled multi-physics feature in analysis.
• HTIME=ALL is used in nonlinear transient structural analysis to perform real time temperature
interpolations. In this case, the nodal temperatures of nonlinear elements are updated at each time
step. These temperatures are equal to the temperature results of the selected thermal database at
current time.
• The set IDs of TEMP(LOAD) must be different from the set IDs of TEMP(INIT).
• To save temperature results of thermal analysis in MASTER nastran database, use the following
command.
nastran thermal_job_name scratch=no
In addition, the user must specify the following Bulk Data entry:
PARAM,NLPACK,-1
for transient thermal models with number of time steps greater than the default NLPACK output
time steps.
• The following File Management Statements are required in the current structural model to select
the thermal database.
ASSIGN hrun='thermal_job_name.MASTER'
DBLOC DATABLK=(HEATDB) LOGI=hrun
• Contact body integrity is not maintained while doing the thermal mapping. While this would
not be a restriction for bodies that are not physically in contact or in glued thermal contact, it
could lead to undesirable temperature mapping for bodies that are in regular thermal contact
with temperature gradients across the contact interface.
Main Index
644 MSC Nastran Quick Reference Guide
Transfer Function Set Selection
TFL (Case) Transfer Function Set Selection
Selects the transfer function set(s) to be added to the direct input matrices.
Format:
TFL=n
Example:
TFL=77
TFL = 1, 25, 77
Describer Meaning
n Set identification of a TF Bulk Data entry (Integer > 0).
Remarks:
1. Transfer functions will not be used unless selected in the Case Control Section.
2. Transfer functions are supported in dynamics problems only.
3. Transfer functions are described in the MSC Nastran Dynamic Analysis User’s Guide.
4. It is recommended that PARAM,AUTOSPC,NO be specified when using transfer functions. See
Constraint and Mechanism Problem Identification in SubDMAP SEKR in the MSC Nastran Reference Guide.
5. The transfer functions are additive if multiple TF values are referenced on the TFL command.
Main Index
CHAPTER 5 645
Temperature Output Request
THERMAL (Case) Temperature Output Request
Requests the form and type of temperature output.
Format:
ALL
SORT1 PRINT, PUNCH
THERMAL ( ) = n
SORT2 PLOT
NONE
Examples:
THERMAL=5
THER(PRINT,PUNCH)=ALL
Describer Meaning
SORT1 Output is presented as a tabular listing of point temperatures for each load or time
step.
SORT2 Output is presented as a tabular listing of loads or time steps for each.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Temperatures for all points will be output.
NONE Temperatures for no points will be output.
n Set identification of a previously appearing SET command. Only temperatures of
points with identification numbers that appear on this SET command will be output
(Integer > 0).
Remarks:
1. The THERMAL output request is designed for use with the heat transfer option. The printed output
will have temperature headings. The PUNCH option produces TEMP Bulk Data entries, and the
SID on the entries will be the subcase number (=1 if no SUBCASES are specified).
Main Index
646 MSC Nastran Quick Reference Guide
Temperature Output Request
2. SORT1 is the default in steady state heat transfer analysis. SORT2 is the default in transient heat
transfer analysis.
3. In a transient heat transfer analysis, the SID on the punched TEMP Bulk Data entries equal the time
step number.
Main Index
CHAPTER 5 647
Output Title
TITLE (Case) Output Title
Defines a character string to appear on the first heading line of each page of MSC Nastran printer output.
Format:
TITLE=title
Example:
TITLE=RIGHT WING, LOAD CASE 3.
Describer Meaning
title Any character string.
Remarks:
1. If this command appears under a SUBCASE command, then the title appears in the output for that
subcase only.
2. If this command appears before all SUBCASE commands, then the title is used in all subcases without
a TITLE command.
3. If no TITLE command is present, then the title line will contain data and page numbers only.
4. The title also appears on plotter output.
Main Index
648 MSC Nastran Quick Reference Guide
Tire Set Selection
TIRE (Case) Tire Set Selection
The TIRE case control entry defines the tires to be included in the analysis by selecting the TIRE bulk data
entry. This case control command can be used in solutions sequences SOLs 103, 107-112, 200 and 400.
Format:
TIRE = n
Example:
TIRE = 100
Describer Meaning
n Set ID of a TIRE bulk data entry (Integer > 0).
Remarks:
1. The TIRE case control command must occur above subcase level.
2. Using a particular combination of tires in the analysis only requires selection of the tires by referencing
the TIRE bulk data entry.
Main Index
CHAPTER 5 649
Transfer Path Analysis (TPA) Request
TPASET (Case) Transfer Path Analysis (TPA) Request
Requests a Transfer Path Analysis.
Format:
TPASET = n
Example:
TPASET = 100
Describer Meaning
n Set identification number of a TRIM Bulk Data entry (Integer > 0).
Remark:
1. TPASET is required for running Single-step TPA.
Main Index
650 MSC Nastran Quick Reference Guide
Aerodynamic Trim Variable Constraint Selection
TRIM (Case) Aerodynamic Trim Variable Constraint Selection
Selects trim variable constraints in static aeroelastic response.
Format:
TRIM = n
Example:
TRIM=1
Describer Meaning
n Set identification number of a TRIM Bulk Data entry (Integer > 0).
Remark:
1. Aerodynamic extra points (trim variables) not constrained by a TRIM Bulk Data entry will be free
during the static aeroelastic response solution.
Main Index
CHAPTER 5 651
Trim Load Output Specification
TRIMF (Case) Trim Load Output Specification
Specifies options for the output of trim loads from a static aeroelastic analysis as FORCE/MOMENT Bulk
Data entries.
Format:
TRIMF UNIT = i LOADSET = n LARGE INERTIA APPLIED AIR
ALL
NOSUM RIGID , NOELASTIC QNORM =
n
Example:
TRIMF(LOADSET=10001,LARGE)=ALL
TRIMF(UNIT=59,INERTIA,NOSUM)=1
Describer Meaning
UNIT Fortran unit to which data are written. (Optional; Default = 7) (punch file).
LOADSET Load set id for output bulk data entries. If the TRIMF specification results in multiple
load sets, then the defined ID will be used for the first and each subsequent load set has
an ID incremented by 1. (Optional; Default = 1)
LARGE Write the output data in large field format (16 characters per field). The default is 8
characters per field.
INERTIA Write out inertial loads as a separate load set. By default, the separate load set will not
be written.
APPLIED Write out applied loads as a separate load set. By default, the separate load set will not
be written.
AIR Write out aerodynamic loads as a separate load set. By default, the separate load set will
not be written.
NOSUM By default, the sum of the inertial, applied, and aerodynamic loads will be written as a
separate load set. This option suppresses the writing of that set of loads.
RIGID Write out rigid instances of the selected loads (Inertial, Applied, Air and/or Sum) as
separate load sets. By default, the separate load set will not be written.
NOELASTIC By default, the sum of the rigid and elastic increment loads will be written as a separate
load set. This option suppresses the writing of that set of loads.
QNORM Normalize the load by the dynamic pressure used in the trim analysis. By default, the
loads are not normalized.
ALL Loads for all points will be output
n Set identification of a previously appearing SET command. Only loads on points with
identification numbers that appear on this SET command will be output (Integer > 0)
Main Index
652 MSC Nastran Quick Reference Guide
Trim Load Output Specification
Remark:
1. By default, the loads are written to the punch file (Fortran unit 7). If the user specifies an alternate
Fortran unit number on the TRIMF entry, by default the loads will be written to a file name that is
machine specific (i.e. ‘fort.53’ on many LINUX platforms). The user may connect the Fortran unit
to a user-defined file name by using an ASSIGN entry in the FMS Section of the input file. For
example:
ASSIGN USERFILE='load13.inc',STATUS=UNKNOWN,FORMATTED,UNIT=53
2. Up to seven loads sets are available: Rigid Inertial, Rigid Applied, Rigid Air, Rigid Sum and four more
with the sum of the rigid and elastic increment, excepting Inertial. This table indicates how the
describers invoke each of these sets:
INERTIAL APPLIED AIR SUM
RIGID O O O O
ELASTIC N/A O O DEFAULT
where O = Optional. For a load to appear, both the row and column in the table above have to be set.
3. Care must be taken if LOADSET is specified in a run with multiple subcases. There are no checks
that the load set IDs which are generated by one subcase are not also used for another subcase. For
example, consider the following Case Control commands:
SUBCASE 1
TRIM = 1
TRIMF(RIGID) = ALL $
SUBCASE 2
TRIM = 2
TRIMF(LOADSET=2) = ALL
Subcase 1 will generate two load sets with set IDs 1 and 2. Subcase 2 will also output a load set ID 2.
4. The LOADSET option should not be specified above the subcase level when there are multiple
subcases. If it is, each subcase will start numbering its load ID’s from LOADSET.
5. If an HDF5OUT entry is included in the input bulk data file, the TRIMF data are output to the h5
file with the TRMC value in the domain mapping to the loads:
TRMC Load
10 Inertial
20 Rigid Applied
30 Elastic Applied
40 Rigid Air
50 Elastic Air
60 Rigid Sum
70 Elastic Sum
Main Index
CHAPTER 5 653
Selection of Trim Component(s)
TRIMGRP (Case) Selection of Trim Component(s)
Selects a set of trim components for analysis.
Format:
ALLTRMC sid
TRIMGRP = ALL
SLTTRMC
NONE
Example:
TRIMGRP=101
Describer Meaning
ALLTRMC Process all TRMCs defined under 'BEGIN BULK TRMC=trimid' regardless if it is
been selected in sid. This is the default option.
SLTTRMC Process only those TRMCs whose ID is selected in sid. It can be equal to or less than
what are been defined under 'BEGIN BULK TRMC=trimid'.
sid Set identification of a previously appearing SET command or TRIMID. (Integer>0).
ALL All trim components present in the model are included in the analysis.
NONE This is the default of TRIMGRP. No trim component is involved in the analysis.
Remark:
1. TRIMGRP is used to select a group of trim components for analysis, including the calculation of trim
component boundary coupling matrices.:
2. PEM capability is available in SOL 108, SOL 111 and SOL 200 with analysis=mfreq.
3. SUBCASEs without TRIMGRP will have the equivalent effect of TRIMGRP=none even with the
presence of 'BEGIN TRMC' in the deck.
4. To run PEM job with multiple processors, additional information is available in 'Running PEM jobs'
section of Using PEM Functions in MSC Nastran in the MSC Nastran Installation and Operations Guide.
5. For restart PEM job, TRIMGRP must remain the same as cold start PEM job and no changes to any
TRMC should be observed. Otherwise, the PEM job should be run as cold start.
6. Collapsed logic is introduced to improve performance of large PEM jobs satisfy following
requirements:
a. Same TRIMGRP for all SUBCASEs and
b. same master frequencies for all TRMCs. The activation of collapsed logic is automatic if
requirements are met. With collapsed logic activated, restart job is restricted to the same
TRIMGRP as cold start.
Main Index
654 MSC Nastran Quick Reference Guide
Selection of Trim Component(s)
7. Following TRIMGRP case control commands have same effect which is to process all defined
TRMCs:
a. TRIMGRP = ALL
b. TRIMGRP(alltrmc)=ALL
c. TRIMGRP(slttrmc)=ALL
8. If TRIMGRP is used in multiple SUBCASEs, SLTTRMC/ALLTRMC on TRIMGRP of above
subcase level or first subcase will be utilized. SLTTRMC/ALLTRMC on TRIMGRP of second
subcase and onwards will be ignored. Note that SLTTRMC on TRIMGRP of first subcase may be
ignored if the union of all TRIMGRP means ALL TRMCs.
Main Index
CHAPTER 5 655
Transient Time Step Set Selection
TSTEP (Case) Transient Time Step Set Selection
Selects integration and output time steps for linear or nonlinear transient analysis.
Format:
TSTEP=n
Example:
TSTEP=731
Describer Meaning
n Set identification number of a TSTEP or Bulk Data entry (Integer > 0).
Remarks:
1. A TSTEP entry must be selected to execute a linear transient analysis (SOLs 109 or 112) and for a
nonlinear transient analysis (SOLs 129 and 159).
2. A entry must be selected in each subcase to execute a nonlinear transient problem.
3. For the application of time-dependent loads in modal frequency response analysis (SOLs 111 and
146), the TSTEP entry must be selected by the TSTEP command. The time-dependent loads will be
recomputed in frequency domain by a Fourier transform.
4. In one subcase or STEP for SOL 400, users should only specify one of TSTEP, TSTEPNL or
NLSTEP.
5. If NLSTEP specified, TSTEP command will be ignored.
Main Index
656 MSC Nastran Quick Reference Guide
Transient Time Step Set Selection for Nonlinear Analysis
TSTEPNL (Case) Transient Time Step Set Selection for Nonlinear Analysis
See the description of the TSTEP (Case). (The TSTEP Case Control entry can be used to select a TSTEPNL
Bulk Data entry, however, a Bulk Data TSTEP is completely different from a Bulk Data Entry TSTEPNL.)
Main Index
CHAPTER 5 657
Temperature Set ID for a Structures Run
TSTRU (Case) Temperature Set ID for a Structures Run
Defines a temperature set ID for a structures run based on a heat transfer subcase.
Format:
TSTRU=n
Example:
TSTRU=999
Describer Meaning
n Set identification for use on TEMP(LOAD)=n or TEMP(INIT)=n
Remarks:
1. TSTRU should be placed in a heat transfer subcase.
2. If TSTRU does not explicitly appear in the heat transfer subcase, it is defaulted to TSTRU=heat
transfer subcase ID.
3. In a structures run, a temperature set generated from a heat transfer run will override an existing
temperature set with identical set ID defined with TEMP, TEMPD, TEMPP1, TEMPRB, or any
combination.
4. TSTRU may be placed in the first subcase of a PARAM,HEATSTAT,YES run.
5. TSTRUs may be placed in each subcase of an APPHEAT run. The associated structural analysis then
requires the following:
ASSIGN heat_run=’heat transfer job name.MASTER’
DBLOC DATABLK=(UG,EST,BGPDTS,CASECCR/CASEHEAT) LOGICAL=heat_run
6. Heat transfer runs and structural runs must have the same mesh.
7. For nonlinear heat transfer SOL 106 or SOL 153, the INOUT field on the NLPARM Bulk Data
entry must be blank or NO if the results of the run are to be transferred to a linear structures run.
PARAM,NLHTLS,-1
The above parameter should be placed in the nonlinear heat run. This will place UG heat transfer on
the database.
Main Index
658 MSC Nastran Quick Reference Guide
Velocity Output Request for trim components, TRMC
TVELOCITY (Case) Velocity Output Request for trim components, TRMC
Requests the form and type of velocity output for TRMC.
Format:
ALL
SORT1 PRINT PUNCH REAL or IMAG
TVELOCITY ( = n
SORT2 PLOT PHASE
NONE
Example:
SET 20 = 3/103, 5/0, 12/ALL $
TVELOCITY=ALL
TVEL(REAL, PUNCH, PRINT)=20
TVELO=20
TVELOCI(SORT2, PRINT)=20
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load and
frequency.
SORT2 Output will be presented as a tabular listing of frequency for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
ALL TRMC velocity for all points of all TRMCs will be output. See Remarks 2.
Main Index
CHAPTER 5 659
Velocity Output Request for trim components, TRMC
Describer Meaning
NONE No TRMC velocity will be output.
n Set identification of a previously appearing SET command. Only points with
identification numbers that appear on this SET command will be output (Integer >
0). SET 20 in above examples section is to request SET 103(not present) for TRMC
3, none for TRMC 5 and ALL for TRMC 12.
Remarks:
1. Refrain from using ALL which may produce voluminous output.
2. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
3. TVELO=NONE suppresses the generation of TRMC velocity output.
4. TVELOCITY is supported only with PARAM,TRMBIM,PHYSICAL
5. TVELOCITY is available for PEM jobs of SOL 111 and SOL 200 with ANALYSIS=MFREQ. Note
that TVELOCITY is available for output only and can not be utilized as design response.
6. For restart PEM job, TVELO request must remain the same as cold start PEM job.
Main Index
660 MSC Nastran Quick Reference Guide
Contact Body Unglue Selection
UNGLUE (Case) Contact Body Unglue Selection
Selects the grids should use standard contact instead of glued contact in glued bodies in SOL 400.
Format:
UNGLUE=n
Example:
UNGLUE=10
Describer Meaning
n Set identification number of the UNGLUE Bulk Data entry (Integer > 0).
Remarks:
1. This command is used only in SOL 400 for 3D Contact analysis.
2. The default SID of UNGLUE Bulk Data entry is defined on BCONTACT Case Control command
if applicable; however, the SID on UNGLUE Case Control command can overwrite it.
Main Index
CHAPTER 5 661
Virtual Crack Closure Technique for SOL 400 Analysis
VCCT (Case) Virtual Crack Closure Technique for SOL 400 Analysis
Selects grid sets to be used for virtual crack closure analysis in SOL 400.
Format:
VCCT=N
Example:
VCCT=0
VCCT=1
Describer Meaning
N ID of a matching Bulk Data VCCT entry specifying the crack.
Remarks:
1. This entry can only be used in SOL 400.
2. Different sets of cracks can be selected for different subcases using this option.
Main Index
662 MSC Nastran Quick Reference Guide
Displacement Output Request
VECTOR (Case) Displacement Output Request
Requests the form and type of displacement vector output.
See the description of the DISPLACEMENT (Case).
Main Index
CHAPTER 5 663
Velocity Output Request
VELOCITY (Case) Velocity Output Request
Requests the form and type of velocity vector output.
Format:
NONE
SORT1 PRINT, PUNCH PRINT, PUNCH
VELOCITY ( ODS = sid
SORT2 PLOT PLOT
ALL
REAL or IMAG PSDF,ATOC,CRMS RPRINT
RPUNCH , CID
PHASE or RALL NORPRINT
ALL
= n
NONE
Examples:
VELOCITY=5
VELOCITY(SORT2,PHASE,PUNCH)=ALL
VELOCITY(SORT2, PRINT, PSDF, CRMS, RPUNCH)=20
VELOCITY(PRINT, RALL, NORPRINT)=ALL
VELOCITY (REAL, SORT2, ODS(PLOT)=ALL, PLOT, PUNCH) = 100
Describer Meaning
SORT1 Output will be presented as a tabular listing of grid points for each load, frequency,
eigenvalue, or time, depending on the solution sequence.
SORT2 Output will be presented as a tabular listing of frequency or time for each grid point.
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
Main Index
664 MSC Nastran Quick Reference Guide
Velocity Output Request
Describer Meaning
ODS Requests Operational Deflection Shape (ODS) element stress output. See Remark 7.
sid Set identification of a previously appearing SET command. Only element stresses in
elements that appear on this SET command will be output as ODS element stresses
(Integer > 0).
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL or IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
PSDF Requests the power spectral density function be calculated and stored in the database
for random analysis postprocessing. Request must be made above the subcase level,
and RANDOM must be selected in Case Control. See Remark 5.
ATOC Requests the autocorrelation function be calculated and stored in the database for
random analysis postprocessing. Request must be made above the subcase level, and
RANDOM must be selected in Case Control. See Remark 5.
CRMS Requests the cumulative root mean square function be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM must
be selected in Case Control. See Remark 5.
RALL Requests all of PSDF, ATOC, and CRMS be calculated for random analysis
postprocessing. Request must be made above the subcase level, and RANDOM must
be selected in Case Control. See Remark 5.
RPRINT Writes random analysis results in the print file (Default).
NORPRINT Disables the writing of random analysis results in the print file.
RPUNCH Writes random analysis results in the punch file.
CID Request to print output coordinate system ID in printed output (.f06) file.
ALL Velocity for all solution points will be output.
NONE Velocity for no solution points will be output.
n Set identification of a previously appearing SET command. Only velocities of points
with identification numbers that appear on this SET command will be output
(Integer > 0).
Remarks:
1. Velocity output is only available for transient and frequency response problems.
2. See Remark 1 under DISPLACEMENT (Case) for a discussion of SORT1 and SORT2.
3. VELOCITY=NONE overrides an overall output request.
4. Velocity results are output in the global coordinate system (see field CD on the GRID Bulk Data
entry).
Main Index
CHAPTER 5 665
Velocity Output Request
5. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis. Here PSDF, ATOC and CRMS output is always in SORT2 format.
6. Note that the CID keyword affects only grid point related output, such as DISP, VELO, ACCEL,
OLOAD, SPCF and MPCF. In addition, the CID keyword needs to appear only once in a grid point-
related output request anywhere in the Case Control Section to turn on the printing algorithm.
7. ODS request must work with Case Control command, ODSFREQ, which specifies a selection of the
excitation frequencies for ODS output.
Main Index
666 MSC Nastran Quick Reference Guide
Vibration Intensity, VI, Output Request
VINTENSITY (Case) Vibration Intensity, VI, Output Request
Request output of vibration intensity for structural elements in SOLs 108 and 111 only.
Format:
ALL
PRINT, PUNCH
VINTENSITY = n
PLOT
NONE
Examples:
VINTENSITY = ALL
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
ALL Vibration Intensities will be computed for all supported structural elements.
n Set identification of a previously defined set of structural elements. Vibration
Intensities will be computed for the structural elements in this set only.
NONE Vibration intensity will not be processed.
Remarks:
1. VINTENSITY = NONE overrides an overall request.
2. This Case Control command can be used in SOL 108 and SOL 111 only
3. Structural element types covered for VI computations are BAR, BEAM, QUAD4, TRIA3, QUADR,
TRIAR, QUAD8, TRIA6, HEXA, PENTA and TETRA.
4. For BAR/BEAM element types, VI is computed in element axial direction using following equation
Main Index
CHAPTER 5 667
Vibration Intensity, VI, Output Request
Where Fx = axial force in element x direction,
V1 = shear force in element y direction,
V2 = shear force in element z direction,
T = torsion about element x direction,
M2 = Bending moment in element y direction,
M1 = Bending moment in element z direction,
vi = Translational velocity about element i direction,
i = Rotational velocity about element i direction,
'*' superscript denotes complex conjugate of the complex value. VIx is computed at both end of
BAR/BEAM element and the average of ends VI is presented as element VIx.
5. For 2D element types, such as QUAD4/TRIA3, VI is computed in element coordinate system using
following equations
* * * * *
VI x = REAL – V x z – M x y + M xy x + F x x + F xy y Areax,
* * * * *
VI y = REAL – V y z + M y x – M xy y + F y y + F yx x Areay,
Where Vx , Vy = transverse shear forces,
Mx , My= Bending moments,
Mxy = twisting moment,
Fx , Fy = Membrane forces,
Fxy, Fyx = Membrane shear,
Areax, Areay = Area in the corresponding element axes,
vi = Translational velocity about element i direction,
i = Rotational velocity about element i direction,
'*' superscript denotes complex conjugate of the complex value. VIi, VIi are computed in element
coordinate system using average corner velocities and the element forces at the element center.
6. For 3D element types, VI is computed in basic coordinate system using following equations
VI x = REAL[ – x v x + xy v y + xz v z
VI y = REAL[ – y v y + yx v x + yz v z
VI z = REAL[ – z v z + zx v x + zy v y
Main Index
668 MSC Nastran Quick Reference Guide
Vibration Intensity, VI, Output Request
Where VIx , VIy , VIx = VI in basic coordinate system,
x, y , z = Normal stresses,
xy , yz , xz = Shear stresses,
vi = Translational velocity in basic i direction,
7. VI for all element types is presented in basic coordinate system in print and/or punch output.
Main Index
CHAPTER 5 669
Rigid Body Mass Reduction Check
WEIGHTCHECK (Case) Rigid Body Mass Reduction Check
At each stage of the mass matrix reduction, compute rigid body mass and compare with the rigid body mass
in the g-set.
Format:
( PRINT PUNCH, SET = ( J G, N, N + AUTOSPC, F, A,V )
NOPRINT ALL
WEIGHTCHECK = YES
NO
GRID = gid, CGI = YES WEIGHT )
NO MASS
Examples:
WEIGHTCHECK=YES
WEIGHTCHECK(GRID=12,SET=(G,N,A),MASS)=YES
Describer Meaning
PRINT Write output to the print file (Default).
NOPRINT Do not write output to the print file.
PUNCH Write output to the punch file.
SET Selects degree of freedom set(s). WEIGHTCHECK output with SET=J
includes only the mass interior to the superelement. Output with SET=G
includes SET=J and the mass from the upstream superelements. If there are no
superelements in the model or no upstream superelements with mass, then the
output for SET=J and SET=G will be identical. See also Remark 4.
(Default SET=G).
gid Reference grid point for the calculation of rigid body motion. The default is
the origin of the basic coordinate system.
CGI For SET G, CGI = YES requests output of center of gravity and mass
moments of inertia (Default: CGI = NO).
WEIGHT/MASS Selects output in units of weight or mass (Default = WEIGHT).
Remarks:
1. WEIGHTCHECK must be specified above the subcase level.
2. For SET=N, N+AUTOSPC, F, or A, the WEIGHTCHECK command also outputs a percentage
loss or gain in the reduced rigid body mass matrix (e.g., MAA) as compared to the g-set rigid body
mass matrix (e.g., MGG). G must also be requested to obtain this comparison; e.g.,
WEIGHTCHECK(SET=(G,A))=YES.
Main Index
670 MSC Nastran Quick Reference Guide
Rigid Body Mass Reduction Check
3. SET=N+AUTOSPC uses the mass matrix for the n-set with the rows corresponding to degrees of
freedom constrained by the PARAM, AUTOSPC operation zeroed out. If AUTOSPC was not
performed, then this check is redundant with respect to SET=N.
4. WEIGHTCHECK is available in all SOLs. However for the residual structure in SOLs 101, 105,
114, and 116, because no mass reduction is performed, only WEIGHTCHECK(SET=J) is available.
The 'J' set does not include upstream superelements.
5. If Lagrange multipliers are present via RIGID=LAGRAN or LGELIM then for degree-of-freedom
sets N, N+AUTOSPC, F, and A the check will be performed on degree-of-freedom sets NL,
NL+AUTOSPC, FL, and AL. The output will also be labeled accordingly.
Main Index
CHAPTER 5 671
Sensitivity Wetted Grids for SOL 108/111
WETSENS (Case) Sensitivity Wetted Grids for SOL 108/111
Select SOLUTION frequencies and RESPONSE DOFs for the generation of sensitivity for wetted grids.
Format:
PRINT, PUNCH REAL or IMAG
WETSENS THRESH = P RESPONSE = r
PLOT PHASE
SOLUTION = ALL
self
ALL
WETTED, SQWETT = n
NONE
Example:
SET 81 = 100.0, 120.0
SET 91 = 11240/T3, 4001/T1
SET 95 = 9000000 THRU 9000050
$
WETSENS(RESPONSE=91,solution=81,WETTED) = 95
Describer Meaning
Printer File (.f06) Punch File (.pch) Plot File (.op2/.h5)
PRINT or (blank) X X*
PUNCH X X*
PLOT X*
* The .op2 binary database file will be generated with “PARAM,POST, X” (or the POST Case Control
command), while the .h5 binary database file will be generated with “HDF5OUT” entry specified in Bulk
Data Section. Both .op2 and .h5 file can be created simultaneously. Note .xdb file is being deprecated.
THRESH The magnitude of element sensitivity less than p will be suppressed in all output
files: print, punch, plot, .op2, and .xdb. (Default = 0.0).
Main Index
672 MSC Nastran Quick Reference Guide
Case Control Applicability Tables
Describer Meaning
RESPONSE Adjoint load response will be computed for unit load applied at grid point
components in SET r.
SOLUTION Frequency responses at these forcing frequencies, defined in setf, will be used for
element sensitivity computation. (Default=all forcing frequencies)
WETTED Sensitivity for wetted grids will be computed and output.
SQWETT Squared sensitivity for wetted grids will be computed and output.
ALL Sensitivities for all elements will be calculated.
n Set identification number. Sensitivity for all elements specified on the SET n
command will be calculated. The SET n command must be specified in the same
subcase as the ELSSENS command, or above all subcases ( Integer > 0 ). The IDs
in set n must be GID (grid ID).
NONE Elemental sensitivity will not be output.
Remarks:
1. Set r for RESPONSE on WETSENS is default to set r on ELSENS. If no ELSENS in the
deck, set r for WETSENS must be provided.
2. The equations for various options of WETSENS
WETSENS(WETTED) = [Usetf]t[AGG][Ur]
WETSENS(SQWETT) = [Usetf]t[AGG][Ur] + [Usetf]*t[AGG]* [Ur]*
where [Usetf] is the displacement of SOLUTION
[Ur] is the displacement of RESPONSE
[AGG] is Fluid/Structure Coupling matrix
superscript * means complex conjugate of the term.
Case Control Applicability Tables
The following tables describe the applicability of Case Control commands to Solution Sequences:
Table 5-3 and SOLs (101 through 200) -- Subcase Definition, Superelement Control, and
Table 5-4 Auxiliary Model Control
Main Index
CHAPTER 5 673
Case Control Applicability Tables
Table 5-5 and SOLs (101 through 200) -- Data Selection
Table 5-6
Table 5-7 and SOLs (101 through 200) -- Output Selection
Table 5-8
Main Index
674 MSC Nastran Quick Reference Guide
Case Control Applicability Tables
Table 5-3 Case Control Commands in SOLs 101 Through 112 -- Subcase Definition, Superelement Control, and
Auxiliary Model Control
Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
ADACT X X
ANALYSIS
AUXCAS
AUXMODEL
BEGIN BULK X X X X X X X X X X
CAMPBELL X X
EXTDRIN X X X X X X X X
EXTDROUT X X X X X X X X
EXTSEOUT X X X X X X X X
MASTER X X X X X X X X X X
MCFRACTION X X X
MODES X
OUTPUT(blank) X X X X X X X X X X
OUTPUT(PLOT) X X X X X X X X X X
OUTPUT (POST) or X X X X X X X X X X
SETS DEFINITION
OUTPUT X X X X X X X X X X
(XYPLOT)
REPCASE X X
SEALL X X X X X X X X X X
SEDR X X X X X X X X X X
SEDV
SEEXCLUD X X X X X X X X X X
SEFINAL X X X X X X X X X X
SEKR X X X X X X X X X X
SELG X X X X X X X
SELR X X X X X X X
SEMR X X X X X X X X X X
SEMR X X X X X X X X
SERE
Main Index
CHAPTER 5 675
Case Control Applicability Tables
Table 5-3 Case Control Commands in SOLs 101 Through 112 -- Subcase Definition, Superelement Control, and
Auxiliary Model Control
Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
STOCHASTICS X X
SUBCASE X X X X X X X X X X
SUBCOM X
SUBSEQ X
SUPER X X X X X X X X X X
SYM X
SYMCOM X
SYMSEQ X
Table 5-4 Case Control Commands in SOLs 114 Through 400 -- Subcase Definition, Superelement Control, and
Auxiliary Model Control
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
ADACT
ANALYSIS X X X X
AUXCAS X
AUXMODEL X
BEGIN BULK X X X X X X X X X X X X X
CAMPBELL X X
EXTDRIN X
EXTDROUT X
EXTSEOUT X
MASTER X X X X X X X X X X X X
MODES X X X
OUTPUT(blank) X X X X X X X X X X X X
OUTPUT(PLOT) X X X X X X X X X X X X
OUTPUT (POST) or X X X X X X X X X X X X
SETS DEFINITION
OUTPUT(XYPLOT) X X X X X X X X X X X X
REPCASE X
SEALL X X X X X X X X X X X X
Main Index
676 MSC Nastran Quick Reference Guide
Case Control Applicability Tables
Table 5-4 Case Control Commands in SOLs 114 Through 400 -- Subcase Definition, Superelement Control, and
Auxiliary Model Control
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
SEDR X X X X X X X X X X X X
SEDV X X
SEEXCLUD X X X X X X X X X X X
SEFINAL X X X X X X X X X X X X
SEKR X X X X X X X X X X X X
SELG X X X X X X X X X X
SELR X X X X X X X X X X
SEMR X X X X X X X X X X X X
SEMR X X X X X X X X X X
SERE X X
STOCHASTICS X X
SUBCASE X X X X X X X X X X X X X
SUBCOM X
SUBSEQ X
SUPER X X X X X X X X X X X X
SYM X
SYMCOM X
SYMSEQ X
Table 5-5 Case Control Commands in SOLs 101 Through 112 -- Data Selection
Structured Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
ADAPT X X
AUTOSPC X X X X X X X X X
AXISYMME X X X X X X X X X
B2GG X X X X X X X X X X
B2PP X X X X X X
BC X
CLOAD X
CMETHOD X X
DEFORM X X
Main Index
CHAPTER 5 677
Case Control Applicability Tables
Table 5-5 Case Control Commands in SOLs 101 Through 112 -- Data Selection (continued)
Structured Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
DESGLB
DESOBJ
DESSUB
DLOAD X X X X X X
DSYM
FMETHOD
FREQUENC X X
GUST
HARMONIC X X X X X X X X X
IC X
K2GG X X X X X X X X X X
K2PP X X X X X X
LOAD X X X X X X X
LOADSET X X X X X X X
M2GG X X X X X X X X X X
M2PP X X X X X X
METHOD X X X X X X X X
MFLUID X X X X X X X
MODTRAK
MPC X X X X X X X X X X
NLPARM X
NONLINEA X X
OMODES X X X* X* X*
P2G X X X X X X X
RANDOM X X
RESVEC X X X X X X X X
SDAMPING X X X
Main Index
678 MSC Nastran Quick Reference Guide
Case Control Applicability Tables
Table 5-5 Case Control Commands in SOLs 101 Through 112 -- Data Selection (continued)
Structured Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
SDENSITY X X X
SMETHOD X X X X
SPC X X X X X X X X X X
STATSUB* X X X X X X X X X
SUPORT1 X X X X X X X X X X
TEMPER(INIT) X
TEMPER(LOAD) X X X X X X X
TEMPER(MATE) X X X X X X X X X X
TFL X X X X X X
TRIM
TRIMGRP X
TSTEP X X
WEIGHTCHECK X X X X X X X X X X
*If STATSUB is specified, then the Case Control commands that select static loads become
applicable to the solution sequence supporting STATSUB.
Table 5-6 Case Control Commands in SOLs 114 Through 400 -- Data Selection
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
ADAPT
AUTOSPC X X X X X X X X X X
AXISYMME X
B2GG X X X X X X X X X X X X X
B2PP X X X X X X X
BC
CLOAD X
CMETHOD X
DEFORM X X X X
DESGLB X
DESMOD X
DESOBJ X
Main Index
CHAPTER 5 679
Case Control Applicability Tables
Table 5-6 Case Control Commands in SOLs 114 Through 400 -- Data Selection (continued)
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
DESSUB X
DESVAR X
DLOAD X X X X X X X
DSYM X X X X
FMETHOD X X
FREQUENC X X X
GUST X X
HARMONIC X X X X X
IC X
K2GG X X X X X X X X X X X X X
K2PP X X X X X X X
LOAD X X X X X X X X X
LOADSET X X X X X X X X X X
M2GG X X X X X X X X X X X X X
M2PP X X X X X X X
METHOD X X X X X X X X X X X
MFLUID X X X X X
MODTRAK X
MPC X X X X X X X X X X X X
NLBUCK X
NLPARM X
NONLINEA X X
OMODES X X
P2G X X X X X X X X
RANDOM X X
RESVEC X X X X X X X X X X
SDAMPING X X X
SMETHOD X
SPC X X X X X X X X X X X X
STATSUB X X
SUPORT1 X X X X X X X X X X X
TEMPER(INIT)
TEMPER(LOAD) X X X X X
Main Index
680 MSC Nastran Quick Reference Guide
Case Control Applicability Tables
Table 5-6 Case Control Commands in SOLs 114 Through 400 -- Data Selection (continued)
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
TEMPER(MATE) X X X X X X X X X X X
TFL X X X X X X
TRIM X X
TRIMGRP X
TSTEP X X X X
WEIGHTCHECK X X X X X X X X X X
Table 5-7 Case Control Commands in SOLs 101 Through 112 -- Output Selection
Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
ACCELERA X X X X X
ACFPMRESULT X X
ACPOWER X X
AEROF
APRESSURE
BOUTPUT X
CMSENRGY X X X X X
DATAREC X X X X X X
DISPLACE X X X X X X X X X X
DSAPRT
ECHO X X X X X X X X X X
EDE X X X X X* X X
EKE X X X X X* X X
ELSDCON X X
ELSUM X X X X X X X X X X
ENTHALPY
ERP X X
ESE X X X X X X X X* X X
FLUX X
FORCE X X X X X X X X X X
Main Index
CHAPTER 5 681
Case Control Applicability Tables
Table 5-7 Case Control Commands in SOLs 101 Through 112 -- Output Selection (continued)
Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
GPFORCE X X X X X X+ X X+
GPKE X X* X* X*
GPSDCON X X
GPSTRAIN X X X X X
GPSTRESS X X X X X
GROUNDCHECK X X X X X X X X X X
HARMONIC X X X X X X X X X
HDOT
HOUTPUT
INTENSITY X X
LABEL X X X X X X X X X X
LINE X X X X X X X X X X
MAXLINES X X X X X
MAXMIN (old form) X X X X X
MAXMIN (DEF) X X X X X X
MPCFORCE X X X X X X X X X
MPRES X X X X X X X
NLLOAD X X
NOUTPUT
OFREQUEN X X
OLOAD X X X X X X X
OTIME X X
PAGE X X X X X X X X X X
PARTN X X X X X X X X X X
PLOTID X X X X X X X X X X
POST X
PRESSURE X X X X
ROTSEKE X X
SACCELER X X X X
SDISPLAC X X X X X X X
SET X X X X X X X X X X
Main Index
682 MSC Nastran Quick Reference Guide
Case Control Applicability Tables
Table 5-7 Case Control Commands in SOLs 101 Through 112 -- Output Selection (continued)
Solution Number
Command Name 101 103 105 106 107 108 109 110 111 112
SKIP X X X X X X X X X X
SPCFORCE X X X X X X X X X X
STRAIN X X X X X X X X X X
STRESS X X X X X X X X X X
STRFIELD X X X X X
SUBTITLE X X X X X X X X X X
SURFACE X X X X X
SVECTOR X X X X X
SVELOCITY X X X X
THERMAL X
TITLE X X X X X X X X X X
VECTOR X X X X X X X X X X
VELOCITY X X X X
VOLUME X X X X X
*For modal part of solution.
+
Forces limited to stiffness contributions.
Main Index
CHAPTER 5 683
Case Control Applicability Tables
Table 5-8 Case Control Commands in SOLs 114 Through 400 --Output Selection
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
ACCELERA X X X X X
ACFPMRESULT
ACPOWER
AEROF X X X X
APRESSURE X X
BOUTPUT X X X
CMSENRGY X X X
DATAREC X
DISPLACE X X X X X X X X X X X X
DSAPRT X
ECHO X X X X X X X X X X X X
EDE X X X X
EKE X X X X
ELSDCON X X
ELSUM X X X X X X X X X
ENTHALPY X
ERP X X
ESE X X X X X X X
FLUX X X X X
FORCE X X X X X X X X X X X X
GPFORCE X X X X X X
GPKE X X
GPSDCON X X X X
GPSTRAIN X X X X X X
GPSTRESS X X X X X X X
GROUNDCHECK X X X X X X X X X X X*
HARMONY X X X X X X
HDOT X
HOUTPUT X X X X
INTENSITY
Main Index
684 MSC Nastran Quick Reference Guide
Case Control Applicability Tables
Table 5-8 Case Control Commands in SOLs 114 Through 400 --Output Selection (continued)
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
LABEL X X X X X X X X X X X X
LINE X X X X X X X X X X X X
MAXLINES X X X X X X X X X X X X
MAXMIN(DEF) X
MPCFORCE X X X X X X X X X
MPRES X X X X X X
NLLOAD X X
NLOPRM X
NLSTEP X
NOUTPUT X X X X
OFREQUEN X X X
OLOAD X X X X X X X X X X
OTIME X X X X X X X X X X
PAGE X X X X X X X X X X X X
PARTN X X X X X X X X X X X X
PLOTID X X X X X X X X X X X
PRESSURE X X
ROTSEKE X
SACCELER X X X X X
SDISPLAC X X X X X X X X
SET X X X X X X X X X X X X
SKIP X X X X X X X X X X X
SPCFORCE X X X X X X X X X X X X
STRAIN X X X X X X X X X X X X
STRESS X X X X X X X X X X X X
STRFIELD X X X X X
SUBSET X
SUBTITLE X X X X X X X X X X X X
Main Index
CHAPTER 5 685
Case Control Applicability Tables
Table 5-8 Case Control Commands in SOLs 114 Through 400 --Output Selection (continued)
Solution Number
Command Name 114 115 116 118 128 129 144 145 146 153 159 200 400
SURFACE X X X X
SVECTOR X X X X X X
SVELOCITY X X X X X
TEMPERATURE
THERMAL X X X X
TITLE X X X X X X X X X X X X
TRIMF X X
VECTOR X X X X X X X X X X X X
VELOCITY X X X X X
VOLUME X X X X
* Only multidisciplinary analysis
Main Index
686 MSC Nastran Quick Reference Guide
X-Y PLOT Commands
X-Y PLOT Commands
The X-Y output request packet of the Case Control Section includes all commands between either
OUTPUT(XYPLOT) or OUTPUT(XYOUT), and either BEGIN BULK or OUTPUT(PLOT). The
remainder of this section describes the X-Y output commands.
A single set of plotted X-Y pairs is known as a curve. Curves are the entities to be plotted. The surface (paper,
microfilm frame, etc.) on which one or more curves is plotted is known as a frame. Curves may be plotted
on a whole frame, an upper-half frame, or a lower-half frame. Grid lines, tic marks, axes, axis labeling, and
other graphic control options may be chosen by the user. The program will select defaults for parameters not
selected by the user.
Only two commands are required for an X-Y output request.
1. Only one of OUTPUT(XYPLOT) or OUTPUT(XYOUT) at the beginning of the X-Y output
command packet.
2. At least one of the commands XYPLOT, XYPEAK, XYPRINT, XYPUNCH, XYPAPLOT.
The commands OUTPUT(XYPLOT) and OUTPUT(XYOUT) are equivalent. If the X-Y output is to be
printed and/or punched, a PLOTTER command is not required.
If only the required commands are used, the graphic control options will all assume default values. Curves
using all default parameters have the following general characteristics.
1. Tic marks are drawn on all edges of the frame. Five spaces are provided on each edge of the frame.
2. All tic marks are labeled with their values.
3. Linear scales are used.
4. Scales are selected such that all points fall within the frame.
5. The plotter points are connected with straight lines.
6. The plotted points are not identified with symbols.
The above characteristics may be modified by inserting any of the parameter definition commands in the next
section, ahead of the XY____ command(s). The use of a parameter definition command sets the value of that
parameter for all following command operation commands unless the CLEAR command is inserted. If grid
lines are requested, they will be drawn at the locations of all tic marks that result from defaults or user request.
The locations of tic marks (or grid lines) for logarithmic scales cannot be selected by the user. Values for
logarithmic spacing are selected by the program. The values for the number of tic marks (or grid lines) per
cycle depend on the number of logarithmic cycles required for the range of the plotted values.
The definition and rules for the X-Y output commands follow. The form of X-Y output commands differ in
many instances from that of similar commands used in the OUTPUT(PLOT) section.
X-Y Output Command Summary
Commands Applied To All Curves
PLOTTER Selects format of plot file for interpretation by plotter postprocessor.
CAMERA Selects plotter media.
Main Index
CHAPTER 5 687
X-Y PLOT Commands
Commands Applied To All Curves
PENSIZE Selects pen number.
DENSITY Selects the line density for microfilm plotters only.
XPAPER Defines the size of the paper in x-direction.
YPAPER Defines the size of the paper in y-direction.
XMIN Specifies the minimum value on the x-axis.
XMAX Specifies the maximum value on the x-axis.
XLOG Selects logarithmic or linear x-axis.
YAXIS Controls the plotting of the y-axis on all curves.
XINTERCEPT Specifies the location of the x-axis on the y-axis.
UPPER TICS Specifies how to draw tic marks on upper edge.
LOWER TICS Specifies how to draw tic marks on lower edge.
CURVELINESYMBOL Selects lines and/or symbols to be drawn through the x-y points.
XDIVISIONS Specifies spacing of tic marks on the x-axis for all curves.
XVALUE PRINT SKIP Specifies how often to print the x-values alongside the x-axis tic marks.
CLEAR Resets X-Y Plot commands to their default value.
XTITLE Defines a character string that will appear along the x-axis.
TCURVE Defines a character string that will appear at the top of the plot frame.
LONG Controls amount of curve’s summary printout.
CSCALE Defines scale factor for characters in the plot frame.
Commands Applied to Whole Frame Curves Only
YMIN Specifies the minimum value on the y-axis.
YMAX Specifies the maximum value on the y-axis.
XAXIS Controls the plotting of the x-axis.
YINTERCEPT Specifies the location of the y-axis on the x-axis.
YLOG Selects logarithmic or linear y-axis.
LEFT TICS Specifies how to draw tic marks on left edge.
RIGHT TICS Specifies how to draw tic marks on right edge of the frame.
ALLEDGE TICS Specifies how to draw tic marks on all edges of the frame.
YDIVISIONS Specifies spacing of tic marks on the y-axis.
YVALUE PRINT Specifies how often to print the y-values alongside the y-axis tic marks
SKIP applies.
Main Index
688 MSC Nastran Quick Reference Guide
X-Y PLOT Commands
Commands Applied to Whole Frame Curves Only
XGRID LINES Controls the drawing of the grid lines parallel to the y-axis at the x-axis tic
marks.
YGRID LINES Controls the drawing of the grid lines parallel to the x-axis at the y-axis tic
marks.
YTITLE Defines a character string that will appear along the y-axis
Commands Applied to Upper Half Frame Curves Only
YTMIN Specifies the minimum value on the y-axis.
YTMAX Specifies the maximum value on the y-axis.
YTAXIS Controls the plotting of the y-axis.
YTINTERCEPT Specifies the location of the y-axis on the x-axis.
YTLOG Selects logarithmic or linear y-axis.
TLEFT TICS Specifies how to draw tic marks on the left edge.
TRIGHT TICS Specifies how to draw tic marks on the right edges.
TALL EDGE TICS Specifies how to draw tic marks on all edges.
YTDIVISIONS Specifies spacing of tic marks on the y-axis.
YTVALUE PRINT Specifies how often to print the y-values alongside the y-axis tic marks.
SKIP
XTGRID LINES Controls the drawing of the grid lines parallel to the y-axis at the x-axis tic
marks.
YTGRID LINES Controls the drawing of the grid lines parallel to the x-axis at the y-axis tic
marks.
YTTITLE Defines a character string that will appear along the y-axis.
Commands Applied to Lower Half Frame Curves Only
YBMIN Specifies the minimum value on the y-axis.
YBMAX Specifies the maximum value on the y-axis.
XBAXIS Controls the plotting of the x-axis.
YBINTERCEPT Specifies the location of the y-axis on the x-axis.
YBLOG Selects logarithmic or linear y-axis.
BLEFT TICS Specifies how to draw tic marks on left edge.
BRIGHT TICS Specifies how to draw tic marks on right edge.
BALL EDGE TICS Specifies how to draw tic marks on all edges.
YBDIVISIONS Specifies spacing of tic marks on the y-axis.
Main Index
CHAPTER 5 689
X-Y PLOT Commands
Commands Applied to Lower Half Frame Curves Only
YBVALUE PRINT Specifies how often to print the y-values alongside the y-axis tic marks.
SKIP
XBGRID LINES Controls the drawing of the grid lines parallel to the y-axis at the x-axis tic
marks.
YBGRID LINES Controls the drawing of the grid lines parallel to the x-axis at the y-axis tic
marks.
YBTITLE Defines a character string that will appear along the y-axis.
X-Y Plot Generation Commands
XYPAPLOT Generate X-Y plots for a printer.
XYPEAK Print only the summary for all curves.
XYPLOT Generate X-Y plots for a plotter.
XYPRINT Generate table of X-Y pairs for a printer.
XYPUNCH Generate table of X-Y pairs for the PUNCH file
Main Index
690 MSC Nastran Quick Reference Guide
Controls Drawing of Tic Marks on All Edges
ALLEDGE TICS Controls Drawing of Tic Marks on All Edges
Specifies how to draw tic marks on all edges of the frame.
Format:
ALLEDGE TICS tic
Example:
ALLEDGE -1
Describer Meaning
tic Specifies how to draw tic marks (Integer, Default= 0).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values (Default).
1 Draw tic marks and associated values.
Remarks:
1. ALLEDGE TICS applies to whole frame curves only.
2. To determine if on any given edge (a) tic marks will be drawn without values, (b) no tic marks or
values will be drawn, or (c) tic marks with values will be drawn, the following sum must be computed
by the user. Add the tic values of the edge in question to its associated ALLEDGE TICS, TALL
EDGE TICS, or BALL EDGE TICS tic values. If the resulting value is less than zero, tic marks will
be drawn without values. If the resulting value is zero, no tic marks or values will be drawn. If the
resulting value is greater than zero, tic marks with values will be drawn. The user should be careful in
the use of the ALLEDGE TICS, TALL EDGE TICS, or BALL EDGE TICS commands. For
example, the use of only the ALLEDGE TICS = -1 command will result in no tic marks or values
being drawn, since the default values for individual edges is +1. Tic values input may only be -1, 0,
or 1.
Main Index
CHAPTER 5 691
Controls Drawing of Tic Marks on Lower Half
BALL EDGE TICS Controls Drawing of Tic Marks on Lower Half
Specifies how to draw tic marks on lower half of frame.
Format:
BALL EDGE TICS tic
Example:
BALL EDGE TICS -1
Describer Meaning
tic Specifies how to draw tic marks (Integer, Default = 0).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values (Default).
1 Draw tic marks and associated values.
Remarks:
1. BALL EDGE TICS applies to lower frame curves only.
2. See Remark 2 under ALLEDGE TICS.
Main Index
692 MSC Nastran Quick Reference Guide
Controls Drawing of Tic Marks on Left Edge
BLEFT TICS Controls Drawing of Tic Marks on Left Edge
Specifies how to draw tic marks on left edge of lower half of frame.
Format:
BLEFT TICS tic
Example:
BLEFT TICS -1
Describer Meaning
tic Specifies how to draw tic marks (Integer; Default= 1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. BLEFT TICS applies to lower frame curves only.
2. See Remark 2 under ALLEDGE TICS.
3. See related command BRIGHT TICS.
Main Index
CHAPTER 5 693
Controls Drawing of Tic Marks on Right Edge
BRIGHT TICS Controls Drawing of Tic Marks on Right Edge
Specifies how to draw tic marks on right edge of lower half of frame.
Format:
BRIGHT TICS tic
Example:
BRIGHT TICS -1
Describer Meaning
tic Specifies how to draw tic marks (Integer; Default = 1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. BRIGHT TICS applies to lower frame curves only.
2. See Remark 2 under ALLEDGE TICS.
Main Index
694 MSC Nastran Quick Reference Guide
Plotter Media Selection
CAMERA Plotter Media Selection
Selects plotter media.
Format:
CAMERA ctype
Example:
CAMERA 1
Describer Meaning
ctype Camera type (Integer 1, 2, or 3; Default= 2).
1 Film
2 Paper (Default)
3 Both
Remark:
1. If the CAMERA command is not specified then CAMERA 2 is assumed.
Main Index
CHAPTER 5 695
Resets X-Y Plot Commands
CLEAR Resets X-Y Plot Commands
Resets X-Y Plot commands to their default values.
Format
CLEAR
Remark:
1. All commands except XTITLE, YTITLE, YTTITLE, YBTITLE, and TCURVE will revert to their
default values.
Main Index
696 MSC Nastran Quick Reference Guide
Character Scale Factor
CSCALE Character Scale Factor
Defines scale factor for characters in the plot frame. See the command CSCALE in the OUTPUT(PLOT)
Section.
Main Index
CHAPTER 5 697
Curve, Line and Symbol Selection
CURVELINESYMBOL Curve, Line and Symbol Selection
Selects lines and/or symbols to be drawn through the x-y points.
Format:
CURVELINESYMBOL symtype
Example:
CURV 4
Describer Meaning
symtype Specifies the symbol drawn at the x-y points. If symtype is 0 then only lines will
be drawn through the points with no symbol. If symtype is less than zero then
only the symbol and not the lines will be drawn. If symtype is greater than zero
then both the symbol and the lines will be drawn (-9< Integer < 9; Default= 0).
symtype Symbol
0 none
1 X
2 *
3 +
4 -
5 .
6 ×
7 []
8 <>
9 /\
Remark:
1. If more than one curve is plotted per frame, then the symbol number is incremented by 1 for each
curve.
Main Index
698 MSC Nastran Quick Reference Guide
Microfilm Plotter Line Density
DENSITY Microfilm Plotter Line Density
Selects the line density for microfilm plotters only.
Format
DENSITY d
Example
DENS 3
Describer Meaning
d Specifies line density scale factor for microfilm plotters. A line density of d is d
times heavier than a line density of 1 (Integer > 0; Default = 1).
Main Index
CHAPTER 5 699
Controls Drawing of Tic Marks on Left Edge
LEFT TICS Controls Drawing of Tic Marks on Left Edge
Specifies how to draw tic marks on left edge of whole frame curves.
Format:
LEFT TICS tic
Example:
LEFT -1
Describer Meaning
tic Specifies how to draw tic marks (Integer; Default = 1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. LEFT TICS applies to whole frame curves only.
2. See Remark 2 under ALLEDGE TICS.
3. See related command RIGHT TICS.
Main Index
700 MSC Nastran Quick Reference Guide
Summary Print Control
LONG Summary Print Control
Controls amount of curve’s summary printout.
Format:
LONG YES
NO
Describers Meaning
YES One page for each curve’s summary (Default).
NO Condensed curve summary.
Remark:
1. If LONG is not specified, then LONG=NO is assumed.
Main Index
CHAPTER 5 701
Controls Drawing of Tic Marks on Lower Edge
LOWER TICS Controls Drawing of Tic Marks on Lower Edge
Specifies how to draw tic marks on lower edge.
Format:
LOWER TICS tic
Example:
LOWER -1
Describers Meaning
tic Specifies how to draw tic marks (Integer; Default= 1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. LOWER TICS applies to all curves.
2. See Remark 2 under ALLEDGE TICS.
Main Index
702 MSC Nastran Quick Reference Guide
Pen Selection
PENSIZE Pen Selection
Selects pen number.
Format:
PENSIZE p
Example:
PENS 3
Describer Meaning
p Specifies pen number to be used to generate the plot (Integer > 0; Default =1).
Main Index
CHAPTER 5 703
X-Y Plot File Format
PLOTTER X-Y Plot File Format
See the command PLOTTER in the OUTPUT(PLOT) Section.
Main Index
704 MSC Nastran Quick Reference Guide
Controls Drawing of Tic Marks on Right Edge
RIGHT TICS Controls Drawing of Tic Marks on Right Edge
Specifies how to draw tic marks on right edge of the frame.
Format:
RIGHT TICS tic
Example:
RIGHT -1
Describers Meaning
tic Specifies how to draw tic marks (Integer; Default = 1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. RIGHT TICS applies to whole frame curves only.
2. See Remark 2 under ALLEDGE TICS.
3. See related command LEFT TICS.
Main Index
CHAPTER 5 705
Superelement Plot Delimiter
SEPLOT Superelement Plot Delimiter
Assigns the subsequent PLOT or XYPLOT commands to one or more superelements.
Format:
SEPLOT seid1 [ seid2 ... ]
Examples:
SEPLOT 5
SEPLOT 0 3 7 200
Describer Meaning
seidi Superelement identification number (Integer > 0).
Remarks:
1. See also related command SEUPPLOT.
2. Any PLOT or XYPLOT commands appearing above all SEPLOT (or SEUPPLOT) commands will
apply in all SEPLOT (or SEUPPLOT) packets.
3. For multiple PLOT or XYPLOT commands, there should be a SEPLOT command with each PLOT.
For the special case where the PLOTs or XYPLOTs refer to the same superelements and use the same
FIND, a single SEPLOT followed by a single FIND may be placed above all commands.
Main Index
706 MSC Nastran Quick Reference Guide
Superelement Plot Delimiter
SEUPPLOT Superelement Plot Delimiter
Assigns the subsequent PLOT or XYPLOT commands to a superelement and all of its upstream
superelements.
Format:
SEUPPLOT seid
Example:
SEUPPLOT 7
Describer Meaning
seid Superelement identification number (Integer > 0).
Remarks:
1. See also related command SEPLOT.
2. Any PLOT or XYPLOT commands appearing above all SEUPPLOT (or SEPLOT) commands will
apply in all SEUPPLOT (or SEPLOT) packets.
3. For multiple PLOT or XYPLOT commands, there should be a SEUPPLOT command with each
PLOT. For the special case where the PLOTs or XYPLOTs refer to the same superelements and use
the same FIND, a single SEUPPLOT followed by a single FIND may be placed above all the
commands.
Main Index
CHAPTER 5 707
Controls Drawing of Tic Marks on All Edges
TALL EDGE TICS Controls Drawing of Tic Marks on All Edges
Specifies how to draw tic marks on all edges of the upper half of the frame.
Format:
TALL EDGE TICS tic
Example:
TALL -1
Describers Meaning
tic Specifies how to draw tic marks (Integer; Default = 0).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values (Default).
1 Draw tic marks and associated values.
Remarks:
1. TALL EDGE TICS applies to upper half frame curves only.
2. See Remark 2 under ALLEDGE TICS.
Main Index
708 MSC Nastran Quick Reference Guide
Curve Title
TCURVE Curve Title
Defines a character string that will appear at the top of the plot frame.
Format:
TCURVE ctitle
Example:
TCUR RIGHT WING -- LOAD CASE 3
Describer Meaning
ctitle Any character string (Character; Default = blank).
Remark:
1. TCURVE may not be continued to the next command line.
Main Index
CHAPTER 5 709
Controls Drawing of Tic Marks on All Edges
TLEFT TICS Controls Drawing of Tic Marks on All Edges
Specifies how to draw tic marks on the left edge of the upper half of the frame.
Format:
TLEFT TICS tic
Example:
TLEFT -1
Describers Meaning
tic Specifies how to draw tic marks (Integer; Default=1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. TLEFT TICS applies to upper half frame curves only.
2. See Remark 2 under ALLEDGE TICS.
3. See related command TRIGHT TICS.
Main Index
710 MSC Nastran Quick Reference Guide
Controls Drawing of Tic Marks on the Right Edge
TRIGHT TICS Controls Drawing of Tic Marks on the Right Edge
Specifies how to draw tic marks on all edges of the upper half of the frame.
Format:
TRIGHT TICS tic
Example:
TRIGHT -1
Describers Meaning
tic Specifies how to draw tic marks (Integer; Default = 1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. TRIGHT TICS applies to upper half frame curves only.
2. See Remark 2 under ALLEDGE TICS.
3. See related command TLEFT TICS.
Main Index
CHAPTER 5 711
Controls Drawing Of Tic Marks On Upper Edge
UPPER TICS Controls Drawing Of Tic Marks On Upper Edge
Specifies how to draw tic marks on upper edge.
Format:
UPPER TICS tic
Example:
UPPER -1
Describers Meaning
tic Specifies how to draw tic marks (Integer; Default= 1).
-1 Draw tic marks only.
0 Do not draw tic marks or associated values.
1 Draw tic marks and associated values (Default).
Remarks:
1. UPPER TICS applies to all curves.
2. See Remark 2 under ALLEDGE TICS.
3. See related command LOWER TICS.
Main Index
712 MSC Nastran Quick Reference Guide
X-Axis Plot Control
XAXIS X-Axis Plot Control
Controls the plotting of the x-axis on whole frame curves only.
Format:
XAXIS YES
NO
Describers Meaning
YES Plot the x-axis.
NO Do not plot the x-axis (Default).
Remarks:
1. XAXIS applies to whole frame curves only.
2. See related command YAXIS.
Main Index
CHAPTER 5 713
X-Axis Plot Control
XBAXIS X-Axis Plot Control
Controls the plotting of the x-axis on lower half frame curves only.
Format:
XBAXIS YES
NO
Describers Meaning
YES Plot the x-axis.
NO Do not plot the x-axis (Default).
Remark:
1. XBAXIS applies to lower half frame curves only.
Main Index
714 MSC Nastran Quick Reference Guide
Plot X-Axis Grid Lines
XBGRID LINES Plot X-Axis Grid Lines
Controls the drawing of the grid lines parallel to the x-axis at the y-axis tic marks on lower half frame curves
only.
Format:
XBGRID LINES YES
NO
Describers Meaning
YES Plot the x-axis grid lines.
NO Do not plot the x-axis grid lines (Default).
Remarks:
1. XBGRID applies to lower half frame curves only.
2. See related command YBGRID LINES.
Main Index
CHAPTER 5 715
Tic Spacing on Y-Axis
XDIVISIONS Tic Spacing on Y-Axis
Specifies spacing of tic marks on the x-axis for all curves.
Format:
XDIVISIONS xd
Example:
XDIV 10
Describer Meaning
xd Number of spaces between tic marks on x-axis (Integer> 0; Default = 5).
Remarks:
1. XDIVISIONS applies to all curves and to the commands: UPPER TICS, LOWER TICS, and
YINTERCEPT.
2. XDIVISIONS is ignored for a logarithmic x-axes.
Main Index
716 MSC Nastran Quick Reference Guide
Plot X-Axis Grid Lines
XGRID LINES Plot X-Axis Grid Lines
Controls the drawing of the grid lines parallel to the x-axis at the y-axis tic marks on whole frame curves only.
Format:
XGRID LINES YES
NO
Describers Meaning
YES Plot the x-axis grid lines.
NO Do not plot the x-axis grid lines (Default).
Remarks:
1. XGRID applies to whole frame curves only.
2. See related command YGRID LINES.
Main Index
CHAPTER 5 717
Location of X-Axis on Y-Axis
XINTERCEPT Location of X-Axis on Y-Axis
Specifies the location of the x-axis on the y-axis.
Format:
XINTERCEPT xi
Example:
XINT 50.
Describer Meaning
xi Location of x-axis on the y-axis (Real; Default = 0.0).
Main Index
718 MSC Nastran Quick Reference Guide
Logarithmic or Linear X-Axis
XLOG Logarithmic or Linear X-Axis
Selects logarithmic or linear x-axis.
Format:
XLOG YES
NO
Describers Meaning
YES Plot a logarithmic x-axis.
NO Plot a linear x-axis (Default).
Remarks:
1. XLOG applies to all curves.
2. The default value for tic division interval depends on the number of log cycles. The default values for
tic divisions are given as follows but will range over whole cycles:
Number of Cycles Intermediate Values
1, 2 2., 3., 4., 5., 6., 7., 8., 9.
3 2., 3., 5., 7., 9.,
4 2., 4., 6., 8.,
5 2., 5., 8.
6, 7 3., 6.
8, 9, 10 3.
Main Index
CHAPTER 5 719
Maximum X-Axis Value
XMAX Maximum X-Axis Value
Specifies the maximum value on the x-axis.
Format:
XMAX xmax
Example:
XMAX 100.
Describer Meaning
xmax Maximum value on the x-axis. (Real)
Remarks:
1. If XMAX is not specified, then the maximum value is set to the highest value of x.
2. See related commands XMIN, YMIN, and YMAX.
Main Index
720 MSC Nastran Quick Reference Guide
Minimum X-Axis Value
XMIN Minimum X-Axis Value
Specifies the minimum value on the x-axis.
Format:
XMIN xmin
Example:
XMIN 100.
Describer Meaning
xmin Minimum value on the x-axis (Real).
Remarks:
1. XMIN applies to all curves.
2. If XMIN is not specified, then the minimum value is set to the lowest value of x.
3. See related commands XMAX, YMIN, and YMAX.
Main Index
CHAPTER 5 721
Paper Size in X-Direction
XPAPER Paper Size in X-Direction
Defines the size of the paper in x-direction.
Format:
XPAPER xsize
Example:
XPAP 10.
Describer Meaning
xsize Size of paper in x-direction and in inches (Real; Default = 20.0).
Remarks:
1. The default paper size is 20 by 20 inches.
2. See related command YPAPER.
Main Index
722 MSC Nastran Quick Reference Guide
X-Axis Plot Control
XTAXIS X-Axis Plot Control
XYAXIS applies to upper half frame curves only.
Format:
XTAXIS YES
NO
Describers Meaning
YES Plot the x-axis.
NO Do not plot the x-axis (Default).
Main Index
CHAPTER 5 723
Plot X-Axis Grid Lines
XTGRID LINES Plot X-Axis Grid Lines
Controls the drawing of the grid lines parallel to the x-axis at the y-axis tic marks on upper half frame curves
only.
Format:
XTGRID LINE YES
NO
Describers Meaning
YES Plot the x-axis grid lines.
NO Do not plot the x-axis grid lines (Default).
Remarks:
1. XTGRID applies to upper half frame curves only.
2. See related command YTGRID LINES
Main Index
724 MSC Nastran Quick Reference Guide
X-Axis Title
XTITLE X-Axis Title
Defines a character string that will appear along the x-axis.
Format:
XTITLE xtit
Example:
XTIT RIGHT WING CASE 3 - TIME
Describer Meaning
xtit Any character string (Character; Default = Blank).
Remarks:
1. XTITLE may not be continued to the next command line.
2. XTITLE applies to all curves.
Main Index
CHAPTER 5 725
Generate X-Y Plots for a Printer
XYPAPLOT Generate X-Y Plots for a Printer
Generates X-Y plots for a printer.
See XYPLOT for format, describers, and additional remarks.
Remarks:
1. The x-axis moves vertically along the page and the y-axis moves horizontally along the page.
2. An asterisk (*) identifies the points associated with the first curve of a frame, and then for successive
curves on a frame the points are designated by symbols O, A, B, C, D, E, F, G, and H.
Main Index
726 MSC Nastran Quick Reference Guide
Print Curve Summary
XYPEAK Print Curve Summary
Print only the summary for all curves. The summary output is titled:
“X Y - O U T P U T S U M M A R Y”
and is also printed under XYPLOT, XYPUNCH, XYPRINT, and XYPAPLOT. This output contains the
maximum and minimum values of y for the range of x.
See XYPLOT for format, describers, and additional remarks.
Main Index
CHAPTER 5 727
Generate X-Y Plots for a Plotter
XYPLOT Generate X-Y Plots for a Plotter
Generates X-Y Plots for a plotter.
Format:
XYPLOT yvtype ptype [ i1, i2, i3,... ] /
id11 (itemu11 [, iteml11] ) , id12 (itemu12 [, iteml12] ) , ... /
id21 (itemu21 [, iteml21] ) , id22 (itemu22 [, iteml22] ) , ... / ....
Examples:
BEGIN BULK or OUTPUT(PLOT) commands are shown as a reminder to place X-Y output request
packets properly in the Case Control Section; i.e., at the end of the Case Control Section, or just ahead of
any structure plot requests.
Example 1:
OUTPUT (XYPLOT)
CSCALE = 1.8
XYPLOT SDISP/16(T1)
BEGIN BULK
This sequence causes a single whole frame to be plotted for the T1 displacement component of solution set
point 16 using the default parameter values. If 16(T1) is not in the solution set, a warning message will be
printed and no plot will be made. The plot will be generated for the NASTRAN plotter on file PLT, which
must be available.
Example 2:
OUTPUT (XYOUT)
CSCALE = 1.8
XYPLOT, XYPRINT VELO RESPONSE 1,5 /3(R1,), 5(,R1)
OUTPUT (PLOT)
This sequence causes two frame plots (each consisting of an upper half frame and a lower half frame) to be
plotted, one for subcase 1 and one for subcase 5, using the default parameter values. The velocity of the first
rotational component of grid point 3 will be plotted on the upper half frame, and that of grid point 5 will be
plotted on the lower half frame. Tabular printer output will also be generated for both curves.
Example 3:
OUTPUT (XYPLOT)
CSCALE = 1.8
YDIVISIONS = 20
XDIVISIONS = 10
SGRID LINES = YES
YGRID LINES = YES
XYPLOT DISP 2,5/10(T1),10(T3)
BEGIN BULK
Main Index
728 MSC Nastran Quick Reference Guide
Generate X-Y Plots for a Plotter
This sequence causes two whole frame plots to be generated, one for subcase 2 and one for subcase 5. Each
plot contains the T1 and T3 displacement component for grid point 10. The default parameters will be
modified to include grid lines in both the x-direction and y-direction, with 10 spaces in the x-direction and
20 spaces in the y-direction. The plot will be generated for the NASTRAN plotter on file .plt.
Example 4
OUTPUT (XYPLOT)
CSCALE = 1.8
XAXIS = YES
YAXIS = YES
XPAPER = 40.
YPAPER = 20.
XYPLOT STRESS 3/ 15(2)/ 21(7)
OUTPUT (PLOT)
This sequence causes two whole frame plots to be generated using the results from subcase 3. The first plot
is the response of the axial stress for rod element number 15. The second plot is the response of the major
principal stress at Z1 for CTRIA3 element number 21. The default parameters will be modified to include
the x-axis and y-axis drawn through the origin. Each plot will be initially scaled to fit on 40 x 20 inch paper.
The plots will be generated for the NASPLT postprocessor and NASTRAN file .plt2 which must be defined.
NASPLT will redefine the plot to 14 x 7-inch paper (with default options).
Example 5
OUTPUT (XYPLOT)
CURVELINESYMBOL = -1
XYPLOT XYPAPLOT VG / 1(G,F) 2(G,F) 3(G,F) 4(G,F)
OUTPUT (PLOT)
This sequence is an example of plotting in a flutter analysis for which a split frame plot is made; the upper
half is V-g and the lower half is V-f. Data from the first four loops will be plotted. Distinct symbols are used
for data from each loop, and no lines are drawn between points (since the flutter analyst must sometimes
exercise judgement about which points should be connected). The plots will also be printed in the normal
output. These plots will not have all the features of the external plots, but can be very useful in getting a quick
picture of the curves.
Example 5
XTITLE=EXCITATION FREQUENCY FROM 2.5 TO 250 HERTZ SC 200
YTITLE=FLUID MODE PF AT FLUID POINT 204 FOR NATURAL MODE 2
XYPLOT,XYPEAK FMPF(2) MODE 200/204
Example 6
YTITLE=EXCITATION FREQUENCY FROM 2.5 TO 250 HERTZ
YTITLE=PSD MPF FOR FLUID GRID 204 FOR NATURAL MODE 2
XYPLOT,XYPEAK FMPF(2) PSDF /204
Example 7
XYPLOT CSIG PSDF / 4 (2003)
Main Index
CHAPTER 5 729
Generate X-Y Plots for a Plotter
This is an example of plotting Composite Stress value of stress
quantity given by Item Code 3 for layer with ID 2 of element with ID
4.
This can also be equivalently written as (see Remark 9 for
explanation)
XYPLOT CSIG PSDF / 4 (-2,3)
Describers Meaning
yvtype Type of y-value to be plotted: (Character).
ACCE Acceleration in the physical set.
BOUT Slideline contact output.
DISP Displacement in the physical set.
ELFORCE Element force.
ENTHALPY Enthalpy in the physical set.
FLUX Element heat flux.
FMPF Fluid mode participation factors. See Remark 8.
(mode_id or
frequency_id)
GMPF Panel grid mode participation factors. See Remark 8.
(mode_id or
frequency_id,
panel_name,
panel_grid_id)
HDOT Rate of change of enthalpy in the physical set.
MPCF Multipoint force of constraint.
LMPF Load mode participation factors. See Remark 8.
NONLINEAR Nonlinear applied load.
OLOAD Applied load.
PMPF Panel mode participation factors. See Remark 8.
(mode_id or
frequency_id,
panel_name)
PRESSURE Pressure of fluid-structure body.
SACCE Acceleration in the solution set.
SDISP Displacement in the solution set.
SMPF Structural mode participation factors. See Remark 8.
(mode_id or
frequency_id)
SPCF Single-point force of constraint.
STEMP Temperature in the solution set.
Main Index
730 MSC Nastran Quick Reference Guide
Generate X-Y Plots for a Plotter
Describers Meaning
STRAIN Element strain.
STRESS Element stress.
SVELO Velocity in the solution set.
TEMP Temperature in the physical set.
VECTOR Displacement in the physical set.
VELO Velocity in the physical set.
VG Flutter analysis.
CSIG Composite Stress
CEPS Composite Strain
CFAI Composite Failure Index
CSRS Composite Strength Ratio
ptype Plot type defining the meaning of i1, i2, ... etc., idi, itemui, and itemli (Character,
Default=“RESPONSE”).
AUTO Autocorrelation function on whole frame curves only.
FREQ Frequency—for given excitation frequency plot mode
participation versus natural frequency—Oxx2E tables—
point plot only. See Remark 8.
MODE Mode - for given fluid mode plot mode participation versus
excitation frequency - Oxx2M tables.
PSDF Power spectral density function on whole frame curves only.
RESPONSE Time or frequency in SORT2 format, or grid point
identification numbers in SORT1 format (Default) .
SPECTRAL Response spectrum on whole frame curves only.
i1, i2,... Subcase identification numbers for ptype=RESPONSE. The list must be specified
in ascending order. For ptype=SPECTRAL, the subcase refers to the RECNO in
the DTI,SPSEL Bulk Data entry. The list is ignored for ptype=AUTO and PSDF
(Integer > 0, Default is all subcases).
Main Index
CHAPTER 5 731
Generate X-Y Plots for a Plotter
Describers Meaning
idij Element, grid, scalar, or extra point identification number for y-value for frame i.
For yvtype=VG, idij refers to the loop count of a flutter analysis (Integer > 0).
itemuij, Item code for y-value. itemuij is for upper half or whole itemlij curves on frame i,
and itemlij is for lower half curves only on frame i. If itemlij is not specified, then
whole frame curves will be plotted with itemuij. itemlij is ignored for
ptype=“AUTO”, “PSDF”, and “SPECTRAL” (Character or Integer > 0).
For elements, the code represents a component of the element stress, strain, or force
and is described in Table 7-1 and Table 7-5 of the Guide. For ptype=“AUTO”and
“PSDF”, the complex stress or strain item codes need to be used. Since the output
quantities are real, you can use either the real or the imaginary item code. Both will
give the same result.
For grid points and pty=“RESPONSE”, the code is one of the mnemonics T1, T2,
T3, R1, R2, R3, T1RM, T2RM, T3RM, R1RM, R2RM, R3RM, T1IP, T2IP,
T3IP, R1IP, R2IP, or R3IP, where Ti stands for the i-th translational component, Ri
stands for the i-th rotational component, RM means real or magnitude, and IP
means imaginary or phase. For scalar or extra points, or heat transfer analysis, use
T1, T1RM, or T1IP. The output format of results in PCH file is dictated by the
case control request for DISP, STRESS. For example for SOL111:
DISP (PLOT, phase, SORT2) = 1
OUTPUT (XYOUT)
XYPUNCH DISP RESP /3 (T3RM)
This will punch results in PCH file in Mag/phase format. If the DISP command is
missing results will shift to Real/Imaginary the default format for SOL111
displacement.
For grid points and ptype=“AUTO” or “PSDF”, the code is one of the mnemonics
T1, T2, T3, R1, R2, R3. For scalar or extra points, use T1.
For yvtype=VG, itemui and/or itemli can be “F” for frequency or “G” for damping.
Remarks:
1. Multiple XYPLOT, XYPUNCH, XYPRINT, XYPEAK, and/or XYPAPLOT commands may be
specified in the OUTPUT(XYPLOT) section.
2. Solution set requests are more efficient, because the time-consuming recovery of the dependent
displacements can be avoided.
3. The item codes also appear in printed summaries as “CURVE ID” for grid points as well as element
data.
Main Index
732 MSC Nastran Quick Reference Guide
Generate X-Y Plots for a Plotter
4. The information after each slash ( / ) specifies the curve(s) that are to be plotted on the same frame.
The describer idij identifies the grid point j or element j associated with the frame number i. All plot
requests on one command are sorted on idij to improve the efficiency of the plotting process. Symbols
are assigned in order by idij.
5. If any of the item codes, itemlij or itemuij, are not specified; e.g., (8) or (5), the corresponding half
frame curve is not plotted. If both the comma ( , ) and itemlij not specified; e.g., (8), then whole frame
curves will be plotted. Also, for any single frame, the specifications of “(itemuij,itemlij)” must be
consistently half frame (upper and/or lower) or whole frame. For example on half frame curves, if
iteml11 and the comma is not specified then either iteml12 or itemu12 must not be specified and on
whole frame curves, the commas, iteml11, and iteml12 must not be specified. In other words, the
curves on each plot frame must be all whole or half (upper and/or lower).
6. The XYPLOT command may be continued on the next line as long as “XYPLOT yvtype ptype [ i1,
i2, i3,... ] /” is specified on the first line.
7. Specifying a nonexistent grid point may cause the program to exit in the XYTRAN module and
missing plots to occur.
8. mode_id is used for natural frequency selection of Oxx2m participation versus excitation frequency
output.
frequency_id is used for excitation frequency selection of Oxx2E participation versus natural
frequency output. frequency_id is an integer value; e.g., (2) would represent the second frequency
calculated.
9. For yvtype = CSIG, CEPS, CFAI and CSRS, we can have (itemuij, itemlij) or (itemuij) formats. For
the (itemuij, itemlij) format, itemuij will be a negative integer and its absolute value indicates the Ply
ID; itemlij indicates the composite stress item code. For the (itemuij) format, itemuij will be an
integer I = PLYID*1000 + ITEM_CODE.
10. Printout in the f06 file coming from X-Y plot commands is not supported by the POST TOCASE
command.
Main Index
CHAPTER 5 733
Generate Table of X-Y Pairs for a Printer
XYPRINT Generate Table of X-Y Pairs for a Printer
Generates tabular printer output of the X-Y pairs.
See XYPLOT for format, describers, and additional remarks.
Main Index
734 MSC Nastran Quick Reference Guide
Generate Table of X-Y Pairs for the PUNCH File
XYPUNCH Generate Table of X-Y Pairs for the PUNCH File
Generates tabular punch output of the X-Y pairs. Same as XYPRINT except the output is written to the
PUNCH file.
See XYPLOT for format, describers, and additional remarks.
Main Index
CHAPTER 5 735
Print Values on X-Axis Tic Marks
XVALUE PRINT SKIP Print Values on X-Axis Tic Marks
Specifies how often to print the x-values alongside the x-axis tic marks.
Format:
XVALUE PRINT SKIP xvps
Example:
XVAL 5
Describer Meaning
xvps Number of tic marks to be skipped between labeled tic marks with their
corresponding values (Integer > 0).
Remark:
1. XVALUE applies to all curves.
Main Index
736 MSC Nastran Quick Reference Guide
Y Axis Plot Control
YAXIS Y Axis Plot Control
Controls the plotting of the y-axis on all curves.
Format:
YAXIS YES
NO
Describers Meaning
YES Plot the y-axis.
NO Do not plot the y-axis (Default).
Main Index
CHAPTER 5 737
Tic Spacing on Y-Axis
YBDIVISIONS Tic Spacing on Y-Axis
Specifies spacing of tic marks on the y-axis for lower half frame curves only.
Format:
YBDIVISIONS ybd
Example:
YBDI 10
Describer Meaning
ybd Number of spaces between tic marks on y-axis (Integer > 0; Default = 5).
Remarks:
1. YBDIVISIONS applies to lower half frame curves only.
2. YBDIVISIONS is ignored for a logarithmic y-axis.
Main Index
738 MSC Nastran Quick Reference Guide
Location of Y Axis on X Axis
YBINTERCEPT Location of Y Axis on X Axis
Specifies the location of the y-axis on the x-axis for lower half frame curves only.
Format:
YBINTERCEPT ybi
Example:
YBINT 50
Describer Meaning
ybi Location of y-axis on the x-axis (Real; Default = 0.0).
Remark:
1. YBINTERCEPT applies to lower half frame curves only.
Main Index
CHAPTER 5 739
Plot Y Axis Grid Lines
YBGRID LINES Plot Y Axis Grid Lines
Controls the drawing of the grid lines parallel to the y-axis at the x-axis tic marks on lower half frame curves
only.
Format:
YBGRID LINES YES
NO
Describers Meaning
YES Plot the y-axis grid lines.
NO Do not plot the y-axis grid lines (Default).
Remarks:
1. YBGRID applies to lower half frame curves only.
2. See related command XBGRID LINES
Main Index
740 MSC Nastran Quick Reference Guide
Logarithmic or Linear Y Axis
YBLOG Logarithmic or Linear Y Axis
Selects logarithmic or linear y-axis for lower half frame curves only.
Format:
YBLOG YES
NO
Describers Meaning
YES Plot a logarithmic y-axis.
NO Plot a linear y-axis (Default).
Remarks:
1. YBLOG applies to lower half frame curves only.
2. See Remark 2 under XLOG.
Main Index
CHAPTER 5 741
Maximum Y Axis Value
YBMAX Maximum Y Axis Value
Specifies the maximum value on the y-axis for lower half frame curves only.
Format:
YBMAX ymax
Example:
YBMAX 100
Describer Meaning
ymax Maximum value on the y-axis (Real).
Remarks:
1. YBMAX applies to lower half frame curves only.
2. If YBMAX is not specified, then the maximum value is set to the highest value of y.
3. See related command YBMIN.
Main Index
742 MSC Nastran Quick Reference Guide
Minimum Y Axis Value
YBMIN Minimum Y Axis Value
Specifies the minimum value on the y-axis for lower half frame curves only.
Format:
YBMIN ymin
Example:
YBMIN 100
Describer Meaning
ymin Minimum value on the y-axis (Real).
Remarks:
1. YBMIN applies to lower half frame curves only.
2. If YBMIN is not specified then the minimum value is set to the lowest value of y.
3. See related command YBMAX.
Main Index
CHAPTER 5 743
Y-Axis Title
YBTITLE Y-Axis Title
Defines a character string that will appear along the y-axis for lower half frame curves only.
Format:
YBTITLE ytit
Example:
YBTIT RIGHT WING LOADS - CASE 3
Describer Meaning
ytit Any character string (Character; Default= Blank).
Remarks:
1. YBTITLE may not be continued to the next command line.
2. YBTITLE applies to lower half frame curves only.
Main Index
744 MSC Nastran Quick Reference Guide
Print Values on Y Axis Tic Marks
YBVALUE PRINT SKIP Print Values on Y Axis Tic Marks
Specifies how often to print the y-values alongside the y-axis tic marks applies on lower half frame curves only.
Format:
YBVALUE PRINT SKIP yvps
Example:
YBVAL 5
Describer Meaning
yvps Number of tic marks to be skipped between labeled tic marks with their
corresponding values (Integer > 0).
Remark:
1. YBVALUE applies to lower half frame curves only.
Main Index
CHAPTER 5 745
Tic Spacing on Y Axis
YDIVISIONS Tic Spacing on Y Axis
Specifies spacing of tic marks on the y-axis for whole frame curves only.
Format:
YDIVISIONS yd
Example:
YDIV 10
Describer Meaning
yd Number of spaces between tic marks on y-axis (Integer> 0; Default=5).
Remarks:
1. YDIVISIONS applies to whole frame curves only and to the commands: LEFT TICS, RIGHT
TICS, and XINTERCEPT.
2. YDIVISIONS is ignored for a logarithmic y-axis.
Main Index
746 MSC Nastran Quick Reference Guide
Location of Y Axis on X Axis
YINTERCEPT Location of Y Axis on X Axis
Specifies the location of the y-axis on the x-axis for whole frame curves only.
Format:
YINTERCEPT yi
Example:
YINT 50
Describer Meaning
yi Location of y-axis on the x-axis. (Real; Default = 0.0)
Remark:
1. YINTERCEPT applies to lower half frame curves only.
Main Index
CHAPTER 5 747
Plot Y Axis Grid Lines
YGRID LINES Plot Y Axis Grid Lines
Controls the drawing of the grid lines parallel to the y-axis at the x-axis tic marks on whole frame curves only.
Format:
YGRID LINES YES
NO
Describers Meaning
YES Plot the y-axis grid lines.
NO Do not plot the y-axis grid lines (Default).
Remarks:
1. YGRID applies to whole frame curves only.
2. See related command XGRID LINES
Main Index
748 MSC Nastran Quick Reference Guide
Logarithmic or Linear Y Axis
YLOG Logarithmic or Linear Y Axis
Selects logarithmic or linear y-axis for whole frame curves only.
Format:
YLOG YES
NO
Describers Meaning
YES Plot a logarithmic y-axis.
NO Plot a linear y-axis (Default).
Remarks:
1. YLOG applies to whole frame curves only.
2. See Remark 2 under XLOG.
Main Index
CHAPTER 5 749
Maximum Y Axis Value
YMAX Maximum Y Axis Value
Specifies the maximum value on the y-axis.
Format:
YMAX ymax
Example:
YMAX 100
Describer Meaning
ymax Maximum value on the y-axis (Real).
Remarks:
1. If YMAX is not specified, then the maximum value is set to the highest value of y.
2. See related command YMIN.
Main Index
750 MSC Nastran Quick Reference Guide
Minimum Y Axis Value
YMIN Minimum Y Axis Value
Specifies the minimum value on the y-axis.
Format:
YMIN ymin
Example:
YMIN 100
Describer Meaning
ymin Minimum value on the y-axis (Real).
Remarks:
1. YMIN applies to all curves.
2. If YMIN is not specified, then the minimum value is set to the lowest value of y.
3. See related command YMAX.
Main Index
CHAPTER 5 751
Paper Size in Y-Direction
YPAPER Paper Size in Y-Direction
Defines the size of the paper in y-direction.
Format:
YPAPER ysize
Example:
YPAP 10
Describer Meaning
ysize Size of paper in y-direction and in inches (Real; Default = 20.0).
Remarks:
1. The default paper size is 20 by 20 inches.
2. See related command XPAPER.
Main Index
752 MSC Nastran Quick Reference Guide
Y Axis Plot Control
YTAXIS Y Axis Plot Control
Controls the plotting of the y-axis on upper half frame curves only.
Format:
YTAXIS YES
NO
Describers Meaning
YES Plot the x-axis.
NO Do not plot the x-axis (Default).
Remark:
1. YTAXIS applies to upper half frame curves only.
Main Index
CHAPTER 5 753
The Spacing on Y Axis
YTDIVISIONS The Spacing on Y Axis
Specifies spacing of tic marks on the y-axis for upper half frame curves only.
Format:
YTDIVISIONS ytd
Example:
YTDI 10
Describer Meaning
ytd Number of spaces between tic marks on y-axis (Integer > 0; Default = 5).
Remarks:
1. YTDIVISIONS applies to upper half frame curves only.
2. YTDIVISIONS is ignored for a logarithmic y-axis.
Main Index
754 MSC Nastran Quick Reference Guide
Plot Y Axis Grid Lines
YTGRID LINES Plot Y Axis Grid Lines
Controls the drawing of the grid lines parallel to the y-axis at the x-axis tic marks on upper half frame curves
only.
Format:
TYGRID LINES YES
NO
Describers Meaning
YES Plot the y-axis grid lines.
NO Do not plot the y-axis grid lines (Default).
Remarks:
1. YTGRID applies to upper half frame curves only.
2. See related command XTGRID LINES
Main Index
CHAPTER 5 755
Location of Y Axis on X Axis
YTINTERCEPT Location of Y Axis on X Axis
Specifies the location of the y-axis on the x-axis for upper half frame curves only.
Format:
YTINTERCEPT yti
Example:
YTINT 50
Describer Meaning
yti Location of y-axis on the x-axis (Real; Default= 0.0).
Remark:
1. YTINTERCEPT applies to upper half frame curves only.
Main Index
756 MSC Nastran Quick Reference Guide
Y Axis Title
YTITLE Y Axis Title
Defines a character string that will appear along the y-axis for whole frame curves only.
Format:
YTITLE ytit
Example:
YTIT RIGHT WING LOADS - CASE 3
Describer Meaning
ytit Any character string (Character; Default = Blank).
Remarks:
1. YTITLE may not be continued to the next command line.
2. YTITLE applies to whole frame curves only.
Main Index
CHAPTER 5 757
Logarithmic or Linear Y Axis
YTLOG Logarithmic or Linear Y Axis
Selects logarithmic or linear y-axis for upper half frame curves only.
Format:
YT(LOG) YES
NO
Describers Meaning
YES Plot a logarithmic y-axis.
NO Plot a linear y-axis (Default).
Remarks:
1. YTLOG applies to upper half frame curves only.
2. See Remark 2 under XLOG.
Main Index
758 MSC Nastran Quick Reference Guide
Maximum Y Axis Value
YTMAX Maximum Y Axis Value
Specifies the maximum value on the y-axis for upper half frame curves only.
Format:
YTMAX ymax
Example:
YTMAX 100
Describer Meaning
ymax Maximum value on the y-axis (Real).
Remarks:
1. YTMAX applies to upper half frame curves only.
2. If YTMAX is not specified, then the maximum value is set to the highest value of y.
3. See related command YTMIN.
Main Index
CHAPTER 5 759
Minimum Y Axis Value
YTMIN Minimum Y Axis Value
Specifies the minimum value on the y-axis for upper half frame curves only.
Format:
YTMIN ymin
Example:
YTMIN 100
Describer Meaning
ymin Minimum value on the y-axis (Real).
Remarks:
1. YTMIN applies to upper half frame curves only.
2. If YTMIN is not specified then the minimum value is set to the lowest value of y.
3. See related command YTMAX.
Main Index
760 MSC Nastran Quick Reference Guide
Y-Axis Title
YTTITLE Y-Axis Title
Defines a character string that will appear along the y-axis for upper half frame curves only.
Format:
YTTITLE ytit
Example:
YTTIT RIGHT WING LOADS - CASE 3
Describer Meaning
ytit Any character string (Character; Default = Blank).
Remarks:
1. YTTITLE may not be continued to the next command line.
2. YTTITLE applies to upper half frame curves only.
Main Index
CHAPTER 5 761
Print Values on Y Axis Tic Marks
YTVALUE PRINT SKIP Print Values on Y Axis Tic Marks
Specifies how often to print the y-values alongside the y-axis tic marks applies on upper half frame curves only.
Format:
YTVALUE PRINT SKIP yvps
Example:
YTVAL 5
Describer Meaning
yvps Number of tic marks to be skipped between labeled tic marks with their
corresponding values (Integer > 0).
Remark:
1. YTVALUE applies to upper half frame curves only.
Main Index
762 MSC Nastran Quick Reference Guide
Print Values on Y Axis Tic Marks
YVALUE PRINT SKIP Print Values on Y Axis Tic Marks
Specifies how often to print the y-values alongside the y-axis tic marks applies on whole frame curves only.
Format:
YVALUE PRINT SKIP yvps
Example:
YVAL 5
Describer Meaning
yvps Number of tic marks to be skipped between labeled tic marks with their
corresponding values (Integer > 0).
Remark:
1. YVALUE applies to whole frame curves only.
Main Index
CHAPTER 5 763
OUTPUT(POST) Commands
OUTPUT(POST) Commands
SURFACE Surface Definition
Defines a surface for the calculation of grid point stresses, strains, or mesh stress discontinuities.
Format:
ALL
SURFACE id SET sid, FIBRE Z1
Z2
MID
ELEMENT X1 R
X1
SYSTEM BASIC AXIS X2 NORMAL M
X2
CORD cid X3 X3
TOPOLOGICAL TOLERANCE THETA
GEOMETRIC
BRANCH MESSAGE BREAK
NOMESSAGE NOBREAK
Example:
CEND
LOAD = 100
STRESS = ALL
SET 98 = 10
GPSTRESS = 98
OUTPUT(POST)
SET 9 = 5, 6, 8, 9
SURFACE 10 SET 9 NORMAL X3
BEGIN BULK
Describer Meaning
id Surface identification number (Required).
SET References a SET command that defines the elements in the surface (required).
Either form of the SET command may be used.
Main Index
764 MSC Nastran Quick Reference Guide
Surface Definition
Describer Meaning
sid Set identification number.
FIBRE Specifies the fiber location at which stresses will be calculated.
ALL Requests output at all fiber locations; i.e., z=Z1, Z2, and MID.
Z1 Requests output z = Z1 only.
Z2 Requests output z = Z2 only.
MID Requests output z = (Z1+Z2)/2 only.
SYSTEM Specifies the coordinate system to be used as the output coordinate system.
ELEMENT Specifies the element coordinate system for output.
CORD cid Specifies the coordinate system defined on a CORDij Bulk Data entry for output.
BASIC Specifies the basic coordinate system for output.
AXIS Specifies the axis of the coordinate system to be used as the x output axis and the local
x-axis when geometric interpolation is used.
X1, X2, X3 Specifies the direction of the axis or the normal. X, Y, and Z may be substituted for
X1, X2, and X3, respectively.
NORMAL Specifies the reference direction for positive fiber and shear stress output, but has no
effect when ELEMENT is specified.
M Specifies the reverse of the direction given by R, X1, X2, or X3 and must be entered
as MR, MX1, MX2, or MX3 with no space between the M and the following letter.
R Specifies the radius vector from the origin of reference coordinate system to the grid
point.
TOPOLOGICAL Specifies the method to calculate the average grid point stress or strain. The default
GEOMETRIC is TOPOLOGICAL.
theta Specifies the interelement slope difference tolerance (in degrees) to detect stress
discontinuity between elements (not used with TOPOLOGICAL) (Real; Default =
0.0).
BRANCH Selects whether multiple element intersections (BREAK/NOBREAK) are to be
treated as discontinuities, and if warning messages (MESSAGE/NOMESSAGE) are
to be issued.
BREAK Multiple element intersections are (or are not) to be treated as stress discontinuities.
NOBREAK
MESSAGE A warning message will (or will not) be issued when multiple element intersections
NOMESSAGE are encountered.
Remarks:
1. SURFACE commands must be specified after OUTPUT(POST).
Main Index
CHAPTER 5 765
Surface Definition
2. The surface identification number must be referenced on a SET command appearing before
OUTPUT(POST). The SET identification number may then be referenced on GPSTRESS,
GPSTRAIN, STRFIELD, ELSDCON, and GPSDCON commands. The sid on the surface entry
must reference a SET defined after OUTPUT(POST).
3. The surface normal is also used in the definition of the local reference surface for geometric
interpolation. Two options are available. In the first option, the radius vector (R) from the origin of
the reference coordinate system to the grid point is used. In the second option, one axis (X1, X2, or
X3) of the coordinate system is used. The direction can be reversed using the modification parameter
M. The positive side of an element is defined as a side from which the NORMAL direction emerges,
rather than the side determined by the connection specified on the element connection entries.
4. When the parameter ELEMENT is present, the element stresses or strains are used unmodified
(defaults to output stresses in output system). The CORD keyword references a CORDij Bulk Data
entry with coordinate system identification number cid.
5. When theta = 0, no testing is made. When theta is negative, grid point stresses will be calculated for
each element connected to an exception point; otherwise, the best estimation of the grid point stress
will be output.
6. BREAK is the default if theta is nonzero.
7. For all elements defined in SET 9 of the preceding example,
• All fiber locations are output;
• The basic output system is used;
• The x-axis is x-axis of the basic system;
• The surface normal direction point is z-axis of the basic system;
• The topological interpolation method is used;
• No tolerance test is made; and
• No branch test is made.
The example illustrates a good choice for regular two-dimensional problems in the x-y plane.
Main Index
766 MSC Nastran Quick Reference Guide
Volume Definition
VOLUME Volume Definition
Defines a volume for the calculation of grid point stresses, strains, or mesh stress discontinuities.
Format:
ELEMENT
VOLUME id SET sid, PRINCIPAL, DIRECT STRESS SYSTEM CORD cid
BASIC
Example:
VOLUME 21 SET 2
Describer Meaning
id Volume identification number.
sid Set identification number of a SET command that defines the elements in the
volume. Either form of the SET command may be used. The default is all
elements.
PRINCIPAL Requests principal stresses or strains, direction cosines, mean pressure, and von
Mises equivalent stresses or strains to be calculated. If neither PRINCIPAL nor
DIRECT is specified, then the default is to output both.
DIRECT Requests direct stress or strains, mean pressure stress, and von Mises equivalent
stress to be calculated. If neither PRINCIPAL nor DIRECT is specified, then the
default is to output both.
SYSTEM Used to specify the reference coordinate system used to define the output stress
orientation coordinate system.
ELEMENT Specifies the element coordinate system.
CORD cid Specifies the coordinate system defined on a CORDij entry.
BASIC Specifies the basic coordinate system.
Remarks:
1. VOLUME commands must be specified after OUTPUT(POST).
2. The volume identification number must be referenced on a SET command appearing after
OUTPUT(POST). The SET identification number may then be referenced on GPSTRESS,
GPSTRAIN, STRFIELD, ELSDCON, and GPSDCON Case Control commands.
3. If ELEMENT is specified, element stresses or strains are not transformed.
4. In the preceding example, for all elements in SET 2:
• Both PRINCIPAL and DIRECT stress are output.
Main Index
CHAPTER 5 767
Volume Definition
• The BASIC output system is used.
Main Index
768 MSC Nastran Quick Reference Guide
OUTPUT(PLOT) Commands
OUTPUT(PLOT) Commands
The PLOT command requests the generation of undeformed, deformed, or contour plots. All other
commands specify how the model will be plotted, type of projection, view angles, scales, etc. All commands
have default actions if not specified by the user. The FIND command may be used to calculate an optimal
SCALE, ORIGIN, and/or VANTAGE POINT to allow the construction of a plot in a user-specified region
of the paper or film. All the commands used in the generation of the various plots will be printed out as part
of the output, whether they are directly specified, defaulted or established using the FIND command.
Initialization of commands to default values occurs only once. Subsequently, these values remain until altered
by direct command input. The only exceptions are the view angles, scale factors, vantage points, and the
origins. Whenever the plotter or the method of projection is changed, the view angles are reset to the default
values, unless they are respecified by the user. In addition, the scale factors, vantage points, and the origin
must be respecified by the user.
The commands are listed here in a logical sequence; however, they need not be so specified. Any order may
be used, but if a command is specified more than once, the value or choice stated last will be used.
PLOTTER Selects format of plot file for interpretation by plotter postprocessor.
ORTHOGRAPHIC, etc. Selects orthographic projection.
PERSPECTIVE Selects perspective projection.
STEREOSCOPIC Selects stereoscopic projection.
AXES Assigns axes of the basic coordinate system to the observer’s coordinate
system.
VIEW Defines the angular relationship between the observer’s coordinate system
(r, s, and t axes specified on the AXES command) and the basic coordinate
system.
MAXIMUM DEFORM Defines the magnification of the maximum displacement.
SCALE Defines reduction, as a scale factor, of the model’s dimensions so that the
model fits on a plot frame.
DISTORTION Specifies the distortion scale factors of axes in the basic coordinate system.
CSCALE Defines scale factor for characters in the plot frame.
ORIGIN Defines the origin of the plot frame with respect to the origin of the (r, s,
t) coordinate system defined on the AXES command.
VANTAGE POINT Defines the location of the observer with respect to the model in the (r, s,
t) coordinate system defined on the AXES command for perspective and
stereoscopic projections only.
PROJECTION Defines the separation, along the r-axis, between the observer and the
projection plane if not already specified on the VANTAGE POINT
command. Used by stereoscopic projections only.
OCULAR SEPARATION Defines the separation of the left and right eye vantage points along the
s-axis for stereoscopic projections.
CAMERA Specifies microfilm plotter options.
Main Index
CHAPTER 5 769
OUTPUT(PLOT) Commands
PAPER SIZE Defines the size and type of the paper.
PEN Generates a message on the printed output to inform the plotter operator
as to what size and color pen point to mount in the various pen holders.
PTITLE Defines a character string that will appear at the top of the plot frame on
the line below the sequence number.
SET Defines a set of elements and/or grid points to be plotted.
FIND Requests the plotter to optimally compute any of the parameters that can
be specified on the SCALE, ORIGIN i, and/or VANTAGE POINT
commands.
CONTOUR Specifies contour plot options for stress, displacement, or temperature.
PLOT Generates an undeformed plot or a deformed plot per subcase, mode
number, frequency, or time step. A contour plot may also be requested with
an undeformed or deformed plot.
Main Index
770 MSC Nastran Quick Reference Guide
Orientation of Observer’s Coordinate System
AXES Orientation of Observer’s Coordinate System
Assigns axes of the basic coordinate system to the observer’s coordinate system.
Format:
AXES r s t SYMMETRIC
ANTISYMMETRIC
Example 1: View toward negative x-axis of model.
AXES MX, Y, MZ
Example 2: Mirror image of model.
AXES Y X Z
.
Describers Meaning
r,s,t Assigns axes of basic coordinate system to axes of observer’s coordinate
system (Default=X, Y, Z).
X X-direction of basic coordinate system (Default for r).
Y Y-direction of basic coordinate system (Default for s).
Z Z-direction of basic coordinate system (Default for t).
MX Negative X-direction of basic coordinate system.
MY Negative Y-direction of basic coordinate system.
MZ Negative Z-direction of basic coordinate system.
SYMMETRIC Specifies a symmetric orientation of the view. See Remark 5. (Default).
ANTISYMMETRIC Specifies an antisymmetric orientation of the view. See Remark 5.
Remarks:
1. If no AXES command is specified, then AXES X, Y, Z is the default.
2. The direction of view is in the negative r-direction; i.e., the projection plane is parallel to the s-t plane.
3. The VIEW command depends on the AXES command specification and defines the angular
relationship between observer’s coordinate system and the basic coordinate system.
4. The AXES command can be used to preposition the object in 90 increments in such a manner that
only rotations less than 90 are required by the VIEW command to obtain the desired orientation.
MX, MY, MZ can be used to define left-handed coordinate systems. Note that the default system is
right-handed.
Main Index
CHAPTER 5 771
Orientation of Observer’s Coordinate System
5. An undeformed or deformed plot of the symmetric portion of an object can be obtained by reversing
the sign of the axis that is normal to the plane of symmetry. In the case of multiple planes of
symmetry, the signs of all associated planes should be reversed. The ANTISYMMETRIC option
should be specified when a symmetric model is loaded in an unsymmetric manner. This will cause
the deformations to be plotted antisymmetrically with respect to the specified plane or planes. Since
the AXES command applies to all parts (SETs) of a single frame, symmetric and antisymmetric
combinations cannot be made with this command (see the symmetry option on the PLOT command
in this section).
6. To avoid a mirror image, ensure that the r, s, and t axes obey the right-hand rule.
Main Index
772 MSC Nastran Quick Reference Guide
Microfilm Plotter Options
CAMERA Microfilm Plotter Options
Specifies microfilm plotter options.
Format:
PAPER
CAMERA FILM BLANK FRAME n
BOTH
Example:
CAMERA FILM
Describers Meaning
FILM Requests 35 mm or 16 mm film and positive or negative images.
PAPER Requests positive prints.
BOTH Requests positive prints and 35 mm or 16 mm film.
Remarks:
1. If the CAMERA command is not specified, then CAMERA PAPER BLANK FRAMES 0 is assumed.
2. If FILM or BOTH is specified, then these options must be communicated to the plotter operator
through normal means of communications at the installation.
3. If FILM or BOTH are specified and if n is greater than 0 then n blank frames will be inserted between
plots. The plotter must be operated in the manual mode in order to have blank frames inserted
between positive prints. If blank frames are desired only on film, and not on paper, the plotter must
be operated in the automatic mode.
Main Index
CHAPTER 5 773
Contour Plot Options
CONTOUR Contour Plot Options
Specifies contour plot options for stress, displacement, or temperature.
Format:
Z1
CONTOUR component EVEN n Z2 COMMON
LIST a, b, ... MAX LOCAL
MID
Example:
CONTOUR MAGNIT LIST 2., 4., 6., 8., 10.
Describers Meaning
component Name of stress, displacement or temperature component (Character,
Default=“MAJPRIN”).
MAJPRIN Major principal stress. Not available for nonlinear elements
(Default).
MINPRIN Minor principal stress. Not available for nonlinear elements.
EQUIVAL von Mises stress. When STRESS(MAXS) is requested in the
Case Control Section, von Mises stress is used for plotting. For
nonlinear analysis, Mohr-Coulomb or Drucker-Prager stress
may also be plotted in conjunction with the MATS1
command.
XNORMAL X component of normal stress.
YNORMAL Y component of normal stress.
ZNORMAL Z component of normal stress.
XYSHEAR XY component of shear stress.
XZSHEAR XZ component of shear stress.
YZSHEAR YZ component of shear stress.
XDISP T1 component of displacement in global coordinate system.
YDISP T2 component of displacement in global coordinate system.
ZDISP T3 component of displacement in global coordinate system.
MAGNIT Magnitude of displacement or temperature.
EVEN n Number of contours (50 > Integer > 0, Default is EVEN 10).
LIST a, b, ... List of stresses, displacements or temperatures which define the contours (Real).
Main Index
774 MSC Nastran Quick Reference Guide
Contour Plot Options
Describers Meaning
Z1 Stresses at Z1 from neutral plane (Default).
Z2 Stresses at Z2 from neutral plane.
MAX Maximum of stress at Z1 and Z2.
MID Average of stress (membrane stress) at Z1 and Z2.
COMMON Plot stress contours in basic coordinate system (Default).
LOCAL Plot stress contours in element coordinate system. This is the coordinate system
used in printed output.
Remarks:
1. The CONTOUR command should be specified immediately before its associated PLOT command.
2. A STRESS command must appear in the Case Control Section for all elements included in a
CONTOUR request. If printed output is not desired, then STRESS(PLOT)=sid should be specified.
3. In linear analysis, stress contour plots are available for the following elements: CTRIA3, CQUAD4,
CSHEAR, and CTRlAX6. In nonlinear analysis, stress contour plots are available for CQUAD4 and
CTRlA3 elements. The Bulk Data element connection entries for all elements must list the grid
points in either clockwise or counterclockwise order. Mixing the order will result in meaningless or
confusing plots.
4. When selecting contour options, note that
• MAJPRIN, MINPRIN, EQUIVAL are the same in COMMON and LOCAL.
• ZNORMAL, XZSHEAR, YZSHEAR, if selected in LOCAL, will be changed to COMMON.
• CSHEAR elements only have the MAXSHEAR value.
5. The CTRIAX6 element stress contour plots are different in that they must be selected as COMMON.
Also, the following equivalences apply:
XNORMAL is radial
YNORMAL is azimuthal
ZNORMAL is axial
XYSHEAR is shear
XZSHEAR is maximum principal
YZSHEAR is von Mises
EQUIVAL is octahedra
Main Index
CHAPTER 5 775
Character Scale Factor
CSCALE Character Scale Factor
Defines scale factor for characters in the plot frame.
Format:
CSCALE cs
Example:
CSCA 2.0
Describer Meaning
cs Scale factor applied to characters in the plot frame (Default = .5).
Remarks:
1. CSCALE is used to control the spacing of characters when plots are made with the NASTRAN plotter
and postprocessed with the MSC/NASPLOT routine. For example, if the SCALE FACTOR on the
NASPLOT data command is 2.0, a value for cs of 0.5 will result in characters of default size (.07
inches) at the regular spacing. A value of 1.8 produces good spacing when using the postprocessing
plotter programs NASTPLT, TEKPLT, and NEUPS. On the other hand, to double the size of both
the plot and the characters, the SCALE FACTOR and the CSCALE FACTOR on the NASPLOT
data command should both be set equal to 2.0.
2. The CSCALE command must immediately precede the PLOTTER command. If a second CSCALE
command is specified, then a second PLOTTER command must also be specified.
Main Index
776 MSC Nastran Quick Reference Guide
Distortion Scale Factors
DISTORTION Distortion Scale Factors
Specifies the distortion scale factors of the axes in the basic coordinate system.
Format:
DISTORTION dx dy dz
Example:
DIST 0.5 1.0 1.0
Describers Meaning
dx Distortion scale factor of the basic coordinate system’s x-axis (Default=1.0).
dy Distortion scale factor of the basic coordinate system’s y-axis (Default=1.0).
dz Distortion scale factor of the basic coordinate system’s z-axis (Default=1.0).
Remarks:
1. If no DISTORTION command is specified, then no distortion is applied.
2. If DISTORTION is specified, then all three values for dx, dy, and dz must be specified even though
one or two will use the default.
3. The distortion factors are applied prior to any other scaling commands: SCALE, MAXIMUM
DEFORMATION, CSCALE, etc.
Main Index
CHAPTER 5 777
Automatic Calculation of Scale, Origin, and Vantage Point
FIND Automatic Calculation of Scale, Origin, and Vantage Point
Requests the plotter to optimally compute any of the parameters that can be specified on the SCALE,
ORIGIN i, and/or VANTAGE POINT commands.
Format:
FIND [ SCALE ORIGIN oid VANTAGE POINT SET setid ,
REGION { le be re te } ]
Example:
FIND SCALE ORIGIN 5 SET 2
Describers Meaning
oid Origin identification number (Integer>0).
setid Set identification number etc. (Integer>0).
le Fractional distance of left edge of plot region from the lower left corner of the
image area (Real, Default=0.0).
be Fractional distance of bottom edge of plot region from the lower left corner of the
image area (Real, Default=0.0).
re Fractional distance of right edge of plot region from the lower left corner of the
image area (Real, Default=1.0).
te Fractional distance of top edge of plot region from the lower left corner of the
image area (Real, Default=1.0).
Remarks:
1. The FIND command is recommended over the specification of SCALE, ORIGIN, and VANTAGE
POINT commands, and should be specified prior to its associated PLOT or CONTOUR command.
2. The FIND command requests the plotter to optimally compute any of the parameters that can be
specified on the SCALE, ORIGIN, and/or VANTAGE POINT commands and based on the
specification of the
• PLOTTER command;
• PROJECTION PLANE command;
• SET and REGION specifications on the FIND command;
• VIEW and/or AXES commands;
• MAXIMUM DEFORMATION command; and
• PAPER SIZE command. All of these commands must precede the associated FIND command.
3. The FIND command can be used to compute any or all of SCALE, ORIGIN, or VANTAGE
POINT as long as they have not been previously specified.
4. If SET is not specified, then the first defined SET will be used.
Main Index
778 MSC Nastran Quick Reference Guide
Automatic Calculation of Scale, Origin, and Vantage Point
5. If no options are specified on the FIND command, a SCALE and VANTAGE POINT are selected
and an ORIGIN is located, using the first defined SET, so that the plotter object is located within the
image area.
6. The plot region is defined as some fraction of the image area (image area = 0.0, 0.0, 1.0, 1.0 and first
quadrant = 0.5, 0.5, 1.0, 1.0). The image area is located inside the margins on the paper.
Main Index
CHAPTER 5 779
Length of Maximum Displacement
MAXIMUM DEFORM Length of Maximum Displacement
Defines the magnification of the maximum displacement. All other displacements are scaled accordingly.
Format:
MAXIMUM DEFORMATION d
Example:
Magnify the displacements such that the maximum displacement is equal to two units of length of the model.
MAXI DEFO 2.
Describer Meaning
d Specifies the length, in units of the model and not of the plot frame, to which
the maximum displacement is scaled. (Default=5% of the largest dimension of
the model represented by the elements in the SET specification on the PLOT
command.)
Remarks:
1. If no MAXIMUM DEFORMATION command is specified, then the previously described default
is assumed.
2. If you wish the FIND command to use the d value, a MAXIMUM DEFORMATION command
should precede the FIND command.
3. If you wish the plot deformation scaling to be different then the FIND scaling, a different
MAXIMUM DEFORMATION command can appear first before the PLOT command.
4. For nonlinear plotting, MAXIMUM DEFORMATION d and the MAXIMUM DEFORMATION
field on the PLOT command should have the same value.
Main Index
780 MSC Nastran Quick Reference Guide
Separation of the Vantage Points
OCULAR SEPARATION Separation of the Vantage Points
Defines the separation of the left and right eye vantage points along the s-axis for stereoscopic projections.
Format:
OCULAR SEPARATION os
Example:
OCULAR SEPARATION 2.0
Describer Meaning
os Separation, in inches, of the two vantage points along the s-axis (Real,
Default=2.756 inches).
Remark:
1. The default value is the separation used in the standard stereoscopic cameras and viewers (70 mm).
The default value is recommended.
Main Index
CHAPTER 5 781
Origin of Plot Frame
ORIGIN Origin of Plot Frame
Defines the origin of the plot frame with respect to the origin of the (r, s, t) coordinate system defined on the
AXES command.
Format:
ORIGIN oid u v
Example:
ORIG 3 -1. -2.
Describers Meaning
oid Origin identification number which may be specified after the ORIGIN describer
on the PLOT command (Integer > 0).
u Horizontal displacement of plot frame origin from the rst origin (Real, Default =
0.0).
v Vertical displacement of paper origin from the rst origin (Real, Default = 0.0).
Remarks:
1. In the transformation performed for any of the three projections, the origins of both the basic
coordinate system and the observer’s coordinate system are coincident. The ORIGIN command may
be used to locate the plot frame origin (lower left hand corner) from the rst origin. The units are
inches, and are not subject to the scaling of the plotted object.
2. The ORIGIN command is not recommended for general use. See the FIND command to have the
origin optimally located so as to place the plotted object in the center of the plot frame.
3. Ten origins may be specified at one time. However, any one can be redefined at any time. An eleventh
origin is also provided if more than ten origins are erroneously defined; i.e., only the last of these
surplus origins will be retained.
4. If a projection; e.g., ORTHOGRAPHIC, STEREOSCOPIC, or PERSPECTIVE, is changed in the
plot packet, or the PLOTTER command is changed, then all previously defined origins are deleted.
Main Index
782 MSC Nastran Quick Reference Guide
Type of Projection
ORTHOGRAPHIC, etc. Type of Projection
Selects type of projection.
Format:
ORTHOGRAPHIC
PERSPECTIVE
STEROSCOPIC
Describers Meaning
ORTHOGRAPHIC Selects orthographic projection (Default).
PERSPECTIVE Selects perspective projection.
STEREOSCOPIC Selects stereoscopic projection.
Remark:
1. If none of the preceding projections are specified, then ORTHOGRAPHIC is used.
Main Index
CHAPTER 5 783
Paper Dimensions
PAPER SIZE Paper Dimensions
Defines the size and type of the paper.
Format:
PAPER SIZE h X or BY v [ TYPE ptype ]
Example:
PAPER SIZE 10. BY 10.
Describers Meaning
h Horizontal size of paper in inches (Real, Default = 20.0).
v Vertical size of paper in inches (Real, Default= 20.0).
ptype Paper type (Character, Default = “VELLUM”).
Remarks:
1. The default paper size for the PLOTTER NAST is 20 by 20 inches which is converted to a 7 by 7
inch plot frame by the NASPLOT postprocessor.
2. PAPER SIZE can be specified along with the NASPLOT postprocessor to create rectangular plots.
For example, the command will result in a 14 by 7 inch plot frame if the default value of 1.0 is used
for the SCALE FACTOR on the NASPLOT command. The SCALE FACTOR on the NASPLOT
data command can be used to make larger plots having the shape defined with PAPER SIZE.
3. PAPER SIZE also affects the raster count for the NASTRAN plotter. The default raster count is 1000
for a paper size of 20 by 20. Doubling the paper size to 40 by 40 will double the raster count to 2000.
Main Index
784 MSC Nastran Quick Reference Guide
Pen Color and Size Assignments
PEN Pen Color and Size Assignments
Generates a message on the printed output which may be used to inform the plotter operator as to what size
and color pen point to mount in the various pen holders.
Format:
PEN pn [ COLOR cname ]
Example:
PEN 2 COLOR RED
Describers Meaning
pn Pen identification number (Integer> 0).
COLOR Flag indicating the next word is a color name.
cname Pen color (Character).
Remarks:
1. The actual number of pens available will depend on the plotter hardware configuration at each
installation.
2. The PEN command does not control the pen used in generating the plot. See the PEN describer on
the PLOT command.
3. The PEN command is optional and is not appropriate for microfilm plotters.
Main Index
CHAPTER 5 785
Selects Perspective Projection
PERSPECTIVE Selects Perspective Projection
See the description of the ORTHOGRAPHIC, etc..
Main Index
786 MSC Nastran Quick Reference Guide
Undeformed or Deformed Plot Request
PLOT Undeformed or Deformed Plot Request
Generates an undeformed plot of the model or a deformed plot for a subcase, mode number or time step.
Format:
PLOT analysis dtype CONTOUR i1, i2 THRU i3, i4, etc. RANGE f1, f2 ,
TIME t1, t2
PHASE LAG
MAXIMUM DEFORMATION d ,
MAGNITUDE
PEN
SET sid1 ORIGIN oid1 SYMMETRY w p SYMBOLS m ,n ,
ANTISYMMETRY DENSITY
LABEL label SHAPE VECTOR v , PRINT ,
OUTLINE
SHRINK t, o NORMALS ,
SET sid2 ORIGIN oid2] etc.
Examples:
See after Remarks Section.
Describers Meaning
analysis Type of analysis results (Character, default results in an undeformed plot
or undeformed underlay for contour plots).
STATIC Plot static deformations.
MODAL Plot mode shapes or eigenvectors.
CMODAL Plot complex mode shapes or eigenvectors.
TRANSIENT Plot transient solutions.
FREQUENCY Plot frequency solutions.
SENOMOVE Plot undeformed superelements in their original
position; i.e., ignore SELOC Bulk Data entry.
dtype Specifies plot quantity (Character, Default = “DEFORMATION”).
Main Index
CHAPTER 5 787
Undeformed or Deformed Plot Request
Describers Meaning
DEFORMATI Plot displacements or temperatures in the Z
ON direction (Default).
VELOCITY Plot velocities.
ACCELERATI Plot accelerations.
ON
CONTOUR Request for contour plot.
i1, i2,... Subcase identification numbers. See SHAPE and VECTOR for use of
“0" (underlay) command. See Remark 3. (Integer > 0, Default is all
subcases).
RANGE f1 f2 Specifies range of natural frequencies, eigenvalues, excitation
TIME t1,t2 frequencies, time steps, or load factors. Used to minimize the amount
of plotted data. See Remark 4. (Real).
PHASE LAG Specified phase lag, in degrees, for plotting complex quantities. See
Remark 5. (Real, Default = 0.0).
MAGNITUDE Requests magnitude of complex quantities.
MAXIMUM Specifies the magnification of the maximum displacement. See Remark
DEFORMATION d 6. (Real).
SET sid Set identification number which defines the set of elements or grid
points to be plotted (Default is first SET command).
ORIGIN oid Origin identification number (Default is first origin defined by the
ORIGIN or FIND command).
SYMMETRY w Request plot of the symmetric portion of the symmetrically or
ANTISYMMETRY w antisymmetrically loaded model. This symmetric portion will be
located in the space adjacent to the region originally defined by
ORIGIN oid, and will appear as a reflection of the antisymmetrically
deformed model about the plane whose normal is oriented parallel to
the coordinate direction w. See Remark 7. (Default is no action).
PEN p Specifies pen number that is used to generate the plot (Integer > 0).
DENSITY d Specifies line density scale factor for film plotters which is d times
heavier than a line density of 1 (Integer > 0).
Main Index
788 MSC Nastran Quick Reference Guide
Undeformed or Deformed Plot Request
Describers Meaning
SYMBOLS m[,n] All the grid points associated with the specified set will have symbol m
overprinted with symbol n printed at its location. If n is not specified,
only symbol m will be printed. See Remark 8.
m or n Symbol
0 none
1 X
2 *
3 +
4 -
5 .
6 ×
7 []
8 <>
9 /\
LABEL label Specifies labeling options at elements and grid points:
GRID All the grid points included in the specified set have
their identification number printed to the right of
the undeformed or deformed location (undeformed
location in the case of superimposed plots)
(Default).
ELEMENTS All the elements included in the specified set are
identified by the element identification number and
type at the center of each element (undeformed
location in the case of superimposed plots). See
Remarks 11. and 12.
BOTH Both GRID and ELEMENT options.
GSPC Label those degrees-of-freedom that are constrained
to zero through permanent single point constraints
on GRID and GRDSET Bulk Data entries, or are
constrained through SPC and SPC1 Bulk Data
entries. The label consists of the grid point ID
number and the constrained degrees-of-freedom.
EPID Label elements with their respective property
identification (PID) numbers. The label consists of
the standard element labels and element PID.
Main Index
CHAPTER 5 789
Undeformed or Deformed Plot Request
Describers Meaning
SHAPE All the elements included in the specified set are shown by connecting
the associated grid points in a predetermined manner. See Remark 9.
OUTLINE Only the outline of all the elements in the specified set is shown.
Elements not supported by contour plots are ignored. Outlines are
always drawn with PEN 1. See Remark 9.
VECTOR v A line will be plotted at the grid points of the set representing by length
and direction the deformation of the point. See Remark 10. Possible
values of v are:
X, Y, or Z Requesting individual components.
XY, XZ, or YZ Requesting two specified components.
XYZ Requesting all three components.
RXY, RXZ, or Requesting vector sum of two components.
RYZ
R Requesting total vector deformation.
N Used with any of the preceding combinations to
request no underlay shape be drawn.
PRINT List of the average stresses at the interior grid points in the set will be
printed for contour stress plots.
SHRINK t,o t is the ratio of the reduction to the original dimensions of all
two-dimensional elements except the CQUAD8 and CTRIA6 (0.0 < t
< 1.0) (Real, Default = 0.1 which results in a 10% reduction).
o is the ratio of the reduction in length to the original length for
one-dimensional elements. There is no default value for o. t must be
specified to shrink one-dimensional elements.
NORMALS Plot vector normal to CHBDYP and CHBDYG elements.
Remarks:
1. If PLOT is specified with no describers, then a picture of the undeformed model will be prepared
using the first defined set and the first defined origin.
2. Describers analysis through PHASE LAG must be specified in the order shown above.
3. The following should be noted when using subcase numbers for plotting eigenvectors.
a. If subcase numbers are specified, then the convention for displacement vectors is that the list of
subcases must refer to subcase IDs whenever the number of modes recovered is equal to or less
than the number of subcases defined. If the number of modes recovered is more than the subcases
defined, the plot request for those modes associated with the subcases must refer to subcase IDs.
After the mode associated with the last defined subcase, higher modes will be identified by
incrementing the last defined subcase ID by one for each such higher mode.
Main Index
790 MSC Nastran Quick Reference Guide
Undeformed or Deformed Plot Request
b. For the display of element quantities in contour plots, the automatic incrementing beyond the
last defined subcase does not occur. All subcase numbers to be plotted must be defined. A
MODES command in the Case Control Section may be used for this purpose.
c. In problems using cyclic symmetry solution sequences, the plot requests for segments of the model
must refer to the coded subcase identification numbers (see Theory in the MSC Nastran Reference
Guide). All eigenvectors recovered for the segment will be plotted. The RANGE option can be
used to select a subset of all eigenvectors for plotting without use of coded subcase IDs.
d. RANGE does not require the use of subcase numbers.
4. RANGE specifies the range of values using requested subcases for which plots will be prepared. If only
one number is input, it is used as the lower bound and the upper bound is set to the highest value
computed. Unless otherwise noted, the default range is all values computed.
a. In real eigenvalue analysis, the values are natural frequencies, in units of cycles per unit time.
b. In buckling analysis, the values are eigenvalues.
c. In frequency response, the values are excitation frequencies in units of cycles per unit time.
d. In transient response, the values are in units of time.
e. In static nonlinear analysis (SOLs 106 and 153), the values are load factors. The default range is
the highest load factor of each subcase.
f. In transient nonlinear analysis (SOLs 129 and 159), the values are in units of time. The default
range is the last time step for each subcase.
5. PHASE LAG is used in the equation:
u R cos – u I sin
where u R an u I are the real and imaginary parts of the response quantity, respectively. The printed
output for magnitude and phase uses the convention of a phase lead.
6. MAX DEFO is not recommended for general use. Each subcase is separately scaled according to its
own maximum if this item is absent. If d is omitted, the set will be scaled to the maximum within the
set being plotted.
7. w specifies the basic coordinates X, Y, or Z, or any combination thereof. This option allows the
plotting of symmetric and/or antisymmetric combinations, provided that an origin is selected for the
portion of the model defined in the Bulk Data Section that allows sufficient room for the complete
plot. This does not permit the combination of symmetric and antisymmetric subcases, as each plot
must represent a single subcase. In the case of a double reflection, the figure will appear as one
reflected about the plane whose normal is parallel to the first of the coordinates w, followed by a
reflection about the plane whose normal is oriented parallel to the second of the coordinates w. This
capability is primarily used in the plotting of models that are loaded in a symmetric or an
antisymmetric manner. The plane of symmetry must be one of the basic coordinate planes.
8. Grid points excluded from the set will not have a symbol. Grid points in an undeformed underlay
will be identified with symbol 2.
Main Index
CHAPTER 5 791
Undeformed or Deformed Plot Request
9. In order to get a deformed shape, either SHAPE or OUTLINE must be present in the PLOT
command. Both deformed and undeformed shapes or outlines may be specified. All the deformed
shapes relating to the subcases listed may be underlaid on each of their plots by including “0" with
the subcase string on the PLOT command. The undeformed plot will be drawn using PEN 1 or
DENSITY 1 and symbol 2 (if SYMBOLS is specified).
10. All plots requesting the VECTOR option will have an underlay generated of the undeformed shape
using the same sets, PEN 1 or DENSITY 1, and symbol 2 (if SYMBOLS is specified). If SHAPE and
VECTOR are specified, the underlay will depend on whether “0" is used along with the subcases with
DEFORMATION. It will be the deformed shape when not used, and will be both deformed and
undeformed shapes when it is used. The part of the vector at the grid point will be the tail when the
underlay is undeformed, and the head when it is deformed. If v=“N” then no shape will be drawn,
but other options such as SYMBOLS will still be valid.
11. Element type labels are: (Plot labels QH and TH indicate hyperelastic elements)
Element Plot Element Plot
Type Label Type Label
CAERO1 AE PLOTEL PL
CAXIF2 A2 CQUAD QH
CAXIF3 A3 CQUAD4 Q4 or QH
CAXIF4 A4 CQUAD8 Q8 or QH
CBAR BR CQUADR QR
CBEAM BM CQUADX QH
CBEND BD CROD RD
CBUSH BU CSHEAR SH
CONEAX CN CSLOT3 S3
CONROD CR CSLOT4 S4
CDUMI Di CTETRA TE
CFLUID2 F2 CTRIAX6 D1
CFLUID3 F3 CTRIA3 T3 or TH
CFLUID4 F4 CTRIA6 T6 or TH
CHBDYG HB CTRIAR TR
CHBDYP HB CTRIAX TH
CHEXA HA CTUBE TU
CPENTA HA CVISC VS
Main Index
792 MSC Nastran Quick Reference Guide
Undeformed or Deformed Plot Request
12. The heat transfer boundary condition elements CHBDYG and CHBDYP can be plotted for
undeformed plots. There are several types of CHBDYi elements, as follows:
Type No. of Primary Grid Points Normals Available
POINT 1 yes
LINE 2 yes
AREA3 3 yes
AREA4 4 yes
REV 2 no
ELCYL 2 no
TUBE 2 yes
FTUBE 2 yes
AREA6 6 yes
AREA6 8 yes
The secondary grid points are used for ambient conditions and are ignored by the plotter. Type
POINT must have a nonzero associated area (see AF on the associated PHBDY entry) and a defined
normal direction (see V1, V2, V3 on the CHBDYP entry) to be plotted. It is plotted as a hexagon
with approximately the correct area. Type LINE must have a nonzero width (see AF on the associated
PHBDY entry) and a defined normal in order to plot.
13. To assign PLOT command to superelements it requires an SEUPPLOT or a SEPLOT command.
Examples:
1. Undeformed SHAPE using first defined SET, first defined ORIGIN and PEN 1 (or DENSITY 1).
PLOT
2. Undeformed SHAPE using SET 3, ORIGIN 4, PEN 2 (or DENSITY 2) with each grid point of the
set having a + placed at its location, and its identification number printed adjacent to it.
PLOT SET 3 ORIGIN 4 PEN 2 SHAPE SYMBOLS 3 LABEL
3. Modal deformations as defined in subcase 5 using first defined SET, first defined ORIGIN, and PEN
1 (or DENSITY 1).
PLOT MODAL DEFORMATION 5 SHAPE
4. STATIC deformations as defined in subcases 3, 4, 5, and 8 deformed SHAPE; drawn with PEN 4,
using first defined SET and ORIGIN, underlaid with undeformed SHAPE drawn with PEN 1. This
command will cause four plots to be generated.
PLOT STATIC DEFORMATION 0, 3 THRU 5, 8 PEN 4, SHAPE
Main Index
CHAPTER 5 793
Undeformed or Deformed Plot Request
5. Deformations as defined in subcases 1, 2, 3, 4, and 5 undeformed underlay with PEN 1, consisting
of SET 2 at ORIGIN 3, SET 2 at ORIGIN 4 (with a < placed at each grid point location), and SET
35 at ORIGIN 4. Deformed data as follows: SHAPE using SET 2 at ORIGIN 3 (PEN 3) and SET
35 at ORIGIN 4 (PEN 4); 3 VECTORS (X, Y and Z) drawn at each grid point of SET 2 at ORIGIN
4 (PEN 4) (less any excluded grid points), with o placed at the end of each vector.
PLOT STATIC DEFORMATION 0 THRU 5,
SET 2 ORIGIN 3 PEN 3 SHAPE,
SET 2 ORIGIN 4 PEN 4 VECTORS XYZ SYMBOLS 0,
SET 35 SHAPE
6. Static deformations as defined in subcases 3 and 4, both halves of a problem solved by symmetry using
the X-Y principal plane as the plane of symmetry. SET 1 at ORIGIN 2 and SET 2 at ORIGIN 3,
with the deformed shape plotted using DENSITY 3 and the undeformed model plotted using
DENSITY 1. The deformations of the “opposite” half will be plotted to correspond to symmetric
loading. This command will cause two plots to be generated.
PLOT STATIC DEFORMATIONS 0, 3, 4,
SET 1 ORIGIN 2 DENSITY 3 SHAPE,
SET 1 SYMMETRY Z SHAPE,
SET 2 ORIGIN 3 SHAPE,
SET 2 SYMMETRY Z SHAPE
7. Transient deformations as defined in subcase 1 for time = 0.1 to time = 0.2, using SET 1 at ORIGIN
1. The undeformed SHAPE using PEN or DENSITY 1 with an * at each grid point location will be
drawn as an underlay for the resultant deformation vectors using PEN or DENSITY 2 with an <
typed at the end of each vector drawn. In addition, a plotted value of 2.0 will be used for the single
maximum deformation occurring on any of the plots produced. All other deformations on all other
plots will be scaled relative to this single maximum deformation. This command will cause a plot to
be generated for each output time step which lies between 0.1 and 0.2.
PLOT TRANSIENT DEFORMATION, TIME 0.1, 0.2,
MAXIMUM DEFORMATION 2.0, SET 1, ORIGIN 1, PEN 2, SYMBOLS 2,
VECTOR R
8. Contour plot of x-component of normal stress for elements in SET 2 in basic coordinate system at a
distance Z1 from neutral plane with 10 contour lines, an outline of elements in SET 2, and using
ORIGIN 4.
CONTOUR XNORMAL
PLOT CONTOUR, SET 2, ORIGIN 4, OUTLINE
Contour plot of magnitude of displacements at grid points associated with elements in SET 5 with 5
contours having values of 2., 4., 6., 8., 10., and an outline of the elements in SET 5 using
ORIGIN 4.
CONTOUR MAGNIT, LIST 2., 4., 6., 8., 10.
PLOT CONTOUR, SET 5, OUTLINE
9. Plot the imaginary part of the complex eigenvector in SET 1.
PLOT CMODAL DEFORMATION PHASE LAG 90. SET 1 VECTOR R
Main Index
794 MSC Nastran Quick Reference Guide
Plot File Format
PLOTTER Plot File Format
Selects format of plot file for interpretation by plotter postprocessor.
Format:
PLOTTER NAST
SC
Example:
PLOTTER NAST
Describers Meaning
NAST Specifies format suitable for Postscript plotters (Default).
SC Specifies Stromberg-Carlson microfilm plotter format.
Remark:
1. If no PLOTTER command is specified, then PLOTTER NAST is the default.
2. If “PLOTTER NAST” is specified (or taken by default) and if the format of the PLOT file has been
changed to formatted through the use of an ASSIGN statement, plot data will be generated in
PostScript mode directly instead of being generated in binary mode. PostScript plot control
information may be specified using the SYS= describer on the ASSIGN statement or by using the
SYSFIELD= command-line keyword, specifying the control information using the
PLOT(keyword=value,...) options. The valid keywords are the same as those that can be
specified for the PLOTPS or MSCPLOTPS utility programs except that the “begin”, “debug”,
“dump”, “end”, “format” and “output” keywords are not allowed.
Main Index
CHAPTER 5 795
Separation Between Projection Plane and Observer
PROJECTION Separation Between Projection Plane and Observer
Defines the separation along the r-axis, and between the observer and the projection plane, if not already
specified on the VANTAGE POINT command. Used by stereoscopic projections only.
Format:
PROJECTION PLANE SEPARATION do
Example:
PROJ PLAN SEPA 1.5
Describer Meaning
do Separation of the observer and the projection plane on the r-axis in model units.
The VANTAGE POINT command may also specify the separation (Real, Default
= 2.0).
Remarks:
1. The PROJECTION PLANE SEPARATION command is not recommended. The FIND command
is recommended because it automatically calculates the optimum separation.
2. A theoretical description of projection plane separation is contained in Plotting in the MSC Nastran
Reference Guide.
Main Index
796 MSC Nastran Quick Reference Guide
Plot Frame Title
PTITLE Plot Frame Title
Defines a character string that will appear at the top of the plot frame on the line below the sequence number.
Format:
PTITLE ptitle
Example:
PTITLE RIGHT WING -- LOAD CASE 3
Describer Meaning
ptitle Any character string (Character, Default= blank).
Remarks:
1. PTITLE may not be continued to the next command line.
2. Up to four lines of title information will be printed in the lower left-hand corner of each plot. The
text for the top three lines is taken from the TITLE, SUBTITLE, and LABEL commands in the Case
Control Section. (See the Case Control Commands for a description of the TITLE, SUBTITLE, and
LABEL commands). The text for the bottom line may be of two forms depending on the type plot
requested. One form contains the word UNDEFORMED SHAPE. The other form contains the type
of plot (statics, modal, etc.) subcase number, load set or mode number, frequency or eigenvalue or
time, and (for complex quantities) the phase lag or magnitude. The sequence number for each plot is
printed in the upper corners of each frame. The sequence number is determined by the relative
position of each PLOT execution command in the plot package. The information on the PTITLE
command will be printed on the line below the sequence number. The date and (for deformed plots)
the maximum deformation are also printed at the top of each frame.
Main Index
CHAPTER 5 797
Scale Factor
SCALE Scale Factor
Defines reduction, as a scale factor, of model’s dimensions so that model fits on a plot frame.
Format:
SCALE a [ b ]
Example:
SCALE 0.5
Describers Meaning
a Scale factor (Default=1.0).
b Ratio of model size/real object size for stereoscopic projection only.
Remarks:
1. The SCALE command is not recommended. The FIND command is recommended because it
automatically calculates the optimum scale factor.
2. For orthographic or perspective projections, a is the ratio of the plotted object, in inches, to the real
object in the units of model; i.e., one inch of paper equals one unit of model.
3. For stereoscopic projections, the stereoscopic effect is enhanced by first reducing the real object to a
smaller model according to b, and then applying a. The ratio of plotted/real object is then the product
of a and b.
4. If the NASTRAN general purpose plotter is used in combination with the PLOTPS postprocessing
routine, a scale factor can computed as follows:
20
a = p ------ K
7
where:
p = ratio of plot size to object size. For instance, if the model is 100 inches long and the plot
size is 7 inches, then
7
p = --------- = .007
100
20- = ratio of default PAPER SIZE to default PLOTPS frame size.
-----
7
K = SCALE value on PLOTPS command (Default=1.0). See Using the Utility Programs in the
MSC Nastran Installation and Operations Guide.
Main Index
798 MSC Nastran Quick Reference Guide
Superelement Plot Delimiter
SEPLOT Superelement Plot Delimiter
Assigns the subsequent PLOT or XYPLOT commands to one or more superelements.
Format:
SEPLOT seid1 [ seid2 ... ]
Examples:
SEPLOT 5
SEPLOT 0 3 7 200
Describer Meaning
seidi Superelement identification number (Integer > 0).
Remarks:
1. See also related command SEUPPLOT.
2. Any PLOT or XYPLOT commands appearing above all SEPLOT (or SEUPPLOT) commands will
apply in all SEPLOT (or SEUPPLOT) packets.
3. For multiple PLOT or XYPLOT commands, there should be a SEPLOT command with each PLOT.
For the special case where the PLOTs or XYPLOTs refer to the same superelements and use the same
FIND, a single SEPLOT followed by a single FIND may be placed above all commands.
Main Index
CHAPTER 5 799
Set Definition Under OUTPUT(PLOT)
SET Set Definition Under OUTPUT(PLOT)
Defines a set of elements or grid point numbers to be plotted.
The SET command specifies sets of elements or grid points, corresponding to portions of the model, which
may be referenced by PLOT and FIND commands. The SET command is required. Each set of elements
defines, by implication, a set of grid points connected by those elements. The set may be modified by deleting
some of its grid points. The elements are used for creating the plot itself and element labeling, while the grid
points are used for labeling, symbol printing, and drawing deformation vectors.
Format:
SET n = ALL ELEMENTS EXCEPT type1 type2 typej
GRID POINTS k1 k2 kj THRU kk BY incj
INCLUDE ELEMENTS type1 type2 typej
EXCLUDE GRID POINTS k1 k2 kj THRU kk BY incj
EXCEPT type1 typem typen
k1 km kn THRU ko BY incn
Examples:
1. SET 1 consists of elements 1, 5, 10, 11, 13, 14, 15, 20, 22, 24, and 26.
SET 1=INCLUDE 1, 5, 10 THRU 15 EXCEPT 12, INCLUDE 20 THRU 26 BY 2
2. SET 2 consists of all CTRIA3 and CQUAD4 elements except element 21.
SET 2=QUAD4 TRIA3 EXCEPT 21
3. SET 10 includes all CTRIAR elements plus elements 70 through 80.
SET 10 TRIAR INCLUDE ELEMENTS 70 THRU 80
4. SET 15 includes all elements from 15 to 20 and 26 to 100.
SET 15=15 THRU 100 EXCEPT 21 THRU 25
5. SET 2 includes all elements except CTETRA elements.
SET 2=ALL EXCEPT TETRA
Describer Meaning
n Sets identification number (0<Integer<999999).
ALL Selects all elements or grid points. See typei.
ELEMENTS Specifies that all identification numbers refer to elements.
GRID POINTS Specifies that all identification numbers refer to grid points.
Main Index
800 MSC Nastran Quick Reference Guide
Set Definition Under OUTPUT(PLOT)
Describer Meaning
INCLUDE Includes specified element or grid point identification numbers or elements in the
set.
EXCLUDE Excludes specified element or grid point identification numbers or element types in
the set.
EXCEPT Modifies a prior ALL, INCLUDE, or EXCLUDE specification.
typei Element types. The allowed element types are (Character):
Element typei on SET Element typei on SET
Type Command Type Command
CAXIF2 AXIF2 CQUAD QUAD
CAXIF3 AXIF3 CQUAD4 QUAD4
CAXIF4 AXIF4 CQUAD8 QUAD8
CBAR BAR CQUADR QUADR
CBEAM BEAM CQUADX QUADX
CBEND BEND CROD ROD
CBUSH BUSH CSHEAR SHEAR
CONEAX CONE CSLOT3 SLOT3
CONROD CONROD CSLOT4 SLOT4
CDUMi DUMi CTETRA TETRA
CFLUID2 FLUID2 CTRIAX6 TRIAX6
CFLUID3 FLUID3 CTRIA3 TRIA3
CFLUID4 FLUID4 CTRIA6 TRIA6
CHBDYG HBDY CTRIAR TRIAR
CHBDYP HBDY CTRIAX TRIAX
CHEXA HEXA CTUBE TUBE
CPENTA PENTA CVISC VISC
PLOTEL PLOTEL
THRU Specifies a range of identification numbers.
BY Specifies an increment for a THRU specification.
inci Increment for THRU range (Integer > 0).
Main Index
CHAPTER 5 801
Set Definition Under OUTPUT(PLOT)
Remarks:
1. This form of the SET command can only be specified after an OUTPUT(PLOT) delimiter.
2. The INCLUDE, EXCLUDE, and EXCEPT specifications may be specified more than once in the
same set. See previous examples.
3. Commas or spaces may be used as separators.
4. Not all of the identification numbers in a THRU range have to correspond to elements or grid points.
For example, elements 2, 4, 7, and 9 may be selected with 2 THRU 9, even if elements 3, 5, 6, and
8 do not exist. This is called an open set. Note that large open sets can cause higher computational
costs.
Main Index
802 MSC Nastran Quick Reference Guide
Superelement Plot Delimiter
SEUPPLOT Superelement Plot Delimiter
Assigns the subsequent PLOT or XYPLOT commands to a superelement and all of its upstream
superelements.
Format:
SEUPPLOT seid
Example:
SEUPPLOT 7
Describer Meaning
seid Superelement identification number (Integer > 0).
Remarks:
1. See also related command SEPLOT.
2. Any PLOT or XYPLOT commands appearing above all SEUPPLOT (or SEPLOT) commands will
apply in all SEUPPLOT (or SEPLOT) packets.
3. For multiple PLOT or XYPLOT commands, there should be a SEUPPLOT command with each
PLOT. For the special case where the PLOTs or XYPLOTs refer to the same superelements and use
the same FIND, a single SEUPPLOT followed by a single FIND may be placed above all the
commands.
Main Index
CHAPTER 5 803
Selects Stereoscopic Projection
STEREOSCOPIC Selects Stereoscopic Projection
See the description of the ORTHOGRAPHIC, etc..
Main Index
804 MSC Nastran Quick Reference Guide
Location of the Observer
VANTAGE POINT Location of the Observer
Defines the location of the observer with respect to the model in the (r, s, t) coordinate system defined on the
AXES command for perspective and stereoscopic projections only.
Format:
VANTAGE POINT ro so to do sor
Example:
VANT 100.
Describers Meaning
ro Location of the observer on the r-axis in model units (Real).
so Location of the observer and left eye of the observer on the s-axis, in model units,
for perspective and stereoscopic projections, respectively (Real).
to Location of the observer on the t-axis in model units (Real).
do Separation of the observer and the projection plane on the r-axis in model units.
The PROJECTION PLANE SEPARATION command may also specify the
separation (Real).
sor Location of the of the observer’s right eye for stereoscopic projections in model
units (Real).
Remarks:
1. VANTAGE POINT or the FIND command must be specified if the PERSPECTIVE or
STEREOSCOPIC command is also specified.
2. The VANTAGE POINT command is not recommended. The FIND command is recommended
because it automatically calculates the optimum vantage point.
3. A theoretical description of the vantage point is contained in Plotting in the MSC Nastran Reference
Guide.
Main Index
CHAPTER 5 805
Angular Relationship of Observer’s Coordinate System
VIEW Angular Relationship of Observer’s Coordinate System
Defines the angular relationship between observer’s coordinate system (r, s, and t axes specified on the AXES
command) and basic coordinate system.
Format:
VIEW gamma beta alpha
Example 1:
View the model from the r-axis.
VIEW 0. 0. 0.
Example 2:
View the model midway between the r- and s-axes.
VIEW 45. 0. 0.
Describers Meaning
gamma Angle of rotation, in degrees, of t axis specified on AXES command (Default =
34.27).
beta Angle of rotation, in degrees, of s axis specified on AXES command (Default =
23.17 if ORTHOGRAPHIC or STEREOSCOPIC command is specified and
0.0 if PERSPECTIVE command is specified).
alpha Angle of rotation, in degrees, of r axis specified on AXES command (Default =
0.0).
Remarks:
1. If no VIEW command is specified, then VIEW 34.27 23.17 0.0 is assumed for orthographic and
stereoscopic projections; and VIEW 34.27 0.0 0.0 is assumed for perspective projections. The default
values produce a plot in which unit vectors on the axes of the basic coordinate system have equal
lengths.
2. The angles are rotated in sequence: gamma rotates the t-axes, followed by beta which rotates the
s-axes, followed by alpha which rotates the r-axes.
Main Index
806 MSC Nastran Quick Reference Guide
Angular Relationship of Observer’s Coordinate System
T,Z
Y
(a) g-rotation about T-axis.
S
R T
X
Z
(b) b-rotation about S-axis.
S
X
T
Y
(c) a-rotation about R-axis.
S
R
X
3. The VIEW command specifies the position of the model with respect to the s-t plane. Gamma and
beta represent the angles of turn and tilt. Alpha is normally not used since it does not affect the
orientation of the s-t plane, but only it’s orientation on the plot frame.
Main Index
Chapter 6: Parameters MSC Nastran Quick Reference Guide
6 Parameters
Parameter Descriptions
Parameter Applicability Tables
Main Index
806 MSC Nastran Quick Reference Guide
Parameter Descriptions
Parameter Descriptions
Parameters are used extensively in the solution sequences for input of scalar values and for requesting special
features. Parameters values are specified on PARAM Bulk Data entries or PARAM Case Control commands.
The PARAM Bulk Data entry is described in the Bulk Data Entries. The PARAM Case Control command is
described in the PARAM (Case). PARAMs may also be used in .rc and .ini files as described in Specifying
Parameters in the MSC Nastran Installation and Operations Guide. A complete alphabetical list of PARAMeter
names and their functions is given in this section.
If the Bulk Data involves the use of part superelements or external superelements, the following points should
be noted regarding the use of the PARAM Bulk Data entry:
1. PARAM entries specified in the Main Bulk Data portion of the input data apply only to the residual
and not to the part superelements or external superelements.
2. PARAM entries specified in the BEGIN SUPER portion of the Bulk Data for a part superelement or
an external superelement apply only to that superelement.
3. The most convenient way of ensuring that PARAM entries apply not only to the residual, but also to
all part superelements and external superelements is to specify such PARAM entries in Case Control,
not in the Main Bulk Data. This is particularly relevant for such PARAMs as POST.
ACEXTMTD
ACEXTMTD is used to select a different solver for solving exterior acoustic model. Valid options are ITER
for selecting iterative solver and KRYLOV for selecting Krylov solver.
ACEXTSET
ACEXTSET is used to select ITER bulk data entry for PARAM,ACEXTMTD,ITER.
ACMPF
Default = -1
ACMPF specifies a Fortran unit number to import the acoustic load modal participation factors provided by
Actran in OP4 file to Nastran SOL 111 to perform stress and strain recovery, random and fatigue analyses.
This parameter is compatible with multiple acoustic load cases.
The Fortran unit must be a valid one which should not conflict with Nastran reserved Fortran unit numbers.
ACOUT
Default = PEAK
ACOUT specifies the type of output to be used with the FORCE Case Control command in coupled
fluid-structural analysis. ACOUT=RMS requests root-mean-square output.
To obtain sound pressure level in units of dB and dBA given by the FORCE command, a peak reference
pressure must be specified with PARAM, PREFDB. The dB level is defined as:
P
dB = 20 log ----------------------
PREFDB
Main Index
CHAPTER 6 807
Parameter Descriptions
Instead of ACCELERATION, suffix INT can be utilized to generate INTENSITY. See also the Case Control
command FLSTCNT (Case).
ACOWEAK
Default = NO
ACOWEAK controls the execution of weakly coupled acoustic formulation logic. PARAM,ACOWEAK,YES
will activate weakly coupled acoustic formulation which will solve exterior acoustic model along with
CACINFx separately using load generated from structural response and coupling matrix. ACOWEAK,YES
is available only in SOL 111 and SOL 200 with ANALYSIS=MFREQ.
In the cases where loading is on exterior acoustic only, PARAM,ACOWEAK,YESR will solve for exterior
acoustic model first and generates loading at coupling nodes for structural and interior acoustic model. In
addition, PARAM, ACOWEAK, YESR can be used to force NASTRAN to solve exterior acoustic model first
if loading is on both structural and exterior acoustic models.
Note that the detailed knowledge on the loading is not required to use ACOWEAK, and with PARAM,
ACOWEAK, yes, the Automated logic will determine which part of FSI to solve first.
The ACOWEAK solution technique supports trim components via TRIMGRP or ACTRIM between
structure and interior cavity only. If there are trim components situated between the structure and exterior
cavity, fully coupled solution techniques should be utilized.
With ACOWEAK solution scheme, the exterior acoustic portion of the model is solved in physical
coordinates. Therefore, acoustic structural modal participation factor will not be possible since acoustic field
eigenvalues and/or eigenvectors are missing or incomplete.
ACSYM
Default = YES
By default, the dynamic equations for coupled fluid-structure analysis in frequency response are symmetrized
for efficiency. PARAM,ACSYM,NO requests the pre-Version 69 formulation which involves no
symmetrization and will require more CPU time. See Formulation of Dynamic Equations in SubDMAP GMA in the
MSC Nastran Reference Guide. See also the Case Control command FLSTCNT (Case).
If the iterative solver is selected (see the Case Control command, SMETHOD (Case)) then the external work
diagnostic will be different between ACSYM=YES and ACSYM=NO.
ACTDMP
Default=0
This parameter can be used to specify DMP processors for Actran. By default(ACTDMP=0), it will be set to
DMP of Nastran job submittal.
ACTSMP
Default=0
This parameter can be used to specify SMP processors for Actran. By default(ACTSMP=0), it will be set to
SMP of Nastran job submittal.
Main Index
808 MSC Nastran Quick Reference Guide
Parameter Descriptions
ACTMEM
Default=0
This parameter can be used to specify TOTAL amount memory for all processors for Actran via DMP or
PARAM,ACTDMP in 4 bytes mega-words. By default (ACTMEM=0), Actran get the memory assigned to
parent node only. An example, for 'memorymax=64gb mem=max', use PARAM,ACTMEM,16000 which
get ACTRAN same amount of TOTAL memory as NASTRAN.
ADJMETH
Default = 0
This parameter selects the processing method used in a triple matrix product in module DSADJ. The default
is usually preferred, but ADJMETH=1 can be used when disk space is critical. ADJMETH=2 only holds the
active solution vectors.
ADMEXTU
Default = 0
ADMEXTU is a file unit number used by the SOL 111/112 restart run along with ADMPOST=1 or 2. This
file unit no is assigned to external super element op2 file. See the Case Control command ADAMSMNF* (Case),
footnote and Remark 20.
ADMPOST
Default = 0
This parameter allows the user to bring an ADAMS results file into Nastran for modal data recovery in SOL
111 and SOL 112. A value of 1 brings in the ADAMS results without consideration of rigid body motion in
the display of the results. A value of 2 brings in the ADAMS results with consideration of rigid body motion
in the display of the results. See the Case Control command ADAMSMNF* (Case) footnote and Remark 19. for
more details on restrictions and required file assignments.
ADPCON
Default = 1.0
Initial penalty values used in contact analysis are calculated automatically by the program and are given by
k SFAC ADPCON where k is a number selected for each secondary node based on the diagonal
stiffness matrix coefficients that are in the contact region, and SFAC is the value specified by the user in the
SFAC field of the BCONP Bulk Data entry. The ADPCON value applies to all the contact regions in the
model. During the analysis, if convergence problems are encountered, penalty values are automatically
reduced. Still there may be some problems where convergence can not be achieved with default values. In
such cases, analysis may be restarted with a lower value of ADPCON.
In some cases the default penalty values may be low. In such situations analysis may be restarted with a higher
value of ADPCON.
Generally, penalty values are recalculated every time there is a change in stiffness. However, if ADPCON is
negative, penalty values are calculated only at the beginning of each subcase, and penalty values are not
adjusted during analysis. This is useful if the contact between two elastic bodies is being analyzed.
Main Index
CHAPTER 6 809
Parameter Descriptions
ADSTAT
Character; Default = YES
In transient analysis (SOLs 109 and 112) and static analysis (SOL 101), if there is a preload (see Case Control
command STATSUB (Case)) and ADSTAT=YES (default); the static displacements, SPC forces, and MPC
forces are included in the results. The OLOADs will be included in the results in SOL 101 only. There is a
limitation in SOLs 101, 109, and 112 that element stresses and forces neglect thermal strains and, hence will
be wrong if there is a TEMP(LOAD) request.
AERODOF
Default=35
Digits 1 through 6 indicate which k-set degrees of freedom are to be output. This is only for Double Lattice
lifting surfaces that provide output in the plunge (3) and pitch (5) degrees of freedom by default. If additional
digits are specified (e.g. AERODOF=1235), then the k-set aerodynamic matrices are padded with null
columns for the additional degrees of freedom. Nastran will not create aerodynamic data for these added
degrees of freedom. This parameter is only useful to the user that knows how to augment the existing
aerodynamic data from an external source. Degrees of freedom 3 and 5 may not be omitted.
AESDISC
Default = 1.E-8
Tolerance for discarding generalized coordinates in the RITZ method (see Case Control command, AESMETH)
which are not linearly independent.
AESMAXIT
Default = 15
Maximum number of iterations for the ITER method (see Case Control command, AESMETH).
AESMETH
Default = SELECT
Solution method for static aeroelastic analysis.
SELECT selects the DIRECT method on models with less than 50000 DOF in the solution set;
otherwise selects AUTO.
AUTO selects the reduced basis method for an approximate solution, which is used as starting
vectors for an ITER solution.
DIRECT selects the direct solution.
RITZ selects the reduced basis approximate solution.
ITER selects the iterative solution.
AESRNDM
Default = 2
Main Index
810 MSC Nastran Quick Reference Guide
Parameter Descriptions
Number of random vectors to use as generalized functions in the RITZ method (see Case Control command,
AESMETH).
AESTOL
Default = 1.E-10
Convergence criteria for the iterative solver.
AGGROT
Default = YES
PARAM, AGGROT, YES (Default) produces both translation and rotational terms in the structure-fluid
interface matrix AGG. PARAM, AGGROT, NO produces only translational terms in the structure-fluid
interface matrix AGG. Since fluid elements see no rotational degrees of freedom, AGGROT YES or NO
should have no significant effect on the results of the fluid cavity. Results on the structural side may change
especially near unconstrained boundaries where there may be a reversal in the signs of some acceleration
terms.
ALPHA1, ALPHA2
Default = 0.0, 0.0
In frequency and transient response analysis, if PARAM,ALPHA1 and/or ALPHA2 are not equal to zero,
then Rayleigh damping is added to the viscous damping. ALPHA1 is the scale factor applied to the mass
matrix and ALPHA2 to the structural stiffness matrix. In SOL400, ALPHA1 and ALPHA2 are supported for
both the linear and nonlinear elements. In SOL 129, Alpha1 scales the mass matrix, and ALPHA2 is not used.
B = B + ALPHA1 M + ALPHA2 K
If i is the damping ratio for the i-th mode i (radians/unit time), then ALPHA1 1 and ALPHA2
2 may be computed as
j –i
1 2 i j i
= ------------------
2
-
2 1-
– 1- ----
2 j – i ----- j
j i
and the damping ratio for any other l mode becomes
i j j l i l
l = ------------------- ----- – ----- i – ----- – ----- j
j – i l j
2
2
l i
Main Index
CHAPTER 6 811
Parameter Descriptions
Note: The use of Rayleigh damping with non-zero values of ALPHA1 may not be appropriate for
enforced motion problems involving large mass since the resulting damping matrix may
essentially violate the assumption of large mass in the problem and thus give wrong answers.
Similarly, the use of Rayleigh damping with non-zero values of ALPHA2 may not be
appropriate for enforced motion problems involving large stiffness since the resulting damping
matrix may essentially violate the assumption of large stiffness in the problem and thus give
wrong answers.
Since Version 2005r3, the ALPHA1, ALPHA2 parameters apply only to stationary structural
components. Prior to this version, the parameters applied to both stationary and rotating
structural components. With the introduction of Version 2005r3, new parameters
ALPHAR1, ALPHAR2 are defined on the RSPINR and RSPINT bulk data entry for the
rotating component, see Remark 8. of the DAMPING bulk data description for a comment
on this item.
Rayleigh damping is designed to be applied only at Superelement, Part Superelement, or
External Superelement residual assembly time. It is not applied in individual Parts or External
superelements.
ALPHA1FL, ALPHA2FL
Default = 0.0, 0.0
In frequency and transient response analysis, if PARAM,ALPHA1FL and/or ALPHA2FL are not equal to
zero, then Rayleigh damping is added to the viscous damping. ALPHA1FL is the scale factor applied to the
mass matrix and ALPHA2FL to the fluid stiffness matrix.
B = B + ALPHA1FL M + ALPHA2FL K
If i is the damping ratio for the i-th mode i (cycles/unit time), then ALPHA1FL 1 and ALPHA2FL
2 may be computed as
j –i
1 2 i j i
= ------------------
2
-
2 1-
– 1- ----
2 j – i -----
j i j
and the damping ratio for any other l mode becomes
i j j l i l
l = ------------------- ----- – ----- i – ----- – ----- j
j – i l j l i
2 2
Main Index
812 MSC Nastran Quick Reference Guide
Parameter Descriptions
Note: The use of Rayleigh damping with non-zero values of ALPHA1FL may not be appropriate for
enforced motion problems involving large mass since the resulting damping matrix may
essentially violate the assumption of large mass in the problem and thus give wrong answers.
Similarly, the use of Rayleigh damping with non-zero values of ALPHA2FL may not be
appropriate for enforced motion problems involving large stiffness since the resulting damping
matrix may essentially violate the assumption of large stiffness in the problem and thus give
wrong answers.
Rayleigh damping is designed to be applied only at Superelement, Part Superelement, or
External Superelement residual assembly time. It is not applied in individual Parts or External
superelements.
ALTRED
Default = NO
ALTRED=YES requests the alternate stiffness and load reduction technique for superelement analysis in
SOLs 101 and 114. This technique is described in Static Solutions in SubDMAP SEKRRS, Static and Dynamic Load
Generation, and Data Recovery Operations in SubDMAP SEDISP in the MSC Nastran Reference Guide.
ARBMASP
Default = 2
ARBMASP defines the maximum aspect ratio of CQUAD4 generated for CP/OP options of PBMSECT if
ARBMSTYP=timoshen. Since the thickness of a ply is usually the small dimension, ARBMASP affects the
size of CQUAD4 lengthwise along a segment.
ARBMFEM
Default = YES
ARBMFEM controls the generation of .bdf file which contains the Finite Element Model of the arbitrary
beam cross section. This parameter is functional for PBRSECT and PBMSECT only. To turn off the
capability, set value of ARBMFEM to ‘NO’.
ARBMNOW
Default = 0
ARBMNOW controls the overwrite of segment property for PBMSECT, arbitrary beam cross section. With
default value of ARBMNOW, segment property overwrite will occur during the process of assigning the
property for each segment. To turn off segment property overwrite, use PARAM,ARBMNOW,1.
ARBMPS
Default = YES
ARBMPS controls the generation of outline plot for arbitrary beam cross section in PostScript format. This
parameter is functional for PBRSECT and PBMSECT only. To turn off capability, set value of ARBMPS to
‘NO’.
Main Index
CHAPTER 6 813
Parameter Descriptions
ARBMSS
Default = NO
ARBMSS controls the stress recovery for the whole arbitrary beam cross section and the companion ‘screened’
stresses. The stress recovery for the whole cross section is available in ‘OP2’ format and suitable for post-
processing. The ‘screened’ stresses for CBAR and CBEAM elements is available in print file (f06) and can be
utilized for design optimization via RTYPE=ABSTRESS on DRESP1. This parameter is functional for
PBRSECT and PBMSECT only. To turn on the capability, set value of ARBMSS to ‘YES’.
Note: The recovery of ‘screened’ stresses will be turned on automatically if RTYPE=ABSTRESS is in
use on DRESP1.
ARBMSTYP
Default = TIMOSHEN
ARBMSTYP controls the solution algorithm for composite arbitrary beam cross-section. Other valid option
is 'TIMOFORC'. This parameter is functional for PBRSECT and PBMSECT only.
ARF
Default = 0.95
See FLUIDMP.
ARS
Default = 0.95
See FLUIDMP.
ASCOUP
Default = YES
In coupled fluid-structure analysis, by default, the coupling between the fluid and structure is computed.
This interaction will be ignored if PARAM,ASCOUP,NO is specified. See also the Case Control command
FLSTCNT (Case) for alternative selections.
ASING
Default = 0
ASING specifies the action to take when singularities (null rows and columns) exist in the dynamic matrices
(or K ll in statics). If ASING=-1, then a User Fatal Message will result.
If ASING=0 (the Default), singularities are removed by appropriate techniques depending on the type of
solution being performed. The procedures used are described in Data Recovery Operations in SubDMAP SEDRCVR
and Real Eigenvalue Analysis in SubDMAPs SEMR3 and MODERS in the MSC Nastran Reference Guide.
Main Index
814 MSC Nastran Quick Reference Guide
Parameter Descriptions
AUNITS
Default = 1.0
AUNITS is used in SOL 144 to convert accelerations specified in units of gravity on the TRIM Bulk Data
entry to units of distance per time squared. Accelerations are divided by this parameter. To convert
accelerations input in g’s into physical, consistent units, set AUNITS to 1/g.
AUTOADJ
Default = YES
In SOL 200, a value of yes will automatically choose the direct or adjoint sensitivity analysis based on the
performance criteria. Other options for this parameter are:
NO - the adjoint method will not be selected.
NOSTAT - the adjoint method will not be selected for static analysis subcases, but may be selected
for frequency response subcases based on the performance criteria.
NOFREQ - the adjoint method will not be selected for frequency responses subcases, but may be
selected for static analysis subcases based on the performance criteria.
The default should be preferred in all cases. However, the other options allow investigation of the alternative
of using direct sensitivity methods.
AUTOGOUT
Default = NO
PARAM,AUTOGOUT,YES simplifies grid point data recovery requests when only a set of elements is
specified. In other words, given a set of elements the program will automatically determine all connected
grid points and honor the data recovery requests for both grid points and elements. See also
PARAM,OELMOPT description.
If PARAM,AUTOGOUT,YES is specified then the program assumes that SET 2 defines the set of desired
elements and SET 1 defines the additional grids not connected to the elements in SET 2. If no additional
grids are desired then the user need only specify SET 1=0. For example, in Case Control,
Param,autogout,yes
Set 2 = 27,35,25,41234,123,thru,134,9701,9901 $ elements
Set 1 = 0 $ additional grids
Displ=1
Gpfor=1
Stres=2
If the user prefers to use different set IDs then user PARAMs OSETELE and OSETGRD may be used to
change the set ids used by this feature. For example:
Param,autogout,yes
Param,osetele,200
Param,osetgrd,100
Set 200 = 27,35,25,41234,123,thru,134,9701,9901 $ elements
Set 100 = 0 $ additional grids
Displ=100
Gpfor=100
Stres=200
Main Index
CHAPTER 6 815
Parameter Descriptions
And if the user wants to add more grids that are not connected to the element set:
Param,autogout,yes
Param,osetele,200
Param,osetgrd,100
Set 200 = 27,35,25,41234,123,thru,134,9701,9901 $ elements
Set 100 = 29 $ additional grids
Displ=100
Gpfor=100
Stres=200
AUTOMSET
Character, Default = NO (Except in SOL 400 with ANALYSIS=STATICS)
The relationship between dependent and independent degrees-of-freedom for rigid elements and MPCs may
be altered from the user’s input specification via PARAM,AUTOMSET,YES or PARAM,
AUTOMSET,LUSOL. For PARAM, AUTOMSET,YES, or PARAM,AUTOMSET, LUSOL, dependent
degrees-of-freedom of the model, the M-set are automatically determined by employing a rectangular
decomposition of the RMG matrix.
YES The rectangular decomposition is performed via UMFPACK, which is used by permission.
Copyright (c) 2002 by Timothy A. Davis. All rights reserved. Availability:
http://faculty.cse.tamu.edu/davis/suitesparse.html
LUSOL The rectangular decomposition is performed via LUSOL, which is capable of Rook or full
pivoting during rectangular decomposition. LUSOL option is especially suitable for ill
conditioned RMG matrix or problems with redundant multi-point constraints. Availability:
http://web.stanford.edu/group/SOL/software/lusol/
AUTO = start run acting as if AUTOMSET were NO, but if that fails, switch to YES and continue the run.
Notes: RSSCON is not supported with AUTOMSET.
AUTOQSET
Default = NO
AUTOQSET=YES requests the automatic calculation of component modes without the need to define a q-
set (generalized coordinates).
1. The calculation of component modes is attempted on all superelements including the residual
structure.
2. All component modes are treated like SPOINTs which means that all component modes are “brought
down” to and assigned to the q-set in the residual structure. In other words, component modes may
not be assigned interior to a superelement.
3. Selected component modes may not be removed (constrained).
4. Since the generalized coordinates are automatically defined, the following entries may not be
specified: QSETi, SEQSETi, SENQSET, or PARAM,NQSET.
Main Index
816 MSC Nastran Quick Reference Guide
Parameter Descriptions
5. This feature is not supported with:
a. Design optimization (SOL 200)
b. Aerodynamic analyses (SOLs 144, 145, 146)
c. Cyclic symmetry analyses (SOLs 114, 115, 116, 118)
d. SECSETi and SEBSETi Bulk Data entries that result in a fixed-free or free-free superelement.
This restriction also applies to BSETi/BNDFIXi and CSETi/BNDFREE/BNDFRE1entries in
part (BEGIN SUPER) superelements.
PARAM,SQSETID may be used to specify the starting identification number of the automatically generated
q-set degrees-of-freedom except when the EXTSEOUT command is present (see Remark 17. of the
EXTSEOUT Case Control command). The default is 99000001.
AUTOSPC
Default = YES
This parameter is obsolete and replaced by the Case Control command AUTOSPC (Case). It is ignored for the
residual structure in all nonlinear analysis solution sequences. SOL 400 only support the AUTOSPC Case
Control command. For the residual structure in SOLs 106 and 129 see the description of parameter
AUTOSPCR. AUTOSPC and the related parameters EPPRT, EPZERO, PRGPST, and SPCGEN are
analogous to and described under the AUTOSPC Case Control command under the EPSING, EPS, PRINT,
and PUNCH keywords, respectively. The specification of the AUTOSPC Case Control command overrides
the specification of PARAM,AUTOSPC and its related parameters EPPRT, EPZERO, PRGPST, and
SPCGEN.
AUTOSPCR
Default = NO (SOLs 106 and 129 only)
PARAM, AUTOSPCR is applicable only to any o-set degrees of freedom in the residual structure in SOL106
and SOL 129. In SOL 106 and SOL 129, the o-set may only be used in the linear part of the residual
structure. The AUTOSPCR=YES requests that after all residual SPC and MPC constraints are processed,
stiffness singularities and near singularities be automatically constrained in the linear stiffness part (o-set) of
the residual structure. The nonlinear part of the residual structural is contained in the a-set degrees of
freedom and is not affected by AUTOSPCR=YES.
If the residual structure contains a complex mix of linear and nonlinear elements, it is recommended that all
degrees-of-freedom attached to nonlinear elements be specified on ASETi entries.
Parameters EPPRT, EPZERO, PRGPST, and SPCGEN may be used with AUTOSPCR.
AUTOSPRT
Default = YES
By default, free-free models will be automatically constrained for calculation of residual vectors (RESVEC
Case Control command) as long as F1 ≤ 0.0 on the EIGR (or EIGRL) Bulk Data entry. The auto-SUPORT
method may be deactivated by specifying a SUPORTi entry, PARAM,AUTOSPRT,NO, or F1 > 0.0.
FZERO is the maximum frequency assumed for a rigid body mode. FZERO is used by the auto-SUPORT
method to extract the rigid body frequencies. The default is 1.0.
Main Index
CHAPTER 6 817
Parameter Descriptions
BAILOUT
Default = 0
See MAXRATIO.
BEAMBEA
Real, Default = 1000.0
Value Equivalent radius to be used for beam-beam contact problems. For tubes or round bars, use
the outer radius. If the radii are different enter the largest outer radius. For beams, enter an
equivalent radius calculated as follows:
I=0.5*(Ix+Iy)
R=sqrt(A/pi2+2*I/A)
where A, Ix, Iy are the cross-section properties and pi2 = 2 .
BEIGRED
Default = YES
PARAM,BEIGRED,YES requests a more efficient method to reduce viscous damping matrices. CPU and
disk space savings may be significant if there is a small number of viscous damping elements. BEIGRED is
automatically disabled if the number of DOF connected to viscous dampers exceeds the value specified by
PARAM,MAXDAMP.
MAXDAMP (default=1000) specifies the maximum number of DOF connected to viscous damping
elements, such that an alternate reduction method is employed. When there are relatively few viscous
dampers, an alternate reduction method is chosen automatically for efficiency. The efficiency is lost however
if the number of viscous damping DOF exceeds about 1000. If the number of viscous damper DOF exceeds
MAXDAMP, User Warning Message 9166 is printed and the alternate damping reduction logic is disabled.
Also note that if MAXDAMP is exceeded, FASTFR is disabled.
BIGER, BIGER1, BIGER2, BIGER3
Default = 0.0
See S1.
BUCKLE
Default = -1
BUCKLE=1 requests a nonlinear buckling analysis in a restart run of SOLs 106 or 153. See the MSC Nastran
Handbook for Nonlinear Analysis.
BUCKLE=2 requests buckling in a SOL 106 cold start run.
BUSHNM
Default = YES
Main Index
818 MSC Nastran Quick Reference Guide
Parameter Descriptions
BUSHNM =NO - If the only frequency dependencies are CBUSH/PBUSH/PBUSHT, (CELAS1 or
CELAS3)/PELAS/PELAST, or (CDAMP1 or CDAMP3)/PDAMP/PDAMPT, or CAABSF/PAABSF or any
combination of these, then the DMAP will execute the original DMAP path designed for these elements.
The original DMAP path designed for the above elements does not make use of the concept of master
frequencies controlled by the Case Control Command MFREQ=n. To obtain the same forcing frequency
selection, and hence the same results, with PARAM,BUSHNM,YES that is in effect, with
PARAM,BUSHNM,NO, the user should either set MFREQ to the same set as defined on the Case Control
Command FREQ=n, or set MFREQ=NOAUTO.
PARAM,BUSHNM,NO in conjunction with a GPFORCE request will cause a Nastran fatal error at the
beginning of the Nastran run. The reason is that the stiffness, structural damping, and viscous damping
matrices are non-standard in form for the old path and represent incremental changes between nominal and
current frequency.
If the user is currently running Porous Elastic Material (PEM), PARAM, BUSHNM is internally set to:
PARAM, BUSHNM, NO and overrides any input value.
BWKD
Default = NO
This parameter will change the default “BW” method on the ACMODL entry to the “BWKD' method if set
to BWKD=YES.
This parameter is also an MSC Nastran job submittal key word and maybe placed in an RC file to override
the “BW” default on the ACMODL entry. Then, it would appear as shown in the following file:
A .nastranrc - file with additional data
…
bwkd =yes
Also, on a manual submittal with no .nastranrc - file:
On the command line the user would have;
nastran20xxxy job_file.dat bwkd=yes.
CASIEMA
Default = NO, SOL 400 CASI Solver only
When the CASI element-based iterative solver is specified (see the Case Control command SMETHOD (Case))
SOL 400 skips various processes associated with the global structure stiffness matrix. The absence of a
complete assembled stiffness matrix and its sub-sets can lead to a termination of the solution process in the
NLSOLV module if the CASI solver detects a singularity. If the parameter is set to YES, SOL 400 performs
all assembly and displacement set reduction operations involving the complete stiffness matrix allowing the
NLSOLV module to select either the matrix-based iterative solver or the sparse direct solver to continue in
the event CASI detects a singularity.
Use a value of YES with caution as it adversely affects run-time performance. Substantial additional disk space
could be required as well as longer run times. Keep in mind that invocation of the sparse direct solver for large
solid element models may degrade performance even further.
Main Index
CHAPTER 6 819
Parameter Descriptions
This parameter only applies to SOL 400 usage of the CASI solver.
CASIMEST
Default = Yes
This parameter controls the memory estimation inside CASI iterative solver. (SOL 101, SOL 400 and SOL
200)
= No; Turns off memory estimation.
CASPIV
Default = 1.0e-10
Input DMAP parameter to the SOLVIT and NLSOLV modules for the CASI iterative solver. It is the pivot
threshold for the CASI PCG (Preconditioned Conjugate Gradient) factorization. Pivot value less than
CASPIV will exit with an error message.
CB1, CB2
Default = (1.0, 0.0)
CB1 and CB2 specify factors for the total damping matrix. The total damping matrix is:
x 2
B jj = CB1 B jj + CB2 B jj
2 x
where B jj is selected via the Case Control command B2GG and B jj comes from CDAMPi or CVlSC
element Bulk Data entries. These parameters are effective only if B2GG is selected in the Case Control
Section.
CDIF
Default = YES for shape optimization with or without property optimization.
Default = NO for property optimization only.
CDIF may be used to override the default finite difference scheme used in the calculation of pseudo loads in
SOL 200. PARAM,CDIF,YES forces the selection of the central difference scheme used in the semianalytic
approach regardless of the type of optimization requested. PARAM,CDIF,NO forces the selection of the
forward difference scheme.
CDITER
Default = 0
If CDITER > 0, perform constrained displacement iterations in SOL 101. The value is the maximum
number of iterations. If CDPRT=YES, print those negative displacements and tension forces which do not
satisfy constraints. If CDPCH=YES, punch DMIG CDSHUT entries for final state; by default all gaps are
closed. These can be used for initial conditions for restart. Potential contact points must be specified on the
SUPORTi entries. The SUPORTi points must be in the residual structure. Optional DMIG entries to
define the initial shut vector may be specified. Degrees-of-freedom that are specified on the SUPORT entry
and have a value of 1.0 defined on the DMIG,CDSHUT entry will be considered closed initially.
Main Index
820 MSC Nastran Quick Reference Guide
Parameter Descriptions
If the DMIG,CDSHUT entry is not supplied, then all degrees-of-freedom specified on the SUPORT entries
will be considered shut initially. A fatal message will be issued if this parameter is used and PARAM,INREL
is specified. Constrained displacement iteration (PARAM,CDITER,YES) does not support parallel
processing (DMP).
CDPCH
Default = NO
See CDITER.
CDPRT
Default = YES
See CDITER.
CFDIAGP
Default = NO
If YES, randomly deleted CFAST elements will be printed. (See CFRANDEL)
CFRANDEL
Default = 0.
Represents a percent, expressed as a decimal fraction, of the number of CFAST elements to be randomly
deleted.
CHECKOUT
Default = NO
CHECKOUT=YES requests a model checkout in SOLs 101 through 200. See Geometry Processing in SubDMAP
PHASE0 in the MSC Nastran Reference Guide. The run will terminate prior to phase 1 of superelement
analysis. The PARAM,POST options are also available with PARAM,CHECKOUT,YES. The following
options and their user parameters are also available with PARAM,CHECKOUT,YES:
1. PARAM,PRTGPL,YES
Prints a list of external grid and scalar point numbers in internal sort. It also lists external grid and
scalar point numbers along with the corresponding sequence numbers in internal sort. The sequence
numbers are defined as (1000*external number) and will reflect any user-requested resequencing.
2. PARAM,PRTEQXIN,YES
Prints a list of external and internal grid and scalar numbers in external sort. It also lists external grid
and scalar numbers with the corresponding coded SIL number in external sort. The coded SIL
numbers are defined as:
1 for grid point
10 SIL + (1)
2 for scalar point
Main Index
CHAPTER 6 821
Parameter Descriptions
The SIL numbers correspond to degrees-of-freedom, i.e., one SIL number for scalar point and six SIL
numbers for a grid point.
3. PARAM,PRTGPDT,YES
Prints, for each grid and scalar point, the following information in internal sort:
• Coordinate system ID in which grid point geometry is defined (ID=-1 for scalar points).
• Spatial location of grid points in the “CP” coordinate system. For scalar points, all entries are
zero.
• Coordinate system ID for grid point displacements, forces, and constraints (ID=0 for scalar
points).
• Permanent single-point constraints defined on GRID Bulk Data entries. A zero is entered for
scalar points.
4. PARAM,PRTCSTM,YES
Prints for each coordinate system type the transformation matrix from the global to the basic
coordinate system, and the origin of the indicated coordinate system in the basic coordinate system.
Coordinate system types are: 1 = rectangular; 2 = cylindrical; 3 = spherical.
5. PARAM,PRTBGPDT,YES
Prints all grid and scalar points listed in internal sort with their x, y, and z coordinates in the basic
coordinate system. In addition, the coordinate system ID for grid point displacements, forces, and
constraints is indicated for each grid point (ID=-1 for scalar points). The x, y, and z coordinates of
scalar points are zero.
6. PARAM,PRTGPTT,YES
Prints, for each temperature load set, information on element and grid point temperatures.
7. PARAM,PRTMGG,YES
Prints the g-size mass matrix labeled by grid point/degree-of-freedom.
8. PARAM,PRTPG,YES
Prints the g-size load vectors labeled by grid point/degree-of-freedom.
9. The summation of forces and moments of applied loads in the basic coordinate system is
automatically output for each loading condition requested in the Case Control Section. Related to
parameters GPECT and PROUT, and Case Control command ELSUM.
CHKCOND
Default = YES
Maximum acceptable value of the condition number of the stiffness matrix if decomposition of the stiffness
matrix indicates potential singularities.
CHKCOND=YES triggers the calculation of the stiffness matrix condition number in linear static analysis,
SOL 101. User Information Message 15201 is printed in the F06 file to display the condition number. The
condition number calculation is supported only for the MSCLDL sparse direct solver. The condition number
is not computed if MUMPS or Pardiso is used.
Main Index
822 MSC Nastran Quick Reference Guide
Parameter Descriptions
CK1, CK2
Default = (1.0, 0.0)
CK1 and CK2 specify factors for the total stiffness matrix. The total stiffness matrix (exclusive of GENEL
entries) is
x z 2
K jj = CK1 K jj + CK2 K jj
2 z
where K jj is selected via the Case Control command K2GG and K jj is generated from structural
element (e.g., CBAR) entries in the Bulk Data. These are effective only if K2GG is selected in Case Control.
A related parameter is CK3.
Note: Stresses and element forces are not factored by CK1, and must be adjusted manually.
CK3
Default = (1.0, 0.0)
CK3 specifies a factor for the stiffness derived from GENEL Bulk Data entries. The total stiffness matrix is
x y
K jj = K jj + CK3 K jj
y x
where K jj comes from the GENEL Bulk Data entries and K jj is derived using PARAMs CK1 and
CK2. CK3 is effective only if GENEL entries are defined. Related parameters include CK1 and CK2.
CLEANVEC
Default = No
CLEANVEC is used when solving for the real modes of a system. If CLEANVEC is set to YES, then if two
modes appear to be repeated roots, the program will attempt to find a set of clean, repeatable eigenvectors for
them. As the eigenvectors of repeated roots can be any combination of the actual eigenvectors, obtaining
clean eigenvectors can make them easier to identify. In the case of ROM model creation, this is essential for
mode-mapping.
CLNVCTOL
Default = 0.01
Tolerance for fractional change in eigenvalue to be used in CLEANVEC module to determine if modes are
potential repeated roots. Input is percentage, so the default of 0.01 gives a tolerance of .0001 in the module.
CLOSE
Default = (1.0)
A value of 1.05 will set natural frequencies within 5% of each other as close. See SCRSPEC.
Main Index
CHAPTER 6 823
Parameter Descriptions
CM1, CM2
Default = (1.0, 0.0)
CM1 and CM2 specify factors for the total mass matrix. The total mass matrix is
x 2
M jj = CM1 M jj + CM2 M jj
2 x
where M jj is selected via the Case Control command M2GG and M jj is derived from the mass element
entries in the Bulk Data Section. These are effective only if M2GG is selected in the Case Control Section.
COMPMATT
Default = NO, SOL 106 and SOL 400 only
In nonlinear statics (SOLs 106, 400 ANALYSIS=NLSTAT), composite materials compute temperature-
dependent properties for the plies only at the reference temperature given on the PCOMP Bulk Data entry.
The ply properties are smeared and used for all load steps, regardless of whether the temperature is changing
through application of thermal loads.
If the parameter is set to YES, the temperature-dependent properties for the plies are updated and smeared
at the current temperature for each load step. For CQUAD4 and CTRIA3 elements with offsets, the large
rotation offset method specified by “MDLPRM,OFFDEF,LROFF” in SOL 400 must be used.
If the parameter is set to NONSMEAR, the temperature-dependent properties for the plies are updated at
the current temperature for each load step. This option, only available for the CQUADR and CTRIAR
elements, is an alternative to the smeared approach.
This parameter only applies to SOLs 106 and 400 ANALYSIS=NLSTAT, and only applies to composite
CQUAD4, CTRIA3, CQUADR and CTRIAR elements that are not associated with the enhanced nonlinear
materials (PSHLN1).
Prior to Nastran version 2019, when COMPMATT was set to YES, material nonlinear was assumed even
when no composite plies had temperature-dependent materials or when there was no MATTi type entries
associated with temperature dependent plies. This has caused confusion as to when SOL106 or SOL400 is
doing linear or nonlinear material solutions. Starting in V2019, PARAM, COMPMATT, YES will only turn
on material nonlinear if there are active MATTi entries as well.
Additionally, prior to Nastran version 2019, when PARAM, COMPMATT, YES was used in conjunction
with TEMPP1 entries, ply stress computation used only the reference plane temperature. Starting in V2019,
ply stress computation will use reference plane temperature plus the thermal gradient term applied at the
center of each ply. (To revert to the old method, NASTRAN SDRCMPTP=1 may be added to the Nastran
section.) The enhanced nonlinear materials (PSHLN1) do not support the TEMPP1 entry.
See the Nastran OFTDCMP(804) entry comment about force/moment data recovery with PARAM,
COMPMATT, YES and a MID4 field specified on the resulting smeared composite internal PSHELL entry.
If the coefficients of thermal expansion, on the resulting smeared MAT2 entries, corresponding to the MID4
field on the resulting PSHELL entry are to be used for nonlinear thermal strain computations,
PARAM, COMPMATT,YES must be present if out of plane thermal bending is deemed important.
Main Index
824 MSC Nastran Quick Reference Guide
Parameter Descriptions
CONFAC
Default = 1.E-5
In superelement analysis, CONFAC specifies the tolerance factor used in checking the congruence of the
location and displacement coordinate systems of the boundary points between image superelements and their
primaries (see the Bulk Data entry, CSUPER). Specification of this parameter is recommended instead of DIAG
37 (DIAG 37 ignores User Fatal Messages 4277 and 4278).
Also, in superelement (module) analysis, CONFAC specifies the global default tolerance for determining
coincident boundary points between superelements (modules). Tolerance is also specified in the field TOL
on the SEBULK (MDBULK) and SECONCT (MDCONCT) Bulk Data entries. CONFAC may be
overridden by TOL on SEBULK (MDBULK) for specific modules, which, in turn, may be overridden by
TOL on SECONCT (MDCONCT) for specific grid points.
COSUBCYC
Default = 1, SOL 700 only
Controls the growth of the subcycling interval in the coupling surface.
Example:
PARAM,COSUBCYC,2
Remarks:
1. The subcycling algorithm automatically estimates the number of subcycles to be used. This is updated
throughout the calculation. This parameter controls how much the number of subcycles can grow.
For example, COSUBCYC is set to 1, and the current number of time steps between updates of the
coupling geometry is 4. If the solver estimates that the subcycling interval should be 7, the subcycling
interval is increased by 1 until a value of 7 is reached.
2. There is no control on the amount by which the subcycling interval can decrease.
COSUBMAX
Default = 0, SOL 700 only
Defines the maximum number of subcycles that can occur in Euler/Lagrange coupling. During a subcycle,
the geometry of the coupling surface is not updated.
Example:
PARAM,COSUBMAX,10
Remarks:
1. Updating the coupling geometry takes a lot of CPU time. Subcycling gives substantial savings in CPU
time for coupled calculations.
Main Index
CHAPTER 6 825
Parameter Descriptions
2. The smaller the value of this parameter, the greater the accuracy of the analysis and the greater the
cost. Conversely, larger values offer significant CPU savings, but very large values give incorrect
results.
3. If the geometry of the coupling surface is changing rapidly, smaller values of PARAM,COSUBMAX
should be used.
COUPMASS
Default = -1
COUPMASS > 0 Requests the generation of coupled rather than lumped mass matrices for elements
with coupled mass capability, as listed in Table 3-1 in the MSC Nastran Reference
Guide. This option applies to both structural and nonstructural mass for the
following elements: CBAR, CBEAM, CONROD, CQUAD4, CHEXA, CPENTA,
CPYRAM, CQUAD8, CROD, CTETRA, CTRIA3, CTRlA6, CTRIAX6,
CTUBE.
COUPMASS < 0 (Default) causes the generation of lumped mass matrices (which may include torsion
inertia for beam elements, and some coupling if there are beam offsets) for all of the
above elements. However, if SYSTEM(414) is greater than zero, (Default = 0) then
the lumped mass matrices will contain translational components only for the CBAR
and CBEAM elements.
CP1, CP2
Default = (1.0, 0.0)
The load vectors are generated from the equation
x 2
P j = CP1 P j + CP2 P j
2 x
where P j is selected via the Case Control command P2G, and P j comes from Bulk Data static load
entries. These parameters are effective only if P2G is selected in the case control section.
CQC
Default = -1
See SCRSPEC.
CURV
Default = -1
PARAM,CURV,1 requests that the CTRIA3 and CQUAD4 element stress and/or strain output be computed
in a material coordinate system (normal output is in the element or basic coordinate system) and/or to
interpolate it to grid points. (CQUAD4 element corner stress output is not supported.)
Main Index
826 MSC Nastran Quick Reference Guide
Parameter Descriptions
The integer parameter OG controls the calculation of stress and/or strain data at grid points. If OG is set to
-1, the calculation for stresses and/or strain data at grid points is not performed. The default value of zero
provides the calculation of these quantities at those grid points to which the selected elements connect.
User parameters S1G, S1M, S1AG, and S1AM, set to 1, request the printout of stresses at grid points, stresses
in the material coordinate system, strains at grid points and strains in the material coordinate system,
respectively.
The integer parameter OUTOPT may be set in accordance with the below options to select print, punch,
and/or plotter output for stress and/or strain data that are computed in user-defined material coordinate
systems.
OUTOPT Value Description
0 Default-standard MSC Nastran device codes are used.
1 Print only
2 Plot only
4 Punch only
The above values may be combined additively to select two or more forms of output. For example,
OUTOPT=6 requests both plot and punch output. Related parameters include BIGER, CURVPLOT,
DOPT, NUMOUT, NINTPTS, S1G, S1M.
For stress and/or strain/curvature output in a user-defined material coordinate system MCSID must be
defined on MAT1 and MAT2 Bulk Data entries. The values of MCSID reference CORDiR, CORDiC, and
CORDiS Bulk Data entries. A value of zero for MCSID does not imply the basic coordinate and will
eliminate all elements which reference the MATi from the subject calculations.
1. If these data are requested at the element centers, the program will compute the unit vector i m along
the T1 or x-axis of the material coordinate system, and compare
n im
for each element that references the material coordinate system, where n is the normal to the surface
of the element. If
2
n i m .4
the projection of the y-axis on the surface of element is taken as the reference axis. Otherwise, the
projection of the x-axis on the surface of the element is taken as the reference axis. The angle between
the x-axis of the element coordinate system and the projection of the selected reference axis of the
material coordinate system is used to transform the stress and/or strain data into the material
coordinate system at the element centers.
Main Index
CHAPTER 6 827
Parameter Descriptions
2. If, on the other hand, the user requests these data at the grid points to which the elements connect
the program will interpolate the results from (a) to the grid points to which the elements connect.
The parameter NlNTPTS=N, the stress and/or strain data at the N closest element centers to the grid
point in question will be used in the interpolation. The program may include more that N points in
the interpolation if the distance of other element centers is not more than 10% greater than the closest
N element centers.
The following specifies the output headings for stresses and/or strains in the material coordinate system.
Element stresses (PARAM,S1M,1)
1. Available in CQUAD4 and CTRlA3 elements
2. Page headings:
STRESSES IN QUADRILATERAL ELEMENTS (CQUAD4)
STRESSES IN TRIANGULAR ELEMENTS (CTRlA3)
3. Under the column FIBER DISTANCE:
Z1 is replaced by MCSID.
Z2 is replaced by 1.0 if the x-axis of the material coordinate system is selected as the reference axis,
and by 2.0 if the y-axis of the material coordinate system is selected as the reference axis.
Grid point stresses (PARAM,S1G,1 and PARAM,OG,1)
1. Available for CQUAD4 and CTRIA3 elements
2. Page heading:
STRESSES AT GRID POINTS
3. Under the column are:
MAT1 – COORD1 – ID
PROJ-CODE
Z1 is replaced by MCSID.
Z2=A+10*N where A is 1.0, 2.0, or 3.0, depending on whether the x-, y-, or z-axis of the material
coordinate system is most nearly normal to the projected plane of the field of elements involved in
the calculation.
Element strains (PARAM,S1AM,1)
1. Available for CQUAD4 and CTRlA3 elements
2. Page headings:
STRAINS IN QUADRILATERAL ELEMENTS (CQUAD4)
STRAINS IN TRIANGULAR ELEMENTS (CTRIA3)
3. Under the column FIBER DISTANCE:
Main Index
828 MSC Nastran Quick Reference Guide
Parameter Descriptions
Z1 is replaced by MCSID.
Z2 is replaced by 1.0 if the x-axis of the material coordinate system is selected as the reference axis,
and by 2.0 if the y-axis of the material coordinate system is selected as the reference axis.
Grid point strains (PARAM,S1AG,1 and PARAM,OG,1)
1. Available for CQUAD4 and CTRIA3 elements.
2. Page heading:
Z2=A+10*N where A is 1.0, 2.0, or 3.0, depending on whether the x-, y-, or z-axis of the material
coordinate system is most nearly normal to the projected plane of the field of elements involved in
the calculation.
STRAINS AND CURVATURES AT GRID POINTS
3. Under the column are:
MAT1 – COORD1 – ID
PROJ-CODE
Z1 is replaced by MCSID.
CURVPLOT
Default = -1
PARAM,CURVPLOT,1 requests that x-y (or curve) plots whose abscissas are a sequence of grid points and
whose ordinates may be displacements, loads, SPC forces, or grid point stresses. To obtain stress plots, set
the CURV parameter to +1. The default for DOPT is the length between grid points.
Specify the XYOUTPUT Case Control command in the usual manner, replacing the point ID with the SID
of SET1 Bulk Data entries.
The SET1 Bulk Data entries must contain unique SIDs for each set of grid points to be plotted.
User requests for xy-plots of output quantities appear in the Case Control Section in the standard form. For
example,
.
.
.
OUTPUT(XYOUT)
.
.
XYPLOT DISP 1/4(T3)
.
.
XYPLOT SPCF 2/5(T1)
.
.
BEGIN BULK
The first XYPLOT command will produce an xy-plot from the displacement output of subcase 1. The
abscissa of the curve will reflect the grid point IDs listed on the SET1 entry with an SID of 4, and the ordinate
will reflect the T3 component of displacement at these grid points. The second XYPLOT command will
Main Index
CHAPTER 6 829
Parameter Descriptions
produce an xy-plot whose ordinates are the T1 components of the forces of constraint in subcase 2 at the grid
points listed on the SET1 entry with an SlD of 5.
The user has some degree of control over the scaling of the abscissas on these xy-plots. This control is
exercised through the parameter DOPT on a PARAM Bulk Data entry. The legal values of this parameter
provide the following scaling options for the abscissas.
Value of DOPT Scaling for Abscissa
0 gj – gi
(Default)
1 xj – xi
2 yj – yi
3 zj – zi
4 1.
Thus, the default value of DOPT will place the first grid point listed on the referenced SET1 entry at the
origin, and subsequent grid points will be located along the abscissa at intervals proportional to the distance
between that grid point and its predecessor. Values of DOPT equal to 1, 2, or 3 will scale the abscissa so that
the interval between adjacent grid points is proportional to the difference in the X, the Y, and the Z
components of the subject grid points respectively. DOPT=4 will space the grid points equally along the
abscissa.
CWDIAGP
Default = NO
For CWELD element: prints elements randomly deleted if set to yes.
CWRANDEL
Default = 0.0
For CWELD element: if not zero, then it specifies as a decimal percent for the number of fasteners to
randomly delete.
DAMPTOL
Real, default = 1.E+8 - see RMSPRMDS
DBALL
Default = DBALL
By default, all data to be stored on the database for restart purposes will be located on the DBALL database
set DBset). These parameters permit the storage of some data blocks on DBsets other than DBALL, which
are defined by the user and specified on the INIT File Management statement. Any or all of these parameters
may be set to SCRATCH in order to reduce overall disk space usage; e.g., PARAM,DBUP,SCRATCH or
PARAM,DBALL,SCRATCH. However, automatic restarts will be less efficient because data normally
assigned to a permanent DBset will have to be recomputed.
Main Index
830 MSC Nastran Quick Reference Guide
Parameter Descriptions
A unique value for each superelement may be specified in the Case Control Section for the parameters
DBALL, DBDN, DBRCV, and DBUP. Certain DBsets may be taken offline depending on which phase (see
Summary of Solution Sequence Operations in the MSC Nastran Reference Guide) of superelement analysis is being
performed. PARAM,DBALL specifies the default value for parameters DBDN, DBUP, and DBRCV.
The DBDN DBset contains data blocks necessary for “downstream” processing. For example, the stiffness,
mass, damping, and static loads matrices that have been reduced to the boundary of the superelement are
stored in this DBset.
The DBRCV DBset contains data blocks that must be online during the first pass through data recovery
(Phase 3). These data blocks are used to recover the total displacement vector ug of the superelement. This
operation is performed by the SSG3 and SDR1 modules. On subsequent data recovery restarts, this DBset
may be taken offline. Its default is determined from the value of DBUP.
The DBUP DBset contains data blocks necessary for “upstream” processing. For example, the geometry and
property tables along with the stiffness, mass, damping, and static loads matrices related to the interior grid
points of the superelement are stored in this DBset. These matrices and tables must be online during the
reduction (Phase 1) and data recovery (Phase 3) of the superelement.
The IFP DBset contains data blocks that are required for all phases of the analysis. These data blocks are
related to the entire model; examples are Bulk Data, superelement map, IFP module outputs, and
resequenced grid points. This DBset must be online for all runs.
PARAM,DBALL also specifies the default value for PARAMs DBEXT and DSO described below.
DBCCONV
Default = XL
See POST=0.
DBCDIAG
Default = 0
See POST=0.
DBCOVWRT
Default = YES
See POST.
DBDICT
Default = -1
Controls the printout of the database directory at the beginning and end of the run. See DBDICT FMS
statement description in Section 3. If DBDICT=0, then the database directory will be printed at the start
of the run. If DBDICT=1, then the directory will be printed at the end of the run. If DBDICT>2, then it
will be printed at the beginning and end of the run. If DBDICT=-1 (the default), the directory is not printed
at the beginning or end of the run.
Main Index
CHAPTER 6 831
Parameter Descriptions
If multiple versions and/or projects exist on the database, then the parameters DBDRPRJ and DBDRVER
allow the user to select the desired project and version, respectively. The appropriate values may be found in
the Project/Version Table that is printed upon restart. If DBDRVER=0 (or DBDRPRJ=0), then the current
version (or project) is selected. If DBDRPRJ=-1 (or DBDRVER=-1), then all projects (or versions) are
selected.
DBDN
Default = value of PARAM,DBALL.
See DBALL.
DBDRPRJ
Default = 0
Specifies the desired project-identification number. See DBDICT.
DBDRVER
Default = 0
Specifies the desired version-identification number. See DBDICT.
DBEXT
Default = value of PARAM,DBALL
Specifies the DBset location to store the external superelement information. External superelement
information is generated by the EXTSEOUT Case Control command.
DBRCV
Default = value of PARAM,DBUP.
See DBALL.
DBUP
Default = value of PARAM,DBALL.
See DBALL.
DDRMM
Default = 0
DDRMM is only recognized if PARAM,SPARSEDR,NO is specified.
By default, the matrix method of data recovery is used in the modal transient and frequency response
solutions. DDRMM=-1 will force calculation of complete g-set solution vectors by the mode displacement
method and is required for FATIGUE analysis using SOL 108 or SOL 111 if PARAM,SPARSEDR,no is also
specified.
DELCLUMP
Default = 0.5, SOL 700 only
Main Index
832 MSC Nastran Quick Reference Guide
Parameter Descriptions
Format:
PARAM,DELCLUMP,VALUE
Example:
PARAM,DELCLUMP,0.1
Prevents small clumps in the Euler mesh from determining the time step and prevents the leakage of small
masses to isolated regions.
VALUE Value of DELCLUMP. See Remark 1. (Real > 0.0)
Remarks:
1. Material in Eulerian elements of a clump with:
fvunc DELCLUMP fblend is eliminated
2. See also parameter FBLEND.
DESPCH
Default = 0
For sizing and shape topography optimization, DESPCH specifies in SOL 200 when the optimized
(updated) bulk data entries are written to the PUNCH file. Currently, all the property entries, material
entries, and connectivity entries that can be designed and DESVAR, DRESP1, and GRID entries can be
written. Notice that the DRESP1 entries will be written if only when a mode tracking is performed and the
DRESP1 responses have type FREQ or EIGN.
For topology/topometry optimization, DESPCH specifies when the topology optimized element density
values (or topometry optimized values) are written to the element result file jobname.des. This file can be
directly read in PATRAN or third party post-processor to displace and animate the topology/topometry
optimization results.
<0 Never
=0 at the last design cycle only (Default)
>0 at every design cycle that is a multiple of DESPCH and the last design cycle. For example, if
n=2 and the maximum number of design cycles is 5 (DESMAX=5 on the DOPTPRM entry),
then, DESVAR and GRID entries at design cycle 2, 4, and 5 are written in the punch file.
DESPCH1
Default = 6
DESPCH1 specifies in SOL 200 the amount of data to be written to the .pch and .des file. A positive
DESPCH1 value request large field formats while a negative value requests small field formats. For a shape
optimization job, if DESPCH1<>0, the updated GRID entries of the whole model will be written in the .pch
file.
Main Index
CHAPTER 6 833
Parameter Descriptions
Descriptions of various DESPCH1 values are given below:
0 Write no data.
+1 Write the property entries that are designed.
+2 Write all the property entries of a given type when one or more property of that type is
designed.
+4 Write DESVAR and DRESP1 entries.
+n Write combine quantities by summing the DESPCH1 values. For example, n=1+4=5
requests writing all the designed property entries, DESVAR and DRESP1 entries to the .pch
file for normal modes analysis.
≥0 Write the designed and non-designed element values to the element density history file
jobname.des.
<0 Write only designed element values to the element density history file jobname.des.
DFREQ
Default = 10-5
DFREQ specifies the threshold for the elimination of duplicate frequencies on all FREQi Bulk Data entries.
Two frequencies, f 1 and f 2 , are considered duplicated if
f 1 – f 2 DFREQ f MAX – f MIN
where f MAX and f MIN are the maximum and minimum excitation frequencies of the combined FREQi
entries.
DIROUT
Default = NO
See CQC under SCRSPEC.
DOPT
Default = 0
See CURVPLOT.
DPEPS
Default = 1.0E-4
In SOL 200, if any difference between the property value on the property entries and the value calculated
from the design variable values on the DESVAR entry (through DVCRELi, DVMRELi, DVPRELi relations)
is greater than DPEPS, the design model values override the analysis values. If all the differences are less than
DPEPS, analysis results from a previous run are accepted in a subsequent sensitivity/optimization task,
thereby avoiding a reanalysis. The PTOL parameter on the DOPTPRM entry is a related parameter that
checks the maximum difference.
Main Index
834 MSC Nastran Quick Reference Guide
Parameter Descriptions
DPHFLG
Integer > 0; Default = 0
Select the method for performing eigenvector sensitivity analysis. Unless repeated eigenvalues are anticipated,
the default value is recommended.
DPHFLG 0 Nelson’s method (Default)
1 Subspace iteration method. Recommended when there are repeated roots.
2 High’s method, # of modes for iteration = min(2n, n+8, m)
n: the highest constrained mode
m: the number of modes request by EIGR
3 High’s method will all modes requested by EIGR used in the iterator.
DPHFLG = 2 and 3 have further control parameters
ITERATE yes Do iteration, for improved sensitivity value. (Default)
no No iteration, equivalent to Fox’s method and provides the most efficient method,
but not the most accurate.
ITMAX Maximum number of iteration. (Default = 10)
TOL Tolerance for convergence in iteration. (Default = 1.0e-4)
LAMBDAS Shift factor. (Default = 0.0)
KORTHO no Use mass for Gram Schmidt orthogonalization. (Default)
yes Use stiffness K for Gram Schmidt orthogonalization.
ITRPRNT no Do not print sensitivity for each iteration. (Default)
yes Print sensitivity for each iteration.
ITFPRNT no Do not print final sensitivity, leave print to SOL 200.
yes Print final sensitivity inside High’s method computation
MDOF no Do not reduce DPHI to USET ‘U6’ DOF. (Default)
yes Reduce DPHI to USET ‘U6’ DOF.
DSNOKD
Default = 0.0
DSNOKD specifies a scale factor to the differential stiffness matrix in buckling design sensitivity analysis. If
DSNOKD > 0.0, the effect of the differential stiffness matrix is included in buckling the design sensitivity
analysis.
If PARAM,DSNOKD,1.0 is specified in SOL 200, the differential stiffness sensitivity calculation is
performed more accurately; i.e., the change in the stiffness matrix due to the changes in the displacements
are computed. However, the calculation is more expensive than with PARAM,DSNOKD,0.0.
Main Index
CHAPTER 6 835
Parameter Descriptions
Non-zero values of PARAM,DSNOKD cannot be used in SOL 200 with multiple buckling design subcases
less each subcase contains the same STATSUB command.
DSO
Default = value of PARAM,DBALL
Specifies the DBset location to store datablocks created for design sensitivity and optimization in SOL 200.
DSZERO
Default = 0.0
DSZERO specifies the minimum absolute value for the printout of design sensitivities.
DV3PASS
Integer, Default = 1 for SOL 200 with nonlinear property sensitivity evaluation.
DV3PASS controls the number of optimizer internal cycles must pass before the re-evaluation of sensitivity
of nonlinear properties, such as I1/I2/J of PBARL/PBEAML/PBRSECT/PBMSECT. With default value of
1, the sensitivity of nonlinear properties is computed for every internal cycle of optimizer. Setting DV3PASS
to 10 causes the sensitivity to be evaluated at optimizer internal cycles of 1, 11, 21 and etc. The sensitivity
of nonlinear properties is considered as invariants if a sufficiently large number, such as 100, is assigned to
DV3PASS.
DYNSPCF
Default = NEW
PARAM,DYNSPCF,NEW requests that mass and damping coupled to ground be included in the SPCForce
calculations for the linear dynamic solutions: SOLs 103, 107 through 112, 115, 118, 145, 146, and 200.
OLD neglects these effects and gives the same SPCForce results obtained in versions prior to Version 68.
Note: Some versions of Dytran have trouble with permanent constraints and issue a bogus error
message in the d3hsp file. This is the case for MSC Nastran 2005 r2.
EIGFILT
Default=1.0E-13
Threshold for zero-frequency eigenvalue for ACMS VERSION=NEW (module ACMS1).
ENFMETH
Default = TOTAL or ABS
This parameter controls the solution method when dynamic enforced motion analysis via SPC/SPCD is used
in SOLs 108, 109, 111, 112, 146 and 200.
The total solution of a dynamic enforced motion analysis using SPC/SPCD can be regarded as a combination
of a static enforced motion solution (similar to what is done in SOL 101) and a dynamic enforced motion
solution that is relative to this static-based solution. The default value of TOTAL/ABS implies that the
Main Index
836 MSC Nastran Quick Reference Guide
Parameter Descriptions
program solves directly, in one step, for the TOTAL solution of the dynamic analysis which includes both the
static-based solution and the dynamic solution that is relative to the static-based solution. If the value is
specified as REL, then the program obtains the total solution of the dynamic analysis in two steps, by first
solving for the static-based solution and then solving separately for the dynamic solution RELATIVE to the
static-based solution. In general, the TOTAL/ABS and REL solution methods both yield essentially the same
results.
The TOTAL/ABS solution method is computationally more efficient. This is also the only method that is
meaningful and that should be employed when a problem involves the use of NOLINi or NLRGAP entries.
An important point to note regarding this method is that, for modal dynamic analysis, residual vectors are
absolutely critical in order for this method to get correct answers.
The REL solution method, though less efficient, may be more accurate for transient solutions and for modal
frequency response solutions at very low forcing frequencies. Also, for modal dynamic analysis, this method
is not as critically dependent on residual vectors as the TOTAL/ABS solution method. In addition, the
current implementation of the REL solution method does not support fluid DOFs with enforced motion.
So, if fluid DOF are among the DOFs with enforced motion, the job will be switched to the ABS solution
method automatically.
It should be emphasized here that PARAM,ENFMETH and PARAM,ENFMOTN are completely separate,
distinct and independent of each other and should not to be confused with each other. The former controls
the solution method when dynamic enforced motion analysis via SPC/SPCD is used while the latter controls
how the results of such an analysis are output.
ENFMOTN
Default = TOTAL or ABS
This parameter controls how the results of the analysis are output when dynamic enforced motion analysis
via SPC/SPCD is used in SOLs 108, 109, 111, 112, 146 and 200.
The total solution of a dynamic enforced motion analysis using SPC/SPCD can be regarded as a combination
of a static enforced motion solution (similar to what is done in SOL 101) and a dynamic enforced motion
solution that is relative to this static solution. The default value of TOTAL/ABS implies that the output
results of the analysis represent the TOTAL solution of the dynamic analysis which includes both the static
solution and the dynamic solution that is relative to this static solution. If the value is specified as REL, then
the output results represent the dynamic solution RELATIVE to the static solution.
It should be noted that, in general, the static solution mentioned above may not be a stress-free solution.
Therefore, in general, the usage of PARAM,ENFMOTN,TOTAL (or ABS) and PARAM,ENFMOTN,REL
in an SPC/SPCD enforced motion analysis may give different results not only for displacements, but also for
stresses.
In general, it is not easy to identify all cases wherein the static solution represents a stress-free solution.
However, one can give examples of such cases.
Thus, for instance, if the SPC/SPCD enforced motion is specified at a single grid point and there are no
constraints at any other grid point, then the static solution will be a stress-free solution.
Similarly, if the SPC/SPCD enforced motion is specified at more than one grid point for a specific grid point
component, but the magnitude and direction of the enforced motion is the same for all of the enforced
Main Index
CHAPTER 6 837
Parameter Descriptions
motion points and there are no other constraints in the model, then all of the enforced motion points will
move in unison and the static solution will be a stress-free solution.
In contrast to the above, consider the situation in which the SPC/SPCD enforced motion is specified at more
than one grid point for a specific grid point component, but the magnitude and direction of the specified
enforced motion is different for the various enforced motion points. In this case, the static solution will not
be a stress-free solution.
If the static solution represents a stress-free solution, then it can be regarded as the base motion of the model.
In such cases, the usage of PARAM,ENFMOTN,TOTAL (or ABS) and PARAM,ENFMOTN,REL will give
different displacements, but the same stresses. Further, in modal dynamic analysis for such cases, the results
using PARAM,ENFMOTN,TOTAL (or ABS) will give the same results as those obtained by using the large
mass approach with all zero (or nearly zero) frequency modes included and the results using
PARAM,ENFMOTN,REL will give the same results as those obtained by using the large mass approach with
all zero (or nearly zero) frequency modes excluded.
If the static solution does not represent a stress-free solution, , the usage of PARAM,ENFMOTN,TOTAL
(or ABS) and PARAM,ENFMOTN,REL will give different results not only for displacements, but also for
stresses. In this case, the results from the usage of PARAM,ENFMOTN,REL do not have the same
significance as in the case of the stress-free static solution except for the fact that these results represent the
dynamic solution RELATIVE to the static solution.
Note: Currently, the usage of PARAM,ENFMOTN,REL is not supported when
PARAM,ENFMETH,ABS is specified (or implied). If this usage is employed, the program
terminates the execution with an appropriate fatal message.
EPPRT
Default = 1.E-8
EPPRT is analogous to and described under the EPSSING keyword on the AUTOSPC Case Control
command. The specification of the AUTOSPC command overrides the specification of PARAM,EPPRT.
EPSILONT
Default = SECANT
In nonlinear statics (SOL 106 and SOL 400), thermal loads are computed using the secant method:
T = load T load – T ref – init T init – T ref
If the parameter is set to INTEGRAL, thermal loads are computed using the integral method:
T load
T = T dT
T init
Main Index
838 MSC Nastran Quick Reference Guide
Parameter Descriptions
This parameter only applies to SOLs 106 and 400 ANALYSIS=NLSTAT, and only applies to CQUAD4,
CTRIA3, CQUADR, and CTRIAR elements that are not associated with the enhanced nonlinear materials
(PSHLN1).
EPZERO
Default = 1.E-8
EPZERO is analogous to and described under the EPS keyword on the AUTOSPC Case Control command.
The specification of the AUTOSPC command overrides the specification of PARAM,EPZERO.
ERPC
Default = 1.0
This parameter represents the phase speed of the fluid for Equivalent Radiated Power (ERP) analysis. This
parameter may alternatively be set using the ERP Case Control command.
ERPREFDB
Default = 1.0
This parameter represents a peak reference ERP value used in the computation of ERP in units of dB. The
dB level is defined as:
ERP
ERPdB = 10log RHOCP ------------------------------
ERPREFDB
This parameter may alternatively be set using the ERP Case Control command.
ERPRHO
Default = 1.0
This parameter represents the fluid density for Equivalent Radiated Power (ERP) analysis. This parameter
may alternatively be set using the ERP Case Control command.
ERPRLF
Default = 1.0
This parameter represents a Radiation Loss Factor scale factor for the Equivalent Radiated Power (ERP)
analysis. This parameter may alternatively be set using the ERP Case Control command.
ERROR
Default = -1
For SOLs 111-112, when the constraint modes have non-zero generalized force the parameter ERROR set
to 0 causes the fatal error exit to be branched over and the dynamic response is computed and output. This
option is intended for model checkout work, where bad results are better for diagnostic work than no results
at all. This parameter is a traditional feature also used in other, similar circumstances.
ESLFSAV
Character, Default = NO
Main Index
CHAPTER 6 839
Parameter Descriptions
ESLFSAV = YES requests that all the intermediate files from an ESLNRO job be saved on disk. The
destination of these files can be directed with the ‘sdir=’ option on a Nastran submittal command line.
ESLMOVE
Integer, Default = 0
ESLMOVE = 0 selects a move limit scheme that poses restrict lower and upper bounds on design variables
during the linear response optimization. The range of the bounds is determined by
L L
X k = max X o X k – 1 – MOVE
U U
X k = min X o X k – 1 + MOVE
MOVE = max DXMIN abs X k – 1 DELXESL
ESLMOVE = 1 selects a move limit scheme that scales back the design move proposed from a linear response
optimization. The amount of scaling back is determined by
* 1
X k = X k – 1 + X k – 1 – X k – 1 DELXESL
*
where X k is the scaled design variable for the k-th design cycle, X k – 1 is the design variable at (k-1)th design
1
cycle, X k – 1 is the proposed design from the linear optimization solution at (k-1)th design cycle.
Parameters DXMIN and DELXESL can be specified on the DOPTPRM entry.
ESLLCOMP
Default = No
ESLLCOMP selects types of compliance response to be included in the design task. The nonlinear
compliance response is defined using a DRESP1 entry with RTYPE=COMP for the ESLNRO topology
optimization tasks. As the default, it is computed by the product of the applied nonlinear loads and
corresponding nonlinear displacement components. Alternatively, ESLLCOMP=YES selects a linear
compliance response that computed as the total work done by the equivalent static loads on the linear system.
ESLMPC1
Default = 0
This parameter applies only to the ESLNRO jobs with 3D contact. Its default has different meanings
depending on the type of contact applications. As the default, for a glued contact ESLNRO job, a linear
response optimization task will include a set of MPC entries that are created from the nonlinear analysis. For
Main Index
840 MSC Nastran Quick Reference Guide
Parameter Descriptions
a touching contact ESLNRO job, the linear response optimization task will not include the MPC entries by
default. Setting ESLMPC1 to a positive number will turn on the MPC inclusion.
1 uses the MPC entries created from the nonlinear analysis at the converged nonlinear analysis.
2 uses the MPC entries created at the beginning of the very first nonlinear analysis.
ESLOPTEX
Default = 0
This parameter allows the user to perform an ESLNRO job at a targeted exit point. The allowable values of
ESLOPTX are listed below with their description.
0 Do not exit. Proceed with ESLNRO nonlinear response optimization.
1 Exit after the initialization of the analysis and design model but before nonlinear FE analysis
begins.
2 Exit after nonlinear FE analysis ends.
3 Exit after design constraint evaluation and screening.
ESLPRT
Default = 0
ESLPRT specifies how often the ESLNRO results are printed in the .f06 file and saved in the .xdb file. By
default, the program will print the results to the .f06 file at the first and the last design cycles and save the
results to .xdb (or .op2) at the first and last design cycles on the disk. (See ESLPRT1 for selection of result
contents.)
>0 then the results are printed at the first design cycle; at every design cycle that is a multiplier of
ESLPRT; and the last design cycle.
<0 the no results are printed and saved.
ESLPRT1
Default = 7
ESLPRT1 specifies what type of results to be written to the .f06 and to .xdb (or .op2). It may take any of the
following base values or a combination of these base values:
0 write no data
1 write the nonlinear analysis results to the .f06 file.
2 write the optimization data controlled by P1 and P2 to the .f06 file.
4 save the nonlinear analysis results to the .xdb (or .op2) file.
8 save the linear response optimization results to the .xdb (or .op2) file.
Main Index
CHAPTER 6 841
Parameter Descriptions
For example, by default, results from the nonlinear analysis, the optimization data will be written to the .f06
file and result data will be written to .xdb or .op2.
ESLRCF,user_rc_file
Character*8, must be lower case. Default = blank
ESLRCF, user_rc_file allows a user to define a custom RC file for the internally spawned jobs.
Example:
PARAM,ESLRCF,myrc
The contents of the myrc file are:
mem=200m
exe=~local_path/MSCNASTRAN
del=~local_path/SSS
The example shows the user-defined RC file, myrc, specifies its own memory allocation and its local Nastran
executable and local DMAP database.
ESLTOPCV
Default = 80
ESLTOPCV specifies an alternate convergence tolerance for an ESLNRO’s topology optimization job. An
ESLNRO’s topology optimization job will be terminated when the percentage of design variables whose
changes are less than a given value, CONVDV specified on the DOPTPRM Bulk Data entry is greater than
ESLTOPCV.
ESLUNT2
Default = 54
ESLUNT2 is a file unit number used by the nonlinear analysis and the linear response optimization runs in
an ESLNRO’s topology optimization job for the access of design variables and designed properties. It only
needs to be changed if there is a conflict with the default.
ESLUNT1
Default = 53
ESLUNT1 is a file unit number used by the linear response optimization run in an ESLNRO’s topology
optimization job for the storage of design variables and designed properties. It only needs to be changed if
there is a conflict with the default.
EST
Replaced by the ELSUM Case Control command.
EULBND
Default = ELEMENT, SOL 700 only
Defines boundary treatment for Euler boundaries.
Main Index
842 MSC Nastran Quick Reference Guide
Parameter Descriptions
Format:
PARAM,EULBND,option
EXTRAPOL The pressure that a wall or coupling surface exerts on the adjacent Euler element is
obtained from extrapolating the element pressure toward this boundary. (Character)
ELEMENT The pressure that a wall or coupling surface exerts on the adjacent Euler element equals
the pressure inside this element. (Character)
Remarks:
1. The finite volume representation in general assumes that element values are constant within each
element. While this assumption is adequate for the large majority of applications, fluid models
involving hydrostatic pressure gradients require that the pressure gradient be also recognized to exist
within the element. When element-internal hydrostatic gradients are not accounted for, the
calculation will be less accurate and will suffer from numerical symptoms like pair forming of element
pressures. By activating the option EXTRAPOL hydrostatic gradients inside the element are taken
into account. For meshes without bias, option EXTRAPOL only modifies the numerical schemes
along the boundary.
2. When coupling surfaces are used DYPARAM,FASTCOUP has to be activated as well.
EULSTRES
Default = VOLUME, SOL 700 only
Defines the update logic for stresses when material is transported in Euler elements.
Format:
PARAM,EULSTRES,option
VOLUME The pressure that a wall or coupling surface exerts on the adjacent Euler element is obtained
from extrapolating the element pressure toward this boundary. (Character)
MASS The pressure that a wall or coupling surface exerts on the adjacent Euler element equals the
pressure inside this element.
Remarks:
1. Only used for the MMSTREN solver.
2. Stresses are a material property and when material flows in or out an element the stress state in the
element is changed. This is analogous to temperature and energy. Not the temperature is transported,
but energy. After transporting energy the temperature is re-computed by dividing the energy by
element mass and specific heat. In case of stress the “energy” is given by mass times stress. After
transporting this “energy” the new stress follows by dividing it by mass. As shown in Chapter 6 of
the Theory Manual this gives a correct updating procedure for stresses. There it also proven that stress
times mass is conserved during transport.
Main Index
CHAPTER 6 843
Parameter Descriptions
3. In most simulations variations in density are small and the multiplication by mass can be replaced by
a multiplication by volume. This method is activated by option VOLUME which is the default
option. Using the MASS option may have some influence on simulations with large density
variations. The option MASS will give the most accurate results.
4. The transport logic of the effective plastic strain is identical to that of stresses. When using option
MASS the plastic strain is computed more accurately when material is compressed.
5. The (single material) Euler with strength solver makes use of the multiplication by mass. The
multiplication by volume is not implemented for this solver.
EUSUBCYC
Default = 1, SOL 700 only
Controls the maximum growth of the subcycling interval in Euler computations.
Example:
PARAM,EUSUBCYC,2
Remarks:
1. The subcycling algorithm automatically estimates the number of subcycles to be used. This is updated
throughout the calculation. This parameter controls how much the number of subcycles can grow.
For example, EUSUBCYC is set to 1, and the current number of time steps between updates of the
Euler variables. If the solver estimates that the subcycling interval should be 7, the subcycling interval
is increased by 1 until a value of 7 is reached.
2. There is no control on the amount by which the subcycling interval can decrease.
EXCLUDE
Default = 0.
PARAM, EXCLUDE, Integer. Add PARAM, EXCLUDE, n in the buckling subcase(s) to activate linear
buckling with local exclusion of differential stiffness. If n is positive, it selects the SET1 entry ID in the bulk
data that defines the list of GRID points for which differential stiffness will be ignored. If n is negative, the
absolute value selects the SET1 entry ID in the bulk data that defines the list of GRID points for which
differential stiffness will be retained.
To select the GRID points care must be exercised by the user which follow natural mesh lines as much as
possible, otherwise an element may be connected to some GRID points that have differential stiffness and
some GRID points that do not. Sometimes this is impossible to ensure, and so the transition zone between
retained-excluded differential stiffness should not be in, or close to, a region of interest. Selecting stiff
(unlikely to buckle) zones for the transition zones is also advised.
While, EXCLUDE, can occur in either Case Control or Bulk Data, for multiple buckling subcases, it must
occur in Case Control.
Main Index
844 MSC Nastran Quick Reference Guide
Parameter Descriptions
SOL105, is a linearization of a nonlinear behavior, therefore it is recommended that parts of the structure,
for which buckling is important, are in the residual or SE=0. However, if the user puts the parts of the
structure for which buckling is to be considered in a BEGIN BULK SUPER=n; then the sets must be in the
Part superelement or Module.
Multiple buckling subcases with different exclude values are allowed. For example:
DISPLACEMENT(PLOT,SORT1,REAL)=ALL
SUBCASE 1
SUBTITLE=Static Load
SPC = 2
LOAD = 2
analysis=statics
subcase 2
SUBTITLE = Buckling Subcase
SPC=2
statsub=1
analysis=buck
METHOD=105
param,exclude,-1
subcase 3
SUBTITLE = Buckling Subcase
SPC=2
analysis=buck
statsub=1
METHOD=105
param,exclude,-2
BEGIN BULK
EXTDR
Deprecated. See the EXTDRIN Case Control command description.
EXTDROUT
Deprecated. See the EXTDROUT Case Control command description.
EXTDRUNT
Deprecated. See the EXTDROUT Case Control command description.
EXTOUT
Deprecated. See the EXTSEOUT Case Control command description.
EXTRCV
Deprecated. See the EXTDRIN Case Control command description.
EXTUNIT
Default = 30.
EXTUNIT specifies the Fortran unit number for an external superelement stored on an op2 or op4 file and
is required if the default value of 30 is not desirable and a CSUPER Bulk Data entry is used to define the
external superelement in an assembly run. EXTUNIT is also required if it references an op4 file in which case
the value for the unit number must be negative.
Main Index
CHAPTER 6 845
Parameter Descriptions
F2
Default = 0.0
F2 is only used in a real eigenvalue solution. If F2 > 0.0, the program will perform a shift at that frequency
(Hz) and determine the number of modes below F2, then terminate.
FACTOR
Default = 10000
See OLDSEQ.
FASTFR
Default = AUTO
In MSC Nastran 2004, the FASTFR method was introduced for modal frequency response analysis. It can
be selected via the Bulk Data entry, PARAM,FASTFR,YES and shows significant performance improvement
for certain models in the mid-frequency range. PARAM,FASTFR,NO deselects the FASTFR method causing
the program to use the standard method for modal frequency analysis.
By default, the program will decide automatically which solution method will be most efficient for the
frequency response part in a SOL 111 analysis. Based on the size of the modal space and some other heuristic
criteria, either the FASTFR solution method will be run, or the FRRD1 module with or without the iterative
solver will be used.
Limitations for the FASTFR method
1. The FASTFR method works only for SOL 111 and for SOL 200 with ANALYSIS=MFREQ.
2. SESDAMP and FASTFR are not allowed in the same run.
3. To force the iterative solver in FRRD1, FASTFR=yes is required.
FBATOLR
Default = 1.0E-05
This is the tolerance that is applied to grid point coordinates in order to determine connections between
potential connection grid points of various FRF components in the FBA process.
The default tolerance should be satisfactory for most situations. A looser tolerance may be needed in certain
situations. An example is the case where the potential connection points of an FRF component are associated
with the shell elements of RSSCON solid-to-shell element connectors. In this case, a looser tolerance may
need to be specified in order to achieve proper connections between FRF components in the FBA process.
FBLEND
Default = 0.6667, SOL 700 only
Eulerian elements with uncovered fractions smaller than FBLEND are blended with adjacent elements to
form a clump so that they do not control the time step.
Main Index
846 MSC Nastran Quick Reference Guide
Parameter Descriptions
Format:
PARAM,FBLEND,VALUE
Example:
PARAM,FBLEND,0.5
VALUE The uncovered fraction below which blending occurs. (0.0 < Real < 1.0)
Remarks:
1. The default value is satisfactory for virtually all calculations.
2. Elements are blended only if they would have controlled the time step otherwise.
3. Elements with uncovered fractions greater than FBLEND are not blended and are allowed to control
the time step.
4. Large values of FBLEND produce a larger time step but many blends. Small values produce a smaller
time step and fewer blends.
5. In a calculation with a coupling surface, STEPFCT is smaller or equal FBLEND to avoid instabilities
(see PARAM,STEPFCT).
FDRLDS
Default = YES
PARAM, FDRLDS, YES turns on the logic to generate additional residual vectors for SOL 111 based on the
differences of structural and structural damping matrices. For free-free models, a SUPORT entry may
improve the free-free modes and yield additional augmented eigenvalues (PARAM, BAILOUT, -1 may
occasionally be needed even for a good static SUPORT set). PARAM, FDRLDS, NO can be used to turn off
the generation of frequency dependent residual vectors.
FIRSTKI
PARAM, FIRSTKI, Integer
This parameter is specified when external superelements are used in assembly models of aircraft. This lists the
location of the first k-set point of the first CAEROi point related to each superelement, SEID.
For example, if superelement 10 (SEID10) contains CAERO1 point 1001, and the first DOF related to this
CAERO1 point is at internal location 51 in the k-set, then this information can be obtained using "PARAM,
USETPRT, 0". This information is then added in the input .dat file using "PARAM, FIRSTKI, 51" after
"BEGIN SUPER=10" line.
FIXEDB
Default = 0
Main Index
CHAPTER 6 847
Parameter Descriptions
FIXEDB is used to reduce the cost of superelement checkout.
-2 (SOL 101 only) is used on the initial runs when the user suspects that the superelement may
contain errors and that only operations necessary for fixed-boundary solutions need be performed.
In particular, the generation of the G oa matrix is branched over in the SEKR operation and
P a is not generated in the SELR operation. These operations typically result in 50% of the
reduction cost and are not needed in the fixed-boundary data recovery operations described in the
next paragraph. After this operation has been completed, the keyword SELANG will appear in the
database dictionary, indicating that the P a stored there is incomplete, and should not be
summed into the downstream superelement, because System Fatal Message 4252 will be issued.
< -1 (SOLs 101 and 103 only) allows uncoupled solutions for any superelement with conventional
output requests. This output may be obtained as soon as the superelement is successfully generated
and reduced and does not require that the entire model be assembled. In superelement statics, the
solution is the component due to the u oo vector, i.e., a fixed-boundary solution. In superelement
modes, the solution is the uncoupled eigenvectors of the component. If PARAM,FIXEDB,-1 is
specified in the Bulk Data or in the residual structure subcase, the modes of the residual structure
will not be computed. For a printout or plotting of the component mode eigenvectors it is
recommended that PARAM,FIXEDB,-1 be specified in the Bulk Data Section or above the subcase
level in Case Control. If the modes of the residual structure are desired, then PARAM,FlXEDB,0
should be specified in the residual structure subcase. Exterior degrees-of-freedom listed on
SECSETi and SESUP entries are free, and those on SEBSETi degrees-of-freedom are fixed. Data
recovery for the residual structure should not be requested for this option.
+1 (SOL 101 only) is used after the superelement has been proven valid. In the SEKR and SELR
operations, it provides a branch over all operations already completed in the SEKR and SELR
phases and completes the generation of the G oa matrix and the boundary stiffness and load
matrices. It is also a method to recover the factor of the K oo matrix if the run aborted while
computing G oa .
FKSYMFAC
Default = 0.024
Follower force stiffness is typically unsymmetric, but in some cases making it symmetric may improve
convergence in nonlinear problems, whereas in other cases it may hinder it.
FKSYMFAC controls the symmetrization of the follower force stiffness in SOL 106 and SOL 400. If
FKSYMFAC = 1.0 is specified, the follower force stiffness K f is symmetrized as:
1 T
K fs = --- K f + K f
2
Main Index
848 MSC Nastran Quick Reference Guide
Parameter Descriptions
and the symmetric part K fs is used for efficiency. If FKSYMFAC= 0. is specified, the original follower force
stiffness K f is used. If a value of 0. < FKSYMFAC < 1. is specified, the non-symmetric part of the follower
force stiffness is calculated as:
K fn = K f – K fs
and the ratio of unsymmetry:
K fn
r = -------------
Kf
is compared with the user specified value of FKSYMFAC. The norm . is the absolute maximum number
of the matrix.
If r < FKSYMFAC, the symmetric stiffness K fs is used.
If r > FKSYMFAC, the original unsymmetric stiffness K f is used.
The default value for FKSYMFAC was determined by a parametric study and for most cases this will make
the follower force stiffness symmetric, which will give sufficiently accurate answers. The asymmetry ratio(r)
increases as geometric nonlinearity intensifies so when it becomes greater than FKSYMFAC, the
unsymmetric follower force stiffness is used.
It is considered important to retain the full unsymmetric follower force stiffness, set FKSYMFAC to zero.
The parameter FKSYMFAC is applicable to SOL 106 and SOL 400 only, all other solution sequences
symmetrize the follower force stiffness. See parameter FOLLOWK for a list of solution sequences which
calculate the follower force stiffness.
FLEXINCR
Default = NO
In SOL 144, a value of YES will cause the TRIM subcases to be ignored. Instead, the TRIM Bulk Data will
be used to obtain the set of Mach, Dynamic pressure and symmetry values for Unit Solutions (Flexible
Increments). These data can be archived in the aeroelastic database for subsequent reuse. (Flexible Increments
are always computed. This param merely avoids the TRIM subcase if these increments are all that is required.)
FLUIDMP
Replaced by options on the Case Control command FLSPOUT (Case).
FLUIDNE
Default = 500
The Householder method of eigenvalue extraction is more reliable and is automatically selected for the fluid’s
system modes if the acoustic cavity is defined in a superelement and there exists fluid boundary points. The
switch to Householder occurs if the number of estimated fluid modes is less than or equal to the value
specified by PARAMeter FLUIDNE.
Main Index
CHAPTER 6 849
Parameter Descriptions
FLUIDSE
Default = 0
PARAM,FLUIDSE,seidf specifies a special superelement reserved for fluid elements. Frequency dependent
fluid elements must still be in the residual. Partitioned superelements are not supported.
FMULTI
Default = .10, SOL 700 only
Defines the dimension of the multimaterial element array.
Format:
PARAM,FMULTI,VALUE
Example:
PARAM,FMULTI,.25
VALUE The relative amount of multimaterial elements. (0.0 < Real < 1.0)
Remark:
The multimaterial Eulerian elements use an overflow array in which to store material data. This array can
hold FMULTI times the total number of Eulerian elements. In a problem where more than 10% of the
elements have more than one material, the default value of FMULTI must be increased.
FOLLOWK
Default = YES
In SOLs 101,103, 105, 106, 107, 108, 109, 110, 111, 112, 115, 116, and SOL 400, FOLLOWK=YES
(Default) requests the inclusion of follower force stiffness in the differential stiffness. FOLLOWK=NO
requests that the follower force stiffness not be included. For FOLLOWK=YES in SOLs 101,103, 105, 107,
108, 109, 110, 111, 112, 115, and 116, a separate static subcase is required and the STATSUB command is
also required in the eigenvalue subcase. In nonlinear analysis (SOL 106 and 400), the follower force is
included if PARAM,LGDISP,1 is specified. FOLLOWK is ignored in SOL 106 and SOL 400 if LGDISP is
not specified.
FRQDEPO
Default = NO
By default, frequency-dependent elements cannot be connected to o-set degrees-of-freedom.
PARAM,FRQDEPO,YES allows frequency-dependent elements to be connected to o-set
degrees-of-freedom. However, results may not be reliable.
FREQTOL
Real, default = 1.E-8 - see RMSPRMDS
Main Index
850 MSC Nastran Quick Reference Guide
Parameter Descriptions
FULLSEDR
Default = NO
In a run with superelements, PARAM,FULLSEDR,YES will merge results (DISPL, STRESS, etc.) from all
of superelements into a single result as if the run contained no superelements. This is not supported for
BEGIN BULK superelements (parts) unless the element and grid identification numbers are unique across
all part superelements and the residual structure. Additionally, if there are part SE present, then FULLSEDR
has to be specified in all Bulk Data sections (BEGIN BULK and BEGIN SUPER) or in the Case Control.
FZERO
Default = 1.0
See AUTOSPRT.
G, GFL
Default = 0.0
G and GFL specify the uniform structural and fluid-damping coefficient in the formulation of dynamics
problems. In coupled fluid-structure analysis, G is applied to the structural portion of the model and GFL
to the fluid portion of the model. To obtain the value for the parameter G or GFL, multiply the critical
damping ratio, C/Co, by 2.0. PARAM,G and GFL are not recommended for use in hydroelastic or
heat-transfer problems. If PARAM,G (or GFL) is used in transient analysis, PARAM,W3 (or W3FL) must
be greater than zero or PARAM,G (or GFL) will be ignored. See Formulation of Dynamic Equations in SubDMAP
GMA in the MSC Nastran Reference Guide.
In frequency response and complex eigenvalue analyses, the use of G or GFL will cause the stiffness matrix
corresponding to the structural or fluid portion of the model to become complex. The user should be aware
that this will, in general, require more memory and resources for the calculations.
GEOMU
Default = 40
See POST=0.
GPECT
Default = -1
GPECT controls the printout of all elements connected to each grid point. GPECT=+1 requests the
printout. In superelement analysis, the list is printed if PARAM,CHECKOUT,YES is specified or the SEMG
or SEALL Case Control command selects the superelement. GPECT=-1 suppresses the printout.
GRADMESH
Default = OFF, SOL 700 only
Glues fine meshes to coarse meshes. See the section on Graded meshes in the user manual for further
information.
Main Index
CHAPTER 6 851
Parameter Descriptions
Format:
PARAM,GRADMESH,OPTION
Example:
PARAM,GRADMESH,MINVOL
OPTION OFF Graded mesh gluing is not used (Character)
MINVOL If an element of one mesh is covered by an element of another mesh the
element with the largest volume will be inactivated. It will also be removed
from the output request for Eulerian archives.
ELNUM If an element of one mesh is covered by an element of another mesh the
element with the smallest element number will be inactivated. It will also be
removed from the output request for Eulerian archives.
Remarks:
1. This parameter can be used to build block-structured meshes.
2. All Euler elements have to be either orthogonal or axial symmetric.
3. To get meaningful physical results, the change in mesh size going from one element to the next should
not be larger than 1.4 or smaller than 0.7.
GRAVSET
Default = 0
A PARAM, GRAVSET, n where n is a Bulk Data SET1 entry, allows the user to apply gravity loading
(GRAV) to just a portion of the structure. GRAVSET like GRAV loading is global and is computed once at
the beginning of the analysis. The Bulk Data SET1 n defines the GRIDS to which the gravity loading is to
be applied. GRAVSET can appear in either the Bulk Data or ABOVE or IN the 1st Subcase. A GRAVSET
appearing in any other Subcase will be ignored and may cause incorrect results. A GRAVSET appearing in
or above the first subcase takes precedence over a GRAVSET appearing in Bulk Data. See also the companion
RFORSET entry. If there is no GRAV loading called out, then PARAM, GRAVSET, n needs to be removed
from the run
GRDPNT
Default = -1
GRDPNT > -1 will cause the grid point weight generator to be executed. The default value
(GRDPNT = -1) suppresses the computation and output of this data. GRDPNT specifies the identification
number of the grid point to be used as a reference point. If GRDPNT = 0 or is not a defined grid point, the
reference point is taken as the origin of the basic coordinate system. All fluid-related masses and masses on
scalar points are ignored. The following weight and balance information is automatically printed following
the execution of the grid point weight generator.
Reference point.
Rigid body mass matrix [MO] relative to the reference point in the basic coordinate system.
Main Index
852 MSC Nastran Quick Reference Guide
Parameter Descriptions
Transformation matrix [S] from the basic coordinate system to principal mass axes.
Principal masses (mass) and associated centers of gravity (X-C.G., Y-C.G., Z-C.G.).
Inertia matrix I(S) about the center of gravity relative to the principal mass axes. Note: Change the
signs of the off-diagonal terms to produce the “inertia tensor.”
Principal inertias I(Q) about the center of gravity.
Transformation matrix [Q] between S-axes and Q-axes. The columns of [Q] are the unit direction
vectors for the corresponding principal inertias.
In superelement static or geometric nonlinear analysis, GRDPNT > -1 also specifies the grid point to be used
in computing resultants, in the basic coordinate system, of external loads and single point constraint forces
applied to each superelement. If GRDPNT is not a grid point (including the default value of -1), then the
resultants are computed about the origin of the basic coordinate system. In superelement analysis, weights
and resultants are computed for each superelement without the effects of its upstream superelements.
For axisymmetric elements, the GRDPNT output may be misleading as the algorithm is designed for 3D
elements. For the TRIAX6 element, the mass is for the entire model and the center of gravity and inertias are
for the cross section in the x-z plane. For the hyperelastic TRIAX and QUADX elements, the mass is for one
radian and the center of gravity and inertias are for the cross section in the x-y plane. For the harmonic
TRIAX and QUADX elements, the mass is for the entire model and the center of gravity and inertias are for
the cross section in the element coordinate system x-y plane.
GUSTAERO
Default = 1
If gust loads are to be computed, for example on restart, set GUSTAERO to -1. The default is recommended
if no gust loads are to be computed after the flutter analysis.
GYROAVG
Default = 0
Used to specify one of two formulations for frequency response analysis using the rotor dynamic capability.
The default is to determine any frequency-dependent terms for each frequency. This option activates the
frequency-dependent looping option. Setting the value < 0 uses an ‘average’ frequency formulation. This
option avoids using the frequency-dependent looping and results in a shorter execution time. For this option,
parameters WR3, WR4 or WHR must be specified to include rotor damping. See RSPINR Remark 10.
GYROFATL
Default = -1
GYROFATL gives an option to override the rotor check fatal message to continue the rotordynamic analysis.
Coupling the rotor and the stator without proper element, such as RBE, spring, damper, etc., may result in
incorrect results, and a fatal message will be generated by the default value (-1) or setting a negative value
(< 0).
If the value >=0, a warning message, instead of a fatal message, will be generated during rotor checking to
remind the user for possible incorrect rotordynamic analysis results and the run will continue.
HEATSTAT
Main Index
CHAPTER 6 853
Parameter Descriptions
Default = NO
In SOL 101, if PARAM,HEATSTAT,YES is entered, then temperatures are computed in a linear steady state
heat transfer and then applied as thermal loads in a subsequent thermal stress analysis. Two subcases are
required. The first defines the temperature loads, boundary conditions, and output requests for the heat
transfer analysis and the second subcase defines the thermal loads, boundary conditions, and output requests
for the thermal stress analysis. Thermal loads in the second subcase are requested through the command
HFREQ, HFREQFL
Default = 1.+30
The parameters LFREQ, HFREQ, LFREQFL, and HFREQFL specify the frequency range in cycles per unit
time of the modes to be used in the modal formulations. (LFREQ and LFREQFL are the lower limits and
HFREQ and HFREQFL are the upper limits). In coupled fluid-structure analysis, HFREQ and LFREQ are
applied to the structural portion of the model and HFREQFL and LFREQFL are applied to fluid portion of
the model. The default for HFREQ and HFREQFL will usually include all vectors computed. Related
parameters are LMODES and LMODESFL.
Note: If the MODESELECT Case Control command is used, it takes precedence over the
parameters LMODES, LFREQ and HFREQ (or LMODESFL, LFREQFL and HFREQFL if
MODESELECT refers to fluid modes). For the hierarchy of usage when the MODESELECT
Case Control command is used in conjunction with these parameters, refer to the Remarks in
the description of the MODESELECT Case Control command. See also the FLSFSEL Case
Control command for an alternative selection.
HTOCITS
Default = 20 (SOL 106 only)
HTOCITS sets the maximum allowable iterations in a hot-to-cold analysis. (See the
ANALYSIS=HOT2COLD Case Control command).
HTOCPRT
Default = NO (SOL 106 only)
PARAM,HTOCPRT,YES requests the printout of the final cold shape’s grid locations in a hot-to-cold
analysis. (See the ANALYSIS=HOT2COLD Case Control command).
HTOCTOL
Default = 1.E-2 (SOL 106 only)
HTOCTOL is used to determine convergence of cold shape in hot-to-cold analysis. (See the
ANALYSIS=HOT2COLD Case Control command). The parameter is used to compare the geometries as
the model deforms from its “hot” to “cold” shape.
HTSYM
Default = 0
Main Index
854 MSC Nastran Quick Reference Guide
Parameter Descriptions
This parameter controls the decomposition method for SOL 400 thermal analysis.
=0 Use symmetric decomposition solver
=1 Use unsymmetric decomposition solver
ICOPT
Default = 1, SOL 400 Only
Parameter ICOPT works together with the NLIC Case Control Command. The user input loads may or may
not be in equilibrium with the initial condition. If ICOPT=0, MSC Nastran will compute the initial
acceleration based on user’s inputs. Otherwise, it will be assumed that the initial acceleration is null. In other
words, when ICOPT=1 (the default), it is assumed the whole structure is in equilibrium automatically.
Theoretically, ICOPT=0 gives better solution. However, due to that the matrix is highly singular, a large
amount CPU time may be required and the accuracy of the result may be in doubt for the solution with
ICOPT=0.
IFP
Default = value of PARAM,DBALL.
See DBALL.
INREL
Default = 0
INREL controls the calculation of inertia relief or enforced acceleration in linear static analysis and buckling.
INREL = -1, -2, or -4 requests that inertia relief or enforced acceleration be performed.
For INREL= -1 and -2, enforced accelerations, if desired, are input on the DMIG,UACCEL Bulk Data entry.
(See Section 7.2 of the MSC Nastran Reference Guide for the theoretical basis.)
Inertia Relief is not currently supported with external superelements and in the contact analysis.
-1 SUPORT or SUPORT1 entries are required on one or more grid points in the Bulk Data Section
which restrain rigid body motion. The total number of degrees-of-freedom specified on
SUPORT and SUPORT1 entries must be less than or equal to six.
In SOL 105, SUPORT1, not SUPORT, Bulk Data entries must be used to define the supported
degrees-of-freedom and the SUPORT1 Case Control command may only be specified in a
separate static subcase.
Loads due to unit rigid body accelerations at the point referenced by PARAM,GRDPNT are
computed and then appended to the external loads. If PARAM,GRDPNT is specified in
superelement analysis, then the point must be interior to the residual structure and exterior to all
superelements.
Main Index
CHAPTER 6 855
Parameter Descriptions
-2 The value of PARAM,INREL,-2 will provide an inertia relief analysis without the use of
SUPORTi entries. To use this capability the structure must contain six and only six rigid body
degrees of freedom. SUPORTi entries must not be present when using this option. If the
structure has either more or less then six rigid body degrees of freedom, the analysis will either fail
or give incorrect results.
-4 SUPORT or SUPORT1 entries are required on one or more grid points in the Bulk Data Section
which restrain rigid body motion. Any number of degrees-of-freedom may be specified on
SUPORT and SUPORT1 entries. With this method, the mass matrix is reduced which will
increase CPU requirements over PARAM,INREL,-1 and -2. The INREL=-4 method is a general
approach and is capable of handling mechanisms and unconstrained problems. It is also capable
of handling problems that have possible rigid body motion in selected directions.
The INREL=-1 and -2 methods are more efficient implementation but are limited to six or less
supported degrees-of-freedom because those methods can only handle problems that are fully
unconstrained (that is, those with no constraints preventing rigid body motion of any kind and
whose model does not contain mechanisms).
INRLM
Replaced by the INRLOD keyword on the RESVEC Case Control command.
IRES
Default = -1
IRES=1 requests that the residual load vectors RULV and RUOV be output in all solution sequences. In
superelement analysis, the parameters PRPA and PRPJ may also be used to request output of the partial load
vectors P a and P j , respectively. In geometric nonlinear analysis, PARAM,IRES,1 will cause the
printing of the residual vector
n+1
P f = K ff u f – uf + Ff – Pf
ITAPE
Default = -1
ITAPE specifies the output status of the DSCMR matrix in SOLs 101, 103, and 105; and the DSCMCOL
table and the DSCM2 matrix in SOL 200. (See the OUTPUT2 and OUTPUT4 module descriptions in the
MSC Nastran DMAP Programmer’s Guide.)
IUNIT
Default = 11
IUNIT specifies the FORTRAN unit number on which the DSCMR matrix in Design Sensitivity SOLs 101,
103, and 105 and the DSCMCOL table and the DSCM2 matrix in SOL 200 will be written. (See the
OUTPUT2 and OUTPUT4 module descriptions in the MSC Nastran DMAP Programmer’s Guide.)
Main Index
856 MSC Nastran Quick Reference Guide
Parameter Descriptions
IEVLOCK
Default=0
Real coupled modes computation uses subspace iteration method. With default IEVLOCK=0, the subspace
iteration continues with the problem size as twice of ND (number of modes requested) until all ND
eigenmodes are converged. If IEVLOCK=1, subspace iteration method turns on eigenvector locking method
during iteration. The eigenvector locking method will lock the eigenvectors already converged within the
locking window size (0.5*number of modes requested) and iterate non-converged eigenvector with additional
random vectors until all ND are found. This will help to reduce the problem size during subspace iteration
and may reduce total performance elapse time.
JWLDET
Default=NOLINK
With the default multiple denotations with EOSJWL are NOT LINKED: the detonation wave of one
explosive cannot ignite another explosive. When the option is LINK, multiple denotations with EOSJWL
are LINKED: the detonation wave of one explosive can ignite another explosive. For option NOLINK:
TDET is set to -1 for elements that have no JWL material. The “NOLINK” option is only valid with true
JWL materials - not valid for the “Static Detonation/Ideal Gas” model. Setting this parameter as “NOLINK”
will prevent “sympathetic ignition”. Each charge will ignite at the specified “TDET” in its own DETSPH
card.
KDAMP, KDAMPFL
Default = 1
If KDAMP or KDAMPFL is set to -1, viscous modal damping is entered into the complex stiffness matrix as
structural damping. In coupled fluid-structure analysis, KDAMP is applied to the structural portion of the
model and KDAMPFL to the fluid portion of the model. See Superelement Analysis in the MSC Nastran
Reference Guide.
KDIAG
Default = -1.0 (SOLs 106, 153, and SOL 400 with non-contact analysis), or 0.0 ( SOL 400 with contact
analysis)
In SOLs 106 (nonlinear static analysis), 153 (steady state heat transfer), and SOL 400 (nonlinear static and
transient analysis), KDIAG may be used to eliminate spurious mechanisms and singularities in the nonlinear
stiffness matrix. The absolute value of KDIAG will be added to some or all of the diagonal terms in the
nonlinear stiffness matrix as follows:
< 0.0 Then add the absolute value of KDIAG to the null diagonal terms only (SOLs 106 and 153).
For SOL 400, the absolute value of KDIAG is added to the diagonal term of null columns
only.
= 0.0 Then no action is taken.
> 0.0 Then add the value of KDIAG to all diagonal terms.
Main Index
CHAPTER 6 857
Parameter Descriptions
KDMFILT
Default = 0
0 Differential stiffness correction will NOT be added to rigid body behavior of pre-stressed
models for modal analysis.
1 Differential stiffness correction will be added to rigid body behavior of pre-stressed models
for modal analysis.
2 If KDMFILT=1 does not provide the desired rigid body modes, KDMFILT=2 may be tried;
it requests an alternative READ rigid body modes method based on filtering the K and M
based on null columns.
1. Currently, PARAM, KDMFILT, 1 is active in SOL103 with a preload subcase (STATSUB) and a
single modal (METHOD) subcase.
2. Currently, PARAM, KDMFILT, 1 is active in SOL400 with a series of preload steps and a single
ANALYSIS=MODES step. Also, in SOL400, the correction is not available when enhanced
nonlinear elements are used via NLMOPTS or PSHLN1, etc., type entries.
In nonlinear mechanics, in theory a tangent matrix is computed, using a deformation gradient. By polar
decomposition, a consistent rotation matrix can be obtained.
In practice, most finite elements such as beam, shell and solid elements, are developed in a heuristic fashion
with polynomial type functions representing displacement and volume characteristics. The tangent stiffness
is composed of several matrices. A linear K matrix, a KD for differential stiffness or geometric stiffness, and
often a KF for follower load stiffness.
In general, the KD matrix which represents a stiffening to the structure due to pre-load of the structure, does
not meet rigid body requirements. When a structure is preloaded with a self-equilibrating set of loads and
statically supported, for a free-free modal analysis of the pre-loaded structure the static support set is removed.
Often because of the deficiency of the KD matrix to correctly represent rigid body modes, the resulting free-
free modes are poor or missing.
PARAM, KDMFILT, 1 turns on a method to orthagonalize and normalize the computed rigid-body modes.
Main Index
858 MSC Nastran Quick Reference Guide
Parameter Descriptions
It cannot be over emphasized the importance of the need to have a self-equilibrating set of loads using a static
support system.
The above structure represents a plate structure to be tension pre-stressed in the x-direction. This is
accomplished by applying FORCE1 entries on grids 111 through 121 in the positive x-direction defined by
grids 1 through 11 to grids 111 to 121 and a set of FORCE1 entries along grids 1 through 11 in the negative
x-direction defined by grids 111 through 121 to grids 1 through 11.
A static support set is applied at grids 1, 11, and 111. This set is removed for the modal analysis.
If, instead of the FORCE1 entries along grids 1 through 11, the user chose to apply SPC1 entries for these
grids, constraining then in the x-direction, a self-equilibrating loading would not be obtained. This is so,
because FORCE1 entries are follower loads while SPC1 entries are not. With the SPC1 entries, the structure
would not be in true static equilibrium upon removal to the static support set.
If, instead, along grids 1 through 11, the user chose to apply SPC1 entries for these grids, constraining then
in the x-direction and non-follower FORCE entries along the grids 111 through 121, an almost self-
equilibrating loading is achieved and PARAM, KDMFILT, 1 will get six good free-free modes. In this case,
however, the Lanczos Method has some stability issues and AHOU should be used.
K4RITZ
Default = 0
Setting PARAM,K4RITZ to a positive value activates logic to generate additional residual vectors for SOL
111 when using ACMS to compute the modal space. Structural damping degrees of freedom (K4) are used
to augment the existing set of residual vectors in order to capture damping effects when GE inputs might
contribute significantly to overall frequency response. The value of K4RITZ specifically controls the number
of iterations performed to compute the basis vectors. Due to extra computation required, this parameter
should be used with caution and should rarely be set greater than 1.
K6ROT
Default = 100.
K6ROT specifies the scaling factor of the penalty stiffness to be added to the normal rotation for CQUAD4
and CTRIA3 elements. The contribution of the penalty term to the strain energy functional is
Main Index
CHAPTER 6 859
Parameter Descriptions
–6 1 2 1 u y u x
p = 10 K6ROT --- G z – z tdA with z = --- -------- – --------
2 2 x y
A
where A is the area of the shell element, t is the shell thickness, G is the in plane shear modulus, see the
MID1 material identification number on the PSHELL Bulk Data entry. The in plane displacements u x u y
and the normal rotation z are shown in Figure 6-1. The normal rotation has no physical meaning and
should be ignored. The penalty stiffness removes the singularity in the normal rotation. A higher value than
K6ROT=100. is not recommended because unwanted stiffening effects may occur. If you use only the
MID1field, Nastran automatically sets K6ROT=0.0
z 4 3
uy
z
y
1
x ux 2
Figure 6-1 In plane displacements u x u y and normal rotation z
LANGLE
Default = 1
LANGLE specifies the method for processing large rotations in nonlinear analysis. By default, large rotations
are computed with the gimbal angle method in nonlinear analyses SOLs 106, 129, 153, and 159 with
geometric nonlinearity (PARAM,LGDlSP,1). If PARAM,LANGLE,2 is specified, then they are computed
with the Rotation Vector method. The value of LANGLE cannot be changed in a subsequent restart. For
SOL 400, users should not use LANGLE. SOL 400 will use the appropriate method depending on type of
element or type of analysis.
LDSUM
Default = 0
Dictates what trim information is to be stored on a CSV (comma separated values) file in a SOL 144 (static
aeroelasticity) task. The unit the CSV file is stored to is specified by PARAM, XYUNIT, n. LDSUM has the
following options:
0 (Default) – Do not create a CSV file for static aeroelasticity
1 Create a CSV file that contains for each static aeroelastic subcase:
Subcase ID
Main Index
860 MSC Nastran Quick Reference Guide
Parameter Descriptions
Mach number
Dynamic Pressure
Trim Values
Mass and CG information (mass, xcg,ycg,zcg, IXX,IYY,IZZ,IXY,IXZ and IYZ)
2 Same as 1 plus net structural monitor point (MONPNT1, MONDSP1, MONPNT2,
MONPNT3) results.
3 Same as 2 plus the output of RIGID AIR, ELASTIC RESTRAINED, and INERTIAL, RIGID
APPLIED and ELASTIC APPLIED components for the structural MONPNT1 results.
4 Same as 3 plus the output of RIGID AIR and ELASTIC RESTRAINED components for
aerodynamic MONPNT1 results.
LFREQ, LFREQFL
Default = 0.0
See HFREQ, HFREQFL
If the MODESELECT Case Control command is used, it takes precedence over the parameters LMODES,
LFREQ and HFREQ (or LMODESFL, LFREQFL and HFREQFL if MODESELECT refers to fluid
modes). For the hierarchy of usage when the MODESELECT Case Control command is used in conjunction
with these parameters, refer to the Remarks in the description of the MODESELECT Case Control
command. See also the FLSFSEL Case Control command for an alternative selection.
LGDISP
LGDISP is a global parameter. For the case with multiple LGDISP definitions, Nastran will use the first
definition for all the subcases and steps. Default = -1
>0 The differential stiffness for structural elements is computed for the linear elements and added
to the differential stiffness of the nonlinear elements.
1 All the nonlinear structural element types that have a large displacement capability in SOLs 106,
129, 153, 159 and SOL 400 (see Table 3-1, under “Geometric Nonlinear” in the MSC Nastran
Reference Guide) will be assumed to have large displacement effects (updated element coordinates
and follower forces). For simultaneous multi-physics coupling analysis defined through the
SUBSTEP Case Control option in SOL 400, nonlinear heat transfer element types will be
treated the same as LGDISP = -1 (i.e., original geometry for thermal stiffness, element fluxes and
external loads).
-1 No large displacement effects will be considered.
2 Follower force for structural elements effects will be ignored but large displacement effects will
be considered. For simultaneous multi-physics coupling analysis defined through the SUBSTEP
Case Control option in SOL 400, nonlinear heat transfer element types will be treated the same
as LGDISP = -1 (i.e., original geometry for thermal stiffness, element fluxes and external loads).
Main Index
CHAPTER 6 861
Parameter Descriptions
11 Nonlinear structural elements will be treated the same as LGDISP = 1 in all supporting solution
sequences.For simultaneous multi-physics coupling analysis defined through the SUBSTEP
Case Control option in SOL 400, nonlinear heat transfer element types will be based on the
current updated geometry (updated element coordinates for the thermal stiffness, element fluxes
and external loads).
12 Nonlinear structural elements will be treated the same as LGDISP = 2 in all supporting solution
sequences. For simultaneous multi-physics coupling analysis defined through the SUBSTEP
Case Control option in SOL 400, nonlinear heat transfer element types will be based on updated
current geometry (updated element coordinates for the thermal stiffness and element fluxes,
original geometry for external loads).
LMFACT
LMFACT and PENFN are the scale factor and penalty function for the Lagrange rigid elements and the
contact analysis. For Lagrange rigid elements, please see Case Control command, RIGID. The purpose of
LMFACT and PENFN is to make the values of stiffness matrix of the Lagrange rigid elements and/or the
contact components about the same relative magnitude as those of the other elements in the model. Too small
a value will produce inaccurate results and too large a value will produce numerical difficulties. The same
value is usually assigned to both LMFACT and PENFN. Under special requirement, user may assign different
values for LMFACT and PENFN. For example, if PENFN=0.0 and LMFACT 0.0 , then the solution
method for the rigid elements becomes the pure Lagrange multiplier method instead of the augmented
Lagrangian method. However, user must exercise caution if different values are assigned to LMFACT and
PENFN. MSC Nastran will compute the appropriate default values for LMFACT and PENFN. The default
value is 1.0e+5 for all solution sequences except SOL 400 and SOL 101 contact.
For SOL 400 and SOL 101 contact, MSC Nastran will compute the appropriate default values for LMFACT
and PENFN. These defaults are currently calculated as 0.05% of the average stiffness of the diagonal terms
of the stiffness matrix. This computed default is good in general. But when the material/element stiffnesses
(e.g., Young’s Modulus, Spring Stiffnesses) used in the model vary in a wide range, users may have to adjust
the computed LMFACT and PENFN. Note that the computed LMFACT, PENFN are printed out in a .f06
file. It is generally recommended that for these cases, the LMFACT and PENFN should be reduced by several
orders of magnitude to avoid numerical difficulty.
If in a coupled multi-physics analysis distinct values for LMFACT and PENFN are desired for each physics
pass, the parameter definitions must be made inside the SUBSTEP Case Control command. If no values are
entered each physics pass computes its own defaults.
LMODES, LMODESFL
Default = 0
LMODES and LMODESFL are the number of lowest modes to use in a modal formulation. In coupled
fluid-structure analysis, LMODES specifies the lowest modes of the structural portion of the model and
LMODESFL the modes of the fluid portion of the model. If LMODES (or LMODESFL) = 0, the retained
modes are determined by the parameters LFREQ and HFREQ (or LFREQFL and HFREQFL).
In SOL 103, LMODES may be used to reduce the number of eigenvectors to be processed in data recovery
which may significantly reduce the CPU and storage costs.
Main Index
862 MSC Nastran Quick Reference Guide
Parameter Descriptions
Note: If the MODESELECT Case Control command is used, it takes precedence over the
parameters LMODES, LFREQ and HFREQ (or LMODESFL, LFREQFL and HFREQFL if
MODESELECT refers to fluid modes). For the hierarchy of usage when the MODESELECT
Case Control command is used in conjunction with these parameters, refer to the Remarks in
the description of the MODESELECT Case Control command. See also the FLSFSEL Case
Control command for an alternative selection.
LOADU
Default = -1
See POST=0.
LOOPID
Default = 0
LOOPID defines the desired loop number for initial conditions in a restart of SOLs 106, 129, 153, and 159.
By default in SOLs 106 and 153 the restart proceeds from the last loop ID of the subcase defined by
SUBCASID or SUBID. In SOLs 106, and 153 PARAM,SUBID or SUBCASID may also be specified.
LSTRN
Replaced by the STRAIN Case Control command.
MACH
Default = 0.0
Mach number. If more than one Mach number was used to compute aerodynamic matrices, the one closest
to MACH will be used in dynamic aeroelastic response analysis. The default causes the matrices computed
at the lowest MACH number to be used.
MAXACCPT
Default = 1.0E+9
If potential singularities are found and MECHOUT is YES, this is the maximum acceptable value of the
matrix diagonal to factor diagonal ratio. If the maximum ratio exceeds this value, even if the matrix condition
number is less than MAXCOND, the run will fail.
MAXAPL
Default = 1000
MAXAPL specifies the maximum number of applied loads to be used as a basis for residual vector
calculations. If the number of applied loads exceeds MAXAPL, User Warning Message 9166 is issued, and
residual vector augmentation is disabled. Note that the computing requirements for a large number of
residual vectors can be prohibitive. See also, the RESVEC Case Control command.
MAXCOND
Default = 1.E+11
Main Index
CHAPTER 6 863
Parameter Descriptions
Maximum acceptable value of the condition number of the stiffness matrix if decomposition of the stiffness
matrix indicates potential singularities.
MAXDAMP
Default = 1000
See BEIGRED.
MAXLP
Default = 5
MAXLP specifies the maximum number of iterations for element relaxation and material point subincrement
processes in SOLs 129 and 159. MAXLP is 10 in SOLs 106 and 153 and cannot be changed by the user.
MAXMECHS
Default = 24
Maximum number of potential mechanism and/or rigid body modes to be output if decomposition of the
stiffness matrix indicates potential singularities.
MAXRATIO
Default = 1.E7
The ratios of terms on the diagonal of the stiffness matrix to the corresponding terms on the diagonal of the
triangular factor are computed. If, for any row, this ratio is greater than MAXRATIO, the matrix will be
considered to be nearly singular (having mechanisms). If any diagonal terms of the factor are negative, the
stiffness matrix is considered implausible (non-positive definite). The ratios greater than MAXRATIO and
less than zero and their associated external grid identities will be printed out. The program will then take
appropriate action as directed by the parameter BAILOUT.
By default, in the superelement solution sequences the program will terminate processing for that
superelement. A negative value for BAILOUT directs the program to continue processing the superelement.
Although forcing the program to continue with near-singularities is a useful modeling checkout technique,
it may lead to solutions of poor quality or fatal messages later in the run. It is recommended that the default
values be used for production runs. A related parameter is ERROR.
The value -1 of BAILOUT causes the program to continue processing with near singularities and a zero value
will cause the program to exit if near singularities are detected.
In SOLs 101 through 200 when PARAM,CHECKOUT,YES is specified, PARAM,MAXRATIO sets the
tolerance for detecting multipoint constraint equations with poor linear independence. (See Superelement
Analysis in the MSC Nastran Reference Guide.)
BAILOUT and MAXRATIO may be specified in the Case Control Section in order to provide different
values between superelements but not between different boundary conditions.
MDK4OPT
Default = 1
Main Index
864 MSC Nastran Quick Reference Guide
Parameter Descriptions
Performance parameter used in MDACMS for the calculation of K4. If MDK4OPT>0 the most common
value of GE for structure elements will be internally applied to PARAM,G to speed up the calculation of K4.
Set MDK4OPT to 0 to disable this feature. The traditional K4 calculation will be used instead.
MDOPT14
Default = YES
Option 14 of the MDENZO functional module modifies degree of freedom (DOF) based domain
decomposition such that DOF belonging to any one grid point are retained in a single domain. This action
(PARAM,MDOPT14,YES) lends stability to the resulting solution at the possible expense of some efficiency.
Setting MDOPT14 to NO bypasses this operation so that DOF may be distributed to any domain without
restriction. This parameter applies to Matrix Domain ACMS.
MDOTM
Default = AUTO
The default selects the most efficient method for data recovery in DOMAINSOLVER ACMS
(PARTOPT=DOF). There are two methods: (1) Output transformation matrix (OTM) method is selected
if the number of modes multiplied by PARAM,MDOTMFAC (Default = 20) exceeds the number of degrees-
of-freedom at which displacements are required in order to complete data recovery (DISP, STRESS, etc.)
This method also requires PARAM,SPARSEPH,YES which is the default. This method may be forced with
PARAM,MDOTM,YES. (2) If the number of modes multiplied by PARAM,MDOTMFAC (Default = 20)
does not exceed the number of degrees-of-freedom at which displacements are required in order to complete
data recovery condition is not satisfied then the non-OTM method is selected. This method may be forced
with PARAM,MDOTM,NO.
MDOTMFAC
Default = 20
See MDOTM.
MDREDOPT
Default = -1
This parameter is used in ACMS for matrix reduction operations. It affects the way in which matrices are
reduced to modal coordinates. Quantities affected are damping, loads, and acoustic coupling. By default, the
ACMS-generated Q-size matrices are reduced to H-size (modal coordinates). This is the most efficient
method. If MDREDOPT=1, a triple matrix multiplication is used.
MECHFIL
Default = 1.E-6
Criterion for discarding massless mechanism modes with small generalized mass. A smaller value will result
in more marginal constraint modes being retained. This parameter is used for PARAM,MMMETH,OLD.
See also MECHFIX, MMMETH, and MMFIL.
MECHFIX
Default = AUTO
Main Index
CHAPTER 6 865
Parameter Descriptions
Control for fixing the massless mechanism problem. This capability is provided automatically for the default
of this parameter, listed above. This capability is executed only when the eigensolution does not provide
answers because of symptoms consistent with the presence of massless mechanisms. If MECHFIX is set to
YES, the constraint modes are removed before attempting an eigensolution. When set to NO, the capability
is blocked, the eigensolution will fail, and User Fatal Message 9117 will be printed in the F06 file. See also
MMFIL and MMMETH.
MECHOUT
Default = 'YES'
Character parameter indicating whether potential mechanisms and/or rigid-body modes should be output
when decomposition of the stiffness matrix indicates potential singularities.
MECHPRT
Default = NO
For SOL 103 only, if massless mechanisms are found the constraint modes are printed with a format similar
to eigenvectors when this parameter is set to YES. They are labeled CONSTRAINT MODES, and are
numbered sequentially. Grid points with only zero values in a mode are not printed. This parameter should
be used when performing initial checkout of a model and a goal is to remove all massless mechanisms before
starting production analysis. The number of each “mode” matches the corresponding GID,C pair in the high
ratio message. If there are many (thousands) of such modes the output file will be large. There is no method
to plot these shapes at present.
MESH
Default = NO
If MESH=YES is specified, then a summary of the shading status and the subelement mesh for each CHBDYi
element referencing a VIEW Bulk Data entry is printed.
METHCMRS
Default = 0
In dynamic analysis (SOLs 103, 107, 108, 109, 110, 111, 112, 145, 146, and 200), METHCMRS specifies
the set identification number of an EIGR or EIGRL entry to be used in the calculation of the normal modes
on the v-set of the residual structure.
By default, the residual structure v-set normal modes will be computed based on the METHOD Case
Control command selection as long as q-set is present.
MHRED
Default = YES
MHRED=YES, selects the c-set and r-set component mode reduction method suggested by Dr. Arya Majed
and Ed Henkel. See the MSC Nastran V2004 Release Guide for details.
MICRO
Default = 10, SOL 700 only
Main Index
866 MSC Nastran Quick Reference Guide
Parameter Descriptions
Defines the accuracy of the initial conditions in Eulerian elements, when using the geometrical shape
definition.
Format:
PARAM,MICRO,VALUE
Example:
PARAM,MICRO,15
VALUE Micro-zoning parameter. (Integer > 0)
Remarks:
1. MICRO is the number of micro zones into which an element is subdivided during initial condition
generation.
2. The default MICRO = 10 results in material fractions as accurate as 0.001. If a higher accuracy is
required, a greater value for MICRO can be used, but the CPU time for the generation increases
rapidly.
3. Micro zoning is only used when the initial conditions of the Eulerian material are specified on a
TICEUL1 entry.
MIDNODE
Default = 0, SOL 200 only
=0 High order element mid-side grid is updated by shape basis vectors.
=1 High order element mid-side grid is smoothed by algorithm 1.
=2 High order element mid-side grid is smoothed by algorithm 2 (most robust).
MINIGOA
Default = NO
Allows for the reduction in the amount of disk space used when using superelements. When this parameter
is set to YES, the transformation matrix GOA will contain terms only for the degrees-of-freedom in the U5
(USET, USET1, SEUSET, SEUSET1) set. This can allow for a significant reduction in the amount of disk
space used by the database. The limitation of using this approach is that data recovery will be available only
for these degrees-of-freedom and elements connected to them.
MINORTHO
Default = 0.9
When Mode Mapping is used, this is the minimum acceptable cross-orthogonality between the baseline and
current modes. If this minimum is not met, the program will terminate with a fatal error.
Main Index
CHAPTER 6 867
Parameter Descriptions
MINORTHR
Default = 0.7
When Mode Mapping is used, this is the minimum acceptable cross-orthogonality between residual vectors
in the baseline and current run. As residual vectors are not necessarily modes, the cross-orthogonality criteria
is relaxed for them.
MMFIL
Default = 1.E-10
Filter value used to distinguish between massless mechanism modes and rigid body modes. A smaller value
may discard rigid body modes. The default value has been effective on all problems solved to date. This
parameter is used for PARAM,MMMETH,NEW and PARAM,MMMETH,BETA. See also MMMETH.
MMMETH
Default = BETA
Selects method for searching for massless mechanisms. The default value is generally the most reliable
method. Use PARAM,MMMETH,NEW to invoke an older procedure that can sometimes find massless
mechanisms when the default does not find any. Specify PARAM,MMMETH,OLD to use the original
procedure. See also MECHFIX.
MODACC
Default = -1
0 Selects the mode acceleration method for data recovery in dynamic analysis. See Formulation
of Dynamic Equations in SubDMAP GMA in the MSC Nastran Reference Guide for further discussion.
If PARAM,SPARSEDR,NO is specified, then PARAM,DDRMM,-1 must also be specified.
1 Is the same as MODACC = 0 except if SUPORTi entries are present then the displacements
are corrected for rigid body motion and the local flexibility at the SUPORTi degrees-of-
freedom.
>0 Is not recommended for use in hydroelastic problems.
MODEL
Default = 0
This parameter also allows several models to be stored in the same graphics database created by
PARAM,POST,0.
MP1SET
Character “F” or “G” (default, see below)
Controls the integration set used in the calculation of MONPNT1 results. For the value of “F”, the integrated
values will reflect any redistribution of loads caused by rigid elements and MPCs. This is particularly useful
in the static aeroelastic solution sequences (SOL 144) when RBE3s are used to distribute mass, applied loads
Main Index
868 MSC Nastran Quick Reference Guide
Parameter Descriptions
and splining. For the value of “G”, no redistribution occurs. The default is a function of the solution
sequence.
SOL 144 - Default = “F”, option “G” is not available.
All other sequences - Default = “G”, option “F” can be specified by the user.
MPCX
Default = 0
See OLDSEQ.
MPTUNIT
Default=0
MPTUNIT is used in conjunction with an FMS ASSIGN statement to specify the unit number for the
storage of monitor points results in OUTPUT2 format in SOL 146. Default=0 indicates that no monitor
point data are to be stored.
MSG10625
Default=0
0 USER FATAL MESSAGE 10625 will stop any frequency response run with frequency
dependent elements, with the DMAP path PARAM, BUSHNM, YES (default) if
multiple subcases with different Case Control FREQ=n are detected.
1 The run will be allowed to proceed.
The frequency dependent path BUSHNM, NO path is only viable when the frequency dependences are
specified on the PBUSHT, PELAST, PDAMPT, PAABSF.
When the frequency dependences include MATiF entries, only the path PARAM, BUSHNM, YES path is
viable. This path is also viable only for new features such as extended GEij on MAT2 or MAT9 entries, or
the use of PDISTB/PDISTBM entries. The frequency dependences provided by PBUSHT, PELAST,
PDAMPT, PAABSF also work for this path. Also, since the required element level K, K4, B matrices
required for frequency dependency are computed in a completely different manner between PARAM,
BUSHNM, YES/NO paths, the GPFORCE calculation is only available in the new PARAM, BUSHNM,
YES path.
When the path PARAM, BUSHNM, YES has any type of frequency dependency, several new solution
techniques are turned on. These include, by default, the use of master frequencies and extended residual
vector calculations. Also, via PARAM, NMNLFRQ, value, in modal frequency the eigenvalue analysis may
be performed using material stiffness values other than the base values defined on the basic MATi entries.
Automatic Master frequencies, controlled via the Case Control MFREQ, are based on the presence of
MAT1F, MAT2F, MAT8F, MAT9F, PBUSHT, PELAST, PDAMPT entries and their associated TABLEDi
entries.
For each forcing frequency corresponding to a determined master frequency, MSC Nastran forms complete
element stiffness, structural damping and viscous damping matrices based on material and property table
lookup at that frequency.
Main Index
CHAPTER 6 869
Parameter Descriptions
For forcing frequencies between master frequencies, the fully assembled g or modal sized stiffness, structural
damping, and viscous damping matrices are computed by interpolation.
When multiple subcases are present, and these subcases have different FREQ=n selection, MASTER
frequencies, computed based on the first subcase, may not have good correlation with forcing frequencies in
subsequent subcases. Thus, USER FATAL MESSAGE 10625 will be issued by default.
MXICODE0
Default = 5
In nonlinear harmonic response analysis, if the solution fails to converge more than MXICODE0 times in
succession, a new trial displacement vector is calculated.
MXLAGM1
Default = 0.0
MXLAGM1 is to override the maximum Lagrange Multiplier that is used by the merit function in Trust
Region.
NASPRT
Default = 0
NASPRT specifies how often data recovery is performed and printed in SOL 200. By default, SOL 200, in
addition to performing an analysis and optimization, will perform full data recovery operations at the first
design cycle and upon completion of the last design cycle.
If NASPRT > 0, then data recovery operations are performed at the first design cycle; at every design cycle
that is a multiple of NASPRT; and the last design cycle. For example, if PARAM,NASPRT,2 and the
maximum number of design iterations requested is 5, then data recovery is obtained at design iterations 1, 2,
4, and 5.
If NASPRT < 0, then no data recovery operations are performed.
NDAMP, NDAMPM
NDAMP:
Default = 0.01 for SOLs 129 and 159, -0.05 for SOL 400 heat transfer and mechanical non-contact analysis,
0.0 for SOL 400 contact.
NDAMPM:
Default = 0.0 for SOL 400 non-contact, 1.0 for SOL 400 contact. Not used for SOL 400 heat transfer.
NDAMP/NDAMPM:
In SOLs 129 and 159, numerical damping may be specified for the METHODS =“ADAPT” on the entry
through the NDAMP entry in order to achieve numerical stability. A value of zero for NDAMP requests no
numerical damping. The recommended range of NDAMP values is from 0.0 to 0.1.
Main Index
870 MSC Nastran Quick Reference Guide
Parameter Descriptions
SOL 400 Mechanical: In SOL 400, numerical damping may be specified for all METHODS (ADAPT, FNT,
etc. on the entry. NDAMP and NDAMPM are two parameters that control the damping scheme and thee
associated dynamic operator. The equilibrium equation for the most general operator (the Generalized-
operator) is given by
int ext
Mu··n + 1 + + Cu· n + 1 + + F n + 1 + = F n + 1 +
m f f f
where m is NDAMPM and f is NDAMP. In the previous equation, a typical quantity F n + 1 + is
given by the expanded form
F n + 1 + = 1 + F n + 1 – F n
Depending on the values of NDAMP and NDAMPM, the equilibrium equations can reduce to the HHT-
scheme (NDAMPM = 0) or the WBZ- scheme (NDAMP = 0) or the Generalized- scheme
( NDAMPM 0 , NDAMP 0 ). For the HHT- scheme, NDAMP can vary in the range of
– 0.33 NDAMP 0.0 . For the WBZ- scheme, NDAMPM can vary in the range of
0.0 NDAMPM 1.0 . For the Generalized- scheme, NDAMP can vary in the range of
– 0.5 NDAMP 0.0 and NDAMPM in the range of – 0.5 NDAMPM 1.0 .
For problems involving no contact, the HHT- is used in SOL 400 with default NDAMP = -0.05 and
NDAMPM = 0.0 except that the model is linear, or no mass and no damping matrix. In this case, the defaults
are NDAMP = 0.0 and NDAMPM = 0.0. For problems involving contact, the WBZ- scheme is used in
SOL 400 with default NDAMPM = 1.0 and NDAMP = 0.0
SOL 400 Heat Transfer: Numerical damping may be specified through the value of NDAMP only.
NDAMPM is not used. NDAMP can be varied in the range of (-2.414,0.414). At these outer limits, the
transient scheme reduces to the Backward-Euler method. Any value that is outside this range is automatically
reset to the closest outer limit. For NDAMP = 0.0, the transient scheme reduces to the Crank-Nicholson
scheme. The default value of NDAMP is -0.05.
SOL 400 Thermo-Mechanical Coupled Analysis: If NDAMP and NDAMPM are unspecified, then the
default that is appropriate for the particular sub-step is used. For e.g., for a coupled transient contact problem,
NDMAP = -0.05 during the heat transfer sub-step and NDAMP = 0.0, NDAMPM = 1.0 during the
mechanical sub-step. If the values of NDAMP and NDAMPM are specified by the user in the Bulk Data
Section, then these values would be applicable for both the thermal and mechanical sub-steps. To make the
values of the NDAMP/NDAMPM physics-dependent, the user can define the values under each sub-step of
the Case Control Section. E.g.,
SUBSTEP 1
ANALYSIS=HTRAN
PARAM,NDAMP,-2.414
SUBSTEP 2
ANALYSIS=NLTRAN
PARAM,NDAMP,-0.05
PARAM,NDAMPM,0.0
Main Index
CHAPTER 6 871
Parameter Descriptions
NEWMARK
Default = NO
See CQC under SCRSPEC.
NFDOPTS
Default = 2
PARAM, NFDOPTS, 2 computes frequency dependent matrices at master frequencies. In general, master
frequencies via MFREQ in case control section of input deck is less than the number of forcing frequencies.
Hence, PARAM, NFDOPTS, 2 can improve performance as well as reduce disk space requirement for large
frequency response jobs. With PARAM, NFDOPTS, 1, frequency dependent matrices are computed at
forcing frequencies.
NHPLUS
Default = 20
In nonlinear harmonic response analysis, in order to avoid aliasing in the calculation of the Fourier
coefficients, a certain number of extra evaluation points are used. NHPLUS allows the number of extra points
to be defined.
NINTPTS
Default = 10
N1NTPTS requests interpolation over the NlNTPTS elements closest to each grid point. NlNTPTS=0
requests interpolation over all elements, which can be computationally intensive. Related parameters include
BlGER, CURV, NUMOUT, OG, OUTOPT, S1G, S1M, S1AG and S1AM.
NLAYERS
Default = 5 for CQUAD4 and CTRIAR, 7 for CQUADR and CTRIAR, 3 for CAXISYM (minimum=1,
maximum=12) (SOLs 106, 129, 153, 159, and 400)
NLAYERS is used in material nonlinear analysis only and is the number of layers used to integrate through
the thickness of CQUAD4, CTRlA3 CQUADR, CTRIAR and CAXISYM elements with isotropic material
properties. Set NLAYERS=1 for efficiency if no bending is selected (MID2=0 or -1 on all PSHELL entries).
Do not specify NLAYERS=1 if MID2 is greater than zero. A larger value of NLAYERS will give greater
accuracy at the cost of computing time and storage requirements. For CQUADR and CTRIAR, the
maximum is 11.
NLHTLS
Default = 0
See Remarks under Case Control command, TSTRU (Case).
NLHTOL
Default = 1.0E-5
Main Index
872 MSC Nastran Quick Reference Guide
Parameter Descriptions
During the iteration procedure of nonlinear harmonic response, the norm of the residual load vector for the
current step is divided by the norm of the residual load vector for the previously converged step; this value is
then compared with NLHTOL. If the value is smaller than NLHTOL, the system is assumed to have
converged.
NLHTWK
Default = 1.0E-5
In nonlinear harmonic response analysis, if convergence is not obtained, a line search procedure is initiated
to calculate a scaling factor for the displacement vector from which updated nonlinear loads are subsequently
calculated. If the solution fails to converge more than 5 times in succession a new trial displacement vector is
calculated using a push off factor the size of which is defined by NLHTWK. See also parameter MXICODE0.
NLMAX
Default = 60
The number of suspected massless mechanisms is determined from the number of high ratio messages. If this
number exceeds NLMAX, the number of trial massless mechanisms is reduced to NLMAX. This avoids an
expensive debug run when there may be thousands of massless mechanisms due to systematic modeling error,
such as having CONM2 elements on many grid points for which structural elements have been left out
through oversight. The value of this parameter may be increased on initial debug runs where many high ratio
DOFs may be present, and the user prefers to see them all at once, rather than on successive runs where only
a part are removed at one time. See also MECHFIX.
NLMIN
Default = 10
In the case of only one or a few high ratio DOFs, more MMs may be present resulting in more trial MM
vectors being used, and those trial vectors that do not indicate true problems are discarded by the code. A
smaller value could be considered on a stable model undergoing small modeling changes. See also MECHFIX.
NLPACK
Default=100
NLPACK is used in the nonlinear solution sequence SOL 400 with ANALYSIS=NLTRAN for transient
analysis only.
In transient analysis SOL 400 will pack output data and restart data for NLPACK output time steps together
at the last time step as a single data package. For example, if NLPACK=100 (the default), then one data
package have output data for 100 output time steps and restart data for the last time step. Later usage such
as restart or initial condition for later step can be performed only at data package boundaries. If NLPACK=
-1, all output data for a STEP and restart data for end of the STEP are grouped into a single package. In this
case, the restart can be performed only at STEP boundaries. NLPACK=0 is illegal. If NLPACK=1, each
package of data on the database includes output data for one output time step and restart data. In this case,
restart can be performed at every output time step. Please note that the output time step is controlled by the
NO field on the Bulk Data entry, or NO filed of FIXED time step control as well INTOUT field of ADAPT
Main Index
CHAPTER 6 873
Parameter Descriptions
time step control in NLSTEP Bulk Data entry. NLPACK also influences the intermediate output selected by
NLOPRM.
Please note that NLPACK is based on the number of the output load steps (concerning INTOUT in
NLSTEP, and so on), but not the number of the calculated load steps. For example, one NLTRAN analysis
has NLSTEP as:
NLSTEP,900,0.2
,fixed,2000,20
,mech,u
It has total 2000 increments, and asks output every 20 increments. Therefore, total output is 100 time step.
In NASTRAN, default value of NLPACK for NLTRAN is 100, in this model, therefore, NASTRAN will
write the results to OP2 after collecting 100 output, i.e., this model will write results to OP2 only one time.
With intermediate output request, only one OP2 file will be created.
If NLPACK=1, NASTRAN will write results to OP2 for every output request. In this model, NASTRAN
will write results to OP2 for every output request, i.e., writing 100 times in this model. With “intermediate
output request, 100 OP2 files will be created.
If NLPACK=2, NASTRAN will write results to OP2 for every two output requests. In this model,
NASTRAN will write results to OP2 for every two output request, i.e., writing 50 times in this model. With
"intermediate output request, 50 OP2 files will be created.
NLTOL
2 (SOL 106 and MD Nastran SOL 400)
Default =
0 (SOL 153, nonlinear heat transfer)
NLTOL establishes defaults for the CONV, EPSU, EPSP and EPSW fields of NLPARM Bulk Data entry for
nonlinear static and heat transfer analysis according to the following table:
NLTOL Level of Accuracy
0 Very high
1 High
2 Engineering Design
3 Preliminary Design
See Remark 16. of the NLPARM entry for further details and corresponding default NLPARM field values.
NMLOOP
Main Index
874 MSC Nastran Quick Reference Guide
Parameter Descriptions
Default = 0
In SOL 106 nonlinear static analysis, normal modes will be computed with the updated nonlinear stiffness
if PARAM,NMLOOP is requested in the subcase section, it must be for all subcases. The nonlinear normal
modes will be computed at the last iteration loop of each subcase in which a METHOD command appears.
NMNLFRQ
Default = 0.0
PARAM, NMNLFRQ, Real_Value allows users to select material or property values for frequency dependent
materials or properties at a desired frequency other than the “nominal” values specified on the MATi or
PBUSH, PCOMP, PCOMPG, PDAMP, or PELAS entries.
If there is only CBUSH frequency dependency and NO other type of material dependency, then Nastran will
not use/update the CBUSH properties at the specified NMNLFRQ.
NOCOMPS
Default = +1
NOCOMPS controls the computation and printout of composite element ply stresses, strains and failure
indices. If NOCOMPS = 1, composite element ply stresses, strains and failure indices are printed. If
NOCOMPS = 0, the same quantities plus element stresses and strains for the equivalent homogeneous
element are printed. If NOCOMPS=-1, only element stresses and strains are printed. MAT1, MAT2, or
MAT8 entries with MIDs>99999999 run the risk of conflicting with internally generated MAT2 entries
when composites are present and should be avoided. Even if no composites are present, MIDs>99999999
signal to shell element stress computations that no STRESS is to be computed. In the case of
MIDs>99999999 if the user desires stress calculations for shell elements, even if no composites are present,
then PARAM, NOCOMPS, -1 is required.
Homogenous stresses are based upon a smeared representation of the laminate’s properties and in general will
be incorrect. Element strains are correct however.
NOCOMPS only supports conventional elements, not advanced elements. For advanced nonlinear element,
only ply stress/strain will be output.
NODCMP
Default = 0
For some type of nonlinear transient problems, including heat transfer, the decomposition of the solution
matrix is not required. In order to increase efficiency, NODCMP is created to determine whether the solution
matrix will be decomposed. If NODCMP=0, the solution matrix will be decomposed. If NODCMP=1, the
solution matrix will NOT be decomposed. In this case, MAXBIS and DJUST on the Bulk Data entry,
NLPARM, must be set zero on the Bulk Data entry. NODCMP is available for SOL 129 and 159 only.
NOELOF
Main Index
CHAPTER 6 875
Parameter Descriptions
Default = -1
If NOELOF > 0, then the grid point forces (GPFORCE Case Control command) are computed along the
edges of the two-dimensional elements. The default value will suppress this output.
NOELOP
Default = -1
If NOELOP > 0, then the sum of the grid point forces (GPFORCE Case Control command) are computed
parallel to the edges of adjacent elements. The effect of CBAR element offsets is not considered in the
calculation of the forces. The default value will suppress this output.
NOGPF
Default = 1
NOGPF controls the printout of grid point forces (GPFORCE Case Control command). NOGPF > 0
specifies that the grid point forces are to be printed. NOGPF < 0 suppresses the printing of the grid point
forces.
NONCUP
Default = -1
In SOLs 111 and 112, NONCUP selects either a coupled or uncoupled solution algorithm in the modal
dynamic response analysis. This parameter has the following meanings in both solution sequences:
NONCUP = -1 Use the uncoupled solution algorithm if there are no off-diagonal terms in any of
(Default) the modal matrices (MHH, BHH and KHH); otherwise use the coupled solution
algorithm. However, in order to ensure correct results, the coupled solution
algorithm is used when large mass enforced displacement, large mass enforced
velocity or SPC/SPCD enforced motion is employed in SOL 112, regardless of the
existence of off-diagonal terms in the modal matrices.
If enforced motion is requested in modal transient analysis, NONCUP = 0 is the
default.
NONCUP > -1 Use the coupled solution algorithm unconditionally
NONCUP = -2 Use the uncoupled solution algorithm unconditionally
User Information Message 5222 indicates which solution algorithm is used in the analysis.
NQSET
Default = 0
If NQSET > 0, and the PARAM entry is in Case Control, all part superelements that do not contain QSET
entries, or are not referenced by SENQSET entries in the main Bulk Data Section, have NQSET generalized
coordinates assigned to them. These QSET variables are functionally equivalent to those generated by
SENQSET entries.
NUMOUT, NUMOUT1, NUMOUT2, NUMOUT3
Main Index
876 MSC Nastran Quick Reference Guide
Parameter Descriptions
See S1, S1G, S1M.
OELMOPT
Integer; Default=3.
PARAM,OELMOPT selects the class of elements to include in the search for grid points:
0 All regular elements but not PLOTEL and rigid elements.
1 All regular elements and PLOTEL.
2 All regular elements and rigid elements.
3 Both 1 and 2 (default).
OELMSET
Integer; Default = 0
Identification number of a Case Control command SET definition. The members of the specified SET
represent the identification numbers of the finite elements that are to be retained in the “reduced” op2 file
element connection data block.
OG
Default=0
See CURV.
OGEOM
Default = YES
See POST < 0.
OGRDOPT
Integer; Default = 1
Selects the method used to create the set of grid points retained in the reduced grid point geometry data block.
The default simply uses the set of grid point IDs listed in the OGRDSET Case Control SET. Set consistency
is checked. OGRDOPT=2 uses the list of grid point IDs that are connected to elements in the OELMSET
Case Control SET. OGRDOPT=3 merges the contents of the OGRDSET Case Control SET with the
contents of the grid point list connected to the elements in the OELMSET Case Control SET. There is no
consistency check for OGRDOPT=2 or OGRDOPT=3. OGRDOPT=0 turns the SET consistency check
off altogether. For this case, the grid points retained are those specified in the OGRDSET SET and the
elements retained are those specified in the OELMSET SET. See also PARAM,OELMOPT description.
OGRDSET
Integer; Default = 0
Identification number of a case control command SET definition. The members of the specified SET
represent the identification numbers of the grid points that are to be retained in the “reduced” op2 file grid
geometry data block.
Main Index
CHAPTER 6 877
Parameter Descriptions
OLDSEQ
-1 for non-iterative-distributed-parallel solutions
5 for iterative solutions using distributed parallel methods
Default =
(NASTRAN ITER=1 and system(231)>0)
6 if SUPER=2
OLDSEQ selects from the following options for resequencing:
-1 No resequencing is performed.
1 Use the active/passive option.
2 Use the band option.
3 For the active/passive and the band option select the option giving the lowest RMS value of the
active columns for each group of grid points.
4 Use the wavefront (Levy) option.
5 Use the Gibbs-King option even if the CPU estimate is higher than for nonsequencing.
6 Use the automatic nested dissection option even if the CPU estimate is higher than for no
resequencing. See the following SUPER=2 description.
8 Semiautomatic selection. The program will compute estimates for two options that are suitable
for the decomposition method selected by the PARALLEL and SPARSE keywords on the
NASTRAN statement and select the option with the lowest estimate. The following table
shows the suitable options for each decomposition method.
Decomposition Method Suitable Options
regular 1 and 4
parallel 2 and 5
sparse 6 and 7
9 The extreme partitioning method is used to partition the model into domains.
10 The METIS partitioning method is used to partition the model into domains.
11 The MSCMLV partitioning method is used to partition the model into domains.
Main Index
878 MSC Nastran Quick Reference Guide
Parameter Descriptions
Notes: 1. The model partitioning options make sense only when running with the
DOMAINSOLVER command in the Executive Control Section. For
DOMAINSOLVER (PARTOPT=GRID), param,oldseq,9 is the default. For all
other DOMAINSOLVER options, the default is param,oldseq,11.
2. The wavefront option does not support superelement resequencing or starting nodes.
Also note that the automatic nested dissection option uses starting nodes only to
establish the root of the initial connectivity tree.
If the value of OLDSEQ is changed in superelement analysis, an SEALL=ALL restart is required.
PARAM,FACTOR is used to generate the sequenced identification number (SEQlD) on the SEQGP entry
as follows:
SEQID=FACTOR*GRP+SEQ
where:
SEQ = generated sequence number
GRP = group sequence number
If GRP=0, use GRP(MAX)+1 where GRP(MAX) is the largest group sequence number in the database.
PARAM,MPCX controls whether the grid point connectivity created by the MPC, MPCADD, and MPCAX
entries and/or the rigid element entries (e.g., RBAR) is considered during resequencing:
-1 Do not consider the connectivity of the MPC, MPCADD, MPCAX, or rigid element entries.
0 Consider the connectivity of the rigid element entries only. (Default).
>0 Consider the connectivity of the rigid element entries and the MPC, MPCADD, and MPCAX
entries with the set identification number set to the value of this parameter.
PARAM,SEQOUT controls the output options as follows:
0 Do not generate any printed or punched output for the new sequence (Default).
1 Print a table of the internal/external sequence in internal order.
2 Write the SEQGP entries to the PUNCH file.
3 Perform SEQOUT=1 and 2.
PARAM,START specifies the number of the grid points at the beginning of the input sequence. The input
sequence will be the sorted order of the grid point numbers including the effect of any SEQGP entries input
by the user. A single SEQGP entry can be input to select the starting point for the new sequence. Otherwise,
the first point of lowest connectivity will be used as the starting point.
If PARAM,SUPER<0, all grid points from the connection table that are not part of the group currently being
processed are deleted. This option provides for sequencing only the interior points of a superelement. If any
Main Index
CHAPTER 6 879
Parameter Descriptions
superelements are present, the residual structure is not resequenced. If all of the grid points are in the residual
structure, they are resequenced.
If PARAM,SUPER=0 or 1, all grid points in the connection table are considered. This option provides for
the recognition of passive columns.
If PARAM,SUPER=2, then all points that are connected to multipoint constraints (via MPC entries) or rigid
elements (e.g., the RBAR entry) are placed in a special group at the end of the sequence. This option also
forces OLDSEQ=6 and may not be selected with other values of OLDSEQ. This option is intended
primarily for models that have many active columns due to MPCs or rigid elements; e.g., a model with
disjoint structures connected only by MPCs or rigid elements.
OLDWELD
Default = NO
By default, the program uses new formulations for connector elements (CFAST, CSEAM and CWELD). To
acquire identical connector results as those from previous versions before v2017.1, specify OLDWELD=YES.
OMACHPR
Default = NO
See POST < 0.
OMAXR
Default = 2 BUFFSIZE
OMAXR specifies the maximum record length of data written by the OUTPUT2 module under
PARAM,POST,<0 and PARAM,OPTEXIT,-4. BUFFSIZE is a machine-dependent value defined in the
MSC Nastran Configuration and Operations Guide. For further information, see the OMAXR parameter
description under the OUTPUT2 module description in MSC Nastran DMAP Programmer’s Guide.
OMID
Default = NO
To print or punch the results in the material coordinate system, the following options are available:
OMID=NO; Output the standard data recovery outputs.
OMID=YES; Output the results in the Material Coordinate System.
OMID=BOTH; Output the results to the OP2 or HDF5 files in both the standard data recovery outputs form
and in the Material Coordinate System form. For option both, the F06 file will contain only the Material
Coordinate System form.
Applicable to forces, strains, and stresses for TRIA3, QUAD4, TRIAR6, and QUAD8. This is available for
linear analysis only. Other elements and outputs are not supported. This capability is not supported by grid
point stress output that assumes output is in element coordinate system, random response analysis, heat
transfer analysis, stress sorting, MAXMIN Case Control, composite elements, MONPNT3 Bulk Data and
external superelement data recovery in the assembly run.
Main Index
880 MSC Nastran Quick Reference Guide
Parameter Descriptions
OMSGLVL
Integer; Default = 0
Set consistency check error message severity flag. The default causes FATAL messages to be generated if the
grid set is not consistent with the element-related grid point set and the job is terminated. If OMSGLVL=1,
the FATAL messages are reduced to WARNINGS and the job is allowed to continue.
OP2GM34
Default = TRUE
By default, the GEOM3 and GEOM4 are written in OP2 file. To avoid GEOM3 and GEOM4 output, set
PARAM, OP2GM34, FALSE.
OP4DIGS
Default = 15 (Integer)
Controls the number of digits for the fractional part of the real values of matrix data written to an OUTPUT4
file.
OP4DIGS is the requested number of digits for the fractional part of the real values written for the ASCII
format option (FORMATTED on the ASSIGN FMS statement). The FORTRAN Format Specification
used internally by OUTPUT4 to write real values will be formed as follows:
FORTRAN Format Specification: 1P,rEw.d
d = OP4DIGS
w=d+7
r = 80/w (integer portion)
So, for the default d=15, w=15+7=22, INT(r)=INT(80/w) =3
Or, 1P,3E22.15 for the format.
OPCHSET
Integer; Default = 0
SET punch request flag. If OPCHSET=1, then the list of grid points used to reduce the grid point geometry
data block will be punched in case control SET definition format.
OPGEOM
Default = -1
OPGEOM > -1 prints the aerodynamic set definitions for all degrees-of-freedom. To print structural degree-
of-freedom sets, please see USETPRT.
Main Index
CHAPTER 6 881
Parameter Descriptions
Sequence Print USETPRT
None None (Default) -1
Row sort only 0
Internal Column sort only 1
Row and Column sort 2
Row sort only 10
External Column sort only 11
Row and Column sort 12
The USETPRT parameter description contains further explanation that is relevant to OPGEOM as well.
OPGTKG
Default = -1
OPGTKG > -1 prints the matrix for the interpolation between the structural and aerodynamic degrees-of-
freedom.
OPPHIB
Default = -1
In the flutter (SOLs 145 and 200) and dynamic aeroelastic (SOLs 146 and 200) solution sequences,
OPPHIB > -1 and a DISPLACEMENT request in the Case Control Section will output the real vibration
modes with the structural displacement components transformed to the basic coordinate system.
OPPHIPA
Default = -1
In the flutter (SOLs 145 and 200) and the dynamic aeroelastic (SOL 146) solution sequences,
OPPHIPA > -1 and a DISPLACEMENT command in the Case Control Section will output the real
structural vibration modes at all degrees-of-freedom, including the aerodynamic degrees-of-freedom in the
global coordinate system. Use PARAM,OPPHIPB to output in the basic system.
OPTEXIT
Default = 0
In SOL 200, especially during the checkout of the analysis model and the design optimization input data
(design model), it may be desirable to exit the solution sequence at certain points before proceeding with full
optimization. OPTEXIT may be set to values of 1 through 7 and -4. The DSAPRT Case Control command
overrides the specification of PARAM,OPTEXIT,4, -4, or 7. The description of OPTEXlT values follow.
Main Index
882 MSC Nastran Quick Reference Guide
Parameter Descriptions
OPTEXIT
Value Description
0 Do not exit. Proceed with optimization.
1 Exit after the initialization of the analysis and design model but before finite element
analysis begins.
2 Exit after finite element analysis and initial design response and shape basis vector
processing.
3 Exit after design constraint evaluation and screening.
4 Exit after design sensitivity analysis and print the matrix of design sensitivity coefficients
(DSCM2). This is equivalent to the DSAPRT (UNFORM,END=SENS) Case Control
command.
-4 Exit after design sensitivity analysis and write the data blocks related to sensitivity
coefficients (DSCM2 and DSCMCOL) to an external file using the OUTPUT2 and
OUTPUT4 modules. This is equivalent to the DSAPRT (NOPRINT,EXPORT
END=SENS) Case Control command. See related parameters ITAPE, IUNIT, and
OMAXR.
5 Exit after the first approximate optimization of the design model.
6 Exit after the first update of the analysis model based on the first approximate
optimization of the design model.
7 Compute and output design sensitivity coefficients at the end of normal program
termination: hard convergence, soft convergence, or maximum design cycles. This is
equivalent to the DSAPRT (UNFORM,START=LAST) Case Control command. If the
final design is a discrete design optimization, no sensitivity is performed and the
OPTEXIT=7 request is not honored.
OPTION
Default = ABS
See SCRSPEC.
OSETELE
Default = 2
See AUTOGOUT.
OSETGRD
Default = 1
See AUTOGOUT.
OSWELM
Main Index
CHAPTER 6 883
Parameter Descriptions
Default = -1
Offset for identification numbers of internally generated RBE3 rigid body elements (generated by all formats
of CFAST and CSEAM as well as CWELD with formats ELEMID, GRIDID, ELPAT and PARTPAT). By
default, OSWELM=-1, the numbering starts with SYSTEM(182) + 1. The default of system cell 182 is
SYSTEM(182)=100,001,001. If the user defines OSWELM > 0, then the numbering starts with OSWELM
+ 1.
Active ONLY for "PARAM,OLDWELD,YES", for each CWELD element, a pair of RWELD constraint
elements is generated if MSET=ON is specified, see the entry PWELD, 3329 for an explanation.
Active ONLY for "PARAM,OLDWELD,YES", in an SOL 400 nonlinear analysis this defines the offset for
identification numbers of internally generated RBE3 rigid body elements (generated by CWELD and
CFAST, all formats) and CONM2 mass elements (generated by CFAST when it has nonzero mass). The
default behavior in SOL 400 is the same as in the linear solution sequences.
OSWPPT
Integer, Default = -1
Offset for internally generated grid identification numbers for connector elements (GA and GB for CWELD
and CFAST if they are not specified and all auxiliary grids for CWELD, CFAST and CSEAM). By default,
OSWPPT=-1, the numbering starts with SYSTEM(178) + 1. The default of system cell 178 is
SYSTEM(178)=101,000,000. If the user provides OSWPPT > 0, then the numbering starts with OSWPPT
+ 1.
Active ONLY for "PARAM,OLDWELD,YES", for each CWELD or CFAST element, a pair of grid points
GA and GB is generated internally if the formats ELEMID, GRIDID, ELPAT or PARTPAT are used and if
no identification numbers for GA and GB are specified, see the entry CWELD, 1696 and CFAST, 1505 for
a definition of the formats.
Active ONLY for "PARAM,OLDWELD,YES", in an SOL 400 nonlinear analysis this defines the offset for
identification numbers of internally generated grids of connector elements CWELD and CFAST (GA and
GB if these are not specified in the bulk data input and all auxiliary grids). The default behavior in SOL 400
is the same as in the linear solution sequences.
OUGCORD
See POST.
OUGSPLIT
Default=YES
By default, displacements, velocities, and accelerations are written to separate tables.
PARAM,OUGSPLIT,NO will combine these tables into a single table and is intended for third-party post-
processors which are not able to read the separate tables. The value of OUGSPLIT does not affect the results
in the f06 file.
OUNIT1
Default = Value of OUNIT2
Main Index
884 MSC Nastran Quick Reference Guide
Parameter Descriptions
For PARAM,POST,-1 and -2 defines the unit that geometry data blocks are output to. See PARAM,POST.
This parameter should not be specified after BEGIN SUPER.
OUNIT2
Default = 12
For PARAM,POST,-1 and -2 defines the unit that results data blocks are output to. See PARAM,POST. This
parameter should not be specified after BEGIN SUPER.
OUTOPT
Default = 0
See CURV.
PACINFID
Integer, no default.
This parameter is used only in data recovery operations for elements in acoustic field point mesh bulk data.
PACINFID is the ID of the PACINF entry that contains the location of the pole used to determine element
orientation. Data recovery operations require that the element surface normal vector point away from the
pole location. This parameter is required only if the acoustic model references multiple PACINF bulk data
entries and the pole locations on the PACINF entries are not coincidental.
PANELMP
Replaced by a keyword on the FLSPOUT Case Control command.
PATPLUS
Default = NO
PARAM,PATPLUS,YES may be used with PARAM,POST,0 to allow the user to also write data related to
geometry, connectivity, and properties and results from GPFORCE, WETSENS, ELSENS, and PACCE to
a Fortran unit as is done under PARAM,POST,-1.
PATVER
Default = 3.0
See POST = -1.
PCOMPRM
Default = 0
PCOMPRM controls the computation and printout of composite element extreme ply stresses, strains,
failure Indices and strength ratios. Note that extreme ply output encompasses ply stresses, ply strains, ply
failure indices and ply strength ratios together. Punch output is not available for extreme ply results.
PCOMPRM = 0 (default) , STANDARD composite ply responses are output.
PCOMPRM = 1 STANDARD & EXTREME composite ply responses are output
PCOMPRM = 2 ONLY EXTREME composite ply responses are output
Main Index
CHAPTER 6 885
Parameter Descriptions
PDRMSG
Default = 1
PDRMSG controls the printout of messages associated with deformed plots, including error messages.
PDRMSG = 0 suppresses the printout. Contour values will not be displayed unless the default value is used.
PEMDMP
Default = 'NO'
Setting the value of character parameter PEMDMP to 'YES' (PARAM,PEMDMP,YES in bulk data) will
invoke the distributed Nastran-PEM solution logic. PEMDMP is intended for large Nastran models with
multiple PEM trim components.
The PEMDMP solution strategy is to distribute Trim Master Frequencies evenly among distributed Nastran
DMP processes. The PEMDMP solution is possible when all the following are true:
• Nastran SOL 111 solution specification
• DOMAINSOLVER ACMS is used
• Command line option "dmp=N" where N>1
• Multiple hosts; or use of RUNOPT=MULTIPAR on the DOMAINSOLVER entry (Multiple-
Parent DMP processing)
• Number of forcing frequencies greater than NDMP (number of DMP processes)
• Number of trim master frequencies greater than NDMP+1
• PARAM,PEMDMP,YES in bulk data
If one of the above items is not true, or if RUNOPT=PARCHILD is specified on the DOMAINSOLVER
entry, the PEMDMP solution is not deployed. If the PEMDMP solution is active, User Information
Messages 10544 and 10545 are printed in the F06 file. Otherwise, no messages are printed.
PEMFRIM
PARAM,PEMFRIM,1 is used to request full Reduced Impedance Matrix (RIM) from Actran, instead of
lower-triangular RIM. By default (PARAM,PEMFRIM,0), Actran returns lower-triangular RIM. Note that
PEMFRIM will increase disk space demand of PEM job. In addition, OOC field of ACPEMCP will cause
Actran to generate full RIM when set to an integer greater than 1.
PEMMAPC
PEMMAPC is used to generate lists of GRD IDs of the coupling surfaces. 'PARAM,PEMMAPC,1' (default
is 0) will produce following files in 'mapping_control' subdirectory of job submit directory.
Main Index
886 MSC Nastran Quick Reference Guide
Parameter Descriptions
For SET ID Generic File name
Structure GID coupled 100000 <deckname>.<job
with all TRMCs seq>.x_nas.structure_component1.set
Fluid GID coupled with 200000 <deckname>.<job
all TRMCs seq>.x_nas.fluid_component2.set
Structure GID coupled y00018xxxx for GLUED or <deckname>.<job seq
with TRIMID=xxxx only z00018xxxx for SLIDING >.x_nas.structure_component1.trim_coupli
ng.<xxxx>.<y or z>.set
Fluid GID coupled with Y00028xxxx for OPEN or <deckname>.<job
TRIMID=xxxx only Z00028xxxx for IMPER seq>.x_nas.fluid_component2.trim_coupli
ng.<xxxx>.<Y or Z>.set
TRIMID=xxxx GID xxxx90001 <deckname>.<job seq
coupled with structure >.x_nas.interface<xxxx>.surface.1.set
TRIMID=xxxx GID xxxx90002 <deckname>.<job seq
coupled with fluid >.x_nas.interface<xxxx>.surface.2.set
Guidelines for PARAM,PEMMAPC,1
1. PARAM,PEMMAPC,1' must be placed in the main bulk data section or under 'BEGIN BULK' to
be effective.
2. Without 'PARAM,PEMNPART,n', PEMMAPC logic has a TRIM ID limit of less than 10000.
3. With 'PARAM,PEMNPART,n', PEMMAPC login has a TRIM ID limit of less than 100.
PEMNCOP4
PARAM,PEMNCOP4,1 (default) is used to request each Reduced Impedance Matrix (RIM) from Actran to
be written into individual file. With PARAM,PEMNCOP4,0, Actran writes all RIMs into a single file. Note
that PARAM,PEMNCOP4,1 can reduce footprint on disk space of large PEM jobs.
PEMNPART
PEMNPART can be utilized to partition a large trim component. The default value for PEMNPART is 1.
'PARAM,PEMNPART,n' will partition a large trim component into 'n' parts. The guidelines are:
1. PARAM,PEMNPART,n' must be placed under 'BEGIN TRMC=xx' to be effective for trim
component 'xx'.
2. Each trim component can have its own 'PARAM,PEMNPART,n'
3. When value of 'n' for PEMNPART is greater than 1, new trim components are generated with ID
equal to 'xx'*100+<seq no> where <seq no> goes from 0 to n-1.
4. For no loss of accuracy, setting 'n' to a value equal to the number of disconnected parts of a large trim
component.
5. For accepting loss of accuracy to run on a machine with limited memory, setting 'n' to a value larger
than the number of disconnected parts of a large trim component.
Main Index
CHAPTER 6 887
Parameter Descriptions
6. 'PARAM,PEMNPART,n' with n>1 should be utilized only as an alternative for running PEM jobs
with large trim component and insufficient memory on the computer. Other alternatives for running
PEM job with large trim component and insufficient memory are:
a. Split large trim component into smaller trim components and/or
b. Acquire more memory for the computer
7. For a trim component with 'PARAM,PEMNPART,n' where n>1 and 'PARAM,TRMBIM,physical',
data recovery will be skipped for all partitioned trim components.
PEMSKIN
‘PARAM,PEMSKIN,1’ is used for Actran to couple the trim bodies only to the surface of the cavity and will
not search any node inside the cavities. The default value for PEMSKIN is 0 which allows Actran to target
both surface and interior nodes of the cavities for trim bodies coupling.
PENFN
Default = 1.0e+5 (See LMFACT)
PERCENT
Default = 40
See CQC under SCRSPEC.
PH2OUT
Default = 0, SOL 400 only
For nonlinear solution sequence, SOL 400, in addition to the regular phase III output, the user can also
request the phase II output. This is useful when the run is terminated abnormally before the phase III outputs
are formatted and printed. The phase II output consists of all outputs requested by the Case Control
commands in the input file and prints in sort1 format. If there’s no PH2OUT, MSC Nastran outputs phase
III outputs only. This is the regular output. If PH2OUT=1, MSC Nastran outputs phase II outputs only.
In this case, there will be no output for the upstream superelements. If PH2OUT=3, MSC Nastran outputs
both phase II and phase III outputs. In this case, some of the outputs for the residual structure may be
redundant.
Case Control command, NLOPRM OUTCTRL, takes precedence over PH2OUT. In other words, when
NLOPRM OUTCTRL is present, PH2OUT is no longer functional. NLOPRM OUTCTRL=SOLUTION
is equivalent to PH2OUT=1 and NLOPRM OUTCTRL=(STD,SOLUTION) to PH2OUT=3.
PKRSP
Default = -1
If PKRSP=0, the magnitude of the output quantities at the time of peak acceleration of the modal variables
is output. This option is available only for modal transient analysis.
PLTMSG
Default = 1
Main Index
888 MSC Nastran Quick Reference Guide
Parameter Descriptions
PARAM,PLTMSG,0 suppresses messages associated with undeformed plot requests, including error
messages.
POST
Default = 9999999
If PARAM,POST,0, then the following parameters and discussion apply (not support in SOL 400):
The data blocks often used for pre- and postprocessing will be stored in the database and also converted, by
the DBC module (see MSC Nastran DMAP Programmer’s Guide), to a format suitable for processing by MSC
Patran. These data blocks include input data related to geometry, connectivity, element and material
properties, and static loads; they also include output data requested through the Case Control commands
OLOAD, SPCF, DISP, VELO, ACCE, THERMAL, ELSTRESS, ELFORCE, FLUX, GPSTRESS,
GPFORCE, ESE, GPSDCON, and ELSDCON.
The converted data is written to logical FORTRAN units, which may be assigned to physical files in the File
Management Section. The FORTRAN unit numbers are specified by the parameters GEOMU, POSTU,
and LOADU. By default, all data is written to the logical FORTRAN unit indicated by GEOMU. If
LOADU > 0, static load data may be diverted to another unit indicated by LOADU. If POSTU > 0, then
output data requested with the Case Control commands listed above will be diverted to the logical unit
indicated by POSTU. See Database Concepts in the MSC Nastran Reference Guide for the procedure for
assigning physical files.
By default, if converted data already exists on the files indicated by GEOMU, POSTU, and LOADU, then
the DBC module will overwrite the old data. If this is not desirable, then PARAM,DBCOVWRT,NO must
be entered. The parameters MODEL and SOLID may be used to store more than one model and solution
in the graphics database. These parameters are not supported by MSC Patran.
PARAM,DBCDIAG > 0 requests the printing of various diagnostic messages from the DBC module (see MSC
Nastran DMAP Programmer’s Guide) during the data conversion. By default, no messages are printed.
If PARAM,PATPLUS,YES is specified along with PARAM,POST,0 then the PARAM,POST,-1, operation
will also be performed.
If PARAM,POST,< 0 or 1, then the following parameters and discussion apply:
PARAM,POST,1 outputs the appropriate files for the SimXpert and Patran programs and should be
used to obtain results from the latest result data blocks from SOL 400 and other recent MSC
Nastran developments such as NEF.
PARAM,POST,-1 outputs the appropriate files for the Patran program (PARAM,POST,1 should be
used for more recent versions of MSC Nastran > 2012).
PARAM,POST,-2 outputs the appropriate files for the Siemens I-deas program.
PARAM,POST,-4 outputs the files indicated below along with OPHIG for the MSC_NF interface
by LMS International.
PARAM,POST,-5 outputs the files indicated in the table below along with LAMA and OPHG1 for
the FEMtools interface by Dynamic Design Solutions.
POST=-4 and -5 are intended for SOL 103 only.
PARAM,POST,-6 outputs the files indicated below for Siemens Unigraphics.
Main Index
CHAPTER 6 889
Parameter Descriptions
PARAM,POST,-7 outputs the files for Free Field Technologies.
An OUTPUT2 file for FORTRAN unit 12 in binary format is automatically created in the same directory
and with the same name as the input file and with the extension “.op2”. For example, if the input file is
fender.dat then the OUTPUT2 file will be called fender.op2.
An ASSIGN statement is required in the FMS Section only if neutral file format is desired as follows:
ASSIGN OUTPUT2=‘filename of FORTRAN file’ FORM
Geometry data blocks are output with PARAM,OGEOM,YES (Default) and are written to a FORTRAN
unit specified by PARAM,OUNIT1 (Default = OUNIT2) for POST = -1, -2, -4, and -6.
PARAM,OUNIT2K (Default = 91) specifies the unit number for KELM and KDICT with
PARAM,POST,-5. PARAM,OUNIT2M (Default = 92) specifies the unit number for MELM and MDICT
with PARAM,POST,-5. Note that PARAM,POST,-5 is not supported with DMP. See the following table for
the specific geometry data blocks written for different values for POST.
See also the PARAM,POSTEXT description for additional data blocks written to the .op2 file.
POST
Geometry Data
-1,1 or -7 -2 -4 -5 -6 Block Description
YES NO NO NO NO GEOM1S Grid Point Definitions (Superelement)
NO YES YES NO YES CSTM Coordinate System
Transformations
NO YES YES NO YES GPL Grid Point List
NO YES YES NO YES GPDT Grid Point Definitions
NO YES YES NO NO EPT Element Properties
NO YES YES NO NO MPT Material Properties
YES YES YES NO NO GEOM2 Element Definitions
YES* YES NO NO NO GEOM3 Load Definitions
YES* YES NO NO NO GEOM4 Constraint Definitions
YES NO NO NO NO DIT Dynamic Table Input
YES NO NO NO NO DYNAMICS Dynamic Loads Definition
NO NO YES YES NO KDICT Element Stiffness Dictionary
NO NO YES YES NO KELM Element Stiffness Matrices
NO NO YES YES NO MDICT Element Mass Dictionary
NO NO YES YES NO MELM Element Mass Matrices
NO NO NO NO YES ECTS Element Connections
YES NO NO NO NO VIEWTB View Element Table
YES NO NO NO NO EDOM Design Model Input
YES NO NO NO NO GEOM2S Same as GEOM2 for superelements
Main Index
890 MSC Nastran Quick Reference Guide
Parameter Descriptions
POST
Geometry Data
-1,1 or -7 -2 -4 -5 -6 Block Description
YES NO NO NO NO CSTMS Same as CSTM for superelements
YES NO NO NO NO EPTS Same as EPT for superelements
YES NO NO NO NO MPTS Same as MPT for superelements
* To avoid having GEOM3 and GEOM4 written if POST=-1, set PARAM,OP2GM34,FALSE.
PARAM,OMACHPR,NO selects the single precision format for GPDT, CSTM, and GEOM1.
PARAM,OMACHPR,YES selects the machine precision format. With PARAM,POST,< 0,
PARAM,OMACHPR,NO is the default. With PARAM,POST,1, PARAM,OMACHPR,YES is the default.
For PARAM,POST = -1 and -2, results data blocks are output to a FORTRAN unit specified by
PARAM,OUNlT2 (Default = 12). This parameter is allowed to vary between superelements. In buckling
solution sequence (SOL 105), a unique value of OUNIT2 should be specified for the buckling subcase. For
all other solution sequences or within a given analysis type, changes to PARAM,OUNIT2 between subcases
is not supported. See the POST Case Control command to change the unit number between subcases. See
also the related parameter OMAXR.
By default the displacements are output in the global coordinate system. To output in the basic coordinate
system, specify PARAM,OUGCORD,BASIC.
PARAM,POST,-1 or 1: Results Data Blocks for Patran and SimXpert
By default, the following data blocks are output under PARAM,POST,-1. The following parameters may be
used to disable the output of data blocks to the OUTPUT2 file. For example, if PARAM,OQG,NO is
specified, then the SPCFORCE output is not written to the OUTPUT2 file. It is recommended when
processing large post files in Patran and SimXpert that the following environment variable setting is used
when starting the session: DRANAS_NAST_MEM=2048MB.
PARAM,PATVER
Parameter Case Data Block
< 3.0 > 3.0 Name Control Name Description
YES YES OQG SPCFORCE OQG1 Forces of single-point constraint
YES NO OUG DISP OUGV1PAT Displacements in the basic coordinate
system
YES YES OUG DISP OUGV1 Displacements in the global coordinate
system
YES NO OES STRESS OES1 Element stresses (linear elements only)
YES NO OEF FORCE OEF1 Element forces or heat flux (linear
elements only)
YES YES OEE STRAIN OSTR1 Element strains
YES YES OGPS GPSTRESS OGS1 Grid point stresses
YES YES OESE ESE ONRGY1 Element strain energy
YES YES OGPF GPFORCE OGPFB1 Grid point force balance table
Main Index
CHAPTER 6 891
Parameter Descriptions
PARAM,PATVER
Parameter Case Data Block
< 3.0 > 3.0 Name Control Name Description
NO YES OEFX FORCE OEF1X Element forces with intermediate (CBAR
and CBEAM) station forces and forces on
nonlinear elements
NO YES OESX STRESS OES1X Element stresses with intermediate
(CBAR and CBEAM) station stresses and
stresses on nonlinear elements
NO YES OPG OLOAD OPG1 Applied static loads
NO YES OCMP STRESS OES1C Ply stresses
NO YES OCMP STRAIN OSTR1C Ply strains
NO YES none DISP OUPV1 Scaled Response Spectra
SPCFORCE OQP1
FORCE DOEF1
STRESS DOES1
STRAIN DOSTR1
none LAMA Nonlinear Buckling
NO YES none DISP OCRUG
OLOAD OCRPG
NO YES none NLSTRESS OESNLXR Nonlinear static stresses
NO YES none BOUTPUT OESNLBR Slideline stresses
NO YES none NLLOAD OPNL1 Nonlinear loads
NO YES none STRESS OESNLXD Nonlinear transient stresses
PARAM,POST,-2: Results Data Blocks for Siemens I-deas
By default, the following data blocks are output under PARAM,POST,-2. By default, the displacements are
output in the basic coordinate system. To output in the global coordinate system, specify
PARAM,OUGCORD,GLOBAL. The following parameters may be used to disable the output of data blocks
to the OUTPUT2 file. For example, if PARAM,OQG,NO is specified, then the SPCFORCE output is not
written to the OUTPUT2 file.
Results Data
PARAMeter Name Case Control Block Name Description
OQG SPCFORCE OQG1 Forces of single-point constraint
OUG DISPLACE BOUGV1 Displacements in the basic coordinate
system
BOPHIG Eigenvectors in the basic coordinate system
OUGV1 Displacements in the global coordinate
system
TOUGV1 Grid point temperatures
OES STRESS OES1 Element stresses (linear elements only)
Main Index
892 MSC Nastran Quick Reference Guide
Parameter Descriptions
Results Data
PARAMeter Name Case Control Block Name Description
OEF FORCE OEF1 Element forces (linear elements only)
FLUX HOEF1 Element heat flux
OEE STRAIN OSTR1 Element strains
OESE ESE ONRGY1 Element strain energy
OCMP STRESS OEFIT Failure indices
STRESS OES1C Ply stresses
STRAIN OSTR1C Ply strains
OUMU ESE LAMA Eigenvalue summary
ONRGY2 Element strain energy
OEFX FORCE OEF1X Element forces (nonlinear elements only)
OESX STRESS OES1X Element stresses (nonlinear elements only)
none none ODELBGPD Shape optimization geometry changes
PARAM, POST, -4: Results Data blocks for LMS International/MSC_NF
By default, the following data blocks are output under PARAM,POST,-4. The following parameters may be
used to disable the output of data blocks to the OUTPUT2 file. For example, PARAM,OUG,NO requests
that eigenvectors not be written to the OUTPUT2 file.
PARAMeter Name Case Control Data Block Name Description
OUG DISPLAC OPHIG Eigenvectors in the global coordinate
system.
PARAM, POST, -5: Results Data blocks for Dynamic Design Solutions/FEMtools
By default, the following data blocks are output under PARAM,POST,-5. The following parameters may be
used to disable the output of data blocks to the OUTPUT2 file. For example, PARAM,OUG,NO requests
that eigenvectors not be written to the OUTPUT2 file. PARAM,OUNIT2O (Default51) specifies the unit
number of the OUTPUT2 file.
Data Block
PARAMeter name Case Control Name Descriptions
OUG DISPLAC OUGV1 Eigenvectors in the global coordinate system.
LAMA Eigenvalue summary.
PARAM, POST, -6: Results Data Blocks for Siemens Unigraphics
Main Index
CHAPTER 6 893
Parameter Descriptions
By default, the following data blocks are output under PARAM,POST,-6. The following parameters may be
used to disable the output of data blocks to the OUTPUT2 file. For example, PARAM,OUG,NO requests
that displacements not be written to the OUTPUT2 file.
Data Block
PARAMeter Name Case Control Name Description
OQG SPCFORCE OQG1 Forces of single-point constraints
OUG DISPLAC OUGV1 Displacements
OES STRESS OES1 Element stresses
OEF STRESS OEF1 Element forces
OEE STRAIN OSTR1 Element strains
OESX STRESS OES1X Element stresses with intermediate station stresses
and stresses on nonlinear elements
OEFX STRESS OEF1X Element forces with intermediate station forces
and forces on nonlinear elements
OPG OLOAD OPG1 Applied static loads
none none DVPTAB Designed property table
none none OPTPRMG Optimization parameters
none none PROPO Final element properties
none none DBCOPT Optimization summary data
PARAM,POST,-7 Results Data Blocks for Free Field Technologies
Except eigenvectors, all other output data blocks are the same as PARAM,POST,-1. For eigenvectors, the
matrix form is written to the OUTPUT2 file.
POSTEXT
Default = NO
Under PARAM,POST,-1 and -2, and if PARAM,POSTEXT,YES is specified, then the following data blocks
are also written to the .op2 file specified by PARAM,OUNIT2.
Data Block Name PARAM POST Description
FRL -1, -2 Frequency response list (modal frequency response only).
BHH -1, -2 Modal damping matrix (modal frequency response only).
KHH -1, -2 Modal stiffness matrix (modal frequency response only).
BGPDT -1 Basic grid point definition table.
PVT0 -1, -2 User parameter value table
CASECC -1 Case Control table
EQEXIN(S) -1 Equivalence external to internal grid ID table
Main Index
894 MSC Nastran Quick Reference Guide
Parameter Descriptions
Data Block Name PARAM POST Description
CLAMA -1, -2 Complex eigenvalue table
OEDE1 -1, -2 Element energy loss output table
OEKE1 -1, -2 Element kinetic energy output table
OUGV2 -1, -2 Displacement output table in SORT2
PSDF -1, -2 Power spectral density table
OGPWG -1, -2 Grid point weight generator output table
TOL -1, -2 Time output list
OPHSA -1, -2 Solution set eigenvectors (modal frequency response only)
LAMA -1 Eigenvalue summary table
ONRGY2 -1 Element kinetic energy (obsolete)
PSDFH -1, -2 Power spectral density table for modal coordinates
DSCM2 -1, -2 Design sensitivity coefficient matrix
DSCMCOL -1, -2 Design sensitivity parameters table
MPOUT -1,-2 Monitor point outputs
POSTADF
Default = NO
This parameter is used to export the results of frequency analysis responses and participation factors by
PFMODE, PFPANEL, and PFGRID in ADF format file. This exportation is requested by setting this
parameter to YES. The unit information of the exported functions should be defined by DTI, UNITS
statement for this function (see ADAMSMNF statement). If not defined, SI unit will be assumed with the
warning message. The ADF file is defined as input data name with the extension “afu” automatically.
Alternatively the name can be defined with ASSIGN ADFFILE= statement in FMS section. For the
participation factor output, FILTER=0. option should be applied in PFMODE and PFPANEL.
POSTU
Default = -1
See POST=0.
PREFDB
Default = 1.0
See ACOUT.
PRGPST
Default = NO
PRGPST is replaced by the PRINT keyword on the AUTOSPC Case Control command. The specification
of the AUTOSPC command overrides the specification of PARAM,PRGPST.
Main Index
CHAPTER 6 895
Parameter Descriptions
PRINT
Default = YES
PARAM,PRINT,NO suppresses the automatic printing of the flutter summary in flutter analysis.
PROUT
Default = -1
PARAM,PROUT,-1 suppresses execution and printout from the ELTPRT module. PROUT≥0 prints a list
of all elements sorted on EID and summary tables giving the range of element identification numbers for
each element type.
ELTPRT will provide an information message when it detects any duplicate element ID. For the case of
CONV and CHYBDi elements, duplicate element IDs are by design. The information message provided by
ELTPRT can be safely ignored for these elements.
PRPA
Default = 1.0E37
PRPJ
PRPA and PRPJ control the printout of intermediate load matrices for diagnostic purposes during
superelement assembly. If the value of PRPA (or PRPJ) is positive, all terms larger in magnitude than the
value are printed. If the value of PRPA (or PRPJ) is negative, all terms smaller in magnitude than the value
are printed. The default value requests no printout. PARAM,IRES,1 must be present for these parameters
to be effective. The PA matrix contains the internal loads transmitted to the downstream superelement. The
PJ matrix contains external loads applied on the superelement; that is, it has the same content as the data
produced by the Case Control command OLOAD. All of this data may be obtained on restart using the
SELR Case Control command option. A related parameter is IRES.
PRPHIVZ
Default = 1.0E37
PRPHIVZ controls the printout of the PHlVZ matrix that contains the component mode eigenvectors of the
model. It includes all degrees-of-freedom with motion except the m-set, eliminated for multipoint
constraints. The FAPPROX matrix contains the square root of the diagonal terms of the generalized stiffness
matrix divided by 2. For fixed-boundary solutions, it is a good approximation for the natural frequencies
of the component. For free- or mixed-boundary solutions, it is of a lower value than the natural frequencies.
All terms larger than PRPHlVZ in both matrices will be printed (i.e., PARAM,PRPHIVZ,0.0 causes all terms
to be printed).
PRTMAXIM
Default = NO
PRTMAXIM controls the printout of the maximums of applied loads, single-point forces of constraint,
multipoint forces of constraint, and displacements. The printouts are titled “MAXIMUM APPLIED
LOADS”, “MAXIMUM SPCFORCES”, “MAXIMUM MPCFORCES”, and “MAXIMUM
DISPLACEMENTS”.
Main Index
896 MSC Nastran Quick Reference Guide
Parameter Descriptions
PRTRESLT
Default = YES
PRTRESLT controls the printout of the resultants of applied loads, single-point forces of constraint, and
multipoint forces of constraint. The printouts are titled “OLOAD RESULTANTS”, “SPCFORCE
RESULTANTS”, and “MPCFORCE RESULTANTS”.
PSENPCH
Default = NO, for SOL 200 job with PART SEs only.
Setting PSENPCH to YES causes updated Bulk Data entries of a PART SE for a design cycle punched to a
separate file named as follows
JOBNAME_psexx_yy.pch – where xx is the PART SE ID and yy is the design cycle.
PTHRES
Default = -1
PARAM, PTHRES, TABLED1_ID requests the PEAKOUT result at which the desired response exceeds a
prescribed threshold value. The threshold value for the response is defined on the TABLED1 Bulk Data entry
as frequency vs. the threshold of a response value.
Q
Default = 0.0
Q specifies the dynamic pressure. Q must be specified in aeroelastic response analysis (SOLs 146), and the
default value will cause a User Fatal Message.
RADMOD
Default = YES
This parameter only applies to heat transfer solution sequences for SOLs 153, 159 and 400. The parameter,
RADMOD, only affects radiation heat transfer problems. The radiation matrix is modified to avoid the
temperature overshoot with a coarse mesh. If the user wants the program to skip this operation (modify the
radiation matrix) then insert PARAM,RADMOD,NO.
RBSETPRT
Default=0
This parameter controls the printout of rigid element IDs that are included in the analysis. Setting
PARAM,RBSETPRT to a value not equal to zero activates the printing of rigid element IDs. Note that this
function works in conjunction with the rigid element selection via MPC=n in case control and SET3,n,RBxx
in bulk data.
REMZERO
Character, default='NO' - see RMSPRMDS
RESLTOPT
Default = 8
Main Index
CHAPTER 6 897
Parameter Descriptions
RESLTOPT’s default value provides component-level force summary output for model checkout (PARAM,
CHECKOUT, YES), loads generation (OLOAD output), and SPC and MPC forces. Setting RESLTOPT to
a value of 1 produces abbreviated output formats only.
RESVEC
This parameter and the related parameters RESVINER, RESVSO, RESVSE, and RESVSLI are obsolete or
replaced by options on the RESVEC Case Control command.
RFORSET
Default = 0
A PARAM, RFORSET, n where n is a Bulk Data SET1 entry, allows the user to apply rotational force loading
(RFORCE) to just a portion of the structure. RFORSET like RFORCE loading is global and is computed
once at the beginning of the analysis. The Bulk Data SET1 n defines the GRIDS to which the rotational force
loading is to be applied. RFORSET can appear in either the Bulk Data or ABOVE or IN the 1st Subcase.
A RFORSET appearing in any other Subcase will be ignored and may cause incorrect results. A RFORSET
appearing in or above the first subcase takes precedence over a RFORSET appearing in Bulk Data. See also
the companion GRAVSET entry. If there is no RFORCE loading called out, then PARAM, RFORSET, n
needs to be removed from the run.
RHOCP
Default = 1.0
This parameter represents a scale factor used in the computation of ERP in units of dB. See the ERPREFDB
parameter. This parameter may alternatively be set using the ERP Case Control command.
RIMINTP
RIMINTP can be used to select the interpolation method for Reduced Impedance Matrix(RIM) for PEM
and ACTRIM. The input options for RIMINTP are LINEAR and LOG10. The default is LINEAR.
RKSCHEME
Default = Remark 1., SOL 700 only
Defines the type of time-integration scheme used in the Riemann solution-based Euler solvers.
Format:
PARAM,RKSCHEME,NUMBER
Example:
PARAM,RKSCHEME,3
NUMBER Number of Runge-Kutta stages. (Integer > 0)
Main Index
898 MSC Nastran Quick Reference Guide
Parameter Descriptions
Remarks:
1. This parameter can be used in combination with the original Roe solver and the improved full 2nd
order fluid- and gas Euler solver. The default number of stages depends on the spatial accuracy of the
solution scheme. One stage is used for first order spatial accuracy, and three stages for second order
spatial accuracy.
2. It is recommended that the user leave the setting to the default values as defined depending on the
selected spatial accuracy of the solution.
3. It has been found that in some cases with fluid flows, it may be necessary to manually limit the time
step to a fixed and lower value than the scheme determines. These occasions are noticeable when you
view a contour plot of the pressure. The user may find that the pressure field looks like a
checkerboard. This is then caused by a numerical instability due to a time step that is too large for the
fluid flow. The face fluxes are always correct but the element values get decoupled due to the time
integration instability. Lowering the time step to about half the maximum value the scheme
determines solves this problem. Please note that this significantly slows down the computation! Since
this problem rarely occurs we have chosen not to automatically limit the time step to a lower value
for performance reasons. However, the user needs to be aware that the analysis may exhibit the
aforementioned behavior.
RMSINT
Default = LINEAR for the trapezoidal approximation.
RMSINT specifies the interpolation method for numerical integration when computing both RMS (Root
Mean Square) and N0 (Number of Zero Crossings or Mean Frequency) from PSDF (Power Spectral Density
Function). RMSINT = LINEAR requests the trapezoidal approximation, which is the existing Nastran
approach. RMSINT = LOGLOG requests the Log-Log interpolation.
RMSPRMDS
Character, default='NO'
In Sol 107, this is the flag to remove spurious modes when creating an ADAMSMNF. If set to ‘YES’, then
the program will attempt to remove potential spurious modes based on the values of the following parameters.
If the natural frequency of a mode is less than FREQTOL and the calculated damping is more than
DAMPTOL, it will be considered spurious and removed. If REMZERO is set to ‘YES’, then modes with a
0.0 natural frequency and a non-zero real part of the eigenvalue will be considered spurious and removed.
ROHYDRO
Default = Remark 3., SOL 700 only
Defines the minimum density for hydrodynamic, single-material Eulerian elements.
Format:
PARAM,ROHYDRO,VALUE
Main Index
CHAPTER 6 899
Parameter Descriptions
Example:
PARAM,ROHYDRO,1.E-6
VALUE Density cutoff. (Real > 0.0)
Remarks:
1. Hydrodynamic, single-material Eulerian elements with a density less than ROHYDRO are
considered to be empty. All of the variables are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of element B after transport is less than ROHYDRO, then no transport is done.
b. If the density of element A after transport is less than ROHYDRO, then all of the mass is
transported to element B.
3. By default, the cutoff density for hydrodynamic Eulerian elements is set to 1.E–5 times the material
reference density. For the Riemann solution-based solvers, the default is set to 1.E-6 times the
reference density.
4. Please note that this parameter has a different effect in the Riemann-solution based Euler solvers. The
elements are never viewed as empty, but a small amount of mass (equal to the element’s volume times
the cut-off density value) remains in the element. All other state variables (velocity, energy and
pressure are reset to zero for these types of elements). For fluid flows where you wish to model
cavitation, use Tait’s equation of state with a critical density at which the pressure remains constant
and the fluid cavitates.
ROMULTI
Default = Remark 3., SOL 700 only
Defines the minimum density for multimaterial Eulerian elements.
Format:
PARAM,ROMULTI,VALUE
Example:
PARAM,ROMULTI,1.E-6
VALUE Density cutoff. (Real > 0.0)
Remarks:
1. Multimaterial Eulerian elements with a density less than ROMULTI are considered to be empty. All
of the variables are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of a specific material in element B after transport is less than ROMULTI, no
transport is done.
Main Index
900 MSC Nastran Quick Reference Guide
Parameter Descriptions
b. If the density of a specific material in element A after transport is less than ROMULTI, all of the
mass of that material is transported to element B.
3. By default, the cut-off density is set for each material separately as 1.E–5 times the material reference
density.
ROSTR
Default = Remark 3., SOL 700 only
Defines the minimum density for single-material Eulerian elements with shear strength.
Format:
PARAM,ROSTR,VALUE
Example:
PARAM,ROSTR,1.E-6
VALUE Density cutoff. (Real > 0.0)
Remarks:
1. Single-material Eulerian elements with shear strength with a density less than ROSTR are considered
to be empty. All of the variables are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of element B after transport is less than ROSTR, then no transport is done.
b. If the density of element A after transport is less than ROSTR, then all of the mass is transported
to element B.
3. By default the cut-off density for Eulerian elements with shear strength is set to 1.E–5 times the
material reference density.
RSPECTRA
Default = -1
RSPECTRA = 0 requests that response spectra be calculated for transient analysis. See Response Spectrum
Analysis (Ch. 9) in Dynamic Analysis User’s Guide for a discussion of this capability. Response spectra will be
calculated for any superelements or the residual structure for which other output requests are present in the
same run. The requirements for the other output requests are also in Response Spectrum Analysis (Ch. 9) in
Dynamic Analysis User’s Guide. Any punch data produced is sent to the standard Nastran PUNCH file.
Related parameters are TABID and RSPRINT.
RSPRINT
Default = 0
RSPRINT controls the printout of tabulated values of response spectra. RSPRINT = -1 suppresses the
printout. The related parameter is RSPECTRA.
Main Index
CHAPTER 6 901
Parameter Descriptions
RSTTEMP
Default = NO
In SOL 106, PARAM,RSTTEMP,YES will cause the automatic restart to ignore changes to or additions of
TEMPij Bulk Data entries. This is applicable to SOL 106 restart runs in which the temperature changes are
only intended to affect the loading and not the material properties. The restart run also requires the use of
the DBLOCATE FMS statement instead of the RESTART statement to reference the data base; e.g.,
assign run1=plate-run1.MASTER
dbloc logical=run1
RVLDFILT
Default = NO
This parameter controls a filtering process for residual vector loads. Set PARAM,RVLDFILT,YES to check
the linear independence of load vectors to be used as a basis for residual vector augmentation. This option is
useful if you have many thousands of applied loads, many of which occupy the same vector space (for
example, same direction). For this case, linearly dependent load vectors will be discarded and not used for
residual vector computation, leading to a more efficient solution. The linear dependence check itself may be
very time consuming, hence the default value is NO. If the number of load vectors is more than about 20,000,
the linear dependence check may require long running time. When the number of load vectors is large, User
Information Messages 10590, 10591, and 10592 may be printed in the F06 file. See also related parameter
MAXAPL.
S1, S1G, S1M
Default = -1
The MAXMIN Case Control command offers more features with much greater efficiency. PARAM,S1i,+1
requests the sorting and/or filtering of the element stresses selected on the DTI,INDTA entry. Stresses in the
element coordinate systems (S1), at grid points (S1G), and/or in material coordinate systems (S1M) based
on the parameters BIGER, NUMOUT, SRTOPT, and SRTELTYP may be requested. The S1G and S1M
options also require the presence of PARAM,CURV,1.
Coordinate
Parameter Quantity System Location Elements
S1 > 0 Stresses Element Element centers CQUAD4,
CQUAD8,
CTRIA3,
CTRIA6
S1M > 0 Stresses Material Element centers CQUAD4,
CTRIA3
S1G > 0 Stresses Material Grid points to which elements CQUAD4,
connect CTRIA3
NUMOUT, in conjunction with BIGER, controls the amount of stress output.
Main Index
902 MSC Nastran Quick Reference Guide
Parameter Descriptions
NUMOUT2 and BIGER2 serve the same function as NUMOUT and BIGER except that they apply only
to composite element failure indices and do not require PARAM,S1i,+1. Similarly, NUMOUT3 and
BIGER3 are used for composite strength ratio.
1. NUMOUT = +N requests that N element stresses be printed (or punched) for each element type.
2. NUMOUT=0 outputs all elements in a group when one or more exceeds BIGER. Some of the
elements will have stresses small than BIGER. This is conceptually the same as describing an element
set in case control, and limiting output in this manner. Stress files obtained with element group
filtering may be used for xy plotting and other postprocessor options with DMAP alters. By contrast,
the stress file when NUMOUT = -2 is more discontinuous, and may not be used for xy plotting.
3. NUMOUT = 0 does not sort but filters according to BIGER by element group. In static analysis an
element group is defined as all case control selected elements for a given load case for SORT1 output.
For SORT2 output an element group is defined as the data for a given element type for all load cases.
In transient analysis an element group is defined as all case control selected elements at a given time
for SORT1 output. For SORT2 output an element group is defined as the data for a given element
at all time steps. The element group option applies only to output types described above for
PARAM,S1. This option is not available with output types selected by PARAMs S1G and S1M.
4. NUMOUT = -1 requests that stresses be sorted and only those stresses with an absolute value that is
greater than BIGER will be output.
5. NUMOUT = -2 (the Default) does not sort but filters according to BIGER. Related parameters
include BIGER, NOELOF, NOELOP, and NOGPF.
6. NUMOUT2 = -3 outputs the maximum value of Failure Index for each element.
BIGER controls the elements for which stresses will be printed. Elements with stresses that are smaller in
absolute value than BIGER will not be output. The quantity tested is element type dependent. Related
parameters include CURV, NUMOUT, S1, S1G, and S1M. SRTOPT controls the scanning option to be
performed.
SRTOPT Value Description
0 Filter/sort on maximum magnitude.
1 Filter/sort on minimum magnitude.
2 Filter/sort on maximum algebraic value.
3 Filter/sort on minimum algebraic value.
SRTELTYP controls the element type to be processed, as described in the following table.
SRTELTYP Value Description
>0 All element types will be processed.
>0 Only element type SRTELTYP will be processed.
Main Index
CHAPTER 6 903
Parameter Descriptions
NUMOUT1 and BlGER1 serve the same function as NUMOUT and BIGER except that they apply only
to composite element stresses and do not require PARAM,S1i,+1.
NUMOUT2 and BIGER2 serve the same function as NUMOUT and BIGER except that they apply only
to composite element failure indices and do not require PARAM,S1i,+1.
S1AG,S1AM
Default = -1
See CURV.
SBSPFORM
No Default
This parameter can be used to specify the Subspace Iteration method formulation for the structure-fluid
coupled modes computation.
Subspace iteration method selects the formulation automatically based on the ratio of structure and fluid size
and the existence of rigid body or constant pressure modes. But using this parameter, user can force one or
other of the methods.
MF: Mobility-Flexibility formulation
SM: Stiffness-Mass formulation
SCRSPEC
Default = -1 (SOLs 103 and 115 only)
SCRSPEC=0 requests that structural response be calculated for response spectra input in normal modes
analysis. See Response Spectrum Analysis (Ch. 9) in the MSC Nastran Dynamic Analysis User’s Guide for a
discussion of this capability. The scaled response calculations are made for elements and grid points of the
residual structure only. There exist two basic methods which are controlled by PARAM,CQC. The default
(CQC=0) selects the traditional method. CQC > 0 selects a more recent method called the complete
quadratic method of peak response combination—also called the CQC method. In both methods, the
responses are summed with the ABS, SRSS, NRL, or NRLO convention, depending on the value of
PARAM,OPTION. If the SRSS, NRL, or NRLO options are used, close natural frequencies will be summed
by the ABS convention, where close natural frequencies meet the inequality f i + 1 CLOSE f i . Both
PARAM,OPTION and PARAM,CLOSE may be set in any subcase, allowing summation by several
conventions in a single run.
In Version 70, the NRL option has been modified slightly to correspond to the NAVSEA-0908-LP-000-3010
specification. NRLO provides the V69 NRL.
PARAM,CQC,1 or 2 selects the complete quadratic method of peak response combination; also called the
CQC method. PARAM,CQC,1 selects CQC method of response combination for sum across modes.
PARAM,CQC,2 is same PARAM,CQC,1, but outputs the CQC coefficients for each mode ij pair and
frequency and damping for each mode. The default is to consider all modes in the calculation but if only a
Main Index
904 MSC Nastran Quick Reference Guide
Parameter Descriptions
subset of modes are of interest then a DTI,CQC,1,... Bulk Data entry may be used to specify a list of modes
(by mode number) to retain for the CQC solution. When multiple excitation directions are specified,
PARAM,CQC,1 or 2 specifies the summation across the modes and PARAM,OPTION specifies the
summation across excitation directions. As with PARAM,OPTION and PARAM,CLOSE, when
PARAM,CQC is used at the subcase level, each subcase can have a different value specified for OPTION,
CLOSE and CQC. This allows comparisons to be made in the same run among summation across directions
using ABS and SRSS methods while using the CQC method to sum across modes.
For the CQC method, PARAM,DIROUT,YES (Default = NO) outputs the responses combined across the
modes for each separate excitation direction as well as the responses combined across modes and directions.
This allows results to be assessed per excitation direction and for the total combined response.
PARAM,POST,-1 will write the additional directional responses to the op2 file for post processing with
Patran. In this case, the directional responses will be labeled in the Patran Results menu with a TIME value
corresponding to the excitation sequence number. For example, if the SUPORT entry specifies the following
degrees of freedom to be excited: SUPORT,1,123 then direction 1 will be labeled with TIME value 1,
direction 2 with TIME value 2, etc. PARAM,POST,-1 will also write the additional maximum response to
the op2 file for post processing. In this case, the maximum response will be labeled in the Patran Results menu
with a TIME value 4.
For the CQC method, PARAM,NEWMARK,YES (Default = NO) may be used in the case where 3
simultaneous excitation directions are defined and calculate the Newmark combinations across the
excitations directions using the 40% rule. PARAM,PERCENT (Default = 40) may be used to specify a
different percentage for Newmark combinations.
SDCSV
Default = 0
Dictates what stability derivative information is to be stored on a CSV (comma separated values) file in a SOL
144 (static aeroelasticity) task. The unit the CSV file is stored to is specified by PARAM, SDUNIT, n.
SDCSV has the following options which can be summed to select multiple options:
0 No output
1 Rigid aero
2 Rigid Splined
4 Elastic restrained
8 Elastic unrestrained
16 Intertial restrained
32 Inertial unrestrained
SDUNIT,n
n SDUNIT is used in conjunction with an FMS ASSIGN statement to specify the unit number for the
storage of stability derivative results in SOL 144.
SEKD
Main Index
CHAPTER 6 905
Parameter Descriptions
Default = RSONLY
Controls the calculation of the upstream superelement differential stiffness matrix in SOL 106.
RSONLY Calculate the differential stiffness for the residual structure only.
ALL Calculate and reduce the differential stiffness for all superelements and the residual
structure.
SEMAP, SEMAPOPT, SEMAPPRT
SEMAP Default = SEMAP
SEMAPOPT Default = 42
SEMAPPRT Default = 3
The superelement map (SEMAP table) contains several lists useful for determining how the program has
partitioned superelement models. It is printed automatically each time this table is generated. It consists of
three major parts:
GPM The Grid Point Map contains a list of each grid point, its interior superelement placement,
and the SElD of all grid points connected directly to it by elements. Three tables follow that
summarize the connectivity between superelements, sorted on grid point sequence, SElD,
and the number of connections.
ISM The Individual Superelement Map lists the interior grid points, exterior grid and scalar
points, elements, and time and storage space estimates for each superelement.
SDT The Superelement Definition Table contains the SEID of every superelement in the model,
the processing order, and a pictorial representation of the superelement tree.
SEMAP, SEMAPOPT, and SEMAPPRT are used to control the amount of output that is printed and other
special features. The possible values for SEMAP are shown in the following table.
SEMAP Value Output and Application
SEMAP (Default) ISM, SDT. The lengthy GPM is suppressed. This is the appropriate value for use
after the model is stable and only minor changes are to be made.
SEMAPALL GPM, ISM, SDT. All tables are printed. This value is useful on the initial debug
run of a model and when making extensive modeling changes.
Main Index
906 MSC Nastran Quick Reference Guide
Parameter Descriptions
SEMAP Value Output and Application
SEMAPCON Only the summary tables of the GPM and the estimation data is output. This is
a useful value when iterating to an economic partitioning scheme for large, complex
models.
SEMAPEST Only the estimation data is printed. This is useful when evaluating several
alternative partitioning schemes.
SEMAPPUN No output is printed. The exterior grid points of the superelement with a SEID
that is input on SEMAPOPT are placed on a CSUPER entry image on the
PUNCH file, allowing the superelement to be used as an external superelement. If
SEMAPOPT > 0, the superelement entry is given an SSID of SEMAPOPT. If
SEMAPOPT < 0, the exterior points listed are those of the residual structure, but
the CSUPER entry is given an SSID of |SEMAPOPT|.
Other special features are available with parameters SEMAPOPT and SEMAPPRT. They are fully described
under parameters OPT1 and OPT2 in the description of the TABPRT module in the MSC Nastran DMAP
Programmer’s Guide.
If the default value of SEMAP is used, the other two parameters may be used to further refine this output, as
described in MSC Nastran DMAP Programmer’s Guide under the TABPRT module description. The printing of
the SEMAP table can be avoided by the use of PARAM,SEMAPPRT,-1.
PARAM,SEMAPPRT,99 requests the printout of the SLIST (superelement processing list) and the DRLIST
(superelement data recovery list).
SENSUOO
Default = NO
By default, in dynamic sensitivity analysis in SOL 200, displacements at the o-set due to pseudo-loads do not
include any effect due to inertia and damping. If PARAM,SENSUOO,YES is specified then these effects will
be computed in a quasi-static manner and included in the sensitivity analysis.
SEP1XOVR
Default = 0
The old and new location of moved shell grid points are printed if SEP1XOVR = 16. When the RSSCON
shell-to-solid element connector is used. By default, the moved shell grid points are not printed,
SEP1XOVR = 0. See the description of PARAM,TOLRSC for more details.
SEQOUT
Default = 0
See OLDSEQ.
SERST
Main Index
CHAPTER 6 907
Parameter Descriptions
Default = AUTO
By default, all restarts are considered automatic (see Restart Procedures in the MSC Nastran Reference Guide).
If none of the following Case Control commands are entered, then SEALL=ALL is the default action:
SEMG, SELG, SEKR, SELR, SELA, SEMA, SEMR, and SEALL.
These commands may be used to partition the analysis into several runs. By default, the restart will proceed
in automatic fashion for each command, regenerating only that data that is affected by modifications in the
Bulk Data and Case Control or changes in upstream superelements. If the user wishes to overwrite the data,
even if it is not affected by modifications to the data, then PARAM,SERST,MANUAL must be entered.
With PARAM,SERST,AUTO or MANUAL, all superelements will be processed through Phase 0 (see
Superelement Analysis in the MSC Nastran Reference Guide). This phase includes execution of the sequencer
module (SEQP), initial superelement processing (SEP1), and initial geometry processing (GP1 and GP2)
modules, which can result in significant CPU overhead. If this overhead is not desired, then
PARAM,SERST,SEMI will limit Phase 0 and Phase 1 to only those superelements specified on the SEMG,
SELG, SEKR, SELR, SELA, SEMA, SEMR, and SEALL Case Control commands. If none of these
commands is entered, then execution will skip Phase 0 and 1.
In the modal solution sequences (SOLs 110, 111, 112, 145, 146, and 200), the modes of the residual
structure are automatically computed in Phase 2 if any SE-type command (e.g., SEMG=n) is requested for
the residual structure. If PARAM,SERST,SEMI and no SE-type command is specified for the residual
structure, then, by default, its modes will not be recomputed. This logic is intended for restarts from SOL
103 into one of the modal solutions. If, however, the modes have not already been computed or need to be
recomputed, then PARAM,SERST,RSMDS must be specified to force the calculation of the residual
structure modes.
If PARAM,SERST,SEDR is specified, then Phases 0, 1, and 2 will be skipped. This option is intended for
data recovery (Phase 3) runs only.
The options of SEMI, RSMDS, and SEDR are intended for models that are defined on more than one
database; i.e., superelements are defined on separate databases (multiple MASTER DBsets) and processed in
separate runs. Also, with this technique, databases are attached with the DBLOCATE File Management
statement rather than the RESTART File Management statement. In general, these options are not
recommended because they disable the automatic restart capability, which compromises the database
integrity.
SESDAMP
Default = NO
PARAM,SESDAMP,YES
Modal damping is calculated for superelements if PARAM,SESDAMP,YES is specified. An SDAMPING
Case Control command that selects a TABDMP1 Bulk Data entry must also be specified in the desired
superelement’s subcase. By default, modal damping is added to viscous damping (B). If you insert
PARAM,KDAMP,-1 (or PARAM,KDAMPFL,-1 for fluid superelements) then modal damping will be added
to structural damping (K4). The SESDAMP parameter needs to be specified as NO for an assembly run.
PARAM,SESDAMP,AUG
Main Index
908 MSC Nastran Quick Reference Guide
Parameter Descriptions
By its nature, classical modal damping in superelements is computed only for the component modes. If fixed
boundary or mixed boundary (some fixed, some free) methods are used to compute the component modes,
no damping is computed for the constraint modes, which can lead to answer differences when comparing the
same model with and without superelements. An enhanced modal damping method has been developed to
account for damping on the constraint modes. To use the enhanced damping method instead of the classical
method, define “PARAM,SESDAMP,AUG”. When this enhanced damping method is defined, the user may
choose how the damping factor for the constraint modes is determined via the parameter TDAMP.
SESEF
Default = -1 (SOLs 103 and 115 only)
If SESEF = 0 in superelement normal modes analysis, the fraction of total strain energy for a superelement
in each of the system’s modes is output in the vector SESEFA for tip superelements and in SESEFG for nontip
superelements. If SESEF = 1, strain energy fractions are output, and expansion of the eigenvectors from a-set
size to g-set is branched over for tip superelements. If SESEF = -1 (the default value), no strain energy
fractions are computed.
Output requests must be present in order for strain energy fractions to be calculated. If SESEF = 1, no other
output results for tip superelements.
SHIFT1
Default = -1.234
The negative shift used when computing massless mechanism constraint modes with
PARAM,MMMETH,OLD. For very stiff model (1000. hz for the first flexible mode), consider using a larger
value. See also MECHFIX and MMMETH.
SHLDAMP
Default = SAME
If SAME, then structural damping is obtained from MID1 material of PSHELL. If DIFF or any value not
equal to SAME, each MIDi field of the PSHELL will have its own structural damping. See Remark 5. of the
PSHELL.
SIGMA
Default = 0.0
The radiant heat flux is proportional to
4
SIGMA T grid + T ABS
where SIGMA is the Stefan-Boltzmann constant, Tgrid is the temperature at a grid point, and TABS is the
scale factor for absolute temperature and may be specified by PARAM,TABS. These parameters must be given
Main Index
CHAPTER 6 909
Parameter Descriptions
in units consistent with the rest of the data in the model. The value for SIGMA in SI units is
5.67×10-8 watt/m2K4. The default value causes radiant heat effects to be discarded.
SKINOUT
Default = NONE
Request that sets of grid and element lists be output for both the fluid and structure at the fluid-structure
interface.
NONE Requests no output of sets.
PUNCH Requests set output to .pch only.
PRINT Requests set output to .f06 only.
ALL Requests set output to both .pch and .f06.
See the Case Control command FLSPOUT as an alternative selection.
SKPAMP
Default = 0
For SOLs 145, 146, and 200, SKPAMP = -1 suppresses all unsteady aerodynamic calculations. The
automatic restart performs a similar function without this parameter. Specifying it ensures suppression of the
calculations, regardless of the determination of the automatic restart.
SLOOPID
Default = 0 (SOL 129 and 159 only)
In a nonlinear transient analysis (SOLs 129 and 159) restart, SLOOPID identifies the initial conditioning
previous nonlinear analysis run (SOLs 106 and 153 respectively). Setting SLOOPID greater than 0 will cause
SOLs 129 and 159 to start from the static deformed position.
SMALLQ
Default = 0.0
By default Nastran removes unused superelement q-set degrees-of-freedom from the residual structure
solution set. Set this parameter to a small value (e.g., 1.0E-10) if you do not want unused superelement q-set
degrees-of-freedom removed.
SNORM
Default = 20.0
SNORM > 0.0 requests the generation of unique grid point normals for adjacent shell elements (see
Figure 6-2). Unique grid point normals are generated for the CQUAD4, CTRIA3, CQUADR, and CTRIAR
elements. The grid point normal is the average of the local normals from all adjacent shell elements including
CQUAD8 and CTRIA6 elements. If grid point normals are present, they are used in all element calculations
of the CQUAD4, CTRIA3, CQUADR, and CTRIAR elements.
Main Index
910 MSC Nastran Quick Reference Guide
Parameter Descriptions
SNORM Tolerance in Degrees
> 0.0 Unique grid point normals are generated if each angle between the grid point normal and
each local normal of the adjacent shell elements is smaller than SNORM. SNORM Bulk
Data entries overwrite a generated normal.
= 0.0 The generation of grid point normals is turned off. The user can define normals with the
SNORM Bulk Data entry.
< 0.0 Grid point normals are not generated. SNORM Bulk Data entries are ignored.
Caution: If the grid shown in Figure 6-2 is located on a symmetric half model boundary and, hence, Shell
2 is not present, you may attain the same result as a full model by specifying the normal
direction with the SNORM Bulk Data entry.
Grid Point
Normal
Local Normal of Shell 1 Local Normal of Shell 2
SNORM SNORM
Shell 1 Shell 2
Figure 6-2 Unique Grid Point Normal for Adjacent Shell Elements
SNORMPRT
Default = -1
PARAM,SNORMPRT,>0 writes the grid point normals of the model in the basic coordinate system to the
.f06 and/or .pch files.
SNORMPRT Switch to Print Out Normals
<0 No output
1 Print out to the punch file (.pch)
2 Print out to the print file (.f06)
3 Print out to the punch (.pch) and print file (.f06)
Main Index
CHAPTER 6 911
Parameter Descriptions
SOFTEXIT
Default = NO
In SOL 200, if soft convergence is achieved during optimization, before completing the maximum number
of design iterations, the user may request an exit with PARAM,SOFTEXIT,YES.
SOLADJC
Default = 0
PARAM SOLADJC indicates if adjoint solution vectors are to be calculated during the analysis:
-1 Do not calculate adjoint solution vectors during the analysis. Any required adjoint solution
vectors will be computed during sensitivity analysis.
>0 For ANALYSIS=DFREQ, the adjoint vectors will be computed during the solution if:
1. All frequency response DRESP1 entries are grid responses.
2. Each subcase has the same set of excitation frequencies.
3. The number of degrees-of-freedom referenced on DRESP1 entries < (number of
independent design variables + number of type-2 properties + number of spawned
nonlinear beam library properties) x (number of subcases.)
4. PARAM AUTOADJ=YES (Default)
999999 For ANALYSIS=MFREQ, the adjoint vectors will be computed during the solution if the four
items above are satisfied and SOLADJC=999999. SOLADJC=999999 cannot be used in
conjunction with FREQ3, FREQ4 or FREQ5 entries to specify excitation frequencies.
SOLID
Default = 0
SOLID also allows several models to be stored in the same graphics database created by PARAM,POST,0.
SPARSEDM
Default = YES
See SPARSEDR.
SPARSEDR
Default = YES
SPARSEDR=YES limits the data recovery matrix calculations to recover only those grid points specified on
SET commands referenced by grid point output requests (DISP, SPCF, etc.) or those points connected to
elements specified on element output requests (STRESS, FORCE, etc.). In SOL 200, the design model and
design responses are also taken into consideration for determining which grid points are needed for data
recovery.
SPARSEDM=YES is for SOL 200 and takes further advantage of small design models/responses during the
adjoint or pseudo-load sensitivity calculations.
Main Index
912 MSC Nastran Quick Reference Guide
Parameter Descriptions
These methods take advantage of very small output requests, and/or small design models in SOL 200, for
large models resulting in significant CPU and disk space savings.
If, however, the output requests and/or the size of the design model in SOL 200 require the calculation of the
solution over a large enough percentage of degrees-of-freedom, then it is more efficient to compute the
solution at all grid points. The user PARAMeter SPDRRAT (Default75) and SPDMRAT (Default60)
specifies this percentage.
The sparse data recovery method is not supported in Aeroelastic (SOL 146), Flutter (SOLs 145 and 200),
Complex Eigenvalue (SOLs 107, 110, 145, and 200), Nonlinear (SOLs 106, 129, 153, 159, and 400) and
Cyclic Symmetry Analysis (SOLs 114, 115, and 118).
The sparse data recovery method is deactivated when the following Case Control commands are specified:
EKE, ESE, EDE, and CMSENRGY.
PARAM,DDRMM is ignored under PARAM,SPARSEDR,YES. To restore the data recovery solution process
to pre-V2004 methods insert PARAM,SPARSEDR,NO.
SPARSEPH
Default = YES
The default selects the very efficient sparse data recovery method during eigenvector data recovery in
DOMAINSOLVER ACMS (PARTOPT=DOF). This method uses the same process for eigenvector data
recovery as is requested by PARAM,SPARSEDR,YES in other dynamic solution sequences like SOLs 107
through 112.
SPARSEPH will be automatically changed to NO if ACPOWER or INTENSITY calculations are requested.
These calculations require all eigenvector DOF to be computed.
PARAM,SPARSEPH,NO forces full data recovery on all degrees-of-freedom and can be significantly less
efficient if data recovery is required at only a few degrees-of-freedom. See related user parameters MDOTM
and SPARSEDR.
SPDRRAT
Default = 75
See SPARSEDR.
SPCGEN
Default = NO
SPCGEN is analogous to and described by the PUNCH keyword on the AUTOSPC Case Control
command. The specification of the AUTOSPC command overrides the specification of PARAM,SPCGEN.
SPDMRAT
Default = 60
See SPARSEDR.
SQSETID
Default = 99000001
Main Index
CHAPTER 6 913
Parameter Descriptions
See AUTOQSET.
SRCOMPS
Default = NO
SRCOMPS controls the computation and printout of ply strength ratios. If SRCOMPS=YES, ply strength
ratios are output for composite elements that have failure indices requested.
SRTELTYP
Default = 0
See S1, S1G, S1M.
SRTOPT
Default = 0
See S1, S1G, S1M.
START
Default = 0
See OLDSEQ.
STEPFCT
Real, Default = 0.666, SOL 700 only. The scale factor has an effect on the time step computation of
Lagrangian and Euler elements.
STEPFCTL
Real > 0, Default = 0.9, SOL 700 only.
Defines a scale factor to be used on the internally calculated time step. When both of STEPFCT and
STEPFCTL are defined, STEPFCTL will be used for Lagrangian elements and STEPFCT will be used for
Euler elements.
STIME
Default = 0.0 (SOLs 109, 112, 129 and 159 only)
In restarts from previous transient analysis runs, the user provides STIME = tN where tN is the last time step
of the subcase to be continued with a new or changed subcase in the new run. Thus, the loading and printout
will start from tN as though the original run contained the new subcase data.
In SOLs 109 and 112 restarts from previous SOLs 109 and 112 runs, STIME is used to specify the proper
starting time of the restart run. If STIME exceeds the last output time of the previous run, the starting time
is assumed to be the last output time. Otherwise, the starting time is assumed to be the output time of the
previous run (not necessarily the last output time) that is closest to STIME. In other words, the starting time
of the restart run need not be the last output time of the previous run, but may be any time earlier than that.
The program informs the user that it is a restart run and indicates the starting time (determined as above)
that is used for the restart run.
Main Index
914 MSC Nastran Quick Reference Guide
Parameter Descriptions
In SOLs 109 and 112 restarts, the user must ensure that the model and the constraints as well as the subcase
setup in the restart run are the same as those in the previous run. The user may, however, specify different
TSTEP and DLOAD requests in Case Control and also different TSTEP and dynamic loading entries in the
Bulk Data compared to the previous run. The loading and the results output from the restart run will start
from the new starting time.
Notes: 1. The responsibility for ensuring that the model and the constraints as well as the subcase
setup in the restart run are the same as those in the previous run is left to the user; the
program does not check for this condition. If this condition is not met, the program
may terminate the execution with a fatal error or give erroneous results.
2. Restarts in SOLs 109 and 112 using STIME > 0.0 are supported only for applied loads,
not for SPC/SPCD enforced motion. If this usage is violated, the program terminates
the execution with an appropriate fatal message.
STRUCTMP
Replaced by a keyword on the FLSPOUT Case Control command.
SUBCASID
Default = 0
PARAM,SUBCASID,n where n is greater than zero, specifies that the restart proceeds from SUBCASE n in
nonlinear static analysis, SOL 106. SUBCASID is an alternative to SUBID and is recommended over
SUBID which indicates the subcase sequence number.
SUBID
Default = 1
In SOL 106 by default, the restart proceeds from the last LOOPID in the last subcase. SUBID may be used
to specify an earlier subcase by specifying the sequential number (for SElD = 0) of the subcase. In SOLs 106
and 153, PARAM,LOOPID may also be specified for an earlier LOOPID. SUBCASID is an alternative to
SUBID and is recommended over SUBID. See Restarts for Nonlinear Static Analysis in Appendix C: Nonlinear
Analysis in MSC Nastran Reference Guide for further discussion.
SUPAERO
Default = ZONA
If SUPAERO=ZONA, then the ZONA51 code is used for supersonic aerodynamic calculations. If
SUPAERO=CPM, then the CPM method is used. If ZONA51 is not available at a particular installation,
PARAM,SUPAERO,CPM must be specified to avoid a fatal error when performing supersonic aerodynamic
analyses. Only one supersonic aerodynamics method can be selected in a given run.
Note: CPM is only supported for planar configurations.
Main Index
CHAPTER 6 915
Parameter Descriptions
SUPDOF
Default = 0
Digits 1 through 6 indicate which of the six rigid body degrees of freedom are supported for a Solution 144
run. For example, SUPDOF=35 indicates that the plunge (3) and pitch (5) degrees of freedom are supported.
This parameter is optional. If omitted, Nastran will compute these data using a numerical method.
SUPER
Default = 0 (nonsuperelement sequences)
– 1 (superelement sequences)
See OLDSEQ.
TABID
Default = 2
TABID controls the punch output for response spectra. See Appendix C in MSC Nastran Reference Guide. A
related parameter is RSPECTRA.
TABS
Default = 0.0
TABS is used to convert units of the temperature input (F or C) to the absolute temperature (R or K).
Specify:
PARAM,TABS,273.16 When Celsius is used.
PARAM,TABS,459.69 When Fahrenheit is used.
Refer to the Bulk Data entry, CREEP for a creep analysis with SOLs 106 or 153. Refer to PARAM,SlGMA for
heat transfer analysis.
TDAMP
Default = 0.0
When using enhanced modal damping for superelements (see PARAM,SESDAMP,AUG ), the user may
choose how the damping factor for the constraint modes is determined.
If TDAMP=0.0 (the default), the damping factor is averaged over all the damping coefficients defined on
TABDMP1.
If TDAMP is less than 0.0, the damping factor from TABDMP1 associated with the lowest natural frequency
is used.
If TDAMP is positive, the damping factor defined by TDAMP is used directly.
Main Index
916 MSC Nastran Quick Reference Guide
Parameter Descriptions
TESTNEG
Default = -2 for Newtons method
-1 for Arc-length method and SOLs 101-112,115,118,187, and 200
In nonlinear static analysis (SOLs 106 and 153), and differential stiffness generation with preload (SOLs 101-
112, 115, 118, 187, and 200 with STATSUB) this parameter specifies the action to take when negative terms
are encountered on the factor diagonal of matrix decomposition. Negative terms indicate that the differential
stiffness has introduced a structural instability. The instability may be real (structural buckling) or
mathematical (the current iteration appears unstable, but a stable solution exists).
TESTNEG Results
-1 Stop if negative terms occur.
1 or 0 Continue if negative terms occur.
-2 If negative terms exist, do not use differential stiffness.
2 Do not use differential stiffness.
3 Use differential stiffness with preload even if negative terms exist (SOLs 101-112,
115, 118, 187, and 200 with STATSUB only)
TFSYMFAC
Default = 1.D-08
TFSYMFAC specifies the tolerance at which matrices generated via the TFL Case Control command are
treated as anti-symmetric in the solution process. The default will not symmetrize the matrix even if the
tolerance is not exceeded. Whereas, if TFSYMFAC is negative then the absolute values is used as the tolerance
and the matrix will be symmetrized if the tolerance is exceeded. If TFSYMFAC is 0.D0 then the symmetry
is not checked.
TINY
Default = 1.E-3
Any elements with strain energy that is less than a TINY percentage of the total strain energy for any
superelement will not be printed or made available for postprocessing by MSC Patran or other programs.
TINY may also be used to suppress the printing of small numbers in the constraint check matrix [Emh]
described in Geometry Processing in SubDMAP PHASE0 in the MSC Nastran Reference Guide.
TOLRSC
Default = 0.05
When the RSSCON shell-to-solid element connector is used, the connecting grid points of the shell element
are moved on to the solid face if the grid points are close enough. The tolerable distance of the shell grid
point to the solid edge or face is h where h is the height of the solid edge; see the sample figure below.
The relative tolerance is user modifiable using the parameter.
Main Index
CHAPTER 6 917
Parameter Descriptions
PARAM,TOLRSC,
The default for the relative tolerance is = 0.05 . Rigid body invariance is satisfied with double-precision
accuracy if the shell grid points are adjusted.
TOPOCONV
Default = 80
Parameter TOPOCONV is applicable only to ESLNRO topology optimization tasks. It sets a lower bound
for the percentage of the design variables whose maximum relative changes are within the tolerance specified
by CONVDV on the DOPTPRM entry.
By default, when more then 80% of the design variables show their maximum relative changes are within
CONVDV, the job will be terminated.
TRMBIM
Default = PHYSICAL
TRMBIM is used to define the formulation used for reduced impedance matrix, RIM, for all trim
components requested under TRIMGRP case control commands. Its default is 'PHYSICAL' which will
generate RIM in physical coordinates. The other valid options for TRMBIM are.
1. 'MODAL' which will produce RIM in modal coordinates
2. 'DATACHK' which perform dry run without producing Reduce Impedance Matrix or results. Job
will be terminated afterwards.
TSTATIC
Default = -1 (SOLs 129, 159 and 400 only)
If TSTATlC = 1, a static solution may be obtained while ignoring inertial and damping forces. For SOLs 129
and 159, this option is available only with the adaptive time-stepping method (see METHOD = “ADAPT”
on the Bulk Data entry, TSTEPNL).
UGASC
SOL 700 only,
Real. Defines a value for the universal gas constant.
1. Must be used if the molar weight is used on a GAS option of the AIRBAG entry, or if molar gas
fractions are given on an INFLFRAC entry.
2. Specify only one universal gas constant per problem.
–1 –1
3. In IS units, R equals 8.3145 J mol K .
2 –2 –1 –1
Using the tonne, mm, system of units R has a value of 8314.5 tonne mm s mol K .
–1 –1 –1 –1
In imperial units, R equals 1.9859 Btu lbmol R or 1545.3 ft lbf lbmol R
UNSYMF
Main Index
918 MSC Nastran Quick Reference Guide
Parameter Descriptions
Default = NO
In SOL 106, nonlinear statics, PARAM,UNSYMF,YES is required to include damping effects in the
calculation of complex eigenvalues. See PARAM,NMLOOP.
UNSYMKB
Character, default = 'NO'
In modal solutions or real eigenvalue solutions, if the stiffness or damping matrix is not symmetric, the run
will normally terminate with a FATAL error message. Setting UNSYMKB to 'YES' will allow the run to
continue.
UPDTBSH
Default = NO
UPDTBSH controls the update of boundary shapes generated by auxiliary boundary model analysis in SOL
200. By default, the auxiliary boundary models and shapes are generated only once at the initial design cycle
and will not be updated in subsequent cycles even if the shape of the primary model is changing.
PARAM,UPDTBSH,YES requests that the auxiliary models and shapes are updated and reanalyzed at every
cycle.
USETPRT
Default = -1
USETPRT controls the tabular printout of the structural degree-of-freedom sets. See Degree-of-Freedom Sets.
To print aerodynamic degree-of-freedom sets, please see OPGEOM.
Sequence Print USETPRT
None None (Default) -1
Row sort only 0
Internal Column sort only 1
Row and Column sort 2
Row sort only 10
External Column sort only 11
Row and Column sort 12
The degrees-of-freedom can be listed in ascending order according to their internal or external sequence
number, but not both. The external sequence number is the grid, scalar, or extra point identification number.
The internal sequence number is the number assigned after resequencing (see PARAM,OLDSEQ).
For a given sequence there are two types of tables that may be printed: row sort and column sort. For row
sort, a table is printed for each set selected by USETSEL. Here is an example of row sort (USETPRT = 0 or
10):
Main Index
CHAPTER 6 919
Parameter Descriptions
U S E T D E F I N I T I O N T A B L E ( I N T E R N A L S E Q U E N C E , R O W S O R T )
A DISPLACEMENT SET
-1- -2- -3- -4- -5- -6- -7- -8- -9- -10-
1= 2-1 2-2
For column sort, a single table is printed for the following sets: SB, SG, L, A, F, N, G, R, O, S, M, E. Here
is an example of column sort (USETPRT=1 or 11):
U S E T D E F I N I T I O N T A B L E ( I N T E R N A L S E Q U E N C E , C O L U M N S O R T )
EXT GP. DOF INT DOF INT GP. SB SG L A F N G R O S M E
----------------------------------------------------------------------------------------------------------------
---
1 - 1 1- 1 G 1 1 1 1
- 2 2- 2 2 2 2
- 3 3- 1 3 3 3
- 4 4- 2 4 4 4
- 5 5- 3 5 5 5
- 6 6- 4 6 6 6
USETSEL
Default = 0
USETSEL specifies the sets which will be printed in the row sort (USETPRT = 0 or 10). In order to select
specific sets to be printed, you must sum their corresponding decimal equivalent numbers. For example, sets
A, L, and R are selected with USETSEL=128+256+8=392. To print the aerodynamic degree-of-freedom
sets: J, JS, K, KS, and SA, please see OPGEOM.
USETSEL Sets Printed
0 Sets SB, SG, L, A, F, N, G, R, O, S, M, and E
-1 All sets as defined in Degree-of-Freedom Sets.
-2 Mutually exclusive sets only; i.e., sets MP, MR, SB, SG, SZ, O, Q, R, C, B, LM, and E.
USETSTRi
Input-character-Default’ ‘
USETSTR1 through USETSTR4 specifies the sets that will be printed by the specification of parameters
USETPRT and USETSEL. Any set in Degree-of-Freedom Sets may be specified. A “:” is used as a separator. In
the following example, the m-set (degrees-of-freedom eliminated by multipoint constraints) and s-set
(degrees-of-freedom eliminated by single point constraints) are specified.
Example:
PARAM,USETSTR1,M:S
Main Index
920 MSC Nastran Quick Reference Guide
Parameter Descriptions
VARPHI
Default = /4 (0.78539816)
Feature angle for detection of singular geometric features (sharp edges or corners) in the mesh during adaptive
mesh refinement.
When adaptive meshing is requested (see Case Control command, HADAPT (Case) and Bulk Data entry,
HADAPTL), singular geometric features such as sharp edges or sharp corners must be detected. To this end the
face outward normals N1, N2 of each pair of adjacent mesh faces and the edge oriented tangents T1, T2 of
each pair of adjacent mesh edges are computed (see Figure 6-3). If the angle between N1 and N2 for mesh faces,
or between T1 and T2 for mesh edges is bigger than the feature angle , then the common edge or vertex will
be considered a splitting edge or vertex where surfaces or lines are broken and a singular geometric feature is
defined.
Edge Vertex
N1
N2
T2
T1
Faces Edge
Figure 6-3
Mesh faces and elements are preprocessed to ensure consistent orientation and that the appropriate sign of
face normals and edge tangents will be accounted for during the computation of their mutual angle.
VELCUT
Default = 1.E-6, SOL 700 only
Defines the minimum velocity in Eulerian meshes.
Format:
PARAM,VELCUT,VALUE
Example:
PARAM,VELCUT,1.0E-6
VALUE Minimum velocity. (Real > 0.0)
Main Index
CHAPTER 6 921
Parameter Descriptions
Remark:
Any velocity less than VELCUT is set to zero. It is mainly used to eliminate harmless but annoying small
values of velocity caused by round-off error and numerical dispersion.
VMOPT
Default = 0
By default (VMOPT=0), virtual mass is included after the component modes are computed. Virtual mass is
not taken into consideration when using GRAV, RFORCE, or ACCEL loading.
If VMOPT=1, then the virtual mass will be included in the mass matrix at the same time as all other mass
elements. In other words, the component modes will reflect the virtual mass. Virtual mass is taken into
consideration when using GRAV, RFORCE, or ACCEL loading.
If VMOPT=2, the modes of the structure or component without the fluid are computed first (“dry” modes).
The fluid effects are added to the modal basis during the residual flexibility computation to produce the “wet”
modes for the component. Both eigenvalue tables are printed, allowing comparison of the dry and wet modes.
The wet modes are used in modal dynamic analysis. Cost savings result from the dense Virtual Mass (VM)
matrix being kept out when computing dry modes in the physical basis. Its presence can increase memory
and computation times by an order of magnitude. The VM is added only to the smaller generalized basis used
in Residual Flexibility Computations. The approximations introduced by this approach are generally small
due to the homogeneous nature of the fluid. It is the preferred method when the number of wetted elements
exceeds several hundred, for reasons of efficiency. It is to be noted that MAX normalization for eigenvectors
with PARAM,VMOPT,2 may produce incorrect results. Therefore, MAX normalization is not
recommended when using PARAM,VMOPT,2.
If VMOPT is not equal to 0, 1 or 2, then no virtual mass is computed.
VREF
Default = 1.0
In modal flutter analysis, the velocities are divided by VREF to convert units or to compute flutter indices.
WHIRLOPT
Default = FWD
Control forward whirl or backward whirl analysis for SYNC option in SOL 107/110 and SOL 108/111 for
analysis in rotating reference frame using the ROTOR entry.
Usage:
PARAM, WHIRLOPT, FWD: For forward whirl analysis
PARAM, WHIRLOPT, BWD: For backward analysis
WMODAL
Default = NO
In Modal Transient analysis (SOL 112), PARAM, WMODAL, YES will automatically produce accurate
conversion at all frequencies using the modal frequencies based on the eigenvalues as shown below. This
Main Index
922 MSC Nastran Quick Reference Guide
Parameter Descriptions
relieves the user of trying to determine the “best” value for (PARAM, W3 and W4). Note, use of WMODAL
does not suppress user specified values of W3 and W4.
1 1 0 0 1 1 0 0
0 1 2 0 0 1 2 0
GK 1
dq + 4
K dd
·· ·· · ·· dd dq ·· ·· · ··
· · · · · · · ·
· ·
0 0 1 q 0 0 1 q
Note the CBUSH, CELAS1, CELAS2, CELAS3, and CFAST elements when computing the element forces
for data recovery do not currently take into account the WMODAL conversion in SOL112.
WRBEAMB
Integer, Default = 0
0 Write equivalent radius for all beams (see PARAM, BEAMBEA) whether beam-beam contact is
anticipated or not. The equivalent radius is the 7th field of Marc’s GEOMETRY values for beam
type elements.
-1 Do not write equivalent radius (7th field is blank). This might be necessary for versions of Marc
earlier than 2003.
WTMASS
Default = 1.0
The terms of the structural mass matrix are multiplied by the value of WTMASS when they are generated.
In coupled fluid-structure analysis WTMASS is applied to the structural portion of the model only.
WTMASS applies to MFLUID entries but it is not recommended for use in hydroelastic problems.
W3, W4, W3FL, W4FL
Default = 0.0
The damping matrix for transient analysis is assembled from the equation:
1 2 G 1 1 4
B dd = B dd + B dd + -------- K dd + -------- K dd
W3 W4
In coupled fluid-structure analysis, W3 and W4 are applied to structural portion of the model and W3FL
and W4FL to the fluid portion of the model. The default values of 0.0 for W3, W4, W3FL, and W4FL cause
1 4
the K dd and K dd items to be ignored in the damping matrix, regardless of the presence of the PARAM,
4
G or GFL or K dd .
Main Index
CHAPTER 6 923
Parameter Descriptions
4
K dd is the structural damping and is created when GE is specified on the MATi entries.
1
K dd is the stiffness. The units of W3, W4, W3FL, and W4FL are radians per unit time. (See Real
Eigenvalue Analysis in SubDMAPs SEMR3 and MODERS in the MSC Nastran Reference Guidefor further discussion.)
In SOLs 129 and 159, W4 may vary between subcases. However, the linear portion of the model uses only the
W4 value from the first subcase and the values in the subsequent subcases are applied to the nonlinear portion of
the model.
Parameters G, W3, W4 are case control selectable by either the PARAM entries in Case Control, or
RSDAMP or SEDAMP appearing in Case Control pointing to a bulk data DAMPING entry. If both
DAMPING type entries and PARAM entries occur in a subcase, the DAMPING entries take precedence.
When there is no Parameters G, W3, W4 or DMAPING reference in the first Case Control, the Bulk Data
specification (if any) will be used. Subsequent Case Control specification will override the Bulk Data
specification and Case Control rules apply to subsequent specifications.
The CBUSH, CELAS1, CELAS2, CELAS3, and CFAST elements when computing the element forces for
data recovery take into account W3 and W4 in SOL109 and SOL112.
Linear CBUSH, CELAS1, CELAS2, CELAS3, and CFAST elements when computing the element forces for
data recovery take into account W3 and W4 in SOL400 with ANALYSIS=NLTRAN. These elements behave
in SOL400 with ANALYSIS=NLTRAN in a linear fashion when PARAM, LGDISP, -1 (Default) and there
are no PBUSHT referring to the CBUSH or PELAST entries referring to the CELAS1, CELAS2, CELAS3.
For linear CBUSH, CELAS1, CELAS2, CELAS3, and CFAST elements in SOL400 with
ANALYSIS=NLTRAN, SOL400 considers Case Control specification of G, W3, or W4 as a data recovery
boundary condition change and each STEPi for the linear elements will pick up the appropriate G, W3, and
W4 values.
Any of these elements in SOL400 with ANALYSIS=NLTRAN that are nonlinear only use the standard force
output data recovery F=Ku(t) since nonlinear elements compute only the unbalanced stiffness force.
In SOL129 or SOL159 linear CBUSH, CELAS1, CELAS2, CELAS3, and CFAST elements (determined as
in SOL400 above) should never have G, W3, or W4 selected in the Case Control as the linear force recovery
will be incorrect as only the G, W3, and W4 of the first subcase is used.
In SOL129, the FUSE option of the CBUSH should never be used if GE or B is specified for the fusing
CBUSH. This is because, unlike SOL400, SOL129 does not update the B or K4 matrix after the CBUSH
fuses. Thus remnant CBUSH forces due to damping will be present.
WR3, WR4, WRH
Default = 0.0, no rotor damping or circulation terms.
Specifies “average” excitation frequency for calculation of rotor damping and circulation terms. See
“Equations Used in Analyses” in the MSC Nastran 2004 Release Guide for equations. The units of WR3,
WR4, and WRH are radians per unit time.
XFACT
Default=0.5
Main Index
924 MSC Nastran Quick Reference Guide
Parameter Descriptions
Additional factor to determine upper bound for Q-set reorthogonalization subspace, for ACMS
VERSION=NEW (module ACMS1). Values should range between 0.1 and 1.0. Note that PARAM,XFACT
only affects XFACT for STRUCT. For the FLUID model, see DOMAINSOLVER.
XFACTX
Default=1.0
Multiplier applied to user’s maximum frequency to determine maximum frequency for reorthogonalization
for ACMS VERSION=NEW (module ACMS1). Values should range between 0.1 and 1.0. Note that
PARAM,XFACTX only affects XFACT for STRUCT. For the FLUID model, see DOMAINSOLVER.
XFLAG
Default = 0
By default (XFLAG = 0), when temperature loads and element deformations are present, the element strain
energy for the linear elements is calculated using the following equation:
1 T T
E = --- u K e u – u P et
2
where u is the deformation, Ke is the element stiffness and Pet is the element load vector for temperature
differences and element deformations. If XFLAG is set to 2, the element strain energy for linear elements is
calculated using the following equation:
1 T 1 T
E = --- u K e u – --- u P et
2 2
The latter formula is the same strain energy calculation used for nonlinear elements.
When requesting Case Control commands ESE or EDE and executing SOL 108 or SOL 111 or
ANALYSIS=DFREQ or ANALYSIS=MFREQ in SOL200 or SOL400 and if the user has included the
parameter PARAM, BUSHNM, NO, if frequency dependent elements are detected (CBUSH if referred to
by PBUSH/PBUSHT; CELAS1, CELAS3 if referred to by PELAS/PELAST; CDAMP1, CDAMP3 if
referred to by PDAMP/PDAMPT), Nastran will automatically remove the entire class of CBUSH, or
CELAS1, or CELAS3, or CDAMP1, or CDAMP3 elements, whether or not all of a class are frequency
dependent, from the residual (SE0) energy calculations because frequency dependent elements are not fully
implemented in the ESE/EDE calculations and may result in wrong answers. USER INFORMATION
MESSAGE 5245 will be issued for each class removed. If the user wishes to override this removal, set XFLAG
to 32. If the user wants XFLAG=2 and XFLAG=33, then set XFLAG=34.
If negative strain energy is desired the THRESH value on the Case Control ESE needs to be turned off, this
is done by setting XFLAG=16384 to override tiny screening for ESE. This will yield all strain energy plus,
minus, zero of all elements selected.
XYMPCH
Default = NO
Main Index
CHAPTER 6 925
Parameter Descriptions
The XYPLOT/XYPUNCH commands do not support SOL103 type mode shapes. XYMPCH when set to
a value PARAM, XYMPCH, YES allows the XYPUNCH command XYPUNCH, DISP, RESPONSE / …
to punch without selective selection SOL103 mode shapes as SOL101 type displacements. For example:
$
METHOD = 10
SET 100 = 6, 7, 13
PARAM, XYMPCH, YES
DISP=100
MODES=20 $
…
OUTPUT(XYPLOT)
XYPUNCH DISP RESPONSE / 6(T3) $
XYPUNCH DISP RESPONSE / 7(T3) $
XYPUNCH DISP RESPONSE / 13(T2) $
A more modern solution is to include in a standard SOL103 run the Nastran entry
NASTRAN HDF5=0
With for example DISP(PLOT)=ALL
And extract the resulting mode shapes from the resulting HDF5 Data Base.
Then the PARAM, XYMPCH, and MODES=n is not needed nor is any of the OUTPU(XYPLOT)
commands.
XYUNIT, n
n XYUNIT is used in conjunction with an FMS ASSIGN statement to specify the unit number for
the storage of design optimization results and design sensitivity data in comma separated value
format for use in a spreadsheet in SOL 200 or the‘ storage of trim results in SOL 144.
ZROCMAS
Default = NO
When performing component modal synthesis with free or mixed boundary conditions, the c-set mass is
normally included during the calculation of the component modes. If the component has large masses on the
c-set degrees-of-freedom, or if the user requests too many modes for the component, the c-set residual
flexibility will become singular. This causes a failure of the component reduction. The singularity may be
avoided by setting ZROCMAS to YES, which will exclude the c-set mass when calculating the component
modes.
ZROVEC
Default=1.E-06
ZROVEC specifies the tolerance at which a residual vector is not linearly independent and subsequently
removed from the residual vector computation process.
Main Index
926 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Parameter Applicability Tables
Table 6-1, Table 6-2, Table 6-3, Table 6-4, and Table 6-5 list parameter applicability to the solution sequences
(SOLs 101 through 114).
Table 6-6, Table 6-7, Table 6-8, Table 6-9, Table 6-10, Table 6-11, Table 6-12, Table 6-13, Table 6-14, and Table 6-15
list parameter applicability to the solution sequences (SOLs 115 through 700).
B Must be specified in the Bulk Data Section only.
E May be specified in either the Bulk Data and/or Case Control Section.
C Must be specified in the Case Control Section only.
Note that only part of the Parameters are supported in NLPERF SOL 400. Please refer to Ap. C: NLPERF
SOL 400 for the supported parameters.
Main Index
CHAPTER 6 927
Parameter Applicability Tables
Table 6-1 PARAMeter Names in SOLs 101 Through 114 Part 1
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
ACEXTMTD B
ACEXTSET B
ACOUT B E E E E E E
ACOWEAK B
ACSYM B B
ADJMETH
ADMPOST E E
ADPCON E
ADSTAT B B B
AERODOF
AESDISC
AESMAXIT
AESMETH
AESRNDM
AESTOL
ALPHA1 B B B B B B
ALPHA2 B B B B B B
ALPHA1FL
ALPHA2FL
ALTRED B B B
ARBMASP
ARBMFEM
ARBMPS
ARBMSS
ARBMSTYP
ARF
ARS
ASCOUP B B B B B B B B B B B
ASING E E E E E E E E E E E
AUNITS
AUTOADJ
AUTOGOUT E E E E E E E E E E E
Main Index
928 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-1 PARAMeter Names in SOLs 101 Through 114 Part 1 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
AUTOMSET E E E E E E E E E E
AUTOQSET E E E E E E E E E E E
AUTOSPC E E E E E E E E E E E
AUTOSPCR E
AUTOSPRT E E E E E E E E
BAILOUT E E E E E E E E E E E
BEAMBEA
BEIGRED E E E E E E E
BETA
BIGER E E E E
BIGER1 E E E E
BIGER2 E E E E
BUCKLE E
BWKD B B B B B B
CAMPBELL E E
CASPIV E
CB1, CB2 E E E E E E E E E E E
CDIF
CFDIAGP E E E E E E E E E E E
CFRANDEL E E E E E E E E E E E
CHECKOUT E E E E E E E E E E E
CK1, CK2, E E E E E E E E E E E
CK3
CLOSE B
CM1, CM2 E E E E E E E E E E E
CONFAC B B B B B B B B B B B
COUPMASS E E E E E E E E E E E
CP1, CP2 E E E E E E E E
CQC B
CURV E E E E
CURVPLOT E E E E E
CWDIAGP E E E E E E E E E E E
CWRANDEL E E E E E E E E E E E
Main Index
CHAPTER 6 929
Parameter Applicability Tables
Table 6-1 PARAMeter Names in SOLs 101 Through 114 Part 1 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
DBALL E E E E E E E E E E E
DBCCONV E E E E E E E E E E E
DBCDIAG E E E E E E E E E E E
DBCOVWRT E E E E E E E E E E E
DBDICT B B B B B B B B B B B
DBDN E E E E E E E E E E E
Table 6-2 PARAMeter Names in SOLs 101 Through 114 Part 2
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
DBDRPRJ B B B B B B B B B B B
DBDRVER B B B B B B B B B B B
DBEXT E E E E E E E E E E E
DBRCV E E E E E E E E E E E
DBUP E E E E E E E E E E E
DDRMM B B
DESPCH
DESPCH1
DFREQ B B
DOPT E E E E
DPEPS
DSNOKD B
DSZERO B B B
DYNSPCF E E E E E E E
EIGFILT B B
ENFMETH E E E E
ENFMOTN E E E E
ERPC
ERPREFDB
ERPRHO
ERPRLF
ERROR E E E E E E E E E E E
Main Index
930 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-2 PARAMeter Names in SOLs 101 Through 114 Part 2 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
ESLFSAV
ESLMOVE
ESLRCF
EST E E E E E E E E E E E
EXCLUDE E
EXTUNIT B B B B B B B B B B B
FACTOR B B B B B B B B B B B
FBATOLR E E
FBLEND
FIXEDB E E
FKSYMFAC E
FLUIDSE B B B B B B B
FOLLOWK E E E E E E E E E
FRQDEPO B B
FULLSEDR E E E E E E E E E E E
FZERO E E E E E E E E
G E E E E E E
GEOMU E E E E E E E E E E E
GFL B B B B B B
GPECT E E E E E E E E E E E
GRAVSET E E E E E E E E E E
GRDPNT E E E E E E E E E E E
GUSTAERO
GYROAVG E E
GYROFATL E E E E
HEATSTAT B
HFREQ B B B
HFREQFL B B B
HTOCITS E
HTOCPRT E
HTOCTOL E
IFP E E E E E E E E E E E
INREL E E
Main Index
CHAPTER 6 931
Parameter Applicability Tables
Table 6-2 PARAMeter Names in SOLs 101 Through 114 Part 2 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
IRES E E E E E E E E
ITAPE B B B
IUNIT B B B
KDAMP B B B
KDAMPFL B B B
KDIAG E
K6ROT E E E E E E E E E E E
LANGLE B
LFREQ B B B
LFREQFL B B B
Table 6-3 PARAMeter Names in SOLs 101 Through 114 Part 3
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
LGDISP E
LMFACT B B B
LMODES E B B B
LMODESFL B B B
LOADU E E E E E E E E E E E
LOOPID E
MACH
MAXLP
MAXRATIO E E E E E E E E E E E
MDK4OPT B B B B
MDOPT14 B B B B
MDOTM B B B B
MDOTMFAC B B B B
MDREDOPT B B B B
MESH B
METHCMRS E E E E E E E
MHRED E E E E E E E
MINIGOA B B B B B B B B B B B
Main Index
932 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-3 PARAMeter Names in SOLs 101 Through 114 Part 3 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
MODACC B B B
MODEL B B B B B B B B B B B
MPCX B B B B B B B B B B B
MPTUNIT
MXICODE0
NASPRT
NDAMP
NHPLUS
NINTPTS E E E E
NLAYERS E
NLHTLS E
NLHTOL
NLHTWK
NLMAX E E E E E E E E
NLMIN E E E E E E E E
NMLOOP E
NMNLFRQ E E
NOCOMPS E E E E E
NOELOF E E E E
NOELOP E E E E
NOGPF E E E E
NONCUP B
NQSET E E E E E E E
NLTOL B
NUMOUT E E E E
NUMOUT1 E E E E
NUMOUT2 E E E E
OCMP E E E E E
OEE E E E E E
OEF E E E E E E E E E E E
OEFX E E E E E E E E E E E
OELMOPT E E E E E E E E E E E
OELMSET E E E E E E E E E E E
Main Index
CHAPTER 6 933
Parameter Applicability Tables
Table 6-3 PARAMeter Names in SOLs 101 Through 114 Part 3 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
OES E E E E E E E E E E E
OESE E E E E E E E E E E E
OESX E E E E E E E E E E E
OG E E E E E
OGEOM E E E E E E E E E E E
OGPF E E E E E
OGPS E E E E E E
OGRDOPT E E E E E E E E E E E
OGRDSET E E E E E E E E E E E
OLDSEQ B B B B B B B B B B B
OMAXR E E E E E E E E E E E
OMID E E E E E E E E E
OMSGLVL E E E E E E E E E E E
OPCHSET E E E E E E E E E E E
OPG E E E E E E E E
OPGEOM
Table 6-4 PARAMeter Names in SOLs 101 Through 114 Part 4
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
OPGTKG
OPPHIB
OPPHIPA
OPTEXIT
OPTION B
OQG E E E E E E E E E E E
OSETELE E E E E E E E E E E E
OSETGRD E E E E E E E E E E E
OSWELM B B B B B B B B B B B
OSWPPT B B B B B B B B B B B
OUG E E E E E E E E E E E
OUGCORD E E E E E E E E E E E
Main Index
934 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-4 PARAMeter Names in SOLs 101 Through 114 Part 4 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
OUGSPLIT E E E E E
OUMU E
OUNIT1 E E E E E E E E E E E
OUNIT2 E E E E E E E E E E E
OUTOPT E E E E E
PACINFID B B
PATPLUS E E E E E E E E E E E
PATVER E E E E E E E E E E E
PCOMPRM B B B B B
PDRMSG E E E E E E E E E E E
PENFN B B B
PLTMSG E E E E E E E E E E E
POST E E E E E E E E E E E
POSTEXT E E E E E E E E E E E
POSTU E E E E E E E E E E E
PREFDB E E E E
PRINT
PROUT E E E E E E E E E E E
PRPA E E
PRPHIVZ E E E E E E E E
PRPJ E E E E E E E
PRTBGPDT E E E E E E E E E E E
PRTCSTM E E E E E E E E E E E
PRTEQXIN E E E E E E E E E E E
PRTGPDT E E E E E E E E E E E
PRTGPL E E E E E E E E E E E
PRTGPTT E E E E E E E E E E E
PRTMAXIM E E E
PRTMGG E E E E E E E E E E E
PRTPG E E E E E E E E E E E
PRTRESLT E E E E E E E E E E E
Q
RBSETPRT E E E E E E E E E E E
Main Index
CHAPTER 6 935
Parameter Applicability Tables
Table 6-4 PARAMeter Names in SOLs 101 Through 114 Part 4 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
RESLTOPT E E E E E E E E E E E
RFORSET E E E E E E E E E E
RHOCP
RSPECTRA E E
RSPRINT E E
RSTTEMP E
S1 E E E E E E E
S1A E E E E E
S1AG E E E E E
S1AM E E E E E
S1G E E E E E
S1M E E E E E
SCRSPEC B
SEMAP B B B B B B B B B B B
SEMAPOPT B B B B B B B B B B B
SEMAPPRT B B B B B B B B B B B
SENSUOO
SEP1XOVR B B B B B B B B B B B
SEQOUT B B B B B B B B B B B
SERST B B B B B B B B B B B
SESDAMP E E E E E E E
SESEF E
Table 6-5 PARAMeter Names in SOLs 101 Through 114 Part 5
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
SHLDAMP E E E E E E
SIGMA
SKINOUT E E E E E E E
SKPAMP
SLOOPID
SMALLQ B B B B B B B B B B B
Main Index
936 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-5 PARAMeter Names in SOLs 101 Through 114 Part 5 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
SNORM B B B B B B B B B B B
SNORMPRT B B B B B B B B B B B
SOFTEXIT
SOLADJC
SOLID B B B B B B B B B B B
SPARSEDM E E E E E E E
SPARSEDR E E E E E E E
SPARSEPH E E E E
SPDDMAT
SPDRRAT E E E E E E E
SQSETID E E E E E E E E E E E
SRTELTYP E E E E
SRTOPT E E E E
START B B B B B B B B B B B
STIME E E
SUBCASID E
SUBID E
SUPAERO
SUPER B B B B B B B B B B B
TABID E E
TABS
TESTNEG E
TFSYMFAC E E E E E E
TINY E E E E
TOLRSC B B B B B B B B B B B
TSTATIC
UNSYMF B
UNSYMKB B B B B B B B
UPDTBSH
USETPRT E E E E E E E E E E E
USETSEL E E E E E E E E E E E
VARPHI C
VMOPT E E E E E E E E E E
Main Index
CHAPTER 6 937
Parameter Applicability Tables
Table 6-5 PARAMeter Names in SOLs 101 Through 114 Part 5 (continued)
Solution Sequence Numbers (101 through 114)
PARAMeter
Name 101 103 105 106 107 108 109 110 111 112 114
VREF B B
WTMASS E E E E E E E E E E E
W3 E E
W3FL E E
W4 E E
W4FL E E
XFACT B B
XFACTX B B
XFLAG E E E
XYUNIT
ZROCMAS E E E E E E E E
ZROVEC E E E E E E E E
Table 6-6 PARAMeter Names in SOLs 115 Through 700 Part 1
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
ACEXTMTD B
ACEXTSET B
ACOUT E
ACOWEAK B
ACSYM B
ADJMETH B
ADPCON E E E E
ADSTAT
AERODOF E E E E
AESDISC B B
AESMAXIT B B
AESMETH B B
AESRNDM B B
AESTOL B B
ALPHA1 B E B B B B B E
ALPHA2 B E B B B B B E
Main Index
938 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-6 PARAMeter Names in SOLs 115 Through 700 Part 1 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
ALPHA1FL
ALPHA2FL
ALTRED
ARBMASP
ARBMFEM
ARBMPS
ARBMSS
ARBMSTYP
ARF
ARS
ASCOUP
ASING
AUNITS
AUTOADJ
AUTOGOUT E E E E E E E E E E E
AUTOMSET E E E E E E E*
AUTOQSET E E E E E E E E E E
AUTOSPC
AUTOSPCR E
AUTOSPRT E E E E E E E E
BAILOUT E E E E E E E E E E E
BEAMBEA
BEIGRED E E E E E E
BETA E E
BIGER E E E E E
BIGER1 E E E E E
BIGER2 E E E E E
BUCKLE
BWKD B B
CAMPBELL E E
CASIEMA E
CASPIV E E
CB1, CB2 E E E E E E E E E E E
Main Index
CHAPTER 6 939
Parameter Applicability Tables
Table 6-6 PARAMeter Names in SOLs 115 Through 700 Part 1 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
CDIF E
CFDIAGP E E E E E E E E E E E
CFRANDEL E E E E E E E E E E E
CHECKOUT E E E E E E E E E E E
CK1, CK2, CK3 E E E E E E E E E E E
CLOSE B
CM1, CM2 E E E E E E E E E E E
CONFAC B B B B B B B B B B B
COUPMASS E E E E E E E E E E E
CP1, CP2 E E E E E E E E
CQC E
CURV E E E E E
CURVPLOT E E E E E
CWDIAGP E E E E E E E E E E E
CWRANDEL E E E E E E E E E E E
DBALL E E E E E E E E E E
DBCCONV E E E E E E E E E E
*For SOL400, AUTOMSET is only valid in SOL400 for RIGID=LINEAR. For RIGID=LAGRAN,
rigid elements become actual physical elements.
Table 6-7 PARAMeter Names in SOLs 115 Through 700 Part 2
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
DBCDIAG E E E E E E E E E E
DBCOVWRT E E E E E E E E E E
DBDICT B B B B B B B B B B
DBDRPRJ B B B B B B B B B B
DBDRVER B B B B B B B B B B
DBDN E E E E E E E E E E
DBEXT E E E E E E E E E E E
DBRCV E E E E E E E E E E
DBUP E E E E E E E E E E
Main Index
940 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-7 PARAMeter Names in SOLs 115 Through 700 Part 2 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
DDRMM B E
DEACTEL E
DECLUMP B
DESPCH E
DESPCH1 E
DFREQ B B B
DOPT E E E E
DPEPS B
DPHFLG
DSNOKD B
DSZERO
DV3PASS B
Main Index
CHAPTER 6 941
Parameter Applicability Tables
Table 6-8 PARAMeter Names in SOLs 115 Through 700 Part 3
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
DYNSPCF E E E E E
ENFMETH E E
ENFMOTN E E
EPPRT
EPSILONT
EPZERO
ERPC
ERPREFDB
ERPRHO
ERPRLF
ERROR E E E E E E E E E E
ESLFSAV E
ESLLCOMP E
ESLMOVE E
ESLMPC1 E
ESLOPTEX E
ESLPRT E
ESLPRT1 E
ESLRCF E
EULBND B
EULSTRES B
EXTUNIT B B B B B B B B B B
FACTOR B B B B B B B B B B
FBATOLR
FBLEND B
FIRSTKI B B B
FIXEDB E
FKSYMFAC E
FLEXINCR
FLUIDMP
FLUIDSE B
FMULTI B
Main Index
942 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-8 PARAMeter Names in SOLs 115 Through 700 Part 3 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
FOLLOWK E E E E
FRQDEPO B B
FULLSEDR E E E E E E E E E E E
FZERO E
G E E E E E E
GEOMU E E E E E E E E E E
GPECT E E E E E E E E E E
GRADMESH B
GRAVSET E E E E E E E E E E E
GRDPNT E E E E E E E E E E
Main Index
CHAPTER 6 943
Parameter Applicability Tables
Table 6-9 PARAMeter Names in SOLs 115 Through 700 Part 4
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
GUSTAERO B B B
GYROAVG
GYROFATL E
HEATSTAT
HFREQ B B B
HFREQFL B B
HTOCITS
HTOCPRT
HTOCTOL
IFP E E E E E E E E E
INREL E
INRLM
IRES E E E E E E E E E
ITAPE B
IUNIT B
KDAMP B B
KDAMPFL B B
KDIAG E E
K6ROT E E E E E E E E E E
LANGLE B B B B
LDSUM E E
LFREQ B B B
LFREQFL B B
LGDISP E E E E
LMFACT B
LMODES B B B
LMODESFL B B
LOADU E E E E E E E
LOOPID E E E E
MACH B
Main Index
944 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-10 PARAMeter Names in SOLs 115 Through 700 Part 6
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
MAXLP E E
MAXRATIO E E E E E E E E E E
MDK4OPT B
MDOPT14 B
MDOTM B
MDOTMFAC B
MDREDOPT B
MESH B B B
METHCMRS E E E E E E
MHRED E E E E E E E
MICRO B
MINIGOA B B B B B B B B B B
Table 6-11 PARAMeter Names in SOLs 115 Through 700 Part 7
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
MODEL B B B B B B B B B B
MPCX B B B B B B B B B B
MPTUNIT E
Table 6-12 PARAMeter Names in SOLs 115 Through 700 Part 8
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
MXLAGM1 B
NASPRT B
NDAMP E E E
NDAMPM E
NINTPTS E E E E
NLAYERS E E
NLHTLS E E
Main Index
CHAPTER 6 945
Parameter Applicability Tables
Table 6-12 PARAMeter Names in SOLs 115 Through 700 Part 8
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
NLMAX E
NLMIN E E
NMLOOP
NMNLFRQ E* E*
NOCOMPS E E E E E
NOELOF E E E E
NOELOP E E E E
NOGPF E E E E
NOMSGSTR E E E E
NONCUP B
NQSET E E E E E E E
NLTOL E B
NUMOUT E E E E
NUMOUT1 E E E E
* ANALYSIS=MFREQ or ANALYSIS=DFREQ only.
Table 6-13 PARAMeter Names in SOLs 115 Through 700 Part 9
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
NUMOUT2 E E E E
OCMP E E E
OEE E E E
OEF E E E E E E E E E E
OEFX E E E E E E E E E E
OELMOPT E E E E E E E E E E E
OELMSET E E E E E E E E E E E
OES E E E E E E E E E E
OESE E E E E E E E E E E
OESX E E E E E E E E E E
OG E E E E E
OGEOM E E E E E E E E E E
OGPF E E E E
Main Index
946 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-13 PARAMeter Names in SOLs 115 Through 700 Part 9 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
OGPS E E E
OGRDOPT E E E E E E E E E E E
OGRDSET E E E E E E E E E E E
OLDSEQ B B B B B B B B B B
OMAXR E E E E E E E E E E
OMID E E E E E E E E E E
OMSGLVL E E E E E E E E E E E
OPCHSET E E E E E E E E E E E
OPG E E E E E E E
OPGEOM E E E E
OPGTKG B B B B
OPPHIB B B B
OPPHIPA B B B
OPTEXIT B
OPTION B
OQG E E E E E E E E E E
OSETELE E E E E E E E E E E E
OSETGRD E E E E E E E E E E E
OSWELM B B B B B B B B B
OSWPPT B B B B B B B B B
OUG E E E E E E E E E E
OUGCORD E E E E E E E E E E
OUGSPLIT E E E E E E
OUMU E E
OUNIT1 E E E E E E E E E E
OUNIT2 E E E E E E E E E E
OUTOPT E E E E E
PARTMEM
PATPLUS E E E E E E E E E E
PATVER E E E E E E E E E E
PDRMSG E E E E E E E E E E
PENFN B
PH2OUT B
Main Index
CHAPTER 6 947
Parameter Applicability Tables
Table 6-13 PARAMeter Names in SOLs 115 Through 700 Part 9 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
PLTMSG E E E E E E E E E E
POST E E E E E E E E E E
POSTEXT E E E E E E E E E E E
POSTU E E E E E E E E E E
PREFDB E
PRINT B B
PROUT E E E E E E E E E E
PRPA E E E
PRPHIVZ E E E E E E E E
PRPJ E E E E E E
PRTCSTM E E E E E E E E E E
PRTEQXIN E E E E E E E E E E
PRTGPDT E E E E E E E E E E
PRTGPL E E E E E E E E E E
PRTGPTT E E E E E E E E E E
PRTMAXIM E E E E E E E E E
PRTMGG E E E E E E E E E E
PRTPG E E E E E E E E E E
PSENPCH B
Table 6-14 PARAMeter Names in SOLs 115 Through 700 Part 10
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
PVALINIT B
Q B
RADMOD B B B
RBSETPRT E E E
RESLTOPT E E E E E E E E E E E
RFORSET E E E E E E E E E E E
RHOCP
RKSCHEME B
RMSINT
Main Index
948 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-14 PARAMeter Names in SOLs 115 Through 700 Part 10 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
ROHYDRO B
ROMULTI B
ROSTR B
RSPECTRA
RSPRINT
RSTTEMP
S1 E E E E E
S1A E E E E E
S1AG E E E E E
S1AM E E E E E
S1G E E E E E
S1M E E E E E
SCRSPEC B
SEMAP B B B B B B B B B B
SEMAPOPT B B B B B B B B B B
SEMAPPRT B B B B B B B B B B
SENSUOO B
SEP1XOVR B B B B B B B B B B
SEQOUT B B B B B B B B B B
SERST B B B B B B B B B B
SESDAMP E E E E E
SESEF E
SHLDAMP E
SIGMA B
SKINOUT E
SKPAMP B B B
SLOOPID E
SMALLQ B B B B B B B B B B
SNORM B B B B B B B B B B
SNORMPRT B B B B B B B B B B
SOFTEXIT B
SOLADJC B
SOLID B B B B B B B B B B
Main Index
CHAPTER 6 949
Parameter Applicability Tables
Table 6-14 PARAMeter Names in SOLs 115 Through 700 Part 10 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
SPARSEDM E E
SPARSEDR E E
SPARSEPH E E E
SPDMRAT E
SPDRRAT E E
SQSETID E E E E E E E E E E E
STEPFCT B
STEPFCTL B
SRTELTYP E E E E
SRTOPT E E E E
START B B B B B B B B B
STIME E E
STRUCTMP E
SUBCASID E
SUBID E E
SUPAERO E E E E
SUPDOF B
SUPER B B B B B B B B B B
TABID
TABS E E E
TESTNEG E E
TFSYMFAC E E E E E E E E
Table 6-15 PARAMeter Names in SOLs 115 Through 700 Part 11
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
TINY E E E E
TOLRSC B B B B B B B B B B
TOPOCONV E
TSTATIC E E E
UNSYMF B
UNSYMKB B B B B B B B
Main Index
950 MSC Nastran Quick Reference Guide
Parameter Applicability Tables
Table 6-15 PARAMeter Names in SOLs 115 Through 700 Part 11 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 700
UPDTBSH E
USETPRT E E E E E E E E E E
VARPHI C
VELCUT B
VMOPT E E E E E E E E E E
VREF B B
WTMASS E E E E E E E E E E
W3 B E B E
W3FL B
W4 B E B E
W4FL B
XFLAG E E
XYUNIT E E
ZROCMAS E E E E E E E E
ZROVEC E E E E E E E E
Main Index
Chapter 7: Item Codes
MSC Nastran Quick Reference Guide
7 Item Codes
Item Code Description
Element Stress (or Strain) Item Codes
Element Force Item Codes
Fluid Virtual Mass Pressure Item Codes
2D Slideline and 3D Surface Contact Item Codes
Element Strain Energy Item Codes
Fatigue Item Codes for LOC=ELEM on FTGPARM
Fatigue Item Codes for LOC=NODE or NODA on FTGPARM
Item Codes for Fatigue Analysis of Spot Welds
Item Codes for Fatigue Analysis of Seam Welds
Equivalent Radiated Power (ERP) Item Codes
Main Index
954 MSC Nastran Quick Reference Guide
Item Code Description
Item Code Description
Item codes are integer numbers assigned to specific output quantities; such as, the third translational
component of displacement, the major principal stress at Z1 in a CQUAD4 element, or the torque in a
CBAR element. Item codes are specified on the following input statements:
DRESP1 entry for Design Sensitivity and Optimization (SOL 200).
X-Y Plotting commands. See Plotting in the MSC Nastran Reference Guide.
DTI,INDTA entry for stress sorting.
The following tables provide item codes for:
Table 7-1. Element Stress or Strain.
Table 7-5. Element Force.
Table 7-7. Fluid Virtual Mass Pressure.
Table 7-8. Heat Transfer Flux.
Table 7-9. Slideline Contact Output.
Table 7-12. Element Strain Energy Item Codes.
Table 7-13. Fatigue Item Codes (LOC=ELEM)
Table 7-14 Fatigue Item Codes (LOC=NODE or NODA)
Table 7-15. Item Codes for Fatigue Analysis of Spot Welds
Table 7-16. Item Codes for Fatigue Analysis of Seam Welds
Table 7-17 Equivalent Radiated Power (ERP) Item Codes
The following superscripts appear in the tables and indicate:
1. Data for components marked with the symbol (1) are included in the data block MES and MEF
outputs from modules DRMH1/DRMH3 and DRMS1. DRMH1/DRMH3 are used in
EXTSEOUT Case Control processing. (See MSC Nastran DMAP Programmer’s Guide.)
2. Composite Element Stresses and Failure Indices.
Element Stress (or Strain) Item Codes
All item codes refer to stresses (or strains) unless otherwise denoted.
If output is magnitude/phase, the magnitude replaces the real part, and the phase replaces the imaginary part.
Strain item codes are equivalent to stress item codes. However, strain is computed for only some elements.
See Table 3-1 in the MSC Nastran Reference Guide.
Main Index
CHAPTER 7 955
Element Stress (or Strain) Item Codes
Table 7-1 Element Stress-Strain Item Codes
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CAXIF2 (47) 21 Radial axis 21 Radial axis RM
31 Axial axis 31 Axial axis RM
41 Tangential edge 41 Tangential edge RM
1 1
5 Circumferential edge 5 Circumferential edge RM
1
6 Radial axis IP
1
7 Axial axis IP
81 Tangential edge IP
1
9 Circumferential edge IP
CAXlF3 (48) 21 Radial centroid 21 Radial centroid RM
1 1
3 Circumferential centroid 3 Circumferential centroid RM
41 Axial centroid 41 Axial centroid RM
1 1
5 Tangential edge 1 5 Tangential edge 1 RM
1 1
6 Circumferential edge 1 6 Circumferential edge 1 RM
1 1
7 Tangential edge 2 7 Tangential edge 2 RM
81 Circumferential edge 2 81 Circumferential edge 2 RM
1 1
9 Tangential edge 3 9 Tangential edge 3 RM
1 1
10 Circumferential edge 3 10 Circumferential edge 3 RM
1
11 Radial centroid IP
121 Circumferential centroid IP
1
13 Axial centroid IP
1
14 Tangential edge 1 IP
1
15 Circumferential edge 1 IP
161 Tangential edge 2 IP
1
17 Circumferential edge 2 IP
181 Tangential edge 3 IP
191 Circumferential edge 3 IP
CAXIF4 (49) 21 Radial centroid 21 Radial centroid RM
31 Circumferential centroid 31 Circumferential centroid RM
1 1
4 Axial centroid 4 Axial centroid RM
1 1
5 Tangential edge 1 5 Tangential edge 1 RM
61 Circumferential edge 1 61 Circumferential edge 1 RM
Main Index
956 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-1 Element Stress-Strain Item Codes (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
71 Tangential edge 2 71 Tangential edge 2 RM
81 Circumferential edge 2 81 Circumferential edge 2 RM
1 1
9 Tangential edge 3 9 Tangential edge 3 RM
1 1
10 Circumferential edge 3 10 Circumferential edge 3 RM
1 1
11 Tangential edge 4 11 Tangential edge 4 RM
121 Circumferential edge 4 121 Circumferential edge 4 RM
13 Radial centroid IP
14 Circumferential centroid IP
15 Axialcentroid IP
16 Tangential edge 1 IP
17 Circumferential edge 1 IP
18 Tangential edge 2 IP
19 Circumferential edge 2 IP
20 Tangential edge 3 IP
21 Circumferential edge 3 IP
22 Tangential edge 4 IP
23 Circumferential edge 4 IP
CAXISYM (241) 2 Z1-Fiber distance 1
Nonlinear 3 Stress-X
4 Stress-Y
5 Stress-XY
6 Strain-X
7 Strain-Y
8 Strain XY
9-15 Item 9 through 15 repeated
for fiber distance Z2
CBAR (34) 21 End A-Point C 21 End A-Point C RM
Linear 31 End A-Point D 31 End A-Point D RM
41 End A-Point E 41 End A-Point E RM
1 1
5 End A-Point F 5 End A-Point F RM
61 Axial 61 Axial RM
1
7 End A maximum 7 End A-Point C IP
1
8 End A minimum 8 End A-Point D IP
Main Index
CHAPTER 7 957
Element Stress (or Strain) Item Codes
Table 7-1 Element Stress-Strain Item Codes (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
9 Safety margin in tension 91 End A-Point E IP
101 End B-Point C 101 End A-Point F IP
1 1
11 End B-Point D 11 Axial IP
1 1
12 End B-Point E 12 End B-Point C RM
1 1
13 End B-Point F 13 End B-Point D RM
14 End B maximum 141 End B-Point E RM
1
15 End B minimum 15 End B-Point F RM
1
16 Safety margin in compression 16 End B-Point C IP
1
17 End B-Point D IP
181 End B-Point E IP
1
19 End B-Point F IP
CBAR (100) 2 Station Distance/Length 2 Station Distance/Length RM
Intermediate 3 Point C 3 Point C RM
Stations
4 Point D 4 Point D RM
5 Point E 5 Point E RM
6 Point F 6 Point F RM
7 Axial 7 Axial RM
8 Maximum 8 Maximum RM
9 Minimum 9 Minimum RM
10 Margin of Safety 10 Point C IP
(Item codes above are given for End A. 11 Point D IP
For codes 2 through 10 at intermediate
stations add (K-1)*9 where K is the 12 Point E IP
station number, and for codes at End B,
K=number of stations plus 1.) 13 Point F IP
14 Axial IP
15 Maximum IP
16 Minimum
(Item codes above are given for End
A. For codes 2 through 16 at
intermediate stations add (K-1)*15
where K is the station number, and
for codes at End B, K=number of
stations plus 1.)
Main Index
958 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-1 Element Stress-Strain Item Codes (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CBAR (238) 2 Station Distance/Length
Arbitrary Cross 3 Max Axial Stress
Section 4 Min Axial Stress
5 Max Shear Stress in xy
6 Min Shear Stress in xy
7 Max Shear Stress in zx
8 Min Shear Stress in zx
9 Max vonMises Stress (Not Supported)
CBEAM (2) 2 External grid point ID 2 External grid point ID
Linear 3 Station distance/length 3 Station distance/length
1 1
4 Long. Stress at Point C 4 Long. Stress at Point C RM
1 1
5 Long. Stress at Point D 5 Long. Stress at Point D RM
1 1
6 Long. Stress at Point E 6 Long. Stress at Point E RM
71 Long. Stress at Point F 71 Long. Stress at Point F RM
1
8 Maximum stress 8 Long. Stress at Point C IP
1
9 Minimum stress 9 Long. Stress at Point D IP
10 Safety margin in tension 101 Long. Stress at Point E IP
11 Safety margin in compression 111 Long. Stress at Point F IP
(Item codes are given for end A. (Item codes are given for end A.
Addition of the quantity (K-1)10 to the Addition of the quantity (K-1)10
item code points to the same to the item code points to the same
information for other stations, where K information for other stations,
is the station number. K=11 for end B where K is the station number.
and 2 through10 for intermediate K=11 for end B and 2 through 10
stations.) for intermediate stations.)
CBEAM (94) 2 External grid point ID Not applicable
Nonlinear 3 C (Character)
4 Long. Stress at point C
5 Equivalent stress
6 Total strain
7 Effective plastic strain
8 Effective creep strain
(Item codes 3 through 8 are repeated
for points D, E, and F. Then the entire
record (from 2 through N) is repeated
for end B of the element.)
Main Index
CHAPTER 7 959
Element Stress (or Strain) Item Codes
Table 7-1 Element Stress-Strain Item Codes (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CBEAM (239) 2 Station Distance/Length
Arbitrary Cross Section 3 Max Axial Stress
4 Min Axial Stress
5 Max Shear Stress in xy
6 Min Shear Stress in xy
7 Max Shear Stress in xz
8 Min Shear Stress in xz
9 Max von Mises Stress (Not supported)
CBEAM3 (184) 2 External grid point ID 2 External grid point ID
Linear 3 Normal stress at point C 3 Normal stress at point C RM
4 Normal stress at point D 4 Normal stress at point D RM
5 Normal stress at point E 5 Normal stress at point E RM
6 Normal stress at point F 6 Normal stress at point F RM
7 Maximum stress 7 Normal stress at point C IP
8 Minimum stress 8 Normal stress at point D IP
9 Safety margin in tension 9 Normal stress at point E IP
10 Safety margin in compression 10 Normal stress at point F IP
11 Shear stress in y-direction at 11 Shear stress in y-direction RM
point C at point C
12 Shear stress in y-direction at 12 Shear stress in y-direction RM
point D at point D
13 Shear stress in y-direction at 13 Shear stress in y-direction RM
point E at point E
14 Shear stress in y-direction at 14 Shear stress in y-direction RM
point F at point F
15 Maximum shear stress in y- 15 Shear stress in y-direction IP
direction at point C
16 Minimum shear stress in y- 16 Shear stress in y-direction IP
direction at point D
17 (Not applicable) 17 Shear stress in y-direction IP
at point E
18 (Not applicable) 18 Shear stress in y-direction IP
at point F
19 Shear stress in z-direction at 19 Shear stress in z-direction RM
point C at point C
Main Index
960 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-1 Element Stress-Strain Item Codes (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
20 Shear stress in z-direction at 20 Shear stress in z-direction RM
point D at point D
21 Shear stress in z-direction at 21 Shear stress in z-direction RM
point E at point E
22 Shear stress in z-direction at 22 Shear stress in z-direction RM
point F at point F
23 Maximum shear stress in z- 23 Shear stress in z-direction IP
direction at point C
24 Minimum shear stress in z- 24 Shear stress in z-direction IP
direction at point D
25 (Not applicable) 25 Shear stress in z-direction IP
at point Z
26 (Not applicable) 26 Shear stress in z-direction IP
at point F
(Item codes are given for end A. they
are repeated for end B and mid-node C, (Item codes are given for end A.
respectively) They are repeated for end B and
mid-node C, respectively)
CBEND (69) 2 External grid point ID 2 External grid point ID
3 Circumferential angle 3 Circumferential angle
41 Long. Stress at Point C 41 Long. Stress at Point C RM
1 1
5 Long. Stress at Point D 5 Long. Stress at Point D RM
61 Long. Stress at Point E 61 Long. Stress at Point E RM
1 1
7 Long. Stress at Point F 7 Long. Stress at Point F RM
1
8 Maximum stress 8 Long. Stress at Point C IP
9 Minimum stress 91 Long. Stress at Point D IP
10 Safety margin in tension 101 Long. Stress at Point E IP
1
11 Safety margin in compression 11 Long. Stress at Point F IP
(Item codes are given for end A. Item (Item codes are given for end A.
codes 12 through 21 point to the same Item codes 12 through 21 point to
information for end B.) the same information for end B.)
CBUSH (102) 21 Translation-x 21 Translation-x R
1 1
3 Translation-y 3 Translation-y R
1 1
4 Translation-z 4 Translation-z R
1 1
5 Rotation-x 5 Rotation-x R
61 Rotation-y 61 Rotation-y R
71 Rotation-z 71 Rotation-z R
81 Translation-x I
Main Index
CHAPTER 7 961
Element Stress (or Strain) Item Codes
Table 7-1 Element Stress-Strain Item Codes (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
91 Translation-y I
101 Translation-z I
1
11 Rotation-x I
1
12 Rotation-y I
1
13 Rotation-z I
CBUSH1D (40) 1 Element ID
2 Axial force
3 Axial displacement
4 Axial velocity Not applicable
5 Axial stress
6 Axial strain
7
8
Table 7-2 Element Stress-Strain Item Codes Part 2
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CCONEAX (35) 2 Harmonic or point angle Not applicable
3 Z1=Fiber Distance 1
41 Normal v at Z1
1
5 Normal u at Z1
1
6 Shear uv at Z1
7 Shear angle at Z1
8 Major principal at Z1
9 Minor principal at Z1
10 Maximum shear at Z1
11 Z2= Fiber Distance 2
121 Normal v at Z2
1
13 Normal u at Z2
1
14 Shear uv at Z2
15 Shear angle at Z2
Main Index
962 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
16 Major principal at Z2
17 Minor principal at Z2
18 Maximum shear at Z2
1
CDUM3 2 S1 21 S1 RM
1 1
thru 3 S2 3 S2 RM
CDUM9 (55-61) 41 S3 41 S3 RM
1 1
5 S4 5 S4 RM
1 1
6 S5 6 S5 RM
1 1
7 S6 7 S6 RM
81 S7 81 S7 RM
1 1
CELAS1 (11) 2 Stress 2 Stress RM
1
3 Stress IP
1 1
CELAS2 (12) 2 Stress 2 Stress RM
31 Stress IP
1 1
CELAS3 (13) 2 Stress 2 Stress RM
1
3 Stress IP
CGAP (86) 2 Normal x Not applicable
3 Shear y
4 Shear z
5 Axial u
6 Shear v
7 Shear w
8 Slip v
9 Slip w
CHEXA (67) 2 Stress coordinate system 2 Stress coordinate system
Linear 3 Coordinate type (Character) 3 Coordinate type (Character)
4 Number of active points 4 Number of active points
5 External grid ID (0=center) 5 External grid ID (0=center)
61 Normal x 61 Normal x RM
71 Shear xy 71 Normal y RM
1
8 First principal 8 Normal z RM
1
9 First principal x cosine 9 Shear xy RM
Main Index
CHAPTER 7 963
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
10 Second principal x cosine 101 Shear yz RM
11 Third principal x cosine 111 Shear zx RM
1
12 Mean pressure 12 Normal x IP
1
13 von Mises or octahedral shear 13 Normal y IP
stress
141 Normal y 141 Normal z IP
1 1
15 Shear yz 15 Shear xy IP
16 Second principal 161 Shear yz IP
1
17 First principal y cosine 17 Shear zx IP
18 Second principal y cosine 18- Items 5 through 17 repeated
121 for 8 corners
19 Third principal y cosine
1
20 Normal z
211 Shear zx
22 Third principal
23 First principal z cosine
24 Second principal z cosine
25 Third principal z cosine
26-193 Items 5 through 25 repeated
for 8 corners
CHEXA (93) 2 Stress coordinate system
Nonlinear 3 Grid/Gauss
4 Number of active points
5 External grid ID
(0=center)
6 Stress-X
7 Stress-Y
8 Stress-Z
9 Stress-XY
10 Stress-YZ
11 Stress-ZX
12 Equivalent stress
13 Effective plastic strain Not applicable
14 Effective creep strain
Main Index
964 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
15 Strain-X
16 Strain-Y
17 Strain-Z
18 Strain-XY
19 Strain-YZ
20 Strain-ZX
21-148 Items 5 through 20
Repeated for 8 corners
CHEXAFD (202) 2 Grid/Gauss
Nonlinear Finite 3 Grid/Gauss ID (0=center)
Deformation with 8
grid points 4 Cauchy stress-X
5 Cauchy stress-Y
6 Cauchy stress-Z
7 Cauchy stress-XY
8 Cauchy stress-YZ
9 Cauchy stress-ZX
10 Pressure1 Not applicable
p = --- x + y + z
3
11 Volumetric strain J-1
12 Logarithmic strain-X
13 Logarithmic strain-Y
14 Logarithmic strain-Z
15 Logarithmic strain-XY
16 Logarithmic strain-YZ
17 Logarithmic strain-ZX
18-122 Items 3 through 17 repeated
for 7 Gauss/grid points
CHEXAFD (207) 2-17 Same as CHEXAFD (202)
Nonlinear Finite 18-407 Items 3 through 17 repeated Not applicable
Deformation with for 26 Gauss points
20 grid points
CIFHEX (65) 2 Grid/Gauss
Nonlinear 3 External Grid ID (0 =
Center)
4 Normal Stress
Main Index
CHAPTER 7 965
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
5 Shear Stress 1
6 Shear Stress 2
7 Normal Strain
8 Shear Strain 1
9 Shear Strain 2
10 Damage Value
11-74 Items 3 through 10 repeated
for 6 Corners
CIFPENT (66) 2 Grid/Gauss
Nonlinear 3 External Grid ID (0 =
Center)
4 Normal Stress
5 Shear Stress 1
6 Shear Stress 2
7 Normal Strain
8 Shear Strain 1
9 Shear Strain 2
10 Damage Value
11-58 Items 3 through 10 repeated
for 6 Corners
CIFQDX (73) 2 Grid/Gauss
Nonlinear 3 External Grid ID (0 =
Center)
4 Normal Stress
5 Shear Stress
6 Normal Strain
7 Shear Strain
8 Damage Value
9-32 Items 3 through 8 repeated
for 4 Corners
CIFQUAD (63) 2 Grid/Gauss
Nonlinear 3 External Grid ID (0 =
Center)
4 Normal Stress
5 Shear Stress
Main Index
966 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
6 Normal Strain
7 Shear Strain
8 Damage Value
9-32 Items 3 through 8 repeated
for 4 Corners
CONROD (10) 21 Axial stress 21 Axial stress RM
1
Linear 3 Axial safety margin 3 Axial stress IP
41 Torsional stress 41 Torsional stress RM
5 Torsional safety margin 51 Torsional stress IP
CONROD (92) 2 Axial stress
Nonlinear 3 Equivalent stress
4 Total strain
5 Effective plastic strain Not applicable
6 Effective creep strain
7 Linear torsional stress
CPENTA (68) 2 Stress coordinate system 2 Stress coordinate system
Linear 3 Coordinate type (Character) 3 Coordinate type (Character)
4 Number of active points 4 Number of active points
5 External grid ID 5 External grid ID
(0=center) (0=center)
1 1
6 Normal x 6 Normal x RM
1 1
7 Shear xy 7 Normal y RM
1
8 First principal 8 Normal z RM
9 First principal x cosine 91 Shear xy RM
1
10 Second principal x cosine 10 Shear yz RM
1
11 Third principal x cosine 11 Shear zx RM
12 Mean pressure 121 Normal x IP
13 von Mises or Octahedral 131 Normal y IP
shear stress
141 Normal y 141 Normal z IP
1 1
15 Shear yz 15 Shear xy IP
1
16 Second principal 16 Shear yz IP
1
17 First principal y cosine 17 Shear zx IP
Main Index
CHAPTER 7 967
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
18 Second principal y cosine 18-95 Items 5 through 17 repeated
for 6 corners
19 Third principal y cosine
201 Normal z
1
21 Shear zx
22 Third principal
23 First principal z cosine
24 Second principal z cosine
25 Third principal z cosine
26-151 Items 5 through 25 repeated
for 6 corners
CPENTA (91) 2 Stress coordinate system
Nonlinear 3 Grid/Gauss
4 Number of active points
5 External grid ID
(0=center)
6 Normal x stress
7 Normal y stress
8 Normal z stress
9 Shear xy stress
10 Shear yz stress
11 Shear zx stress
12 Equivalent stress Not applicable
13 Effective plastic strain
14 Effective creep strain
15 Normal x strain
16 Normal y strain
17 Normal z strain
18 Shear xy strain
19 Shear yz strain
20 Shear zx strain
21-116 Items 5 through 20
Repeated for 6 corners
Main Index
968 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CPENTAFD (204) 2-17 Same as CHEXAFD (201)
Nonlinear Finite 18-92 Items 3 through 17 repeated Not applicable
Deformation with 6 for 5 Gauss points
grid points
CPENTAFD (209) 2-17 Same as CHEXAFD (201)
Nonlinear Finite 18-317 Items 3 through 17 repeated Not applicable
Deformation with for 20 Gauss points
15 grid points
Main Index
CHAPTER 7 969
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CPYRAM (242) 2 Stress coordinate system 2 Stress coordinate system
Linear 3 Coordinate Type (Character) 3 Coordinate Type (Character)
4 Number of active points 4 Number of active points
5 External grid ID (0=centre) 5 External grid ID (0=centre)
6 Normal x 6 Normal x RM
7 Shear xy 7 Normal y RM
8 First principal 8 Normal z RM
9 First principal x cosine 9 Shear xy RM
10 Second principal x cosine 10 Shear yz RM
11 Third principal x cosine 11 Shear zx RM
12 Mean pressure 12 Normal x IP
13 von Mises or octahedral shear 13 Normal y IP
stress
14 Normal y 14 Normal z IP
15 Shear yz 15 Shear xy IP
16 Second principal 16 Shear yz IP
17 First principal y cosine 17 Shear zx IP
18 Second principal y cosine 18-82 Items 5 through 17 repeated
for 5 corners
19 Third principal y cosine
20 Normal z
21 Shear zx
22 Third Principal
23 First principal z cosine
24 Second principal z cosine
25 Third principal z cosine
26-130 Items 5 through 25 repeated
for 5 corners
Main Index
970 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-2 Element Stress-Strain Item Codes Part 2 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CPYRAM (242) 2 Stress coordinate system Not Applicable
Non Linear 3 Grid/Gauss
4 Number of active points
5 External grid ID (0=centre)
6 Stress X
7 Stress Y
8 Stress Z
9 Stress XY
10 Stress YZ
11 Stress ZX
12 Equivalent Stress
13 Effective plastic strain
14 Effective creep strain
15 Strain X
16 Strain Y
17 Strain Z
18 Strain XY
19 Strain YZ
20 Strain ZX
21-100 Items 5 through 20 repeated
for 5 corners
Table 7-3 Element Stress-Strain Item Codes Part 3
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CQUAD4 (33) 2 Z1=Fiber distance 1 2 Z1=Fiber distance 1
1 1
Linear 3 Normal x at Z1 3 Normal x at Z1 RM
1 1
4 Normal y at Z1 4 Normal x at Z1 IP
1 1
5 Shear xy at Z1 5 Normal y at Z1 RM
6 Shear angle at Z1 61 Normal y at Z1 IP
Main Index
CHAPTER 7 971
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
7 Major principal at Z1 71 Shear xy at Z1 RM
8 Minor principal at Z1 81 Shear xy at Z1 IP
9 von Mises or 9 Z2=Fiber distance 2
maximum shear at Z1
10 Z2=Fiber distance 2 101 Normal x at Z2 RM
1 1
11 NormaI x at Z2 11 NormaI x at Z2 IP
1 1
12 Normal y at Z2 12 Normal y at Z2 RM
131 Shear xy at Z2 131 Normal y at Z2 IP
14 Shear angle at Z2 14 Shear xy at Z2 RM
15 Major principal at Z2 15 Shear xy at Z2 IP
16 Minor principal at Z2
17 von Mises or
maximum shear at Z2
CQUAD4 (90) 2 Z1=Fiber distance 1 (plane
stress only)
Nonlinear
3 Stress-X (at Z1, if plane stress)
4 Stress-Y (at Z1, if plane stress)
5 Stress-Z (plane strain only)
6 Stress-XY (at Z1, if plane stress)
7 Equivalent stress (at Z1, if
plane stress)
8 Plastic strain (at Z1, if plane
stress)
9 Creep strain (at Z1, if plane Not applicable
stress)
10 Strain-X (at Z1, if plane stress)
11 Strain-Y (at Z1, if plane stress)
12 Strain-Z (plane strain only)
13 Strain-XY (at Z1, if plane
stress)
14-25 Items 2 through 13 repeated for
fiber distance Z2 (plane stress
only)
CQUAD42 (95) 2 Lamina Number 2 Lamina Number
Composite 3 Normal-1 3 Normal-1 RM
4 Normal-2 4 Normal-2 RM
Main Index
972 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
5 Shear-12 5 Shear-12 RM
6 Shear-1Z 6 Shear-1Z RM
7 Shear-2Z 7 Shear-2Z RM
8 Shear angle 8 Normal-1 IP
9 Major principal 9 Normal-2 IP
10 Minor principal 10 Shear-12 IP
11 Maximum shear 11 Shear-1Z IP
12 12 Shear-2Z IP
CQUAD4 (144) 1 EID 1 EID
CORNER 2 CEN/ 2 CEN/
Output
3 4 3 4
4 Z1-Fiber distance 4 Z1-Fiber distance
5 Normal x at Z1 5 Normal x at Z1 RM
6 Normal y at Z1 6 Normal x at Z1 IP
7 Shear xy at Z1 7 Normal y at Z1 RM
8 Shear angle at Z1 8 Normal y at Z1 IP
9 Major principal at Z1 9 Shear xy at Z1 RM
10 Minor principal at Z1 10 Shear xy at Z1 IP
11 von Mises or maximum shear at 11 Z2-Fiber distance
Z1
12 Z2-Fiber distance 12 Normal x at Z2 RM
13 Normal x at Z2 13 Normal x at Z2 IP
14 Normal y at Z2 14 Normal y at Z2 RM
15 Shear xy at Z2 15 Normal y at Z2 IP
16 Shear angle at Z2 16 Shear xy at Z2 RM
17 Major principal at Z2 17 Shear xy at Z2 IP
18 Minor principal at Z2 18 Grid 1
19 von Mises or maximum shear at 19-32 Same as 4 through 17 for
Z2 corner 1
20 Grid 1 33 Grid 2
21-36 Same as 4 through19 for corner 34-47 Same as 4 through 17 for
1 corner 2
37 Grid 2 48 Grid 3
Main Index
CHAPTER 7 973
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
38-53 Same as 4 through19 for corner 49-62 Same as 4 through 17 for
2 corner 3
54 Grid 3 63 Grid 4
55-70 Same as 4 through 19 for corner 64-77 Same as 4 through 17 for
3 corner 4
71 Grid 4
72-87 Same as 4 through 19 for corner
4
CQUAD8 (64) 51 Normal x at Z1 51 Normal x at Z1 RM
1 1
6 Normal y at Z1 6 Normal x at Z1 IP
1 1
7 Shear xy at Z1 7 Normal y at Z1 RM
8 O Shear angle at Z1 81 Normal y at Z1 IP
1
9 Major principal at Z1 9 Shear xy at Z1 RM
1
10 Minor principal at Z1 10 Shear xy at Z1 IP
1
11 von Mises or 12 Normal x at Z2 RM
maximum shear at Z1
131 NormaI x at Z2 131 NormaI x at Z2 IP
141 Normal y at Z2 141 Normal y at Z2 RM
151 Shear xy at Z2 151 Normal y at Z2 IP
1
16 Q Shear angle at Z2 16 Shear xy at Z2 RM
1
17 Major principal at Z2 17 Shear xy at Z2 IP
18 Minor principal at Z2 20-32 Same as items 5 through 17
for corner 1
19 von Mises or 35-47 Same as items 5 through 17
maximum shear at Z2 for corner 2
22-36 Same as items 5 through 19 for 50-62 Same as items 5 through 17
corner 1 for corner 3
39-53 Same as items 5 through 19 for 65-77 Same as items 5 through 17
corner 2 for corner 4
56-70 Same as items 5 through 19 for
corner 3
73-87 Same as items 5 through 19 for
corner 4
CQUAD82 (96) Same as CQUAD4(95) Same as CQUAD4(95)
Composite
Main Index
974 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CQUADFD (201) 2 Grid/Gauss
Nonlinear Finite 3 Grid/Gauss ID (0=center)
Deformation with
4 grid points 4 Cauchy stress-X
5 Cauchy stress-Y
6 Cauchy stress-Z
7 Cauchy stress-XY
8 Pressure1 Not applicable
p = --- x + y + z
3
9 Volumetric strain J-1
10 Logarithmic strain-X
11 Logarithmic strain-Y
13 Logarithmic strain-XY
14-46 Items 3 through 13 repeated for
3 Gauss points
CQUADFD (208) 2-13 Same as CQUADFD (201)
Nonlinear Finite 14-101 Items 3 through 13 repeated for Not applicable
Deformation with 8 Gauss points
8 or 9 grid points
CQUADR (82) Same as CQUAD4(144) Same as CQUAD4(144)
Linear CORNER output
CQUADR (172) Same as CQUAD4(90) Not applicable
Nonlinear
CQUADR (232) Same as CQUAD4(95) Same as CQUAD4(95)
Composite
Main Index
CHAPTER 7 975
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CQUADX(18) 1 (Elem ID) 1 (Elem ID)
Harmonic 2 Harmonic 2 Harmonic
3 CEN/grid 3 CEN/grid
4 Stress_xx 4 Stress_xx RM
5 Stress_yy 5 Stress_yy RM
6 Stress_tt 6 Stress_tt RM
7 Stress_xy 7 Stress_xy RM
8 Stress_yt 8 Stress_yt RM
9 Stress_tx 9 Stress_tx RM
10 VON MISES* 10 Stress_xx IP
11-18 1st corner 11 Stress_yy IP
19-26 2nd corner 12 Stress_tt IP
27-34 3rd corner 13 Stress_xy IP
35-42 4th corner 14 Stress_yt IP
15 Stress_tx IP
16-28 1st corner
29-41 2nd corner
42-54 3rd corner
55-67 4th corner
CQUADXFD (214) 2 Grid/Gauss
Nonlinear Finite 3 Gauss ID
Deformation with
4 grid points 4 Cauchy stress-X (radial)
5 Cauchy stress-Y (axial)
6 Cauchy stress-Z
(circumferential)
7 Cauchy stress-XY
8 Pressure1 Not applicable
p = --- x + y + z
3
9 Volumetric strain
J-1
10 Logarithmic strain-X (radial)
11 Logarithmic strain-Y (axial)
12 Logarithmic strain-Z
(circumferential)
Main Index
976 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
13 Logarithmic strain-XY
14-46 Items 3 through 13 repeated for
remaining 3 Gauss points
CQUADXFD (215) 2-13 Same as QUADXFD (214) Not applicable
Nonlinear Finite 14-101 Items 3 through 13 repeated for
Deformation with remaining 8 Gauss points
8 or 9 grid points
CROD (1) Same as CONROD(10) Same as CONROD(10)
Linear
CROD (89) Same as CONROD(92) Not applicable
Nonlinear
CSHEAR (4) 2 Maximum shear 2 Maximum shear RM
1
3 Average shear 3 Maximum shear IP
1
4 Safety margin 4 Average shear RM
1
5 Average shear IP
CSLOT3 (50) 2 Radial centroid 2 Radial centroid RM
3 Axial centroid 3 Axial centroid RM
4 Tangential edge 1 4 Tangential edge 1 RM
5 Tangential edge 2 5 Tangential edge 2 RM
6 Tangential edge 3 6 Tangential edge 3 RM
7 Radial centroid IP
8 Axialcentroid IP
9 Tangential edge 1 IP
10 Tangential edge 2 IP
11 Tangential edge 3 IP
CSLOT4 (51) 2 Radial centroid 2 Radial centroid RM
3 Axial centroid 3 Axial centroid RM
4 Tangential edge 1 4 Tangential edge 1 RM
5 Tangential edge 2 5 Tangential edge 2 RM
6 Tangential edge 3 6 Tangential edge 3 RM
7 Tangential edge 4 7 Tangential edge 4 RM
8 Radial centroid IP
9 Axial centroid IP
10 Tangential edge 1 IP
Main Index
CHAPTER 7 977
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
11 Tangential edge 2 IP
12 Tangential edge 3 IP
13 Tangential edge 4 IP
CTETRA (39) 2 Stress coordinate system 2 Stress coordinate system
Linear 3 Coordinate type (Character) 3 Coordinate type (Character)
4 Number of active points 4 Number of active points
5 External grid ID 5 External grid ID
(0=center) (0=center)
1 1
6 Normal x 6 Normal x RM
71 Shear xy 71 Normal y RM
1
8 First principal 8 Normal z RM
1
9 First principal x cosine 9 Shear xy RM
1
10 Second principal x cosine 10 Shear yz RM
11 Third principal x cosine 111 Shear zx RM
1
12 Mean pressure 12 Normal x IP
1
13 von Mises or octahedral shear 13 Normal y IP
stress
141 Normal y 141 Normal z IP
151 Shear yz 151 Shear xy IP
16 Second principal 161 Shear yz IP
1
17 First principal y cosine 17 Shear zx IP
18 Second principal y cosine 18-69 Items 5 through 17 repeated
for four corners
19 Third principal y cosine
201 Normal z
211 Shear zx
22 Third principal
23 First principal z cosine
24 Second principal z cosine
25 Third principal z cosine
26-109 Items 5 through 25 repeated
for four corners
Main Index
978 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-3 Element Stress-Strain Item Codes Part 3 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CTETRA (85) 2 Stress coordinate system
Nonlinear 3 Grid/Gauss
4 Number of active points
5 External grid ID
(0=center)
6 Stress-X
7 Stress-Y
8 Stress-Z
9 Stress-XY
10 Stress-YZ
11 Stress-ZX
12 Equivalent stress
13 Effective plastic strain Not applicable
14 Effective creep strain
15 Strain-X
16 Strain-Y
17 Strain-Z
18 Strain-XY
19 Strain-YZ
20 Strain-ZX
21-84 Items 5 through 20
Repeated for four corners
CTETRAFD (205) 2-17 Same as CHEXAFD (202) Not applicable
Nonlinear Finite
Deformation with
4 grid points
CTETRAFD (210) 2-17 Same as CHEXAFD (202)
Nonlinear Finite 18-77 Items 3 through 17 repeated for Not applicable
Deformation witn 4 Gauss points
10 grid points
Main Index
CHAPTER 7 979
Element Stress (or Strain) Item Codes
Table 7-4 Element Stress-Strain Item Codes Part 4
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CTRIA3 (74) Same as CQUAD4(33) Same as CQUAD4(33)
CTRIA32 (97) Same as CQUAD4(95) Same as CQUAD4(95)
Composite
CTRIA3 (88) Same as CQUAD4(90) Not applicable
Nonlinear
CTRIA6 (75) 51 Normal x at Z1 51 Normal x at Z1 RM
Linear 61 Normal y at Z1 61 Normal x at Z1 IP
1 1
7 Shear xy at Z1 7 Normal y at Z1 RM
1
8 Q shear angle at Z1 8 Normal y at Z1 IP
1
9 Major principal at Z1 9 Shear xy at Z1 RM
10 Minor principal at Z1 101 Shear xy at Z1 IP
1
11 von Mises or 12 Normal x at Z2 RM
maximum shear at Z1
131 NormaI x at Z2 131 Normal x at Z2 IP
1 1
14 Normal y at Z2 14 Normal y at Z2 RM
151 Shear xy at Z2 151 Normal y at Z2 IP
1
16 Q shear angle at Z2 16 Shear xy at Z2 RM
17 Major principal at Z2 171 Shear xy at Z2 IP
18 Minor principal at Z2 20-32 Same as items 5 through 17
for corner 1
19 von Mises or 35-47 Same as items 5 through 17
maximum shear at Z2 for corner 2
22-36 Same as items 5 through 19 50-62 Same as items 5 through 17
for corner 1 for corner 3
39-53 Same as items 5 through 19
for corner 2
56-70 Same as items 5 through 19
for corner 3
CTRIA62 (98) Same as CQUAD4(95) Same as CQUAD4(95)
CTRIAFD (206) 2-13 Same as CQUADFD(201) Not applicable
Nonlinear
Deformation with 3
grid points
Main Index
980 MSC Nastran Quick Reference Guide
Element Stress (or Strain) Item Codes
Table 7-4 Element Stress-Strain Item Codes Part 4 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CTRIAFD (211) 2-13 Same as CQUADFD (201)
Nonlinear Finite 14-35 Items 3 through 12 repeated Not applicable
Deformation with 6 for 2 Gauss points
grid points
CTRlAR (70) Same as CTRlA6(75) Same as CTRlA6(75)
Linear
CTRIAR (173) Same as CQUAD4(90) Not applicable
Nonlinear
CTRIAR (233) Same as CQUAD4(95) Same as CQUAD4(95)
Composite
CTRIAX(17) 1 (Elem ID) 1 (Elem ID)
Harmonic 2 Harmonic 2 Harmonic
3 CEN/grid 3 CEN/grid
4 Stress_xx 4 Stress_xx RM
5 Stress_yy 5 Stress_yy RM
6 Stress_tt 6 Stress_tt RM
7 Stress_xy 7 Stress_xy RM
8 Stress_yt 8 Stress_yt RM
9 Stress_tx 9 Stress_tx RM
10 VON MISES* 10 Stress_xx IP
11-18 1st corner 11 Stress_yy IP
19-26 2nd corner 12 Stress_tt IP
27-34 3rd corner 13 Stress_xy IP
14 Stress_yt IP
15 Stress_tx IP
16-28 1st corner
29-41 2nd corner
42-54 3rd corner
CTRIAX6 (53) 31 Radial 31 Radial RM
1 1
4 Azimuthal 4 Radial IP
1 1
5 Axial 5 Azimuthal RM
61 Shear stress 61 Azimuthal IP
Main Index
CHAPTER 7 981
Element Stress (or Strain) Item Codes
Table 7-4 Element Stress-Strain Item Codes Part 4 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
7 Maximum principal 7 Axial RM
8 Maximum shear 8 Axial IP
9 von Mises or octahedral 9 Shear RM
10 Shear IP
11-17 Same as items 3 through 9 12-19 Same as items 3 through 10
for corner 1 for corner 1
19-25 Same as Items 3 through 9 21-28 Same as items 3 through 10
for corner 2 for corner 2
27-33 Same as items 3 through 9 30-37 Same as items 3 through 10
for corner 3 for corner 3
CTRIAXFD (212) 2-13 Same as CQUADXFD (214) Not applicable
Nonlinear Finite
Deformation with 3
grid points
CTRIAXFD (213) 2-13 Same as CQUADXFD (214)
Nonlinear Finite 14-35 Items 3 through 13 repeated Not applicable
Deformation with for 2 Gauss points
6 grid points
CTUBE (3) Same as CONROD (10) Same as CONROD(10)
Linear
CTUBE (87) Same as CONROD(92) Not applicable
Nonlinear
Main Index
982 MSC Nastran Quick Reference Guide
Element Force Item Codes
Table 7-4 Element Stress-Strain Item Codes Part 4 (continued)
Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
CWELDP 2 Axial 2 Axial RM
(118) 3 Maximum End A 3 Maximum End A RM
if PARTPAT 4 Minimum End A 4 Minimum End A RM
or ELPAT 5 Maximum End B 5 Maximum End B RM
6 Minimum End B 6 Minimum End B RM
CWELDC
7 Maximum Shear 7 Maximum Shear RM
(117)
8 Bearing Stress 8 Bearing Stress RM
if (Not applicable to Strain) (Not applicable to Strain)
MSET=OFF and
9 Axial IP
oldweld=yes
10 Maximum End A IP
CWELD 11 Minimum End A IP
(200) 12 Maximum End B IP
if 13 Minimum End B IP
MSET=ON or 14 Maximum Shear IP
olddweld=no 15 Bearing Stress IP
(Not applicable to Strain)
Element Force Item Codes
All items are element forces (or moments) unless otherwise indicated.
Table 7-5 Element Force Item Codes Part 1
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
CBAR (34) 21 Bending End A plane 1 21 Bending End A plane 1 RM
1 1
Linear 3 Bending End A plane 2 3 Bending End A plane 2 RM
1 1
4 Bending End B plane 1 4 Bending End B plane 1 RM
1 1
5 Bending End B plane 2 5 Bending End B plane 2 RM
61 Shear plane 1 61 Shear plane 1 RM
71 Shear plane 2 71 Shear plane 2 RM
1 1
8 Axial force 8 Axial force RM
91 Torque 91 Torque RM
101 Bending End A plane 1 IP
Main Index
CHAPTER 7 983
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
111 Bending End A plane 2 IP
121 Bending End B plane 1 IP
1
13 Bending End B plane 2 IP
1
14 Shear plane 1 IP
1
15 Shear plane 2 IP
161 Axial force IP
1
17 Torque IP
CBAR (100) 2 Station Distance/Length 2 Station Distance/Length
Intermediate 3 Bending Moment Plane 1 3 Bending Moment Plane 1 RM
Stations 4 Bending Moment Plane 2 4 Bending Moment Plane 2 RM
5 Shear Force Plane 1 5 Shear Force Plane 1 RM
6 Shear Force Plane 2 6 Shear Force Plane 2 RM
7 Axial 7 Axial RM
8 Torque 8 Torque RM
Item codes are given for end A. 9 Bending Moment Plane 1 IP
Addition of the quantity (K-1) * 8
to the item code points to the same 10 Bending Moment Plane 2 IP
information for other stations,
where K is the station number. K=8 11 Shear Force Plane 1 IP
for end B and 2 through 7 for
intermediate stations.
12 Shear Force Plane 2 IP
13 Axial IP
14 Torque IP
(Item codes above are given for
End A. For codes 2 through 14 at
intermediate stations add (K-
1) * 13 where K is the station
number, and for codes at End B,
K+number of stations plus 1.)
CBEAM (2) 2 External grid point ID 2 External grid point ID
Linear 3 Station distance/length 3 Station distance/length
41 Bending moment plane 1 41 Bending moment plane 1 RM
51 Bending moment plane 2 51 Bending moment plane 2 RM
61 Web shear plane 1 61 Web shear plane 1 RM
71 Web shear plane 2 71 Web shear plane 2 RM
1 1
8 Axial force 8 Axial force RM
91 Total torque 91 Total torque RM
Main Index
984 MSC Nastran Quick Reference Guide
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
101 Warping torque 101 Warping torque RM
(Item codes are given for end A. 111 Bending moment plane 1 IP
Addition of the quantity (K-1) 9 to 1
the item code points to the same 12 Bending moment plane 2 IP
information for other stations,
1
where K is the station number. 13 Web shear plane 1 IP
K=11 for end B and 2 through 10
1
for intermediate stations.) 14 Web shear plane 2 IP
151 Axial force IP
1
16 Total torque IP
1
17 Warping torque IP
(Item codes are given for end A.
Addition of the quantity (K-1) 16
to the item code points to the same
information for other stations,
where K is the station number.
K=11 for end B and 2 through 10
for intermediate stations.)
CBEAM3 (184) 2 External grid point ID 2 External grid point ID
Linear 3 Bending moment in y- 3 Bending moment in y- RM
direction direction
4 Bending moment in z- 4 Bending moment in z- RM
direction direction
5 Shear force in y-direction 5 Shear force in y-direction RM
6 Shear force in z-direction 6 Shear force in z-direction RM
7 Axial force 7 Axial force RM
8 Total torque 8 Total torque RM
9 Bi-shear force 9 Bi-shear force RM
10 Bi-moment 10 Bi-moment RM
(Item codes are given for end A.
They are repeated for end B and
mid-node C, respectively)
11 Bending moment in y- IP
direction
12 Bending moment in z- IP
direction
13 Shear force in y-direction IP
14 Shear force in z-direction IP
15 Axial force IP
16 Total torque IP
17 Bi-shear force IP
Main Index
CHAPTER 7 985
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
18 Bi-moment IP
(Item codes are given for end A.
They are repeated for end B and
mid-node C, respectively)
CBEND (69) 2 External grid point ID 2 External grid point ID
1 1
3 Bending moment plane 1 3 Bending moment plane 1 RM
41 Bending moment plane 2 41 Bending moment plane 2 RM
1 1
5 Shear plane 1 5 Shear plane 1 RM
1 1
6 Shear plane 2 6 Shear plane 2 RM
1 1
7 Axial force 7 Axial force RM
81 Torque 81 Torque RM
1
(Item codes are given for end A. 9 Bending moment plane 1 IP
Item codes 9 through 15 point to 1
the same information for end B.) 10 Bending moment plane 2 IP
111 Shear plane 1 IP
121 Shear plane 2 IP
1
13 Axial force IP
1
14 Torque IP
(Item codes are given for end A.
Item codes 15 through 27 point to
the same information for end B.)
CBUSH (102) 21 Force-x 21 Force-x RM
1 1
3 Force-y 3 Force-y RM
1 1
4 Force-z 4 Force-z RM
51 Moment-x 51 Moment-x RM
1 1
6 Moment-y 6 Moment-y RM
1 1
7 Moment-z 7 Moment-z RM
81 Force-x IP
91 Force-y IP
1
10 Force-z IP
1
11 Moment-x IP
1
12 Moment-y IP
131 Moment-z IP
CCONEAX (35) 2 Harmonic or point angle Not applicable
3 Bending moment v
Main Index
986 MSC Nastran Quick Reference Guide
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
4 Bending moment u
5 Twist moment
6 Shear v
7 Shear u
CDAMP1 (20) Same as CELAS1 Same as CELAS1
CDAMP2 (21) Same as CELAS1 Same as CELAS1
CDAMP3 (22) Same as CELAS1 Same as CELAS1
CDAMP4 (23) Same as CELAS1 Same as CELAS1
1 1
CDUM3 thru 2 F1 2 F1 RM
CDUM9 (55 - 61) 31 F2 31 F2 RM
1 1
4 F3 4 F3 RM
1 1
5 F4 5 F4 RM
1 1
6 F5 6 F5 RM
71 F6 71 F6 RM
1 1
8 F7 8 F7 RM
91 F8 91 F8 RM
1 1
10 F9 10 F9 RM
111 F1 IP
1
12 F2 IP
1
13 F3 IP
141 F4 IP
151 F5 IP
1
16 F6 IP
1
17 F7 IP
1
18 F8 IP
191 F9 IP
1 1
CELAS1 (11) 2 Force 2 Force RM
3 Force 3 Force IP
CELAS2 (12) Same as CELAS1 Same as CELAS1
CELAS3 (13) Same as CELAS1 Same as CELAS1
CELAS4 (14) Same as CELAS1 Same as CELAS1
Main Index
CHAPTER 7 987
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
CGAP (38) 2 Normal x Not applicable
3 Shear y
4 Shear z
5 Axial u
6 Shear v
7 Shear w
8 Slip v
9 Slip w
1
CONROD (10) 2 Axial force 21 Axial force RM
1 1
3 Torque 3 Axial force IP
41 Torque RM
51 Torque IP
1 1
CQUAD4 (33) 2 Membrane force x 2 Membrane force x RM
1 1
Linear 3 Membrane force y 3 Membrane force y RM
41 Membrane force xy 41 Membrane force xy RM
1 1
5 Bending moment x 5 Bending moment x RM
1 1
6 Bending moment y 6 Bending moment y RM
1 1
7 Bending moment xy 7 Bending moment xy RM
81 Shear x 81 Shear x RM
1 1
9 Shear y 9 Shear y RM
1
10 Membrane force x IP
1
11 Membrane force y IP
121 Membrane force xy IP
1
13 Bending moment x IP
1
14 Bending moment y IP
1
15 Bending moment xy IP
161 Shear x IP
171 Shear y IP
CQUAD4 (95) 2-3 Theory or blank Not applicable
Composite 4 Lamina number
5 FP (failure index)
/SP (strength ratio)
for direct stresses
Main Index
988 MSC Nastran Quick Reference Guide
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
6 Failure mode for
Maximum strain theory
7 FB (failure index)
/SB (strength ratio) or -1 for
interlaminar shear-stress
8 MAX of FP, FB or -1
or
MIN of SP, SB or -1
9 Failure flag
CQUAD4 (144) 1 EID 1 EID
Corner Output 2 CEN/ 2 CEN/
3 4 3 4
4 Membrane x 4 Membrane x RM
5 Membrane y 5 Membrane y RM
6 Membrane xy 6 Membrane xy RM
7 Bending x 7 Bending x RM
8 Bending y 8 Bending y RM
9 Bending xy 9 Bending xy RM
10 Shear x 10 Shear x RM
11 Shear y 11 Shear y RM
12 Grid 1 12 Membrane x IP
13-20 Same as 4 through 11 for 13 Membrane y IP
corner 1
21 Grid 2 14 Membrane xy IP
22-29 Same as 4 through 11 for 15 Bending x IP
corner 2
30 Grid 3 16 Bending y IP
31-38 Same as 4 through 11 for 17 Bending xy IP
corner 3
39 Grid 4 18 Shear x IP
40-47 Same as 4 through 11 for 19 Shear y IP
corner 4
20 Grid 1
21-36 Same as 4 through 19 for
corner 1
37 Grid 2
Main Index
CHAPTER 7 989
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
38-53 Same as 4 through 19 for
corner 2
54 Grid 3
55-70 Same as 4 through 19 for
corner 3
71 Grid 4
71-87 Same as 4 through 19 for
corner 4
CQUAD8 (64) 1 EID 1 EID
Linear 2 CEN/ 2 CEN/
3 4 3 4
41 Membrane force x 41 Membrane force x RM
1 1
5 Membrane force y 5 Membrane force y RM
1 1
6 Membrane force xy 6 Membrane force xy RM
1 1
7 Bending moment x 7 Bending moment x RM
81 Bending moment y 81 Bending moment y RM
1 1
9 Bending moment xy 9 Bending moment xy RM
1 1
10 Shear x 10 Shear x RM
1 1
11 Shear y 11 Shear y RM
12 Grid1 121 Membrane force x IP
1
13-20 Same as items 4 through 11 13 Membrane force y IP
for corner 1
21 Grid2 141 Membrane force xy IP
1
22-29 Same as items 4 through 11 15 Bending moment x IP
for corner 2
30 Grid3 161 Bending moment y IP
1
31-38 Same as items 4 through 11 17 Bending moment xy IP
for corner 3
39 Grid4 181 Shear x IP
40-47 Same as items 4 through 11 191 Shear y IP
for corner 4
20 Grid1
21-36 Same as items 4 through
19 for corner 1
37 37 Grid2
Main Index
990 MSC Nastran Quick Reference Guide
Element Force Item Codes
Table 7-5 Element Force Item Codes Part 1 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
38-53 Same as items 4 through
19 for corner 2
54 Grid3
55-70 Same as items 4 through
19 for corner 3
71 Grid4
72-87 Same as items 4 through
19 for corner 4
CQUAD82 (96) Same as CQUAD4(95) Same as CQUAD4(95)
Composite
CQUADR (82) Same as CQUAD8(64) Same as CQUAD8(64)
CQUADR (235) Same as CQUAD4(33) Same as CQUAD4(33)
Center
Table 7-6 Element Force Item Codes Part 2
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
CROD (1) Same as CONROD(10) Same as CONROD(10)
1 1
CSHEAR (4) 2 Force 4 to 1 2 Force 4 to 1 RM
1 1
3 Force 2 to 1 3 Force 2 to 1 RM
41 Force 1 to 2 41 Force 1 to 2 RM
51 Force 3 to 2 51 Force 3 to 2 RM
1 1
6 Force 2 to 3 6 Force 2 to 3 RM
1 1
7 Force 4 to 3 7 Force 4 to 3 RM
81 Force 3 to 4 81 Force 3 to 4 RM
91 Force 1 to 4 91 Force 1 to 4 RM
1 1
10 Kick force on 1 10 Force 4 to 1 IP
1 1
11 Shear 12 11 Force 2 to 1 IP
121 Kick force on 2 121 Force 1 to 2 IP
131 Shear 23 131 Force 3 to 2 IP
1 1
14 Kick force on 3 14 Force 2 to 3 IP
Main Index
CHAPTER 7 991
Element Force Item Codes
Table 7-6 Element Force Item Codes Part 2 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
151 Shear 34 151 Force 4 to 3 IP
161 Kick force on 4 161 Force 3 to 4 IP
1 1
17 Shear 41 17 Force 1 to 4 IP
1
18 Kick force on 1 RM
1
19 Shear 12 RM
201 Kick force on 2 RM
1
21 Shear 23 RM
1
22 Kick force on 3 RM
1
23 Shear 34 RM
241 Kick force on 4 RM
1
25 Shear 41 RM
1
26 Kick force on 1 IP
1
27 Shear 12 IP
281 Kick force on 2 IP
1
29 Shear 23 IP
1
30 Kick force on 3 IP
311 Shear 34 IP
321 Kick force on 4 IP
1
33 Shear 41 IP
CTRIA3 (74) Same as CQUAD4(33) Same as CQUAD4(33)
Linear
CTRIA32 (97) Same as CQUAD4(95) Same as CQUAD4(95)
Composite
CTRlA6 (75) 41 Membrane force x 41 Membrane force x RM
Linear 51 Membrane force y 51 Membrane force y RM
1 1
6 Membrane force xy 6 Membrane force xy RM
71 Bending moment x 71 Bending moment x RM
1 1
8 Bending moment y 8 Bending moment y RM
91 Bending moment xy 91 Bending moment xy RM
1 1
10 Shear x 10 Shear x RM
1 1
11 Shear y 11 Shear y RM
13-20 Same as items 4 through 121 Membrane force x IP
11 for corner 1
Main Index
992 MSC Nastran Quick Reference Guide
Element Force Item Codes
Table 7-6 Element Force Item Codes Part 2 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
22-29 Same as items 4 through 131 Membrane force y IP
11 for corner 2
31-38 Same as items 4 through 141 Membrane force xy IP
11 for corner 3
151 Bending moment x IP
161 Bending moment y IP
1
17 Bending moment xy IP
1
18 Shear x IP
1
19 Shear y IP
21-36 Same as items 4 through
19 for corner 1
38-53 Same as items 4 through
19 for corner 2
55-70 Same as items 4 through
19 for corner 3
CTRlA62 (98) Same as CQUAD4(95) Same as CQUAD4(95)
Composite
CTRIAR (70) Same as CTRIA6(75) Same as CTRIA6(75)
CTRIAR (236) Same as CQUAD4(33) Same as CQUAD4(33)
Center
CTUBE (3) Same as CONROD(10) Same as CONROD(10)
CVlSC (24) Not applicable Same as CONROD(10)
CWELDP (118) 2 mz bending end A plane 1 2 mz bending end A plane 1 RM
if PARTPAT or 3 my bending end A plane 2 3 my bending end A plane 2 RM
ELPAT
4 mz bending end B plane 1 4 mz bending end B plane 1 RM
5 my bending end B plane 2 5 my bending end B plane 2 RM
6 fy shear force plane 1 6 fy shear force plane 1 RM
7 fz shear force plane 2 7 fz shear force plane 2 RM
8 fx axial force 8 fx axial force RM
CWELDC (117) 9 mx torque 9 mx torque RM
if MSET = OFF 10 mz bending end A plane 1 IP
11 my bending end A plane 2 IP
Main Index
CHAPTER 7 993
Fluid Virtual Mass Pressure Item Codes
Table 7-6 Element Force Item Codes Part 2 (continued)
Real Element Forces Complex Element Forces
Element Name Item Item Real/Mag. or
Code Code Item Code Item Imag/Phase
CWELD (200) 12 mz bending end B plane 1 IP
if MSET = ON 13 my bending end B plane 2 IP
14 fy shear force plane 1 IP
15 fz shear force plane 2 IP
16 fx axial force IP
17 mx torque IP
Fluid Virtual Mass Pressure Item Codes
Table 7-7 Fluid Virtual Mass Pressure Item Codes
Real Fluid Pressure Complex Fluid Pressure
Element Real/Mag. or
Name Code Item Code Item Imag./Phase
Plate 2 Fluid pressure 2 Pressure RM
Family 3 Pressure IP
Table 7-8 Heat Transfer Item Codes (Curve type is FLUX.)
Element Name (Code) Code Item
Heat Transfer Elements 2 Element type
1
3
41 x gradient
51 y gradient
1
6 z gradient
7 x flux
8 y flux
9 z flux
CHBDYE 4 Applied load
(107) 5 Free convection
6 Forced convection
7 Radiation
Main Index
994 MSC Nastran Quick Reference Guide
2D Slideline and 3D Surface Contact Item Codes
Table 7-8 Heat Transfer Item Codes (Curve type is FLUX.)
Element Name (Code) Code Item
8 Total
CHBDYG Same as Same as CHBDYE
(108) CHBDYE
CHBDYP Same as Same as CHBDYE
(109) CHBDYE
2D Slideline and 3D Surface Contact Item Codes
Table 7-9 Contact Item Codes
Real Element Data
Item
Element Name (Code) Code Slideline Item
CSLIFID (116) 1 SECNDRY grid point
2 Contact region identification number
3 Primary grid 1
4 Primary grid 2
5 Surface coordinate
6 Normal force
7 Shear force
8 Normal stress
9 Shear stress
10 Normal gap
11 Slip
12 Slip ratio (Shear force/u*normal force)
13-14 Slip code (Character)
Main Index
CHAPTER 7 995
2D Slideline and 3D Surface Contact Item Codes
Table 7-10 Contact Item Code for Nodal Data (SOL 400 only)
Real Nodal Data
Element Code Item 3D Surface Item (SOL 400 only)
203 1 Grid point ID
2 First touched body
3 Second touched body
4 Third touched body
5 Contact status (Remark 7)
6 Normal contact force magnitude
7 Friction contact force magnitude
8 Normal stress
9 Friction stress 1
10 Friction stress 2
11 Contact normal force component F nx
12 Contact normal force component F ny
13 Contact normal force component F nz
14 Contact friction force component F fx
15 Contact friction force component F fy
16 Contact friction force component F fz
Table 7-11 Contact Item Code for Body Data (SOL 400 only)
Rigid Body Data
Element Code Item 3D Surface Item (SOL 400 Only)
203 1 BCBODY ID
2-17 XMAT 4x4
18 Contact force component RF x
19 Contact force component RF y
20 Contact force component RF z
21 Contact moment component RM x
22 Contact moment component RM y
23 Contact moment component RM z
Main Index
996 MSC Nastran Quick Reference Guide
Element Strain Energy Item Codes
Remarks:
1. F nx F ny F nz are normal force components in the global coordinate system.
2. F fx F fy F fz are friction force components in the global coordinate system.
3. Normal force magnitude is square root of sum of squares of F nx F ny F nz .
4. Friction force magnitude is square root of sum of squares of F fx F fy F fz with sign of largest
absolute of these values.
5. Contact touched body applies to SECNDRY grids (touching node) only.
6. A secondary grid may not contact more than 3 bodies.
7. Only secondary grids have non-zero contact status or touched bodies.
8. RF x RF y RF z RM x RM y RM z are the contact force and moment in the global coordinate
system that applied on the centroid of the corresponding rigid body.
9. [XMAT] is the translation matrix to compute the new location of the rigid body.
10. These contact outputs, both Table 7-10 and Table 7-11 are saved in datablock OFCON3D.
Element Strain Energy Item Codes
Table 7-12 Element Strain Energy Item Codes
Real Element Data
Element Name Item Code Item
Element groups A and B 2 Element strain energy
Element groups A and B 3 Percent of total energy
Element group A 4 Element strain energy density
Remark:
1. Element group A includes elements of CBAR, CBEAM, CBEND, CONROD, CHEXA, CPENTA,
CPYRAM, CQUAD4, CQUADR, CROD, CSHEAR, CTETRA, CTRIA3, CTRIA6, CTRIAR,
and CTUBE. Element group B includes elements of CELAS1, CELAS2, CELAS3, AND CGAP.
Main Index
CHAPTER 7 997
Fatigue Item Codes
Fatigue Item Codes
Note that the codes of the Table 7-13 through Table 7-16 are limited to those that can be referenced on a
DRESP1 entry with RTYPE= FATGUE.
Table 7-13 Fatigue Item Codes for LOC=ELEM on FTGPARM
Element Name Item Code Real Element Data Item
Element Group A and 4 Fatigue life in Repeats of the loading sequence
Element Group B (-4) See remark 4.
(for Z1 layer - bottom) 5 (-5) Log of fatigue life in Repeats of the loading sequence
6 (-6) Fatigue life in user defined fatigue equivalent units
7 (-7) Log of fatigue life in user defined fatigue equivalent
units
8 (-8) Fatigue damage
9 (-9) Log of fatigue damage
12 (-12) Scale factor from Factor of Safety analysis
Element Group B 18 Fatigue life in Repeats of the loading sequence
(for Z2 layer - top) 19 Log of fatigue life in Repeats of the loading sequence
20 Fatigue life in user defined fatigue equivalent units
21 Log of fatigue life in user defined fatigue equivalent
units
22 Fatigue damage
23 Log of fatigue damage
26 Scale factor from Factor of Safety analysis
Remark:
1. Element Group A consists of elements: CHEXA, CPENTA, CPYRAM, CTETRA, CTRIA3,
CSHEAR
2. Element Group B consists of elements: CQUAD4, CQUAD8, CQUADR, CTRIA6, CTRIAR
3. For CTRIA3 and CSHEAR elements, LOC=ELEM and LOC=NODE or NODA options on
FTGPARM use the same item codes in Table 7-13.
4. For Element Group B (shell elements), if the item code is negative (e.g., -4) for layer Z1, this flags
Nastran to automatically (and internally) create a DRESP1 with the corresponding item code for
layer Z2. This is a convenient method to include responses from both top and bottom by defining
only a single DRESP1 entry for any particular set of elements or property sets.
Main Index
998 MSC Nastran Quick Reference Guide
Fatigue Item Codes
Note: SOL 200 only supports NODE and not NODA on the FTGPARM entry
Table 7-14 Fatigue Item Codes for LOC=NODE or NODA on FTGPARM
Element Name Item Codes Real Element Data Item
CTETRA 4,16,28,40 Life in Repeats of the loading sequence
5,17,29,41 Log of life in Repeats of the loading sequence
6,18,30,42 Life in user defined fatigue equivalent units
7,19,31,43 Log of life in user defined equivalent units
8,20,32,44 Fatigue damage
9,21,33,45 Log of fatigue damage
12,24,36,48 Scale factor from Factor of Safety analysis
CQUAD4 4,33,62,91 Life in Repeats of the loading sequence
CQUAD8 (-4,-33,-62,-91) See remark 8.
CQUADR 5,34,63,92 Log of life in Repeats of the loading sequence
(for Z1 layer - bottom) (-5,-34,-63,-92)
6,35,64,93 Life in user defined fatigue equivalent units
(-6,-35,-64,-93)
7, 36, 65, 94 Log of life in user defined equivalent units
(-7,-36,-65, -94)
8, 37, 66, 95 Fatigue damage
(-8,-37,-66,-95)
9, 38, 67, 96 Log of fatigue damage
(-9,-38,-67-96)
12, 41, 70, 99 Scale factor from Factor of Safety analysis
(-12,-41,-70,-99)
(for Z2 layer - top) 18, 47, 76, 105 Life in Repeats of the loading sequence
19, 48, 77, 106 Log of life in Repeats of the loading sequence
20, 49, 78, 107 Life in user defined fatigue equivalent units
21, 50, 79, 108 Log of life in user defined equivalent units
22, 51, 80, 109 Fatigue damage
23, 52, 81, 110 Log of fatigue damage
26, 55, 84, 113 Scale factor from Factor of Safety analysis
Main Index
CHAPTER 7 999
Fatigue Item Codes
Table 7-14 Fatigue Item Codes for LOC=NODE or NODA on FTGPARM (continued)
Element Name Item Codes Real Element Data Item
CTRIA6 4, 33, 62 Life in Repeats of the loading sequence
CTRIAR (-4, -33, -62) See remark 8.
(for Z1 layer - bottom) 5, 34, 63 Log of life in Repeats of the loading sequence
(-5, -34, -63)
6, 35, 64 Life in user defined fatigue equivalent units
(-6, - 35, -64)
7, 36, 6 Log of life in user defined equivalent units
(-7, -36, -6)
8, 37, 66 Fatigue damage
(-8, -37, -66)
9, 38, 67 Log of fatigue damage
(-9, -38, -67)
12, 41, 70 Scale factor from Factor of Safety analysis
(-12, -41, -70)
(for Z2 layer - top) 18, 47, 76 Life in Repeats of the loading sequence
19, 48, 77 Log of life in Repeats of the loading sequence
20, 50, 79 Life in user defined fatigue equivalent units
22, 51, 80 Log of life in user defined equivalent units
23, 52, 81 Fatigue damage
26, 55, 84 Log of fatigue damage
Scale factor from Factor of Safety analysis
CPENTA 4,16,28,40,52,64 Life in Repeats of the loading sequence
5,17,29,41,53,65 Log of life in Repeats of the loading sequence
6,18,30,42,54,66 Life in user defined fatigue equivalent units
7,19,31,43,55,67 Log of life in user defined equivalent units
8,20,32,44,56,68 Fatigue damage
9,21,33,45,57,69 Log of fatigue damage
12,24,36,48,60,72 Scale factor from Factor of Safety analysis
Main Index
1000 MSC Nastran Quick Reference Guide
Fatigue Item Codes
Table 7-14 Fatigue Item Codes for LOC=NODE or NODA on FTGPARM (continued)
Element Name Item Codes Real Element Data Item
CPYRAM 4,16,28,40,52 Life in Repeats of the loading sequence
5,17,29,41,53 Log of life in Repeats of the loading sequence
6,18,30,42,54 Life in user defined fatigue equivalent units
7,19,31,43,55 Log of life in user defined equivalent units
8,20,32,44,56 Fatigue damage
9,21,33,45,57 Log of fatigue damage
12,24,36,48,60 Scale factor from Factor of Safety analysis
CHEXA 4,16,28,40,52,64,76,88 Life in Repeats of the loading sequence
5,17,29,41,53,65,77,89 Log of life in Repeats of the loading sequence
6,18,30,42,54,66,78,90 Life in user defined fatigue equivalent units
7,19,31,43,55,67,79,91 Log of life in user defined equivalent units
8,20,32,44,56,68,80,92 Fatigue damage
9,21,33,45,57,69,81,93 Log of fatigue damage
12,24,36,48,60,72,84,96 Scale factor from Factor of Safety analysis
Remarks:
1. CTRIA6 and CTRIAR item codes are listed for Grids 1-3, respectively.
2. CQUAD4, CQUAD8, CQUADR, CTETRA item codes are listed for Grids 1-4, respectively.
3. CPYRAM item codes are listed for Grids 1-5, respectively.
4. CPENTA item codes are listed for Grids 1-6, respectively.
5. CHEXA item codes are listed for Grids 1-8, respectively.
6. For CTRIA3 and CSHEAR elements, LOC=ELEM and LOC=NODE or NODA options on
FTGPARM use the same item codes in Table 7-13.
7. If it is desired to use a life response (or other item) for all nodes (using LOC=NODE or NODA on
FTGPARM), all item codes for the particular item are required, e.g., 4, 16, 27, and 38 for CTETRA
(one DRESP1 entry for each item code).
8. For shell elements with bottom (Z1) and top (Z2) layers, if the item code is negative (e.g., -4) for layer
Z1, this flags Nastran to automatically (and internally) create a DRESP1 with the corresponding item
code for layer Z2. This is a convenient method to include responses from both top and bottom by
defining only a single DRESP1 entry for any particular response for a set of elements or property sets.
So as an example, to specify the bottom and top response (Life in Repeats) for all the grids of the
specified element or property set for a CQUAD4 element, use items codes: -4,-27,-50,-73
9. These item codes are used for LOC=NODE or NODA and all other element nodal values of
RECOVER on the FTGPARM entry, namely, “SGAGE”, “CORNER”, “BILIN”, and “CUBIC”
also.
Main Index
CHAPTER 7 1001
Fatigue Item Codes
Table 7-15 Item Codes for Fatigue Analysis of Spot Welds
Element Name Item Code Real Element Data Item
CBAR 4 Fatigue life in Repeats of the loading sequence
CBEAM (-4) (-1004) See remarks 2. and 3.
CWELD 5 ( -5)(-1005) Log of fatigue life in Repeats of the loading sequence
CHEXA
(For Top Sheet at 6 (-6)(-1006) Fatigue life in user defined fatigue equivalent units
Angle = 0.0 7 (-7)(-1007) Log of fatigue life in user defined fatigue equivalent units
degrees) 8 (-8)(-1008) Fatigue damage
9 (-9)(-1009) Log of fatigue damage
13 (-13)(-1013) Scale factor from Factor of Safety analysis
CBAR 4+12*NANGLE Fatigue life in Repeats of the loading sequence
CBEAM 5+12*NANGLE Log of fatigue life in Repeats of the loading sequence
CWELD
CHEXA 6+12*NANGLE Fatigue life in user defined fatigue equivalent units
(For Weld Nugget 7+12*NANGLE Log of fatigue life in user defined fatigue equivalent units
at Angle = 0.0 8+12*NANGLE Fatigue damage
degrees)
9+12*NANGLE Log of fatigue damage
13+12*NANGLE Scale factor from Factor of Safety analysis
CBAR 4+24*NANGLE Fatigue life in Repeats of the loading sequence
CBEAM 5+24*NANGLE Log of fatigue life in Repeats of the loading sequence
CWELD
CHEXA 6+24*NANGLE Fatigue life in user defined fatigue equivalent units
(For Bottom 7+24*NANGLE Log of fatigue life in user defined fatigue equivalent units
Sheet at Angle = 8+24*NANGLE Fatigue damage
0.0 degrees)
9+24*NANGLE Log of fatigue damage
13+24*NANGLE Scale factor from Factor of Safety analysis
Remarks:
1. Spot weld fatigue item code is related to NANGLE, the number of calculation angles around the weld
circumference as defined on the FTGPARM entry. Item codes listed above are for the first angle at
zero (0) degrees. For each subsequent angle, the item code should be increased by 12. For example,
item code =16 is for “Fatigue life in Repeats of the loading sequence” at the Top Sheet for the second
angle.
Main Index
1002 MSC Nastran Quick Reference Guide
Fatigue Item Codes
2. If item codes 4-9 or 13 are negative (e.g., -4), this flags Nastran to automatically (and internally)
create a DRESP1 with the corresponding item code for the nugget and bottom sheet as well and for
all specified angles. This is a convenient method to include responses from all locations and angles by
defining only a single DRESP1 entry for any particular response for a set of spot weld elements or
property sets. So as an example, to specify the response (Life in Repeats) for all the locations and angles,
use a single DRESP1 entry with item code: -4.
3. In conjunction with the above remark, if the item code is negative and multiplied by 1000
(e.g., -1004), then the nugget responses are not generated. Only the top and bottom sheet responses
are internally generated.
Table 7-16 Item Codes for Fatigue Analysis of Seam Welds
Element Name Item Code Real Element Data Item
CQUAD4 4, 19, 34, 45 Fatigue life in Repeats of the loading sequence
CQUAD8 5, 20, 35, 46 Log of fatigue life in Repeats of the loading sequence
CQUADR
6, 21, 36, 47 Fatigue life in user defined fatigue equivalent units
7, 22, 37, 48 Log of fatigue life in user defined fatigue equivalent units
8, 23, 38, 49 Fatigue damage
9, 24, 39, 50 Log of fatigue damage
12, 27, 42, 53 Scale factor from Factor of Safety analysis
CTRIA6 4, 19, 34 Fatigue life in Repeats of the loading sequence
CTRIAR 5, 20, 35 Log of fatigue life in Repeats of the loading sequence
6, 21, 36 Fatigue life in user defined fatigue equivalent units
7, 22, 37 Log of fatigue life in user defined fatigue equivalent units
8, 23, 38 Fatigue damage
9, 24, 39 Log of fatigue damage
12, 27, 42 Scale factor from Factor of Safety analysis
Remarks:
1. CQUAD4, CQUAD8, CQUADR item codes are listed for Grids 1-4, respectively.
2. CTRIA6 and CTRIAR item codes are listed for Grids 1-3, respectively.
3. Note that FTGDEF has a keyword “SEAMW” that may have the field NDSIDi, which lists seam line
grids. If this is used, it means that some grids of the elements will not have fatigue life associated with
them and are excluded from the analysis.
Main Index
CHAPTER 7 1003
Equivalent Radiated Power (ERP) Item Codes
Equivalent Radiated Power (ERP) Item Codes
Table 7-17 Equivalent Radiated Power (ERP) Item Codes
Element Name
Item Code Item
QUAD4, CQUADR, CTRIA3,CTRIAR 2 ERP value
QUAD4, CQUADR, CTRIA3,CTRIAR 3 ERP Fraction
QUAD4, CQUADR, CTRIA3,CTRIAR 4 ERP(DB)
Main Index
1004 MSC Nastran Quick Reference Guide
Equivalent Radiated Power (ERP) Item Codes
Main Index
Chapter 8: Degree-of-Freedom Sets MSC Nastran Quick Reference Guide
8 Degree-of-Freedom Sets
Degree-of-Freedom Set Definitions
Degree-of-Freedom Set Bulk Data Entries
Main Index
1006 MSC Nastran Quick Reference Guide
Degree-of-Freedom Set Definitions
Degree-of-Freedom Set Definitions
Each degree-of-freedom is a member of one mutually exclusive set. Set names have the following definitions:
Set Name Definition
mp Degrees-of-freedom eliminated by multipoint constraints.
mr
Degrees-of-freedom eliminated by multipoint constraints created by the rigid elements
using the LGELIM method on the Case Control command RIGID.
sb* Degrees-of-freedom eliminated by single-point constraints that are included in boundary
condition changes and by the AUTOSPC feature. (See the sz set)
sg* Degrees-of-freedom eliminated by single-point constraints that are specified on the PS field
on GRID Bulk Data entries.
sz Degrees-of-freedom eliminated by the AUTOSPC feature.
o Degrees-of-freedom omitted by structural matrix partitioning.
q Generalized degrees-of-freedom assigned to component modes and residual vectors.
r reference degrees-of-freedom used to determine free body motion.
c Degrees-of-freedom that are free during component mode synthesis or dynamic reduction.
b Degrees-of-freedom fixed during component mode analysis or dynamic reduction.
Lagrange multiplier degrees-of-freedom created by the rigid elements using the LAGR
lm method on the Case Control command, RIGID.
e extra degrees-of-freedom introduced in dynamic analysis.
sa Permanently constrained aerodynamic degrees-of-freedom.
k Aerodynamic mesh point set for forces and displacements on the aero mesh.
j Aerodynamic mesh collocation point set (exact physical interpretation is dependent on the
aerodynamic theory).
*Strictly speaking, sb and sg are not exclusive with respect to one another. Degrees-of-freedom may exist in
both sets simultaneously. Since these sets are not used explicitly in the solution sequences, this need not
concern the user. However, those who use these sets in their own DMAPs should avoid redundant
specifications when using these sets for partitioning or merging operations. That is, a degree-of-freedom
should not be specified on both a PS field of a GRID entry (sg set) and on a selected SPC entry (sb set).
Redundant specifications will cause UFM 2120 in the VEC module and behavior listed in MSC Nastran
DMAP Programmer’s Guide for the UPARTN module. These sets are exclusive, however, from the other
mutually exclusive sets.
Main Index
Chapter 8: Degree-of-Freedom Sets 1007
Degree-of-Freedom Set Definitions
Each degree-of-freedom is also a member of one or more combined sets called “supersets.” Supersets have the
following definitions:
sets supersets
mp
m
mr
sb
sg s
o
g
q p
r n ne
c a d f
t fe
b l
lm
e
k
ks
sa
js
j
Set Name Meaning (+ indicates union of two sets)
s = sb + sg all degrees-of-freedom eliminated by single point constraints
l = b + c + lmthe degrees-of-freedom remaining after the reference degrees-of-freedom are removed
(degrees-of-freedom left over)
t = l+r the total set of physical boundary degrees-of-freedom for superelements
a = t+q the analysis set used in eigensolution
d = a+e the set used in dynamic analysis by the direct method
f = a+o unconstrained (free) structural degrees-of-freedom
fe = f + e free degrees-of-freedom plus extra degrees-of-freedom
n = f+s all degrees-of-freedom not constrained by multipoint constraints
ne = n + e all degrees-of-freedom not constrained by multipoint constraints plus extra degrees-of-
freedom
m = mp + mrall degrees-of-freedom eliminated by multipoint constraints
g = n + m all degrees-of-freedom including scalar degrees-of-freedom
p = g+e all physical degrees-of-freedom including extra point degree-of-freedom
ks = k + sa the union of k and the re-used s-set (6 dof per grid)
js = j + sa the union of j and the re-used s-set (6 dof per grid)
table continued on the next page
Main Index
1008 MSC Nastran Quick Reference Guide
Degree-of-Freedom Set Definitions
Set Name Meaning (+ indicates union of two sets)
fr = o + l statically independent set minus the statically determinate supports fr = f – q – r
v = o + c + r the set free to vibrate in dynamic reduction and component mode synthesis
al = a – lm a-set without Lagrange multiplier degree-of-freedoms.
dl = d – lm d-set without Lagrange multiplier degree-of-freedoms.
gl = g – lm g-set without Lagrange multiplier degree-of-freedoms.
ll = l – lm l-set without Lagrange multiplier degree-of-freedoms.
nf = ne – lmne-set without Lagrange multiplier degree-of-freedoms.
pl = p – lm p-set without Lagrange multiplier degree-of-freedoms.
tl = t – lm t-set without Lagrange multiplier degree-of-freedoms.
nl = n – lm n-set without Lagrange multiplier degree-of-freedoms.
fl = f – lm f-set without Lagrange multiplier degree-of-freedoms.
ff = fe – lm fe-set without Lagrange multiplier degree-of-freedoms.
The a-set and o-set are created in the following ways:
1. If only OMITi entries are present, then the o-set consists of degrees-of-freedom listed explicitly on
OMITi entries. The remaining f-set degrees-of-freedom are placed in the b-set, which is a subset of
the a-set.
2. If ASETi or QSETi entries are present, then the a-set consists of all degrees-of-freedom listed on
ASETi entries and any entries listing its subsets, such as QSETi, SUPORTi, CSETi, and BSETi
entries. Any OMITi entries are redundant. The remaining f-set degrees-of-freedom are placed in the
o-set.
3. If there are no ASETi, QSETi, or OMITi entries present but there are SUPORTi entries present, then
the entire f-set is placed in the a-set and the o-set is not created.
4. There must be at least one explicitly ASETi, QSETi, or OMITi entry for the o-set to exist, even if the
ASETi, QSETi, or OMITi entry is redundant.
In dynamic analysis, additional vector sets are obtained by a modal transformation derived from real
eigenvalue analysis of the a-set. These sets are as follows:
o = rigid body (zero frequency) modal degrees-of-freedom
f = finite frequency modal degrees-of-freedom
i = o + f , the set of all modal degrees-of-freedom
One vector set is defined that combines physical and modal degrees-of-freedom:
u h = i + u e , the set of all modal degrees-of-freedom
Main Index
Chapter 8: Degree-of-Freedom Sets 1009
Degree-of-Freedom Set Definitions
The membership of each degree-of-freedom can be printed by use of the Bulk Data entries
PARAM,USETPRT and PARAM,USETSEL.
Main Index
1010 MSC Nastran Quick Reference Guide
Degree-of-Freedom Set Bulk Data Entries
Degree-of-Freedom Set Bulk Data Entries
Degrees-of-freedom are placed in sets as specified by the user on the following Bulk Data entries:
Name Bulk Data Entry Name
m MPC, MPCADD, MPCAX, POINTAX, RBAR, RBAR1, RBE1, RBE2, RBE3, RJOINT,
RROD, RSPLINE, RSSCON, RTRPLT, RTRPLT1
sb SPC, SPC1, SPCADD, SPCAX, FLSYM, GMSPC*, BNDGRID, PARAM,AUTOSPC,YES
sz PARAM,AUTOSPC,YES
sg GRID, GRIDB, GRDSET (PS field)
o OMIT, OMIT1, OMlTAX, GRID (SEID field), SESET
q QSET, QSET1
r SUPORT, SUPORT1, SUPAX
c CSET, CSET1, BNDFREE, BNDFRE1
b BSET, BSET1, BNDFIX, BNDFIX1
e EPOINT
sa CAEROi
k CAEROi
a ASET, ASET1, Superelement exterior degrees-of-freedom, CSUPEXT
ap ACCSPT
rv RVDOF and RVDOF1
u1 - u6 USET, USET1, SEUSET, and SEUSET1
In superelement analysis, the appropriate entry names are preceded by the letters SE, and have a field reserved
for the superelement identification number. This identification is used because a boundary (exterior) grid
point may be in one mutually exclusive set in one superelement and in a different set in the adjoining
superelement. The SE-type entries are internally translated to the following types of entry for the referenced
superelement:
Entry Type Equivalent Type
SEQSETi QSETi
SESUP SUPORT
SECSETi CSETi, BNDFREE, DNBDRE1
SEBSETi BSETi, BNDFIXi
Main Index
Chapter 9: Bulk Data Entries MSC Nastran Quick Reference Guide
9 Bulk Data Entries
Key to Descriptions
Bulk Data Entry Descriptions
Main Index
1012 MSC Nastran Quick Reference Guide
Key to Descriptions
Key to Descriptions
The field names in fields 2 through 9
The name of are for reference only. Names
the entry. Must enclosed in quotation marks A brief sentence
be entered as represent character constants; e.g., about the function
shown. “THRU” on ASET1 entry. of the entry is
ACMODL Fluid-Structure Interface Modeling Parameters
If a box in fields 2 through
9 is shaded, then the field
must be left blank.
Defines modeling parameters for the interface between the fluid and the structure.
Format:
1 2 3 4 5 6 7 8 9 10
ACMODL INTER INFOR FSET SSET FSTO
Example:
If the box in field 10 is
ACMODL 0.002 shaded, then no continuation
entries may follow.
FieldContents
INTERType of interface between the fluid and the structure. See Remark 1. (Character = “IDENT” or “DIFF”;
Default = “DIFF”). Each of the fields is briefly described. Further
details may be discussed under Remarks.
INFORIndicates whether FSET and SSET are to be used to define the fluid-structure interface. (Character =
Character constants
“ALL” areDefault
or “NONE”, enclosed in
= “NONE”).
quotation marks to distinguish them from
FSETIdentification number of a SET1 entry that contains a list of fluid grid points on the interface. See Remark
field names. Do not input these quotation
marks.
2. (Integer > 0 or blank). Under contents, “blank” usually means that
this
SSETIdentification number of a SET1 entry that contains a listfeature can
of structural gridbe optionally
points selected
on the interface. See by the
Remark 2. (Integer > 0 or blank). user. It may also mean the default action or
value is described under Remarks. When
FSTOLTolerance, in units of length, used in determiningcontent
the fluid-structure
item isinterface.
listed (Real
as, >for
0.0;example,
Default =
0.001).
(Integer>0 or blank) a value of 0 entered in
the field is equivalent to "blank".
Remarks:
The
1. Only one ACMODL entry is allowed. field’s
If this entrytype
is not(Integer, Real,
present, then or Character),
the program will
assume INTER = “DIFF” and FSTOL allowable
= .001. range, and default value are enclosed
in parentheses. If no default value is given, then
2. If INFOR = “ALL”, then both FSETaand SSET
value mustbe
must be specified
specified andby
matching is
the user.
checked at only those grid points referenced by FSET and SSET.
3. See the MSC Nastran Reference Guide, 15 for a description of the methods used in
determining the fluid-structure interface.
4. The points referenced by FSET and SSET must lie exactly on the fluid-structure
interface.
TheAremarks
fatal message
are isgenerally
issued if: (a) INTER =in“IDENT”
arranged order ofand a point in SSET or
FSET importance
does not have aand
corresponding and coincident
indicate such things aspoint
thein FSET or SSET,
respectively,
entry’sor relationship
(b) INTER = “DIFF” andentries
to other any pointor
in SSET or FSET does not lie on the
interface.
commands, restrictions, and recommendations
on usage, or further details regarding the fields.
Main Index
Chapter 9: Bulk Data Entries 1013
Key to Descriptions
The Bulk Data Section
The Bulk Data Section contains entries that specify model geometry, element connectivity, element and
material properties, constraints (boundary conditions), and loads. Some entries, such as loads and constraints,
are selected by an appropriate Case Control command.
Entries are prepared in either fixed or free field format. The descriptions in this section show only the fixed
format. For a description of the various format options, see the Use of Parameters in the MSC Nastran Reference
Guide.
New Bulk Data Entries added after the MSC Nastran 2011 version are only valid with the default option
IFPSTAR=YES.
Main Index
1014 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Bulk Data Entry Descriptions
Each Bulk Data entry is described as follows:
Description
A brief sentence about the function of the entry is given.
Format
The name of the entry is given in the first field. The subsequent fields are described under the Field and
Contents Section. Shaded fields must be left blank. If field 10 is shaded, then no continuation entries are
permitted. Character strings enclosed in quotation marks must be specified without the quotation marks as
shown in the example. Typically, strings enclosed in quotation marks indicate that the entry is optional and
if multiple such strings occur, they may appear in any order.
Example
A typical example is given.
Field and Contents
Each of the fields 2 through 9 that are named in the Format section is briefly described under Contents. The
field’s type (e.g., Integer, Real, or Character), allowable range, and default value are enclosed in parentheses.
The field must be specified by the user if no default value is given.
Remarks
The remarks in the Remarks Section are generally arranged in order of importance and indicate such things
as how the Bulk Data entry is selected in the Case Control Section, its relationship to other entries,
restrictions and recommendations on its use, and further descriptions of the fields.
Main Index
Chapter 9: Bulk Data Entries 1015
Bulk Data Entry Descriptions
Format of Bulk Data Entries
Real, Integer, and Character Input Data
Nastran is quite particular about the input requirements for data entry. The three possible types of data entries
are Integer, Real, and Character (sometimes called literal, or BCD-binary coded decimal). The three types of
data are described as follows:
Integer Cannot contain a decimal point.
Real Must contain a decimal point. If however, system cell 444 is set to 9 and the only possible
value format is real, then an integer representation (less decimal point) will be converted
to real. A single decimal point is not be considered a real zero value. Either 0 or 0. (a digit)
must be supplied.
Character Can be alphanumeric, and with exceptions (listed on specific bulk data entries) should
always start with an alpha character. Legal alpha characters are the English: A-Z and a-z.
Legal numeric characters are 0-9, and in special circumstances in fields that allow user
naming the dash (-) and the underscore (_). In user naming fields use of $, &, *, =, +,
period (.), comma (,) should be avoided as they often have special meaning to the nastran
bulk data interpreter. Misspelled required words such as the name of an entry will result
in a fatal message. Substitution of non English alphabetic characters will cause a fatal
message to be issued.
Real numbers may be entered in a variety of ways. For example, the following are all acceptable versions of
the real number seven:
7.0 .7E1 0.7+1
.70+1 7.E+0 70.-1
Free, Small, and Large Field Formats
Nastran has three different field formats for input data:
Free Field Format Input data fields are separated by commas.
Small Field Format Ten fields of eight characters each.
Large Field Format Ten fields-eight fields containing actual data are sixteen characters each (fields 2-
5 and 6-9). Large fields are used when greater numerical accuracy is required. See
the Large Field Format, 1020 for additional information.
The NASTRAN statement, File Management Section, Executive Control Section, and Case Control Section
use free field format. The Bulk Data Section allows the use of any of the three formats.
Nastran Bulk Data contains ten fields per input data entry. The first field contains the character name of the
Bulk Data item (e.g., GRID, CBAR, MAT1, etc.). Fields two through nine contain data input information
Main Index
1016 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
for the Bulk Data entry. The tenth field never contains data-it is reserved for entry continuation information,
if applicable.
Consider the format of a typical MSC Nastran Bulk Data entry, the GRID entry, which is used in Nastran
to describe the geometry of the structural model.
Field Number
1 2 3 4 5 6 7 8 9 10
GRID ID CP X1 X2 X3 CD PS SEID
Fields containing input
data for the GRID entry. Field 10 is used only for
optional continuation
Character name of information when applicable.
this Bulk Data entry
Example:
1 2 3 4 5 6 7 8 9 10
GRID 2 1.0 -2.0 3.0 136
We will now represent this example in free field, small field, and large field formats.
Free Field Format
In free field format, data fields are separated by commas or blanks (commas are strongly recommended). The
following shows the GRID Bulk Data entry example in free field format:
GRID,2,,1.0,-2.0,3.0,,136
Two consecutive commas
indicate an empty field
The rules for free field format are as follows:
Free field data entries must start in column 1.
To skip one field, use two commas in succession. To skip two fields, use three commas in succession
(and so on).
Integer or character fields with more than eight characters cause a fatal error.
Real numbers with more than eight characters are rounded off and lose some precision. For example,
an entry of 1.2345678+2 becomes 123.4568. If more significant digits are needed, use the large field
format. If however, NASTRAN IFPSTAR=YES is used, then the entry will automatically be
converted to large field format.
Main Index
Chapter 9: Bulk Data Entries 1017
Bulk Data Entry Descriptions
Free field data cannot contain embedded blanks to skip fields. An example of a free field embedded
blank is shown:
GRID,2,,1 0,-2.0,3.0,,136
Embedded blank
not allowed
In a continuation line, if a comma is the first character and in the first 8 columns, this line is free
format.
A dollar sign $ can be used within a line. All data following the $ on the line will be for comments.
An example of a comment is shown:
DISP(PUNCH)=ALL $ request punched displacement output for all grids
The free field data entry capability in Nastran have been enhanced to support easy to use data input formats.
The following examples illustrate the possible forms of the free field data input and the resulting translation
to the fixed-field format.
Entry with or without user continuation mnemonics.
MATT9,1101,2 ,3 ,4 ,,,,8 ,+P101
+P101,9 ,,,,13
Translates to:
1 2 3 4 5 6 7 8 9 10
MATT9 1101 2 3 4 8 +P101
+P101 9 13
GRID,100,,1.0,0.0,0.0,,456
Translates to:
GRID 100 1.0 0.0 0.0 456
The continuation mnemonics are not included because they are not required. This is illustrated by the entry
with automatic continuation:
SPC1,100,12456,1,2,3,4,5,6,7,8,9,10
Translates to:
1 2 3 4 5 6 7 8 9 10
SPC1 100 12456 1 2 3 4 5 6
7 8 9 10
If more than 80 characters of data are required, the free field may be continued in the next line provided that
the next entry starts with a comma in the first column. The next entry will be a logical continuation of the
first. For example, the free-field entry:
Main Index
1018 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
MATT9,1151,2 ,3 ,4 ,,,,8
,9 ,,,,13
Translates to:
1 2 3 4 5 6 7 8 9 10
MATT9 1151 2 3 4 8
9 13
Which is equivalent to:
MATT9,1151,2 ,3 ,4 ,,,,8 ,+
+,9 ,,,,13
Translates to:
1 2 3 4 5 6 7 8 9 10
MATT9 1151 2 3 4 8 +
+ 9 13
The free field data entry can be used to input mixed Small Field, Large Field continuations. Note that the
plus (+) and asterisk (*) characters are used to indicate Small Field and Large Field input form respectively
when free field data entry is used. For example, the entries:
MATT9*,1302,2 ,,4 ,+
+,,,,,13
Translates to:
1 2 3 4 5 6 7 8 9 10
MATT9* 1302 2 4 +
+ 13
MATT9,1303,2 ,3 ,4 ,,,,8 ,+
*,9 ,,,,+
*,13
Translates to:
1 2 3 4 5 6 7 8 9 10
MATT9 1303 2 3 4 8 +
* 9
* 13
MATT9,1355,2 ,3 ,,5 ,,,8 ,+
*,,10 ,,,+
+,17
Main Index
Chapter 9: Bulk Data Entries 1019
Bulk Data Entry Descriptions
Translates to:
1 2 3 4 5 6 7 8 9 10
MATT9 1355 2 3 5 8 +
* 10 +
+ 17
System cell 363 must be set to 1 (i.e., system(363)=1, or STRICTUAI=1) if more than 80 characters of data
are required, then the free-field entry is continued by terminating the parent with a comma. The next entry
will be a logical continuation of the first. It is not required to end the first entry at any specific point. This is
illustrated by the entry:
CHEXA,200, 200, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
17, 18, 19, 20
Translates to:
1 2 3 4 5 6 7 8 9 10
CHEXA 200 200 1 2 3 4 5 6
7 8 9 10 11 12 13 14
15 16 17 18 19 20
Because of the feature allowing more than 10 fields of data to be entered on one free field entry, IT IS NOT
ALLOWED to terminate a single free field entry with a comma. For example:
CHEXA,200, 200, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
Small Field Format
Small field format separates a Bulk Data entry into ten equal fields of eight characters each:
8 character field
1 2 3 4 5 6 7 8 9 10
11 12 13 14 15 16 17 18 19 20
80 characters
The following is an example of the GRID entry in small field format:
1 2 3 4 5 6 7 8 9 10
GRID 2 1.0 -2.0 3.0 136
The rules for small field format are as follows:
Fields 1 and 10 must be left justified.
Fields 2 through 9 do not need to be either right or left justified, although aligning the data fields is
good practice.
Main Index
1020 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Small field input data cannot contain any embedded blanks. An example of a small field embedded
blank is shown:
8 character field
7 . 6 5
Embedded blank
not allowed
Large Field Format
A high degree of numerical accuracy is required in some Nastran applications. Large field format is used when
small field format does not provide enough significant digits (recall that a minus sign, decimal point, and the
“E” in scientific notation count as characters).
Large field format requires (at least) two lines for each entry: the first and last field of each line contains eight
columns, and the fields in between contain 16 columns. Short field becomes two lines. Large field entries are
denoted by an asterisk (*) immediately following the character string in field 1A of the first line and
immediately preceding the character string in field 1B of the second line.
The following is an example of the GRID Bulk Data entry example in large field format:
First Line: (Left half of single field)
Field 1A 2 3 4 5 6
GRID* 2 1.0 -2.0 *GRID10
8 16 16 16 16 8
columns
Second Line: (Right half of single field)
Field 1B 6 7 8 9 10B
*GRID10 3.0 136
8 16 16 16 16 8
columns
Continuations
Some Bulk Data entries require more than eight fields (72 columns) of data. Continuations are required in
such cases. To do this, a parent entry (the first line) is followed by one or more continuation entries on
subsequent lines. For example, consider the following PBAR simple beam property entry (do not worry about
what each field represents-this will be explained later):
Main Index
Chapter 9: Bulk Data Entries 1021
Bulk Data Entry Descriptions
Format:
1 2 3 4 5 6 7 8 9 10
PBAR PID MID A I1 I2 J NSM
C1 C2 D1 D2 El E2 F1 F2
K1 K2 I12
Continuation Example:
PBAR 39 6 2.9 1.86 2.92 .48 +PB1
+PB1 0. 0. 0. 1. 1. 1. 1. 0. +PB2
+PB2 .86 .86
+PB1 in field 10 of the parent entry is an arbitrary (and unique) user-defined pointer to field 1 of the second
line. +PB2 in the second line points the third line, and so on.
Continuation fields can also be generated automatically by Nastran (this approach is the recommended
practice). To automatically generate a continuation, the continuation line (or lines) must immediately follow
the parent Bulk Data entry. In addition, fields 1 and 10 of the continuation line (or lines) must be left blank.
In the case of double-width generated continuations are not blank in field 1, but have an “*” in column 1.
Nastran will then generate unique continuations for you. This process is illustrated in the following example:
Input (.DAT) file:
CHEXA, 1, 10, 3, 5, 7, 1, 15, 17,
, 19, 13, 4, 6, 8, 2, 10, 11,
, 12, 9, 16, 18, 20, 14
Output (.F06) file:
GEAR TOOTH EXAMPLESEPTEMBER 29, 1993 MSC.Nastran 9/ 4/91 PAGE 3
S O R T E D B U L K D A T A E C H O
CARD
COUNT. 1 .. 2 .. 3 .. 4 .. 5 .. 6 .. 7 .. 8 .. 9 .. 10 .
1- CHEXA 1 10 3 5 7 1 15 17 +000001
2-++000001 19 13 4 6 8 2 10 11 +000002
3-++000002 12 9 16 18 20 14 +000003
Blank lines are allowed if they are in between entries but not allowed if they
are in an entry and further continuations are followed if ifpstar is yes, for
example, the blank line in below entry is not allowed. To ignore those blank
lines, set system(767) to 1.
CHEXA, 1, 10, 3, 5, 7, 1, 15, 17,
, 19, 13, 4, 6, 8, 2, 10, 11,
, 12, 9, 16, 18, 20, 14
Nastran Continuation fields (fields one and ten) are replicated using the following conventions:
1. Only letters of the alphabet and integers may be used. They are coded into a base 36 number. That
is, the sequence of numbers is 0,1, 2, ..., 8, 9, A, B, ...
2. The first character in field one or ten is not incremented.
3. The continuation fields are incremented by +1 regardless of the value specified by the user.
Main Index
1022 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
4. The number of characters in an incremented field will not be increased. For example, if the first field
is “0", the thirty-seventh field will also be “0", resulting in an illegal entry. A method to solve this
problem would be to start with a first field of “00". This will provide thirty-six squared unique fields.
5. At least one field in fields 2 through 8 of continuation entries must be non-blank.
Replication
Replication is a limited data generation capability which may be used in a fixed or free-field format and is not
currently fully supported with NASTRAN SYSTEM(444)=1 and its use, therefore, is not recommended.
Also replication is not at all currently supported with SimX reading a user-generated input file and strange
models may be displayed.
1. Duplication of fields from the preceding entry is accomplished by coding the symbol =.
2. Duplication of all trailing fields from the preceding entry is accomplished by coding the symbol ==.
3. Incrementing a value from the previous entry is indicated by coding *x or *(x), where x is the value
of the increment. “x” should be a real number for real fields or an integer for integer fields.
4. Repeated replication is indicated by coding =n or =(n), where n is the number of images to be
generated using the values of the increments on the preceding entry.
5. Data items may be enclosed with parentheses or the parentheses may be deleted.
6. Replication capabilities are described here by example:
• Continuation entry fields may be incremented or decremented.
• Repeated replication is indicated by coding =(n) in field 1, where n is number of entry images to
be generated using the values of increments from the current or preceding replication entry.
Entered entries:
GRID, 101, 17, 1 .0, 10.5,,17,3456
= , *1, =, *0.2, ==
=3
Generated entries:
GRID 101 17 1.0 10.5 17 3456
GRID 102 17 1.2 10.5 17 3456
GRID 103 17 1.4 10.5 17 3456
GRID 104 17 1.6 10.5 17 3456
GRID 105 17 1.8 10.5 17 3456
• A blank in field 1 indicates immediate continuation entry replication. The default continuation
entry increment is 1. Example:
BSET1,123,1,2,3,4,5,6,7
,,*7,*7,*7,*7,*7,*7,*7
=(3)
Generated entries:
Main Index
Chapter 9: Bulk Data Entries 1023
Bulk Data Entry Descriptions
BSET1 123 1 2 3 4 5 6 7 +00001
++00001 8 9 10 11 12 13 14 +00002
++00002 15 16 17 18 19 20 21 +00003
++00003 22 23 24 25 26 27 28 +00004
++00004 29 30 31 32 33 34 35 +00005
• A “=(D)” in field 1 indicates delayed continuation entry replication. A maximum of 9 entries may
be replicated as a group. The default continuation entry increment is 10. Example:
Entered entries:
CTRIA3,10,1,1,10,11/+C1
=(D),*(1),=,=,*(1),*(1)/*(20)
+C1,,,2.0,1.0,1.0
=(2),==
Generated entries:
CTRIA3 10 1 1 10 11 +C1
+C1 2.0 1.0 1.0
CTRIA3 11 1 1 11 12 +C21
+C21 2.0 1.0 1.0
CTRIA3 12 1 1 12 13 +C41
+C41 2.0 1.0 1.0
• Parentheses are optional on replication entries and an equal sign may replace an asterisk.
The following is an example of the use of replication, automatic continuation field generation,
and the free field format:
GRID, 101, 17, 1.0, 10.5,,17,3456
=,*1,=,*0.2, *(0.1), == $ COMMENTS MAY APPEAR AFTER $
=3
EIGR,13,GIV,,30.
,MASS
CBAR,1 ,1 ,101 ,102,0.,0.,1.,,+0
=,*1,=,*1,*1====*1
+0,56
*1,=$
The above free-field entries will generate the following Bulk Data in the 8-column format, as seen
in the SORTED BULK DATA ECHO:
Note: A “,” should always be used after the “*1” for the continuation increment even if fixed field
format is being used.
CBAR 1 1 101 102 0. 0. 1. +0
+0 56
Main Index
1024 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
CBAR 2 1 102 103 0. 0. 1. +1
+1 56
EIGR 13 GIV 30. +000001
++000001 MASS
GRID 101 17 1.0 10.5 17 3456
GRID 102 17 1.2 10.6 17 3456
GRID 103 17 1.4 10.7 17 3456
GRID 104 17 1.6 10.8 17 3456
GRID 105 17 1.8 10.9 17 3456
The automatically generated continuation entries start with the number 1, are incremented by 1, and are
padded with zeros and plus signs as shown above. If this feature is used, it is the user’s responsibility not to
enter continuation entries that also use this convention. In particular, data generated on another run and then
written to the PUNCH file with the ECHO=PUNCH, will cause problems when introduced into other data
with blank continuation fields.
Identifiers
MSC Nastran is designed to use Identifiers for many quantities, the most common include:
ID Grid Identification number
EID Element Identification number
PID Property Identification number
MID Material Identification number
CID Coordinate System number
When these identifications are given they must be unique in their class. All IDs defined on GRID, GRIDB,
GRIDF, GRIDS, POINT, SPOINT and EPOINT must be unique.
In the case of Element Identification (EID), elements are generally given by "C" entries, such as CBAR,
CBEAM, CQUAD, CHEXA, but rigid elements such as RBAR, RBE1, RBE2 are also treated as elements
with respect to the EID, and should also be part of this class. All EID must be unique.
All Identification numbers must be greater than zero ( example EID > 0)
Furthermore Element Identification and Grid Identification must be less than 100,000,000 to insure data
integrity.
There are two types of Property entries, primary ones and secondary ones. The property id on the primary
property entries must be unique.
Main Index
Chapter 9: Bulk Data Entries 1025
Bulk Data Entry Descriptions
Referenced by Primary Property Names
CHBDYP BDYOR
CHBDYG BDYOR
CHBDYE BDYOR
CAABSF PAABSF
CACINF3 PACINF
CACINF4 PACINF
CAERO1 PAERO1
CAERO2 PAERO2
CAERO3 PAERO3
CAERO4 PAERO4
CAERO5 PAERO5
CAXISYM PAXISYM
CBAR PBAR,PBARL, PBRSECT
CBEAM PBEAM, PBCOMP, PBEAML, PBMSECT,PDISCR,
PBMARB6,PMMNUM6
CBEAM3 PBEAM3, PBMSECT
CBELT PBELTD
CBEND PBEND
CBUSH PBUSH, PBUSHT
CBUSH1D PBUSH1D
CBUSH2D PBUSH2D
CCONEAX PCONEAX
CDAMP1 PDAMP
CDAMP1D PDAMP
CDAMP3 PDAMP
CDAMP5 PDAMP5
CDUMi PDUMi
CELAS1 PELAS1
CELAS1D PELAS1
CELAS3 PELAS
CFAST PFAST
CGAP PGAP
Main Index
1026 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Referenced by Primary Property Names
CHACAB PACABS
CHACBR PACBAR
CHBDYP PHBDY
CHEXA PSOLID, PLSOLID, PCOMPLS
CIFHEX PCOHE
CIFPENT PCOHE
CIFQDT PCOHE
CIFQUAD PCOHE
CMARKB2 PMARKER
CMARKN1 PMARKER
CMASS1 PMASS
CMASS3 PMASS
CMREBAI PMREBAI
CMREBAR PMREBAR
CONSPOT PBSPOT
CPENTA PSOLID, PLSOLID
CQUAD PLPLANE,PLCOMP
CQUAD4 PSHELL,PCOMP,PCOMPG, PLPLANE,PSHELL1,PSHELLD,PLCOMP
CQUAD8 PSHELL,PCOMP,PCOMPG,PLPLANE,PLCOMP
CQUADR PSHELL,PCOMP,PCOMPG,PLPLANE
CQUADX PAXSYMH, PLPLANE,PLCOMP
CRAC2D PRAC2D
CRAC3D PRAC3D
CROD PROD,PBELTD
CSEAM PSEAM
CSHEAR PSHEAR
CSPH PSPH
CSPR PSPRMAT
CSSHL PSSHL
CSSHLH PSSHL
CSSHLP PSSHL
CTETRA PSOLID, PLSOLID
CTQUAD PTSHELL
Main Index
Chapter 9: Bulk Data Entries 1027
Bulk Data Entry Descriptions
Referenced by Primary Property Names
CTRIA3 PSHELL,PCOMP,PCOMPG, PLPLANE, PSHELL1
CTRIA6 PSHELL,PCOMP,PCOMPG,PLPLANE
CTRIAR PSHELL,PCOMP,PCOMPG, PLPLANE
CTRIAX PAXSYMH
CTTRIA PTSHELL
CTUBE PTUBE
CVISC PVISC
CWELD PWELD
The secondary Property entries use the same property id as the primary property id. The relationship between
these two is shown below.
Primary Secondary
PSOLID PSLDN1
PLPLANE PSHLN2
PCOMP PCOMPA
PBAR PBARN1
PBEAM PBEAM71
PBEAM PBEMN1
PBEAML PBEMN1
PCOMP PCOMPF
PCOMPG PCOMPF
PDAMP PDAMPT
PELAS PELAST
PROD PROND1
PSHEAR PSHEARN
PSHELL PSHLN1
PCOMP PSHLN1
PDISTB PBAR, PBEAM, PBEAM3, PCOMP, PCOMPG,
PROD, PSHEAR, PSHELL, PSOLID and PTUBE
PDISTBM PBAR, PBEAM, PBEAM3, PCOMP, PCOMPG,
PROD, PSHEAR, PSHELL, PSOLID, and PTUBE
Main Index
1028 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
There are two types of Material entries, primary ones and secondary ones. The material id on the primary
material entries must be unique. The material id on the secondary Material entry must agree with the material
id on the associated primary Material entry. The correlation between primary and secondary Material entries
is given below.
Material
Model Primary Secondary
Isotropic MAT1 MATT1 MATS1 MATVP MATEP MATTEP MATF MATTF MATF1 MATFTG MATVE MATTV
E
MAT1F
Shell MAT2 MATT2 MATVP MATEP MATTEP MATF MATTF
Anisotropic
MAT2F
Planar MAT3 MATT3 MATS3 MATVP MATEP MATTEP MATF MATTF
Orthotropic
Hypoelastic MATUSR MATTUSR
User Sub.
General MATORT MATTORT MATSORT MATF MATTF
Orthotropic
Shell MAT8 MATT8 MATS8 MATF MATTF
Orthotropic
MAT8F
General MAT9 MATT9
Anisotropic
MAT9F
Geneal MATHE MATTHE MATVE MATTV
Hyperelastic E
Gasket MATG MATTG
5th order MATHP
Mooney-
Rivlin
Advanced MATNLE
NLELAST
Shape Memory MATSMA
Isotropic MATPE1
Poroelastic
CZM Material MCOHE
SOL 400
NLELAST MATNLE
2D/3D MATCB
Progressive
Failure
Digimat MATDIGI
Composite
Isotropic Heat MAT4 MATT4
Transfer
Anisotropic MAT5 MATT5
Heat Transfer
Fluid MAT10 MAT10F
Main Index
Chapter 9: Bulk Data Entries 1029
Bulk Data Entry Descriptions
Bulk Data Entry Summary
This section contains a summary of all Bulk Data entries. The entries are categorized as Geometry, Elements,
Material Properties, Constraints, Loads, Solution Control, and Miscellaneous. Entries that are exclusive to
Explicit Nonlinear analysis (SOL 700) have also been grouped together at the end of the summary.
Constraints and Partitioning
Component Mode Boundary Conditions
BNDFIX Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized
dynamic reduction or component mode synthesis calculations.
BNDFIX1 Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized
dynamic reduction or component mode synthesis calculations.
BNDFREE Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during generalized
dynamic reduction or component modes calculations.
BNDFRE1 Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during generalized
dynamic reduction or component modes calculations.
BSET Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during component mode
synthesis calculations.
BSET1 Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during component mode
synthesis calculations.
CSET Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during component modes
calculations.
CSET1 Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during component modes
calculations.
QSET Defines generalized degrees-of-freedom (q-set) to be used for component mode synthesis.
QSET1 Defines generalized degrees-of-freedom (q-set) to be used for component mode synthesis.
SEBSET Defines boundary degrees-of-freedom to be fixed (b-set) during component mode
synthesis calculations.
SEBSET1 Defines boundary degrees-of-freedom to be fixed (b-set) during component mode
synthesis calculations.
SECSET Defines boundary degrees-of-freedom to be free (c-set) during component mode
synthesis calculations.
SECSET1 Defines boundary degrees-of-freedom to be free (c-set) during component mode
synthesis calculations.
SENQSET Defines number of internally generated scalar points for superelement dynamic
reduction.
SEQSET Defines the generalized degrees-of-freedom of the superelement to be used in component
mode synthesis.
Main Index
1030 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
SEQSET1 Defines the generalized degrees-of-freedom of the superelement to be used in component
mode synthesis.
SESUP Defines determinate reaction superelement degrees-of-freedom in a free-body analysis.
Free Body Supports
CYSUP Defines fictitious supports for cyclic symmetry analysis.
SUPAX Defines determinate reaction degrees-of-freedom in free bodies for conical shell analysis.
SUPORTi Defines degrees-of-freedom for determinate reactions.
Multipoint Constraints
MPC Defines a linear relationship for two or more degrees-of-freedom.
MPCADD Defines a multipoint constraint set as a union of multipoint constraint sets defined via
MPC entries.
MPCD Defines a load selectable value for nonhomogeneous multi-point constraint.
MPCY Defines a linear nonhomogeneous relationship for two or more degrees-of-freedom.
MPCAX Defines multipoint constraints for conical shell problems.
POINTAX Defines multipoint constraints for point on conical shell.
RBAR Defines multipoint constraints for rigid bar.
RBEi Defines multipoint constraints for RBE1, RBE2, RBE3.
RROD Defines multipoint constraints for rigid rod.
RSPLINE Defines multipoint constraints for spline element.
RTRPLT Defines multipoint constraints for rigid triangular plate.
Partitioning
ASET Defines degrees-of-freedom in the analysis set (a-set).
ASET1 Defines degrees-of-freedom in the analysis set (a-set).
CSUPEXT Assigns exterior points to a superelement.
GRID Defines interior points for a superelement.
OMIT Defines degrees-of-freedom to be excluded (o-set) from the analysis set (a-set).
OMIT1 Defines degrees-of-freedom to be excluded (o-set) from the analysis set (a-set).
OMITAX Defines degrees-of-freedom to be excluded (o-set) from the analysis set (a-set).
RELEASE Defines degrees-of-freedom for superelement exterior grid points that are not connected
to the superelement.
SEELT Reassigns superelement boundary elements to an upstream superelement.
SESET Defines interior grid points for a superelement.
Main Index
Chapter 9: Bulk Data Entries 1031
Bulk Data Entry Descriptions
Single Point Constraints
FLSYM Symmetry control for boundary in axisymmetric fluid problem.
GRID Includes single point constraint definition.
GRIDB Includes single point constraint definition.
GRDSET Includes default for single point constraints.
SPC Defines a set of single-point constraints and enforced motion (enforced displacements in
static analysis and enforced displacements, velocities or acceleration in dynamic analysis).
SPC1 Defines a set of single point constraints.
SPCADD Defines a single-point constraint set as a union of single-point constraint sets defined on
SPC or SPC1 entries.
SPCAX Defines a set of single-point constraints or enforced displacements for conical shell
coordinates.
SPCOFF Defines degrees-of-freedom to be excluded from the AUTOSPC operation.
SPCOFF1 Defines a set of degrees-of-freedom to be excluded from the AUTOSPC operation.
User Sets
DEFUSET Defines new names for degree-of-freedom sets.
SEUSET Defines a degree-of-freedom set for a superelement.
SEUSET1 Defines a degree-of-freedom set for a superelement.
USET Defines a degree-of-freedom set.
USET1 Defines a degrees-of-freedom set.
Elements
A summary of the capabilities and characteristics of the small strain elements is available in Element Summary
-- Conventional MSC Nastran Elements in the MSC Nastran Reference Guide.
Aerodynamic Elements
AEFACT Defines real numbers for aeroelastic analysis.
AELINK Defines relationships between or among AESTAT and AESURF entries.
AELIST Defines a list of aerodynamic elements to undergo the motion prescribed with the
AESURF Bulk Data entry for static aeroelasticity. Also defines server specific integer data
for external spline methods.
AEQUAD4 Defines the connectivity of a quadrilateral aerodynamic element.
AESTAT Specifies rigid body motions to be used as trim variables in static aeroelasticity.
AESURF Specifies an aerodynamic control surface as a member of the set of aerodynamic extra
points.
Main Index
1032 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
AESURFS Optional specification of the structural nodes associated with an aerodynamic control
surface that has been defined on an AESURF entry.
AETRIA3 Defines the connectivity of a triangular aerodynamic element.
CAERO1 Defines an aerodynamic macro element (panel) in terms of two leading edge locations
and side chords.
CAERO2 Defines aerodynamic slender body and interference elements for Doublet-Lattice
aerodynamics.
CAERO3 Defines the aerodynamic edges of a Mach Box lifting surface. If no cranks are present,
this entry defines the aerodynamic Mach Box lifting surface.
CAERO4 Defines an aerodynamic macro element for Strip theory.
CAERO5 Defines an aerodynamic macro element for Piston theory.
CSSCHD Defines a scheduled control surface deflection as a function of Mach number and angle
of attack.
PAERO1 Defines associated bodies for the panels in the Doublet-Lattice method.
PAERO2 Defines the cross-sectional properties of aerodynamic bodies.
PAERO3 Defines the number of Mach boxes in the flow direction and the location of cranks and
control surfaces of a Mach box lifting surface.
PAERO4 Defines properties of each strip element for Strip theory.
PAERO5 Defines properties of each strip element for Piston theory.
Aerodynamic to Structure Interconnection
AELISTC Defines a list of 8-character strings.
SET1 Defines a list of structural grid points.
SET2 Defines a list of structural grid points in terms of aerodynamic macro elements.
SET3 Defines a list of grids, elements or points.
SPBLND1 Defines a strip based blending of two splines.
SPBLND2 Defines a curve based blending of two splines.
SPLINE1 Defines a surface spline for interpolating motion and/or forces for aeroelastic problems
on aerodynamic geometries defined by regular arrays of aerodynamic points.
SPLINE2 Defines a beam spline for interpolating motion and/or forces for aeroelastic problems on
aerodynamic geometries defined by regular arrays of aerodynamic points.
SPLINE3 Defines a constraint equation for aeroelastic problems. Useful for control surface
constraints.
SPLINE4 Defines a curved surface spline for interpolating motion and/or forces for aeroelastic
problems on general aerodynamic geometries using either the Infinite Plate, Thin Plate
or Finite Plate splining method.
Main Index
Chapter 9: Bulk Data Entries 1033
Bulk Data Entry Descriptions
SPLINE5 Defines a 1D beam spline for interpolating motion and/or forces for aeroelastic problems
on aerodynamic geometries defined by irregular arrays of aerodynamic points.
SPLINE6 Defines a 6DOF or 3DOF finite surface spline for interpolating motion and/or forces
between two meshes.
SPLINE7 Defines a 6DOF finite beam spline for interpolating motion and/or forces between two
meshes.
SPLINEX Defines the input for a spline that will be evaluated with a user-supplied procedure.
SPLINRB Defines a rigid body spline for interpolating motion or forces for aeroelastic problems on
general aerodynamic geometries.
SPRELAX Defines relaxation of a spline based on an adjacent spline.
Axisymmetric Elements
CAXISYM Defines an axisymmetric shell.
CCONEAX Defines a conical shell element.
CQUADX Defines an axisymmetric quadrilateral element with up to nine grid points for use in fully
nonlinear (i.e., large strain and large rotations) hyperelastic analysis.
CTRIAX Defines an axisymmetric triangular element with up to 6 grid points for use in fully
nonlinear (i.e., large strain and large rotations) hyperelastic analysis.
CTRIAX6 Defines an isoparametric and axisymmetric triangular cross section ring element with
midside grid points.
PCONEAX Defines the properties of a conical shell element described on a CCONEAX entry.
Cohesive Zone Modeling Elements
CIFHEX Defines a solid interface cohesive zone modeling element in SOL 400.
CIFPENT Defines a solid interface cohesive zone modeling element in SOL 400.
CIFQDX Defines an axisymmetric interface cohesive zone modeling element in SOL 400.
CIFQUAD Defines a planar interface element for cohesive zone modeling element in SOL 400.
MCOHE Defines damage and cohesive energy for interface zone modeling elements in SOL 400.
PCOHE Defines the properties of a cohesive interface zone modeling elements in SOL 400.
Connector Elements
CFAST Defines a fastener with material orientation connecting two surface patches.
CSEAM Defines a seam-line connecting two surfaces.
CSLOT3 Defines an element connecting three points that solve the wave equation in two
dimensions.
CSLOT4 Defines an element connecting four points that solve the wave equation in two
dimensions.
Main Index
1034 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
CWELD Defines a weld or fastener connecting two surface patches or points.
PFAST Defines the CFAST fastener property values.
PSEAM Defines the CSEAM fastener property values.
PWELD Defines the property of connector (CWELD) elements.
SWLDPRM Overrides default values of parameters for connector search.
Slidelines Contact (SOL 106, 129)
BCONP Defines the parameters for a contact region and its properties.
BFRlC Defines frictional properties between two bodies in contact.
BLSEG Defines a curve that consists of a number of line segments via grid numbers that may
come in contact with another body.
BWIDTH Defines widths or thicknesses for line segments in 3-D or 2-D slideline contact defined
in the corresponding BLSEG Bulk Data entry.
Gap Elements
CGAP Defines a gap or friction element.
PGAP Defines the properties of the gap element (CGAP entry).
Crack Tip Elements
CRAC2D Defines a two-dimensional crack tip element.
CRAC3D Defines a three-dimensional crack tip element.
PRAC2D Defines the properties and stress evaluation techniques to be used with the CRAC2D
structural element.
PRAC3D Defines the properties of the CRAC3D structural element.
VCCT Virtual Crack Closure Technique
Damping Elements
CBUSH1D See line elements.
CDAMP1 Defines a scalar damper element.
CVISC Defines a viscous damper element.
DAMPING Specifies the values for parameter damping and/or selects optional HYBRID damping.
HYBDAMP Specifies hybrid damping parameters.
PBUSH1D See line elements.
PDAMP Specifies the damping value of a scalar damper element using defined CDAMP1 or
CDAMP3 entries.
Main Index
Chapter 9: Bulk Data Entries 1035
Bulk Data Entry Descriptions
PDAMP5 Defines the damping multiplier and references the material properties for damping.
CDAMP5 is intended for heat transfer analysis only.
PDAMPT Defines the frequency-dependent properties for a PDAMP Bulk Data entry.
PVISC Defines properties of a one-dimensional viscous damping element (CVISC entry).
ROTHYBD Defines Hybrid damping for rotordynamics.
Dummy Elements
ADUMi Defines attributes of the dummy elements (1 < i < 9)
CDUMi Defines a dummy element (1 < i < 9)
PDUMi Defines the properties of a dummy element (1 < i < 9). Referenced by the CDUMi
entry.
PLOTEL Defines a one-dimensional dummy element for use in plotting.
Fluid and Acoustic Elements
CAABSF Defines a frequency-dependent acoustic absorber element in coupled fluid-structural
analysis.
CACINFi Defines few types of acoustic infinite elements.
CAXIFi Defines an axisymmetric fluid element that connects i = 2, 3, or 4 fluid points.
CAXISYM Defines two or three node axisymmetric thick shell elements.
CFLUIDi Defines three types of fluid elements for an axisymmetric fluid model.
CHACAB Defines the acoustic absorber element in coupled fluid-structural analysis.
CHACBR Defines the acoustic barrier element.
CHEXA Connection definition for a pentahedron element in coupled fluid-structural analysis.
CPENTA Connection definition for a tetrahedron element in coupled fluid-structural analysis.
CSLOTi Defines slot element for acoustic cavity analysis.
CTETRA Defines the connections of the four-sided solid element with four to ten grid points.
ELIST Defines a list of structural elements for virtual fluid mass.
MAT10 Fluid Material Property Definition.
PAABSF Defines the properties of a frequency-dependent acoustic absorber element.
PACABS Defines the properties of the acoustic absorber element.
PACBAR Defines the properties of the acoustic barrier element.
PACINF Defines the properties of acoustic infinite elements.
PANEL Selects the set of structural grid points that define one or more panels.
Main Index
1036 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
PSOLID Defines the fluid properties of solid elements (CHEXA, CPENTA, and CTETRA
entries).
SET1 Defines a list of structural grid points for aerodynamic analysis, XY-plots for SORT1
output, and the PANEL entry.
Equivalent Radiated Power
ERPPNL Equivalent Radiated Power Definition
Poroelasticity (PEM)
ACTRIM ACTRAN Trimmed Material Matrices for SOL 108/111
ACLOAD ACTRAN Acoustic Pressure Load Matrices for SOL 108/111
MATPE1 Isotropic Poroelastic Material Property definition
MATF1 Frequency Dependent Isotropic Material Definition
Heat Transfer Elements
BDYOR Defines default values for the CHBDYP, CHBDYG, and CHBDYE entries.
CHBDYi Connection definition for surface element (CHBDYE, CHBDYG, CHBDYP).
CONTRLT Thermal control element for heat transfer analysis.
PHBDY A property entry referenced by CHBDYP entries to give auxiliary geometric information
for boundary condition surface elements.
The PRODN1, PSHLN1, PSHLN2, PSLDN1, PSHEARN, PLCOMP, and PCOMPLS may be used to
extend the nonlinear capabilities of heat transfer elements in SOL 400. PCOMPLS may also be used to
extend the nonlinear capabilities of heat transfer elements in all linear solutions between SOL101 and
SOL112.
The following elastic elements may also be used as heat conduction elements:
Linear: CBAR, CROD, CONROD, CTUBE, CBEAM, CBEND.
Membrane: CTRIA3, CTRIA6, CQUAD4, CQUAD8.
Axisymmetric: CTRIAX6.
Solid: CTETRA, CHEXA, CPENTA.
Line Elements
BAROR Default for orientation and property for CBAR.
BEAMOR Defines default vlaues for field 3 and fields 6 through 8 of the CBEAM entry.
CBAR Defines a simple beam element.
CBEAM Defines a beam element.
Main Index
Chapter 9: Bulk Data Entries 1037
Bulk Data Entry Descriptions
CBEAM3 Defines a three-node beam element.
CBEND Defines a curved beam, curved pipe, or elbow element.
CBUSH1D Defines the connectivity of a one-dimensional spring and viscous damper element.
CFAST Defines a fastener with material orientation connecting two surface patches.
CINTC Defines a line interface element with specified boundaries.
CONROD Defines a rod element without reference to a property entry.
CROD Defines a tension-compression-torsion element.
CTUBE Defines a tension-compression-torsion tube element.
CWELD Defines a weld or fastener connecting two surface patches or points.
PBAR Defines the properties of a simple beam element (CBAR entry).
PBARL Defines the properties of a simple beam element (CBAR entry) by cross-sectional
dimensions.
PBARN1 Specifies additional nonlinear properties for elements that point to a PBAR or PBARL
entry.
PBCOMP Alternate form of the PBEAM entry to define properties of a uniform cross-sectional
beam referenced by a CBEAM entry.
PBEAM Defines the properties of a beam element (CBEAM entry). This element may be used to
model tapered beams.
PBEAM3 Defines the properties of a three-node beam element (CBEAM3 entry).
PBEAML Defines the properties of a beam element by cross-sectional dimensions.
PBEMN1 Specifies additional nonlinear properties for elements that point to a PBEAM or
PBEAML entry.
PBEND Defines the properties of a curved beam, curved pipe, or elbow element (CBEND entry).
PFAST Defines the CFAST fastener property values.
PBMSECT Defines the shape of arbitrary cross-section for CBEAM element.
PBRSECT Defines the shape of arbitrary cross-section for CBAR element.
PBUSH1D Defines linear and nonlinear properties of a one-dimensional spring and damper element
(CBUSH1D entry).
PBUSH2D Defines linear and nonlinear properties of a two-dimensional element (CBUSH2D
entry).
PROD Defines the properties of a rod element (CROD entry).
PRODN1 Defines nonlinear property extensions for the PROD in SOL 400.
PTUBE Defines the properties of a thin-walled cylindrical tube element (CTUBE entry).
PWELD Defines the properties of connector (CWELD) elements.
Main Index
1038 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Mass Elements
CMASSi Connection definition for scalar mass, also property definition for i=2 or 4.
CONM1 Defines a 6 x 6 symmetric mass matrix at a geometric grid point.
CONM2 Defines concentrated mass at a grid point.
PMASS Specifies the mass value of a scalar mass element (CMASS1 or CMASS3 entries).
NSM Non Structural Mass by ID.
NSM1 Non Structural Mass (alternate form).
NSMADD Non Structural Mass Set Combination.
NSML Lumped Non Structural Mass by ID.
NSML1 Lumped Non Structural Mass (alternate form).
Rigid Elements
RBAR Defines a rigid bar with six degrees-of-freedom at each end.
RBAR1 Alternative format for RBAR.
RBE1 Defines a rigid body connected to an arbitrary number of grid points.
RBE2 Defines a rigid body with independent degrees-of-freedom that are specified at a single
grid point and with dependent degrees-of-freedom that are specified at an arbitrary
number of grid points.
RBE3 Defines the motion at a reference grid point as the weighted average of the motions at a
set of other grid points.
RJOINT Defines a rigid joint element connecting two coinciding grid points.
RROD Defines a pin-ended element that is rigid in translation.
RSPLINE Defines multipoint constraints for the interpolation of displacements at grid points.
RSSCON Defines multipoint constraints to model clamped connections of shell-to-solid elements.
RTRPLT Defines a rigid triangular plate.
RTRPLT1 Defines a rigid triangular plate (alternate).
Scalar and Bushing Elements
CBUSH Defines a generalized spring-and-damper structural element that may be nonlinear or
frequency dependent.
CBUSH1D Defines the connectivity of a one-dimensional spring and viscous damper element.
CBUSH2D Defines the connectivity of a two-dimensional Linear-Nonlinear element.
CELASi Connection definition for scalar spring, also property definition for i=2 or 4.
GENEL Defines a general element.
PBUSH Defines the nominal property values for a generalized spring-and-damper structural
element.
Main Index
Chapter 9: Bulk Data Entries 1039
Bulk Data Entry Descriptions
PBUSHT Defines the frequency dependent properties or the stress dependent properties for a
generalized spring and damper structural element.
PBUSH1D Defines linear and nonlinear properties of a one-dimensional spring and damper element
(CBUSH1D entry).
PELAS Specifies the stiffness, damping coefficient, and stress coefficient of a scalar elastic (spring)
element (CELAS1 or CELAS3 entry).
PELAST Defines the frequency dependent properties for a PELAS Bulk Data entry.
Solid Elements
CHEXA Defines the connections of the six-sided solid element with eight to twenty grid points.
CPENTA Defines the connections of a five-sided solid element with six to fifteen grid points.
CTETRA Defines the connections of the four-sided solid element with four to ten grid points.
PCOMPLS Defines the linear/nonlinear properties of an n-ply composite material laminate for a
layered solid (CHEXA) element in SOL 400 and all linear solution sequences between
SOL101 and SOL112.
PLSOLID Defines a fully nonlinear (i.e., large strain and large rotation) hyperelastic solid element.
PSLDN1 Defines the nonlinear property extensions for a PSOLID entry in SOL 400.
PLSOLID Defines the properties of solid elements (CHEXA, CPENTA, and CTETRA entries).
Surface Elements
CQUAD Defines a plane strain quadrilateral element with up to nine grid points for use in fully
nonlinear (i.e., large strain and large rotation) hyperelastic analysis.
CQUAD4 Defines an isoparametric membrane-bending or plane strain quadrilateral plate element.
CQUAD8 Defines a curved quadrilateral shell or plane strain element with eight grid points.
CQUADR Defines an isoparametric membrane and bending quadrilateral plate element.
CSHEAR Defines the properties of a shear panel (CSHEAR entry).
CTRIA3 Defines an isoparametric membrane-bending or plane strain triangular plate element.
CTRIA6 Defines a curved triangular shell element or plane strain with six grid points.
CTRIAR Defines an isoparametric membrane-bending triangular plate element. However, this
element does not include membrane-bending coupling. It is a companion to the
CQUADR element.
PCOMP Defines the properties of an n-ply composite material laminate.
PCOMPF Defines the integration procedure for through the thickness integration of composite
shells. (SOL 400)
PCOMPG Defines global (external) ply IDs and properties for a composite material laminate.
PLCOMP Defines the linear/nonlinear properties of an n-ply composite material laminate of a plane
stress, plane strain, or axisymmetric (CQUAD or CQUADX entry) element in SOL 400.
Main Index
1040 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
PLPLANE Defines the properties of a fully nonlinear (i.e., large strain and large rotation) hyperelastic
plane strain or axisymmetric element.
PSHELL Defines the membrane, bending, transverse shear, and coupling properties of thin shell
elements.
PSHLN1 Defines nonlinear property extensions for a PSHELL or PCOMP or PCOMPG entry in
SOL 400.
PSHLN2 Defines nonlinear property extensions for a PLPLANE entry in SOL 400.
PSHEAR Defines the properties of a shear panel (CSHEAR entry).
PSHEARN Defines nonlinear property extensions for a PSHEAR in SOL 400.
SNORM Defines a surface normal vector at a grid point for CQUAD4, CQUADR, CTRIA3, and
CTRIAR shell elements.
Geometry
Adaptive Meshing
HADACRI Specifies Mesh adaptivity criterion and corresponding parameters.
HADAPTL Specifies local adaptive Mesh refinement control parameters.
Axisymmetry
AXIC Defines the existence of an axisymmetric conical shell problem.
AXIF Defines basic parameters and the existence of an axisymmetric fluid analysis.
AXSLOT Defines the harmonic index and the default values for acoustic analysis entries.
FLSYM Defines the relationship between the axisymmetric fluid and a structural boundary having
symmetric constraints. The purpose is to allow fluid boundary matrices to conform to
structural symmetry definitions.
POINTAX Defines the location of a point on an axisymmetric shell ring at which loads may be applied
via the FORCE or MOMENT entries and at which displacements may be requested. These
points are not subject to constraints via MPCAX, SPCAX, or OMITAX entries.
RINGAX Defines a ring for conical shell problem.
SECTAX Defines a sector of a conical shell.
Coordinate Systems
BAROR Defines default values for field 3 and fields 6 through 8 of the CBAR entry.
BEAMOR Defines default values for field 3 and fields 6 through 8 of the CBEAM entry.
CORD1C Cylindrical coordinate system definition.
CORD1R Rectangular coordinate system definition.
Main Index
Chapter 9: Bulk Data Entries 1041
Bulk Data Entry Descriptions
CORD1S Spherical coordinate system definition.
CORD3G Defines a general coordinate system using three rotational angles as functions of coordinate
values in the reference coordinate system.
Cyclic Symmetry
CYAX Lists grid points that lie on the axis of symmetry in cyclic symmetry analysis.
CYJOIN Defines the boundary points of a segment in cyclic symmetry problems.
Fluid Points
ACMODL Defines modeling parameters for the Fluid-Structure Interface.
FREEPT Defines the location of points on the surface of a fluid for recovery of surface displacements
in a gravity field.
FSLIST Defines the fluid points (RINGFL entry) that lie on a free surface boundary.
GRID Defines fluid points in coupled fluid-structural analysis.
GRIDB Grid point location on RINGFL.
GRIDF Defines a scalar degree-of-freedom for harmonic analysis of a fluid.
GRIDS Defines a scalar degree-of-freedom with a two-dimensional location. Used in defining
pressure in slotted acoustic cavities.
PRESPT Defines the location of pressure points in the fluid for recovery of pressure data.
RINGFL Defines a circle (fluid point) in an axisymmetric fluid model.
SLBDY Defines a list of slot points that lie on an interface between an axisymmetric fluid and a set
of evenly spaced radial slots.
Geometric Points and Spline Grids
GMBNDC Defines a geometric boundary consisting of edges along a curve interface. The boundary
may consist of edges of shell, beam, solid elements
POINT Defines the X, Y, Z coordinates of a geometric point (See PBMSECT)
Grid Points
AEGRID Defines the location of an aerodynamic grid point.
GRID Defines the location of a geometric grid point, the directions of its displacement, and its
permanent single-point constraints.
GRIDB Defines the location of a geometric grid point on a fluid point (RINGFL entry) for an
axisymmetric fluid model and/or axisymmetric structure. Also defines the boundary of the
fluid.
Main Index
1042 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
GRDSET Defines default options for fields 3, 7, 8, and 9 of all GRID entries.
SEQGP Used to manually order the grid points and scalar points of the problem. This entry is used
to redefine the sequence of grid and scalar points to optimize bandwidth.
Scalar Points
EPOINT Defines extra points for use in dynamic problems.
SEQGP Grid and scalar point number resequencing.
SPOINT Defines scalar points.
Superelement Analysis
CSUPER Defines the grid or scalar point connections for identical or mirror image superelements or
superelements from an external source. These are all known as secondary superelements.
CSUPEXT Assigns exterior points to a superelement.
EXTRN Defines a boundary connection for an external superelement.
GRID Defines interior points for a superelement.
RELEASE Defines degrees-of-freedom for superelement exterior grid points that are not connected to
the superelement.
SEBNDRY Defines a list of grid points in a partitioned superelement for the automatic boundary search
between a specified superelement or between all other superelements in the model.
SEBULK Defines superelement boundary search options and a repeated, mirrored, or collector
superelement.
SECONCT Explicitly defines grid and scalar point connection procedures for a partitioned
superelement.
SEDLINK Relates one design variable of a PART SE to one or more other design variables from other
PART SEs.
SEDRSP2 Defines equation responses that are used in the design, either as constraints or as an
objective with quantities from multiple PART SEs.
SEDRSP3 Defines constituents from multiple PART SE for an external response using user-supplied
routine(s).
SEELT Reassigns superelement boundary elements to an upstream superelement.
SEEXCLD Defines grid points that will be excluded during the attachment of a partitioned
superelement.
SELABEL Defines a label or name to be printed in the superelement output headings.
SELOAD Selects and/or scales external superelement loads
SELOC Defines a partitioned superelement relocation by listing three noncolinear points in the
superelement and three corresponding points not belonging to the superelement.
SEMPLN Defines a mirror plane for mirroring a partitioned superelement.
Main Index
Chapter 9: Bulk Data Entries 1043
Bulk Data Entry Descriptions
SEQSEP Used with the CSUPER entry to define the correspondence of the exterior grid points
between an identical or mirror-image superelement and its primary superelement.
SESET Defines interior grid points for a superelement.
SETREE Specifies superelement reduction order.
Main Index
1044 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Module Analysis
EXCLUDE Specifies Bulk Data entries in the primary Module to be ignored in the secondary (or
copied) Module.
MDBCATP Defines Parameters of Across Modules for Automatic Contact Generation
MDBCNCT Defines the Touching and Touched Contact Bodies in Different Modules.
MDBCPAR Defines Candidates Modules for Automatic Contact Detection Across Modules
MDBCTB1 Defines a Contact Table for Bodies in Different Modules.
MDBKSYS Defines Brake System for Modules
MDBNDRY Module to Module Boundary Point Definitions.
MDBOLT Defines the Multi-Point Constraints for a Bolt Between Two Modules.
MDBULK Module Type Definitions.
MDBUSH Generalized Spring and Damper Connection between Modules.
MDCONCT Module Boundary Point Connections.
MDDMIG Direct Matrix Input at Points Defined in Two or More Modules.
MDEXCLD Module to Module Excluded Boundary Point Definitions.
MDFAST A Shell Patch Fastener Connection Between Two Modules.
MDFSET Set Definition for Fluid Elements or Grid Points in Modules.
MDLABEL Module Output Label.
MDLOC Module Reposition by Translation and/or Rotation.
MDMIR1 Defines a Module mirror by three non-collinear points on the mirror plane.
MDMIR2 Defines a Module mirror by specifying a pair of coordinate system axes on the mirror
plane.
MDMOVE Defines a Module repositioning sequence. References MDMIRi, MDROTi, and
MDTRAN entries.
MDMPC Multipoint Constraint Between Two or More Modules.
MDMPLN Module Reposition by Mirroring.
MDRBE2 Rigid Body Element Between Two or More Modules, Form 2.
MDRBE3 Interpolation Constraint Element Between Two or More Modules.
MDRJNT Rigid Joint Between Two Modules.
MDROT1 Defines a Module rotation by specifying a rotation vector and reference point.
MDROT2 Defines a Module rotation by specifying a coordinate system axis for the rotation vector.
MDRROD Rigid Pin-Ended Element Connection Between Two Modules.
MDSEAM A Shell Patch SEAM Connection Between Two Modules.
MDSSET Set Definition for Structural Elements or Grid Points in Modules.
Main Index
Chapter 9: Bulk Data Entries 1045
Bulk Data Entry Descriptions
MDTRAN Defines a Module translation by specifying a vector.
MDWELD Weld or Fastener Element Connection Between Two Modules.
Loads
Dynamic Loads
ACSRCE Defines acoustic source as a function of power vs. frequency.
DAREA Defines scale (area) factors for static and dynamic loads. In dynamic analysis, DAREA
is used in conjunction with RLOADi and TLOADi entries.
DELAY Defines the time delay term in the equations of the dynamic loading function.
DLOAD Defines a dynamic loading condition for frequency response or transient response
problems as a linear combination of load sets defined via RLOAD1 or RLOAD2 entries
for frequency response or TLOAD1 or TLOAD2 entries for transient response.
DPHASE Defines the phase lead term in the equation of the dynamic loading function.
LOADCYH Defines the harmonic coefficients of a static or dynamic load for use in cyclic symmetry
analysis.
LOADCYN Defines a physical static or dynamic load for use in cyclic symmetry analysis.
LSEQ Defines a sequence of static load sets.
NOLIN1 Nonlinear transient load definition.
NLRGAP Defines a nonlinear transient radial (circular) gap.
RLOAD1 Frequency dependent excitation definition.
TABLED1 Tabular functions for generating dynamic loads.
TLOAD1 Time dependent excitation definition.
Heat Transfer Loads
CONV Specifies a free convection boundary condition for heat transfer analysis through
connection to a surface element (CHBDYi entry).
CONVM Specifies a forced convection boundary condition for heat transfer analysis through
connection to a surface element (CHBDYi entry).
PCONV Specifies the free convection boundary condition properties of a boundary condition
surface element used for heat transfer analysis.
PCONVM Specifies the forced convection boundary condition properties of a boundary condition
surface element used for heat transfer analysis.
QBDY1 Defines a uniform heat flux into CHBDYj elements.
QBDY2 Defines grid point heat flux into CHBDYj elements.
Main Index
1046 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
QBDY3 Defines a uniform heat flux load for a boundary surface.
QHBDY Defines a uniform heat flux into a set of grid points.
QVECT Defines thermal vector flux from a distant source into a face of one or more CHBDYi
boundary condition surface elements.
QVOL Defines a rate of volumetric heat addition in a conduction element.
RADBC Specifies an CHBDYi element face for application of radiation boundary conditions.
RADBND Specifies Planck’s second radiation constant and the wavelength breakpoints used for
radiation exchange problems.
RADCAV Identifies the characteristics of each radiant enclosure.
RADLST Identifies the individual CHBDYi surface elements that comprise the entire radiation
enclosure.
RADMTX Provides the F ji = A j f ji exchange factors for all the faces of a radiation enclosure
specified in the corresponding RADLST entry.
RADSET Specifies which radiation cavities are to be included for radiation enclosure analysis.
SLOAD Defines concentrated static loads on scalar or grid points.
SLOADN1 Describes TOP/BOT/MID Scalar Load for Heat Shell Element in SOL 400
TEMP Defines temperature at grid points for determination of thermal loading,
temperature-dependent material properties, or stress recovery.
TEMPB3 Defines a temperature field for the three-node beam element (CBEAM3 entry).
TEMPBC Defines the temperature boundary conditions for heat transfer analysis. Applies to
steady-state and transient conditions.
TEMPD Specifies default initial temperature at grid points.
TEMPN1 TOP/BOT/MID Grid Point Temperature Field for Heat Shell Element in SOL 400
VIEW Defines radiation cavity and shadowing for radiation view factor calculations.
VIEW3D Defines parameters to control and/or request the Gaussian Integration method of view
factor calculation for a specified cavity.
Static Loads
ACCEL Defines static acceleration loads, which may vary over a region of the structural model.
The load variation is based upon the tabular input defined on this Bulk Data entry.
ACCEL1 Defines static acceleration loads at individual GRID points.
CLOAD Defines a static load as a linear combination of previously calculated superelement loads
defined by the LSEQ entry in nonlinear static analysis (SOL 106 or 153).
DEFORM Defines enforced axial deformation for one-dimensional elements for use in statics
problems.
FORCE Defines a static concentrated force at a grid point by specifying a vector.
Main Index
Chapter 9: Bulk Data Entries 1047
Bulk Data Entry Descriptions
FORCE1 Defines a static concentrated force at a grid point by specification of a magnitude and
two grid points that determine the direction.
FORCE2 Defines a static concentrated force at a grid point by specification of a magnitude and
four grid points that determine the direction.
FORCEAX Defines a concentrated force on a conical shell ring.
FORCEi Defines concentrated load at grid point.
GRAV Defines acceleration vectors for gravity or other acceleration loading.
GRIDA Defines an associative GRID point to be used in the COMBINE step of PAA.
LOAD Defines a static load as a linear combination of load sets defined via FORCE,
MOMENT, FORCE1, MOMENT1, FORCE2, MOMENT2, PLOAD, PLOAD1,
PLOAD2, PLOAD4, PLOADB3, PLOADX1, SLOAD, RFORCE, and GRAV,
ACCEL and ACCEL1 entries.
LOADCLID Defines a loading combination in PAA using the Load ID from SUBCASEs of the Parts
LOADCNAM Used only in PAA to define a loading combination using the LOADNAMEs used in
Case Control for Parts
LOADCSUB Defines a loading combination in PAA using the SUBCASE IDs from the Parts
LOADCYH Defines the harmonic coefficients of a static or dynamic load for use in cyclic symmetry
analysis.
LOADCYN Defines a physical static or dynamic load for use in cyclic symmetry analysis.
LOADCYT Specifies loads as a function of azimuth angle by references to tables that define scale
factors of loads versus azimuth angles. This entry is used only when STYPE = “AXI” on
the CYSYM entry.
LSEQ Defines a sequence of static load sets.
MOMAX Defines a static concentrated moment load on a ring of a conical shell.
MOMENT Defines a static concentrated moment at a grid point by specifying a scale factor and a
vector that determines the direction.
MOMENTi Defines moment at grid point.
PLOAD Defines a uniform static pressure load on a triangular or quadrilateral surface comprised
of surface elements and/or the faces of solid elements.
PLOAD1 Defines concentrated, uniformly distributed, or linearly distributed applied loads to the
CBAR or CBEAM elements at user-chosen points along the axis. For the CBEND
element, only distributed loads over an entire length may be defined.
PLOAD2 Defines a uniform static pressure load applied to CQUAD4, CSHEAR, or CTRIA3
two-dimensional elements.
PLOAD4 Defines a pressure load on a face of a CHEXA, CPENTA, CTETRA, CTRIA3,
CTRIA6, CTRIAR, CQUAD4, CQUAD8, or CQUADR element.
PLOADB3 Defines a distributed load to a CBEAM3 element over entire length of the beam axis.
Main Index
1048 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
PLOADX1 Defines surface traction to be used with the CQUADX, CTRIAX, and CTRIAX6
axisymmetric element.
PRESAX Defines the static pressure loading on a conical shell element.
RFORCE Defines a static loading condition due to an angular velocity and/or acceleration.
SLOAD Defines concentrated static loads on scalar or grid points.
SPCD Defines an enforced displacement value for static analysis and an enforced motion value
(displacement, velocity or acceleration) in dynamic analysis.
SPCR Defines an enforced relative displacement value for a load step in SOL 400.
TEMP Defines temperature at grid points for determination of thermal loading,
temperature-dependent material properties, or stress recovery.
TEMPD Defines a temperature value for all grid points of the structural model that have not
been given a temperature on a TEMP entry.
TEMPP1 Defines temperature field for surface elements.
TEMPRB Defines a temperature field for the CBAR, CBEAM, CBEND, CROD, CTUBE, and
CONROD elements for determination of thermal loading, temperature-dependent
material properties, or stress recovery.
TEMPAX Defines temperature sets for conical shell problems.
Materials
Anisotropic
MAT2 Defines the material properties for linear anisotropic materials for two-dimensional
elements.
MAT3 Defines the material properties for linear orthotropic materials used by the CTRIAX6
element entry. It also is allowed with orthotropic materials on the PSHLN2 and
PLCOMP entries.
MAT5 Defines the thermal material properties for anisotropic materials.
MAT8 Defines the material property for an orthotropic material for isoparametric shell
elements.
MAT9 Defines the material properties for linear, temperature-independent, anisotropic
materials for solid isoparametric elements (see PSOLID entry description).
MATCB Define 2D/3D Orthotropic Material with Cuntze-Bold progressive failure (for SOL400
in conjunction with PCOMP(G) and PCOMPLS)
MATORT Define elastic 3D Orthotropic Material (SOL 400. Also all linear solutions between
SOL101 and 112 in conjunction with PCOMPLS.)
Fatigue
MATFTG Defines cyclic material properties (S-N + -N) for use in fatigue analysis.
Main Index
Chapter 9: Bulk Data Entries 1049
Bulk Data Entry Descriptions
Fluid
AXIF Includes default values for mass density and bulk modulus.
AXSLOT Includes default values for mass density and bulk modulus.
CFLUIDi Includes mass density and bulk modulus.
FSLIST Includes mass density at free surface.
MAT10 Defines material properties for fluid elements in coupled fluid-structural analysis.
MFLUID Defines the properties of an incompressible fluid volume for the purpose of generating a
virtual mass matrix.
SLBDY Includes mass density at interface between fluid and radial slots.
Isotropic
MAT1 Defines the material properties for linear isotropic materials.
MAT4 Defines the constant or temperature-dependent thermal material properties for
conductivity, heat capacity, density, dynamic viscosity, heat generation, reference
enthalpy, and latent heat associated with a single-phase change.
MATHP Specifies material properties for use in fully nonlinear (i.e., large strain and large rotation)
hyperelastic analysis of rubber-like materials (elastomers).
RADM Defines the radiation properties of a boundary element for heat transfer analysis.
Stress Dependent
CREEP Defines creep characteristics based on experimental data or known empirical creep law.
MATS1 Specifies stress-dependent material properties for use in applications involving nonlinear
materials.
NLMOPTS Defines nonlinear material option control for SOL 400.
TABLES1 Defines a tabular function for stress-dependent material properties such as the
stress-strain curve (MATS1 entry), creep parameters (CREEP entry) and hyperelastic
material parameters (MATHP entry).
Temperature Dependent
MATTi Table references for temperature-dependent MATi materials.
RADMT Specifies table references for temperature dependent RADM entry radiation boundary
properties.
TABLEM1 Tabular functions for generating temperature-dependent material properties.
TABLEST Table references for temperature dependent MATS1 materials.
TEMP Defines temperature at grid points for determination of thermal loading,
temperature-dependent material properties, or stress recovery.
TEMPAX Defines temperature sets for conical shell problems.
Main Index
1050 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
TEMPD Defines a temperature value for all grid points of the structural model that have not been
given a temperature on a TEMP entry.
TEMPP1 Defines temperature field for surface elements.
TEMPRB Defines a temperature field for the CBAR, CBEAM, CBEND, CROD, CTUBE, and
CONROD elements for determination of thermal loading, temperature-dependent
material properties, or stress recovery.
Frequency Dependent or Spatial Dependent or Both
MATiF Table reference for frequency dependent MATi materials.
TABLEDi For frequency dependent material properties.
TABLED5 (Frequency as a function of temperature) entry is not currently supported
with spatial entries.
PDISTB Defines element distributions of property data.
PDISTBM Defines element distributions of property data.
PCOMPFQ Defines the frequency dependent properties for a PCOMP/PCOMPG Bulk Data entry.
Miscellaneous
Brake Squeal (SOL 400)
BRKPROP Specifies property of brake system for brake squeal analysis.
BRKSYS Specifies data for brake system for brake squeal analysis.
BSQUEAL Specifies data for brake squeal analysis.
MOTION Specifies motion direction in brake system for brake squeal analysis.
Comments
$ Used to insert comments into the input file. Comment statements may appear anywhere
within the input file.
Delete
/ Control Input Stream
Direct Matrix Input
CONM1 Defines a 6x6 mass matrix at a geometric grid point.
DMI Defines matrix data blocks.
DMIG Defines direct input matrices related to grid, extra, and/or scalar points.
DMIG,UACCEL Defines rigid body accelerations in the basic coordinate system.
Main Index
Chapter 9: Bulk Data Entries 1051
Bulk Data Entry Descriptions
DMIAX Defines axisymmetric (fluid or structure) related direct input matrix terms.
TF Defines a dynamic transfer function.
Direct Matrix Input for Aeroelasticity
DMIJ Defines direct input matrices related to collation degrees-of-freedom (js-set) of
aerodynamic mesh points for CAERO1, CAERO3, CAERO4 and CAERO5 and for
the slender body elements of CAERO2. These include W2GJ, FA2J and input
pressures and downwashes associated with AEPRESS and AEDW entries.
DMIJI Defines direct input matrices related to collation degrees-of-freedom (js-set) of
aerodynamic mesh points for the interference elements of CAERO2.
DMIK Defines direct input matrices related to physical (displacement) degrees-of-freedom
(ks-set) of aerodynamic grid points.
End of Input
ENDDATA Designates the end of the Bulk Data Section.
Include File
INCLUDE Inserts an external file into the input file. The INCLUDE statement may appear
anywhere within the input data file.
Materials (SOL 400)
MATDIGI e-XstreamDigimat material interface
MATEP Elasto-plastic material properties.
MATF Specifies material failure model. Also maybe used in all linear solutions between SOL101
and 112 in conjunction with PCOMPLS.)
MATG Gasket material properties.
MATHE Hyperelastic material properties.
MATORT Elastic 3D orthotropic material properties. Also maybe used in all linear solutions
between SOL101 and 112 in conjunction with PCOMPLS.
MATTEP Thermoelastic-Plastic material properties.
MATTF Material Failure Model Temperature Variation
MATTG Temperature variation of interlaminar materials.
MATTHE Thermo hyperelastic material.
MATTORT Thermoelastic orthotropic material
MATS3 Specifies NLELAST option for advanced orthotropic, nonlinear elastic materials at
axisymmetric conditions.
Main Index
1052 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
MATS8 Specifies NLELAST option for advanced orthotropic, nonlinear elastic material for
plane stress and shell elements.
MATSMA Material properties for shape memory alloys.
MATSORT Specifies NLELAST option for advanced 3D orthotropic, nonlinear elastic materials.
MATTVE Thermo-visco-elastic material properties
MATVE Viscoelastic material properties
MATVP Viscoplastic or creep material properties
MCOHE Cohesive materials
Non-Structural Mass Distribution Selection
NSM Non Structural Mass entry by property or element ID, value.
NSM1 Non Structural Mass entry by property or element ID, value.
NSMADD Non Structural Mass as sum of listed sets.
NSML Lumped non structural mass entry by property or element ID, value.
NSML1 Lumped non structural mass entry by property or element ID, value.
OpenFSI (SOL 400)
FSICTRL Defines the analysis type for OpenFSI fluid structure analysis simulations.
WETELME Defines a wetted element used in OpenFSI fluid structure interaction simulations.
WETELMG Defines a wetted element used in OpenFSI fluid structure interaction simulations.
WETLOAD Defines the load set and associated wetted surface for OpenFSI fluid structure
interaction simulations.
WETSURF Defines a wetted surface used in OpenFSI fluid structure interaction simulations.
Output Control
BOUTPUT Defines secondary nodes at which output is requested.
CBARAO Defines a series of points along the axis of a bar element (CBAR entry) for stress and
force recovery output.
ECHOOFF Marks the point or points in the input file to deactivate printed echo of the Bulk Data.
ECHOON Marks the point or points in the input file to activate printed echo of the Bulk Data.
FREEPT Surface point location for data recovery in hydroelastic problems.
PLOTEL Defines a one-dimensional dummy element for use in plotting.
POINTAX Defines the location of a point on an axisymmetric shell ring at which loads may be
applied via the FORCE or MOMENT entries and at which displacements may be
requested.
Main Index
Chapter 9: Bulk Data Entries 1053
Bulk Data Entry Descriptions
PRESPT Defines the location of pressure points in the fluid for recovery of pressure data in
hydroelastic problems.
SET1 Defines a set of grid points.
TSTEP Specifies time step intervals for data recovery in transient response.
TSTEPNL Specifies time step intervals for data recovery in nonlinear transient response.
Monitor Points
AECOMP Defines a component for use in aeroelastic monitor point definition or external splines.
AECOMPL Defines a component for use in aeroelastic monitor point definition or external splines as a
union of other components.
MONPNT1 Defines an integrated load monitor point at a point (x,y,z) in a user defined coordinate
system.
MONPNT2 Element Monitor Output Results Item.
MONPNT3 Sums select Grid Point Forces to a user chosen monitor point.
MONCNC Stripwise aerodynamic lift and pitching moment coefficients.
M
MONSUM Linear combination of monitor point components.
MONSUM1 Linear combination of two or more monitor points.
MONSUMT Linear combination of two or more monitor points with moment transfer.
Parameters
CAMPBLL Specifies the parameters for Campbell diagram generation.
PARAM Specifies values for parameters used in solution sequences or user-written DMAP
programs.
MDLPRM Specifies parameters which affect the solution of the structural model.
Solution Control
ITER Defines options for the iterative solver in SOLs 101, 106, 108, 111 and 153.
RVDOF Degrees-of-freedom specification for residual vector computations.
RVDOF1 Degrees-of-freedom specification for residual vector computations (alternate form).
Tabular Input
DTI Defines table data blocks.
DTI,ESTDATA Provides override data for time and space estimation for superelement processing
operations.
Main Index
1054 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
DTI,INDTA Specifies or overrides default item codes for the sorting and filtering of element stresses,
strains, and forces.
DTI,SETREE Defines a superelement tree that determines the superelement processing order.
DTI,SPECSEL Correlates spectra lines specified on TABLED1 entries with damping values.
DTI,SPSEL Correlates output requests with frequency and damping ranges.
DTI,UNITS Defines units necessary for conversion during the analysis for the Nastran/ADAMS
interface and Nastran fatigue analysis.
TABDMP1 Defines modal damping as a tabular function of natural frequency.
TABLED1 Tabular functions for generating dynamic loads.
TABLEM1 Tabular functions for generating temperature-dependent material properties.
TABLES1 Defines a tabular function for stress-dependent material properties such as the
stress-strain curve (MATS1 entry), creep parameters (CREEP entry) and hyperelastic
material parameters (MATHP entry).
TABL3D Specifies a table where an entry can be a function of up to 4 variables such as strain,
temperature, strain rate, etc. (SOL 400).
TABLE3D Specify a function of three variables for the CORD3G entry only.
TABLFTG Defines cyclic load variation for use in fatigue analysis.
TABLRPC Tabular functions for generating dynamic loads by reading the tabular data from an
external channel data file.
TABRND1 Defines power spectral density as a tabular function of frequency for use in random
analysis. Referenced by the RANDPS entry.
3D Contact Region
BCBMRAD Allows the equivalent radius in beam-to-beam contact to be different for each beam cross
section. (SOL 400)
BCBOX Defines a 3D contact region.
BCHANGE Changes definitions of contact bodies.
BCMATL Defines a 3D contact region by element material.
BCMOVE Defines movement of bodies in contact.
BCPARA Defines contact parameters.
BCPROP Defines a 3D contact region by element properties.
BSURF Defines a contact body or surface by element IDs.
Old Contact Format
BCTABLE Defines a contact table.
BCBODY Defines a flexible rigid contact body in 2D or 3D.
New Contact Format
Main Index
Chapter 9: Bulk Data Entries 1055
Bulk Data Entry Descriptions
BCTABL1 Defines a contact table.
BCONECT Defines the Touching and Touched Contact Bodies
BCONPRG Geometric Contact Parameters of Touching Bodies
BCONPRP Physical Contact Parameters of Touching Bodies in SOL 101 and 400
BCBODY1 Flexible or Rigid Contact Body in 2D and 3D
BCBDPRP Contact Body Parameters in SOLs 101 and 400
BCRIGID Defines a Rigid Contact Body in SOLs 101 and 400
BCRGSRF Rigid Contact Surface List in SOLs 101 and 400
BCPATCH Defines a Rigid Contact Body Made up of Quadrilateral Patches in SOLs 101 and 400
BCBZIER Defines a Rigid Contact Body Made up of Bezier Surfaces in SOLs 101 and 400
BCNURB2 Defines a 2D Rigid Contact Body Made up of NURBS in SOLs 101 and 400
BCNURBS Defines a Rigid Contact Body Made up of NURBS in SOLs 101 and 400
BCTRIM Defines the Geometry of a Trimming Curve
User-Defined Subroutines and Services
BCONUDS Allows the user to provide contact routines for use with enhanced MSC Nastran contact
analysis. (SOL 400)
GENUDS User Data for Notify User Defined Service or Subroutine
MATUDS Allows the user to provide material routines for use with enhanced MSC Nastran
material models. (SOL 400)
MATTUSR Specifies table variation of user defined generic materials in SOL 400 only.
UDSESV Define the number and names of user state variables for material user subroutines (SOL
400)
Explicit Nonlinear (SOL 700)
Air Bags (SOL 700)
GBAG Defines the pressure within an enclosed volume.
Main Index
1056 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
ATB Models (SOL 700)
ATBACC Defines an acceleration field that will be applied to ATB segments.
ATBJNT This entry can only be used together with the ATBSEG entries that this joint
connects. The ATBSEG entries overwrite the position and orientation of the ATB
segments as specified in the ATB input file. The ATBJNT entry can be used to create
a Bulk Data file containing elements and grid points to visualize the ATB segment
together with its joints. This visualization of the joints makes it possible to position
the ATB model in any available preprocessor.
ATBSEG Defines the position and orientation of the ATB segments.
RELEX Defines a rigid ellipsoid whose properties and motion are defined by either ATB.
Contact (SOL 700)
BCBODY Defines a flexible or rigid contact body in 2D or 3D.
BCBODY1 Defines a flexible or rigid contact body in 2D or 3D.
BCBOX Defines a 3D contact region - all elements within the region define a contact body.
BCELIPS Defines a list of ellipsoid names (character strings) for use of contact analysis.
BCGRID (SOL Grids to be included in contact analyses.
700 only)
BCMATL Defines a 3D contact region by element material. All elements with the specified
materials define a contact body.
BCONECT Defines the touching and touched contact bodies used for general contact.
BCONPRG-700 Defines geometric contact parameters of touching bodies.
BCONPRP-700 Defines physical contact parameters of touching bodies.
BCSEG Grids which are part of an element to be used in contact analyses.
BCTABLE Defines a contact table (old format).
BCTABL1 Defines a contact table (new format).
BSURF Defines a contact body or surface by Element IDs.
Coordinate Systems (SOL 700)
CORD3R Defines a moving rectangular coordinate system using three points (SOL 700 only).
Dampers/Springs (SOL 700)
CDAMP1D Defines a scalar damper connection for use in SOL 700 only.
CDAMP2D Defines a scalar damper connection for use in SOL 700 only.
CELAS1D Defines a scalar spring connection for use in SOL 700 only.
CELAS2D Defines a scalar spring connection for use in SOL 700 only.
Main Index
Chapter 9: Bulk Data Entries 1057
Bulk Data Entry Descriptions
Direct Text Input (SOL 700)
ENDDYNA Defines the end of direct text to Dytran.
TODYNA Defines the start of direct text to Dytran.
Element Properties (SOL 700)
PBELT Defines the properties of a belt element referenced by a CROD entry.
PELAS1 Defines a spring property designated by a force-deflection curve for SOL 700.
PSHELL1 Defines the properties of SOL 700 shell elements that are much more complicated
than the shell elements defined using the PSHELL entry.
PVISC1 Defines the properties of a nonlinear damper where the damping constant varies
with the velocity.
Eulerian Boundary (SOL 700)
BARRIER Defines a barrier for transport in a Eulerian mesh.
FLOW Defines the properties of a material for the boundaries of an Eulerian mesh.
FLOWC Defines the properties of a material for the boundaries of a Eulerian mesh.
FLOWDEF Definition of default Eulerian flow boundary condition.
FLOWT Defines the material properties for the in- or outflow of material trough the
boundary of an Euler mesh.
HYDSTAT Initializes the Euler element densities in accordance to a hydrostatic pressure profile.
Eulerian Initial Conditions (SOL 700)
CYLINDR Cylindrical shape used in the initial condition definition on the TICEUL entry.
SPHERE Spherical shape used in the initial condition definition on the TICEUL entry.
SURFINI Defines a surface that is used for initialization of regions of an Eulerian mesh.
TICEL Defines the initial values of element variables at the beginning of the analysis.
TICEUL1 Defines the initial values sets for Eulerian regions. The Eulerian regions are defined
by geometric shapes.
TICREG Defines the initial values sets for Eulerian regions. The Eulerian regions are defined
by geometric shapes.
TICVAL Defines the initial values of an Eulerian geometric region.
Main Index
1058 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Eulerian Materials (SOL 700)
EOSDEF EOSDEF defines the properties of the deflagration equation of state, and the
reaction rate to model the burning of solid propellants. The burning of the solid
propellant produces hot gas.
EOSGAM Defines the properties of a Gamma Law equation of state where the pressure p is
defined.
EOSIG Defines the properties of Ignition and Growth equation of state and the reaction
rate equation used to model high explosives.
EOSJWL Defines the properties of a JWL equation of state commonly used to calculate the
pressure of the detonation products of high explosives.
EOSMG Defines the properties of a Mie-Gruneisen equation of state commonly used to
calculate the pressure p in high strain rate processes.
EOSNA Defines the properties of Noble-Abel equation of state.
EOSPOL Defines the properties of a polynomial equation of state where the pressure p is
defined.
FAILJC Defines the properties of the Johnson-Cook failure model.
FAILMPS Defines the properties of a failure model where failure occurs when the equivalent
plastic strain exceeds the specified value.
MATDEUL Defines a complete constitutive model as a combination of an equation of state, a
shear model, a yield model, a failure model, a spall model (PMIN), and
corotational frame.
PMINC Defines a spallation model where the minimum pressure is constant.
SHREL Defines an elastic shear model with a constant shear modulus.
SHRPOL Defines an elastic shear model with a polynomial shear modulus.
YLDHY Defines a yield model with zero yield stress.
YLDJC Defines a Johnson-Cook yield model where the yield stress is a function of effective
plastic strain, strain rate, and temperature.
YLDMSS Defines the yield model for snow material. This entry must be used in combination
with MATDEUL, EOSPOL and SHREL.
YLDPOL Defines a polynomial yield model where the yield stress is a function of effective
plastic strain.
YLDRPL Defines a rate power law yield model where the yield stress is a function of effective
plastic strain and strain rate.
YLDSG Defines the Steinberg-Guinan yield model where the yield stress is a function of
effective plastic strain, pressure and temperature.
YLDTM Defines the Tanimura-Mimura yield model where the yield stress is a function of
effective plastic strain, strain rate and temperature.
Main Index
Chapter 9: Bulk Data Entries 1059
Bulk Data Entry Descriptions
YLDVM Defines a bilinear or piecewise-linear yield model with isotropic hardening, using
the von Mises yield criterion.
YLDZA Defines the Zerilli-Armstrong yield model where the yield stress is a function of
effective plastic strain, strain rate and temperature.
Eulerian Solid Elements (SOL 700)
PEULER Defines the properties of Eulerian element.
PEULER1 Eulerian element properties.
Euler/Lagrange Coupling (SOL 700)
ABINFL Defines an inflator model suited for airbag analyses.
COUCOHF Defines a cohesive friction model suited for Euler Coupled analyses. The friction
model is defined as part of the coupling surface.
COHFRIC Allows friction and sticking during tensile conditions at the coupling surface.
COUOPT Defines the interaction factor and a pressure load from the covered side acting on
a BSURF.
COUP1FL Defines the surrounding variables when a segment of a coupling surface fails.
COUPINT Defines the surrounding variables when a segment of a coupling surface fails.
COUPLE Defines a coupling surface that acts as the interface between an Eulerian (finite
volume) and a Lagrangian (finite element) domain.
INFLCG Defines the cold gas-inflator characteristics of a COUPLE and/or GBAG
subsurface.
INFLFRC Defines the gas fractions as a function of time for hybrid inflators.
INFLGAS Defines a thermically ideal gas to be used with a standard or hybrid inflator.
INFLHB Defines the hybrid-inflator characteristics of a COUPLE and/or GBAG
subsurface.
INFLTNK Defines the Tanktest-inflator characteristics of a COUPLE and/or GBAG
subsurface.
INFLTR Defines the inflator characteristics of a COUPLE and/or GBAG subsurface.
INITGAS Specifies the initial gas composition inside a gasbag or Euler coupling surface.
LEAKAGE Defines the porosity model to be used with GBAG or COUPLE.
PERMEAB Defines the permeability of a COUPLE and/or GBAG (sub)surface.
PERMGBG Defines a permeable area of a COUPLE and/or GBAG surface, connected to
another GBAG.
PORFCPL Defines an interaction between two coupling surfaces through a hole.
PORFLOW Defines the material properties for the in- or outflow of an Eulerian mesh through
a porous area of the couple surface.
Main Index
1060 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
PORFLWT Defines a time dependent flow trough a porous area of the couple surface.
PORFGBG Defines a hole in a couple and/or GBAG (sub)surface, connected to another
GBAG.
PORHOLE Defines a hole in a COUPLE and/or GBAG surface.
PORHYDS Prescribes a hydrostatic pressure profile on a porous BSURF.
Hourglass Control (SOL 700)
HGSUPPR Defines the hourglass suppression method and the corresponding hourglass
damping coefficients.
Initial Conditions (SOL 700)
TIC3 Allows for the definition of a velocity field of grid points consisting of a rotation and
a translation specification. Used in Explicit Nonlinear (SOL 700) only.
Materials (SOL 700)
MAT1 Defines the material properties for linear isotropic materials.
MAT2 Defines the material properties for linear anisotropic materials for two-dimensional
elements.
MAT8 Defines the material property for an orthotropic material for isoparametric shell
elements.
MATBV Defines the bulk viscosity for materials.
MATEP Elasto-plastic material properties for SOL 700 only.
MATF Specifies failure model properties.
MATFAB Defines the properties of a bi-directional woven fabric material for shell elements.
MATHE Specifies hyperelastic (rubber-like) material properties for nonlinear analysis.
MATORT Specifies elastic orthotropic material properties for 3-dimensional and plane strain
and shell behavior for linear and nonlinear analyses.
MATRIG Defines the properties of a rigid body.
MATVE Specifies isotropic visco-elastic material properties to be used for quasi-static or
dynamic analysis
Miscellaneous (SOL 700)
BIAS Specifies a variation of the mesh-size in one direction for use in the MESH entry.
CMARKB2 Defines a 2-noded marker beam element by means of connecting two grid points.
CMARKN1 Defines a 1-noded marker element on a grid point.
DETSPH Defines the ignition point from which a spherical detonation wave travels, causing
the reaction of high explosive materials.
Main Index
Chapter 9: Bulk Data Entries 1061
Bulk Data Entry Descriptions
DYFSISW Allows activating or deactivating Fluid Structure Interaction and Eulerian solver.
EULFOR Defines a body force loading (acceleration) on Euler elements per unit mass.
EULFOR1 Alternative way to define an acceleration within a geometric region of the Euler
model regions are defined by geometric shapes which are defined by EULFREG
entries.
EULFREG Defines the acceleration field for sets of Eulerian regions, The Eulerian regions are
defined by geometric shapes. For each coordinate direction a time-depended
acceleration can be defined.
FFCONTR Defines the pressure within a closed volume. Intended for the use in (partially)
filled containers, where dynamic fluid effects are negligible, e.g. top loading and
hot filling.
MESH Defines a mesh.
PMARKER Defines the behavior of the marker element in the FV domain.
Multi-Variable Parameters (SOL 700)
DYPARAM, ATBAOUT Defines the frequency at which output is written to the main
output file of ATB.
DYPARAM, ATBHOUT A time-history file is created containing the output as requested
in the ATB input file on cards H.1 to H.11.
DYPARAM, ATBTOUT Defines the frequency at which output is written to the time-
history files of ATB.
DYPARAM,AUTOCOUP Defines the automatic coupling algorithm.
DYPARAM,AXIALSYM Axial symmetric analysis.
DYPARAM,AXREMAP Allows import of a 2D axial symmetric Euler archive into a 3D
simulation.
DYPARAM,BULKL Defines the default value of the linear bulk viscosity coefficient.
DYPARAM,BULKQ Defines the default value of the quadratic bulk viscosity
coefficient.
DYPARAM,BULKTYP Defines the default type of bulk viscosity.
DYPARAM,CFULLRIG Converts all 123456 constraints to the FULLRIG option on all
entries.
DYPARAM,CLUFLIM This DYPARAM activates a limiter that scales down the volume
strain rate for clumps with a small average uncovered fraction. It
can keep an instable airbag run stable, just like PARAM,
VELMAX can keep runs stable.
DYPARAM,CLUMPENR Sets the definition of the kinetic energy calculation method for
Eulerian blended clumps.
DYPARAM,COHESION Cohesion for Coulomb Friction
Main Index
1062 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
DYPARAM,CONM2OUT Determines if a summary of concentrated masses and their
energy and momentum is written to the output file.
DYPARAM,CONTACT Defines certain defaults for the contact definitions.
DYPARAM,COSUBMXT Defines the maximum number of subcycles that can occur in
Euler/Lagrange coupling. During a subcycle, the geometry of
the coupling surface is not updated. This number can vary in
time and is given by a table.
DYPARAM,COUFRIC Defines the Coulomb friction scheme.
DYPARAM,ELDLTH Print initial time step sizes for elements in the first cycle.
DYPARAM,EULERCB Divides a Euler domain into several cubes.
DYPARAM,EULTRAN Sets the definition of the face velocity used in the transport
scheme of the Multi-material solver and the single material
strength solver.
DYPARAM,EUSUBCYC Controls the growth of the subcycling interval in Euler
computations.
DYPARAM,EUSUBMAX Defines the maximum number of subcycles that can occur in the
Euler solver. During a subcycle, the Euler computations are
skipped.
DYPARAM,FAILDT Defines the property of a failure model where element failure
occurs when the element’s time step falls below the specified
limit.
DYPARAM,FAILOUT Defines whether failed elements are written to the output file
(ARCHIVES).
DYPARAM,FASTCOUP Defines the fast coupling algorithm.
DYPARAM,FLOWMETH Defines the method for simulating material flow between two
Euler domains across open areas in coupling surfaces.
DYPARAM,GEOCHECK This parameter forces a check of the geometry for consistent
connectivity of the defined hexagonal elements and correction if
needed.
DYPARAM,HGCMEM Defines the default membrane damping coefficient for shell
elements.
DYPARAM,HGCOEFF Defines the global default hourglass damping coefficient.
DYPARAM,HGCSOL Define the default damping coefficient for solid elements.
DYPARAM,HGCTWS Defines the default twisting damping coefficient for shell
elements.
DYPARAM,HGCWRP Defines the default warping damping coefficient for shell
elements.
DYPARAM,HGSHELL Defines the default hourglass suppression method for shell
elements.
Main Index
Chapter 9: Bulk Data Entries 1063
Bulk Data Entry Descriptions
DYPARAM,HGSOLID Defines the default hourglass suppression method for solid
elements.
DYPARAM,HGTYPE Defines the default type of hourglass suppression method.
DYPARAM,HICGRAV Defines the value of the gravity to be used by the HIC
calculations.
DYPARAM,HVLFAIL Defines element failure on the hydrodynamic volume limit
DYPARAM,HYDROBOD Defines a body force for single hydro material in Euler.
DYPARAM,IMM The option allows to specify the IMM method to be used.
DYPARAM,INFOBJ Additional information about the BJOIN and spotweld
connectivity will be listed in the output file.
DYPARAM,INISTEP Defines the time step used at the start of the analysis.
DYPARAM,JWLDET Specifies whether the blast wave of one explosive can ignite
another explosive. Here it assumed that the explosives are
modeled by a combination of EOSJWL and DETSPH entries.
DYPARAM,LIMCUB Defines the maximum number of cubes used to sort the grid
points in a contact definition.
DYPARAM,LIMITER Defines the type and the spatial accuracy of scheme used in the
Euler solver based on the ideas of Prof. Philip Roe.
DYPARAM,MATRMERG Merges MATRIG and/or RBE2-FULLRIG rigid bodies into a
new FULLRIG assembly.
DYPARAM,MATRMRG1 Merges MATRIG and/or RBE2-FULLRIG rigid bodies into
one existing MATRIG or RBE2-FULLRIG assembly with
predefined properties.
DYPARAM,MAXSTEP Defines the maximum allowable time step.
DYPARAM,MESHPLN Defines Mesh density for covering rigid planes.
DYPARAM,MINSTEP Defines the minimum time step that causes the analysis to
terminate.
DYPARAM,MIXGAS Specifies whether the gas constants of the Euler material or of gas
bags are updated based on the gas composition and temperature.
DYPARAM,NZEROVEL Set the velocity of a node to zero in case all attached elements
have failed.
DYPARAM,OLDLAGT Activate the collapsed hexahedron scheme as default for
lagrangian CTETRA elements.
DYPARAM,PARALLEL The option allows you to gather information on the parallel
section.
DYPARAM,PLCOVCUT Defines time when PLCOVER is cut off.
DYPARAM,PMINFAIL Defines Lagrangian solid element failure on reaching the spall
limit.
Main Index
1064 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
DYPARAM,RBE2INFO The grid points attached to MATRIG and RBE2assemblies are
listed to the output file.
DYPARAM,RHOCUT Defines the minimum density for all Eulerian elements.
DYPARAM,RJSTIFF Defines the stiffness of a rigid joint.
DYPARAM,SHELLFRM Sets the default for the shell formulation for quadrilateral
elements.
DYPARAM,SHELMSYS Defines the shell element system for the BLT shells.
DYPARAM,SHPLAST Specifies the type of calculation used to determine the plane
stress plasticity method for shells.
DYPARAM,SHSTRDEF Specifies the default coordinate system for the stress and strain
output of composite shells.
DYPARAM,SHTHICK Specifies whether or not the thickness of the shell changes with
membrane straining.
DYPARAM,SLELM Defines whether shell sublayer variables are to be stored in the
element arrays.
DYPARAM,SMP,BATCHSIZ Define batch size and number of CPU loops, per entity type.
DYPARAM,SMP,CPUINFO Define the CPU information per entity type.
DYPARAM,SNDLIM Defines the minimum value for the speed of sound.
DYPARAM,SPHERSYM Enables an efficient and accurate 1D spherical symmetric
solution for Euleran materials
DYPARAM,STRNOUT Saves the total strains and equivalent effective stress (von Mises
stress) at shell sublayers for output.
DYPARAM,TOLCHK To check the direction of an Euler face, the face normal vector is
projected onto the closest coordinate direction. If this projection
is 1, the normal is exactly in the coordinate direction. When this
projection is within a sufficient small tolerance of 1, the face can
be handled by fast coupling. The tolerance used is TOLCHK. If
the projection is smaller than 1-TOLCHK, the face cannot be
handled by fast coupling and the analysis terminates. Options
are then to slightly increase TOLCHK, write out double
precision format in PATRAN, use general coupling, or use the
MESH entry. Increasing TOLCHK too much can make the
coupling surface computation less accurate. To keep the
computation accurate, the maximal allowed value of TOLCHK
is 1e-6. If DYPARAM,TOLCHK is not used, the tolerance used
is 1e-14.
DYPARAM,VDAMP Controls the global damping in the dynamic relaxation.
DYPARAM,VELMAX Defines the maximum velocity in Eulerian meshes.
Main Index
Chapter 9: Bulk Data Entries 1065
Bulk Data Entry Descriptions
DYPARAM,VELMAX1 Defines the maximum translational and angular velocity in
Eulerian and Lagrangian meshes
DYPARAM,VISCPLAS Activate the overstress formula to update strain-rate dependent
plasticity. This formula is normally used for viscous-plastic
material.
Rigid Elements (SOL 700)
BJOIN Defines (multiple) pairs of grid points of one-dimensional and/or shell elements to
be joined during the analysis.
RBJOINT Defines a joint between two rigid bodies.
WALL Defines a rigid plane through which specified Lagrangian grid points
cannot penetrate. Used in Explicit Nonlinear (SOL 700) only.
Time Step Control (SOL 700)
TSTEPNL Defines parametric controls and data for nonlinear transient structural or heat
transfer analysis.
User Defined Subroutines (SOL 700)
COMPUDS Defines an orthotropic failure model for shell composites specified by a user
subroutine.
EOSUDS Defines the frequency dependent properties for an isotropic poroelastic
material.
FAILUDS User defined simple failure of Eulerian materials.
FLOWUDS Defines a flow boundary on an Eulerian mesh specified by a user subroutine.
FORCUDS Defines enforced motion at grid points specified by a user subroutine.
NLOUTUD User defined output requests for elements or Lagrangian grid points.
PORUDS Defines a porosity model of a COUPLE surface through a user-written
subroutine.
SHRUDS Specifies that a user subroutine is being used to define the shear modulus.
TABLUDS Specifies that a user routine is being used to define an arbitrary function.
TICEUDS User defined simple failure of Eulerian materials.
YLDUDS Specifies that a user subroutine is being used to define a simple yield model.
Main Index
1066 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Solution Control
Aerodynamic Matrix Generation
MKAERO1 Provides a table of Mach numbers (m) and reduced frequencies (k) for aerodynamic
matrix calculation.
MKAERO2 Provides a list of Mach numbers (m) and reduced frequencies (k) for aerodynamic
matrix calculation.
Aerodynamic Parameters
AERO Gives basic aerodynamic parameters for unsteady aerodynamics.
AEROS Defines basic parameters for static aeroelasticity.
Aeroelastic Response Analysis
AEDW Defines a downwash vector associated with a particular control vector of the associated
aerodynamic configuration (AECONFIG).
AEFORCE Defines a vector of absolute or “per unit dynamic pressure” forces associated with a
particular control vector.
AEPARM Defines a general aerodynamic trim variable degree-of-freedom (aerodynamic extra
point).
AEPRESS Defines a vector of pressure/unit dynamic pressure associated with a particular control
vector.
AESCALE Defines reference lengths to scale aerodynamic grid points.
GUST Defines a stationary vertical gust for use in aeroelastic response analysis.
TABRNDG Defines the power spectral density (PSD) of a gust for aeroelastic response analysis.
TRIM Specifies constraints for aeroelastic trim variables. The SPLINE1 and SPLINE4 entries
need to be here for the finite plate spline.
UXVEC Specification of a vector of aerodynamic control point values.
Aeroelastic Stability Analysis
DIVERG Defines Mach numbers (m) for a static aeroelastic divergence analysis.
FLFACT Used to specify density ratios, Mach numbers, reduced frequencies, and velocities for
flutter analysis.
FLUTTER Defines data needed to perform flutter analysis.
Buckling Analysis
EIGB Defines data needed to perform buckling analysis.
EIGRL Defines data needed to perform real eigenvalue (vibration or buckling) analysis with the
Lanczos method.
Main Index
Chapter 9: Bulk Data Entries 1067
Bulk Data Entry Descriptions
Cyclic Symmetry
CYSYM Defines parameters for cyclic symmetry analysis.
Eigenvalue Analysis
EIGC Defines data needed to perform complex eigenvalue analysis.
EIGR Defines data needed to perform real eigenvalue analysis.
EIGRL Defines data needed to perform real eigenvalue (vibration or buckling) analysis
with the Lanczos method.
EIGP Defines poles that are used in complex eigenvalue extraction by the Determinant
method.
RVDOF, Degrees-of-freedom specification for residual vector calculation.
RVDOF1
Monte-Carlo simulation
MONCARL Defines the parameters for Monte-Carlo simulations.
Fatigue Analysis
DTI,UNITS Defines units necessary for conversion during the analysis for the Nastran/ADAMS
interface and Nastran fatigue analysis.
FTGDEF Defines elements and their associated fatigue properties to be considered for fatigue
analysis.
FTGPARM Defines parameters for a fatigue analysis
FTGSEQ Defines the loading sequence for pseudo-static fatigue analysis using SOL 101 or
modal transient fatigue analysis using SOL 103 or SOL 112 or random vibration
fatigue analysis using SOL 108 or SOL 111.
FTGEVNT Groups simultaneously applied loads into loading events for pseudo-static fatigue
analysis using SOL 101 or modal transient fatigue analysis using SOL 103 or
random vibration fatigue analysis using SOL 108 or SOL 111 by referencing
FTGLOAD entries.
FTGLOAD Defines cyclic loading variation for pseudo-static fatigue analysis using SOL 101 or
modal transient fatigue analysis using SOL 103 or random vibration fatigue
analysis using SOL 108 or SOL 111.
MATFTG Defines fatigue material properties.
PFTG Defines fatigue elemental properties.
RANDPS Defines PSDs and cross PSDs for frequency domain fatigue (random vibration)
analysis using SOL 108 or SOL 111.
TABLFTG Defines tabular data for specifying fatigue cyclic loading variation for time domain
fatigue analysis using SOL 101 or SOL 103.
Main Index
1068 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
TABLRPC Tabular functions for generating dynamic loads by reading the tabular data from an
external channel data file.
TABRND1 Defines tabular data for specifying PSD random vibration loading for frequency
domain fatigue (random vibration) analysis using SOL 108 or SOL 111.
TIM2PSD Defines parameters and triggers conversion of time history channel data into
corresponding Power Spectral Density (PSD) functions for use in random vibration
fatigue analysis using SOL 108 or SOL 111.
UDNAME Provides the name of a file that can be referenced from other bulk data entries such
as FTGLOAD.
Frequency Response
FREQ Defines a set of frequencies to be used in the solution of frequency response problems.
FREQ1 Defines a set of frequencies for problem solution.
TABDMP1 Defines modal damping as a tabular function of natural frequency.
Nonlinear Static Analysis
ITER Defines options for the iterative solver in SOLs 101, 106, 108, 111, 153, 200 and 400.
NLADAPT Defines additional parameters for automatic load or time stepping used with enhanced
nonlinear in SOL 400.
NLPARM Defines a set of parameters for nonlinear static analysis iteration strategy.
NLPCI Defines a set of parameters for the arc-length incremental solution strategies in nonlinear
static analysis (SOL 106).
NLSTEP Describes the Control Parameters for Mechanical, Thermal and Coupled Analysis in
SOL 400 and for Contact Analysis in SOL 101.
Optimization (SOL 200 Only)
BEADVAR Defines design region for topography (bead or stamp) optimization.
BNDGRID Specifies a list of grid point identification numbers on design boundaries or surfaces for
shape optimization (SOL 200).
DCONADD Defines the design constraints for a subcase as a union of DCONSTR entries.
DCONSTR Defines design constraints.
DDVAL Define real, discrete design variable values for discrete variable optimization.
DEQATN Defines a design variable for design optimization.
DESVAR Defines a design variable for design optimization.
DLINK Relates one design variable to one or more other design variables.
DOPTPRM Overrides default values of parameters used in design optimization.
Main Index
Chapter 9: Bulk Data Entries 1069
Bulk Data Entry Descriptions
DRESP1 Defines a set of structural responses that is used in the design either as constraints or as
an objective.
DRESP2 Defines equation responses that are used in the design, either as constraints or as an
objective.
DRESP3 Defines an external response using user-supplied routine.
DSCREEN Defines screening data for constraint deletion.
DTABLE Defines a table of real constants that are used in equations (see DEQATN entry).
DTABLE2 Defines real constants from a field of property, material or connections bulk data entries
which can then be invoked by a DVxREL2, DRESP2, or DRESP3 entry.
DVBSHAP Associates a design variable identification number to a linear combination of boundary
shape vectors from a particular auxiliary model.
DVCREL1 Defines the relation between a connectivity property and design variables.
DVCREL2 Defines the relation between a connectivity property and design variables with a user-
supplied equation.
DVGRID Defines the relationship between design variables and grid point locations.
DVLREL1 Defines the linear relation between analysis model loading and design variables
DVMREL1 Defines the relation between a material property and design variables.
DVMREL2 Defines the relation between a material property and design variables with a user-
supplied equation.
DVPREL1 Defines the relation between an analysis model property and design variables.
DVPREL2 Defines the relation between an analysis model property and design variables with a
user-supplied equation.
DVPSURF Design Variable to Control Surface Setting Relation
DVSHAP Defines a shape basis vector by relating a design variable identification number (DVID)
to columns of a displacement matrix.
MODTRAK Specifies parameters for mode tracking in design optimization (SOL 200).
SEDLINK Multiple Design Variable Linking Across PART SE Boundary
SEDRSP2 Design Sensitivity Equation Response Quantities for PART SE
SEDRSP3 Defines External Response with User-Supplied Routines
STOCHAS Randomization of Model Parameters
TOMVAR Defines a design region for topometry optimization (element-by-element
optimization).
TOPVAR Defines a topology design region for topology optimization.
Main Index
1070 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions
Random Response
RANDPS Defines load set power spectral density factors for use in random analysis.
RANDT1 Defines time lag constants for use in random analysis autocorrelation function
calculation.
RCROSS Cross-power spectral density and cross-correlation function output.
TABRND1 Defines power spectral density as a tabular function of frequency for use in random
analysis. Referenced by the RANDPS entry.
Rotordynamics
RGYRO Specifies synchronous or asynchronous analysis, reference rotor, and rotation speed of the
reference rotor.
ROTBENT Define kinks and offsets to be applied on a rotor, pull the rotor on to its bearing and then
carry out rotordynamic analysis (SOL 400 only).
ROTHYBD Hybrid damping for rotors
ROTOR Rotor Model Definition
ROTORAX Axisymmetric Model Rotor Definition
ROTORG Specifies grids that compose the rotor line model.
ROTORSE Specifies grids that compose the rotor line model.
RSPINR Specifies the relative spin rates between rotors for complex eigenvalue, frequency response,
and static analysis.
RSPINT Specifies rotor spin rates for nonlinear transient analysis.
UNBALNC Specifies an unbalanced load for transient analysis in terms of a cylindrical system with the
rotor rotation axis as the z-axis.
Transient Response
TIC Defines values for the initial conditions of variables used in structural transient analysis.
TSTEP Defines time step intervals at which a solution will be generated and output in transient
analysis.
TSTEPNL Defines parametric controls and data for nonlinear transient structural or heat transfer
analysis. Is intended for SOLs 129, 159, and 99.
Main Index
$ 1071
Comment
Entries A - B
$ Comment
Used to insert comments into the input file. Comment statements may appear anywhere within the input file.
Format:
$ followed by any characters out to column 80.
Example:
$ TEST FIXTURE-THIRD MODE
Remarks:
1. Comments are ignored by the program.
2. Comments will appear only in the unsorted echo of the Bulk Data.
3. For free field entries (See Format of Bulk Data Entries above), a $ can be used to terminate the field
entries and any required remaining fields will be modulo replicated as blank.
4. For the default NASTRAN SYSTEM (IFPSTAR) = YES, input using FIXED field, a $ can be used
to terminate the field entries and any required remaining fields will be modulo replicated as blank.
The OLD IFP (NASTRAN SYSTEM (IFPSTAR) = NO) will fail with this option.
Main Index
1072 /
Control Input Stream
/ Control Input Stream
Allows the user control over field width, and on restart entry deletion, insert and update, and process control.
(This entry’s execution is dependent on whether NASTRAN SYSTEM(444)= 0 or 1.)
Format:
1 2 3 4 5 6 7 8 9 10
/ Alpha numeric text as described below
Examples:
/ 0 12
/delete all
/ Delete FORCE1,PARAM MATVP
Describer Meaning
/ Must be first character and occur somewhere in fields one through 8. (Character)
If NASTRAN SYSTEM(444)=0, then the n1, n2 directive below is the only valid form:
n1,n2 Two integers indicating following number of lines of previous input are to be deleted.
(Integer. n1 > 10, n2 > n1). /, n1,n2 directive must be entered before any new data is
added to the input stream.
If NASTRAN SYSTEM(444)=1, then the above n1, n2 directive will not work and only the following
forms are valid:
DELETE Keyword indicating following listed items are to be deleted. (Character) /DELETE
directive must be entered before any new data is added to the input stream.
ALL Keyword indicating following a /DELETE directive. All previous input items will be
deleted on RESTART. (Character)
List of names A list of Bulk Data names to be deleted following a /DELETE directive. All previous
input Bulk entries with the names indicated will be deleted on RESTART. (Character)
SFW A Keyword that is used for fixed field entries and allows the user to define the field
width of single field entries for Field 2 thru Field 9. See Remark 1. (Character)
n Single Field Width value n used with SFW. This is used for fixed field entries and
allows the user to define the field width of single field entries for Field 2 thru Field 9
to the value n.(Integer 8 < n < 14, Default = 8). If double field is selected by use of the
* option, then Field 2 thru Field 9 are of 2n width. (Field 1 and Field 10 always remain
of width 8). See Remark 1.
Main Index
/ 1073
Control Input Stream
Describer Meaning
SKIPON Input data following this keyword would not be processed in the current execution.
(Character). This command is terminated by one of three methods: 1) The occurrence
of a SKIPOFF. 2) The occurrence of a BEGIN (Such as BEGIN SUPER=10) 3) The
occurrence of an ENDDATA.
SKIPOFF Keyword turning off the SKIPON command. (Character)
INSERT Keyword that implies that entries when placed into the input stream must not be
previously present. See Remark 1. (Character; Default for INITIAL runs.)
UPDATE Keyword that implies that entries when placed into the input stream are new or are to
replace existing entries. See Remark 1. (Character; Default for RESTART runs.)
DUPMETH Keyword that allows reversion to the original IFP, DUPTOL tolerance selection.
/DUPMETH=OLD selects original IFP tolerance selection. See the
DPBLKTOL(402) system cell description and Remark 1. (Character; Default NEW
for IFPSTAR tolerance selection).
DUPTOL Keyword that allows a closeness tolerance value when searching for removal of
duplicate entries. (Character)
v Tolerance value, used with DUPTOL, when searching for removal of duplicate entries.
See Remark 1. (Real > 0.; Default 1.0-5.)
LISTON Keyword to indicate a "list of data to follow" See Remark 10. (Character)
LISTOFF Keyword to indicate a "list of data is terminated" See Remark 10. (Character)
Remarks:
1. If the SFW, INSERT, UPDATE, DUPMETH, DUPTOL Keywords and any associated value (n, v)
occur in the first BEGIN BULK Section the values set will carry forward to any other BEGIN section
included. If a user wishes to have some later BEGIN have different control values, then the BEGIN
BULK values can be overridden for that particular BEGIN Section by the inclusion of / entries
particular to that specific BEGIN Section. The DUPMETH must come before the DUPTOL entry.
Currently IFPSTAR will not recognize the settings from the command line or RC file due to default
usage issues at the application state and real value passing through the component level. When
DUPMETH is OLD and DPBLKTOL or DUPTOL is zero or positive, remove grids with duplicated
id without checking CP, CD, PS ,SE fields and distance tolerance.
Example:
/DUPMETH=OLD
/DUPTOL=0.1
With the following NASTRAN entry required:
NASTRAN SYSTEM(402)=0.1
Main Index
1074 /
Control Input Stream
2. The input stream into Nastran is now part of a Common Data Model component and entries are
committed to a data base as soon as they are interpreted in a single unsorted pass. When the user
requests a sorted ECHO, the ECHO represents a binary value converted back into a column character
location. It does not represent the actual binary entry value! Unsorted ECHO respects the request list
of the ECHO command.
3. If an improperly formatted bulk data entry is encountered, the true file line number of the error is
printed along with reference to the Parent entry. If the offending entry is in an include file the file is
identified.
4. Usage of the continuation mnemonic is no longer needed and its usage is not recommended.
5. Default Fixed Fields are 80 characters (see SFW). Free field supports 128 characters.
6. Because the Common Data Model component entries are committed to a data base as soon as they
are interpreted in a single unsorted pass, the /DELETE syntax is now required to be used on restart.
7. If an /INSERT is present on RESTART the Common Data Model component will signal an error
condition EXCEPT when certain objects such as GRID entries have been classified as Remove
Duplicate or when objects such as SPC that allow superposition are encountered.
8. Entries that allow superposition are always in /INSERT.
9. If NASTRAN SYSTEM(444)=1, then the Nastran Replication feature is not recommended.
10. For convenience in entering an ordered list of elements (tuples) data or, such as table value inputs,
the following is allowed for example:
tabled1,111
/liston
1.0 1.0
2.0 1.0
3.0 2.0
4.0 2.0
5.0 1.0
6.0 1.0
/listoff
,endt
or for example if user likes commas:
tabled1,112
/liston
1.0, 1.0
2.0, 1.0
3.0, 2.0
4.0, 2.0
Main Index
/ 1075
Control Input Stream
5.0, 1.0
6.0, 1.0
/listoff
,endt
Main Index
1076 ABINFL
Inflator Model to be Used With GBAG or COUPLE Entries
ABINFL Inflator Model to be Used With GBAG or COUPLE Entries
Defines an inflator model suited for airbag analyses. The inflator model is defined as part of the GBAG or
COUPLE surface. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
ABINFL CID INFID SUBID INFTYPE INFTYPID COEFF COEFFV
Example:
ABINFL 201 1 120 INFLHB 11 0.012
Describer Meaning
CID Unique number of a ABINFL entry. (Integer > 0; Required)
INFID Number of a set of ABINFL entries NFID must be referenced from a GBAG or COUPLE
entry. (Integer > 0; Required)
SUBID Number of a BSURF, BCBOX, BCPROP, BCMATL or BCSEG, which must be a part of
the as defined on the GBAG or COUPLE entry. (Integer > 0; Required)
INFTYPE Defines the type of inflator. (Character; Required)
INFLTR The INFLTR logic is used to model inflators in an air bag.
INFLHB The INFLHB logic is used to model hybrid inflators in an air bag.
INFLCG The INFLCG logic models a cold gas inflator.
INFLTNK The INFLTNK logic models the inflator properties (mass flow rate and
inflator gas temperature) calculated from the empirical results.
INFTYPID Number of the entry selected under INFTYPE, for example, INFLTR,INFTYPID.
(Integer > 0; Required)
COEFF Method of defining the area coefficient. (Character, CONSTANT)
CONSTANT The area coefficient is constant and specified on COEFFV.
TABLE The area coefficient varies with time. COEFFV is the number of a
TABLED1 entry giving the variation with time.
COEFFV The area coefficient or the number of a TABLED1 entry depending on the COEFF entry.
(0.0 < Real < 1.0 or 1 > 0)
Remarks:
1. The INFLTR or INFLHB inflator geometry and location is defined by a BSURF, BCBOX,
BCPROP, BCMATL or BCSEG. The area of the hole through which the gas enters is equal to the
area of the subsurface multiplied by COEFFV. A value of COEFFV = 1.0 will open up the complete
subsurface area, while a value of COEFFV = 0.0 will result in a closed inflator area with no inflow.
Main Index
ABINFL 1077
Inflator Model to be Used With GBAG or COUPLE Entries
2. This allows for setting up the exact same model for either a uniform pressure model or an Euler
Coupled model. This makes it possible to set up the model using the switch from full gas dynamics
to uniform pressure (GBAGCOU).
Main Index
1078 ABSNMVB
Meta data group Boolean name/value pairs
ABSNMVB Meta data group Boolean name/value pairs
Associate Boolean Name/Value pairs to meta data collectors (ABSTRCT)
Format:
1 2 3 4 5 6 7 8 9 10
ABSNMVB ABSTID NAME1 VAL1 NAME2 VAL2 -etc.- ...
Example:
1 2 3 4 5 6 7 8 9 10
ABSNMVB 50 STIFFNER TRUE VARSECT FALSE
Describer Meaning
ABSTID Unique identification number for meta data group (ABSTRCT). (Integer>0).
NAMEi Up to eight characters defining the name of this Name/Value pair. (Character).
VALi Value of this Name/Value pair -Boolean- data (Character) TRUE or FALSE.
Remarks:
1. This entry has no impact on the solution.
2. The only allowed character values are “TRUE” or “FALSE”.
Main Index
ABSNMVI 1079
Meta data group Integer name/value pairs
ABSNMVI Meta data group Integer name/value pairs
Associate Integer Name/Value pairs to meta data collectors (ABSTRCT).
Format:
1 2 3 4 5 6 7 8 9 10
ABSNMVI ABSTID NAME1 VAL1 NAME2 VAL2 -etc.-
Example:
1 2 3 4 5 6 7 8 9 10
ABSNMVI 50 SPANS 12
Describer Meaning
ABSTID Unique identification number for meta data group (ABSTRCT). (Integer>0).
NAMEi Up to eight characters defining the name of this Name/Value pair. (Character).
VALi Value of this Name/Value pair (Integer).
Remarks:
1. This entry has no impact on the solution.
Main Index
1080 ABSNMVR
Meta data group Real Name/Value pairs
ABSNMVR Meta data group Real Name/Value pairs
Associate Real Name/Value pairs to meta data collectors (ABSTRCT).
Format:
1 2 3 4 5 6 7 8 9 10
ABSNMVR ABSTID NAME1 VAL1 NAME2 VAL2 -etc.-
Example:
1 2 3 4 5 6 7 8 9 10
ABSNMVR 50 ANGLEA 15.0 ANGLEB 45.0
Describer Meaning
ABSTID Unique identification number for meta data group (ABSTRCT). (Integer>0)
NAMEi Up to eight characters defining the name of this Name/Value pair. (Character)
VALi Value of this Name/Value pair (Real)
Remarks;
1. This entry has no impact on the solution.
Main Index
ABSNMVS 1081
Meta data group String name/value pairs
ABSNMVS Meta data group String name/value pairs
Associate String Name/Value pairs with meta data collectors (ABSTRCT).
Format:
1 2 3 4 5 6 7 8 9 10
ABSNMVS ABSTID
NAME1 VAL1
NAME2 VAL2
-etc.-
Example:
1 2 3 4 5 6 7 8 9 10
ABSNMVS 50
ABSNAME B pillar model year 2020
ABSDESC B pillar including locking bushing
Describer Meaning
ABSTID Unique identification number for meta data group (ABSTRCT). (Integer>0)
NAMEi Up to eight characters defining the name of this Name/Value pair. (Character).
VALi Value of this Name/Value pair. May consist of any Character A-Z, or numbers, and
underscore or dash. Limited to 56 characters. (Character).
Remarks:
1. This entry has no impact on the solution.
2. The name/value pair entries may be specified in any order.
Main Index
1082 ABSNMVS
Meta data group String name/value pairs
3. In the HDF5 viewer
4. In the above Example, the following SET3 entries might include:
$ CBEAM elements for B pillar
SET3, 10, ELEM, 7701, THRU, 7799
$ CBUSH elements for locking
SET3, 30, ELEM, 66, 67, 68, 69
$ RIGID ELEMENTS
SET3, 90, RBEIN, 9991, THRU, 9996
Main Index
ABSTRCT 1083
Meta Data Collector for HDF5 output and post processing
ABSTRCT Meta Data Collector for HDF5 output and post processing
Allows the user to define an arbitrary group of Nastran entities (ABSTRACTion), using any Nastran keyword
type including elements, grids, materials, etc. and associate a name and description for the group.
Format:
1 2 3 4 5 6 7 8 9 10
ABSTRCT ABSTNM ABSTID NASTNM NASTID1 NASTID2 NASTID3 -etc.-
Example:
1 2 3 4 5 6 7 8 9 10
ABSTRCT PILLAR 50 CBEAM 10
ABSTRCT PILLAR 50 CBUSH 30
ABSTRCT PILLAR 50 RBE3 90
Describer Meaning
ABSTNM Up to eight characters for the name of the meta data group. (Character).
ABSTID Unique identification number for the meta data group. (Integer>0).
NASTNM Up to eight characters for the name of the Nastran entity being added to the meta data
group. (Character).
NASTIDi ID referencing a Nastran entity of the specified type or a set of such entities.
Remarks:
1. The group definition is transmitted from the input file to the .op2 and/or .h5 results file with no
impact on the solution.
2. The group definition can subsequently be recovered from either the .op2 or .h5 file by a post-
processor.
3. Associated with this entry are the entries: ABSNMVS, ABSNMVB, ABSNMVI, ABSNMVR.
Main Index
1084 ACCEL
Acceleration Load
ACCEL Acceleration Load
Defines static acceleration loads, which may vary over a region of the structural model. The load variation is
based upon the tabular input defined on this Bulk Data entry.
Format:
1 2 3 4 5 6 7 8 9 10
ACCEL SID CID N1 N2 N3 DIR
LOC1 VAL1 LOC2 VAL2 Continues in Groups of 2
Example(s):
ACCEL 100 2 0.0 1.0 2.0 X
0.0 1.0 1000.0 3.0
Describer Meaning
SID Load set identification number (Integer > 0)
CID Coordinate system identification number. (Integer ≥ 0; Default = 0)
Ni Components of the acceleration vector measured in coordinate system CID. (Real; at least
one Ni 0.0 )
DIR Component direction of acceleration variation. (Character; one of X, Y, and Z)
LOCi Location along direction DIR in coordinate system CID for specification of a load scale
factor. (Real)
VALi The load scale factor associated with location LOCi. (Real)
Remarks:
1. For all grids of the model, the acceleration vector is defined by a = VAL N , where N is the vector
defined by (N1, N2, N3). The magnitude of a is equal to VAL times the magnitude of N . The scale
factor VAL for each grid is found linearly interpolating the DIR coordinate of the grid between table
values LOCi/VALi. If the GRID point coordinate in coordinate system CID is outside the range of
the table, VAL is determined either from VAL1 or VALn (the last value, see the following figure).
2. This type of acceleration load may be combined with other loads, such as FORCE, MOMENT,
GRAV, and ACCEL1 loads, by specification on a LOAD entry. The SID on an ACCEL entry may
not be the same as that of any other load entry.
3. This acceleration load does not include effects due to mass on scalar points.
4. A CID of zero references the basic coordinate system.
5. The DIR field must contain one of the characters X, Y, or Z. The DIR direction defines the direction
of acceleration load variation along direction 1, 2, or 3 respectively of coordinate system CID.
Main Index
ACCEL 1085
Acceleration Load
6. A minimum of two pairs of {LOCi, VALi} data must be specified.
VAL
VAL2
VAL3
VALn
VAL1
DIR
LOC1 LOC2 LOC3 LOCn
Definition of Load Scale Factor vs Location
7. If Modules are present then this entry may only be specified in the main Bulk Data section.
8. In the static solution sequences, SID must be selected by the LOAD Case Control command. In the
dynamic solution sequences, if there is a LOADSET Case Control command, then SID must be
referenced in the LID field of a selected LSEQ entry. If there is no LOADSET Case Control
command, then SID must be referenced in the EXCITEID field of an RLOADi or TLOADi entry.
Main Index
1086 ACCEL1
Acceleration Load
ACCEL1 Acceleration Load
Defines static acceleration loads at individual GRID points.
Format:
1 2 3 4 5 6 7 8 9 10
ACCEL1 SID CID A N1 N2 N3
GRIDID1 GRIDID2 -etc.-
Example(s):
ACCEL1 100 2 10.0 1.0 2.0 0.0
1 2 3 4 THRU 10 BY 2
20 21 THRU 30 40 52 69 70
82 90 100
Describer Meaning
SID Load set identification number (Integer > 0)
CID Coordinate system identification number. (Integer ≥ 0; Default = 0)
A Acceleration vector scale factor. (Real)
Ni Components of the acceleration vector measured in coordinate system CID. (Real; at
least one Ni 0.0 )
GRIDIDi List of one or more GRID point identification numbers. Key words “THRU” and
“BY” can be used to assist the listing. (Integer > 0)
Remarks:
1. The acceleration vector is defined by a = A N , where N is the vector defined by (N1, N2, N3).
The magnitude of a is equal to A times the magnitude of N .
2. This type of acceleration load may be combined with other loads, such as FORCE, MOMENT,
GRAV, and ACCEL loads, by specification on a LOAD entry. The SID on an ACCEL1 entry may
not be the same as that of any other load entry.
3. This acceleration load does not include effects due to mass on scalar points.
4. A CID of zero references the basic coordinate system.
5. ACCEL1 loads are not supported with super elements.
6. In the static solution sequences, SID must be selected by the LOAD Case Control command. In the
dynamic solution sequences, if there is a LOADSET Case Control command, then SID must be
referenced in the LID field of a selected LSEQ entry. If there is no LOADSET Case Control
command, then SID must be referenced in the EXCITEID field of an RLOADi or TLOADi entry.
Main Index
ACCSSPT 1087
Access Point Definition
ACCSSPT Access Point Definition
Defines a grid interior to an external superelement whose motion will be retained in the residual structure of
the assembled superelement model. This entry is used during the external superelement creation run and is
valid only in external superelements.TR
Format:
1 2 3 4 5 6 7 8 9 10
ACCSSPT GID1 GID2 GIDi etc
Example:
ACCSSPT 117 119
Describer Meaning
GIDi Identification number of a grid point designated as an access point (Integer>0)
Remarks:
1. An access point may only be defined in an external superelement.
2. Access point IDs must be unique across all external superelements.
3. Access points must be interior points in the external superelement.
4. Access points will be automatically placed in the m-set of the residual structure of the assembly and
will have the same displacements in the residual structure as it does in the external superelement.
5. If the user needs the access points to be in the a-set, or if user needs to connect access points from
different superelements via MPCs, the following two parameters are required:
PARAM, SEP1XOVR, 128
PARAM, AUTOMSET, YES
6. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1088 ACIFPRM
Defines Parameters of Acoustic Conjugate Infinite Element
ACIFPRM Defines Parameters of Acoustic Conjugate Infinite Element
Defines parameters related to acoustic conjugate infinite elements.
Format:
1 2 3 4 5 6 7 8 9 10
ACIFPRM PARAM1 VAL1 PARAM2 VAL2
Example(s):
ACIFPRM TOLER 0.01
Field Contests
PARAMi Name of a parameter. Allowable names are given below (Character).
VALi Value of the parameter. See below (Real or Integer).
Name Description
TOLER Geometric Tolerance (Real > 0.0; Default=0.001)
The tolerance is used to detect if an acoustic field point, defined by BEGIN BULK AFPM,
falls within an infinite element. If not, Nastran will issue a user WARNING message, 3117,
and the acoustic results at the AFPM point (ACFPMRESULT) are not recovered (set to
zero).
EPTID1 Starting Identification Number of Extra Points to be Created (Integer > 0;
Default=200,000,000)
Remarks:
1. Only one ACIFPRM entry is allowed in the Bulk Data Section.
2. The default of EPTID1 generates the identification numbers of extra points with 9 digits.
Main Index
ACLOAD 1089
ACTRAN Acoustic Pressure Load Matrices for SOL 108/111
ACLOAD ACTRAN Acoustic Pressure Load Matrices for SOL 108/111
Defines ACTRAN acoustic pressure load matrices.
Format:
1 2 3 4 5 6 7 8 9 10
ACLOAD SID UNIT1 UNIT2 SCLR SCLI LSQID
Example(s):
ACLOAD 101 41 42 1.5
Field Contests
SID Set identification number. See Remark 1. (Integer > 0)
UNIT1 Fortran unit number of mapped data from ACTRAN. See Remark 2. (Integer > 0)
UNIT2 Fortran unit number of property matrices from ACTRAN. See Remark 2. (Integer > 0)
SCLR The real part of complex scale factor to be multiplied to ACTRAN matrices. (Real; Default
= 1.0)
SCLI The imaginary part of complex scale factor to be multiplied to ACTRAN matrices. (Real;
Default = 0.0)
LSQID Load SeQuence IDentification number on an ACTRAN file with multiple load cases.
(Integer > 0, default=1).
Remarks:
1. Dynamic excitation sets must be selected with the Case Control command DLOAD = SID for
frequency response analysis.
2. The following type of ASSIGN should be specified in the FMS section with the vacant unit number
(see ASSIGN statements). The unit number cannot be selected doubly.
ASSIGN INPUTT2=’ACTRAN_pressure.f70’ UNIT=41
ASSIGN INPUTT4=’ACTRAN_pressure.op4’ UNIT=42
3. SID must be unique for all RLOAD1, RLOAD2, ACSRCE and ACLOAD entries.
4. Refer the ACTRAN manual for the details of exportation of the acoustic pressure load matrix data
for Nastran.
5. The residual vectors for ACLOAD will not be computed.
6. Value of LSQID that is greater than the actual load cases in the ACTRAN file is a fatal error.
Main Index
1090 ACMODL
Fluid-Structure Interface Parameters
ACMODL Fluid-Structure Interface Parameters
Optional entry to define modeling parameters for Fluid-Structure Interface.
Note that ACMODL is not supported in NLPERF SOL 400.
Format:
(If METHOD=“BW”)
1 2 3 4 5 6 7 8 9 10
ACMODL INTER INFOR FSET SSET NORMAL METHOD SKNEPS DSKNEPS
INTOL ALLSSET SRCHUNIT
(If METHOD=“CP”)
ACMODL INTER INFOR FSET SSET NORMAL METHOD
Example(s):
ACMODL IDENT NORMAL
Describer Meaning
INTER Type of structure-fluid interface. (Character = “IDENT” or “DIFF”;
Default = “DIFF”)
INFOR For METHOD = “BW” or “BWKD” and INTER = “DIFF”,
indicates if FSET and SSET are used to define the fluid-structure
interface, “NONE” if not used, and whether they contain grids or
elements. (Character = “GRIDS”, “ELEMENTS”, “ALL”, or
“NONE”, Default = “NONE”)
For METHOD = “CP” and INTER = “DIFF”, indicates if FSET and
SSET are used to define the fluid-structure interface, “NONE” if not
used. See Remark 10. (Character = “ALL”, or “NONE”,
Default = “NONE”)
FSET Optional identification of a SET1 entry that contains a list of fluid
elements or grids on the fluid "skin". See Remark 2. If Modules are
present and the MDFSET entry is to be used instead of SET1 then set
FSET to -1. (Integer -1 or >0 or blank).
SSET Optional identification of a SET1 entry that contains a list of
structural elements or grids on the structure-fluid interface. See
Remark 2. If Modules are present and the MDSSET entry is to be used
instead of SET1 then set SSET to -1. (Integer -1 or >0 or blank).
NORMAL Fluid normal tolerance. See Remark 5. (Real; Default = 1.0 (Real; .001
for IDENT)
Main Index
ACMODL 1091
Fluid-Structure Interface Parameters
Describer Meaning
METHOD Character: Default = “BW”
“BW” = Body in White method
“BWKD” = Body in White Modified method with forces at fluid surface scaled.
See Remark 13.
“CP” = Closed Pressure Vessel Method. See Remarks 10. and 11.
SKNEPS Fluid skin growth tolerance. (Real; Default 0.5)
DSKNEPS Secondary fluid skin growth tolerance (Real; Default .75)
INTOL Tolerance of inward normal. (Real; Default .5)
ALLSSET If “NO” then SSET structure is searched and coupled if found. If
‘YES’ then all the structure given by SSET is coupled.
(Character = ‘YES’, or ‘NO’; Default = ‘NO’)
SRCHUNIT Search units. (Character=‘ABS’ for absolute model units or ‘REL’ for
relative model units based on element size; Default = ‘REL’)
Remarks:
1. Only one ACMODL entry is allowed. In general, for large irregular models, it is recommended that,
initially, this entry not be used, so the defaults will be applied.
2. For METHOD = “BW” and INTER = “DIFF” (Default), FSET and SSET refer to either grids or
elements as selected below. For INTER = “IDENT”, FSET and SSET refer to grids.
a. For INTER = “DIFF”, INFOR = “ELEMENTS”, for FSET, the search algorithm is restricted to
elements referenced by FSET. For SSET, the search algorithm is restricted to elements referenced
by SSET. This allows the user to de-select specific structural faces of a solid structural element.
Both these sets are optional and the user can have one without the other.
b. For INTER = “DIFF”, INFOR = “GRIDS”, for FSET, the search algorithm is restricted to grids
referenced by FSET. This allows the user to deselect fluid grids. Fluid grid selection is the only
way to deselect specific fluid faces. For SSET, the search algorithm is restricted to grids referenced
by SSET. This allows the user to de-select structural grids. Both these sets are optional and the
user can have one without the other.
c. For INTER = “IDENT”, INFOR = “ALL”, the points referenced by FSET and SSET must lie
exactly on the fluid-structure interface. These sets are optional, but if used, both must be present
or no fluid interface is calculated.
3. For INTER = “DIFF”, a .PCH file is created with a SET1 representing the fluid “skin” and a SET1
representing the structure interface. This file is useful for graphic post-processing for viewing the
interface. It also produces the sets that can be used as FSET and SSET.
Main Index
1092 ACMODL
Fluid-Structure Interface Parameters
4. For ALLSSET = ‘NO’ (default) the elements and grids determined by the couplings algorithm are
written to the .PCH file. The user can then deselect elements or grids as defined by the .PCH file by
editing them out of the SET1 entries defined in the file and referencing the edited SET1 with the
SSET. To add structural elements that the coupling algorithm did not include in the .PCH file, it is
not sufficient to just include them on the SET1 entry referenced by SSET. In addition,
ALLSSET = ‘YES’ must be specified.
5. NORMAL determines the height of the fluid box in the outward normal direction to the fluid
surface. The fluid box is used to locate the structural elements used in defining the fluid-structure
coupling matrix. If L is the smallest edge of the fluid element surface, then the height of the box is L
x NORMAL.
For INTER = “IDENT”, NORMAL = .001 is the default and represents a tolerance, in units of
length, used in determining the fluid-structure interface.
6. SKNEPS represents the enlargement of the plane of the fluid surface used to define the search box.
The diagonal distance from the center of the fluid surface to each surface grid is pushed out (diagonal
x (1. + SKNEPS)).
Search Box
NORMAL*L
INTOL*L
SKNEPS*D
7. DSKNEPS represents a secondary enlargement of the plane of the fluid surface used to define the
search box if SKNEPS fails to find ANY structural elements. The diagonal distance from the center
of the fluid surface to each surface grid is pushed out (diagonal x (1. + DSKNEPS)).
Main Index
ACMODL 1093
Fluid-Structure Interface Parameters
8. INTOL represents a normal direction into the fluid for the case when the fluid protrudes past the
structural interface. It is defined as L x INTOL where L is the smallest edge of the fluid element
surface.
9. The BW method is summarized in the following table:
Table of Fluid/Structure Search Control and Override METHOD=BW
INFOR Indicates the types of FSET and SSET entered
ELEMENTS Element sets are used to select element fluid and structure faces.
GRIDS Grid sets are used to select element fluid and structure faces.
FSET Fluid Set ID to delete or add fluid faces to fluid/structure interface
SSET Structure Set ID to delete or add structure faces to fluid/structure interface
ALLSET=NO Delete structural element faces
ALLSET=YES Add structural element faces
A SET specification will for the specified set given override any search parameters.
Caution: When deleting items from a set, especially structural element sets an element ID
may occur more than once and ALL must be removed.
SRCHUNIT REL Units are in the units of smallest fluid edge of current fluid face being
searched.
L = smallest fluid surface edge of element being searched.
D = Diagonal from center of fluid surface to each grid
NORMAL = NORMAL_value_input * L, Height of box +normal to
plane of fluid.
SKNEPS = D * (1.0 + SKNEPS_value_input), Search plane diagonals.
DSKNEPS = D * (1.0 + DSKNEPS_value_input) Secondary search plane
diagonals
DSKNEPS is only used when SKNEPS < DSKNEPS
INTOL = INTOL_value_input * L, Height of box -normal to plane of
fluid.
ABS Normal units are in the UNITS of the STRUCTURE. Use when distance
between the structure interface and the fluid interface is same constant
everywhere.
NORMAL = NORMAL_value_input* L, Height of box -normal to plane
of fluid. In ABS units.
SKNEPS = D * (1.0 + SKNEPS_value_input), Search plane diagonals. In
ABS units.
DSKNEPS = D * (1.0 + DSKNEPS_value_input), Secondary search
plane diagonals. In ABS units.
Main Index
1094 ACMODL
Fluid-Structure Interface Parameters
Table of Fluid/Structure Search Control and Override METHOD=BW
INTOL = INTOL_value_input * L, Height of box -normal to plane of
fluid. In ABS units.
ALLSSET NO Designed to take a modified PARAM SKINOUT PUNCH set and
DELETE elements from the STRUCTURE element set. Note if the
FLUID set has some deleted elements and the STRUCTURE set has
added elements this option may result in some change of structure
elements in the set and not keep the structural set UNMODIFIED. This
is because not all of the UNMODIFIED structure elements of the set
project with the reduced set of Fluid elements.
Recommended for only deleted structural elements.
YES Designed to take a modified PARAM SKINOUT PUNCH set and
ADD elements to the STRUCTURE element set. If some previously
found FLUID and STRUCTURE are also deleted the algorithm keeps all
the added structural set elements but will of course recomputed the
interface for the deleted boundary so that a sensible set intersection is
computed.
Recommended for the combination of deleted and added structural
elements or just added structural elements.
Coupling 1. Use the search box algorithm to locate the fluid free faces and the corresponding
Algorithm structural element faces.
2. For a fluid free face and its list of structural element faces (that were determined by
boxing normal to the fluid element) do as follows:
a. For each fluid free face establish a face coordinate system.
b. Determine the resultant pressure force for each grid on the fluid element.
c. Resolve this resultant pressure force for a unit grid pressure to the grids of the
fluid element. (Determined by principal virtual work).
d. Using the origin of the free fluid face, determine the center of pressure.
e. Using rigid body motion consider only a unit motion normal to the fluid face
with the appropriate moment relationships, determine the resulting load
distribution at the grids of each of the structural elements. The area of each
structural element projected normal to the fluid element is used as a weighting
function.
f. Loop over each grid of the fluid element and accumulate the forces at the
structural grids.
g. The algorithm always maintains of rigid body equilibrium.
3. Repeat for the next fluid element and its associated group of structural elements.
Accumulate the forces at the structural grids.
Guidelines 1. Run default ACMODL with PARAM , SKINOUT, PUNCH
Main Index
ACMODL 1095
Fluid-Structure Interface Parameters
Table of Fluid/Structure Search Control and Override METHOD=BW
2. View SETS both FLUID and STRUCTURE.
3. Adjust ACMODL search parameters until close to desired interface is obtained.
4. Modify the FSET, or SSET, or both to include and exclude Girds or Elements as
seems appropriate to get final coupling elements.
5. Run acoustic analysis with ACMODL using final FSET, SSET sets with
ALLSSET=YES if SSET contains both deleted and added elements. Or
ALLSSET=NO (default) if SSET contains only deleted elements.
6. The ABS option IS NOT RECOMMENDED for complex acoustic models such as
body in white models with multi contouring surfaces.
Parallel When there are "parallel" over lapping structural meshes, the search algorithm will pick an
Structural element of the closest mesh to the fluid face. All elements connected to this first element are
Element then checked to see if they are in the search box. Once and element, such as the elements of
Meshes in the outer parallel mesh, are found not to connect to the inner patch it is eliminated from the
the Search search. Thus outer patch elements tend to be excluded from the search unless some
Box connectivity to the inner patch is detected. The ALLSET=YES is to force an interface
between the listed structural elements and the nearest fluid faces.
10. The default METHOD is the “BW” searching algorithm that requires a special license.
The pre-Version 2004 method is selected with METHOD = “CP” in which:
• The search box is not used so the SKNEPS, DSKNEPS, INTOL, ALLSET, SRCHUNIT fields
are ignored.
• If INFOR = ‘ALL’ (METH = ‘CP’ only), then both FSET and SSET must be specified and
matching is checked at only those grid points referenced by FSET and SSET.
• FSET and SSET refer to grids.
• NORMAL = blank is the default (recommended), 1. < NORMAL < 10. gets acceptable results.
In this case, NORMAL represents a maximum cutoff value measured in physical units. When
NORMAL = ‘blank’, Nastran will compute the cutoff value.
This field replaces the pre-Version 2004 FSTOL field. Different units are also used so pre-Version
2004 FSTOL values may need to be changed to obtain the same results.
11. METH = ‘CP’ is not recommended when complex acoustic cavities (such as body in white
automotive models) exist in the model.
12. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1096 ACMODL
Fluid-Structure Interface Parameters
13. The “BWKD” method is essentially the same as the "BW" method with the exception that the forces
at the fluid surface are scaled (Knocked Down) by:
Areas of projected structural faces
F = F ---------------------------------------------------------------------------------------------- ,
Fluid face area
where Areas of projected structural faces < Fluid face area.
This method overcomes a complaint that the “BW” algorithm puts too much weight on the structural
grids for fluid grids far from the structural face.
While the set option removes the unwanted fluid grids, their removal can, on complex body in white
models be a complex and time-consuming task.
The Body in White Knocked Down method (BWKD) provides an alternative method that may
reduce the need to physically remove unwanted fluid grids with results close to their actual removal.
The BWKD method may also be used in conjunction with ACMODL parameter settings and set
definitions and may provide a more accurate fluid-structure interface result.
The new “BWKD” method can be evoked in one of two ways:
a. Enter the “BWKD” in the METHOD field (7) of the ACMODL entry.
b. With the new parameter, BWKD set to YES. This allows the user to make BWKD the default by
the following procedure:
This parameter maybe placed in an RC file to override the “BW” default on the ACMODL entry.
Then, it would appear as shown in the following file:
A .nastranrc - file with additional data
…
bwkd =yes
The user can also manually, at each job submittal, without using a .nastranrc - file by
specifying bwkd=yes on the NSC Nastran job submittal.
Main Index
ACPEMCP 1097
Trim Component Interface Coupling and Constraints Definition
ACPEMCP Trim Component Interface Coupling and Constraints Definition
Defines the interface coupling conditions and constraints of a trim component.
Format:
1 2 3 4 5 6 7 8 9 10
ACPEMCP TID SGLUED SSLIDE SOPEN SIMPER OOC SPM SAIRGAP
SCUX SCUY SCUZ SCRX SCRY SCRZ SCFP RID
CRIMSR CRIMFR
Example:
ACPEMCP 1 1002 1004
Describer Meaning
TID Identification number of trim component. (Integer>0; Required)
SGLUED Identification number of SET1/SET3 entry of grids belonging to the solid-phase and/or
structure volume elements in the trim component, which are glued to a structure; see
Remark 2. (Integer 0 or Blank)
SSLIDE Identification number of SET1/SET3 entry with grids belonging to the solid-phase and/or
structure volume elements in the trim component, which are in the sliding-contact to a
structure; see Remark 3. (Integer 0 or Blank)
SOPEN Identification number of SET1/SET3 entry of grids belonging to the fluid-phase elements
in the trim component, which has an open interface with the cavities; see Remark 4. (Integer
0 or Blank)
SIMPER Identification number of SET1/SET3 entry of grids of the solid-phase and/or structure
volume elements in the trim component, which has an impervious interface with the
cavities; see Remark 5. (Integer0 or Blank)
OOC Number of blocks for Out-Of-Core solver, see remark 8. (Integer≥1, Default=1)
SPM Flag for selecting single precision MUMPS for computing reduced impedance matrix, see
Remark 9. (Integer0 or Blank)
SAIRGAP Identification number of SET1/SET3 entry with grids belonging to the solid-phase and/or
structure volume elements in the trim component, which are in contact with structure via
air gap. See Remark 10. (Integer 0 or Blank)
SCUX ID of SET1/SET3 with which grid IDs in the trim component TID is zero-constrained in
translation X direction of output coordinate system. (Integer0 or Blank)
SCUY ID of SET1/SET3 with which grid IDs in the trim component TID is zero-constrained in
translation Y direction of output coordinate system. (Integer0 or Blank)
SCUZ ID of SET1/SET3 with which grid IDs in the trim component TID is zero-constrained in
translation Z direction of output coordinate system. (Integer0 or Blank)
Main Index
1098 ACPEMCP
Trim Component Interface Coupling and Constraints Definition
Describer Meaning
SCRX ID of SET1/SET3 with which grid IDs in the trim component TID is zero-constrained in
rotation X direction of output coordinate system. (Integer0 or Blank)
SCRY ID of SET1/SET3 with which grid IDs in the trim component TID is zero-constrained in
rotation Y direction of output coordinate system. (Integer0 or Blank)
SCRZ ID of SET1/SET3 with which grid IDs in the trim component TID is zero-constrained in
rotation Z direction of output coordinate system. (Integer0 or Blank)
SCFP ID of SET1/SET3 with which grid IDs in the trim component TID is zero-constrained in
fluid pressure.(Integer0 or Blank)
RID ID of a region of a TRMC. (Integer ≥ 0 or Blank).
CRIMSR Reduced Impedance Matrix Compression Ratio for coupling with structure (1.0 ≥ Real >
0.0, Default=1.0)
CRIMFR Reduced Impedance Matrix Compression Ratio for coupling with cavity (1.0 ≥ Real > 0.0,
Default=1.0)
Remarks:
1. ACPEMCP is a required entry for each trim component that is referenced by TRIMGRP. It must be
put in the main Bulk Data section or BEGIN BULK. It specifies the boundary coupling conditions
as well as the coupling degrees of freedom for computing the reduced boundary impedance matrices
of the trim component.
2. A glued interface means that the trim component is completely constrained on to the structure, such
as a car body. There is no relative movement between the trim component and the structure at the
interface.
3. A sliding interface means that the trim component is laid on the surface of structure, such as a car
body. There is no relative movement in the normal direction of the interface between the trim
component and the structure. Relative sliding movement is allowed in the contact surface.
4. An open interface means that the free flow of fluid between the fluid-phase and cavities occurs at the
interface.
5. An impervious or closed interface means that the fluid flow between the trim component and cavities
is prohibited at the interface. This can happen when the porous material is covered by a thin film
which stops the fluid flow or the cavity is in touch with a structure part of the trim component.
6. The SET1/SET3 entries must reside in the Bulk Data section introduced by Case Control, BEGIN
BULK TRMC.
7. Under current PEM implementation, only 3D elements are allowed for trim components. Hence,
SCRX, SCRY and SCRZ fields of ACPEMCP are not processed.
8. OOC is intended for large trim component. The number of OOC field defines the number of blocks
to be used for the Schur complement evaluation which reduces the memory requirement. A side effect
of OOC>1 is full RIM is generated, instead of lower triangular RIM, which is similar to
PARAM,PEMFRIM,1.
Main Index
ACPEMCP 1099
Trim Component Interface Coupling and Constraints Definition
9. SPM is a flag for selecting single precision MUMPS in ACTRAN. With default value of 0, double
precision MUMPS is utilized. Single precision MUMPS will be used with SPM field having value
greater 0. Single precision MUMPS has the benefits of reduced memory requirement and better
performance. However, single precision MUMPS may suffer minor degradation on accuracy.
10. An air gap interface means the trim component is assumed to be coupled to the structure through a
very thin air layer. The thin air layer is taken into the analysis without being modeled (not being
defined in the trim model file).
11. A TRMC can have many ACPEMCP entries. However, an ACPEMCP of a TRMC with blank RID
field is a must before ACPEMCP with non-blank RID can show up.
12. CRIMSR and CRIMFR compression ratios allow to reduce the size of the reduce impedance
matrices. This size reduction allows a significant memory disk usage reduction. This compression may
imply a loss of accuracy on results. A ratio of 1.0 means no compression. CRIMSR and CRIMFR
requires the modal approach to be selected for RIM (PARAM,TRMBIM,MODAL).
Main Index
1100 ACPMCP1
Analytical Trim Component Interface Coupling and Constraints Definition
ACPMCP1 Analytical Trim Component Interface Coupling and Constraints Definition
Defines the interface coupling conditions of a 1D analytical trim component.
Format:
1 2 3 4 5 6 7 8 9 10
ACPMCP1 TID SGLUED SSLIDE SOPEN SIMPER
RID
METHOD
Example:
ACPMCP1 1 1002 1004
1D
Describer Meaning
TID Identification number of a trim component. (Integer > 0; Required)
SGLUED Identification number of SET3 entry of PLTSURF surface mesh on the trim
component, which is glued to a structure. See Remark 2. (Integer ≥ 0 or Blank)
SSLIDE Identification number of SET3 entry of PLTSURF surface mesh on the trim
component, which are in the sliding contact to a structure; see Remark 3. (Integer ≥ 0 or
Blank)
SOPEN Identification number of SET3 entry of PLTSURF surface mesh on the trim
component, which has an open interface with the cavities. See Remark 4. (Integer ≥ 0 or
Blank)
SIMPER Identification number of SET3 entry of PLTSURF surface mesh on the trim
component, which has an impervious interface with the cavities; see Remark 5. (Integer
≥ 0 or Blank)
RID ID of a region of a TRMC. (Blank or Integer ≥ 0, Default=0)
METHOD Modeling method of analytical trim. (Character = “1D” or Blank)
Remarks
1. ACPMCP1 is a required entry for each 1D analytical trim component that is referenced by
TRIMGRP. It must be put in the main Bulk Data section or BEGIN BULK. It specifies the boundary
coupling conditions as well as the coupling degrees of freedom for computing the reduced impedance
matrices of the trim component.
Main Index
ACPMCP1 1101
Analytical Trim Component Interface Coupling and Constraints Definition
2. A glued interface means that the skeleton or solid-phase of a trim component is completely
constrained on to the structure. There is no relative movement between the trim component and the
structure at the interface (continuity of the displacement field). The reduction nodes of boundary
impedance matrices carry three degrees of freedom (Tx, Ty, Tz).
3. A sliding interface means that the trim component is laid on the surface of structure, such as a car
body. There is no relative movement in the normal direction of the interface between the trim
component and the structure. Relative sliding movement is allowed in the contact surface. However,
because of intrinsic analytical 1D trim assumption, if SSLIDE exists, they will be automatically
understood as SGLUED.
4. An open interface means that the free flow of fluid between the fluid-phase of a trim component and
cavities occurs at the interface (acoustic energy transfer).
5. An impervious or closed interface means that the fluid flowing between the trim component and
cavities is prohibited at the interface. This can happen when the porous material is covered by a thin
film which stops the fluid flowing or the cavity is in touch with a structure part of the trim
component. However, because of intrinsic analytical 1D trim assumption, if SIMPER exists, they will
be automatically understood as SOPEN.
Main Index
1102 ACSRCE
Acoustic Source Specification
ACSRCE Acoustic Source Specification
Defines acoustic source as a function of power vs. frequency.
1 8CP f i + 2f
Source Strength = A -------- --------------------- e
2f
C = B
Format:
1 2 3 4 5 6 7 8 9 10
ACSRCE SID EXCITEID DELAYI/ DPHASEI/ TP/RP RHO B
DELAYR DPHASER
Example:
ACSRCE 103 11 20 5.0 12 1.0 15.0
Describer Meaning
SID Load set identification number. See Remarks 1. and 3. (Integer > 0)
EXCITEID Identification number of DAREA, FBALOAD (in FRF Based Assembly or FBA
process) or SLOAD entry set the defines A . See Remark 6. (Integer > 0)
DELAYI Identification number of DELAY or FBADLAY (in FRF Based Assembly or FBA
process) Bulk Data entry that defines time delay . See Remarks 4. and 5. (Integer > 0
or blank)
DELAYR Value of time delay that will be used for all fluid degrees-of-freedom that are excited
by this dynamic load entry. See Remark 5. (Real or blank)
DPHASEI Identification number of DPHASE or FBAPHAS (in FRF Based Assembly or FBA
process) Bulk Data entry that defines phase angle . (See Remarks 4. and 5.
(Integer > 0 or blank)
DPHASER Value of phase angle (in degrees) that will be used for all fluid degrees-of-freedom
that are excited by this dynamic load entry. See Remark 5. (Real or blank)
TP Identification number of a TABLEDi entry that defines power versus frequency, P f .
(Integer > 0)
RP Value of power P to be used for all frequencies (Real, non-zero)
RHO Density of the fluid. (Real > 0.0)
B Bulk modulus of the fluid. (Real > 0.0)
Remarks:
1. Acoustic sources must be selected in the Case Control Section with DLOAD = SID.
2. For additional remarks, see the RLOAD1 entry description.
Main Index
ACSRCE 1103
Acoustic Source Specification
3. SID need not be unique for all ACSRCE, RLOAD1, RLOAD2, TLOAD1 and TLOAD2 dynamic
load entries. The DLOAD = SID Case Control command will select all dynamic load entries with
the set identification of SID.
4. The referenced EXCITEID, DELAY, and DPHASE entries must specify fluid points only.
5. If any of the DELAYI/DELAYR or DPHASEI/DPHASER fields are blank or zero, the corresponding
or will be zero.
6. If there is no LOADSET Case Control command, then EXCITEID may reference DAREA and
SLOAD entries. If there is a LOADSET Case Control command, then EXCITEID may reference
DAREA entries as well as SLOAD entries specified by the LID field in the selected LSEQ entry
corresponding to EXCITEID.
7. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1104 ACTRIM
ACTRAN Trimmed Material Matrices for SOL 108/111
ACTRIM ACTRAN Trimmed Material Matrices for SOL 108/111
Defines ACTRAN trimmed material matrices.
Format:
1 2 3 4 5 6 7 8 9 10
ACTRIM NAME UNIT1 UNIT2 SCLR SCLI
Example(s):
ACTRIM FLOOR 31 32 2.0 0.5
Field Context
NAME Name of the ACTRAN trimmed material matrices. See Remark 1. (One to eight
alphanumeric characters, the first of which is alphabetic)
UNIT1 Fortran unit number of mapped data from ACTRAN. See Remark 2. (Integer > 0)
UNIT2 Fortran unit number of property matrices from ACTRAN. See Remark 2. (Integer > 0)
SCLR The real part of complex scale factor to be multiplied to ACTRAN matrices. (Real; Default
= 1.0)
SCLI The imaginary part of complex scale factor to be multiplied to ACTRAN matrices. (Real;
Default = 0.0)
Remarks:
1. ACTRAN trimmed material matrices defined by this entry will be used for frequency response
analysis if it is selected via the Case Control ACTRIM = NAME.
2. The following type of ASSIGN should be specified in the FMS section with the vacant unit number
(see ASSIGN statements). The unit number cannot be selected doubly.
ASSIGN INPUTT2=’ACTRAN_trimmed.f70’ UNIT=31
ASSIGN INPUTT4=’ACTRAN_trimmed.op4’ UNIT=32
3. Refer the ACTRAN manual for the details of exportation of the trimmed material matrix data for
Nastran.
Main Index
ADUMi 1105
Dummy Element Attributes
ADUMi Dummy Element Attributes
Defines attributes of the dummy elements (3 < i < 9).
Format:
1 2 3 4 5 6 7 8 9 10
ADUMi NG NC NP ND ELNM
Example:
ADUM8 18 0 5 0 CRAC2D
Describer Meaning
NG Maximum number of grid points that may be connected by DUMi dummy element
(Integer>0.)
NC Number of additional fields (Ai) on the CDUMi connection entry. (Integer > 0)
NP Number of additional fields (Ai) on the PDUMi property entry. (24 > Integer > 0)
ND Number of displacement components at each grid point used in generation of the
differential stiffness matrix. Zero implies no differential stiffness. (Integer 3 or 6)
ELNM The name of the element connection and property entry. In the example above, the
connection entry is named “CRAC2D” and the property entry is named “PRAC2D”.
Remarks:
ADUM8 and ADUM9 are used exclusively for the CRAC2D and CRAC3D entries respectively.
Main Index
1106 AECOMP
Component for an Integrated Load Monitor Point
AECOMP Component for an Integrated Load Monitor Point
Defines a component for use in monitor point definition or external splines.
Format:
1 2 3 4 5 6 7 8 9 10
AECOMP NAME LISTTYPE LISTID1 LISTID2 LISTID3 LISTID4 LISTID5 LISTID6
LISTID7 -etc.-
Example:
AECOMP WING AELIST 1001 1002
Describer Meaning
NAME A character string of up to eight characters identifying the component. (Character)
LISTTYPE One of CAERO, AELIST or CMPID for aerodynamic components and SET1 for
structural components. Aerodynamic components are defined on the aerodynamic
ks-set mesh while the structural components are defined on the g-set mesh. See
Remarks 2. and 4.
LISTIDi The identification number of either SET1, AELIST or CAEROi entries that define
the set of grid points that comprise the component. See Remarks 2. and 4.
Remarks:
1. The Identification name must be unique among all AECOMP and AECOMPL entries.
2. If the component is defined on the structure, LISTIDs must refer to SET1 entry(ies) that define the
list of associated GRID points. For the AELIST or CAERO option, the LISTIDs must refer to
AELIST or CAERO i entries, respectively. Note that, for DLM models (CAERO1/2), the set of
points defined by the AELIST are the box identification numbers. For example, if the control
surface’s grids are desired, the same AELIST used for the AESURF can be referred to here. An
AECOMP component must be defined as either an aerodynamic mesh component or a structural
component. The two mesh classes cannot be combined into a single component.
3. The AECOMPL entry can be used to combine AECOMP entries into new components. When
combining components, the structural and aerodynamic classes must be kept separate.
4. If LISTTYPE = CMPID, LISTID1 identifies the associated set of AEQUAD4, AETRIA3 elements
that define the aero component.
Main Index
AECOMPL 1107
Component for an Integrated Load Monitor Point
AECOMPL Component for an Integrated Load Monitor Point
Defines a component for use in aeroelastic monitor point definition or external splines as a union of other
components.
Format:
1 2 3 4 5 6 7 8 9 10
AECOMPL NAME LABEL1 LABEL2 LABEL3 LABEL4 LABEL5 LABEL6 LABEL7
LABEL8 -etc.-
Example:
AECOMPL HORIZ STAB ELEV BALANCE
Describer Meaning
NAME A character string of up to eight characters Identifying the component. (Character)
LABELi A string of 8 characters referring to the names of other components defined by either
AECOMP or other AECOMPL entries.
Remarks:
1. The Identification name must be unique among all AECOMP and AECOMPL entries.
2. The AECOMPL entry can be used to combine AECOMP entries into new components. When
combining components, the structural and aerodynamic classes must be kept separate.
Main Index
1108 AEDW
Parametric Normal Wash Loading for Aerodynamics
AEDW Parametric Normal Wash Loading for Aerodynamics
Defines a downwash vector associated with a particular control vector of the associated aerodynamic
configuration (AECONFIG). From this downwash vector, a force vector on the aerodynamic grids will be
defined for use in nonlinear static aeroelastic trim.
Format:
1 2 3 4 5 6 7 8 9 10
AEDW MACH SYMXZ SYMXY UXID DMIJ DMIJI
Example:
AEDW 0.90 SYMM ASYMM 101 ALP1
Describer Meaning
MACH The Mach number for this force, see Remark 2. (Real 0.0, 1.0)
SYMXZ,SYMXY The symmetry of this force vector. One of SYMM, ASYMM or ANTI (Character).
UXID The identification number of a UXVEC entry that defines the control parameter
vector associated with this downwash vector.
DMIJ The name of a DMI or DMIJ entry that defines the downwash.
DMIJI The name of a DMIJI entry that defines the CAERO2 interference element
“downwashes”.
Remarks:
1. The AEDW, AEFORCE and AEPRESS are associated with the current AECONFIG using either
Case Control (if in the main Bulk Data Section) or using the BEGIN AECONFIG=<config> if in a
partition of the Bulk Data.
2. The DMIJ field refers to either a DMI or a DMIJ entry. The DMIJI is only applicable to CAERO2
and is only required if nonzero “downwash” (j-set) input is needed on the interference body elements.
3. Mach numbers > 1.0 require that the supersonic aerodynamic option be available.
Main Index
AEFACT 1109
Aerodynamic Lists
AEFACT Aerodynamic Lists
Defines real numbers for aeroelastic analysis.
Format:
1 2 3 4 5 6 7 8 9 10
AEFACT SID D1 D2 D3 D4 D5 D6 D7
D8 D9 -etc.-
Example:
AEFACT 97 .3 .7 1.0
Describer Meaning
SID Set identification number. (Unique Integer > 0)
Di Number. (Real)
Remarks:
1. AEFACT entries must be selected by a CAEROi, PAEROi or SPLINEX entry.
2. Embedded blank fields are not allowed.
3. To specify division points, there must be one more division point than the number of divisions.
4. When referenced by the CAERO3 entry, AEFACT defines the aerodynamic grid points. The ID
number of the first point defined by each AEFACT entry is the value of the CAERO3 ID that selected
the AEFACT entry. The ID of each following point defined on the AEFACT is incremented by 1.
Main Index
1110 AEFORCE
Parametric Force for Aerodynamics
AEFORCE Parametric Force for Aerodynamics
Defines a vector of absolute or “per unit dynamic pressure” forces associated with a particular control vector.
This force vector may be defined on either the aerodynamic mesh (ks-set) or the structural mesh (g-set). The
force vector will be used in static aeroelastic trim.
Format:
1 2 3 4 5 6 7 8 9 10
AEFORCE MACH SYMXZ SYMXY UXID MESH LSET DMIK PERQ
Example:
AEFORCE 0.90 SYMM ASYMM 101 AERO BETA
Describer Meaning
MACH The Mach number for this force. (Real 0.0, 1.0)
SYMXZ,SYMXY The symmetry conditions for this force vector. One of SYMM, ASYMM or ANTI.
(Character)
UXID The identification number of a UXVEC entry that defines the control parameter
vector associated with this force vector.
MESH One of AERO or STRUCT that declares whether the force vector is defined on the
aerodynamic ks-set mesh or the structural g-set mesh.
LSET SID of a load set that defines the vector. See Remark 2. (Integer > 0 if
MESH=STRUCT)
DMIK The name of a DMIK entry that defines the aerodynamic force vector. See Remark
3. (Character; Required if MESH=AERO)
PERQ The string PERQ or blank. If PERQ and MESH=STRUCT, the input FORCE set
is multiplied by the dynamic pressure. (Default = blank; see Remark 4.)
Remarks:
1. The AEFORCE is associated with the current AECONFIG and must be entered for the appropriate
Mach numbers and aerodynamic symmetries.
2. For the STRUCT mesh option, the LSET can refer to any existing load type (e.g., FORCE1,
PLOAD4 or LOAD) that is available to define static loads.
3. For the AERO mesh option, the DMIK Bulk Data are used. Any forces associated with the
aerodynamic model’s permanently SPC’d degrees-of-freedom (which are dependent on the type of
aerodynamic model being used) will be ignored.
4. For the AERO mesh option, the PERQ field is not used. The FORCE data input on the DMIK entry
is always multiplied by dynamic pressure.
5. When STRUCT mesh option is used the integrated loads output for aerodynamic monitor points are
not meaningful.
Main Index
AEGRID 1111
Aerodynamic Grid Point
AEGRID Aerodynamic Grid Point
Defines the location of an aerodynamic grid point.
Format:
1 2 3 4 5 6 7 8 9 10
AEGRID GID CP X1 X2 X3 CD ASID
Example:
AEGRID 1 1 2.1 3.2 2.0 3 4
Describer Meaning
GID Grid Point Identification Number (0 < Integer < 100,000,000)
CP Identification number of a coordinate system in which the location of the grid point is
defined. (Integer > 0 or blank)
X1, X2, X3 Location of the grid point in the coordinate system CP.
CD Identification number of coordinate system in which the degrees-of-freedom of the grid
point are defined. (Integer > 0 or blank)
ASID Identification number of an AESCALE Bulk Data entry. (Integer > 0 or blank)
Remarks:
1. All grid point identification numbers must be unique with respect to all other aerodynamic grid point
identification numbers.
2. If both CP and ASID are defined, coordinates are first scaled and subsequently transformed to the
basic coordinate system.
3. The meaning of X1, X2 and X3 depends on the type of coordinate system CP. (See Remark 2 of the
GRID entry).
4. A zero or blank in the CP and CD fields refers to the basic coordinate system.
5. The AEGRID, AETRIA3, AEQUAD4, and AESCALE entries provide an aerodynamic mesh in a
readable, portable format. There are no internal aerodynamics created on this mesh.
Main Index
1112 AELINK
Links Aeroelastic Variables
AELINK Links Aeroelastic Variables
Defines relationships between or among AESTAT and AESURF entries, such that:
n
D I
u + Ci u i = 0.0
i=1
Where:
D
u = dependent variable
I
u i = independent variable
Format:
1 2 3 4 5 6 7 8 9 10
AELINK ID LABLD LABL1 C1 LABL2 C2 LABL3 C3
LABL4 C4 -etc.-
Example:
AELINK 10 INBDA OTBDA -2.0
Describer Meaning
ID If an integer > 0 is specified, this is the TRIM set ID selected in Case Control and the
AELINK only applies to that subcase. If an integer value of 0 or the character string
“ALWAYS” is specified, this AELINK is applicable to all subcases. (Integer > 0 or the
“ALWAYS” character string.)
LABLD Character string to identify the dependent aerodynamic variable. (Character)
LABLi Character string to identify the i-th independent aerodynamic variable. (Character)
Ci Linking coefficient for the i-th variable. (Real)
Remarks:
1. If the ID is a positive integer, the AELINK entry (or entries) is selected by the TRIM=ID in Case
Control.
2. If the ID is 0 or the character string ALWAYs, the linking relationship applies to all subcases.
3. The entry constrains the dependent variable to be a linear combination of the independent variables.
4. LABLD data must be unique for a given ID or if ID=0 or AWAYS is being used (i.e., the variable
cannot be constrained more than once).
5. LABLD and LABLi refer to AEPARM, AESTAT or AESURF Bulk Data entries.
Main Index
AELIST 1113
Aerodynamic List
AELIST Aerodynamic List
Defines a list of aerodynamic elements or grid ID’s.
Format:
1 2 3 4 5 6 7 8 9 10
AELIST SID E1 E2 E3 E4 E5 E6 E7
E8 -etc.-
Example:
AELIST 75 1001 THRU 1075 1101 THRU 1109 1201
1202
Describer Meaning
SID Set identification number. (Integer > 0)
Ei List of aerodynamic box ID's or aerodynamic grid ID's (Integer>0 or "THRU")
Remarks:
1. The AELIST entry can be referenced by AESURF, AECOMP, SPLINEi, SPLINRB, SPBLND2 and
SPRELAX entries. Refer to these entries for the meaning of the data provided.
2. When the “THRU” option is used, all intermediate grid points must exist. The word “THRU” may
not appear in field 3 or 9 (2 or 9 for continuations).
3. Intervening blank fields are not allowed.
Main Index
1114 AELISTC
Character Item List
AELISTC Character Item List
Defines a list of 8-character strings.
Format:
1 2 3 4 5 6 7 8 9 10
AELISTC SID C1 C2 C3 C4 C5 C6 C7
C8 -etc.-
Example:
AELISTC 101 FBS STRING12
Describer Meaning
SID Set identification number. (Integer > 0)
Ci List of 8-character strings.
Remark:
1. Intervening blank fields are not allowed.
Main Index
AEPARM 1115
General Controller for Use in Trim
AEPARM General Controller for Use in Trim
Defines a general aerodynamic trim variable degree-of-freedom (aerodynamic extra point). The forces
associated with this controller will be derived from AEDW, AEFORCE and AEPRESS input data.
Format:
1 2 3 4 5 6 7 8 9 10
AEPARM ID LABEL UNITS
Example:
AEPARM 5 THRUST LBS
Describer Meaning
ID Controller identification number. (Integer > 0)
LABEL Controller name. See Remark 1. (Character)
UNITS Label used to describe the units of the controller values. (Character)
Remarks:
1. Controller LABELs that comprise the unique set relative to all the AESURF, AESTAT and AEPARM
entries will define the set of trim variable degrees-of-freedom for the aeroelastic model.
2. Unit labels are optional and are only used to label outputs. No units will be associated with the
controller if left blank.
Main Index
1116 AEPRESS
Parametric Pressure Loading for Aerodynamics
AEPRESS Parametric Pressure Loading for Aerodynamics
Defines a vector of pressure/unit dynamic pressure associated with a particular control vector. From this
pressure vector, a force vector on the aerodynamic grids will be defined for use in nonlinear static aeroelastic
trim.
Format:
1 2 3 4 5 6 7 8 9 10
AEPRESS MACH SYMXZ SYMXY UXID DMIJ DMIJI
Example:
AEPRESS 0.90 SYMM ASYMM 101 ALP1
Describer Meaning
MACH The Mach number for this force, see Remark 2. (Real 0.0, 1.0)
SYMXZ,SYMXY The symmetry of this force vector. One of SYMM, ASYMM or ANTI.
(Character)
UXID The identification number of a UXVEC entry that defines the control
parameter vector associated with this pressure vector.
DMIJ The name of a DMI or DMIJ entry that defines the pressure per unit dynamic
pressure.
DMIJI The name of a DMIJI entry that defines the CAERO2 interference element
“downwashes”.
Remarks:
1. The AEDW, AEFORCE, and AEPRESS are associated with the current AECONFIG using Case
Control.
2. Mach numbers > 1.0 require that the supersonic aerodynamic option be available.
3. The DMIJ field refers to either a DMI or a DMIJ entry. The DMIJI is only applicable to CAERO2
and is only required if nonzero “downwash” (j-set) input is needed on the interference body elements.
Main Index
AEQUAD4 1117
Quadrilateral Aerodynamic Element Connection
AEQUAD4 Quadrilateral Aerodynamic Element Connection
Defines the connectivity of a quadrilateral aerodynamic element.
Format:
1 2 3 4 5 6 7 8 9 10
AEQUAD4 EID CMPID G1 G2 G3 G4
Example:
AEQUAD4 100 2 12 32 41 50
Describer Meaning
EID Element Identification Number. (0 < Integer < 100,000,000)
CMPID Aerodynamic Component Identification Number. (Integer > 0)
Gi Grid Point Identification Numbers of Connection Points. (Integer > 0)
Remarks:
1. The geometry of a quadrilateral aerodynamic element may collapse to a triangle, i.e., two connection
points may have the same geometric location. However, all four grid point identification numbers
must be different.
2. The AEGRID, AETRIA3, AEQUAD4, and AESCALE entries provide an aerodynamic mesh in a
readable, portable format. There are no internal aerodynamics created on this mesh.
Main Index
1118 AERO
Aerodynamic Physical Data
AERO Aerodynamic Physical Data
Gives basic aerodynamic parameters for unsteady aerodynamics.
Format:
1 2 3 4 5 6 7 8 9 10
AERO ACSID VELOCITY REFC RHOREF SYMXZ SYMXY
Example:
AERO 3 1.3+4 100. 1.-5 1 -1
Describer Meaning
ACSID Aerodynamic coordinate system identification. See Remark 2. (Integer > 0; Default is
the basic coordinate system)
VELOCITY Velocity for aerodynamic force data recovery and to calculate the BOV parameter. See
Remark 5. (Real>0.0 or blank)
REFC Reference length for reduced frequency. (Real > 0.0)
RHOREF Reference density. (Real > 0.0)
SYMXZ Symmetry key for the aero coordinate x-z plane. See Remark 6. (Integer = +1 for
symmetry, 0 for no symmetry, and -1 for antisymmetry; Default = 0)
SYMXY The symmetry key for the aero coordinate x-y plane can be used to simulate ground
effect. (Integer = -1 for symmetry, 0 for no symmetry, and +1 for antisymmetry;
Default = 0)
Remarks:
1. This entry is required for aerodynamic problems. Only one AERO entry is allowed.
2. The ACSID must be a rectangular coordinate system. Flow is in the positive x-direction.
3. Set SYMXY = -1 to simulate ground effect.
4. PARAM,WTMASS does not affect aerodynamic matrices. RHOREF must be input in mass units.
5. VELOCITY is used only in aeroelastic response analysis, and it must be equal to V on the GUST
Bulk Data entry.
6. The symmetry fields on this entry are only used if neither of the Case Control commands
(AESYMXY, AESYMXZ) are supplied. If either Case Control command is supplied, even the defaults
from Case will override these Bulk Data entries. The Case Control symmetry is the preferred means
of declaring the flow and geometric symmetry for aeroelastic analysis.
Main Index
AEROS 1119
Static Aeroelasticity Physical Data
AEROS Static Aeroelasticity Physical Data
Defines basic parameters for static aeroelasticity.
Format:
1 2 3 4 5 6 7 8 9 10
AEROS ACSID RCSID REFC REFB REFS SYMXZ SYMXY
Example:
AEROS 10 20 10. 100. 1000. 1
Describer Meaning
ACSID Aerodynamic coordinate system identification. See Remark 2. (Integer > 0; Default is
the basic coordinate system)
RCSID Reference coordinate system identification for rigid body motions. (Integer > 0;
Default is the basic coordinate system)
REFC Reference chord length. (Real > 0.0)
REFB Reference span. (Real > 0.0)
REFS Reference wing area. (Real > 0.0)
SYMXZ Symmetry key for the aero coordinate x-z plane. See Remark 6. (Integer = +1 for
symmetry, 0 for no symmetry, and -1 for antisymmetry; Default = 0)
SYMXY The symmetry key for the aero coordinate x-y plane can be used to simulate ground
effects. (Integer = +1 for antisymmetry, 0 for no symmetry, and -1 for symmetry;
Default = 0)
Remarks:
1. This entry is required for static aeroelasticity problems. Only one AEROS entry is allowed.
2. The ACSID must be a rectangular coordinate system. Flow is in the positive x-direction (T1).
3. The RCSID must be a rectangular coordinate system. All AESTAT degrees-of-freedom defining trim
variables will be defined in this coordinate system.
4. REFB should be full span, even on half-span models.
5. REFS should be half area on half-span models.
6. The symmetry fields on this entry are only used if neither of the Case Control commands
(AESYMXY, AESYMXZ) are supplied. If either Case Control command is supplied, even the defaults
from Case will override these Bulk Data entries. The Case Control symmetry is the preferred means
of declaring the flow and geometric symmetry for aeroelastic analysis.
Main Index
1120 AESCALE
Aerodynamic Grid Point Scaling
AESCALE Aerodynamic Grid Point Scaling
Defines reference lengths to scale aerodynamic grid points.
Format:
1 2 3 4 5 6 7 8 9 10
AESCALE ASID X1REF X2REF X3REF
Example:
AESCALE 100 1 1 1
Describer Meaning
ASID Identification Number called out on an AEGRID entry. (0 < Integer < 100,000,000)
X1REF Reference length to scale X1. (Real or blank; Default = 1.0)
X2REF Reference length to scale X2. (Real or blank; Default = 1.0)
X3REF Reference length to scale X3. (Real or blank; Default = 1.0)
Remark:
1. The scaled coordinates are computed from XiS = Xi XiREF .
2. The AEGRID, AETRIA3, AEQUAD4, and AESCALE entries provide an aerodynamic mesh in a
readable, portable format. There are no internal aerodynamics created on this mesh.
Main Index
AESTAT 1121
Static Aeroelasticity Trim Variables
AESTAT Static Aeroelasticity Trim Variables
Specifies rigid body motions to be used as trim variables in static aeroelasticity.
Format:
1 2 3 4 5 6 7 8 9 10
AESTAT ID LABEL
Example:
AESTAT 5001 ANGLEA
Describer Meaning
ID Identification number of an aerodynamic trim variable degree-of-freedom. See Remark
1. (Integer > 0)
LABEL An alphanumeric string of up to eight characters used to identify the degree-of-
freedom. See Remark 1. (Character)
Remarks:
1. The degrees-of-freedom defined with this entry represent rigid body motion in the reference
coordinate system defined on the AEROS entry. The standard labels that define the various rigid
body motions are as follows:
Table 1 Standard Labels Defining Rigid Body Motions
LABEL Degree-of-Freedom Motion Description
ANGLEA ur (R2) Angle of Attack
SIDES ur (R3) Angle of Sideslip
ROLL u· r (R1) Roll Rate = pb/2V
PITCH u· r (R2) Pitch Rate = qc/2V
YAW u· r (R3) Yaw Rate = rb/2V
URDD1 u··r (T1) Longitudinal (See Remark 3.)
URDD2 u··r (T2) Lateral
URDD3 u··r (T3) Vertical
URDD4 u··r (R1) Roll
URDD5 u··r (R2) Pitch
URDD6 u··r (R3) Yaw
Main Index
1122 AESTAT
Static Aeroelasticity Trim Variables
These reserved names may be defined on the AEPARM entry instead, in which case the incremental
load due to the unit perturbation of the rigid body degree-of-freedom is not created. (See the
AEPARM, AEPRESS, and AEFORCE entries.)
2. The degrees-of-freedom defined with this entry are variables in the static aeroelastic trim solution,
unless they are constrained by referencing them with a TRIM Bulk Data entry.
3. If a label other than those above is specified, then the user must either generate the corresponding
forces with an AELINK or via a DMI Bulk Data entry along with a DMAP alter that includes the
DMIIN module and additional statements to merge into the appropriate matrices. Or, using
AEPARM and the AEDW, AEPRESS, and/or AEFORCE, you can accomplish this purpose without
the need for any alters.
Main Index
AESURF 1123
Aerodynamic Control Surface
AESURF Aerodynamic Control Surface
Specifies an aerodynamic control surface as a member of the set of aerodynamic extra points. The forces
associated with this controller will be derived from rigid rotation of the aerodynamic model about the hinge
line(s) and from AEDW, AEFORCE and AEPRESS input data. The mass properties of the control surface
can be specified using an AESURFS entry.
Format:
1 2 3 4 5 6 7 8 9 10
AESURF ID LABEL CID1 ALID1 CID2 ALID2 EFF LDW
CREFC CREFS PLLIM PULIM HMLLIM HMULIM TQLLIM TQULIM
Example:
AESURF 6001 ELEV 100 100 200 200
10.0 180.0 -1.4E4 1.2E4 20 30
Describer Meaning
ID Controller identification number. (Integer > 0)
LABEL Controller name. (Character)
CIDi Identification number of a rectangular coordinate system with a y-axis that defines
the hinge line of the control surface component. (Integer > 0)
ALIDi Identification of an AELIST Bulk Data entry that identifies all aerodynamic
elements that make up the control surface component. (Integer > 0)
EFF Control surface effectiveness. See Remark 4. (Real 0.0; Default = 1.0)
LDW Linear downwash flag. See Remark 2. (Character, one of LDW or NOLDW;
Default = LDW).
CREFC Reference chord length for the control surface. (Real > 0.0; Default = 1.0)
CREFS Reference surface area for the control surface. (Real > 0.0; Default = 1.0)
PLLIM,PULIM Lower and upper deflection limits for the control surface in radians. (Real, Default
= ± /2)
HMLLIM,HMULI Lower and upper hinge moment limits for the control surface in force-length units.
M (Real; Default = no limit)
TQLLIM,TQULIM Set identification numbers of TABLEDi entries that provide the lower and upper
deflection limits for the control surface as a function of the dynamic pressure.
(Integer > 0; Default = no limit)
Main Index
1124 AESURF
Aerodynamic Control Surface
Remarks:
1. The ID on AESURF, AESTAT, and AEPARM entries are ignored. AESURFS can be used to define
mass properties of the control surface.
2. The degrees-of-freedom defined on this entry represent a rigid body rotation of the control surface
components about their hinge lines. In the default LDW (Linear DownWash) case, the downwash
due to a unit perturbation of the control surface will be computed as part of the database. In the
NOLDW case, the user must prescribe the controller’s effects by direct definition of the induced
forces using the AEPRESS, AEDW and/or AEFORCE entries.
3. Either one or two control surface components may be defined.
4. If EFF is specified, then the forces produced by this surface are modified by EFF (e.g., to achieve a
40% reduction, specify EFF=0.60).
5. The continuation is not required.
6. The CREFC and CREFS values are only used in computing the nondimensional hinge moment
coefficients.
7. Position limits may be specified using either PiLIM or TQiLIM, but not both.
8. Position and hinge moment limits are not required.
Main Index
AESURFS 1125
Structural Grids on an Aerodynamic Control Surface
AESURFS Structural Grids on an Aerodynamic Control Surface
Optional specification of the structural nodes associated with an aerodynamic control surface that has been
defined on an AESURF entry. The mass associated with these structural nodes define the control surface
moment(s) of inertia about the hinge line(s).
Format:
1 2 3 4 5 6 7 8 9 10
AESURFS ID LABEL LIST1 LIST2
Example:
AESURFS 6001 ELEV 6002 6003
Describer Meaning
ID Controller identification number, see Remark 1. (Integer > 0)
LABEL Controller name, see Remark 1. (Character)
LISTi Identification number of a SET1 entry that lists the structural grid points that are
associated with this component of this control surface. (Integer > 0)
Remarks:
1. The LABEL on the AESURFS entry must match one on an AESURF entry. The ID is ignored.
2. The mass of the GRID points listed on the SETi entries is used to compute the mass moment of
inertia of the control surface about its i-th hinge line. The presence of these data will allow the hinge
moments to include the inertial forces in the computations. These data are optional, and, if omitted,
result in hinge moments which include only the applied, aeroelastically corrected, forces.
3. These data will be associated to a structural superelement by grid list or partitioned SUPER=<seid>
if the AESURFS is defined in the main bulk data section.
Main Index
1126 AETRIA3
Triangular Aerodynamic Element Connection
AETRIA3 Triangular Aerodynamic Element Connection
Defines the connectivity of a triangular aerodynamic element.
Format:
1 2 3 4 5 6 7 8 9 10
AETRIA3 EID CMPID G1 G2 G3
Example:
AETRIA3 3768 8 368 872 999
Describer Meaning
EID Element Identification Number. (0 < Integer < 100,000,000)
CMPID Aerodynamic Component Identification Number. (Integer > 0)
Gi Grid Point Identification Numbers of Connection Points. (Integer > 0)
Remarks:
1. The AEGRID, AETRIA3, AEQUAD4, and AESCALE entries provide an aerodynamic mesh in a
readable, portable format. There are no internal aerodynamics created on this mesh.
Main Index
ASET 1127
Degrees-of-Freedom for the a-set
ASET Degrees-of-Freedom for the a-set
Defines degrees-of-freedom in the analysis set (a-set).
Format:
1 2 3 4 5 6 7 8 9 10
ASET ID1 C1 ID2 C2 ID3 C3 ID4 C4
Example:
ASET 16 2 23 3516 1 4
Describer Meaning
IDi Grid or scalar point identification number. (Integer > 0)
Ci Component numbers. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points with no embedded blanks.)
Remarks:
1. Degrees-of-freedom specified on this entry form members of the mutually exclusive a-set. They may
not be specified on other entries that define mutually exclusive sets. See Degree-of-Freedom Sets for a
list of these entries.
2. When ASET, ASET1, QSET, and/or QSET1 entries are present, all degrees-of-freedom not
otherwise constrained (e.g., SPCi or MPC entries) will be placed in the omitted set (o-set).
3. In nonlinear analysis, all degrees-of-freedom attached to nonlinear elements must be placed in the
a-set. In other words, if the ASET or ASET1 entry is specified then all nonlinear degrees-of-freedom
must be specified on the ASET or ASET1 entry.
4. SOL 400 does not support OMITAX as well as ASETi, OMITi, BSETi, CSETi, SUPORTi, and
QSETi except in the following situations:
a. Multidisciplinary (linear) analysis. See Remark 3-e. under the ANALYSIS Case Control
command regarding “Standard linear physics”. This means there are no subcases for nonlinear
analysis using ANALYSIS=NLSTATICS, NLTRAN, HSTAT or HTRAN.
b. Linear perturbation with:
i. EXTSEOUT Case Control command for external superelement creation. This includes runs
with AVLEXB Case Control command.
ii. ADAMSMNF Case Control command. The ASETi/ QSETi entries must be specified in the
BEGIN BULK FLXBDY section. See Remark 21. under the ADAMSMNF Case Control
command.
c. Superelements defined with BEGIN SUPER may contain ASETi, OMITi, BSETi, CSETi, and
QSETi entries.
Main Index
1128 ASET
Degrees-of-Freedom for the a-set
5. ASET can be used to specify the boundary points of the external module created by the
EXTMDOUT Case Control command. In this case, this entry must be specified in the main Bulk
Data section.
Main Index
ASET1 1129
Degrees-of-Freedom For the a-set, Alternate Form of ASET Entry
ASET1 Degrees-of-Freedom For the a-set, Alternate Form of ASET Entry
Defines degrees-of-freedom in the analysis set (a-set).
Format:
1 2 3 4 5 6 7 8 9 10
ASET1 C ID1 ID2 ID3 ID4 ID5 ID6 ID7
ID8 ID9 ID10 -etc.-
Example:
ASET1 345 2 1 3 10 9 6 5
7 8
Alternate Format and Example:
ASET1 C ID1 “THRU” ID2
ASET1 123456 7 THRU 109
Describer Meaning
C Component number. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points with no embedded blanks.)
IDi Grid or scalar point identification numbers. (Integer > 0; for THRU option,
ID1 < ID2)
Remarks:
1. Degrees-of-freedom specified on this entry form members of the a-set that is exclusive from other sets
defined by Bulk Data entries. See Degree-of-Freedom Sets for a list of these entries.
2. When ASET, ASET1, QSET, and/or QSET1 entries are present, all degrees-of-freedom not
otherwise constrained (e.g., SPCi or MPC entries) will be placed in the omitted set (o-set).
3. If the alternate format is used, all points in the sequence ID1 through ID2 are not required to exist,
but there must be at least one degree-of-freedom in the a-set for the model, or a fatal error will result.
Any points implied in the THRU that do not exist will collectively produce a warning message but
will otherwise be ignored.
4. In nonlinear analysis, all degrees-of-freedom attached to nonlinear elements must be placed in the
a-set. In other words, if the ASET or ASET1 entry is specified then all nonlinear degrees-of-freedom
must be specified on the ASET or ASET1 entry.
5. SOL 400 does not support OMITAX as well as ASETi, OMITi, BSETi, CSETi, SUPORTi, and
QSETi except in some situations (See Remark 4. under ASET).
Main Index
1130 ASET1
Degrees-of-Freedom For the a-set, Alternate Form of ASET Entry
6. ASET1 can be used to specify the boundary points of the external module created by the
EXTMDOUT Case Control command. In this case, this entry must be specified in the main Bulk
Data section.
Main Index
ATBACC 1131
Acceleration Field applied to ATB Segments- SOL 700
ATBACC Acceleration Field applied to ATB Segments- SOL 700
Defines an acceleration field that will be applied to ATB segments. Used in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
ATBACC LID SCALE NX NY NZ
+ NAME1 NAME2 NAME3 NAME4 NAME5 NAME6 NAME7 NAMEi
Example:
ATBACC 32 386.088 1.0 0.0 0.0 0 0
+ LT MT UT N H RUL RLL
Field Content
LID Number of a set of loads. (Integer > 0; required)
SCALE ATBACC scale factor. (Real ≥ 0.0; default=1.0)
NX, NY, NZ Components of gravity vector. At least one component must be nonzero. (Real;
default=0.0)
NAMEi Name of an ATB segment as given in the first field of a B.2 entry in the ATB input
file. (Character; required)
Remarks:
1. The acceleration is defined as:
t = T t .SCALE. N
where SCALE is the acceleration scale factor; is the vector defined by NX, NY, and NZ; is the value
interpolated at time from the table referenced by the TLOADn entry.
2. LID must be referenced by a TLOADn entry.
3. The type field on the TLOADn entry must be set to zero.
4. More than one ATBACC acceleration field can be defined per problem.
5. This acceleration field is intended to apply a crash pulse to ATB segments that define a crash dummy.
The acceleration is multiplied by the mass of the segment and the resulting force is added as an
external force.
6. To compare the accelerations of the ATB segments to experiments, the crash pulse needs to be
subtracted from the total acceleration. The acceleration of the segments as defined on the H1 entries
in the ATB input file are automatically corrected.
Main Index
1132 ATBJNT
Interface to ATB Joints- SOL 700
ATBJNT Interface to ATB Joints- SOL 700
This entry can only be used together with the ATBSEG entries that this joint connects. The ATBSEG entries
overwrite the position and orientation of the ATB segments as specified in the ATB input file. The ATBJNT
entry can be used to create a Bulk Data file containing elements and grid points to visualize the ATB segment
together with its joints. This visualization of the joints makes it possible to position the ATB model in any
available preprocessor. Used in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
ATBJNT ID NAME
+ G0 G1 G2 G3 EID1 EID2 EID3
+ G4 G5 G6 G7 EID4 EID5 EID6
Example:
ATBJNT 1 HN
+ 1010 1011 1012 1013 1004 1005 1006
+ 2010 2011 2012 2013 2004 2005 2006
Field Content
LID Unique ATBJNT number. (Integer > 0; required)
NAME Name of an ATB joint as given in the first field of a B.3 entry in the ATB input file.
(Character; required)
G0~G7 An ATB joint connects two segments. A local joint coordinate system is attached to
each of these two segments. The position and orientation of these two coordinate
systems relative to the segment coordinate systems is given on entry B.3 in the ATB
input file. For each joint (J = 1, NJNT) a B.3 entry is defined in the ATB input file.
The joint J connects the segment JNT(J) as given on the B.3 entry and the segment J
+ 1. SOL700 finds the two segments that are connected by the joint with name =
NAME. The grid points G0-G3 and G4-G7 define the joint coordinate systems for
the segments JNT(J) and J + 1, respectively. (Integer > 0; required)
G0 located at the origin of the joint coordinate system for the ATB segment
JNT (J)
G1 located on the local x-axis.
G2 located on the local y-axis.
G3 located on the local z-axis.
G4 located at the origin of the joint coordinate system for the ATB segment J
+ 1.
Main Index
ATBJNT 1133
Interface to ATB Joints- SOL 700
Field Content
G5 located on the local x-axis.
G6 located on the local y-axis.
G7 located on the local z-axis.
Remarks:
All elements related to an ATB segment refer to the same material number. This material number is defined
on the ATBSEG entry. If the material is defined to be rigid by means of a MATRIG entry, all elements can
be easily connected to the contact ellipsoid of the ATB segment by means of METHOD=RELLIPS in
BCTABLE or BCONPRG entry referencing the MATRIG entry. In this way, all elements related to an ATB
segment move together with the ATB segment during the analyses and can be postprocessed.
Main Index
1134 ATBSEG
Interface to ATB Segments- SOL 700
ATBSEG Interface to ATB Segments- SOL 700
Defines the position and orientation of the ATB segments. The position and orientation as specified on the
G.2 and G.3 entries in the ATB input file will be overruled by the definitions given here.
This entry can be used to create a Bulk Data file containing elements and grid points to visualize the ATB
segment, together with the contact ellipsoid and the joints it is connected by. See also ATBJNT and
DYPARAM, ATBSEG. Used in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
ATBSEG ID NAME COVER NUMELM GSTART ESTART MID PIDCOV
+ G0 G1 G2 G3 EID1 EID2 EID3 PIDCG
Example:
ATBSEG 1 HEAD YES 100 1000 1000 1000
+ 1010 1011 1012 1013 1001 1002 1003 1001
Field Content
ID Unique ATBSEG number. (Integer > 0; required)
NAME Name of an ATB segment as given in the first field of a B.2 entry in the ATB input
file. (Character; required)
G0~G3 The grid points span the local coordinate system of the ATB segment. G0~G3 are used
by SOL700 to overwrite the initial position and orientation of the segments as
specified in the ATB input file. EID1-EID3 are about how to generate the grid points
for an existing ATB input file. (Integer > 0; required)
G0 located at the origin of the ATB segment.
G1 located on the local x-axis.
G2 located on the local y-axis.
G3 located on the local z-axis.
Main Index
AXIC 1135
Conical Shell Problem Flag
AXIC Conical Shell Problem Flag
Defines the existence of an axisymmetric conical shell problem.
Format:
1 2 3 4 5 6 7 8 9 10
AXIC H
Example:
AXIC 15
Describer Meaning
H Highest harmonic defined for the problem. (0 Integer < 998)
Remarks:
1. Only one AXIC entry is allowed. When the AXIC entry is present, most other entries are not allowed.
The types that are allowed with the AXIC entry are listed below:
CCONEAX MATT1 SPCADD
DAREA MOMAX SPCAX
DELAY MOMENT SUPAX
DLOAD MPCADD TABDMP1
DMI MPCAX TABLED1
DMIG NOLIN1 TABLED2
DPHASE NOLIN2 TABLED3
EIGB NOLIN3 TABLED4
EIGC NOLIN4 TABLE11
EIGP NSM TABLEM2
EIGR NSM1 TABLEM3
EIGRL NSMADD TABLEM4
EPOINT OMITAX TEMPAX
FORCE PARAM TF
FORCEAX PCONEAX TIC
FREQ POINTAX TLOAD1
FREQ1 PRESAX TLOAD2
FREQ2 RINGAX TSTEP
Main Index
1136 AXIC
Conical Shell Problem Flag
GRAV RFORCE
LOAD RLOAD1
MAT1 RLOAD2
MAT2 SECTAX
2. For a discussion of the conical shell element, see the Conical Shell Element (RINGAX) in the MSC Nastran
Reference Guide.
Main Index
AXIF 1137
Fluid Related Axisymmetric Parameters
AXIF Fluid Related Axisymmetric Parameters
Defines basic parameters and the existence of an axisymmetric fluid analysis.
Format:
1 2 3 4 5 6 7 8 9 10
AXIF CID G DRHO DB NOSYM F
N1 N2 N3 N4 N5 -etc.-
Example:
AXIF 2 32.2 0.12 2.4+5 YES
1 2 3 4 7 10
Alternate Formats and Examples of Continuation Data:
N1 “THRU” Ni
0 THRU 10
N1 “THRU” Ni “STEP” NS
0 THRU 9 STEP 3
AXIF 100 -386.0 0.0 NO
0 THRU 50 STEP 5
52
54 THRU 57
61 THRU 65
68 71 72 75
81 92
Describer Meaning
CID Fluid coordinate system identification number. (Integer > 0)
G Value of gravity for fluid elements in the axial direction. (Real)
DRHO Default mass density for fluid elements. (Real > 0.0 or blank)
DB Default bulk modulus for fluid elements. (Real)
NOSYM Request for nonsymmetric (sine) terms of series. (Character: “YES” or “NO”)
F Flag specifying harmonics. (Blank if harmonic is specified, or Character: “NONE”)
Main Index
1138 AXIF
Fluid Related Axisymmetric Parameters
Describer Meaning
Ni Harmonic numbers for the solution, represented by an increasing sequence of integers.
On continuation entries, without the “THRU” option, blank fields are ignored.
“THRU” implies all numbers including upper and lower harmonics.
(0 < Integer < 100, or Character: “THRU”, “STEP” or blank)
NS Every NSth step of the harmonic numbers specified in the “THRU” range is used for
solution. If field 5 is “STEP”, Ni = i*NS+N1 where i is the number of harmonics.
(Integer)
Remarks:
1. Only one AXIF entry is allowed.
2. CID must reference a cylindrical or spherical coordinate system.
3. Positive gravity (+G) implies that the direction of free fall is in the -Z direction of the fluid coordinate
system.
4. The DRHO value replaces blank values of RHO on the FSLIST, BDYLIST and CFLUIDi entries.
5. The DB value replaces blank values of B on the CFLUIDi entries. If the CFLUIDi entry is blank and
DB is zero or blank, the fluid is incompressible.
6. If NOSYM = “YES”, both sine and cosine terms are specified. If NOSYM = “NO”, only cosine terms
are specified.
7. If F = “NONE”, no harmonics are specified, no fluid elements are necessary, and no continuations
may be present. In this case, AXIS = “FLUID” should not be specified in the Case Control Section.
8. Superelements cannot be used.
Main Index
AXSLOT 1139
Axisymmetric Slot Analysis Parameters
AXSLOT Axisymmetric Slot Analysis Parameters
Defines the harmonic index and the default values for acoustic analysis entries.
Format:
1 2 3 4 5 6 7 8 9 10
AXSLOT RHOD BD N WD MD
Example:
AXSLOT 0.003 1.5+2 3 0.75 6
Describer Meaning
RHOD Default density of fluid in units of mass/volume. (Real > 0.0 or blank)
BD Default bulk modulus of fluid in units of force/volume ratio change. (Real 0.0 or
blank)
N Harmonic index number. (Integer > 0 or blank)
WD Default slot width. (Real > 0.0 or blank)
MD Default number of slots. (Integer > 0 or blank)
Remarks:
1. Only one AXSLOT entry is allowed.
2. If any of the RHO, B, W, and M fields on the GRID, SLBDY, CAXIFi, and CSLOTi entries are
blank, then values must be specified for the RHOD, BD and MD fields.
3. If the number of slots (M) is different in different regions of the cavity, this fact may be indicated on
the CSLOTi and SLBDY entries. If the number of slots is zero, no matrices for CSLOTi elements
are generated.
4. BD= 0.0 implies the fluid is incompressible.
Main Index
1140 BAROR
CBAR Entry Default Values
BAROR CBAR Entry Default Values
Defines default values for field 3 and fields 6 through 8 of the CBAR entry.
Format:
1 2 3 4 5 6 7 8 9 10
BAROR PID X1 X2 X3 OFFT
Example:
BAROR 39 0.6 2.9 -5.87 GOG
Alternate Format and Example:
BAROR PID G0 OFFT
BAROR 39 18 GOG
Describer Meaning
PID Property identification number of the PBAR entry. (Integer > 0 or blank)
X1, X2, X3 Components of orientation vector v , from GA, in the displacement coordinate system
at GA (default), or in the basic coordinate system. See Remark 5. (Real)
G0 Alternate method to supply the orientation vector v , using grid point G0. The
direction of v is from GA to G0. v is then translated to End A. (Integer > 0;
G0 GA or GB on CBAR entry)
OFFT Offset vector interpretation flag. See Remark 5. (Character or blank)
Remarks:
1. The contents of fields on this entry will be assumed for any CBAR entry whose corresponding fields
are blank.
2. Only one BAROR entry is allowed.
3. For an explanation of bar element geometry, see the Three-Node Beam Element (CBEAM3) in the MSC
Nastran Reference Guide.
4. If field 6 is an integer, then G0 is used to define the orientation vector and X2 and X3 must be blank.
If field 6 is real or blank, then X1, X2, and X3 are used.
5. OFFT is a character string code that describes how the offset and orientation vector components are
to be interpreted. By default (string input is GGG or blank), the offset vectors are measured in the
displacement coordinate systems at grid points A and B and the orientation vector is measured in the
displacement coordinate system of grid point A. At user option, the offset vectors can be measured in
an offset coordinate system relative to grid points A and B, and the orientation vector can be measured
in the basic system as indicated in the following table:
Main Index
BAROR 1141
CBAR Entry Default Values
String Orientation Vector End A Offset End B Offset
GGG Global Global Global
BGG Basic Global Global
GGO Global Global Offset
BGO Basic Global Offset
GOG Global Offset Global
BOG Basic Offset Global
GOO Global Offset Offset
BOO Basic Offset Offset
Any attempt to specify invalid combinations results in a bulk data entry input error message. For
example, a value of OOO (indicating offset and orientation vectors are specified in an offset reference
system) results in a fatal error since the orientation vector cannot be specified in an offset system. The
offset system x-axis is defined from GA to GB. The orientation vector v and the offset system x-axis
are then used to define the z and y axes of the offset system. (Note: The character “O” in the table
replaces the obsolete character “E”.)
Main Index
1142 BARRIER
Barrier for Eulerian Transport
BARRIER Barrier for Eulerian Transport
Defines a barrier for transport in a Eulerian mesh. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
BARRIER BID BCID MESH DIR SKFRIC
XMIN XMAX YMIN YMAX ZMIN ZMAX
Example:
BARRIER 100 20
Describer Meaning
BID Unique barrier number. (Integer > 0; Required)
BCID Number of a set of BCSEG entries that define the element faces that are barriers to
Eulerian transport. See Remark 4. (Integer > 0)
MESH Denotes the ID of the Euler mesh to which the boundary condition has to be applied.
See Remark 5. (Integer > 0)
DIR Allowed values are NEGX, POSX, NEGY, POSY, NEGZ and POSZ. See Remark 6.
(Character)
SKFRIC Skin friction value. See Remark 8. (Real 0.0, 0.0)
XMIN-ZMAX Defines a square by specifying the ranges of the x,y,z coordinates. For a square in for
example the x-plane it is required that either XMIN = XMAX or that XMAX is left
blank. See Remark 7. (Real)
Remarks:
1. Material cannot pass through any of the faces referenced.
2. Barriers can be modeled on the edge as well as the inside of an Eulerian mesh.
3. BARRIER overrules FLOW and FLOWT definition.
4. BCID is optional. If used, all other inputs are ignored. If not used, the barrier can be defined by either
using DIR or by using XMIN, XMAX, YMIN, etc.
5. The MESH-ID is only used when multiple Euler domains have been defined and when BCID is
blank. If multiple Euler domains have been defined but if the MESH-ID is blank all Euler domains
will be considered in assigning the boundary condition.
6. DIR is optional. It will only be used when BCID is blank. When DIR is used XMIN, XMAX, YMIN
etc. are ignored.
Main Index
BARRIER 1143
Barrier for Eulerian Transport
7. XMIN, XMAX, YMIN, etc are only used when both BCID and DIR are blank. The XMIN,YMIN
option defines an area on the MESH BOX boundary as shown in Figure 9-1. If neither the MIN nor
MAX value has been set the default value is respectively -1E+20 and 1e+20 for the MIN and MAX
value. If the MIN value has been set the default value of the MAX value is the MIN value.
8. The skin friction is defined as:
w
C f = ---------------------
2
0.5 u
Here w denotes the shear friction in an Euler element adjacent to a couple surface segment where
is the density and u is the tangential relative velocity in the Euler element that is adjacent to a
couple surface segment. SKFRIC will only be used when VISC has been set on either an EOSGAM
or an EOSPOL entry. If VISC has been set and if SKFRIC has not been set then a no slip condition
will be prescribed at the interface between fluid and structure.
9. Internal barriers can only be defined on existing Euler element faces using the BCID option. They
cannot be defined by using the XMIN,YMIN option.
Figure 9-1 MESH BOX boundary
Main Index
1144 BCAUTOP
Automatic contact generation property.
BCAUTOP Automatic contact generation property.
Specifies parameters for automatic contact generation (ACG). When ACG is activated, contact bodies are
automatically generated based on connectivity or specified grids or elements, and establishes the contact pairs
in which two contact bodies may come into contact based on the DISTANCE tolerance. Please refer to the
section of Chapter 9: Contact, SOL 400 User’s Guide for details.
Format:
etc
1 2 3 4 5 6 7 8 9 10
BCAUTOP PID Param1 Value1 Param2 Value2 Param3 Value3
Param4 Value4 etc
Example:
BCAUTOP CTYPE PGLUE DISTANCE 0.1
Describer Meaning
PID Reserved for future use (integer >=0, default is 0)
Param(i) Name of a parameter. Allowable names are given below (Character).
Value(i) Value of the parameter. See below (Real, Integer or Character). See Remark 3.
Remarks:
1. Only one entry of BCAUTOP is allowed. If there are modules, only one BCAUTOP is allowed per
module.
2. This entry has no effect if BCONTACT=AUTO is absent in the Case Control section.
3. The parameters in this entry may be divided into two types – primary parameters and secondary
parameters. The primary parameters are the most important parameters for creation of contact bodies
and match of contact pairs. The secondary parameters are helpful if more detail to define contact
parameters is necessary with ACG. The primary and secondary parameters are listed in the tables
below.
4. When modules are present, contact data is generated for the module if a BCAUTOP exists in the
module, otherwise no contact data is generated for the module. In this latter case, user supplied
contact data can be used if a BCTABL1 ID=1 and/or ID=0 exists.
Main Index
BCAUTOP 1145
Automatic contact generation property.
Table 9-1 Primary Parameters in BCAUTOP
Describer Meaning
CTYPE Characters: one of TOUCH (default), PGLUE, SGLUE, or GGLUE. If CTYPE is
specified in both this BCAUTOP entry and in the Case Control command,
(BCONTACT=AUTO,ctype), the specification in this BCAUTOP entry takes
precedent.
DISTANCE Distance tolerance of contact pair. If the distance between any two points which
belong to two different contact bodies is less than this value, these two contact bodies
are recognized to be a contact pair. Default value of DISTANCE is 100 times the
contact ERROR tolerance. ERROR may be defined in either BCAUTOP or left blank.
When ERROR is left blank, ERROR is set to the smallest of the following values:
1. 1/20 of the smallest nonzero element dimension (plates or solids) in the contact
body
2. 1/4 of the thinnest shell thickness in the contact body
For more detail, please see ERROR definition in the BCPARAentry.
ESET ID of SET1 to specify the element IDs of the contact bodies. Only the elements
specified make up the contact bodies based on connectivity search. Any connected
elements that are not specified in the list are left out of the bodies. If this parameters is
not specified, all elements in the model are used. One body for each continuous set of
connected elements is created. Only one of ESET, SeedESet, SeedGSet, or PropSet can
be specified in the same BCAUOTP entry.
SeedESet ID of SET1 to specify element IDs as seeds for determining contact bodies based on
connectivity. The program uses the seed elements to determine connectivity. One body
for each continuous set of connected elements is created. Only one of ESET, SeedESet,
SeedGSet, or PropSet can be specified in the same BCAUOTP entry.
SeedGSet ID of SET1 to specify grids IDs as seeds for determining contact bodies. The program
uses the seed grids to determine connectivity. One body for each continuous set of
connected elements is created. Only one of ESET, SeedESet, SeedGSet, or PropSet can
be specified in the same BCAUOTP entry.
PropSet ID of SET1 to specify property IDs to construct contact bodies. Only one of ESET,
SeedESet, SeedGSet, or PropSet can be specified in the same BCAUOTP entry.
RigidSet ID of SET1 to specify IDs of rigid bodies to be in contact.
Main Index
1146 BCAUTOP
Automatic contact generation property.
Table 9-2 Secondary Parameters in BCAUTOP
Describer Meaning
BEAMCNT Characters, YES or NO (default) - beam contact.
YES: BEAMs are included in the contact description.
NO: BEAMs are NOT included in the contact description.
BEAMCAP Characters, FREEEND (default) or NO. If set to FREEEND, BCSCAP entries are added
to the free end of beam elements; if NO, no BCSCAP is added. This is mainly used for
contact pair detection where the contact occurs at the free beam end.
DIMENS Characters, 2D or 3D (default) - dimension of the contact bodies.
EDGECNT Characters, YES or NO (default) - edge contact.
YES: The free and hard shell edges are included in the contact definition
NO: Shell edges are NOT included in the contact definition.
FTYPE Characters, BLCOUL/BLSHEAR; or Integer, 6 / 7. BLCOUL or 6 is Bilinear Coulomb
friction. BLSHEAR or 7 is Bilinear Shear friction. Default is No Friction.
FRIC Friction coefficient. If the value is an integer, it represents the ID of a TABLEM1,
TABLEM2 or TABL3D, i.e., a temperature-dependent or multi-dimensional table.
(Real ≥ 0.0 or Integer > 0; Default = 0.0)
IGNTHK Character, YES or NO (default) - ignore thickness of shell for contact.
YES: ignore the thickness of the shell
NO: include the thickness of the shell.
INISF Character, YES or NO (default) - initial stress free contact.
Yes: initial stress free contact
No: general contact without implementation of initial stress free contact
SelfCont Characters, YES or NO (default). Option of self-contact.
Yes: self-contact allowed
No: self-contact ignored
All Other All the parameters in BCPARA, BCONPRP, BCONPRG, and BCBDPRP entries may
be set directly in BCAUTOP. For the detailed list of these parameters, please refer to
BCPARA, BCONPRP, BCONPRG, and BCBDPRP entiries.
Note: Note that the parameters defined in BCAUTOP are applied only for BCONTACT=AUTO,
including all default values.
Main Index
BCBDPRP 1147
Contact Body Parameters in SOLs 101 and 400
BCBDPRP Contact Body Parameters in SOLs 101 and 400
Defines contact body parameters used in SOLs 101 and 400 only. The parameters defined here are referenced
by the BCBODY1 entry.
Format:
1 2 3 4 5 6 7 8 9 10
BCBDPRP PID PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3
PARAM4 VAL4 PARAM5 VAL5 -etc.-
Example:
BCBDPRP 90 FRIC 0.05 ISTYP 0
Describer Meaning
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 9-3 (Character).
VALi Value of a parameter. See Table 9-3 (Real or Integer).
Main Index
1148 BCBDPRP
Contact Body Parameters in SOLs 101 and 400
Table 9-3 Contact Body Parameters in SOLs 101 and 400
Name Description, Type and Value (Default is 0 for integer, 0.0 for Real Unless Otherwise
Indicated)
BNC Exponent associated with the natural convective heat flow for near field behavior. (Real or
Integer; Default = 1.0). If Real, the value entered is the exponent associated with the near
field natural convection coefficient. If Integer, the value entered is the ID of a TABLEM1 OR
TABLEM2 entry specifying the exponent associated with the near field natural convection
coefficient vs temperature or a TABL3D entry specifying the exponent associated with the
near field natural convection coefficient vs temperature and possibly other variables.
BNCE Exponent associated with natural convection heat flow to the environment. (Real or Integer;
Default = 1.0). If Real, the value entered is the exponent associated with the environment
natural convection coefficient. If Integer, the value entered is the ID of a TABLEM1 or
TABLEM2 entry specifying the exponent associated with the environment natural
convection coefficient vs temperature or a TABL3D entry specifying the exponent associated
with the environment natural convection coefficient vs temperature and possibly other
variables.
BNL Exponent associated with the nonlinear convective heat flow for near field behavior. (Real or
Integer; Default = 1.0) If Real, the value entered is the exponent associated with the near field
nonlinear convection coefficient. If Integer, the value entered is the ID of a TABLEM1 OR
TABLEM2 entry specifying the exponent associated with the near field nonlinear convection
coefficient vs temperature or a TABL3D entry specifying the exponent associated with the
near field nonlinear convection coefficient vs temperature and possibly other variables.
BNLE Exponent associated with the nonlinear convective heat flow to the environment. (Real or
Integer; Default = 1.0) If Real, the value entered is the exponent associated with the
environment nonlinear convection coefficient. If Integer, the value entered is the ID of a
TABLEM1 or TABLEM2 entry specifying the exponent associated with the environment
nonlinear convection coefficient vs temperature or a TABL3D entry specifying the exponent
associated with the environment nonlinear convection coefficient vs temperature and
possibly other variables.
CFILM Heat transfer coefficient (film) to environment. (Real or Integer, Default = 0.0) If Real, the
value entered is the film coefficient. If Integer, the value entered is the ID of a TABLEM1 or
TABLEM2 entry specifying the heat transfer coefficient vs temperature or a TABL3D entry
specifying the film coefficient vs temperature and possibly other variables.
CMB Heat capacity of the rigid body, when entered as a geometric entity with an associated scalar
point. (Real > 0.0; Default = 0.0) For nonzero values, a grounded CDAMP4 element with
the scalar point on its first side is generated internally which obtains this capacity.
CMS Heat capacity of the environment, when associated with a scalar point. (Real > 0.0;
Default = 0.0) For nonzero values a grounded CDAMP4 element with the scalar point on its
first side is generated internally which obtains this capacity.
COPTB Flag to indicate how body surfaces may contact. See Remark 2. on the BCONPRG entry.
(Integer; Default = 0)
Main Index
BCBDPRP 1149
Contact Body Parameters in SOLs 101 and 400
EMISS Emissivity for radiation to the environment or near thermal radiation. (Real or Integer;
Default = 0.0) If real, the value entered is the emissivity. If Integer, the value entered is the ID
of a TABLEM1 or TABLEM2 entry specifying the emissivity vs temperature or a TABL3D
entry specifying the emissivity vs temperature and possibly other variables.
FRIC Friction coefficient. If the value is an integer, it represents the ID of a TABLEM1, TABLEM2
or TABL3D, i.e., a temperature-dependent or multi-dimensional table. (Real ≥ 0.0 or Integer
> 0; Default = 0.0)
When a grid point contacts a rigid body, the coefficient of friction associated with the rigid
body is used. When a grid point contacts a deformable body, the average of the coefficients
for the two bodies are used.
In general, entering the friction coefficient for a contact body pair via a BCTABLE and
BCONECT/BCONPRP is strongly recommended.
HBL Separation distance dependent thermal convection coefficient. (Real or Integer; Default =
0.0) If Real, the value entered is the separation distance dependent thermal convection
coefficient. If Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry
specifying the convection coefficient vs temperature or a TABL3D entry specifying the
convection coefficient vs temperature and possibly other variables.
HCT Contact heat transfer coefficient. (Real or Integer; Default = 0.0) If Real, the value entered is
the contact heat transfer coefficient. If Integer, the value entered is the ID of a TABLEM1 or
TABLEM2 entry specifying the contact heat transfer coefficient vs temperature or a TABL3D
entry specifying the contact heat transfer coefficient vs temperature and possibly other
variables. See Remark 3.
HCV Convection coefficient for near field behavior. (Real or Integer; Default = 0.0) If Real, the
value entered is the near field convection coefficient. If Integer, the value entered is the ID of
a TABLEM1 or TABLEM2 entry specifying the near field convection coefficient vs
temperature or a TABL3D entry specifying the near field convection coefficient vs
temperature and possibly other variables.
HNC Natural convection coefficient for near field behavior. (Real or Integer; Default = 0.0) If Real,
the value entered is the near field natural convection coefficient. If Integer, the value entered
is the ID of a TABLEM1 or TABLEM2 entry specifying the near field natural convection
coefficient vs temperature or a TABL3D entry specifying the near field natural convection
coefficient vs temperature and possibly other variables.
HNCE Natural convection coefficient for heat flow to the environment. (Real or Integer,
Default = 0.0) If Real, the value entered is the environment natural convection coefficient. If
Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry specifying the
environment natural convection coefficient vs temperature or a TABL3D entry specifying the
environment natural convection coefficient vs temperature and possibly other variables.
HNL Heat transfer coefficient for nonlinear convective heat flow for near field behavior. (Real or
Integer; Default = 0.0) If Real, the value entered is the near field nonlinear convection
coefficient. If Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry
specifying the near field nonlinear convection coefficient vs temperature or a TABL3D entry
specifying the near field nonlinear convection coefficient vs temperature and possibly other
variables.
Main Index
1150 BCBDPRP
Contact Body Parameters in SOLs 101 and 400
HNLE Heat transfer coefficient for nonlinear convective heat flow to the environment. (Real > 0.0
or Integer; Default = 0.0) If Real, the value entered is the environment nonlinear convection
coefficient. If Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry
specifying the environment nonlinear convection coefficient vs temperature or a TABL3D
entry specifying the environment nonlinear convection coefficient vs temperature and
possibly other variables.
IDSPL Controls geometric smoothing of boundary of deformable body option. (Integer; Default =
0)
=0 or blank, discrete geometric representation.
>0 the surface of the body is smoothed out with splines (2D) or Coons surfaces (3D) and
discontinuity edges/corners are being defined by using abs (IDSPL) as the ID of the BLSEG
entries. If BLSEG with ID=abs(IDSPL) does not exist, the whole body is smoothed and there
are no user-defined discontinuity corners(2D) or edges(3D). (See Remark 1.
<0 Same as IDSPL>0. Furthermore, additional discontinuity edges are being generated
automatically if the difference in patch normals exceeds the value of SANGLE.
ISTYP Check of contact conditions. (Integer > 0; Default = 0 for all solutions)
ISTYP is not necessary in segment-to-segment contact.
For a deformable body:
=0 check each body, versus the other.
=2 double-sided contact with automatic optimization of contact constraint equations (this
option is known as “optimized contact”).
Note that ISTYP is supported with ISEARCH=0 in BCTABLE or BCONPRG only.
ITYPE An option entry for heat transfer only (Integer; no Default)
1 - Heat sink (rigid body)
2 - Deformable body (with heat conduction)
4 - Heat conduction body (heat-rigid body) (Not supported in SOL 400 coupled thermal-
mechanical analysis, i.e. the same contact body with ITYPE=4 cannot be used in mechanical
analysis of SOL 400.)
Main Index
BCBDPRP 1151
Contact Body Parameters in SOLs 101 and 400
MIDNOD Mid-side node projection flag. (Integer > 0; Default = 0)
When MIDNOD > 0 and IDSPL ≠ 0, the mid-side grid of quadratic elements are projected
onto the selected spline surfaces. This operation is performed before the contact process starts
and it may change the location of grids in contact bodies. It may operate in combination with
the initial stress-free contact. Only used if IDSPL is not zero.
SANGLE Threshold for automatic discontinuity detection in degrees. (Real; Default = 60.0) Used for
geometric smoothing option in SOL 400 only. SANGLE is not used and is always set to 0.0
when IDSPL≥ 0.
TBODY Body temperature. (Real or Integer; Default = 0.0) If Real, the value entered is the body
temperature. If Integer, the value entered is the ID of a TABLED1 or TABLED2 entry
specifying the body temperature vs time or a TABL3D entry specifying the body temperature
vs time and possibly other variables. When entered as a negative integer, its absolute value is
a scalar point identification number. If a scalar point is specified on this entry, it need not be
defined on an SPOINT entry. See Remark 8.
TSINK Environment sink temperature. (Real or Integer, Default = 0.0) If Real, the value entered is
the sink temperature. If Integer, the value entered is the ID of a TABLED1 or TABLED2
entry specifying temperature vs time or a TABL3D entry specifying the sink temperature vs
time and possibly other variables. When entered as a negative integer its absolute value is a
scalar point identification number. If a scalar point is specified on this entry, it need not be
defined on an SPOINT entry. See Remark 8.
Remarks:
1. When IDSPL is greater than 1, these nodes are entered in pairs. For a quad surface (for example,
CQUAD4 or edge of a CHEXA) usually 4 sets of nodal pairs are needed to describe the surface. For
example, a CQUAD4 with grid numbering 1,2,4,3 would need pairs of nodes, 1,2 2,4 4,3 3,1. The
nodal pairs may be entered in any order. See MSC Nastran Nonlinear User’s Guide, Chapter 9,
Contact for more details.
2. For hard contact, with HGLUE=1 (see BCONPRP for the meaning of HGLUE):
a. The temperature of the contacting grid is tied to the temperatures of the contacted element face
or the temperature of the rigid geometry when it has a scalar point associated with it.
b. The temperature of the contacting grid is set to the rigid geometry temperature when it has no
scalar point associated with it.
Note: “Glued” thermal contact can result in overshoot of the temperatures at the interface, in
particular, if two bodies that have non-uniform initial temperatures are placed in contact. The
overshoot effect may be damped somewhat if one uses a near contact distance with some
convective heat transfer.
3. For hard contact, with HGLUE=0:
The convective heat flow per unit area over the two interfaces is given by:
Main Index
1152 BCBDPRP
Contact Body Parameters in SOLs 101 and 400
q = HCT T A – T B
where TA is the contacting grid temperature and TB is the face temperature in the contact point in
case of a meshed body or the TBODY temperature in case of a rigid geometry.
It is recommended to enter the HCT value on the BCONPRP Bulk Data entry, since it generally
applies to body pairs and is not a property of a single body.
4. For near contact:
q = HCV T A – T B +
BNC
HNC T A – T B +
BNL BNL
HNL T A – TB +
4 4
EMISS T A – T B +
dist dist
HCT 1 – ------------------------- + HBL ------------------------- T A – T B
DQNEAR DQNEAR
where the last term is only activated when HBL ≠ 0, TA is the contacting grid temperature and TB is
the face temperature in the contact point in case of a meshed body or the TBODY temperature in case
of a rigid geometry.
It is recommended to enter the near contact heat transfer coefficients and the corresponding
exponents on the BCONPRP Bulk Data entry, since they generally apply to body pairs and are not
properties of a single body.
5. For no contact:
q = CFILM T A – T SINK +
BNCE
HNCE T A – T SINK +
BNLE BNLE
HNLE T A – T SINK +
4 4
EMISS T A – T SINK
6. The heat transfer coefficients and associated exponents can all be temperature dependent, when they
are entered as an integer value. This integer value is the table ID of a TABLEM1, TABLEM2 or
TABL3D entry (formulas are not supported on TABL3D).
7. The TSINK and TBODY temperatures can be time dependent when they are entered as a positive
integer value. This integer value is the table ID of a TABLED1, TABLED2 or TABL3D entry
(formulas are not supported on TABL3D).
Main Index
BCBDPRP 1153
Contact Body Parameters in SOLs 101 and 400
8. TBODY entries only apply to rigid bodies (i.e., RIGID as the BEHAV value in BCBODY1 entry).
TSINK entries only apply to deformable bodies (meshed regions with DEFORM or HEAT as the
BEHAV value in BCBODY1 entry).
Main Index
1154 BCBMRAD
Modify Equivalent Radius for Beam-to-Beam Contact
BCBMRAD Modify Equivalent Radius for Beam-to-Beam Contact
Allows the equivalent radius in beam-to-beam contact to be different for each beam cross section in SOL 101,
SOL 400. The BCBMRAD entry is only used for node-to-segment beam-to-beam contact. For segment-to-
segment beam contact, the beam cross section geometry is defined via PBARL or PBEAML
Format:
1 2 3 4 5 6 7 8 9 10
BCBMRAD RADIUS TYPE ID1 ID2 THRU ID3 BY N
ID4 THRU ID5 ID6 ID7 ID8 ID9
Example 1:
BCBMRAD 2.5 EID 100 20 THRU 300 BY 2
200 3457 8456 4712 1000 THRU 2000
3.0 4112 THRU 4700
2.8 BODY 502 517 3459
Example 2:
BCBMRAD 2.5 ALL
2.8 EID 2567 1240 THRU 1760
Describer Meaning
RADIUS Equivalent radius to be used for beam-beam contact problems. See Remark 6. (Real; no
Default)
TYPE The attribute of all following ID’s. (Character; Default = “EID”)
EID Defines all the following entries are the IDs of beam-type elements.
BODY Defines all the following entries are the IDs of BCBODYs.
ALL Defines the default RADIUS for all beam-type elements.
IDi ID of a beam-type element, CROD, CBAR, CBEAM and CBEAM3, or a BCBODY
with the specified radius. (Integer; no Default)
Remarks:
1. Multiple BCBMRAD Bulk Data entries, which are open-ended are allowed in one file.
2. In each entry of BCBMRAD, there is only one RADIUS input allows, on the field 2. From the field
4 to the rest fields, including all continuation entries, user can input all ID's in any combination of
the following 3 basic formats
• ID1 ID2 ID3 ID4 ...
• ID1 THRU ID2
Main Index
BCBMRAD 1155
Modify Equivalent Radius for Beam-to-Beam Contact
• ID1 THRU ID2 BY N
Note that blank fields are allowed for readability.
3. When all beam contact radii are the same, user can put “ALL” on the filed 3 following a RADIUS
value on the BCBMRAD Bulk Data entry. This value of RADIUS will be applied to all beam-type
elements (See the previous Example 2). User can also use this way to give default radius of all beam-
type elements.
4. The RADIUS value of the other BCBMRAD's (TYPE=BODY or EID) can override the default value
(TYPE=ALL) in the following order:
a. When any BCBODY is selected on BCBMRAD with TYPE=BODY, the specified RADIUS will
be applied to all beam-type elements in this BCBODY. This value always overrides the default
(TYPE=ALL).
b. The RADIUS with TYPE=EID always overrides the value from TYPE=BODY and ALL.
5. When TYPE=ALL, then all IDi must be blank.
6. For tubes or round bars, enter the outer radius. For beam, enter an equivalent radius calculated as
follows:
I = 0.5 I x + I y
A
----- I
R = + 2 ---
2 A
7. This is only used for node-to-segment contact.
Main Index
1156 BCBODY
Flexible or Rigid Contact Body in 2D and 3D
BCBODY Flexible or Rigid Contact Body in 2D and 3D
Defines a flexible or rigid contact body in 2D or 3D used in SOLs 101, 400, and 700 only. The BCBODY1
option is the preferred method to defining contact bodies for SOL 400.
Use only as many forms (i.e. HEAT, PATCH3D, BEZIER, POLY, CYLIND, SPHERE, NURBS2, or
NURBS) as necessary to describe the body (if rigid). Deformable bodies are described using as many standard
elements as necessary and are specified by the BSID field with BEHAV=DEFORM (only the first line should
be entered for deformable bodies). Unless shrink fit its being analyzed, deformable bodies should not be
inside other deformable bodies when the thickness of each body is taken into account.
The “RIGID” header may be used with any of the other rigid entries but only once per body. Also, only one
of the character entries after RIGID (HEAT, PATCH3D, NURBS, etc.) should be entered for any particular
body. See Remark 4. for an important note regarding how to define the outward direction of rigid bodies
(which must point towards a flexible body for contact to occur).
Format: (SOLs 101 and 400 only)
1 2 3 4 5 6 7 8 9 10
BCBODY BID DIM BEHAV BSID ISTYP FRIC IDSPL CONTROL
NLOAD ANGVEL DCOS1 DCOS2 DCOS3 VELRB1 VELRB2 VELRB3
“ADVANCE” SANGLE COPTB MIDNO
D
“RIGID” CGID NENT --- Rigid Body Name ---
“APPROV” A N1 N2 N3 V1 V2 V3
“GROW” GF1 GF2 GF3 TAB-GF1 TAB-GF2 TAB-GF3
“HEAT” CFILM TSINK HCT TBODY HCV HNC ITYPE
BNC EMISS HBL HNL BNL HNLE BNLE
HNCE BNCE CMB CMS
“PATCH3D” NPATCH
IDP G1 G2 G3 G4
IDP G1 G2 G3 G4
etc. (npatch
entries)
“BEZIER” NP1 NP2 NSUB1 NSUB2
G1 G2 G3 G4 etc (np1*np2
values)
“NURBS2D” NPTU NORU NSUB (2D
Contact)
G1 or X1 G2 or Y1 G3 G4 or X2 G5 or Y2 G6 [abs(nptu) See
grids or x, Remark 8
y,z, values]
Main Index
BCBODY 1157
Flexible or Rigid Contact Body in 2D and 3D
Homo1 Homo2 Homo3 Homo4 etc. (nptu
values)
Knot1 Knot2 Knot3 Knot4 Knot5 etc. (nptu+nor
u values)
“NURBS” NPTU NPTV NORU NORV NSUBU NSUBV NTRIM
G1 or X1 G2 or Y1 G3 or Z1 G4 or X2 G5 or Y2 G6 or Z2 G7 See
Remark 8
G8 or X3 G9 or Y3 G10 or Z3 etc. [abs(nptu) See
*nptv Remark 8
values]
Homo1 Homo2 Homo3 Homo4 Homo5 Homo6 Homo7
Homo8 Homo9 etc. (nptu*npt
v vales)
Knot1 Knot2 Knot3 Knot4 Knot5 Knot6 Knot7 `
Knot8 Knot9 etc. (nptu+nor
u+ntpv+n
orv values)
IDtrim NPTUtrim NORUtrim NSUBtrim (repeat
this and all
following
lines
NTRIM
times)
Xisoparam Yisoparam (NPTUtri
m entries)
Homo1 Homo2 Homo3 etc (NPTUtri
m entries)
Knot1 Knot2 Knot3 etc. (NPTUtri
m+
NORUtri
m entries)
Format: (SOL 700 only)
BCBODY BID DIM BEHAV BSID
Examples (of Deformable and Rigid Contact):
Example 1 -- Typical deformable body
BCBODY 1 DEFORM 101 0 .05
Example 2 -- Simple 4-node rigid patch (see Remark 4. for rigid bodies)
BCBODY 2 RIGID 102 0 .08
PATCH3D 1
1 101 102 103 104
Main Index
1158 BCBODY
Flexible or Rigid Contact Body in 2D and 3D
Describer Meaning
BID Contact body identification number referenced by BCTABLE, BCHANGE, or
BCMOVE. (Integer > 0; Required)
DIM Dimension of body. (Character; Default= 3D) (Ignored by SOL 700)
DIM=2D planar body in x-y plane of the basic coordinate system, composed of 2D
elements or curves.
DIM=3D any 3D body composed of rigid surfaces, shell elements or solid elements.
BEHAV Behavior of curve or surface (Character; Default = DEFORM) (Ignored by SOL 700)
DEFORM body is deformable, RIGID body is rigid, SYMM body is a symmetry body,
HEAT indicates body is a heat-rigid body. See Remark 4. for Rigid Bodies.
BSID Identification number of a BSURF or BCPROP entry if BEHAV=DEFORM. For SOL
700 the BSID may also be the identification number of a BCBOX, BCMATL, BCSEG,
BCGRID or BCELIPS entry. (Integer > 0)
ISTYP Check of contact conditions. (Integer > 0; Default = 0 for all solutions)
ISTYP is not necessary in segment-to-segment contact.
For a deformable body:
=0 check each body, versus the other .
=2 double-sided contact with automatic optimization of contact constraint equations
(this option is known as “optimized contact”).
Note that ISTYP is supported with ISEARCH=0 in BCTABLE or BCONPRG only.
FRIC Friction coefficient. If the value is an integer, it represents the ID of a TABLEM1,
TABLEM2 or TABL3D, i.e., a temperature-dependent or multi-dimensional table.
(Real ≥ 0.0 or Integer > 0; Default = 0.0)
When a grid point contacts a rigid body, the coefficient of friction associated with the
rigid body is used. When a grid point contacts a deformable body, the average of the
coefficients for the two bodies are used.
In general, entering the friction coefficient for a contact body pair via a BCTABLE and
BCONECT/BCONPRP is strongly recommended.
IDSPL Controls geometric smoothing of boundary of deformable body. (Integer; Default = 0)
=0 or blank, discrete geometric representation
>0 the surface of the body is smoothed out with splines (2D) or Coons surfaces (3D)
and discontinuity edges/corners are being defined by using abs (IDSPL) as the ID of
the BLSEG entries. If BLSEG with ID=abs(IDSPL) does not exist, the whole body is
smoothed and there are no user-defined discontinuity corners(2D) or edges(3D). (See
Remark 7.)
<0 Same as IDSPL>0. Furthermore, additional discontinuity edges are being generated
automatically if the difference in patch normals exceeds the value of SANGLE.
Main Index
BCBODY 1159
Flexible or Rigid Contact Body in 2D and 3D
Describer Meaning
CONTROL = -1 for position control. The coordinates of the final position of GRID Point defined
in CGID is given in VELRBi in the following line.
= 0 for velocity control (default).
= positive number for "load control". The positive number entered is the grid number
defined in CGID at which translational forces or SPCD are applied. (Note: The
rotation in this case is defined by NLOAD in the following line.)
NLOAD Enter a positive number if "load controlled" and rotations are allowed (Integer). The
positive number is the grid number where the moments or rotations are applied. The
rotations are specified using SPCD at grid ID NLOAD and can be specified using dof's
1-3 (for rotation about x, y, z respectively), or by dof's 4-6 (for rotation about x, y, z
respectively).
Note: This rotation takes the position of the grid point defined in CGID field as the
center of rotation.
ANGVEL Angular velocity or angular position about local axis through center of rotation. If the
value is an integer it represents the ID of a TABLED1, TABLED2 or TABL3D, i.e., a
time-dependent or multi-dimensional table; however, no log scales, only linear scales.
(Real or Integer; Default = 0.0)
DCOSi Components of direction cosine of local axis if ANGVEL is nonzero. If the value is an
integer, it represents the ID of a TABLED1, TABLED2 or TABL3D, i.e., a time-
dependent or multi-dimensional table; however, no log scales, only linear scales. (Real
or Integer; Default=0.0) In 2D contact only DCOS3 is used and the Default is 1.0.
VELRBi Translation velocity or final position (depending on the value of CONTROL) of rigid
body at the grid point defined in CGID filed. For velocity control only, if the value is
an integer, it represents the ID of TABLED1, TABLED2 or TABL3D, i.e., a time-
dependent or multi-dimensional table; however, no log scales, only linear scales. Only
VELRB1 and VELRB2 are used in 2D contact. (Real or Integer; Default = 0.0)
“ADVANCE” The entries for this continuation line are for advanced options starting with
MD Nastran R2.
SANGLE Threshold for automatic discontinuity detection in degrees. (Real; Default = 60.0)
Used for SPLINE option in SOL 400 only. SANGLE is not used when IDSPL 0.
COPTB Flag to indicate how body surfaces may contact. See Remark 9. on the BCTABLE entry.
(Integer; Default = 0)
MIDNOD Mid-side node projection flag. (Integer > 0; Default = 0)
When MIDNOD > 0 and IDSPL 0, the mid-side grid of quadratic elements are
projected onto the selected spline surfaces. This operation is performed before the
contact process starts and it may change the location of grids in contact bodies. It may
operate in combination with the initial stress-free contact.
“RIGID” The entries of this continuation line are for the rigid body description. See Remark 4.
Main Index
1160 BCBODY
Flexible or Rigid Contact Body in 2D and 3D
Describer Meaning
CGID Grid point identification number defining the initial position of the reference point of
(5,i) i=1,2,3 the rigid body or the point where a concentrated force or moment is applied
NENT Number of geometric entities to describe this rigid surface. A rigid surface can be
described by multiple sets of patches, nurbs, etc. For example, if it takes 3 sets of
PATCH3D entries to describe a rigid surface, then set NENT=3. (Integer > 0; Default
= 1)
Rigid Body Name associated with the rigid body. (Default is blank, 24-characters maximum)
Name
“APPROV” The entries of this continuation line are for approaching velocity to establish initial
contact.
A Angular velocity about local axis through center of rotation. (Real, Default = 0.0)
Ni Components of direction cosines of local axis of the angular velocity. The N1, N2, N3
define the axis through the point defined in the “RIGID”, CGID entry. Only N1 and
N2 are used in 2D contact. (Real, Default = 0.0)
Vi V1, V2 and V3 define the three components of the approaching velocity. Only V1 and
V2 are used in 2D contact. (Real; Default = 0.0)
“GROW” The entries of this continuation line are for rigid body growth. If tables are used for
growth, they should either be TABLED1, TABLED2(growth vs time) or TABL3D
(growth vs one or more variables).
GFi Components of Growth factor of rigid body in the coordinate system of the “RIGID”,
CGID entry. (Real, Default = 1.0)
TAB-GFi Tabled IDs for growth factor of rigid body in the coordinate system of the “RIGID”,
CGID entry. (Integer > 0 or blank, Default is blank)
“HEAT” The entries of this continuation line(s) are for contact in heat transfer in a pure thermal
analysis or in a coupled thermal/structural analysis. In a pure structural analysis they are
ignored.
CFILM Heat transfer coefficient (film) to environment. (Real or Integer, Default = 0.0) If Real,
(9,1)/(10,1) the value entered is the film coefficient. If Integer, the value entered is the ID of a
TABLEM1 or TABLEM2 entry specifying the heat transfer coefficient vs temperature
or a TABL3D entry specifying the film coefficient vs temperature and possibly other
variables.
TSINK Environment sink temperature. (Real or Integer, Default = 0.0). If Real, the value
(9,2)/(10,2) entered is the sink temperature. If Integer, the value entered is the ID of a TABLED1
or TABLED2 entry specifying temperature vs time or a TABL3D entry specifying the
sink temperature vs time and possibly other variables. When entered as a negative
integer its absolute value is a scalar point identification number. If a scalar point is
specified on this entry it need not be defined on an SPOINT entry.
Main Index
BCBODY 1161
Flexible or Rigid Contact Body in 2D and 3D
Describer Meaning
HCT Contact heat transfer coefficient. (Real or Integer; Default = 0.0). If Real, the value
(9,3)/(10,3) entered is the contact heat transfer coefficient. If Integer, the value entered is the ID of
a TABLEM1 or TABLEM2 entry specifying the contact heat transfer coefficient vs
temperature or a TABL3D entry specifying the contact heat transfer coefficient vs
temperature and possibly other variables.
TBODY Body temperature. (Real or Integer; Default = 0.0). If Real, the value entered is the body
(9,4)/(10,4) temperature. If Integer, the value entered is the ID of a TABLED1 or TABLED2 entry
specifying the body temperature vs time or a TABL3D entry specifying the body
temperature vs time and possibly other variables. When entered as a negative integer its
absolute value is a scalar point identification number. If a scalar point is specified on
this entry it need not be defined on an SPOINT entry.
HCV Convection coefficient for near field behavior (Real or Integer; Default = 0.0). If Real
(9,5)/(10,5) the value entered is the near field convection coefficient. If Integer, the value entered is
the ID of a TABLEM1 or TABLEM2 entry specifying the near field convection
coefficient vs temperature or a TABL3D entry specifying the near field convection
coefficient vs temperature and possibly other variables.
HNC Natural convection coefficient for near field behavior (Real or Integer; Default = 0.0).
(9,6)/(10,6) If Real, the value entered is the near field natural convection coefficient. If Integer, the
value entered is the ID of a TABLEM1 or TABLEM2 entry specifying the near field
natural convection coefficient vs temperature or a TABL3D entry specifying the near
field natural convection coefficient vs temperature and possibly other variables.
ITYPE An option entry for heat transfer only (Integer; no Default)
[4,8] 1 - Heat sink (rigid body)
2 - Deformable body (with heat conduction)
4 - Heat conduction body (heat-rigid body) (Not supported in SOL 400 coupled
thermal-mechanical analysis)
BNC Exponent associated with the natural convection coefficient for near field behavior
(9,7)/(10,7) (Real or Integer; Default = 1.0). If Real, the value entered is the exponent associated
with the near field natural convection coefficient. If Integer, the value entered is the ID
of a TABLEM1 or TABLEM2 entry specifying the exponent associated with the near
field natural convection coefficient vs temperature or a TABL3D entry specifying the
exponent associated with the near field natural convection coefficient vs temperature
and possibly other variables.
EMISS Emissivity for radiation to the environment or near thermal radiation (Real or Integer;
(9,8)/(10,8) Default = 0.0). If real, the value entered is the emissivity. If Integer, the value entered is
the ID of a TABLEM1 or TABLEM2 entry specifying the emissivity vs temperature or
a TABL3D entry specifying the emissivity vs temperature and possibly other variables.
Main Index
1162 BCBODY
Flexible or Rigid Contact Body in 2D and 3D
Describer Meaning
HBL Separation distance dependent thermal convection coefficient (Real or Integer; Default
(7,6)/(8,6) = 0.0). If Real, the value entered is the separation distance dependent thermal a
convection coefficient. If Integer, the value entered is the ID of a TABLEM1 entry
specifying the convection coefficient vs temperature or a TABL3D entry specifying the
convection coefficient vs temperature and possibly other variables.
HNL Heat transfer coefficient for nonlinear convective heat flow for near field behavior. (Real
or Integer; Default = 0.0). If Real, the value entered is the near field nonlinear
convection coefficient. If Integer, the value entered is the ID of a TABLEM1 or
TABLEM2 entry specifying the near field nonlinear convection coefficient vs
temperature or a TABL3D entry specifying the near field nonlinear convection
coefficient vs temperature and possibly other variables.
BNL Exponent associated with the nonlinear convective heat flow for near field behavior.
(Real or Integer; Default = 1.0). If Real, the value entered is the exponent associated
with the near field nonlinear convection coefficient. If Integer, the value entered is the
ID of a TABLEM1 OR TABLEM2 entry specifying the exponent associated with the
near field nonlinear convection coefficient vs temperature or a TABL3D entry
specifying the exponent associated with the near field nonlinear convection coefficient
vs temperature and possibly other variables.
HNLE Heat transfer coefficient for nonlinear convective heat flow to the environment.
(Real > 0.0 or Integer; Default = 0.0). If Real, the value entered is the environment
nonlinear convection coefficient. If Integer, the value entered is the ID of a TABLEM1
or TABLEM2 entry specifying the environment nonlinear convection coefficient vs
temperature or a TABL3D entry specifying the environment nonlinear convection
coefficient vs temperature and possibly other variables.
BNLE Exponent associated with the nonlinear convective heat flow to the environment (Real
or Integer; Default = 1.0). If Real, the value entered is the exponent associated with the
environment nonlinear convection coefficient. If Integer, the value entered is the ID of
a TABLEM1 or TABLEM2 entry specifying the exponent associated with the
environment nonlinear convection coefficient vs temperature or a TABL3D entry
specifying the exponent associated with the environment nonlinear convection
coefficient vs temperature and possibly other variables.
HNCE Natural convection coefficient for heat flow to the environment. (Real or Integer,
Default = 0.0). If Real the value entered is the environment natural convection
coefficient. If Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry
specifying the environment natural convection coefficient vs temperature or a TABL3D
entry specifying the environment natural convection coefficient vs temperature and
possibly other variables.
Main Index
BCBODY 1163
Flexible or Rigid Contact Body in 2D and 3D
Describer Meaning
BNCE Exponent associated with natural convection heat flow to the environment. (Real or
Integer; Default = 1.0). If Real, the value entered is the exponent associated with the
environment natural convection coefficient. If Integer, the value entered is the ID of a
TABLEM1 or TABLEM2 entry specifying the exponent associated with the
environment natural convection coefficient vs temperature or a TABL3D entry
specifying the exponent associated with the environment natural convection coefficient
vs temperature and possibly other variables.
CMB Heat capacity of the rigid body, when entered as a geometric entity with an associated
scalar point. (Real > 0.0; Default = 0.0). For nonzero values a grounded CDAMP4
element with the scalar point on its first side is generated internally which obtains this
capacity.
CMS Heat capacity of the environment, when associated with a scalar point. (Real > 0.0;
Default = 0.0). For nonzero values a grounded CDAMP4 element with the scalar point
on its first side is generated internally which obtains this capacity.
“PATCH3D” Entries for this continuation line describe a rigid body made up of as many 4-node
patches as desired. (Triangular patches are not available.)
IDP ID of the patch (Integer number 1 through highest value).
G1, G2, G3, G4 Grid numbers for each of the 4 nodes of the patch (see Note 5).
“BEZIER” Entries for this continuation line describe a rigid body made up of Bezier Surfaces.
NP1 Number of points in 1st direction. (Integer > 0)
NP2 Number of points in 2nd direction. (Integer > 0)
NSUB1 Number of subdivisions in 1st direction. (Integer > 0)
NSUB2 Number of subdivisions in 2nd direction. (Integer > 0)
G1, G2, G3, etc Grid numbers of each point (must be in order). There must be NP1*NP2 grid points
defined. Enter NP1 points for NP2=1, then NP2 points for NP2=2, etc. (Integer)
“NURBS2D” Entries for this continuation line describe a 2D rigid body made up of nurmbs.
NPTU Number of control points. If the control points are entered as coordinates rather than
grid IDs NPTU may be set to a negative value whose absolute value is the number of
xyz coordinates, but that is not required. (Integer, no Default)
NORU Order
NSUB Number of subdivisions
G1, G2, G3, G4 Grid numbers for each of the NPTU control points
X1, Y1, X2, Y2, Alternate method to define control points without using GRID points. There must be
etc. abs(NPTU)*NPTV (x,y,z) entries.
Homo1, Homogeneous coordinates (0.0 to 1.0) (Real). There must be NPTU entries.
Homo2,
Homo3, etc.
Main Index
1164 BCBODY
Flexible or Rigid Contact Body in 2D and 3D
Describer Meaning
Knot1, Knot2, Knot vectors (0.0 to 1.0) (Real). There must be (NPTU+NORU) entries.
Knot3, etc.
“NURBS” Entries for this continuation line describe a rigid body made up of nurbs.
NPTU Number of control points in U direction. If the control points are entered as
coordinates rather than grid IDs NPTU may be set to a negative value whose absolute
value is the number of xyz coordinates, but that is not required. (Integer > 0; Required)
NPTV Number of control points in V direction. (Integer > 0; Required)
NORU Order along U direction. (Integer > 0; Required)
NORV Order along V direction (Integer > 0; Required)
NSUBU Number of subdivisions in U direction (Integer > 0; Required)
NSUBV Number of subdivisions in V direction (Integer > 0; Required)
NTRIM Number of trimming curves (Integer > 0 or blank)
G1, G2, G3, Grid point IDs defining control points (Integer > 0). There must be NPTU*NPTV
etc. entries.
X1, Y1, Z1, X2, Alternate method to define control points without using GRID points. There must be
Y2, Z2, etc. abs(NPTU)*NPTV (x,y,z) entries.
Homo1, Homogeneous coordinates (0.0 to 1.0). There must be NPTU*NPTV entries. (Real)
Homo2,
Homo3, etc
Knot1, Knot2, Knot vectors (0.0 to 1.0). There must be (NPTU+NORU)+(NPTV+NORV) entries.
Knot3, etc (Real)
IDtrim ID of trimming vector. There must NTRIM of these entries and those entries that
follow. (Integer > 0)
NPUTtrim Number of control points for this trimming vector. (Integer > 0)
NORUtrim Order for this trimming vector. (Integer > 0)
NSUBtrim Number of subdivisions for this trimming vector. (Integer > 0)
Xisoparam First coordinate of point in isoparametric space. (Real)
Ysoparam Second coordinate of point in isoparametric space. (Real)
Homo1, Homogeneous coordinates (0.0 to 1.0) of this trimming vector. There must be
Homo2, NPTUtrim entries. (Real)
Homo3, etc
Knot1, Knot2, Knot vectors (0.0 to 1.0) of this trimming vector. There must be
Knot3, etc NPTUtrim+NORUtrim entries. (Real)
Main Index
BCBODY 1165
Flexible or Rigid Contact Body in 2D and 3D
Remarks:
1. Named continuation entries are ignored for a deformable curve or surface (BEHAV=DEFO), except
for “HEAT”.
2. The grid CGID is the reference grid for the rigid body motion. Loads and enforced motion must be
defined in the global coordinate system of CGID.
3. All continuation lines may be omitted if not required.
4. WARNING: For rigid contact, the right hand rule determines the interior side of the rigid surface.
A deformable surface which contacts a rigid surface must be on the exterior side of the rigid surface
(i.e., in the direction opposite to the right hand rule). If a rigid surface is described backwards, contact
will not occur because the deformable body is already inside the rigid body at the start of the analysis.
5. For BEZIER surfaces, enter np1*np2 points in the order shown below:
Mesh Normal Order Reversed Order
2x2 1,2,3,4 2,1,4,3
3x2 1,2,3,4,5,6 3,2,1,6,5,4
3x3 1,2,3,4,5,6,7,8,9 3,2,1,6,5,4,9,8,7
3 4 4 5 6 7 8 9
1 2 3 4
1 2 5 6
1 2 3
6. For NURBS, enter NPTU grid points G1, G2, G3, etc. (set NPTU to a positive value equal to the
number of grid points or enter X1, Y1, Z1, X2, Y2, Z2, etc. coordinates for abs(NPTU) points and
set NPTU to a negative value.
7. When IDSPL is greater than 1, these nodes are entered in pairs. For a quad surface (for example,
CQUAD4 or edge of a CHEXA) usually 4 sets of nodal pairs are needed to describe the surface. For
example, a CQUAD4 with grid numbering 1,2,4,3 would need pairs of nodes, 1,2 2,4 4,3 3,1. The
nodal pairs may be entered in any order. See Marc Volume C SPLINE (SOL 400 chapter 9) option
documentation for more details.
8. For hard contact, with HGLUE=1 (see BCTABLE for the meaning of HGLUE):
a. The temperature of the contacting grid is tied to the temperatures of the contacted element face
or the temperature of the rigid geometry when it has a scalar point associated with it.
Main Index
1166 BCBODY
Flexible or Rigid Contact Body in 2D and 3D
b. The temperature of the contacting grid is set to the rigid geometry temperature when it has no
scalar point associated with it.
Note: “Glued” thermal contact can result in overshoot of the temperatures at the interface, in
particular, if two bodies that have non-uniform initial temperatures are placed in contact. The
overshoot effect may be damped somewhat if one uses a near contact distance with some
convective heat transfer.
9. For hard contact, with HGLUE=0:
The convective heat flow per unit area over the two interfaces is given by:
q = HCT T A – T B
where T A is the contacting grid temperature and T B is the face temperature in the contact point in
case of a meshed body or the T BODY temperature in case of a rigid geometry. It is recommended to
enter the HCT value on the BCTABLE Bulk Data input, since it generally applies to body pairs and
is not a property of a single body.
10. For near contact:
q = HCV T A – T B +
BNC
HNC T A – T B +
BNL BNL
HNL T A – TB +
4 4
EMISS T A – T B +
dist dist
HCT 1 – ------------------------- + HBL ------------------------- T A T B
DQNEAR DQNEAR
where the last term is only activated when HBL 0 , T A is the contacting grid temperature and T B
is the face temperature in the contact point in case of a meshed body or the T BODY temperature in
case of a rigid geometry. It is recommended to enter the near contact heat transfer coefficients and the
corresponding exponents on the BCTABLE Bulk Data input, since they generally apply to body pairs
and are not properties of a single body.
11. For no contact:
Main Index
BCBODY 1167
Flexible or Rigid Contact Body in 2D and 3D
q = CFILM T A – T SINK +
BNCE
HNCE T A – T SINK +
BNLE BNLE
HNLE T A – T SINK +
4 4
EMISS T A – T SINK
12. The heat transfer coefficients and associated exponents can all be temperature dependent, when they
are entered as an integer value. This integer value is the table ID of a TABLEM1, TABLEM2 or
TABL3D entry (formulas are not supported on TABL3D).
13. The T SINK and T BODY temperatures can be time dependent when they are entered as a positive
integer value. This integer value is the table ID of a TABLED1, TABLED2 or TABL3D entry
(formulas are not supported on TABL3D).
14. Table IDs of tables used on the BCBODY and the BCTABLE entry must be unique.
15. TBODY entries only apply to rigid bodies (i.e., RIGID as the BEHAV value). TSINK entries only
apply to deformable bodies (meshed regions with DEFORM or HEAT as the BEHAV value).
Main Index
1168 BCBODY1
Flexible or Rigid Contact Body in 2D and 3D (New Form)
BCBODY1 Flexible or Rigid Contact Body in 2D and 3D (New Form)
Defines a flexible or rigid contact body in 2D or 3D used in SOLs 101, 400, and 700 only.
If the body is rigid, this entry may refer to BCRIGID entry by the BCRGID field to describe the body. See
Remark 1. for an important note regarding how to define the outward direction of rigid bodies (which must
point towards a flexible body for contact to occur).
Deformable bodies are described using as many standard elements as necessary and are specified by the BSID
field with BEHAV=DEFORM. Unless shrink fit or interference fit is being analyzed, deformable bodies
should not be inside other deformable bodies when the thickness of each body is taken into account.
Format: (SOLs 101 and 400 only)
1 2 3 4 5 6 7 8 9 10
BCBODY1 BID BPID DIM BEHAV BSID BCRGID BCGOUT
Format: (SOL 700 only)
1 2 3 4 5 6 7 8 9 10
BCBODY1 BID BSID
Examples of Deformable and Rigid Contact:
Example 1 -- Typical deformable body
BCBODY1 94 3001 DEFORM 103
Example 2 -- Simple rigid patch (see Remark 1. for rigid bodies)
BCBODY1 6 3001 RIGID 206 115
Describer Meaning
BID Unique contact body identification number referenced by BCONECT, BCHANGE, or
BCMOVE. (Integer > 0; Required)
BPID Parameter identification number of a BCBDPRP entry. (Integer > 0 or blank) Ignored in
SOL 700. See Remark 2.
DIM Dimension of body. (Character; Default= 3D) Ignored in SOL 700.
DIM=2D: planar body in x-y plane of the basic coordinate system, composed of 2D
elements or curves.
DIM=3D: any 3D body composed of rigid surfaces, shell elements or solid elements.
BEHAV Behavior of curve or surface (Character; Default = DEFORM) Ignored in SOL 700.
DEFORM body is deformable; RIGID body is rigid (See Remark 1.); SYMM body is a
symmetry rigid body; HEAT indicates body is a heat-rigid body (See Remark 3..).
Main Index
BCBODY1 1169
Flexible or Rigid Contact Body in 2D and 3D (New Form)
BSID For SOLs 101 and 400: Identification number of a BSURF or BCPROP entry if
BEHAV=DEFORM or HEAT, or identification number of a BCRGSRF, BCPATCH,
BCBZIER, BCNURB2, or BCNURBS entry if BEHAV=RIGID or SYMM (See Remark
4.).
For SOL 700: Identification number (RBID) of a BSURF, BCBOX, BCPROP, BCMATL,
BCSEG, BCGRID or BCELIPS entry. (Integer > 0).
BCRGID For SOLs 101 and 400: Identification number of a BCRIGID entry if BEHAV=RIGID or
SYMM. Ignored in SOL 700. (Integer > 0)
BCGOUT Reference point in basic coordinate system to calculate the global resultant contact
force/moment (integer)
-1 Origin
0 Estimated centroid of deformable body (default)
Remarks:
1. WARNING: For rigid contact, the right hand rule determines the interior side of the rigid surface.
A deformable surface which contacts a rigid surface must be on the exterior side of the rigid surface
(i.e., in the direction opposite to the right hand rule). If a rigid surface is described backwards, contact
will not occur because the deformable body is already inside the rigid body at the start of the analysis.
2. If BPID field is blank, then default values are set for the parameters defined in BCBDPRP entry.
3. For pure thermal analysis, BEHAV=DEFORM and BEHAV=HEAT are identical. However, in
coupled thermal-mechanical analysis, BEHAV=DEFORM specifies a deformable in mechanical
analysis part, while BEHAV=HEAT defines a rigid meshed body in mechanical analysis part.
4. If BCRGSRF entry does not exist, BCBODY1 entry can refer to one of the identification number of
BCPATCH, BCBZIER, BCNURB2, or BCNURBS entry directly (RBID).
Main Index
1170 BCBOX
3D Contact Region
BCBOX 3D Contact Region
Defines a 3D contact region - all elements within the region define a contact body in SOL 700.
Format (Form 1):
1 2 3 4 5 6 7 8 9 10
BCBOX ID HOW
N1 N2 N3 N4 N5 N6 N7 N8
Form 2:
BCBOX ID COORD HOW
X1 Y1 Z1 X2 Y2 Z2
X3 Y3 Z3 X4 Y4 Z4
X5 Y5 Z5 X6 Y6 Z6
X7 Y7 Z7 X8 Y8 Z8
Example (for Form 1):
BCBOX 101 0
1001 1002 1003 1004 1005 1006 1007 1008
R
Describer Meaning
ID Identification of a deformable surface corresponding to a BSID value on the BCBODY
entry if the Case Control BCONTACT=BCBOX is specified. All elements
corresponding to the designated box may potentially come into contact. See Remark 1.
(Integer > 0)
COORD Enter COORD in field 3 if x,y,z coordinates of the box are to be specified rather than
grid IDs. (Character)
HOW A flag indicating whether an element is in the defined box or not. (Integer; Default = 0)
0 If only one grid point of an element is in the box, the entire element is
considered to be in the box.
1 All grid points comprising the element must be within the box,
otherwise the element is considered outside of the box.
N1-N8 Enter 8 Grid IDs defining a box (hexa-like region) if the third field is blank. (Integer;
Required if COORD is blank)
Xi, Yi, Zi Enter eight x,y,z values in the basic coordinate system if the third field is COORD. See
Remark 6. (Real; Required if “COORD” is entered in field 3 of line 1)
Main Index
BCBOX 1171
3D Contact Region
Remarks:
1. ID must be unique with respect to all other BSURF, BCBOX, BCPROP, and BCMATL entries.
2. The deformable surface may alternately be defined using BSURF, BCPROP, or BCMATL entries.
3. Only one kind of entry (BSURF, BCBOX, BCPROP, or BCMATL) may be used to define a
particular deformable surface.
4. All elements corresponding to the IDs entered will be used to define the deformable surface.
5. The model is searched to determine whether each element lies within the specified box region as
specified by the HOW criteria option.
6. For SOL 700, the BCBOX allows a general box and edges do not need to be aligned with the
coordinates axis. The eight grid points define the box identical to the CHEXA grid point numbering.
7. BCBOX is not supported in SOLs 101 and 400.
Main Index
1172 BCBZIER
Defines a Rigid Contact Body Made up of Bezier Surfaces in SOLs 101 and 400
BCBZIER Defines a Rigid Contact Body Made up of Bezier Surfaces in SOLs 101 and 400
Defines a rigid contact body made up of Bezier surfaces used in SOLs 101 and 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCBZIER RBID NP1 NP2 NSUB1 NSUB2
G1 G2 G3 G4 -etc.-
Example:
BCBZIER 98 3 3 25 15
21 11 1 84 74 64 147 137
127
Describer Meaning
RBID Unique identification number referenced by a BCRGSRF or BCBODY1 entry. (Integer >
0) See Remark 1.
NP1 Number of points in 1st direction. (Integer > 0)
NP2 Number of points in 2nd direction. (Integer > 0)
NSUB1 Number of subdivisions in 1st direction. (Integer > 0)
NSUB2 Number of subdivisions in 2nd direction. (Integer > 0)
G1, G2, Grid numbers of each point (must be in order). There must be NP1*NP2 grid points
G3, etc. defined. Enter NP1 points for NP2=1, then NP1 points for NP2=2, etc. (Integer > 0)
Remarks:
1. If BCRGSRF entry does not exist, BCBZIER entry will be referenced by the BCBODY1 entry
directly.
2. For BEZIER surfaces, enter np1*np2 points in the order shown below
Mesh Normal Order Reversed Order
2x2 1,2,3,4 2,1,4,3
3x2 1,2,3,4,5,6 3,2,1,6,5,4
3x3 1,2,3,4,5,6,7,8,9 3,2,1,6,5,4,9,8,7
Main Index
BCBZIER 1173
Defines a Rigid Contact Body Made up of Bezier Surfaces in SOLs 101 and 400
Main Index
1174 BCELIPS
Contact Ellipsoid List- SOL 700
BCELIPS Contact Ellipsoid List- SOL 700
Defines a list of ellipsoid names (character strings) for use of contact analysis. Used in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCELIPS CID NAME1 NAME2 NAME3 NAME4 NAMEi etc
Example:
BCELIPS 1 HUB RIM HEAD CHEST
Field Content
CID Unique identification number of ellipsoid names which can be used for contact.
(Integer > 0; required)
NAME Name of an ellipsoid. (Character; required)
Remarks:
Use as many continuations as required to define the complete list of names. A blank field terminates the list..
Main Index
BCGRID (SOL 700 only) 1175
Contact Node Region
BCGRID (SOL 700 only) Contact Node Region
Grids to be included in contact analyses in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCGRID CID GID1 GID2 GID3 GID4 GID5 GID6 GID7
GID8 GID9 GID10 GID11 GID12 GID13 -etc.-
Example:
BCGRID 100 12 14 17 121 234 235 270
309 1001 THRU 2000 BY 2
Describer Meaning
ID Unique identification number of a “cloud” of grid points which can be used for contact
or RCONN, BJOIN or WALL. (Integer > 0; Required)
GID1, Gridpoint ID. THRU indicates a range to be used. BY is the increment to be used
GID2,… within this range. (Integer > 0; Required)
Remarks:
1. ID must be unique with respect to all other BSURF, BCBOX, BCPROP, BCMATL, or BCSEG
entries.
2. BCGRID may only be used for SECNDRY body definitions on the BCTABLE entry.
3. As many continuation lines as necessary may be used to define all GRID points used in the definition.
Main Index
1176 BCGRID
Contact region by a list of grid points.
BCGRID Contact region by a list of grid points.
Define a contact region by a grid point list, for SOLs 101, 103, 105, 107, 108, 109, 110, 111, 112, 200 and
400.
Format:
1 2 3 4 5 6 7 8 9 10
BCGRID BID BPID DIM
GID1 GID2 GID3 “THRU” GID4 “BY” GID5 GID6
GID7
Example:
BCGRID 2 3 3D
12 21 THRU 101 3 6
Describer Meaning
BID Unique contact face identification number referenced by BCONECT (Integer > 0;
Required). See remark 1.
BPID Parameter identification number of a BCBDPRP entry. (Integer > 0 or blank)
DIM Dimension of the contact entry. (Character; Default= “3D”), “3D” or “2D”.
GIDi Grid point ids. (Integer > 0)
Remarks:
1. BID must be unique among all BCSURF, BCBODY1 and BCGRID entries.
2. BCGRID entries are able to coexist with BCBODY1 entries. A BCGRID entry can be used with a
BCSURF or a BCBODY1 entry to construct a contact pair. The BCGRID entry must be a secondary,
the BCSURF or BCBODY must be a primary.
3. This entry only works in node to segment method.
4. The identification of BCGRID cannot be specified in the continuations of a BCONECT entry.
5. If a BCRIGID is referenced by a BCONECT, COPTS and COPTM in the BCONPRG referenced
by the BCONECT will be ignored.
Main Index
BCHANGE 1177
Changes Definitions of Contact Bodies
BCHANGE Changes Definitions of Contact Bodies
Changes definitions of contact bodies used in SOL 101 and SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
BCHANGE ID TYPE IDBOD1 N1 N2 INC
IDBOD2 N1 N2 INC IDBOD3 etc.
Example:
BCHANGE 201 NODE 1 1001 1010 1
2 2001 2021 2
Describer Meaning
ID Identification number referenced by a BCONTACT or BCHANGE Case Control
command within a SUBCASE or STEP. See Remark 1. (Integer > 0; Required)
Type Type of modification (Character; Required)
NODE Defines nodes of a contact body which may come into contact.
EXCLUDE Excludes 2 node segments in 2D or 4 node patches in 3D.
IDBODi Identification number of a contact body, BCBODY or BCBODY1 entry. (Integer > 0)
N1 Starting grid ID. More than one N1-N2-INC range may be entered for each body, see
Remark 7. (Integer > 0; Default = 1)
N2 Ending grid ID.
INC Grid ID increment.
Remarks:
1. To place an entry in the loadcase 0, set ID=0, which does not need any corresponding Case Control
command BCONTACT=0 or BCHANGE=0, and it is always executed automatically. To place an
entry in any physical loadcase (SUBCASE or STEP), the ID must be selected by the Case Control
command BCONTACT=ID or BCHANGE=ID. Note that if BCHANGE Case Control command
exists, it always dominates the selection of BCHANGE Bulk Data entries.
2. The BCHANGE entry does not apply to rigid bodies. Multiple BCHANGE entries are allowed. A
body may be entered more than once with different grid IDs.
3. BCHANGE is useful only for saving computer time and is not recommended for general usage.
4. Warning -- For the NODE option, if some nodes in a body are inadvertently omitted, they may
penetrate other bodies.
5. BCHANGE with the NODE option is not supported in Segment-to-segment contact.
Main Index
1178 BCHANGE
Changes Definitions of Contact Bodies
6. NODE and EXCLUDE may not be used simultaneously in the same BCHANGE entry.
7. If TYPE=NODE, the form of N1-N2-INC range has the following rules:
a. The format of INC is either blank or integer (> 0).
b. N1-N2-0 or N1-N2-blank represents 2 nodes (N1,N2) where 0<N1 and 0<N2,
c. N1-N2-INC, INC>0, represent a range input but 0<N1<N2.
8. If TYPE=EXCLUDE, the form of N1-N2-INC range has the following rules:
a. For node segment, N1-N2-INC is used. If 0<N1<N2 and INC>0, the range is applied. If INC-
blank or 0, it is 2 nodes (N1,N2) input that can be in any order.
b. For 4 nodes patch, (N1,N2,N3,N4), 2 sets of range, which have to input in sequence, are
required.
(IDBOD1,-N1,N2,INC1) and (IDBOD2,N3,N4,INC2) where IDBOD1=IDBOD2, Ni>0,
INC1 and INC2 are ignored.
The following example is for a 4-node patch (100,110,300,200)
1 2 3 4 5 6 7 8 9 10
BCHANGE 1 EXCLUDE 1 -100 110
1 300 200
c. For 3 nodes patch, (N1,N2,N3), 2 sets of range, which have to input in sequence, are required
(IDBOD1,-N1,N2,INC1) and (IDBOD2,N3,N3,INC2)
where IDBOD1=IDBOD2,Ni>0, INC1 and INC2 are ignored.
The following example is for a 3-noded patch (132,97,95)
1 2 3 4 5 6 7 8 9 10
BCHANGE 1 EXCLUDE 1 -132 97
1 95 95
Main Index
BCMATL 1179
3D Contact Region by Element Materials
BCMATL 3D Contact Region by Element Materials
Defines a 3D contact region by element material. All elements with the specified materials define a contact
body used in SOL 700.
Format:
1 2 3 4 5 6 7 8 9 10
BCMATL ID IM1 IM2 IM3 IM4 IM5 IM6 IM7
IM8 IM9 etc.
Example:
BCMATL 1001 101 201 301
Describer Meaning
ID Identification of a deformable surface corresponding to a BSID value on the BCBODY
entry if the Case Control command, BCONTACT=BCMATL is specified. All
elements corresponding to the material IDs specified may potentially come into
contact. See Remark 1. (Integer > 0)
IMi Material ID. A minimum of one entry is required. (Integer)
Remarks:
1. ID must be unique with respect to all other BSURF, BCBOX, BCPROP, and BCMATL entries.
2. The deformable surface may alternately be defined using BSURF, BCBOX, or BCPROP entries.
3. Only one kind of entry (BSURF, BCBOX, BCPROP, or BCMATL) may be used to define a
particular deformable surface.
4. All elements corresponding to the IDs entered will be used to define the deformable surface.
5. As many continuation lines as necessary may be used to define all material IDs associated with a
particular deformable body.
6. BCMATL may not be used to define contact regions made up of composite elements.
Main Index
1180 BCMOVE
Movement of Bodies in Contact
BCMOVE Movement of Bodies in Contact
Defines movement of bodies in contact used in SOL 101 and SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
BCMOVE ID MTYPE
IDRBOD1 IDRBOD2 IDRBOD3 etc.
Examples:
BCMOVE 33 RELEASE
1 3 5 7
BCMOVE 1 approach
Describer Meaning
ID Identification number referenced by a BCONTACT or BCMOVE Case Control
command within a SUBCASE or STEP. See Remark 1. (Integer > 0; Required)
MTYPE Movement type. (Character; Default = APPROACH)
APPROACH All rigid bodies are moved so that they all make contact with
deformable bodies.
RELEASE The contact condition is released for selected bodies.
SYNCHRON All rigid bodies are moved until the first rigid body makes
contact with a deformable body.
IDRBODi Identification numbers of contact bodies to be released, for option RELEASE only.
Points to BCBODY or BCBODY1 Bulk Data entries.
Remarks:
1. To place an entry in the loadcase 0, set ID=0, which does not need any corresponding Case Control
command BCONTACT=0 or BCMOVE=0, and it is always executed automatically. To place an
entry in any physical loadcase (SUBCASE or STEP), the ID must be selected by the Case Control
command BCONTACT=ID or BCMOVE=ID. Note that if BCMOVE Case Control command
exists, it always dominates the selection of BCMOVE Bulk Data entries. ID must be unique (only
one BCMOVE per SUBCASE).
2. For MTYPE=APPROACH and MTYPE=SYNCHRON leave all following fields blank.
3. The APPROACH and SYNCHRON options apply to rigid contact surfaces only.
4. You may release a deformable body from contact with either a deformable or rigid body.
Main Index
BCNURB2 1181
Defines a 2D Rigid Contact Body Made up of NURBS in SOLs 101 and 400
BCNURB2 Defines a 2D Rigid Contact Body Made up of NURBS in SOLs 101 and 400
Defines a 2D rigid contact body made up of NURBS used in SOLs 101 and 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCNURB2 RBID NPTU NORU NSUB
“GRID” G1 G2 G3 G4 -etc.-
or or or or or
“COORD” X1 Y1 X2 Y2
“HOMO” Homo1 Homo2 Homo3 Homo4 -etc.-
“KNOT” Knot1 Knot2 Knot3 Knot4 Knot5 -etc.-
Examples:
BCNURB2 102 4 1 1
GRID 237 101 104 235
HOMO 0.0 0.5 0.5 1.0
KNOT 0.0 0.2 0.4 0.8 1.0
BCNURB2 3001 -5 3 50
COORD -.1 .14 -.1 .04 -1.4-16 .04
.1 .04 .1 .14
HOMO 1. .707107 1. .707107 1.
KNOT 0.0 0.0 0.0 0.5 0.5 1.0 1.0
1.0
Describer Meaning
RBID Unique identification number referenced by a BCRGSRF or BCBODY1 entry.
(Integer > 0) See Remark 1.
NPTU Number of control points. If the control points are entered as coordinates rather than
grid IDs NPTU must be set to a negative value whose absolute value is the number of
xy coordinates. (Integer; no Default)
NORU Order along U direction. (Integer > 0)
NSUB Number of subdivisions. (Integer > 0)
“GRID” Indicate the start of the list of grid numbers. See Remark 2.
G1, G2, G3, G4, Grid numbers for each of the NPTU control points. (Integer > 0)
etc.
“COORD” Indicate the start of the list of xy coordinates. See Remark 2.
Main Index
1182 BCNURB2
Defines a 2D Rigid Contact Body Made up of NURBS in SOLs 101 and 400
X1, Y1, X2, Y2, Alternate method to define control points without using GRID points. There must be
etc. abs(NPTU) set of (x,y) entries. (Real)
“HOMO” Indicate the start of the list of homogeneous coordinates.
Homo1, Homo2, Homogeneous coordinates. (Real; 0.0 to 1.0) There must be NPTU entries.
Homo3, etc.
“KNOT” Indicate the start of the list of knot vectors.
Knot1, Knot2, Knot vectors. (Real; 0.0 to 1.0) There must be (NPTU+NORU) entries.
Knot3, etc.
Remarks:
1. If BCRGSRF entry does not exist, BCNURB2 entry will be referenced by the BCBODY1 entry
directly.
2. The list of grid IDs (“GRID”) and the list of xy coordinates (“COORD”) cannot coexist.
Main Index
BCNURBS 1183
Defines a Rigid Contact Body Made up of NURBS in SOLs 101 and 400
BCNURBS Defines a Rigid Contact Body Made up of NURBS in SOLs 101 and 400
Defines a rigid contact body made up of NURBS used in SOLs 101 and 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCNURBS RBID NPTU NPTV NORU NORV NSUBU NSUBV
“GRID” G1 G2 G3 G4 G5 G6
or or or or or or or -etc.-
“COORD” X1 Y1 Z1 X2 Y2 Z2
“HOMO” Homo1 Homo2 Homo3 Homo4 Homo5 Homo6 Homo7
Homo8 Homo9 -etc.-
“KNOT” Knot1 Knot2 Knot3 Knot4 Knot5 Knot6 Knot7
Knot8 Knot9 -etc.-
“TRIM” IDtrim1 IDtrim2 IDtrim3 -etc.-
Examples:
BCNURBS 48 2 1 2 1 50 50
GRID 3005 102
HOMO 1. .3333
KNOT 0.0 0.0 0.5 0.5 1. 1.
BCNURBS 63 -2 2 2 2 50 50
COORD .3 -.6 0. .3 -.1 0.
HOMO 1. 1. 1. 1.
KNOT 0.0 0.0 1. 1. 0. 0.
1. 1.
TRIM 511 2002 87 704
Describer Meaning
RBID Unique identification number referenced by a BCRGSRF or BCBODY1 entry.
(Integer > 0) See Remark 1.
NPTU Number of control points in U direction. If the control points are entered as
coordinates rather than grid IDs, NPTU must be set to a negative value whose
absolute value is the number of xyz coordinates. See Remark 2. (Integer > 0; Required)
NPTV Number of control points in V directions. (Integer > 0; Required)
NORU Order along U direction. (Integer > 0; Required)
Main Index
1184 BCNURBS
Defines a Rigid Contact Body Made up of NURBS in SOLs 101 and 400
NORV Order along V direction. (Integer > 0; Required)
NSUBU Number of subdivisions in U direction. (Integer > 0; Required)
NSUBV Number of subdivisions in V direction. (Integer > 0; Required)
“GRID” Indicate the start of the list of grid numbers. See Remark 3.
G1, G2, G3, etc. Grid point IDs defining control points. (Integer > 0) There must be NPTU*NPTV
entries.
“COORD” Indicate the start of the list of xyz coordinates. See Remark 3.
X1, Y1, Z1, X2, Alternate method to define control points without using GRID points. There must
Y2, Z2, etc. be abs(NPTU)*NPTV sets of (x,y,z) entries.
“HOMO” Indicate the start of the list of homogeneous coordinates.
Homo1, Homo2, Homogeneous coordinates (0.0 to 1.0). There must be abs(NPTU)*NPTV entries.
Homo3, etc. (Real)
“KNOT” Indicate the start of the list of knot vectors.
Knot1, Knot2, Knot vectors (0.0 to 1.0). There must be (abs(NPTU)+NORU)+(NPTV+NORV)
Knot3, etc. entries. (Real)
“TRIM” Indicate the start of the list of trimming vector IDs.
IDtrimi Trimming vector identification number of a BCTRIM entry. (Integer > 0)
Homot1, Homogeneous coordinates (0.0 to 1.0) of this trimming vector. There must be
Homot2, NPTUtrim entries. (Real)
Homot3, etc.
Knott1, Knott2, Knot vectors (0.0 to 1.0) of this trimming vector. There must be
Knott3, etc. NPTUtrim+NORUtrim entries. (Real)
Remarks:
1. If BCRGSRF entry does not exist, BCNURBS entry will be referenced by the BCBODY1 entry
directly.
2. Enter NPTU grid points G1, G2, G3, etc. (set NPTU to a positive value equal to the number of grid
points) or enter X1, Y1, Z1, X2, Y2, Z2, etc. coordinates for abs(NPTU) points and set NPTU to a
negative value.
3. The list of grid IDs (“GRID”) and the list of xyz coordinates (“COORD”) cannot coexist.
Main Index
BCONECT 1185
Defines a Contact Pair
BCONECT Defines a Contact Pair
Defines a contact pair used in SOLs 101, 103, 105, 107, 108, 109, 110, 111, 112, 200, 400 and 700. Only
SOL 101, 400 and 700 can support all contact types: touching contact, glued, step glue and permanent glue
(see Chapter 7: Contact Types of Nastran SOL 400 Getting Started Guide). Note that SOL 700 calls it “tie” contact
to glue (also step glue or permanent glue). SOL 103~112 and standard 200 (without calling SOL 400) can
only support permanent glue. When SOL 200 calls SOL 400 (or say SOL 400 optimization), it can support
all contact types.
Format:
1 2 3 4 5 6 7 8 9 10
BCONECT ID BCGPID BCPPID IDSCND IDPRIM
“SECNDRY” IDSEC1 IDSEC2 IDSEC3 IDSEC4 IDSEC5 IDSEC6 IDSEC7
IDSEC8 IDSEC9 -etc.-
“PRIMARY” IDPRIM1 IDPRIM2 IDPRIM3 IDPRIM4 IDPRIM5 IDPRIM6 IDPRIM7
IDPRIM8 IDPRIM9 -etc.-
Examples:
BCONECT 57 306 2 1002
BCONECT 9 108
SECNDRY 30 26
PRIMARY 294 135 528
Describer Meaning
ID Unique identification number referenced by a BCTABL1 entry (Integer ≥ 0). See Remark
1.
BCGPID Parameter identification number of a BCONPRG entry (Integer ≥ 0 or blank). See
Remark 2.
BCPPID Parameter identification number of a BCONPRP entry (Integer ≥ 0 or blank). See
Remark 2.
IDSCND Identification number of BCBODY1, BCSURF and BCGRID entry defining the
touching body (Integer ≥ 0 or blank). See Remarks 3. and 4.
IDPRIM Identification number of BCBODY1 and BCSURF entry defining the touched body
(Integer ≥ 0 or blank). See Remarks 5. and 6.
“SECNDRY” Indicates the start of the list of the touching bodies. See Remark 4.
Main Index
1186 BCONECT
Defines a Contact Pair
IDSECi Identification number of BCBODY1 entry defining the touching bodies (Integer ≥ 0 or
blank).
For SOL 700, leaving IDSEC1 blank will result in contact for all elements in the model.
In this case, you are allowed to use ADAPT=YES.
“PRIMARY” Indicates the start of the list of bodies touched by touching bodies. See Remark 6.
IDPRIMi Identification number of BCBODY1 entry defining touched bodies (Integer ≥ 0 or
blank).
Remarks:
1. BCONECT can be selected by the Case Control command BCONTACT=ID to define surface
contact if BCTABL1 entry does not exist. See Remarks 2.. and 3.. of BCTABL1 entry.
2. If BCGPID or BCPPID field is blank, then default values are set for the parameters of touching
bodies.
3. A short input to define a single touching body exists if the user provides IDSCND. On the other
hand, if the user leaves IDSCND blank, then “SECNDRY” descriptor is required and IDSEC1 must
be specified. Exceptions are for SOL 700 self-contact, which may use a secondary IDSEC1 of zero
and no “PRIMARY” entry.
4. “SECNDRY” and IDSECi fields will be ignored if IDSCND exists. If IDSCND field is blank, then
“SECNDRY” and IDSECi must be specified. In this case, each IDSECi will be processed separately.
5. A short input to define a single touched body exists if the user provides IDPRIM. On the other hand,
if the user leaves IDPRIM blank, then “PRIMARY” descriptor is required and IDPRIM1 must be
specified.
6. “PRIMARY” and IDPRIMi fields will be ignored if IDPRIM exists. If IDPRIM field is blank, then
“PRIMARY” and IDPRIMi must be specified.
7. The concept of Secondary and Primary relation is important to the node-to-segment contact but not
relevant for segment-to-segment contact. In segment-to-segment contact, they are mainly used to
define the contact pair(s).
8. If all the BCONPRG that are referenced by a BCONECT (which is referenced by BCTABL1) have
a value of IGLUE > 0, and this BCONECT is referenced in the 1st Loadcase SOL 101 to 112 and
SOL 200 or the 1st Step (SOL 400) then the connections are considered to be permanent and do not
change (unless a BCPARA is used to deactivate the permanent glue).
Main Index
BCONP 1187
Contact Parameters
BCONP Contact Parameters
Defines the parameters for a contact region and its properties for slideline contact in SOL 106 or SOL 129.
SOL 400 is the preferred method for contact analysis, see BCBODY1, BCONECT, BCONPRG,
BCONPRP, BCPARA and BCTABL1.
Format:
1 2 3 4 5 6 7 8 9 10
BCONP ID SECNDRY PRIMARY SFAC FRICID PTYPE CID
Example:
BCONP 95 10 15 1.0 33 1
Describer Meaning
ID Contact region identification number. See Remark 1. (Integer > 0)
SECNDRY Secondary region identification number. See Remark 2. (Integer > 0)
PRIMARY Primary region identification number. See Remark 3. (Integer > 0)
SFAC Stiffness scaling factor. SFAC is used to scale the penalty values automatically calculated by
the program. See Remark 4. (Real > 0.0; Default = 1.0)
FRICID Contact friction identification number. See Remark 5. (Integer > 0 or blank)
PTYPE Penetration type. See Remark 6. (Integer 1 or 2; Default = 1)
1 Unsymmetrical (secondary penetration only--Default)
2 Symmetrical
CID Coordinate system identification number to define the slideline plane vector and the
slideline plane of contact. See Remark 7. (Integer > 0; Default = 0, which means the basic
coordinate system)
Remarks:
1. ID field must be unique with respect to all other BCONP identification numbers.
2. The referenced SECNDRY is the identification number in the BLSEG Bulk Data entry. This is the
secondary line. The width of each secondary segment must also be defined to get proper contact
stresses. See the Bulk Data entry, BWIDTH for the details of specifying widths.
3. The referenced PRIMARY is the identification number in the BLSEG Bulk Data entry. This is the
primary line. For symmetrical penetration, the width of each primary segment must also be defined.
See the Bulk Data entry, BWIDTH for the details of specifying widths.
Main Index
1188 BCONP
Contact Parameters
4. SFAC may be used to scale the penalty values automatically calculated by the program. The program
calculates the penalty value as a function of the diagonal stiffness matrix coefficients that are in the
contact region. In addition to SFAC, penalty values calculated by the program may be further scaled
by the ADPCON parameter (see description of ADPCON parameter for more details). The penalty
value is then equal to k*SFAC*|ADPCON|, where k is a function of the local stiffness. It should be
noted that the value in SFAC applies to only one contact region, whereas the ADPCON parameter
applies to all the contact regions in the model.
5. The referenced FRICID is the identification number of the BFRIC Bulk Data entry. The BFRLC
defines the frictional properties for the contact region.
6. In an unsymmetrical contact algorithm only secondary nodes are checked for penetration into
primary segments. This may result in primary nodes penetrating the secondary line. However, the
error depends only on the mesh discretization. In symmetric penetration both secondary and primary
nodes are checked for penetration. Thus, no distinction is made between secondary and primary.
Symmetric penetration may be up to thirty percent more expensive than the unsymmetric
penetration.
7. In Figure 9-2, the unit vector in the Z-axis of the coordinate system defines the slideline plane vector.
The slideline plane vector is normal to the slideline plane. Relative motions outside the slideline plane
are ignored, and therefore must be small compared to a typical primary segment. For a primary
segment the direction from primary node 1 to primary node 2 gives the tangential direction (t). The
normal direction for a primary segment is obtained by the cross product of the slideline plane vector
with the unit tangent vector (i.e., n=z x t). The definition of the coordinate system should be such
that the normal direction must point toward the secondary region. For symmetric, penetration, the
normals of primary segments and secondary segments must face each other. This is generally
accomplished by traversing from primary line to secondary line in a counterclockwise or clockwise
fashion depending on whether the slideline plane vector forms a right-hand or left-hand coordinate
system with the slideline plane.
k-th Secondary Segment
k+1 k k-1 Secondary Line X-Y plane is the slideline
plane. Unit normal in the
l-1 Z-direction is the slideline
l+1 plane vector.
Primary Line
Arrows show positive
direction for ordering
nodes. Counterclockwise
l-th Primary from primary line to
Y Segment
secondary line.
Secondary and primary
X segment normals must face
Slideline Plane Vector each other.
Z Direction
Figure 9-2 A Typical Finite Element Slideline Contact Region
Main Index
BCONPRG 1189
Geometric Contact Parameters of Touching Bodies
BCONPRG Geometric Contact Parameters of Touching Bodies
Defines geometric contact parameters used to determine if contact occurs between bodies. For segment-to-
segment contact it also defines additional numerical parameters used to apply the constraints. The parameters
defined here are referenced by the BCONECT entry. This entry is used in conjunction with the BCONPRP
entry.
Geometric Contact Parameters of Touching Bodies in SOLs 101 and 400 for General Contact or in SOLs
101, 103, 105, 107 - 112, 200 and 400 for the Permanently Glued or Tied Contact.
Format:
1 2 3 4 5 6 7 8 9 10
BCONPRG BCGPID PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3
PARAM4 VAL4 PARAM5 VAL5 -etc.-
Example:
BCONPRG 90 ICOORD 1 IGLUE 1
Describer Meaning
BCGPID Identification number for geometric contact parameters (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 9-4 (Character).
VALi Value of a parameter. See Table 9-4 (Real or Integer).
Main Index
1190 BCONPRG
Geometric Contact Parameters of Touching Bodies
Table 9-4 Geometric Contact Parameters of Touching Bodies in SOLs 101, 103, 105, 107-112, 200 and
400
Name Description, Type and Value (Default is 0 for integer, 0.0 for Real Unless Otherwise
Indicated)
AUGDIST Penetration distance beyond which an augmentation will be applied; used by the segment-
to-segment contact algorithm only. (Real ≥ 0.0, see Remark 6. for default)
BIAS Contact tolerance bias factor. If this field is left blank, the default is the BIAS of the
BCPARA entry. A nonblank entry will override the BIAS entered on the BCPARA entry.
Note 0.0 is not default, and will override the BIAS on BCPARA. SYSTEM(758)=1 will set
0.0 same as blank. (0.0<=Real<=1.0)
CINTERF The definition varies depending on OPINTRF. (Real; Default = 0.0)
When OPINTRF is set to 0 (default), Interference closure amount, normal to the contact
surface. For CINTERF < 0.0, overlap between bodies. For CINTERF > 0.0, gap between
bodies.
When OPINTRF is set to 1, interference closure magnitude. To clear penetration, set a
negative value.
When OPINTRF is set to 2, magnitude of translation vector defining in VXINTRF,
VYINTRF and VZINTRF.
When OPINTRF is set to 3, not used.
When OPINTRF is set to 4, not used.
COPTS, Flag to indicate how secondary and primary surfaces may contact. See Remark 2. (Integer;
COPTM Default = 1011). COPTS and COPTM are ignored if secondary or primary in BCONECT
is a BCGRID entry but honored if it is a BCSURF entry.
ERROR Distance below which a node is considered touching a body. Default = blank, automatic
calculation. See BCPARA Bulk Data entry for more details. (Real)
HARDS Hard-soft ratio. This entry is only used if double-sided contact with automatic constraint
optimization is used, i.e. ISTYP=2 on the BCBDPRP entry. The hard-soft ratio can be used
by the program if there is a significant difference in the average stiffness of the contact
bodies (expressed by the trace of the initial stress-strain law). If the ratio of the stiffnesses is
larger than the hard-soft ratio, the nodes of the softest body are the preferred secondary
nodes. (Real; Default = 2.0) This parameter is ignored for the permanently glued contact.
FGCFLG Flag to activate Cohesive (Flexible) Glued Contact: (See Remark 12.)
0 – no Cohesive (Flexible) Glued Contact
1 – activate Cohesive (Flexible) Glued Contact
FGCNST Equivalent normal contact stiffness of connector for Cohesive (Flexible) Glued Contact
FGCTST Equivalent tangential contact stiffness of connector for Cohesive (Flexible) Glued Contact
FGCNSTR ID of table for define contact normal stress versus relative displacement for Cohesive
(Flexible) Glued Contact. Only TABL3D allowable.
FGCTSTR ID of table for define contact tangential stress versus relative displacement for Cohesive
(Flexible) Glued Contact. Only TABL3D allowable.
Main Index
BCONPRG 1191
Geometric Contact Parameters of Touching Bodies
FGCNSTI ID of table for define contact normal stiffness versus relative displacement or temperature
for Cohesive (Flexible) Glued Contact. Only TABL3D allowable.
FGCTSTI ID of table for define contact tangential stiffness versus relative displacement or
temperature for Cohesive (Flexible) Glued Contact. Only TABL3D allowable.
FGCRCEN Reference Grid at which resultant contact force of secondary body to primary body is
evaluated. See Remark 12.
FGCRCN1 Reference Grid at which resultant contact force of primary body to secondary body is
evaluated.
Default of FGCRCN1 is FGCRCEN
ICOORD Enter 1 to modify the coordinates of a node in contact with a deformable body so that
stress-free initial contact can be obtained. Enter 2 to extend the tangential error tolerance
at sharp corners of deformable bodies to delay sliding off a contacted segment. Enter 3 to
have both 1 and 2 active. (Integer; Default = 0)
IGLUE Flag to activate glue options (Integer ≥ 0). Default is 0, no glue option. See JGLUE option
for controlling a glue contact type in details. This field must be specified for the
permanently glued contact. See Remarks 4. and 5. A negative value of IGLUE indicates that
this method of glue will be used for the entire Step in SOL 400. See Remark 9.
1 or -1 Activates the glue option. In the glue option, all degrees-of- freedom of the contact nodes
are tied in case of deformable-deformable contact once the node comes in contact. The
relative tangential motion of a contact node is zero in case of deformable-rigid contact. The
node will be projected onto the contact body. For the permanently glued contact, this
option is recommended when there is no gap or overlap between contact surfaces or initial
stress free contact is specified.
2 or -2 Activates a special glue option to insure that there is no relative tangential and normal
displacement when a node comes into contact. An existing initial gap or overlap between
the node and the contacted body will not be removed, as the node will not be projected onto
the contacted body. To maintain an initial gap, ERROR should be set to a value slightly
larger than the physical gap.
3 or -3 Insures full moment carrying glue when shells contact. The node will be projected onto the
contacted body. For the permanently glued contact, this option is recommended when
moments are important and there is no gap or overlap between contact surfaces or initial
stress free contact is specified.
4 or -4 Insures full moment carrying glue when shells contact. The node will not be projected onto
the contact body and an existing initial gap or overlap between the node and the contacted
body will not be removed, as the node will not be projected onto the contacted body.
Main Index
1192 BCONPRG
Geometric Contact Parameters of Touching Bodies
ISEARCH Option for contact searching order, from Secondary to Primary or from Primary to
Secondary, for deformable contact bodies. ISEARCH is not necessary in segment-to-
segment contact. (Integer; Default = 0)
0 (Double orders search) the search order is from lower BCBODY1 ID's to higher ones
first. Then it searches the opposite order. See Remark 3.
1 (Single order search) the searching order is from Secondary to Primary.
2 (Single order search) let the program decide which search order. See Remark 3.
Note that ISTYP in BCBDPRP or BCBODY is supported with ISEARCH=0 only.
JGLUE This option is only relevant if the glue option is invoked (IGLUE > 0). Enter 0 if a node
should not separate (default). Enter 1 to invoke the standard separation behavior based on
the maximum residual force (related to FNTOL parameter of BCPARA or BCONPRP
entry). Enter 2 to activate breaking glue (related to BGM, BGN, BGSN and BGST
parameters of BCONPRP entry). (Integer; Default = 0) This parameter is ignored for the
permanently glued contact or step glued contact, see Remark 9.
PENALT Augmented Lagrange penalty factor; used by the segment-to-segment contact algorithm
only. (Real ≥ 0.0; see Remark 7. for default)
SLIDE Delayed slide off distance. This entry should not be made unless ICOORD ≥ 2 (see above).
When using the delayed slide off option, a node sliding on a segment will slide off this
segment only if it passes the node (2-D) or edge (3-D) at a sharp corner over a distance
larger than the delayed slide off distance. By default, the delayed slide off distance is related
to the dimensions of the contacted segment by a 20 percent increase of its isoparametric
domain. (Real; Default=0.0)
STKSLP Maximum allowable slip distance for sticking, beyond it there is no sticking, only sliding
exists, used by the segment-to-segment contact algorithm only. (Real ≥ 0.0; Default = 0.0)
See Remark 8.
TPENALT Augmented Lagrange penalty factor for sticking part of friction, used by the segment-to-
segment contact algorithm only. (Real > 0.0) The default is PENALT/1000, where
PENALT parameter is the Augmented Lagrange penalty factor for normal contact.
OPINTRF The method for interference fit. (Integer0; Default=0) See Remark 10.
0 small interference fit (solved in one increment)
1 interference fit varying with time; resolved in the normal direction
2 interference fit varying with time in a user specified direction
3 interference fit varying with time using scale factor
4 automatic interference fit varying with time and node location
Main Index
BCONPRG 1193
Geometric Contact Parameters of Touching Bodies
TBINTRF TABLED1 id used by interference fit. (Integer>0; Required only when OPINTRF > 0)
When OPINTRF=1, TABLED1 id giving variation of interference closure with respect to
time
When OPINTRF=2, TABLED1 id giving variation of magnitude of translation vector with
respect to time
When OPINTRF=3, TABLED1 id giving variation of magnitude of scale factor with
respect to time
When OPINTRF=4, TABLED1 id giving variation of magnitude of penetration vector
projected node position on the primary segment with respect to time
CBINTRF Contact body selection for interference fit. Only required when OPINTRF=2, 3 or 4.
(Integer=0 or 1; Default=0)
0 is secondary body, 1 is primary body
When OPINTRF=2, secondary or primary body for which translation vector to be used
When OPINTRF=3, secondary or primary body for which scale factors to be used.
When OPINTRF=4, secondary or primary body of which penetrations to be determined.
CDINTRF Coordinate system ID of VXINTRF, VYINTRF and VZINTRF for interference fit. Only
required when OPINTRF=2, 3. (Integer0; Default=0)
When OPINTRF=2, Coordinate system for direction cosines for the translation vector.
When OPINTRF=3, Coordinate system for scale factor vector.
VXINTRF X component of vector for interference fit. Only required when OPINTRF=2, 3. (Real;
default=0.0)
When OPINTRF=2, Direction cosines for the translation vector.
When OPINTRF=3, scale factor vector
VYINTRF Y component of vector for interference fit. Only required when OPINTRF=2, 3. (Real;
default=0.0)
When OPINTRF=2, Direction cosines for the translation vector.
When OPINTRF=3, scale factor vector.
VZINTRF Z component of vector for interference fit. Only required when OPINTRF=2, 3. (Real;
default=0.0)
When OPINTRF=2, Direction cosines for the translation vector.
When OPINTRF=3, scale factor vector.
PTINTRF Penetration search tolerance for interference fit. Only required when OPINTRF=4.
(Real0.0; default=error tolerance*100)
XCINTRF X component of center of scaling. Only required when OPINTRF=3. (Real; default=0.0)
Center is described in global coordinate (Coord0).
YCINTRF Y component of center of scaling. Only required when OPINTRF=3. (Real; default=0.0)
Center is described in global coordinate (Coord0).
ZCINTRF Z component of center of scaling. Only required when OPINTRF=3. (Real; default=0.0)
Center is described in global coordinate (Coord0).
OPINGP Initial gap or overlap option. See Remark 11.(Integer 0; default=0)
0 not used
1 initial gap or overlap
Main Index
1194 BCONPRG
Geometric Contact Parameters of Touching Bodies
TOLINGP Search tolerance of initial overlap. (Real 0.0; default= average edge length of all contact
segments, required only when OPINGP =1)
TOLING1 Search tolerance of initial gap. (Real 0.0; default=average edge length of all contact
segments, required only when OPINGP =1) See Remark 14.
CDINGP Contact body to be adjusted. (Integer 0; default=0, required only when OPINGP =1)
0 secondary body
1 primary body
MGINGP Gap or overlap magnitude. (Real ; default=0.0, required only when OPINGP =1)
> 0 gap
=0 Preserve initial clearance distance. See Remark 11.
< 0 overlap
SFNPNLT Scale factor of augmented Lagrange penalty factor along contact normal direction; used by
segment-to-segment contact method only. (Real>0.0;Default=1.0) SFNPNLT*PENALT is
used in analysis.
If this field is left default, value of SFNPNLT entered in BCPARA will be used. A nonblank
value entered in SFNPNLT will override the value of SFNPNLT in BCPARA.
SFTPNLT Scale factor of augmented Lagrange penalty factor along contact tangential direction; used
by segment-to-segment contact method only. (Real>0.0;Default=1.0)
SFTPNLT*TPENALT is used in analysis.
If this field is left default, value of SFTPNLT entered in BCPARA will be used. A nonblank
value entered in SFTPNLT will override the value of SFTPNLT in BCPARA.
TCNTCTL Flag to define the touching contact status in linear perturbation and ignoring the touching
Contact status determined by the contact analysis in NLSTATIC analysis at the load point
assigned by NLIC. (Integer; Default = 0).
Value of TCNTCTL defined in BCONPRG will override one defined in BCPARA.
0 - Skip this option, keep the original contact status obtained in NLSTATIC
1 - Assuming sliding status of touching contact for contact and frictional stiffness matrix
calculation.
2 - Assuming sticking status of touching contact for contact and frictional stiffness matrix
calculation.
3 - Assuming glued contact status for touching contact for contact stiffness matrix
calculation.
Remarks:
1. With Node-to-Segment contact (N2S), the multipoint constraint equations (MPC equations)
internally created from general contact or glued contact can be printed out in standard Nastran punch
file by using case control command, NLOPRM MPCPCH.
2. COPTS and COPTM are packed numbers designating how the surfaces may contact using the
formula
COPTx=A+10*B+1000*C
where the following codes apply:
A: the outside of the solid elements in the body.
Main Index
BCONPRG 1195
Geometric Contact Parameters of Touching Bodies
• = 1: the outside will be in the contact description (Default).
B: (flexible bodies): the outside of the shell elements in the body.
• = 1: both top and bottom faces will be in the contact description, thickness offset will be included
(Default).
• = 2: only bottom faces will be in the contact description, thickness offset will be included.
• = 3: only bottom faces will be in the contact description, shell thickness will be ignored.
• = 4: only top faces will be in the contact description, thickness offset will be included.
• = 5: only top faces will be in the contact description, shell thickness will be ignored.
• = 6: both top and bottom faces will be in the contact description, shell thickness will be ignored.
Note: The choice B = 6 for both bodies in a contact combination is only meaningful for glued
contact. If in such cases separation is allowed, separated nodes will not come into contact
anymore, unless a new CONTACT TABLE is defined to reset the value of B.
Note: For node-to-segment with edge-to-edge glue contact, use B=6.
Note: For thermal contact with 2D shell elements, i.e. uniform temperature gradient across
thickness, do not use B=2 or B=3.
B: (rigid bodies): the rigid surface.
• = 1: the rigid surface should be in the contact description (Default).
C: (flexible bodies): the edges of the body.
• = 1: only the beam/bar edges are included in the contact description (Default).
• = 10: only the free and hard shell edges are included in the contact description.
• = 11: both the beam/bar edges and the free and hard shell edges are included in the contact
description.
Note that C has no effect if beam-to-beam contact is not switched on. (BEAMB ≠ 1 on BCPARA).
Note that C has no effect if segment-to-segment contact is used.
3. When ISEARCH=0 (and ISTYP=0 in default on BCBDPRP), the search order is from lower
BCBODOY1 ID to higher one to create the first set of contact constraints and then add the
constraints in the search order from higher BCBODY1 ID to lower one as long as they are not in
conflict with the first set.
When ISEARCH=2, the program looks into the smallest element edge at the outer boundary (and
the smallest thickness in case of shell elements) of each BCBODY1. Then, the search order of the two
deformable contact bodies is determined by the following rule when ID1 < ID2.
CL1= Min(1/20 of the smallest edge,1/4 of the smallest thickness) of BCBODY1 ID1
CL2= Min(1/20 of the smallest edge,1/4 of the smallest thickness) of BCBODY1 ID2
The search order is from lower BCBODY1 ID1 to higher BCBODY1 ID2 if CL1≤1.05*CL2.
Otherwise, if CL1>1.05*CL2 the search order is from BCBODY1 ID2 to BCBODY1 ID1.
4. For the permanently glued contact, IGLUE = ±2 or ±4 is favorable to pass the GROUNDCHECK.
The initial stress free contact is also available to preserve the six rigid body modes with IGLUE = ±1
or ±3.
Main Index
1196 BCONPRG
Geometric Contact Parameters of Touching Bodies
5. A permanently glued contact for small rotation cannot be used to glue a deformable body to a rigid
one. If it is a SOL 101 or SOL 400 job, the permanently glued contact for large deformation and
rotation (IGLUE <0) or general contact (IGLUE > 0) with glued option must be performed.
6. By default, the threshold value of this penetration distance is 0.05 times the default contact
characteristic distance.
AUGDIST = 0.05L
7. The penalty factor used in the augmented Lagrange method is by default derived from the contact
characteristic distance and the stiffness of the deformable contact bodies involved (note that the
dimension of the penalty factor is force per cubic length).
0.5 S i + Sj
PENALT = ----------------------------
L
The body stiffness (Si and Sj), are either defined by the average trace of the initial stress-strain law of
the elements defining the two contact bodies or by the average bulk modulus for (nearly)
incompressible rubber materials, whichever of the two is the largest.
For continuum elements, the characteristic length (L) is given by one half of the average length of all
the edges being part of the contact boundary. For shell elements, the characteristic length is given by
half of the average thickness of all the shell elements being part of a contact body. When there is
contact between a solid and a shell element, then the characteristic length is defined by the shell
element.
In case of contact with a rigid body, since there is no body stiffness associated with a rigid body, the
default value is related to the deformation body only and is given by
1000S i
PENALT = ----------------
L
8. If STKSLP is set to 0.0 (Default), the sticking stiffness K1 is equal to the maximum friction force
(µ·Fnormal, where µ is the friction coefficient) divided by the maximum sticking displacement.
Otherwise, K1 is equal to the maximum friction force divided by the value of STKSLP.
9. A negative value of IGLUE enforces the gluing of the pair of bodies in the BCONECT that reference
this BCONPRG is based upon the geometric conditions at the beginning of the step and will not
change over this step. IGLUE will be changed to negative automatically if SYSTEM(758)=2 when
Permanently Glued setting is found with large rotation/deformation effect turned on.
10. For interference fit contact, the following options are available.
CINTERF, OPINTRF, TBINTRF, CBINTRF, CDINTRF, VXINTRF, VYINTRF, VZINTRF,
PTINTRF, XCINTRF, YCINTRF and ZCINTRF
11. For setting the initial gap or overlap, the following options are available. OPINGP, TOLINGP,
CDINGP and MGINGP.
When OPINGP is 1 in means that there it will try to preserve a distance between the two bodies often
called the clearance distance.
When MGINGP is zero, the clearance is not changed from the distance between the original
coordinate positions of the nodes. This is call the distance D0
Main Index
BCONPRG 1197
Geometric Contact Parameters of Touching Bodies
When MGINGP is > 0 it means the distance between the bodies can shrink (i.e. the bodies can get
closer together), but when the distance reaches D0 - MGINGP. The clearance condition is satisfied
and this clearance distance (D0 - MGINGP ) is preserved.
When MGINGP is < 0 in means that it considers the bodies to be overlapping, so it first tries to
separate them by a distance = |MGINGP|; then it imposes the clearance condition such that the
clearance distance is D0 + |MGINGP|
12. Please note that
• Cohesive Contact is supported for only for segment-to-segment contact.
• All limitations of segment-to-segment contact is applicable for cohesive contact feature also.
• Breaking Glue feature is not supported with Cohesive contact.
• FGCNST/FGCNSTI/FGCNSTR are mutually exclusive; FGCTST/FGCTSTR/FGCRSTI
are mutually exclusive.
• FGCRCEN/FGCRCN1 applies to all contact pairs, not limited to cohesive contact
(FGCFLG=1) pairs .
13. When the initial stress-free(ICOORD=1), Node-to-Segment updates model geometry to close the
gap, nodes are projected onto the contact body; but Segment-to-Segment treats initial stress-free as
pre-stress in the equation without geometry update, no node projection is considered.
14. TOLINGP and TOLING1 follows the rules below.
a. When both of TOLINGP and TOLING1 are not defined, the default value of average edge
length of all contact segments will be used for both.
b. When TOLINGP is only defined, TOLINGP value will be used for both of TOLINGP and
TOLING1.
c. When TOLING1 is only defined, TOLING1 value will be used for TOLING1 only, and the
default value of average edge length of all contact segments will be used for TOLINGP.
d. When both of TOLINGP and TOLING1 are defined, each values are used for each case.
15. For SOL108, SOL111, SOL200 and SOL400 for ANALYSIS=DFREQ or MFREQ with frequency
dependent materials, the contact stiffness is computed using nominal material properties and is not
frequency dependent.
Main Index
1198 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700
BCONPRG-700 Geometric Contact Parameters of Touching Bodies in SOL 700
Defines geometric contact parameters of touching bodies used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10 11
BCONPRP PID PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3
PARAM4 VAL4 PARAM5 VAL5 -etc.-
Example:
BCONPRP 90 IGLUE 1
Describer Meaning
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 9-5 (Character).
VALi Value of a parameter. See Table 9-5 (Real or Integer).
Main Index
BCONPRG-700 1199
Geometric Contact Parameters of Touching Bodies in SOL 700
Table 9-5 Geometric Contact Parameters of Touching Bodies in SOL 700
Name Description, Type and Value (Default is 0 for integer, 0.0 for Real Unless Otherwise
Indicated)
IGLUE Flag to activate glue option (Integer = 0 or 1). Default is 0, no glue option. JGLUE option
controls a glue contact type in details. Without assigning IGLUE and JGLUE options, tied
contact methods (METHOD=TIEDxxx) can assign glue contact types as well.
0. No glue contact.
1. Activates the glue option. In the glue option, all degrees-of- freedom of the
contact nodes are tied in case of deformable-deformable contact once the node
comes in contact. The relative tangential motion of a contact node is zero in case
of deformable-rigid contact. The node will be projected onto the contact body.
JGLUE This option is only relevant if the glue option is invoked (IGLUE > 0). See
METHOD=TIEDxxx. (Integer ≥ 0; Default = 0) The following options are available:
0 Secondary nodes in contact and which come into contact will permanently stick.
Tangential motion is inhibited. This option is only available with
METHOD=SS1WAY or SS2WAY and AUTO=YES.
METHOD Character, Influences the contact type used. See Remark 18. (Character, Default = FULL)
Options are:
FULL: Regular Contact
AIRBAG: Single Surface Contact
SS1WAY: Surface To Surface One Way
SS2WAY: Surface To Surface Two Way
RB1WAY: Rigid Body One Way To Rigid Body
RB2WAY: Rigid Body Two Way To Rigid Body
RNRB: Rigid Nodes To Rigid Body
TIEDNS: Tied Nodes to Surface
TIEDNSO: Tied Nodes to Surface with Offset
RELLIPS: Tied contact between grid points or rigid materials to ATB dummies. See
Remark 4.
BELT: Suited for modeling contact between a belt element and a rigid structure.
Primary secondary contact only. The contact logic doesn't apply a contact force, but
applies an enforced displacement and velocity that keeps the secondary nodes
exactly on top of the primary face. The secondary node does not slide relative to the
primary face when the friction coefficient (FS) is set to 1E20
Main Index
1200 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700
BELT1: Identical to BELT algorithm, except that the secondary nodes are initially
repositioned on top of the closest primary face. All secondary nodes initially
penetrated or within a distance of INITMON from a primary face, are repositioned.
DRAWBEAD: Suited for modeling a drawbead. STYPE Must be GRID. The list
of secondary nodes must be ordered along the drawbead line. MTYPE Must be
SURF. The restraining force per unit drawbead length is specified in the field
DRWBEADF. It is V2 version contact.
DRAWBDV4: Suited for modeling a drawbead. STYPE Must be GRID. The list
of secondary nodes must be ordered along the drawbead line. MTYPE Must be
SURF. The restraining force per unit drawbead length is specified in the field
DRWBEADF. It is V4 version contact.
ADAPT Character, influences the contact type used. (Character, Default = NO)
Options are NO or YES.
When ADAPT=YES, the BCBODY1 entries IDPRIMi must be defined as:
behav=DEFORM
bsid references a BCPROP
THICK Shell thickness scale factor. (Real > 0.0; Default = same as the value in
DYPARAM,CONTACT,THICK)
THICKOF Artificial contact thickness offset. (Real > 0.0; Default = 0.0)
PENV Overwrites the default maximum penetration distance factor. (Real > 0.0;Default = 1.E20)
MAXPAR Maximum parametric coordinate in segment. (Real > 0.0; Default = 1.025), search (values
1.025 and 1.20 recommended). Larger values can increase cost. If zero, the default is set to
1.025. This factor allows an increase in the size of the segments. May be useful at sharp
corners.
SOFT Soft constraint option: (Integer ≥ 0; Default = 1)
1 Soft constraint formulation (same as original Dytran method).
In the soft constraint option, the interface stiffness is based on the nodal mass and the global
time step size. This method is more suited for contact between two materials where the
elastic moduli vary greatly.
IGNORE Ignore initial penetrations. (Integer, Default = 1)
0 Take default from PARAM,DYCONIGNORE*,<value> (Default)
1 Allow initial penetrations to exist by tracking it
2 Move nodes to eliminate initial penetrations
Main Index
BCONPRG-700 1201
Geometric Contact Parameters of Touching Bodies in SOL 700
AUTO Activation of automatic contact (Character, Default = Yes.)
Options are:
YES Automatic Contacts Activated
NO Non-Automatic Contact Activated. This option is not recommended when
Distributed Memory Parallel is activated.
SIDE Defines which side will be the monitoring side of a primary face. The opposite side of the
primary face will be the penetration side. See Remark 1. (Characters; default=BOTH)
BOTH: The side from which a secondary node approaches the primary face will become
the monitoring side.
TOP:The monitoring side will always be on the side of the primary face that its normal is
pointing at.
BOTTOM: The monitoring side is always on the opposite side of the primary face that its
normal is pointing at.
WEIGHT The contact force is multiplied by a mass-weighting factor. The following options are
available. See Remark 25. (Character; default=BOTH)
BOTH:M_scale=(M_secondary M_primary)/(M_secondary+M_primary )
SECNDRY: M_scale=M_secondary
PRIMARY: M_scale=M_primary
NONE:M_scale=1.0
MONDIS Defines the fixed part of the monitoring distance. When the normal distance of a secondary
node to a primary face becomes smaller than the monitoring distance the secondary node
will tag itself to the primary face. The side from which the secondary node is moving
towards the primary face becomes the monitoring region. (Character; default=FACTOR)
FACTOR: The monitoring distance is equal to a factor times a characteristic length of the
primary faces. The factor is specified in MONDISV.
DISTANCE: The monitoring distance is specified in MONDISV.
MONDISV Value of the monitoring distance or value of the FACTOR to calculate the monitoring
distance. (Real; default=2.0)
INITMON Fixed part of the monitoring distance used during the initialization. If not specified, the
value of MONDIS is used. (Real > 0.0; default=MONDIS)
Main Index
1202 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700
Remarks:
1. When METHOD=RELLIPS is used, BCGRID or BCMATL are only available for SECNDRY body
and BCELIPS is only available for PRIMARY body. When BCMATL is used, the MATRIG id or
RBE2 id are only acceptable. When Euler solver is deactivated, no output will be generated for the
Eulerian elements.
2. The options TOP/BOTTOM are useful in the following cases:
a. When a secondary node initially is located on the primary face (see the picture below), the contact
situation is uniquely defined, only if the TOP or BOTTOM side of the primary surface is defined:
SIDE=TOP case:
b. When hooking of secondary nodes on the wrong side of a primary face might occur. This often
is the case when the primary face is at the edge of a shell element structure:
SIDE=BOTTOM case: penetration of node 1 (SIDE=BOTH: no penetration of node 1)
3. Recommended usage of WEIGHT:
SECNDRY PRIMARY WEIGHT
Deformable Deformable BOTH
Deformable Rigid SECNDRY
Rigid Deformable PRIMARY
Rigid Rigid NONE
Default setting when BCELIPS is used in SECNDRY or PRIMARY:
Main Index
BCONPRG-700 1203
Geometric Contact Parameters of Touching Bodies in SOL 700
SECNDRY PRIMARY WEIGHT
Non-BCELIPS Non-BCELIPS NONE
BCELIPS
4. When METHOD=RELLIPS is used, BCGRID or BCMATL are only available for SECNDRY body
and BCELIPS is only available for PRIMARY body. When BCMATL is used, the MATRIG id or
RBE2 id are only acceptable.
Main Index
1204 BCONPRP
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400
BCONPRP Physical Contact Parameters of Touching Bodies in SOLs 101 and 400
Defines physical contact parameters of touching bodies used in SOLs 101 and 400 only. The parameters
defined here are referenced by the BCONECT entry. This entry is used in conjunction with the BCONPRG
entry.
Format:
1 2 3 4 5 6 7 8 9 10
BCONPRP PID PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3
PARAM4 VAL4 PARAM5 VAL5 -etc.-
Example:
BCONPRP 90 FRIC 0.3
Describer Meaning
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowabe names are given in Table 9-6 (Character).
VALi Value of a parameter. See Table 9-6 (Real or Integer).
Main Index
BCONPRP 1205
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400
Table 9-6 Physical Contact Parameters of Touching Bodies in SOLs 101 and 400
Name Description, Type and Value (Default is 0 for integer, 0.0 for Real Unless Otherwise
Indicated)
BGM Exponent for the tangential stress term in deciding if a glue-contact will break. See Remark
1. (Real; Default = 2.0)
BGN Exponent for the normal stress term in deciding if a glue-contact will break. See Remark 1.
(Real; Default = 2.0)
BGSN Maximum normal stress for breaking glue. See Remark 1. (Real; Default = 0.0)
BGST Maximum tangential stress for breaking glue. See Remark 1. (Real; Default = 0.0)
BNC Exponent associated with the natural convection coefficient for near field behavior. If Real,
the value entered is the exponent associated with near field natural convection coefficient.
If Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry specifying the
exponent associated with the near field natural convection coefficient vs. temperature or a
TABL3D entry specifying the exponent associated with the near field natural convection
coefficient vs. temperature and possibly other variables. Ignored in a pure structural analysis.
See Remark 5. (Real or Integer; Default = 1.0.)
BNL Exponent associated with the nonlinear convective heat flow for near field behavior. If Real,
the value entered is the exponent associated with the near field nonlinear convection
coefficient. If Integer, the value entered is the ID of a TABLEM1 OR TABLEM2 entry
specifying the exponent associated with the near field nonlinear convection coefficient vs
temperature or a TABL3D entry specifying the exponent associated with the near field
nonlinear convection coefficient vs temperature and possibly other variables. Ignored in a
pure structural analysis. See Remark 5. (Real or Integer; Default = 1.0)
DQNEAR Distance below which near thermal contact behavior occurs. Used in heat transfer analysis
only. See Remark 2. (Real; Default = 0.0; which means near contact does not occur)
EMISS Emissivity for radiation to the environment or near thermal radiation. If Real, the value
entered is the emissivity. If Integer, the value entered is the ID of a TABLEM1 or TABLEM2
entry specifying the emissivity vs. temperature or a TABL3D entry specifying the emissivity
vs. temperature and possibly other variables. Ignored in a pure structural analysis. See
Remark 5. (Real or Integer; Default = 0.0)
FNTOL Separation force, stress, or fraction above which a node separates from a body. FNTOL is
closely related to IBSEP. Its default value is dependent on the IBSEP value. (Real)
FRIC Friction coefficient. If the value is an integer, it represents the ID of a TABLEM1,
TABLEM2 or TABL3D, i.e., a temperature-dependent or multi-dimensional table.
(Real ≥ 0.0 or Integer > 0; Default = 0.0)
FRLIM Friction stress limit. This entry is only used for friction type 6 (Coulomb friction using the
bilinear model). If the shear stress due to friction reaches this limit value, then the applied
friction stress will be reduced so that the maximum friction stress is given by min(µn,
limit), with µ the friction coefficient and n the contact normal stress. (Real; Default =
1.0E20)
Main Index
1206 BCONPRP
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400
HBL Separation distance dependent thermal convection coefficient. If Real, the value entered is
the convection coefficient. If Integer, the value entered is the ID of a TABLEM1 or
TABLEM2 entry specifying the convection coefficient vs. temperature or a TABL3D entry
specifying the convection coefficient vs. temperature and possibly other variables. Ignored
in a pure structural analysis. See Remark 5. (Real or Integer; Default = 0.0)
HCT Contact heat transfer coefficient. If Real, the value entered is the contact heat transfer
coefficient. If Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry
specifying the contact heat transfer coefficient vs. temperature or a TABL3D entry
specifying the contact heat transfer coefficient vs. temperature and possibly other variables.
Ignored in a pure structural analysis. See Remark 5. (Real or Integer; Default = 0.0; In a
thermal/mechanical coupled analysis a default value of 1.0E6 is used when the mechanical
glue option is activated, i.e., when IGLUE > 0.)
HCV Convection coefficient for near field behavior. If Real, the value entered is the near field
convection coefficient. If Integer, the value entered is the ID of a TABLEM1 or TABLEM2
entry specifying the near field convection coefficient vs. temperature or a TABL3D entry
specifying the near field convection coefficient vs. temperature and possibly other variables.
Ignored in a pure structural analysis. See Remark 5. (Real or Integer; Default = 0.0)
HGLUE Flag to activate the thermal glue option. When left blank or set to zero, thermal contact
conditions will be treated by convective heat transfer between the bodies. When set to 1, the
temperature fields of the bodies are tied as soon as they come in contact and there will be
no convective heat transfer over the body interfaces. Ignored in a pure structural analysis.
See Remarks 3. , 4. and 5. (0 < Integer < 1; Default = 0)
HNC Natural convection coefficient for near field behavior. If Real, the value entered is the near
field natural convection coefficient. If Integer, the value entered is the ID of a TABLEM1
or TABLEM2 entry specifying the near field natural convection coefficient vs. temperature
or a TABL3D entry specifying the near field natural convection coefficient vs. temperature
and possibly other variables. Ignored in a pure structural analysis. See Remark 5. (Real or
Integer; Default = 0.0).
HNL Heat transfer coefficient for nonlinear convective heat flow for near field behavior. If Real,
the value entered is the near field nonlinear convection coefficient. If Integer, the value
entered is the ID of a TABLEM1 or TABLEM2 entry specifying the near field nonlinear
convection coefficient vs. temperature or a TABL3D entry specifying the near field
nonlinear convection coefficient vs. temperature and possibly other variables. Ignored in a
pure structural analysis. See Remark 5. (Real or Integer; Default = 0.0)
Remarks:
1. Breaking Glue provides glued contact to all GRID's at their very 1st contact. This kind of glued-
contact will break if
(sigma_n/BGSN)**bgn + (sigma_t/BGST)**bgm > 1.0
Main Index
BCONPRP 1207
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400
When a contact node breaks due to the above criterion, standard contact is activated if it comes into
contact again. If BGSN = 0.0 the first term is ignored. Similarly, the second term is ignored if BGST
= 0.0. For SOL 400, parameters BGSN, BGST, BGM and BGN are only required if JGLUE = 2. If
both BGSN and BGST are equal to 0.0, JGLUE will be set to 0 internally. If Step Glue is used, then
Breaking Glue is inactive in this step. If Permanent Glue is active, then Breaking Glue is inactive.
2. For near contact the following convective heat flow law describes the heat exchange per unit area
between the body areas (“near” contact is when bodies are not touching each other – but are close
enough for convection and radiation.):
q = HCV T A – T B +
BNC
HNC T A – T B +
BNL BNL
HNL T A –TB +
4 4
EMISS T A – T B +
dist dist
HCT 1 – ------------------------- + HBL ------------------------- T A – T B
DQNEAR DQNEAR
where the last term is only activated when HBL ≠ 0, TA is the contacting grid temperature and TB is
the face temperature in the contact point in case of a meshed body or the TBODY temperature in case
of a rigid geometry.
3. For hard contact (i.e., two bodies are actually touching each other – heat transfer mode between the
bodies is conduction), with HGLUE=1:
a. The temperature of the contacting grid is tied to the temperatures of the contacted element face
or the temperature of the rigid geometry when it has a scalar point associated with it.
b. The temperature of the contacting grid is set to the rigid geometry temperature when it has no
scalar point associated with it.
Note: “Glued” thermal contact can result in overshoot of the temperatures i.e. Gibbs Phenomenon
or the temperature oscillations at the interface, in particular, if two bodies that have non-
uniform initial temperatures are placed in contact. The overshoot effect may be damped
somewhat if one uses a near contact distance with some convective heat transfer.
4. For hard contact, with HGLUE=0:
The convective heat flow per unit area over the two interfaces is given by:
q = HCT T A – T B
where TA is the contacting grid temperature and TB is the face temperature in the contact point in
case of a meshed body or the TBODY temperature in case of a rigid geometry.
Main Index
1208 BCONPRP
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400
5. The heat transfer coefficients and associated exponents can all be temperature dependent, when they
are entered as an integer value. This integer value is the table ID of a TABLEM1, TABLEM2 or
TABL3D entry (formulas are not supported on TABL3D). Table IDs of tables used on the
BCBDPRP entry and the BCONPRP entry must be unique.
6. Parameters BGM, BGN, BGSN, BGST and DQNEAR are not supported in segment to segment
contact analysis.
Main Index
BCONPRP-700 1209
Physical Contact Parameters of Touching Bodies in SOL 700
BCONPRP-700 Physical Contact Parameters of Touching Bodies in SOL 700
Defines physical contact parameters of touching bodies used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCONPRP PID PARAM1 VAL1 PARAM2 VAL2 PARAM VAL3
3
PARAM4 VAL4 PARAM5 VAL5 -etc.-
Example:
BCONPRP 90 FRIC 0.3
Describer Meaning
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 9-7 (Character).
VALi Value of a parameter. See Table 9-7 (Real or Integer).
Table 9-7 Physical Contact Parameters of Touching Bodies in SOL 700
Name Description, Type and Value (Default is 0 for integer, 0.0 for Real Unless Otherwise
Indicated)
FRIC Static friction coefficient. When it is set to -1.0, different static friction coefficients on
properties can be assigned using BCPROP1. (Real ≥ -1.0; Default=0.0 for SOL700)
FK Kinetic coefficient of friction. (Real > 0.0; Default = 0.0)
EXP Exponential decay coefficient. (Real > 0.0; Default = 0.0)
FACT Scale factor for the contact forces. (Real > 0.0; Default = 0.1)
Main Index
1210 BCONPRP-700
Physical Contact Parameters of Touching Bodies in SOL 700
TSTART Time at which the contact is activated. (Real > 0.0; Default = 0.0)
TEND Time at which the contact is deactivated. (Real > 0.0; Default = 1.e20)
IADJ Adjacent material treatment option for solid elements. (Integer ≥ 0; Default =1)
0 Solid element faces are included only for free boundaries.
1 Solid element faces are included if they are on the boundary of the material
subset. This option also allows the erosion within a body and the subsequent
treatment of contact.
DAMPING Specifies if a high frequency damping is active or not. The damping force is based on the
relative velocity of a secondary node with respect to a primary face. The damping is
preferably turned on in all cases, except for RIGID-RIGID contact. In RIGID-RIGID
contact it can result in a substantial loss of energy. VERSION V4 only. (Character;
Default=YES).
YES damping is activated
NO damping is not activated.
Main Index
BCONUDS 1211
Contact Body User Defined Service
BCONUDS Contact Body User Defined Service
Allows the user to provide contact routines for use with enhanced SOL 400 contact analysis.
Format:
1 2 3 4 5 6 7 8 9 10
BCONUDS BID BTYPE GROUP UNAME
“INT” IDATA1 IDATA2 IDATA3 IDATA4 IDATA5 IDATA6 IDATA7
IDATA8 IDATA9 ... ... IDATAn
“REAL” RDATA1 RDATA2 RDATA3 RDATA4 RDATA5 RDATA6 RDATA7
RDATA8 RDATA9 ... ... RDATAn
“CHAR” CDATA1 CDATA2 ... ... CDATAn
Example:
In FMS Section of MSC Nastran input stream:
CONNECT SERVICE CONTACT ‘SCA.MDSolver.Util.Ums’
In Bulk Data:
BCONUDS 17 BCBODY CONTACT UFRIC
BCONUDS 17 BCBODY CONTACT SEPFOR
REAL .00134 1.467+4 .03
BCONUDS 17 BCBODY CONTACT MOTION
REAL .00134 1.467+4 .03
INT 8 3
Describer Meaning
BID Contact body identification number defined by BCBODY or BCBODY1. (Integer
> 0; Required)
BTYPE The name of the contact entry. BCBODY/BCBODY1 (Character; no Default)
GROUP The group name used for the FMS Section CONNECT SERVICE statement.
(Character; no Default)
UNAME User subroutine name associated with the entry. See Remark 6. and 7. (Character)
“INT” Keyword indicating that the following data is integer. (Character)
IDATAi Additional user supplied Integer data not already existing on the specified contact
property entry. (Integer, no Default)
“REAL” Keyword indicating that the following data is real. (Character)
Main Index
1212 BCONUDS
Contact Body User Defined Service
Describer Meaning
RDATAi Additional user supplied Real data not already existing on the specified contact
property entry. (Real; no Defaults)
“CHAR” Keyword indicating that the following data is Character. (Character)
CDATAi Additional user supplied Character data not already existing on the specified contact
property entry. (Character; no Default)
Remarks:
1. This entry triggers the call to a user contact subroutine for advanced nonlinear materials. The
GROUP must match the GROUP field of the CONNECT SERVICE FMS statement.
2. On the FMS CONNECT statement, only the CONNECT SERVICE can be used with this entry.
3. The BID must match an existing BID.
4. A CDATAi entry cannot be the Character “REAL”, “INT”, or “CHAR”.
5. Certain user subroutines may require integer or real data input as specified in the User Defined
Services manual.
6. UNAME must be truncated to 8 characters in the bulk data field
7. The following user subroutines are currently available for user convenience. See the User Defined
Services manual for details.
Type Uname Purpose
BCBODY motion Define velocity of rigid surfaces
BCBODY ufric Define friction coefficients
BCBODY sepfor Define separation forces
BCBODY sepstr Define separations stresses
BCBODY ubsqueal Define friction coefficient and effective stiffness in brake squeal
analysis
Main Index
BCPARA 1213
Contact Parameters -SOLs 101 and 400
BCPARA Contact Parameters -SOLs 101 and 400
Defines contact parameters used in SOL 101 and SOL 400. This entry is not available in SOL 700.
For its usage in NLPERF SOL 400, refer to BCPARA in the Ap. C: NLPERF SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
BCPARA ID Param1 Value1 Param2 Value2 Param3 Value3
Param4 Value4 Param5 Value5 etc.
Example:
BCPARA ERROR 0.1 BIAS 0.5
Describer Meaning
ID Subcase to which the defined parameters belong. If ID is zero, the parameters belong
to all subcases. (Integer > 0; no Default)
Param(i) Name of a parameter. Allowable names are given in Table 9-7. (Character)
Value(i) Value of the parameter. See Table 9-7. (Real or Integer)
Main Index
1214 BCPARA
Contact Parameters -SOLs 101 and 400
Table 9-8 Contact Parameters -SOLs 101 and 400
Description, Type and Value (Default is 0 for Integer, 0.0 for Real Unless Otherwise
Name Indicated)
ERROR Distance below which a node is considered touching a body. (Real; Default = blank).
Automatically calculated if left blank. If left blank, the code calculates ERROR as the
smallest value resulting from: Either dividing the smallest nonzero element dimension
(plates or solids) in the contact body by 20. Or dividing the thinnest shell thickness in
the contact body by 4. This value is then used for all contact pairs.
BIAS Contact tolerance bias factor. (0.0 Real 1.0.);
Default = 0.9 for IGLUE=0, if field left blank.
Default = 0.0 for IGLUE <>0. Note that when IGLUE<>0, BIAS can only be given by
the BCTABLE or BCONPRG.
Default = 0.0 for BEHAVE=SYMM on BCBODY, if field left blank or 0.0.
FGCFLG Flag to activate Cohesive (Flexible) Glued Contact: (See Remark 12.)
0 No Cohesive (Flexible) Glued Contact
1 Activate Cohesive (Flexible) Glued Contact
FGCNST Equivalent normal contact stiffness of connector for Cohesive (Flexible) Glued Contact
FGCTST Equivalent tangential contact stiffness of connector for Cohesive (Flexible) Glued
Contact
FGCNSTR ID of table for define contact normal stress versus relative displacement for Cohesive
(Flexible) Glued Contact. Only TABL3D allowable.
FGCTSTR ID of table for define contact tangential stress versus relative displacement for Cohesive
(Flexible) Glued Contact. Only TABL3D allowable.
FGCNSTI ID of table for define contact normal stiffness versus relative displacement or
temperature for Cohesive (Flexible) Glued Contact. Only TABL3D allowable.
FGCTSTI ID of table for define contact tangential stiffness versus relative displacement or
temperature for Cohesive (Flexible) Glued Contact. Only TABL3D allowable.
FGCRCEN Reference Grid at which resultant contact force of secondary body to primary body is
evaluated. See Remark 12.
FGCRCN1 Reference Grid at which resultant contact force of primary body to secondary body is
evaluated.
Default of FGCRCN1 is FGCRCEN
FNTOL Separation force (or stress if separation is controlled by stress as determined by IBSEP)
above which a node separates from a body. Automatically calculated if left blank. (Real;
Default = blank). See Remark 10.
MAXSEP Maximum number of separations allowed in each increment. After MAXSEP
separations have occurred, if the standard convergence tolerance conditions are
achieved, the step will converge. (Integer > 0; Default = 9999)
Main Index
BCPARA 1215
Contact Parameters -SOLs 101 and 400
Description, Type and Value (Default is 0 for Integer, 0.0 for Real Unless Otherwise
Name Indicated)
ICSEP Flag to control separation. Not used for segment-to-segment contact. (Integer > 0;
Default = 0)
0 The node separates and an iteration occurs if the force on the node is
greater than the separation force.
1 If a node which was in contact at the end of the previous increment has
a force greater than the separation force, the node does NOT separate
in this increment, but separates at the beginning of the next increment.
2 If a new node comes into contact during this increment, it is not
allowed to separate during this increment, prevents chattering.
3 Both 1 and 2 are in effect.
IBSEP Flag for separation based on stresses or forces. (Integer > 0; Default = 0)
0 Separation based on forces.
1 Separation based on absolute stresses (force/area)
2 Separation based on absolute stress (extrapolating integration point
stresses)
3 Relative nodal stress (force/area)
4 Separation based on relative stress (extrapolating integration point
stresses)
Segment to segment contact ignores IBSEP and will use 2 internally. See Remarks 6.
and 8.
RVCNST For the bilinear friction model, RVCNST is the slip threshold. (Real ≥ 0.0; Default =
0.0).
Default=0.0 means that the actual value is automatically calculated.
FTYPE Friction type. See Remark 5. (Integer)
0 No friction. (Default)
6 Bilinear Coulomb friction.
7 Bilinear Shear friction.
BEAMB Beam-Beam contact flag. See Remark 7. (Integer 0 or 1)
0 No beam-beam contact. (Default for SOLs 101/400)
1 Activate beam-beam contact options. (Default for SOL 700)
Main Index
1216 BCPARA
Contact Parameters -SOLs 101 and 400
Description, Type and Value (Default is 0 for Integer, 0.0 for Real Unless Otherwise
Name Indicated)
NLGLUE If all secondary's for the BCTABLE or BCONPRG corresponding to the first loadcase
(SOLs 101 and (first subcase and first step) contain IGLUE >0, permanent glued contact with small
400 only) rotation condition will be used for all SECNDRY entries in all subcases and all steps
unless BCPARA,0,NLGLUE,1 is specified. If IGLUE < 0 exists in the first subcase and
first step, STEP Glued Contact is activated, it behaves as conventional Permanent
Glued Contact but for large deformation and rotation within the corresponding load
case. In this case of any IGLUE < 0 in the first load case, NLGLUE is ignored no matter
it is 0 or 1. (Integer; Default = 0)
NODSEP Skip separation check in contact for any grid already touched and separated.
NODSEP times within the current increment. (Integer; Default = 5)
>0 Keep grid contact status
<0 Separate grid from contact
METHOD Flag to select Contact methods. (Character)
NODESURF Node to segment contact. (Default)
SEGTOSEG Segment to segment contact (distributed penalty)
S2SNP Segment to segment contact (nodal penalty). See Remark 18.
AUGMENT Augmentation method used in a segment-to-segment contact analysis. (Integer)
0 No augmentation (Default)
1 Augmentation based on a constant Lagrange multiplier field for linear
elements and on a (bi)linear Lagrange multiplier field for quadratic
elements
2 Augmentation based on a constant Lagrange multiplier field
3 Augmentation based on a (bi)linear Lagrange multiplier field
PENALT Augmented Lagrange penalty factor; used by the segment-to-segment contact
algorithm only. (Real > 0.0; see BCTABLE or BCONPRG entries for default)
AUGDIST Penetration distance beyond which an augmentation will be applied; used by the
segment-to-segment contact algorithm only. (Real > 0; see BCTABLE entry for default)
SLDLMT Maximum allowed sliding distance, beyond it the contact segments are redefined, for
segment to segment contact analysis with large deformation. (Real 0.0; Default = 0.0)
See remark 9.
SEGSYM Specify symmetric or non-symmetric friction matrix in segment to segment contact
analysis. (Integer 0 = symmetric matrix or 1 = non-symmetric matrix; Default = 0)
ERRBAS Error computation option. (Integer 0 = compute error globally or 1 = calculate error
based on each pair of secondary-primary; Default = 0)
DDULMT Maximum value of DDU in a Newton-Raphson cycle. (Real 0.0; Default = 0.0, no
limitation)
Main Index
BCPARA 1217
Contact Parameters -SOLs 101 and 400
Description, Type and Value (Default is 0 for Integer, 0.0 for Real Unless Otherwise
Name Indicated)
TAUGMNT Augmentation for the sticking part of friction in a segment-to-segment contact analysis.
(Integer 0 = no augmentation or 1 = use augmentation; Default = 0)
TPENALT Augmented Lagrange penalty factor for sticking part of friction, used by the segment-
to-segment contact algorithm only. (Real > 0.0) The default is PENALT/1000, where
PENALT parameter is the Augmented Lagrange penalty factor for normal contact.
STKSLP Maximum allowable slip distance for sticking, beyond it there is no sticking, only
sliding exists, used by the segment-to-segment contact algorithm only. (Real 0.0;
Default = 0.0) See Remark 11.
THKOFF Ignore thickness from the tolerance used by ISEARCH=2 in node-to-surface contact or
from the characteristic length (for PENALT and AUGDIST) in segment-to-segment
contact. (Integer 0 = do not ignore thickness or 1 = remove thickness; Default = 0)
LINCNT Flag for Linear Contact (under infinitesimal assumption, small sliding with small
deformation and rotation). Supports both node-to-segment and segment-to-segment
method. See Remark 14..
0 - (Default) general contact
1 - activate Linear Contact, the contact force is distributed based upon undeformed
geometry.
-1 - force Linear Contact with large displacement (not recommended).
SFNPNLT Scale factor of augmented Lagrange penalty factor along contact normal direction; used
by segment-to-segment contact method only. (Real>0.0;Default=1.0)
SFNPNLT*PENALT is used in analysis.
A nonblank value of SFNPNLT entered in BCONPRG will override it.
SFTPNLT Scale factor of augmented Lagrange penalty factor along contact tangential direction;
used by segment-to-segment contact method only. (Real>0.0;Default=1.0)
SFTPNLT*TPENALT is used in analysis.
A nonblank value of SFTPNLT entered in BCONPRG will override it.
SEGANGL Minimum angle between segment normal vectors allowing the segments to come into
contact; used by segment-to-segment contact only. (Real>90.0 <180.0;
Default=120.0).
TCNTCTL Flag to define the touching contact status in linear perturbation and ignoring the
touching Contact status determined by the contact analysis in NLSTATIC analysis at
the load point assigned by NLIC. (Integer; Default = 0)
Value of TCNTCTL defined in BCONPRG will override one defined in BCPARA.
0 - Skip this option, keep the original contact status obtained in NLSTATIC.
1 - Assuming sliding status of touching contact for contact and frictional stiffness
matrix calculation.
2 - Assuming sticking status of touching contact for contact and frictional stiffness
matrix calculation.
3 - Assuming glued contact status for touching contact for contact stiffness matrix
calculation.
Main Index
1218 BCPARA
Contact Parameters -SOLs 101 and 400
Description, Type and Value (Default is 0 for Integer, 0.0 for Real Unless Otherwise
Name Indicated)
VERSION Defaults version control in Segment-to-Segment method, see remark 15.
1 (default in Version 1
S2SNP)
2 (default in Version 2 (lower default penalty, recommended)
SEGTOSEG)
BACKCTL Backward compatible bit-wise control in contact analysis, see remark 16.
1st to 7th bit segment-to-segment only
-1 Activate all of following items (back to 2020 SP1)
0 None of following items will be activated
1 Body order independent
2 Evaluation of contact matrix/force on segment coordinates (old logic)
4 Segment sequence renumbering (old method)
8 No reset iteration count after separation (old logic)
16 Creating new polygon under sliding condition (old logic)
32 Scaled incremental displacement update in small rotation (old
method)
64 Ramping down penalty when angle of segment normals between 180
degree and SEGANGL
128 Old algorithm of nodal projection in contact
2021.3 release onwards, the default uses the enhanced contact
projection algorithm, which helps in consistent contact detection at
corners and for warped surface.
GLUEOUT Contact force and stress output preference in glued contact.
0 Normal and tangential components are separated (segment-to-
segment only)
1 (default) Normal and tangential components are combined
SEPACC Flag to control the accelerated separation check in node-to-segment contact for SOL
400. See remark 17. (Integer ≥ 0; Default = 0).
0 Accelerated separation check turned off
1 Accelerated separation check turned on
Main Index
BCPARA 1219
Contact Parameters -SOLs 101 and 400
Description, Type and Value (Default is 0 for Integer, 0.0 for Real Unless Otherwise
Name Indicated)
DYNPRFA Dynamic contact projection factor (0.0 ≤ Real ≤ 1.0; Default= 0.0)
A value of 0.0 may show some penetration.
Values greater than 0 reduce penetration and can introduce transient vibration. It is
strongly recommended to use the default values in NLTRAN to avoid the chattering in
contact analysis.
OSPLNFRQ Output frequency of smooth spline representation of deformable contact body when
BOUTPUT output requested. (Integer ≥ -1; Default=-1).
-1 Initial output only
0 No output
n Every nth output increment along with initial output.
Note that OSPLNFRQ is based on the number of output load
increments, but not calculated load increments. It is determined by
“NO” in fixed time stepping or “NOUT” in adaptive time stepping on
NLSTEP.
Remarks:
1. The ID of BCPARA should be left blank or a value of zero. Blank is treated as zero.
2. Only one BCPARA entry should be made. Multiple BCPARA entries with ID=0 cause a Fatal Error.
3. All SOLs only support ID=0, this entry is applied to all the subcases, except the corresponding ones
are assigned in BCTABLE or BCONPRG.
4. Refer to the Case Control command BCONTACT (Case), to see the lists of parameters in BCPARA that
are not supported by SOLs 101 and 400.
5. In SOLs 101/400, FTYPE only supports options 0, 6, and 7. Friction with segment-to-segment
contact is a pre-release capability in the 2012 release. In the 2012.2 version and later, it is fully
supported.
6. Shell elements (CQUAD4 CQUAD8 CTRIA3 CTRIA6) in 3D Contact only supports IBSEP = 0,
1 and 3. If IBSEP = 2 or 4 in this case, it will automatically be set to 1 or 3, respectively. In SOLs
101/400, LINQUAD is not supported and it is set to -1 in order that the mid-side nodes are
considered in Contact. Quadratic shell elements consider mid-side nodes only in 2D Contact.
a. If IBSEP is set to 1, then for bodies consisting of mid-side node elements, IBSEP will
automatically be set to 2. This allows for using IBSEP=1 for elements without mid-side nodes and
IBSEP=2 for elements with mid-side nodes in one analysis.
b. If IBSEP is set to 3, then for bodies consisting of mid-side nodes elements, IBSEP will
automatically be set to 4. This allows for using IBSEP=3 for elements without mid-side nodes and
IBSEP=4 for elements with mid-side nodes in one analysis.
Main Index
1220 BCPARA
Contact Parameters -SOLs 101 and 400
This rule is always applied to the solid elements with mid-side nodes. However, the mid-side nodes
of CQUAD8 and CTRIA6 shell elements are ignored in node-to-segment 3D contact with separation
because there is no normal stress in shell elements, and the contact normal forces for these elements
do not give a good estimation of the nodal contact stress. Hence it is not recommended to use
CQUAD8 and CTRIA6 shell elements in a node-to-segment contact analysis with separation.
7. For SOLs 101/400 if BEAMB=1, Bulk Data entry BCBMRAD must be entered. Those entries are
not required in the beam contact of segment-to-segment contact.
8. Parameters MAXSEP, ICSEP, IBSEP, RVCNST and BEAMB are not supported in segment to
segment contact analysis.
9. The default of SLDLMT parameter is 5 times the default error tolerance. See the description of
ERROR parameter for the definition of default error tolerance.
10. IBSEP and FNTOL are related to each other. The Default value of FNTOL is dependent on IBSEP
value.
a. IBSEP=0 : Separation is based on forces. A contact node will separate if the contact pulling force
exceeds FNTOL. If FNTOL is zero it will be taken as the absolute value of the largest component
in the residual force vector.
b. IBSEP=1 : Separation is based on nominal contact stresses (force/area). A contact node will
separate if the nominal contact pulling stress exceeds FNTOL. If FNTOL is zero, it will be 0.1
times of the maximum nominal contact pushing stress of any node of any contact body.
c. IBSEP=2 : Separation is based on nodal stress (extrapolating integration point stresses). A contact
node will separate if the nodal pulling stress exceeds FNTOL. If FNTOL is zero it will be 0.1
times of the maximum nodal pushing stress of any node of any contact body
d. IBSEP=3 : Separation is based on relative nominal contact stress (force/area). A contact node will
separate if the nominal contact pulling stress exceeds FNTOL times of maximum nominal contact
pushing stress of any node of any contact body. If FNTOL is zero, it will be taken as 0.1
e. IBSEP=4 : Separation is based on relative nodal stress (extrapolating integration point stresses). A
contact node will separate if the nodal pulling stress exceeds FNTOL times of maximum nodal
pushing stress of any node of any contact body. If FNTOL is zero, it will be taken as 0.1
11. If STKSLP is set to 0.0 (Default), the sticking stiffness K1 is equal to the maximum friction force
( FNORMAL, where µ is the friction coefficient) divided by the maximum sticking displacement.
Otherwise, K1 is equal to the maximum friction force divided by the value of STKSLP.
12. The parameters of cohesive contact defined in BCPARA will be applied to all the contact pairs unless:
• The contact pair has its own definition for cohesive contact in BCONPRG; or
• Its IGLUE=0, i.e., general touching contact.
• FGCRCEN/FGCRCN1 applies to all contact pairs, not limited to cohesive contact
(FGCFLG=1) pairs.
Cohesive contact is only applied to glued contact, but not touching contact.
13. If Modules are present then this entry may only be specified in the main Bulk Data section.
14. LINCNT does not support RIGID contact body with velocity control.
Main Index
BCPARA 1221
Contact Parameters -SOLs 101 and 400
When LINCNT=1, initial search range is doubled (2*ERROR); nodes not being detected initially
will not come into contact during analysis
15. Version 1 is equivalent to system cell 701=0; Version 2 is equivalent to system cell 701=1
Version 2 is improved default values for contact problems involving geometrically and physically
nonlinear behavior:
a. Augmented Lagrange penalty factor. For bodies with the same body stiffness, this factor is chosen
to be lower than the default value. For a body combination with different values of the body
stiffness, the smallest of the two is used.
b. Penetration distance beyond which an augmentation is applied. This distance is chosen to be
larger than the default value, thus avoiding too many iterations due to augmentation. It is
recommended to use an augmentation procedure for contact.
c. Augmented Lagrange penalty factor for sticking contact. This factor is chosen to be dependent on
the normal pressure.
16. Following features are defaults of segment-to-segment method since 2021.0
• Body order dependent
• Evaluate contact matrix/force based upon true updated segment coordinates
• New segment sequence renumbering
• Reset iteration count after separation (Version 2 only)
• New logic in creating new polygons under sliding condition
• Scaled incremental displacement update in large rotation
• Ramping down penalty when angle of segment normals below SEGANGL (minimum segment
angle, default 120 degree)
17. SEPACC=0: Nodes are checked for separation only after satisfying all specified convergence criteria.
SEPACC=1: Nodes are checked for separation as soon as the maximum residual force in the model
drops to less than 10% of the maximum reaction force in the model.
a. SEPACC is only applicable to node-to-segment method, not supported in segment-to-segment
method.
b. Accelerated separation check could reduce iteration when EPSP less than 0.1
c. Accelerated separation check may increase total separation count, hence default MAXSEP is
preferred when SEPACC=1.
d. Accelerated separation check algorithm is only available in NLSTEP scheme, not supported in
NLPARM.
18. S2SNP only supports permanent glue. S2SNP does not support 1D elements defined in contact.
Main Index
1222 BCPATCH
Defines a Rigid Contact Body Made up of Quadrilateral Patches in SOLs 101 and 400
BCPATCH Defines a Rigid Contact Body Made up of Quadrilateral Patches in SOLs 101 and 400
Defines a rigid contact body made up of quadrilateral patches used in SOLs 101 and 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCPATCH RBID
IDP G1 G2 G3 G4
IDP G1 G2 G3 G4
-etc.-
Example:
BCPATCH 12
1 101 102 103 104
Describer Meaning
RBID Unique identification number referenced by a BCRGSRF or BCBODY1 entry (Integer
> 0). See Remark 1.
IDP ID of the patch (Integer number 1 through highest value).
G1, G2, G3, Grid numbers for each of the 4 nodes of the patch.
G4
Remarks:
1. If BCRGSRF entry does not exist, BCPATCH entry will be referenced by the BCBODY1 entry
directly.
Main Index
BCPFLG 1223
Defines a beam section segment flag
BCPFLG Defines a beam section segment flag
Defines a beam section branch and segment for segment to segment beam contact used in SOL 101 and 400
for general contact or in SOLs 101, 103, 105, 107 - 112, 200 and 400 for the permanently glued Contact.
Format:
1 2 3 4 5 6 7 8 9 10
BCPFLG PID IBRNCH1 IOUTIN IBRNCH2 IOUTIN2 IBRNCHi IOUTINi
1
Example:
BCPFLG 2 1 2 3 13
Describer Meaning
PID Beam property/section identification number of PBEAML/PBARL. (Integer > 0;
Required)
IBRNCHi Branch selection flag for segment generation. Only required for thin wall sections. See
Remark 1, 2, 3 and 4. (Integer; default=0).
0 select all branches for thin wall sections
IOUTINi Beam segment location. See Remark 4, 5, 6 and 7. (Integer; default=0; up to three
unique integers may be placed in the field with no embedded blanks.)
0 - all segments
1 - location 1 of thin wall section or only outer of solid or tube sections
2 - location 2 of thin wall section or only inner of tube section
3 - location 3 of thin wall section (thickness direction of branch)
4 - segment not including thickness
Remarks:
1. If the card is not defined but the beam property is included in segment to segment contact, all
segments will be generated and used. This card is only useful when a user needs to define the specific
beam segments for segment to segment contact. It will help the performance of calculation because
only selected segments will be considered in the contact calculation.
2. IBRNCHi fields are only required for thin wall beam sections. Solid beam sections such as
rectangular, rod, etc or tube sections require only IOUTIN1.
3. Each branch of thin wall beam section has four segments.
4. Segment locations of thin wall beam sections are listed below. TYPE is defined by PBEAML/PBARL.
The number circled is the branch number of each shape and the number without circle is the segment
number which is used in IOUTINi. Segment 1 and 2 of each branch are the segments in the branch
direction and segment 3's are the segment in the thickness direction of the branch.
Main Index
1224 BCPFLG
Defines a beam section segment flag
Main Index
BCPFLG 1225
Defines a beam section segment flag
5. If there is not thickness, one segment will be generated in the branch.
6. "3" cannot be used alone and "4" must be used only with "1" or "2". IOUTINi must be one of "0",
"1", "2", "12", "13", "14", "23", "24" and "123".
7. "14" and "24" generate the identical segment since the thickness is ignored but segment normal
direction will be different.
Main Index
1226 BCPROP
3D Contact Region by Element Properties
BCPROP 3D Contact Region by Element Properties
Defines a 3D contact region by element properties. All elements with the specified properties define a contact
body.
Format:
1 2 3 4 5 6 7 8 9 10
BCPROP ID IP1 IP2 IP3 IP4 IP5 IP6 IP7
IP8 IP9 etc.
Example:
BCPROP 1 101 201 301
Alternate Format:
BCPROP ID IP1 THRU IP2 IP3 IP4 IP5 IP6
IP7 IP8 IP9 etc.
Alternate Example:
BCPROP 1 101 THRU 102 105 THRU 109 110
Describer Meaning
ID Identification number of a deformable surface corresponding to a BSID value on the
BCBODY entry. All elements corresponding to the property IDs specified that may
potentially come into contact. Do not specify mixed property types (use all shell, all solid
or all beam properties only). See Remark 1. (Integer > 0)
IPi Property ID. A minimum of one entry is required. (Integer; no Default)
Remarks:
1. ID must be unique with respect to all other BSURF, BCBOX, BCPROP, and BCMATL entries.
2. The deformable surface may alternately be defined using BSURF, BCBOX, or BCMATL entries.
3. Only one kind of entry (BSURF, BCBOX, BCPROP, or BCMATL) may be used to define a
particular deformable surface.
4. All elements corresponding to the IDs entered will be used to define the deformable surface.
5. As many continuation lines as necessary may be used to define all property IDs associated with a
particular deformable body.
6. The alternate format is triggered if field 4 contains THRU. The THRU keyword may appear in fields
4 thru 8.
7. BCBOX and BCMATL are not available for SOL 101 or SOL 400
Main Index
BCRIGID 1227
Defines a Rigid Contact Body in SOLs 101 and 400
BCRIGID Defines a Rigid Contact Body in SOLs 101 and 400
Defines a rigid contact body used in SOLs 101 and 400 only.
Format: (SOLs 101 and 400 only)
1 2 3 4 5 6 7 8 9 10
BCRIGID BCRGID CGID CONTROL
NLOAD ANGVEL DCOS1 DCOS2 DCOS3 VELRB1 VELRB2 VELRB3
“APPROV” A N1 N2 N3 V1 V2 V3
“GROW” GF1 GF2 GF3 TAB-GF1 TAB-GF2 TAB-GF3
Example:
BCRIGID 1001 1 1
0 0. 0. 0. 1. 1. 1. 1.
Describer Meaning
BCRGID Unique identification number referenced by a BCBODY1 entry. (Integer > 0)
CGID Grid point identification number defining the initial position of the reference point of the
rigid body or the point where a concentrated force or moment is applied. (Integer > 0) See
Remark 1.
CONTROL Indicates the type of control for the body.
Integer:
= -1 for position control. The coordinates of the final position of GRID Point defined in
CGID is given in VELRBi in the following line.
= 0 for velocity control. (default)
= positive number for “load control”. The positive number is the grid number defined in
CGID at which translational forces or SPCD are applied. (Note: The rotation in this case is
defined by NLOAD in the following line.)
NLOAD Enter a positive number if “load controlled” and rotations are allowed. (Integer) The positive
number is the grid number where the moments or rotations are applied. The rotations are
specified using SPCD at grid ID NLOAD and can be specified using dof’s 1-3 (for
translation along x, y, z respectively), or by dof’s 4-6 (for rotation about x, y, z respectively).
Note: This rotation takes the position of the grid point defined in CGID field as the center
of rotation.
ANGVEL Angular velocity or angular position about local axis through center of rotation. If the value
is an integer it represents the ID of a TABLED1, TABLED2 or TABL3D, i.e., a time-
dependent or multi-dimensional table; however, no log scales, only linear scales. (Real or
Integer; Default = 0.0)
Main Index
1228 BCRIGID
Defines a Rigid Contact Body in SOLs 101 and 400
DCOSi Components of direction cosine of local axis if ANGVEL is nonzero. If the value is an
integer, it represents the ID of a TABLED1, TABLED2 or TABL3D, i.e., a time-dependent
or multi-dimensional table; however, no log scales, only linear scales. (Real or Integer;
Default=0.0) In 2D contact only DCOS3 is used and the Default is 1.0.
VELRBi Tranlational velocity or final position (depending on the value of CONTROL) of rigid body
at the grid point defined in CGID filed. For velocity control only, if the value is an integer,
it represents the ID of TABLED1, TABLED2 or TABL3D, i.e., a time-dependent or multi-
dimensional table; however, no log scales, only linear scales. Only VELRB1 and VELRB2
are used in 2D contact. (Real or Integer; Default = 0.0)
“APPROV” The entries of this continuation line are for approaching velocity to establish initial contact.
A Angular velocity about local axis through center of rotation. (Real, Default = 0.0)
Ni Components of direction cosines of local axis of the angular velocity. The N1, N2, N3
define the axis through the point defined in the CGID field. Only N1 and N2 are used in
2D contact. (Real, Default = 0.0)
Vi V1, V2 and V3 define the three components of the approaching velocity. Only V1 and V2
are used in 2D contact. (Real; Default = 0.0)
“GROW” The entries of this continuation line are for rigid body growth. If tables are used for growth,
they should either be TABLED1, TABLED2 (growth vs time) or TABL3D (growth vs one
or more variables).
GFi Components of growth factor of rigid body in the coordinate system of the CGID field.
(Real, Default = 1.0)
TAB-GFi Table IDs for growth factor of rigid body in the coordinate system of the CGID field.
(Integer > 0 or blank, Default is blank)
Remarks:
1. The grid CGID is the reference grid for the rigid body motion. Loads and enforced motion must be
defined in the global coordinate system of CGID. If CGID is not specified, basic coordinate will be
used.
2. All continuation lines may be omitted if not required.
Main Index
BCRGSRF 1229
Rigid Contact Surface List in SOLs 101 and 400
BCRGSRF Rigid Contact Surface List in SOLs 101 and 400
Defines a list of rigid contact surfaces used in SOLs 101 and 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCRGSRF BSID RBID1 RBID2 RBID3 RBID4 RBID5 RBID6 RBID7
RBID8 -etc.-
Example:
BCRGSRF 1008 35 2
Describer Meaning
BSID Unique identification number referenced by a BCBODY1 entry. (Integer > 0) See Remark
1.
RBIDi Identification number of BCPATCH, BCBZIER, BCNURB2 or BCNURBS entry.
(Integer > 0)
Remarks:
1. If BCRGSRF entry does not exist, BCBODY1 entry can refer to one of the identification number of
BCPATCH, BCBZIER, BCNURB2 or BCNURBS entry directly.
Main Index
1230 BCSCAP
Defines a cap and number of segments
BCSCAP Defines a cap and number of segments
Defines whether a cap is added to a beam section and/or defines the number of segments used to model rod
and tube sections for segment to segment beam contact in SOL 101 and 400 for general contact or in SOLs
101, 103, 105, 107 - 112, 200 and 400 for the permanently glued contact
Format:
1 2 3 4 5 6 7 8 9 10
BCSCAP EID IESCAP NSEG
Example:
1 2 3 4 5 6 7 8 9 10
BCSCAP 2 1 20
Describer Meaning
EID Beam element identification number. (Integer > 0; Required)
IESCAP End and side cap flag (Integer 0; default=0).
0 no end or side cap
1 end cap only
2 side cap only
3 averaged side cap only
4 end cap and side cap
5 end cap and averaged side cap
NSEG Number of segments for circular sections TYPE=ROD, TUBE or TUBE2 beam
sections defined on PBARL or PBEAML. See remarks 2. (Integer 3; default=32)
Remarks:
1. If the card is not defined but the beam is included in segment to segment contact, all caps will be
ignored. This card is only useful when a user needs to define the cap of beams for segment to segment
contact.
Main Index
BCSCAP 1231
Defines a cap and number of segments
2. The segments for circular cross sections will be generated as the figure below.
Main Index
1232 BCSEG
Contact Segment Defined Using Grids
BCSEG Contact Segment Defined Using Grids
Grids which are part of an element to be used in contact analyses in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
BCSEG ID IBODY G1 G2 G3 G4
Example:
1 2 3 4 5 6 7 8 9 10
BCSEG 100 1005 11 12 13 14
Describer Meaning
ID Unique identification number for this BCSEG entry. (Integer > 0; Required)
IBODY Identification number of a surface that is called out on the 5th field of a BCBODY
entry. (Integer > 0; Required)
G1,G2,G3,G4 GRID point identification numbers of an element on this surface. For quad plates
and quad surfaces of solids, enter four grid id’s. For triangular plates or triangular
faces of solids, leave G4 blank. (Integer > 0; Required)
Remarks:
1. This entry is used as shown in the example below:
BCBODY, 201,,,1005
BCSEG,1,1005,11,12,13,14
BCSEG,2,1005,21,22,23,24
BCSEG,3,1005,31,32,33,34
(In the above 11-14, 21-24 and 31-34 are GRID ID’s)
Main Index
BCSURF 1233
Contact entry by element faces
BCSURF Contact entry by element faces
Define a contact region by element faces for SOLs 101, 103, 105, 107, 108, 109, 110, 111, 112, 200 and
400. This has three forms based the FORM (the 6th) field. “FACE” (default) is to define contact face by
element face IDs, “GRID” is to define the same by grid point ids, and “RIGID” is to define a rigid face.
Format 1: FORM="FACE" (default)
1 2 3 4 5 6 7 8 9 10
BCSURF BID BPID DIM FORM INCTHK EDGCNT
ESID1 FACEID1 IDTYPE1 ESID2 FACEID2 IDTYPE2
ESID3 FACEID3 IDTYPE3 ...
...
Format 2: FORM="GRID"
1 2 3 4 5 6 7 8 9 10
BCSURF BID BPID DIM “GRID” INCTHK EDGCNT
EID1 G11 G12 G13 EID2 G21 G22 G23
EID3 G31 G32 G33 ...
...
Format 3: FORM="RIGID"
1 2 3 4 5 6 7 8 9 10
BCSURF BID BPID DIM “RIGID”
BSID BCRGID
Example:
FACE form (default)
BCSURF 2 3 3D NO
12 S2 4 S4 SET
GRID form
BCSURF 3 3 3D GRID YES
11 1 3 6 16 31 14 15
RIGID form
BCSURF 4 3D RIGID
101 201
Main Index
1234 BCSURF
Contact entry by element faces
Describer Meaning
BID Unique contact face identification number referenced by BCONECT (Integer > 0;
Required). See remark 1.
BPID Parameter identification number of a BCBDPRP entry. (Integer > 0 or blank).
DIM Dimension of body. (Character; Default= “3D”), “3D” or “2D”.
FORM Select a type of the entry. (Character; Default =”FACE”).
FACE define the contact surface by element face IDs
GRID define the contact surface by grid points on an element face
RIGID define the contact surface by rigid surface
INCTHK Option to include shell thickness offset. (Character; Default =”YES”), “YES” or
“NO”.
EDGCNT Option for edge contact. (Integer, default=1), below three values can be specified.
1: only the beam/bar edges are included in the contact description
(Default).
10: only the free and hard shell edges are included in the contact description.
11: both the beam/bar edges and the free and hard shell edges are included in
the contact description.
ESIDi Element id or set id. (Integer, no default). If IDTYPEi is “SET”, it is a set id defined
by a SET3, and the SET3 must be element type. If IDTYPEi is “ELEM” (default),
it is an element id.
FACEIDi Element face ID. (Character, blank can be used to express BOTH for shell elements
and the whole bodies of beam or bar elements). See remarks 6., 7., 8. and 9.
IDTYPEi Type of ESIDi. (Character, “ELEM”).
ELEM ESIDi is an element id.
SET ESIDi is a SET3 id.
EIDi Element id. (Integer > 0)
GIDij Three corner grid point ids of the element face. (Integer, no default). All the three
fields of for an EIDi are blanks or zeros mean BOTH for shell elements and the
whole bodies of bar or beam elements. See remark 2.
BSID Identification number of a BCRGSRF, BCPATCH,BCBZIER, BCNURB2, or
BCNURBS. (Integer > 0).
BCRGID Identification number of a BCRIGID entry. (Integer > 0).
Remarks:
1. BID must be unique among all BCSURF, BCBODY1 and BCGRID entries.
2. BCSURF entries are able to coexist with BCBODY1 entries. A BCSURF can be used with a
BCGRID, another BCSURF or a BCBODY1 entry to construct a contact pair.
Main Index
BCSURF 1235
Contact entry by element faces
3. BCSURF cannot be specified in the continuations of a BCONECT.
4. If a BCSURF is referenced by a BCONECT, COPTS and COPTM in the BCONPRG referenced
by the BCONECT will be used, and FACEIDs and INCTHK fields of BCSURF are ignored.
5. For GRID form, three corner grid point IDs are required to specify a 3D element face, two corner
grid point ids are required to specify a 2D element edge. For shell faces, the sequence of G1,G2,G3
of the element definition means TOP(top) and the reverse order means BTM(bottom), blanks or
zeros means BOTH(both).
6. FACEIDi varies depending on element type and DIM. Refer to remark 9 for the list of FACEIDs.
7. For shell elements, TOP, BTM and BOTH are to define the contact face on top, bottom and both
sides of the element. A blank is the same as BOTH. It is possible to have TOP and BTM in the same
BCSURF entry but not allowed to combine BTM with BOTH or TOP with BOTH.
8. For beam elements, ENDA and ENDB express beam or bar enda and endb points respectively. A
blank means the whole beam or bar body.
9. List of face ID.
Refer to following pages
CHEXA
Linear Element Quadratic Element
S1 4-3-2-1 4-3-2-1-11-10-9-12
S2 5-6-7-8 5-6-7-8-17-18-19-20
S3 1-2-6-5 1-2-6-5-9-14-17-13
S4 2-3-7-6 2-3-7-6-10-15-18-14
S5 3-4-8-7 3-4-8-7-11-16-19-15
S6 4-1-5-8 4-1-5-8-12-13-20-16
Main Index
1236 BCSURF
Contact entry by element faces
CPENTA
Linear Element Quadratic Element
S1 3-2-1 3-2-1-8-7-9
S2 4-5-6 4-5-6-13-14-15
S3 1-2-5-4 1-2-5-4-7-11-13-10
S4 2-3-6-5 2-3-6-5-8-12-14-11
S5 3-1-4-6 3-1-4-6-9-10-15-12
Main Index
BCSURF 1237
Contact entry by element faces
CPYRAM
Linear Element Quadratic Element
S1 4-3-2-1 4-3-2-1-8-7-6-9
S2 1-2-5 1-2-5-6-11-10
S3 2-3-5 2-3-5-7-12-11
S4 3-4-5 3-4-5-8-13-12
S5 4-1-5 4-1-5-9-10-13
CTETRA
Linear Element Quadratic Element
S1 3-2-1 3-2-1-6-5-7
S2 1-2-4 1-2-4-5-9-8
S3 2-3-4 2-3-4-6-10-9
S4 3-1-4 3-1-4-7-8-10
Main Index
1238 BCSURF
Contact entry by element faces
CQUAD4/CQUAD/CQUAD8/CQUADR when DIM is 3D
Linear Element Quadratic Element
E1 1- 2 1-2-5
E2 2-3 2-3-6
E3 3-4 3-4-7
E4 4-1 4-1-8
TOP 1-2-3-4 1-2-3-4-5-6-7-8
BTM 4-3-2-1 4-3-2-1-7-6-5-8
Main Index
BCSURF 1239
Contact entry by element faces
CTRIA3/ CTRIA6/CTRIAR when DIM is 3D
Linear Element Quadratic Element
E1 1- 2 1-2-4
E2 2-3 2-3-5
E3 3-1 3-1-6
TOP -2-3 1-2-3-4-5-6
BTM 3-2-1 3-2-1-5-4-6
Main Index
1240 BCSURF
Contact entry by element faces
CQUAD4, CQUAD8 and CQUADX when DIM is 2D
Linear Element Quadratic Element
S1/E1 1- 2 1-2-5
S2/E2 2-3 2-3-6
S3/E3 3-4 3-4-7
S4/E4 4-1 4-1-8
CTRIA3, CTRIA6, CTRIAX, CTRIAX6 when DIM is 2D
Linear Element Quadratic Element
S1/E1 1- 2 1-2-4
S2/E2 2-3 2-3-5
S3/E3 3-1 3-1-6
Main Index
BCSURF 1241
Contact entry by element faces
CAXISYM
Linear Element Quadratic Element
S1 1 1
S2 2 2
TOP 1-2 1-2-3
BTM 2-1 2-1-3
Main Index
1242 BCSURF
Contact entry by element faces
CBAR, CBEAM and CBEAM3
Linear Element Quadratic Element
ENDA 1 1
ENDB 2 2
(BLANK) 1-2 1-2-3
Main Index
BCTABLE 1243
Defines a Contact Table for General Contact
BCTABLE Defines a Contact Table for General Contact
Defines a contact table used in SOL 101, 400 and 700. SOL 200 (without calling SOL 400) SOL 144, 145
and 146 can only support permanent glue. When SOL 200 calls SOL 400 (or say SOL 400 optimization),
it can support all contact types. The BCTABL1 option is the preferred method to define a contact table.
Format: (SOLs 101 and 400 only)
1 2 3 4 5 6 7 8 9 10
BCTABLE ID IDSCND IDPRIM NGROUP COPTS COPTM
“SECNDRY” IDSEC1 ERROR FNTOL FRIC CINTERF IGLUE
ISEARCH ICOORD JGLUE DQNEAR
“FBSH” FRLIM BIAS SLIDE HARDS COPTS1 COPTM1
“BKGL” BGSN BGST BGM BGN
“SEGS” PENALT AUGDIST TPENALT STKSLP
“HHHB” HCT HCV HNC BNC EMISS HBL
HNL BNL HGLUE
“PRIMARY” IDPRIM1 IDPRIM2 IDPRIM3 IDPRIM4 IDPRIM5 IDPRIM6 IDPRIM7
IDPRIM8 IDPRIM9 ...
Format: (SOL 700 only)
1 2 3 4 5 6 7 8 9 10
BCTABLE ID IDSCND IDPRIM NGROUP
“SECNDRY” IDSEC1 FRIC IGLUE
JGLUE
FK EXP METHOD ADAPT THICK THICKOF PENV
FACT TSTART TEND MAXPAR
IADJ
IGNORE
AUTO
Main Index
1244 BCTABLE
Defines a Contact Table for General Contact
1 2 3 4 5 6 7 8 9 10
SIDE WEIGHT MONDIS MONDIS INITMON DAMPIN
V G
"PRIMARY" IDPRIM1 IDPRIM2 IDPRIM3 IDPRIM4 IDPRIM5 IDPRIM6 IDPRIM7
IDPRIM8 IDPRIM9 ...
Examples:
BCTABLE 2 3
SECNDRY 10 0.2
PRIMARY 20 30
SECNDRY 20 0.3
PRIMARY 10
SECNDRY 30 0.2
PRIMARY 10
BCTABLE 0 1 2 0
Describer Meaning
ID Identification number referenced by a BCONTACT Case Control command. See
Remark 5. (Integer; Required)
IDSCND Identification number of a BCBODY entry defining the touching body. (Integer >
0 or blank)
IDPRIM Identification number of a BCBODY Bulk Data entry defining the touched body.
(Integer > 0 or blank)
NGROUP Flag to indicate that the continuation entries “SECNDRY” and “PRIMARY” are
entered or not. Zero means no continuation entries are entered. Any positive
integer means one or more sets of secondary/primary entries are entered. (Integer;
Default = 1).
COPTS, COPTM, Flag to indicate how secondary and primary surfaces may contact. See Remark 9.
COPTS1, COPTM1 (Integer; Default = 0) COPTS and COPTM apply to all secondary and primary
surfaces on this BCTABLE. To set individual secondary/primary combination
differently, use COPTS1 and/or COPTM1. Ignored by SOL 700.
“SECNDRY” Indicates that this line defines the touching body and its parameters.
IDSEC1 Identification number of a BCBODY Bulk Data entry defining the touching body.
(Integer > 0)
For SOL 700, leaving IDSEC1 blank will result in contact for all elements in the
model. In this case, you are allowed to use ADAPT=YES.
Main Index
BCTABLE 1245
Defines a Contact Table for General Contact
Describer Meaning
ERROR Distance below which a node is considered touching a body. Default = blank
automatic calculation. See the Bulk Data entry BCPARA for more details. Ignored by
SOL 700. (Real)
FNTOL Separation force, stress, or fraction above which a node separates from a body.
FNTOL is closely related to IBSEP. It’s default value is dependent on the IBSEP
value. See remark 10. Ignored by SOL 700. (Real)
FRIC Friction coefficient. If the value is an integer, it represents the ID of a TABLEM1,
TABLEM2 or TABL3D, i.e., a temperature-dependent or multidimensional table.
SOL700 does not support the table definition. (Real > 0.0 or Integer > 0; Default
= 0.0 for SOL400, Real >0.0; Default=0.0 for SOL700)
CINTERF Interference closure amount, normal to the contact surface. Default = 0. For
CINTERF < 0, overlap between bodies. For CINTERF > 0., gap between bodies.
Ignored by SOL 700. (Real)
IGLUE Flag to activate glue option (Integer 0). Default is 0, no glue option. For SOL
700, IGLUE=1 is only acceptable. JGLUE option controls a glue contact type in
details. Without assigning IGLUE and JGLUE options, general contact methods
(METHOD=TIEDxxx) can assign glue contact types as well. (See Remarks 8.
through 16.)
±1 Activates the glue option. In the glue option, all degrees-of-
freedom of the contact nodes are tied in case of deformable-
deformable contact once the node comes in contact. The relative
tangential motion of a contact node is zero in case of deformable-
rigid contact. The node will be projected onto the contact body.
±2 Activates a special glue option to insure that there is no relative
tangential and normal displacement when a node comes into
contact. An existing initial gap or overlap between the node and the
contacted body will not be removed, as the node will not be
projected onto the contacted body. To maintain an initial gap,
ERROR should be set to a value slightly larger than the physical
gap.
±3 Insures full moment carrying glue when shells contact. The node
will be projected onto the contacted body.
±4 Insures full moment carrying glue when shells contact. The node
will not be projected onto the contact body and an existing initial
gap or overlap between the node and the contacted body will not
be removed, as the node will not be projected onto the contacted
body.
ISEARCH Option for contact searching order, from Secondary to Primary or from Primary to
Secondary, for deformable contact bodies. Ignored by SOL 700. ISEARCH is not
necessary in segment-to-segment contact. (Integer; Default = 0)
Main Index
1246 BCTABLE
Defines a Contact Table for General Contact
Describer Meaning
0 (Double orders search) ) the search order is from lower BCBODOY
ID's to higher ones first. Then it searches the opposite order. See
Remark 19.
1 (Single order search) the searching order is from Secondary to
Primary
2 (Single order search) let the program decide which search order. See
Remark 19.
Note that ISTYP in BCBDPRP or BCBODY is supported with ISEARCH=0 only.
ICOORD Enter 1 to modify the coordinates of a node in contact with a deformable body so
that stress-free initial contact can be obtained. Enter 2 to extend the tangential error
tolerance at sharp corners of deformable bodies to delay sliding off a contacted
segment. Enter 3 to have both 1 and 2 active. Ignored by SOL 700. (Integer;
Default = 0)
JGLUE This option is only relevant if the general glue option is invoked (IGLUE > 0 and
=1). Enter 0 if a node should not separate (default). Enter 1 to invoke the standard
separation behavior based on the maximum residual force. For SOLs 101 and 400,
enter 2 to activate breaking glue. (Integer; Default = 0)
For SOL 700 the following options are available:
0 Secondary nodes in contact and which come into contact will
permanently stick. Tangential motion is inhibited. This option is
only available with METHOD=SS1WAY or SS2WAY and
AUTO=YES.
DQNEAR Distance below which near thermal contact behavior occurs. Used in heat transfer
analysis only. Ignored by SOL 700. (Real; Default = 0; which means near contact
does not occur)
“FBSH” Enter character string FBSH if the line with items FRLIM, BIAS, SLIDE, HARDS
is required to change the defaults of any of these values. (SOLs 101 and 400)
FRLIM Friction stress limit. This entry is only used for friction type 6 (Coulomb friction
using the bilinear model). If the shear stress due to friction reaches this limit value,
then the applied friction force will be reduced so that the maximum friction stress
is given by min n limit , with the friction coefficient and n the
contact normal stress. (Real; Default = 1.0E20)
BIAS Contact tolerance bias factor. If this field is left blank, the default is the BIAS of the
BCPARA entry. A nonblank entry will override the BIAS entered on the BCPARA
entry. Note 0.0 is not default, and will override the BIAS on BCPARA.
SYSTEM(758)=1 will set 0.0 same as blank. (0.0<=Real<=1.0)
Main Index
BCTABLE 1247
Defines a Contact Table for General Contact
Describer Meaning
SLIDE Delayed slide off distance ratio. This entry should not be made unless ICOORD ≥
2 (see above). When using the delayed slide off option, a node sliding on a segment
will slide off this segment only if it passes the node (2-D) or edge (3-D) at a sharp
corner over a distance larger than the delayed slide off distance. By default, the
delayed slide off distance is related to the dimensions of the contacted segment by
a 20 percent increase of its isoparametric domain. (Real; Default = 0.2)
HARDS Hard-soft ratio. This entry is only used if double-sided contact with automatic
constraint optimization is used, (ISTYP=2 on the BCBODY entry). The hard-soft
ratio can be used by the program if there is a significant difference in the (average)
stiffness of the contact bodies (expressed by the trace of the initial stress-strain law).
If the ratio of the stiffnesses is larger then the hard-soft ratio, the nodes of the softest
body are the preferred secondary nodes. (Real; Default = 2.0)
“BKGL” Enter the character string BKGL if the line with items BGST, BGSN, BGM, BGN
is required. (SOLs 101 and 400)
BGSN Maximum normal stress for breaking glue. See Remark 10. (Real; Default = 0.0)
BGST Maximum tangential stress for breaking glue. See Remark 10. (Real; Default = 0.0)
BGM Exponent for the tangential stress term in deciding if a glue-contact will break. See
Remark 10. (Real; Default = 2.0)
BGN Exponent for the normal stress term in deciding if a glue-contact will break. See
Remark 10. (Real; Default = 2.0)
“SEGS” Enter the character string SEGS if the line with items PENALT and AUGDIST,
TPENALT and STKSLP is required for the segment-to-segment contact.
PENALT Augmented Lagrange penalty factor; used by the segment-to-segment contact
algorithm only. (Real > 0.0; see Remark 16. for default)
AUGDIST Penetration distance beyond which an augmentation will be applied; used by the
segment-to-segment contact algorithm only. (Real > 0, see Remark 17. for default)
“HHHB” Enter the character string HHHB if the line with items HCT, HCV, HNC, ..., up
to HGLUE is required in a pure thermal analysis or in a coupled thermal/structural
analysis. In a pure structural analysis they are ignored.
HCT Contact heat transfer coefficient. If Real, the value entered is the contact heat
transfer coefficient. If Integer, the value entered is the ID of a TABLEM1 or
TABLEM2 entry specifying the contact heat transfer coefficient vs temperature or
a TABL3D entry specifying the contact heat transfer coefficient vs temperature and
possibly other variables. (Real or Integer; Default = 0.0; In a thermal/mechanical
coupled analysis a default value of 1.0E6 is used when the mechanical glue option
is activated, i.w., when IGLUE > 0.)
Main Index
1248 BCTABLE
Defines a Contact Table for General Contact
Describer Meaning
HCV Convection coefficient for near field behavior. If Real, the value entered is the near
field convection coefficient. If Integer, the value entered is the ID of a TABLEM1
or TABLEM2 entry specifying the near field convection coefficient vs temperature
or a TABL3D entry specifying the near field convection coefficient vs temperature
and possibly other variables. (Real or Integer; Default = 0.0).
HNC Natural convection coefficient for near field behavior. If Real, the value entered is
the near field natural convection coefficient. If Integer, the value entered is the ID
of a TABLEM1 or TABLEM2 entry specifying the near field natural convection
coefficient vs temperature or a TABL3D entry specifying the near field natural
convection coefficient vs temperature and possibly other variables. (Real or Integer;
Default = 0.0).
BNC Exponent associated with the natural convection coefficient for near field behavior.
If Real, the value entered is the exponent associated with near field natural
convection coefficient. If Integer, the value entered is the ID of a TABLEM1 or
TABLEM2 entry specifying the exponent associated with the near field natural
convection coefficient vs temperature or a TABL3D entry specifying the exponent
associated with the near field natural convection coefficient vs temperature and
possibly other variables. (Real or Integer; Default = 1.0.)
EMISS Emissivity for radiation to the environment or near thermal radiation. If Real, the
value entered is the emissivity. If Integer, the value entered is the ID of a TABLEM1
or TABLEM2 entry specifying the emissivity vs temperature or a TABL3D entry
specifying the emissivity vs temperature and possibly other variables. (Real or
Integer; Default = 0.0)
HBL Separation distance dependent thermal convection coefficient. If Real, the value
entered is the convection coefficient. If Integer, the value entered is the ID of a
TABLEM1 or TABLEM2 entry specifying the convection coefficient vs
temperature or a TABL3D entry specifying the convection coefficient vs
temperature and possibly other variables. (Real or Integer; Default = 0.0).
HNL Heat transfer coefficient for nonlinear convective heat flow for near field behavior..
If Real, the value entered is the near field nonlinear convection coefficient. If
Integer, the value entered is the ID of a TABLEM1 or TABLEM2 entry specifying
the near field nonlinear convection coefficient vs temperature or a TABL3D entry
specifying the near field nonlinear convection coefficient vs temperature and
possibly other variables. (Real or Integer; Default = 0.0)
BNL Exponent associated with the nonlinear convective heat flow for near field behavior.
If Real, the value entered is the exponent associated with the near field nonlinear
convection coefficient. If Integer, the value entered is the ID of a TABLEM1 OR
TABLEM2 entry specifying the exponent associated with the near field nonlinear
convection coefficient vs temperature or a TABL3D entry specifying the exponent
associated with the near field nonlinear convection coefficient vs temperature and
possibly other variables. (Real or Integer; Default = 1.0)
Main Index
BCTABLE 1249
Defines a Contact Table for General Contact
Describer Meaning
HGLUE Flag to activate the thermal glue option. When left blank or set to zero, thermal
contact conditions will be treated by convective heat transfer between the bodies.
When set to 1, the temperature fields of the bodies are tied as soon as they come in
contact and there will be no convective heat transfer over the body interfaces. (0 <
Integer < 1; Default = 0)
FK Kinetic coefficient of friction. (Real > 0.0; Default = 0.0)
(SOL 700 only)
EXP Exponential decay coefficient. (Real > 0.0; Default = 0.0)
(SOL 700 only)
METHOD Character, Influences the contact type used. See Remark 19. Options are:
(SOL 700 only) FULL: Regular Contact (Default)
AIRBAG: Single Surface Contact
SS1WAY: Surface To Surface One Way
SS2WAY: Surface To Surface Two Way
RB1WAY: Rigid Body One Way To Rigid Body
RB2WAY: Rigid Body Two Way To Rigid Body
RNRB: Rigid Nodes To Rigid Body
TIEDNS: Tied Nodes to Surface
TIEDNSO: Tied Nodes to Surface with Offset
RELLIPS: Tied contact between grid points or rigid materials to ATB dummies.
See Remark 23.
BELT: Suited for modeling contact between a belt element and a rigid structure.
Primary secondary contact only. The contact logic doesn't apply a contact force, but
applies an enforced displacement and velocity that keeps the secondary nodes
exactly on top of the primary face. The secondary node does not slide relative to the
primary face when the friction coefficient (FS) is set to 1E20.
BELT1: Identical to BELT algorithm, except that the secondary nodes are initially
repositioned on top of the closest primary face. All secondary nodes initially
penetrated or within a distance of INITMON from a primary face, are
repositioned.
DRAWBEAD: Suited for modeling a drawbead. STYPE Must be GRID. The list
of secondary nodes must be ordered along the drawbead line. MTYPE Must be
SURF. The restraining force per unit drawbead length is specified in the field
DRWBEADF. It is V2 version contact.
DRAWBDV4: Suited for modeling a drawbead. STYPE Must be GRID. The list
of secondary nodes must be ordered along the drawbead line. MTYPE Must be
SURF. The restraining force per unit drawbead length is specified in the field
DRWBEADF. It is V4 version contact.
Main Index
1250 BCTABLE
Defines a Contact Table for General Contact
Describer Meaning
ADAPT Character, influences the contact type used.
(SOL 700 only) Options are NO or YES.
Default = NO
When ADAPT=YES, the BCBODY entries IDPRIMi must be defined as:
behav=DEFORM
bsid references a BCPROP
THICK Shell thickness scale factor. (Real > 0.0; Default = same as the value in
(SOL 700 only) DYPARAM,CONTACT,THICK)
THICKOF Artificial contact thickness offset. (Real > 0.0; Default = 0.0)
(SOL 700 only)
PENV Overwrites the default maximum penetration distance factor. (Real > 0.0; Default
(SOL 700 only) = 1.E20)
FACT Scale factor for the contact forces. (Real > 0.0; Default = 0.1)
(SOL 700 only)
TSTART Time at which the contact is activated. (Real > 0.0; Default = 0.0)
(SOL 700 only)
TEND Time at which the contact is deactivated. (Real > 0.0; Default = 1.e20)
(SOL 700 only)
MAXPAR Maximum parametric coordinate in segment. (Real > 0.0; Default = 1.025), search
(SOL 700 only) (values 1.025 and 1.20 recommended). Larger values can increase cost. If zero, the
default is set to 1.025. This factor allows an increase in the size of the segments.
May be useful at sharp corners.
IADJ Adjacent material treatment option for solid elements. (Integer > 0; Default = 1)
(SOL 700 only)
0 Solid element faces are included only for free boundaries.
1 Solid element faces are included if they are on the boundary of the
material subset. This option also allows the erosion within a body
and the subsequent treatment of contact.
IGNORE Ignore initial penetrations. (Integer > 1)
(SOL 700 only)
1 Allow initial penetrations to exist by tracking it
2 Move nodes to eliminate initial penetrations
AUTO (Character)
(SOL 700 only) Options are:
YES Automatic Contacts Activated (Default)
NO Non-Automatic Contact Activated. This option is not
recommended when Distributed Memory Parallel is activated.
Main Index
BCTABLE 1251
Defines a Contact Table for General Contact
Describer Meaning
SIDE Defines which side will be the monitoring side of a primary face. The opposite side
(SOL 700 only) of the primary face will be the penetration side. See Remark 24. (Characters;
default=BOTH)
BOTH: The side from which a secondary node approaches the primary face
will become the monitoring side.
TOP: The monitoring side will always be on the side of the primary face
that its normal is pointing at.
BOTTOM: The monitoring side is always on the opposite side of the primary
face that its normal is pointing at.
WEIGHT The contact force is multiplied by a mass-weighting factor. The following options
(SOL 700 only) are available. See Remark 25. (Character; default=BOTH)
BOTH: M sec ndry M primary
M scale = ---------------------------------------------------
M sec ndry + M primary
SECNDRY: M scale = M sec ndry
PRIMARY: M scale = M primary
NONE: M scale = 1.0
MONDIS Defines the fixed part of the monitoring distance. When the normal distance of a
(SOL 700 only) secondary node to a primary face becomes smaller than the monitoring distance the
secondary node will tag itself to the primary face. The side from which the
secondary node is moving towards the primary face becomes the monitoring
region. (Character; default=FACTOR)
FACTOR: The monitoring distance is equal to a factor times a characteristic
length of the primary faces. The factor is specified in MONDISV.
DISTANCE: The monitoring distance is specified in MONDISV.
MONDISV Value of the monitoring distance or value of the FACTOR to calculate the
(SOL 700 only) monitoring distance. (Real; default=2.0)
INITMON Fixed part of the monitoring distance used during the initialization. If not specified,
(SOL 700 only) the value of MONDIS is used. (Real > 0.0; default=MONDIS)
DAMPING Specifies if a high frequency damping is active or not. The damping force is based
(SOL 700 only) on the relative velocity of a secondary node with respect to a primary face. The
damping is preferably turned on in all cases, except for RIGID-RIGID contact. In
RIGID-RIGID contact it can result in a substantial loss of energy. VERSION V4
only. (Character; Default=YES)
YES damping is activated
N damping is not activated
Main Index
1252 BCTABLE
Defines a Contact Table for General Contact
Describer Meaning
“PRIMARY” Indicates the start of the list of bodies touched by touching body IDSEC1.
IDPRIMi Identification numbers of BCBODY Bulk Data entries defining touched bodies.
(Integer > 0)
Remarks:
1. BCTABLE defines surface contact.
2. If BCTABLE is not given, the default for contact analysis is assumed if BCONTACT=ALLBODY
in Case Control Section, and, every body detects the possibility of contact relative to all other bodies
and itself if it is a deformable body. If BCTABLE is given, the default for every body is overwritten.
The touching body does not contact itself unless requested. When the touched body is deformable,
double-sided contact is applied by default. BCTABLE is useful for deactivating or activating bodies
to reduce computational effort and to change contact conditions between subcases.
3. A short input to define two contact bodies exits if the user provides IDSCND and IDPRIM. Then it
is assumed that there are only two contact bodies, NGROUP is ignored and continuation entries are
not allowed. Default values are set for the parameters on the continuation entry.
4. If the user leaves IDSCND and IDPRIM blank, then NGROUP is normally required and
continuation entries are usually expected for NGROUP SECNDRY/PRIMARY combinations.
Exceptions are for SOL 700 self-contact may be designated using a secondary IDSEC1 of zero and
no PRIMARY entry.
5. For SOLs 101 and 400, the BCTABLE with ID=0 will be used in loadcase 0 automatically that does
not need a corresponding Case Control command BCONTACT=0. The loadcase 0 is purely elastic
and it can also be used to (1) move rigid contact bodies so that they just touch flexible contact bodies,
and/or (2) remove any prestressed condition by adjusting the coordinates of the active nodes, which
are the Grid Points on the surface of all deformable BCBODY’s. BCTABLE, 0 is not used to define
the contact relationship for any loadcases. ONLY BCTABLE, n(n>0), will dominate the contact
analysis for each loadcase. To place an entry in any physical loadcase (SUBCASE or STEP), the ID
must be selected by the Case Control command BCONTACT=ID. When
BCONTACT=ALLBODY, there is no ID of BCTABLE specified; therefore, the default values of all
entries of BCTABLE are assumed.
6. The line starting with “HHHB” is used for heat transfer or thermal contact analyses only. Also, see
Remark 17.
7. It is not necessary to enter all continuation lines between SECNDRY and PRIMARY. For example,
if an entry is required on the 4th SECNDRY line, the first 3 must be entered with some being blank
and those after the 4th may be omitted. All continuation lines prior to the last needed must be
entered.
Main Index
BCTABLE 1253
Defines a Contact Table for General Contact
8. Many secondary/primaries may be entered up to the number specified in Remark 5. A new secondary
entry may not begin until the primaries from the previous entry are finished (as shown in the
example). The number of primary surfaces for any given secondary surface is limited by the number
specified in Remark 5., however most GUI’s produce one secondary surface and one primary surface
per secondary/primaries pairs.
9. COPTS, COPTM, COPTS1 and COPTM1 are packed numbers designating how the surfaces may
contact using the formula
COPxxx=A+10*B+1000*C
where the following codes apply:
A: the outside of the solid elements in the body
• = 1: the outside will be in the contact description (Default)
B (flexible bodies): the outside of the shell elements in the body
• = 1: both top and bottom faces will be in the contact description, thickness offset will be included
(Default)
• = 2: only bottom faces will be in the contact description, thickness offset will be included
• = 3: only bottom faces will be in the contact description, shell thickness will be ignored
• = 4: only top faces will be in the contact description, thickness offset will be included
• = 5: only top faces will be in the contact description, shell thickness will be ignored
• = 6: both top and bottom faces will be in the contact description, shell thickness will be ignored
Note: The choice B = 6 for both bodies in a contact combination is only meaningful for glued
contact. If in such cases separation is allowed, separated nodes will not come into contact
anymore, unless a new CONTACT TABLE is defined to reset the value of B.
Note: For node-to-segment with edge-to-edge glue contact, use B=6.
Note: For thermal contact with 2D shell elements, i.e., uniform temperature gradient across
thickness, do not use B=2 or B=3.
B (rigid bodies): the rigid surface
• = 1: the rigid surface should be in the contact description (Default)
C (flexible bodies): the edges of the body
• = 1: only the beam/bar edges are included in the contact description (Default)
• = 10: only the free and hard shell edges are included in the contact description
• = 11: both the beam/bar edges and the free and hard shell edges are included in the contact
description
Note that C has no effect if beam-to-beam contact is not switched on (BEAMB 1on
BCPARA).
Note that C has no effect if segment-to-segment contact is used.
10. Breaking Glue provides glued contact to all GRID's at their very 1st contact. This kind of glued-
contact will break if
Main Index
1254 BCTABLE
Defines a Contact Table for General Contact
(sigma_n/BGSN)**bgn + (sigma_t/BGST)**bgm > 1.0
When a contact node breaks due to the above criterion, standard contact is activated if it comes into
contact again. If BGSN = 0.0 the first term is ignored. If BGST is zero, the second term is ignored.
11. For hard contact, with HGLUE=1:
a. The temperature of the contacting grid is tied to the temperatures of the contacted element face
or the temperature of the rigid geometry when it has a scalar point associated with it.
b. The temperature of the contacting grid is set to the rigid geometry temperature when it has no
scalar point associated with it.
Note: “Glued” thermal contact can result in overshoot of the temperatures at the interface, in
particular, if two bodies that have non-uniform initial temperatures are placed in contact. The
overshoot effect may be damped somewhat if one uses a near contact distance with some
convective heat transfer.
12. For hard contact, with HGLUE=0:
The convective heat flow per unit area over the two interfaces is given by:
q = HCT T A – T B
where TA is the contacting grid temperature and TB is the face temperature in the contact point in
case of a meshed body or the TBODY temperature in case of a rigid geometry.
13. For near contact:
q = HCV T A – T B +
BNC
HNC T A – T B +
BNL BNL
HNL T A – TB +
4 4
EMISS T A – T B +
dist dist
HCT 1 – ------------------------- + HBL ------------------------- T A T B
DQNEAR DQNEAR
where the last term is only activated when HBL 0, TA is the contacting grid temperature and TB is
the face temperature in the contact point in case of a meshed body or the TBODY temperature in case
of a rigid geometry.
14. The heat transfer coefficients and associated exponents can all be temperature dependent, when they
are entered as an integer value. This integer value is the table ID of a TABLEM1, TABLEM2 or
TABL3D entry (formulas are not supported on TABL3D).
15. Table IDs of tables used on the BCTABLE and the BCBODY entry must be unique.
Main Index
BCTABLE 1255
Defines a Contact Table for General Contact
16. The penalty factor used in the augmented Lagrange method is by default derived from the contact
characteristic distance and the stiffness of the deformable contact bodies involved (note that the
dimension of the penalty factor is force per cubic length).
0.5 S i + S j
PENALT = ----------------------------
L
The body stiffness (Si and Sj), are either defined by the average trace of the initial stress-strain law of
the elements defining the two contact bodies or by the average bulk modulus for (nearly)
incompressible rubber materials, whichever of the two is the largest.
For continuum elements, the characteristic length ( L ) is given by one half of the average length of all
the edges being part of the contact boundary. For shell elements, the characteristic length is given by
half of the average thickness of all the shell elements being part of a contact body. When there is
contact between a solid and a shell element, then the characteristic length is defined by the shell
element.
In case of contact with a rigid body, since there is no body stiffness associated with a rigid body, the
default value is related to the deformation body only and given by:
1000S i
PENALT = ----------------
L
17. By default, the threshold value of this penetration distance is 0.05 times the default contact
characteristic distance.
AUGDIST = 0.05L
18. The multipoint constraint equations (MPC equations) internally created from body contact can be
printed out in standard Nastran punch file by using Case Control command, NLOPRM MPCPCH.
This capability is good for all solutions except SOL 700.
19. When ISEARCH=0 (and ISTYP=0 in default on BCBODY), the search order is from lower
BCBODOY ID to higher one to create the first set of contact constraints and then add the constraints
in the search order from higher BCBODY ID to lower one as long as they are not in conflict with the
first set.
When ISEARCH=2, the program looks into the smallest element edge at the outer boundary (and
the smallest thickness in case of shell elements) of each BCBODY. Then, the search order of the two
deformable contact bodies is determined by the following rule when ID1 < ID2
CL1= Min(1/20 of the smallest edge,1/4 of the smallest thickness) of BCBODY ID1
CL2= Min(1/20 of the smallest edge,1/4 of the smallest thickness) of BCBODY ID2
CL1 and CL2 refers to characteristic length of BCBODY ID1 and ID2.
Main Index
1256 BCTABLE
Defines a Contact Table for General Contact
The search order is from lower BCBODY ID1 to higher BCBODY ID2 if CL1<=1.05*CL2.
Otherwise, if CL1>1.05*CL2 the search order is from BCBODY ID2 to BCBODY ID1.
20. Fields ISEARCH, DQNEAR and "BKGL" are not supported in segment to segment contact analysis.
21. If STKSLP is set to 0.0 (Default), the sticking stiffness K1 is equal to the maximum friction force
(µ FNORMAL), where µ is the friction coefficient) divided by the maximum sticking displacement.
Otherwise, K1 is equal to the maximum friction force divided by the value of STKSLP.
22. When the initial stress-free(ICOORD=1), Node-to-Seg updates model geometry to close the gap,
nodes are projected onto the contact body; but Seg-to-Seg treats initial stress-free as pre-stress in the
equation without geometry update, no node projection is considered.
23. When METHOD=RELLIPS is used, BCGRID or BCMATL are only available for SECNDRY body
and BCELIPS is only available for PRIMARY body. When BCMATL is used, the MATRIG id or
RBE2 id are only acceptable.
24. The options TOP/BOTTOM are useful in the following cases:
a. When a secondary node initially is located on the primary face (see the picture below), the contact
situation is uniquely defined, only if the TOP or BOTTOM side of the primary surface is defined:
SIDE=TOP case:
b. When hooking of secondary nodes on the wrong side of a primary face might occur. This often
is the case when the primary face is at the edge of a shell element structure:
SIDE=BOTTOM case: penetration of node 1 (SIDE=BOTH: no penetration of node 1)
Main Index
BCTABLE 1257
Defines a Contact Table for General Contact
25. Recommended usage of WEIGHT:
SECNDRY PRIMARY WEIGHT
Deformable Deformable BOTH
Deformable Rigid SECNDRY
Rigid Deformable PRIMARY
Rigid Rigid NONE
Default setting when BCELIPS is used in SECNDRY or PRIMARY:
SECNDRY PRIMARY WEIGHT
Non-BCELIPS BCELIPS SECNDRY
BCELIPS Non-BCELIPS NONE
BCELIPS
Main Index
1258 BCTABLE - Glued Option
Defines a Contact Table for Permanently Glued Contact
BCTABLE - Glued Option Defines a Contact Table for Permanently Glued Contact
Defines a glued contact used in SOLs 101, 103, 105, 107, 108, 109, 110, 111, 112, 144, 145, 146, 200 and
SOL 400 for the permanently-glued or general contact.
Format:
1 2 3 4 5 6 7 8 9 10
BCTABLE ID NGROUP COPTS COPTM
“SECNDRY” IDSEC1 ERROR CINTERF IGLUE
ISEARCH ICOORD
“FBSH” BIAS SLIDE COPTS1 COPTM1
“PRIMARY” IDPRIM1 IDPRIM2 IDPRIM3 IDPRIM4 IDPRIM5 IDPRIM6 IDPRIM7
IDPRIM8 IDPRIM9 ...
Examples:
BCTABLE 101 2 61 61
SECNDRY 20 0.002 0.2 1
1
FBSH 0.01 60 60
PRIMARY 31 32 33
SECNDRY 40 1
PRIMARY 51 52 53 54
Describer Meaning
ID Identification number of a BCTABLE entry to be selected by BCONTACT Case
Control command. See Remark 5. for the general contact. Case Control,
BCONTACT=ALLBODY, cannot be used for the permanently glued contact. See
Remark 1. (Integer > 0; Required)
NGROUP Flag to indicate the number of pairs of “SECNDRY” and “PRIMARY” entries in the
continuation lines. (Integer > 0; Required)
COPTS, COPTM Flag to indicate how secondary and primary surfaces may contact. See Remark 6. for
the general contact.
“SECNDRY” Indicates that this line defines the secondary or touching body and its parameters.
IDSEC1 Identification number of a BCBODY Bulk Data entry defining the touching body.
(Integer > 0; Required)
ERROR Distance below which a node is considered touching a body. When this field is left
blank or 0.0, the value is taken from BCPARA = 0, ERROR, if it is specified.
Otherwise, Nastran automatically calculates the value. See the Bulk Data entry
BCPARA for more details. (Real)
Main Index
BCTABLE - Glued Option 1259
Defines a Contact Table for Permanently Glued Contact
Describer Meaning
CINTERF Interference closure amount, normal to the contact surface. For CINTERF < 0.0,
overlap between bodies, CINTERF > 0.0, gap between bodies. (Real; Default = 0.0)
IGLUE Flag to activate the glue options. See the descriptions of various options in
BCTABLE for the general contact. This field must be specified for the glued
contact. See Remark 4. (Integer > 0; Required).
1. Activates the glue option. In the glue option, all degrees-of- freedom of the
contact nodes are tied in case of deformable-deformable contact once the
node comes in contact. The relative tangential motion of a contact node is
zero in case of deformable-rigid contact. This option is recommended when
there is no gap or overlap between contact surfaces or initial stress free contact
is specified.
2. Activates a special glue option to insure that there is no relative tangential and
normal displacement when a node comes into contact. An existing initial gap
or overlap between the node and the contacted body will not be removed, as
the node will not be projected onto the contacted body. To maintain an
initial gap, ERROR should be set to a value slightly larger than the physical
gap.
3. Insures full moment carrying glue when shells contact. This option is
recommended when moments are important and there is no gap or overlap
between contact surfaces or initial stress free contact is specified.
4. Insures full moment carrying glue when shells contact. The node will not be
projected onto the contact body and an existing initial gap or overlap
between the node and the contacted body will not be removed, as the node
will not be projected onto the contacted body.
ISEARCH Option for contact searching order, from a secondary (touching) to a primary
(touched) body or visca versa, for deformable contact. See the options in BCTABLE
for the general contact. (Integer; Default = 0)
0 (Double orders search) 0(Double orders search) the search order is from
lower BCBODOY ID's to higher ones first. Then it searches the opposite
order. See Remark 19. in BCTABLE.
1 (Single order search) the searching order is from Secondary to Primary
2 (Single order search) let the program decide which search order. See
Remark 19. in BCTABLE.
ICOORD Enter 1 to modify the coordinates of a node in contact with a deformable body so
that stress-free initial contact can be obtained. Enter 2 to extend the tangential error
tolerance at sharp corners of deformable bodies to delay sliding off a contacted
segment. Enter 3 to have both 1 and 2 active. (Integer; Default = 0)
“FBSH” Character string used to introduce BIAS, COPTS1, and COPTM1.
Main Index
1260 BCTABLE - Glued Option
Defines a Contact Table for Permanently Glued Contact
Describer Meaning
BIAS Contact tolerance bias factor. If this field is left blank, the default is the BIAS of the
BCPARA entry. A nonblank entry will override the BIAS entered on the BCPARA
entry. Note 0.0 is not default, and will override the BIAS on BCPARA.
SYSTEM(758)=1 will set 0.0 same as blank. (0.0<=Real<=1.0)
SLIDE Delayed slide off distance. This entry should not be made unless ICOORD ≥ 2 (see
above). When using the delayed slide off option, a node sliding on a segment will
slide off this segment only if it passes the node (2-D) or edge (3- D) at a sharp corner
over a distance larger than the delayed slide off distance. By default, the delayed slide
off distance is related to the dimensions of the contacted segment by a 20 percent
increase of its isoparametric domain. (Real; Default = 0.2)
COPTS1, Flag to indicate how individual pair of secondary and primary contact surfaces may
COPTM1 contact. These two fields override COPTS and COPTM. See Remark 6.
“PRIMARY” Indicates the start of the list of bodies touched by touching body IDSEC1.
IDPRIMi Identification numbers of BCBODY Bulk Data entries defining touched bodies.
(Integer > 0; Required)
Remarks:
1. This BCTABLE entry is tailored specifically for what we called the permanently-glued contact (or
tied contact), from the entry of BCTABLE for the general contact, where the glued is an option in
the approaching-and-touched contact. Most of the descriptions and remarks on the fields in this entry
can be found in the BCTABLE for the general contact.
2. Permanent glued contact for small rotation condition is defined when all IGLUE fields of BCTABLE,
reference by the very first loadcase, (the 1st STEP of the 1st SUBCASE in SOL 400 or the 1st
SUBCASE in others) is set to larger than 0, IGLUE(>0). In BCPARA with ID=0, the value of
NLGLUE may not be 1.
For large deformation and large rotation condition, permanent glued contact is activated by negative
IGLUE (<0) and works in corresponding subcase or step in the corresponding subcase or step where
it is defined, no matter what is set (1 or 0). This type of permanent glued contact with large
deformation and large rotation may be applied together with combination of general glued contact
and touching contact. IGLUE will be changed to negative automatically if SYSTEM(758)=2 when
Permanently Glued setting is found with large rotation/deformation effect turned on.
3. The MPC equations internally created for the glued contact can be printed out in Nastran standard
punch file by using Case Control command, NLOPRM MPCPCH=BEGN.
4. IGLUE=±2 or ±4 is favorable to passing the GROUNDCHECK. The initial stress-free contact is also
available to preserve the six rigid-body modes with IGLUE = 1 or 3.
5. For SOLs 101 and 400, the BCTABLE with ID=0 will be used in loadcase automatically that does
not need a corresponding Case Control command BCONTACT=0. The loadcase 0 is purely elastic
and it can also be used to (1) move rigid contact bodies so that they just touch flexible contact bodies,
and/or (2) remove any prestressed condition by adjusting the coordinates of the active nodes, which
Main Index
BCTABLE - Glued Option 1261
Defines a Contact Table for Permanently Glued Contact
are the Grid Points on the surface of all deformable BCBODY’s. To place an entry in any physical
loadcase (SUBCASE or STEP), the ID must be selected by the Case Control command
BCONTACT=ID. When BCONTACT=ALLBODY, there is no ID of BCTABLE specified;
therefore, the default values of all entries of BCTABLE are assumed.
6. COPTS, COPTM COPTS1 and COPTM1 are packed numbers designating how the surfaces may
contact using the formula
COPxxx=A+10*B+1000*C
where the following codes apply:
A: the outside of the solid elements in the body
• = 1: the outside will be in the contact description (Default)
B (flexible bodies): the outside of the shell elements in the body
• = 1: both top and bottom faces will be in the contact description, thickness offset will be included
(Default)
• = 2: only bottom faces will be in the contact description, thickness offset will be included
• = 3: only bottom faces will be in the contact description, shell thickness will be ignored
• = 4: only top faces will be in the contact description, thickness offset will be included
• = 5: only top faces will be in the contact description, shell thickness will be ignored
• = 6: both top and bottom faces will be in the contact description, shell thickness will be ignored
Note: The choice B = 6 for both bodies in a contact combination is only meaningful for glued
contact. If in such cases separation is allowed, separated nodes will not come into contact
anymore, unless a new CONTACT TABLE is defined to reset the value of B.
Note: For node-to-segment with edge-to-edge glue contact, use B=6.
Note: For thermal contact with 2D shell elements, i.e., uniform temperature gradient across
thickness, do not use B=2 or B=3.
B (rigid bodies): the rigid surface
• = 1: the rigid surface should be in the contact description (Default)
C (flexible bodies): the edges of the body
• = 1: only the beam/bar edges are included in the contact description (Default)
• = 10: only the free and hard shell edges are included in the contact description
• = 11: both the beam/bar edges and the free and hard shell edges are included in the contact
description
Note that C has no effect if beam-to-beam contact is not switched on (BEAMB≠1 on BCPARA)
7. It is not supported that a permanently-glued contact is used to glue a deformable body to a rigid one.
If it is a SOL 101 or SOL 400 job, the general contact with glued option must be performed.
8. For SOL108, SOL111, SOL200 and SOL400 for ANALYSIS=DFREQ or MFREQ with frequency
dependent materials, the contact stiffness is computed using nominal material properties and is not
frequency dependent.
Main Index
1262 BCTABL1
Defines a Contact Table
BCTABL1 Defines a Contact Table
BCTABL1 specifies a list of contact pairs through the BCONECT option for SOLs 101, 103, 105, 107, 108,
109, 110, 111, 112, 144, 145, 146, 200, 400 and 700. Only SOL 101, 400 and 700 can support all contact
types: touching contact, glued, step glue and permanent glue (see Chapter 7: Contact Types of Nastran SOL 400
Getting Started Guide). Note that SOL 700 calls it “tie” contact to glue (also step glue or permanent glue).
SOL 103, 105, 107 - 112, 144, 145, 146 and standard 200 can only support permanent glue. When SOL
400 optimization, it can support all contact types. This contact table is activated in the BCONTACT Case
Control command.
Format:
1 2 3 4 5 6 7 8 9 10
BCTABL1 BCID ID1 ID2 ID3 ID4 ID5 ID6 ID7
ID8 ID9 -etc.-
Examples:
BCTABL1 2 198 62 75 8 159 31 82
17
BCTABL1 0 23 56
BCTABL1 5 31 35 THRU 40 163 THRU 169
1077 1088
Describer Meaning
BCID Unique identification number referenced by a BCONTACT Case Control command.
See Remark 3. (Integer ≥ 0; default=0)
IDi Identification number of BCONECT entry (Integer > 0 or “THRU”; ID1 is required).
See Remark 4. and 5.
Remarks:
1. BCTABL1 defines surface contact. If BCTABL1 does not exist, the Case Control command
BCONTACT=BCID may refer to the BCONECT Bulk Data entry directly.
2. If neither BCTABL1 nor BCONECT is given, the default for contact analysis is assumed, every body
detects the possibility of contact relative to all other bodies and itself if it is a deformable body. If
BCTABL1 or BCONECT is given, the default for every body is overwritten. The touching body does
not contact itself unless requested. When the touched body is deformable, double-sided contact is
applied by default. BCTABL1 or BCONECT is useful for deactivating or activating bodies to reduce
computational effort and to change contact conditions between subcases.
Main Index
BCTABL1 1263
Defines a Contact Table
3. For SOLs 101 and 400, the BCTABL1 or BCONECT with ID=0 will be used in loadcase 0
automatically that does not need a corresponding Case Control command BCONTACT=0. The
loadcase 0 is purely elastic and it can also be used to (1) move rigid contact bodies so that they just
touch flexible contact bodies, and/or (2) remove any prestressed condition by adjusting the
coordinates of the active nodes, which are the Grid Points on the surface of all deformable
BCBODY1’s. To place an entry in any physical loadcase (SUBCASE or STEP), the BCID must be
selected by the Case Control command BCONTACT=BCID or BCONECT=BCID. When
BCONTACT=ALLBODY, there is no BCID of BCTABL1 or BCONECT specified; therefore, the
default values of all entries of BCONPRG and BCONPRP are assumed. Case Control command
BCONTACT=ALLBODY cannot be used for permanently glued contact.
4. When the “THRU” option is used, all BCONECT entries associated with intermediate BCONECT
IDs must exist. The word “THRU” may not appear in field 3 or 9 (2 or 9 for continuations).
5. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1264 BCTRIM
Defines the Geometry of a Trimming Curve
BCTRIM Defines the Geometry of a Trimming Curve
Defines the geometry of a trimming curve used to specify a NURBS for a rigid contact body.
Format:
1 2 3 4 5 6 7 8 9 10
BCTRIM IDtrim NPTUtrim NORUtrim NSUBtrim
“COORD” Xisoparam1 Yisoparam1 Xisoparam2 Yisoparam2 -etc.-
“HOMO” Homot1 Homot2 Homot3 -etc.-
“KNOT” Knott1 Knott2 Knott3 -etc.-
Examples:
BCTRIM 202 2 2 50
COORD 0.0 0.0 1.0 0.0
HOMO 1. 1.
KNOT 0.0 0.0 1. 1.
Describer Meaning
IDtrim Unique trimming vector identification number referenced by a BCNURBS entry.
(Integer > 0)
NPTUtrim Number of control points for this trimming vector. (Integer > 0)
NORUtrim Order for this trimming vector. (Integer > 0)
NSUBtrim Number of subdivisions for this trimming vector. (Integer > 0)
“COORD” Indicate the start of the list of isoparametric coordinates of points.
Xisoparam1, First and second coordinates of point in isoparametric space. There must be
Yisoparam1, NPTUtrim set of (Xisoparam, Yisoparam) entries. (Real)
Xisoparam2,
Yisoparam2, etc.
“HOMO” Indicate the start of the list of homogeneous coordinates of this trimming vector.
Homot1, Homot2, Homogeneous coordinatesof this trimming vector. There must be NPTUtrim
Homot3, etc. entrie. (Real; 0.0 to 1.0)
“KNOT” Indicate the start of the list of knot vectors of this trimming vector.
Knot1, Knot2, Knot vectors of this trimming vector. There must be (NPTUtrim+NORUtrim)
Knot3, etc. entries. (Real; 0.0 to 1.0)
Remarks:
1. BCTRIM is referenced by a BCNURBS entry to define the trimming curve of a NURBS for a rigid
contact body.
Main Index
BDYLIST 1265
Fluid Boundary List
BDYLIST Fluid Boundary List
Defines the boundary between a fluid and a structure.
Format:
1 2 3 4 5 6 7 8 9 10
BDYLIST RHO IDF1 lDF2 IDF3 IDF4 IDF5 IDF6 IDF7
IDF8 -etc.-
Example:
BDYLIST .037 AXIS 432 325 416 203 256 175
Describer Meaning
RHO Fluid mass density at boundary. (Real > 0.0 or blank; Default is DRHO on the AXIF
entry)
IDF1 Identification number of a RINGFL entry. (Integer > 0 or Character = “AXIS” or
“LAXIS”) See Remark 7.
IDF2-IDFi Identification number of additional RINGFL entries. (Unique Integers > 0)
Remarks:
1. This entry is allowed only if an AXIF entry is also present.
2. Each entry defines a boundary if RHO 0.0. The order of the points must be sequential with the
fluid on the right with respect to the direction of travel.
3. The word “AXIS” defines an intersection with the polar axis of the fluid coordinate system.
4. There is no limit to the number of BDYLIST entries specified. If the fluid density varies along the
boundary, there must be one BDYLIST entry for each interval between fluid points.
5. The BDYLIST entry is not required and should not be used to specify a rigid boundary where
structural points are not defined. Such a boundary is automatically implied by the omission of a
BDYLIST.
6. If RHO=0.0, no boundary matrix terms will be generated to connect the GRIDB points to the fluid.
This option is a convenience for structural plotting purposes. GRIDB points may be located on a fluid
ring (RINGFL entry) only if the rings are included in a BDYLIST.
7. If the polar axis of the fluid coordinate system is to occur at the first point use AXIS. If the polar axis
of the fluid coordinate system is to occur at the last point use LAXIS.
Main Index
1266 BDYOR
CHBDYi Entry Default Values
BDYOR CHBDYi Entry Default Values
Defines default values for the CHBDYP, CHBDYG, and CHBDYE entries.
Format:
1 2 3 4 5 6 7 8 9 10
BDYOR TYPE IVIEWF IVIEWB RADMIDF RADMIDB PID GO
CE E1 E2 E3
Example:
BDYOR AREA4 2 2 3 3 10
Describer Meaning
TYPE Default surface type. See Remark 2. (Character)
IVIEWF Default identification number of front VIEW entry. (Integer > 0 or blank)
IVIEWB Default identification number of back VIEW entry. (Integer > 0 or blank)
RADMIDF Default identification number of a RADM entry for front face. (Integer > 0 or blank)
RADMIDB Default identification number of a RADM entry for back face. (Integer > 0 or blank)
PID Default PHBDY property entry identification number. (Integer > 0 or blank)
GO Default orientation grid point. (Integer > 0; Default = 0)
CE Default coordinate system for defining the orientation vector. (Integer > 0 or blank)
E1, E2, E3 Default components of the orientation vector in coordinate system CE. The origin of
this vector is grid point G1 on a CHBDYP entry. (Real or blank)
Remarks:
1. Only one BDYOR entry may be specified in the Bulk Data Section.
2. TYPE specifies the type of CHBDYi element surface; allowable values are: POINT, LINE, REV,
AREA3, AREA4, ELCYL, FTUBE, AREA6, AREA8, and TUBE.
3. IVIEWF and IVIEWB are specified for view factor calculations only (see VIEW entry).
4. GO is only used from BDYOR if neither GO nor the orientation vector is defined on the CHBDYP
entry and GO is > 0.
5. E1, E2, E3 is not used if GO is defined on either the BDYOR entry or the CHBDYP entry.
Main Index
BEADVAR 1267
Topography Design Variable
BEADVAR Topography Design Variable
Defines design region for topography (bead or stamp) optimization.
Format:
1 2 3 4 5 6 7 8 9 10
BEADVAR ID PTYPE PID MW MH ANG BF SKIP
“DESVAR” NORM/XD YD ZD CID XLB XUB DELXV
“GRID” NGSET DGSET
Example using NORM:
BEADVAR 10 PSHELL 101 10.0 20.0 70.0
Example using “DESVAR” and “GRID”:
BEADVAR 10 PSHELL 101 10.0 20.0 70.0 NONE
DESVAR 2.0 3.0 4.0 -1.0 1.0
GRID 100
Describer Meaning
ID Unique topography design region identification number. (Integer > 0)
PTYPE Property entry type. Used with PID to identify the element nodes to be
designed. (Character: “PSHELL”, “PSHEAR”, “PCOMP”, or “PCOMPG”.)
PID Property entry identifier. See Remark 1. (Integer > 0)
MW Minimum bead width. This parameter controls the width of the beads. The
recommended value is between 1.5 and 2.5 times the average element width.
See Remark 2. (Real > 0.0)
MH Maximum bead height (Real > 0.0). This parameter sets the maximum height
of the beads when XUB=1.0 (as Default). See Remark 2.
ANG Draw angle in degrees (0.0 < Real < 90.0). This parameter controls the angle
of the sides of the beads. The recommended value is between 60 and 75
degrees.
BF Buffer zone ('yes' or 'no'; Default='yes'). This parameter creates a buffer zone
between elements in the topography design region and elements outside the
design region when BF='yes'. See Remark 3.
Main Index
1268 BEADVAR
Topography Design Variable
Describer Meaning
SKIP Boundary skip (“bc”, “load”, “both”, or “none”; Default = “both”). This
parameter indicates which element nodes are excluded from the design region.
“bc” indicates all nodes referenced by “SPC” and “SPC1” are omitted from the
design region. “load” indicates all nodes referenced by “FORCE”, “FORCE1”,
“FORCE2”, “MOMENT”, “MOMENT1”, “MOMENT2”, and “SPCD”
are omitted from the design region. “both” indicates nodes with either “bc” or
“load” are omitted from the design region. “none” indicates all nodes
associated with elements referencing PID specified in field 4 are in the design
region.
“DESVAR” Indicates that this line defines bead design variables that are automatically
generated.
NORM/XD, YD, ZD Bead vector (draw direction). Norm indicates the shape variables are created in
the normal directions to the elements. If XD, YD, and ZD are provided, the
shape variables are created in the direction specified by the xyz vector defied by
XD/YD/ZD that is given in the basic coordinate system or CID. See Remark
4. (Character or Real; Default = blank = norm).
CID Coordinate system ID used for specifying draw direction (Blank or Integer >
0; Default = blank = basic coordinate system)
XLB Lower bound. (Real < XUB or blank; Default = blank=0.0). This ensures the
lower bound on grid movement equal to XLB*MH. See Remark 5.
XUB Upper bound. (Real > XLB or blank; Default = 1.0). This sets the upper bound
of the beads equal to XUB*MH. See Remark 5.
DELXV Fractional change allowed for the design variable during approximate
optimization. See Remark 3. (Real > 0.0; Default = 0.2)
“GRID” Indicates this line defines what element nodes can be added and/or removed
from topography design regions.
NGSET All grids listed on a Bulk Data entry SET1 = NGSET are removed from
topography design regions.
DGSET All grids listed on a Bulk Data entry SET1 = DGSET are added to topography
design regions.
Remarks:
1. Multiple BEADVAR’s are allowed in a single file. Combined topometry, topology, topography,
sizing, and shape optimization is supported in a single file.
Main Index
BEADVAR 1269
Topography Design Variable
2. The user can provide allowable bead dimensions.
MW
MH
ANG
Bead Dimensions
3. It is recommended to set buffer zone = yes to maintain a good quality of mesh during topography
optimization.
Design elements
Buffer zone No buffer zone
Nondesign elements Nondesign elements
4. The grids moves in the normal direction. All element grids referenced by one BEADVAR entry must
follow the right hand rule.
Element normal vectors
Baseline surface
Optimized
surface
Element Normal
Main Index
1270 BEADVAR
Topography Design Variable
User defined draw vector
Baseline surface
Optimized
surface
User’s Provided Draw Direction
5. To force the grids to move only in the positive bead vector direction (one side of the surface), use XLB
= 0.0. To force the grids to move only in the negative bead vector direction (another side of the
surface), use XUB = 0.0. To allow grids to move in both positive and negative bead vector directions,
use XLB < 0.0 and XUB > 0.0. For example,
Bead Vector
Bead Vector
Base Surface
Optimized Surface Optimized Surface
(a) XLB = 0.0 and XUB = 1.0 (b) XLB = -1.0 and XUB = 0.0 (c) XLB = -1.0 and XUB = 1.0
6. The jobname.h5 file (created by specifying MDLPRM,HDF5,0 in the bulk data input) has
topography optimization results (shape changes) that can be viewed in Patran. The text file
jobname.pch also has updated grid coordinates that can be copied to the original file, replace the
original grids, and imported to Patran and other post-processors to view topography optimization
results.
7. The BEADVAR entry cannot be used with thermal loads.
Main Index
BEAMOR 1271
CBEAM Entry Default Values
BEAMOR CBEAM Entry Default Values
Defines default values for field 3 and fields 6 through 9 of the CBEAM entry.
Format:
1 2 3 4 5 6 7 8 9 10
BEAMOR PID X1 X2 X3 OFFT
Example:
BEAMOR 39 0.6 2.9 -5.87 GOG
Alternate Format and Example:
BEAMOR PID G0 OFFT
BEAMOR 39 86 GOG
Describer Meaning
PID Property identification number of the PBEAM or PBCOMP entry. (Integer > 0 or
blank)
X1, X2, X3 Components of orientation vector v , from GA, in the displacement coordinate system
at GA (default), or in the basic coordinate system. See Remark 5. (Real)
G0 Alternate method to supply the orientation vector v , using grid point G0. Direction
of v is from GA to G0. v is then translated to End A. (Integer > 0; G0 GA or GB
on CBEAM entry)
OFFT Offset vector interpretation flag. See Remark 5. (Character or blank)
Remarks:
1. The contents of fields on this entry will be assumed for any CBEAM entry with corresponding fields
that are blank.
2. Only one BEAMOR entry is allowed.
3. For an explanation of beam element geometry, see the CBEAM entry description.
4. If X1 or G0 is integer, G0 is used. If X1 or G0 is blank or real, then X1, X2, X3 is used.
5. OFFT in field 9 is a character string code that describes how the offset and orientation vector
components are to be interpreted. By default (string input is GGG or blank), the offset vectors are
measured in the displacement coordinate systems at grid points A and B and the orientation vector is
measured in the displacement coordinate system of grid point A. At user option, the offset vectors can
be measured in an offset system relative to grid points A and B, and the orientation vector can be
measured in the basic system as indicated in the following table:
Main Index
1272 BEAMOR
CBEAM Entry Default Values
String Orientation Vector End A Offset End B Offset
GGG Global Global Global
BGG Basic Global Global
GGO Global Global Offset
BGO Basic Global Offset
GOG Global Offset Global
BOG Basic Offset Global
GOO Global Offset Offset
BOO Basic Offset Offset
Any attempt to specify invalid combinations results in a bulk data entry input error message. For
example, a value of OOO (indicating offset and orientation vectors are specified in an offset reference
system) results in a fatal error since the orientation vector cannot be specified in an offset system. The
offset system x-axis is defined from GA to GB. The orientation vector v and the offset system x-axis
are then used to define the z and y axes of the offset system. (Note: The character “O” in the table
replaces the obsolete character “E”.)
Main Index
BFRlC 1273
Contact Friction
BFRlC Contact Friction
Defines frictional properties between two bodies in contact using the slideline contact in SOL 106 and SOL
129. SOL 400 is the recommended approach for contact analysis.
Format:
1 2 3 4 5 6 7 8 9 10
BFRIC FID FSTIF MU1
Example:
BFRIC 33 0.3
Describer Meaning
FID Friction identification number. See Remark 1. (Integer > 0)
FSTlF Frictional stiffness in stick. See Remarks 2. and 3. (Real > 0.0; Default = automatically
selected by the program)
MU1 Coefficient of static friction. (Real > 0.0)
Remarks:
1. This identification number must be unique with respect to all other friction identification numbers.
This is used in the FRICID field of BCONP Bulk Data entry.
2. The value of frictional stiffness requires care. A method of choosing its value is to divide the expected
frictional strength (MU1*expected normal force) by a reasonable value of the relative displacement
that may be allowed before slip occurs. The relative value of displacement before slip occurs must be
small compared to expected relative displacements during slip. A large stiffness value may cause poor
convergence, while too small a value may cause poor accuracy.
Frictional stiffness specified by the user is selected as the initial value. If convergence difficulties are
encountered during the analysis, the frictional stiffness may be reduced automatically to improve
convergence.
3. The stiffness matrix for frictional slip is unsymmetric. However, the program does not use the true
unsymmetric matrix. Instead the program uses only the symmetric terms. This is to avoid using the
unsymmetric solver to reduce CPU time.
Main Index
1274 BIAS
MESH Bias Definition
BIAS MESH Bias Definition
Specifies a variation of the mesh-size in one direction for use in the MESH entry in SOL 700. The MESH
entry can create a biased or non-uniform mesh. A uniform mesh consists of a number of planes separated by
a fixed distance, but for a biased mesh the distance between subsequent planes can differ. The BIAS definition
allows specifying the locations of planes in one direction. For a number of intervals the density of planes can
be specified.
Format:
1 2 3 4 5 6 7 8 9 10
BIAS BID
X0 GROWTH0 N0 DXS0 DXE0
X1 GROWTH1 N1 DXS1 DXE1
Xi GROWTHi Ni DXSi DXEi
Example:
BIAS 100
-4.5 0.2 15
-1 1 20
1 0.1 0.46
Describer Meaning
BID Unique bias number. Must be referenced from MESH entry. (Integer; Required)
Xi Begin coordinate of an interval. The interval ends at the X i + 1 entry. (Real;
Default = 0.0)
GROWTHi GROWTHi is the ratio between the step size at the beginning of the interval and at the
end of the interval. If it is smaller than 1.0 then the mesh refines when going from the
beginning of the interval to the end of the interval. (Real>0)
See Remarks 1.- 3.
Ni Ni is the number of elements inside the interval. (Integer>0) See Remarks 1.- 3.
DXSi DXSi is the start element size of the interval. (Real>0) See Remarks 1.- 3.
DXEi DXEi is the end element size of the interval. (Real>0) See Remarks 1.- 3.
Remarks:
1. The begin point of the first interval has to be equal to the X0 field of the MESH entry and may be
left unspecified. The end point of the last interval is given by X0 + DX as specified by the MESH
entry. In the example above, the first interval is given by [-4.5,-1], the second one by [-1,1] and the
last one by [1,4.5], assuming that X0 + DX = 4.5 on the MESH entry that references the bias
definition from IBIDX.
Main Index
BIAS 1275
MESH Bias Definition
2. To define the bias in an interval four fields are available. These are GROWTHi, Ni, DXSi and DXEi.
To specify the bias inside an interval two of these four variables have to specified. The other two
variables have to left blank. In addition the mesh size can be chosen constant by defining Ni and
leaving GROWTHi, DXSi an DXEi blank.
This gives seven methods of specifying a bias;
1. Define GROWTHi and Ni. DXSi and DXEi have to be left blank.
2. Define DXSi and DXEi. GROWTHi and Ni have to be left blank.
3. Define DXSi and Ni. GROWTHi and DXEi have to be left blank.
4. Define DXEi and Ni. GROWTHi and DXSi have to be left blank.
5. Define GROWTHi and DXSi. Ni and DXEi have to be left blank.
6. Define GROWTHi and DXEi. Ni and DXSi have to be left blank.
7. Only define Ni and leave GROWTHi, DXSi an DXEi blank.
For method 2 it can happen that the biased elements do not exactly fit into the interval.
To get a good fit a small change to defined start and end step sizes is made. These changes in general
amount to a few percents.
For method 5 and 6 a small change to the specified growth factor can be made so that the biased
elements fit into the interval.
3. The algorithm for each method first determines an appropriate growth factor so that the biased
elements fit into the interval. In addition the number of planes is determined. For method 2, 3 and
4 this is done by using bisection. The location of the planes is given by:
X i = X i – 1 + X i – 1
X i = GROWFAC X i – 1
N–1
GROWTHi = GROWFAC
Here X(i) denotes the location of the Euler plane, Xi denotes the step size of the interval and N
denotes the number of Euler planes. The index i runs across the Euler planes. The variable
GROWFAC denotes the grow factor between planes within the interval. The locations of the planes
X(i) are written to the OUT file as part of MESH output. In addition, the growth of the element sizes
is written out in the next column. This is given as the ratio in element size between the layer of
elements to the right of the plane and to the left of the plane. Let x0, x1 and x2 denote three
subsequent planes, then the element size to the left of the x1-plane is given x1-x0 and to the right it
is given by x2-x1. The ratio by which the element size grows if one goes across the x1-plane is:
X2 – X1-
-------------------
X1 – X0
To get physically meaningful results, this value should not exceed 1.3 or be smaller than 0.7 .
Within each interval the ratio in element size equals GROWFAC. But the element size between two
adjacent elements that are in two different intervals can differ from GROWFAC. Here each interval
has a distinct GROWFAC variable.
Main Index
1276 BIAS
MESH Bias Definition
For both method 2, 5 and 6 The growth factor GROWFAC and start and end step sizes that are
actually used can be obtained from this plane summary in the OUT file. In this summary for each
plane a growth factor and step size is specified.
Also the total number of elements is written out.
Main Index
BJOIN 1277
BJOIN
Defines (multiple) pairs of grid points of one-dimensional and/or shell elements to be joined during the
analysis in SOL 700. When the failure criterion for a grid-point pair is satisfied, the grid-point pair is removed
from the join and the grid-point motion is computed for the separate grid points. The join ceases to exist
when all pairs of the join have failed, after which all of the grid points of the join are treated as separate grid
points.
Format:
1 2 3 4 5 6 7 8 9 10
BJOIN BID SID TOL TYPE SN SS
MULTI
TF
Example:
BJOIN 1 2 SPOTWELD 1.E3 1.E3
Describer Meaning Type Default
BID BJOIN number. Integer > 0 Required
SID BCGRID ID of set of grid points. Integer > 0 Required
TOL Tolerance used in matching grid point pairs. Real > 0.0 1.E-4
TYPE Type of failure criterion. C SPOTWELD
SPOTWELD Spotweld-type failure.
SN Failure force in tension. Real > 0.0 No failure
SS Failure force in shear. Real > 0.0 No failure
MULTI Multiple breakable joins, where the grid points must be C YES
entered as a sequence of BJOIN pairs.
YES The grid points are entered on the BCGRID entry
as a sequence of BJOIN pairs.
NO The code creates BJOIN pairs for every two grid
points entered on the BCGRID entry when the grid
point positions fall within the tolerance (TOL).
TF Failure time for nodal constraint set. Real 1.0E20
Main Index
1278 BJOIN
Remarks:
1. Nodes connected by a spot weld cannot be members of another constraint set that constrain the same
degrees-of-freedom, a tied interface, or a rigid body, i.e., nodes cannot be subjected to multiple,
independent, and possibly conflicting constraints. Also, care must be taken to ensure that single point
constraints applied to nodes in a constraint set do not conflict with the constraint sets constrained
degrees-of-freedom.
2. When the failure time, TF, is reached the spot weld becomes inactive and the constrained nodes may
move freely.
3. Note that the shell elements do not have rotary stiffness in the normal direction and, therefore, this
component cannot be transmitted.
4. For MULTI=YES, a spotweld or rivet will always be created, regardless if their distance is larger than
the value of TOL. TOL will only be used for MULTI=NO.
Main Index
BLSEG 1279
Boundary Line Segments
BLSEG Boundary Line Segments
Defines a curve that consists of a number of line segments via grid numbers that may come in contact with
another body.
Format:
1 2 3 4 5 6 7 8 9 10
BLSEG ID G1 G2 G3 G4 G5 G6 G7
Alternate Format:
BLSEG ID G1 “THRU” G2 “BY” INC
The Continuation Entry formats may be used more than once and in any order. They may also be used with
either format above.
Continuation Entry Format 1:
G8 G9 G10 G11 -etc.-
Continuation Entry Format 2:
G8 “THRU” G9 “BY” INC
Example:
BLSEG 15 5 THRU 21 BY 4
27 30 32 33
35 THRU 44
67 68 72 75 84 93
Describer Meaning
ID Line segments identification number. See Remark 2. (Integer > 0)
Gi Grid point identification numbers on a curve in a continuous topological order so that
the normal to the segment points toward the other curve. See Remark 3. (Integer > 0)
INC Grid point identification number increment. See Remark 3. (Integer or blank)
Remarks:
1. A line segment is defined between every two consecutive grid points. Thus, the number of line
segments defined is equal to the number of grid points specified minus 1. A corresponding BWlDTH
Bulk Data entry may be required to define the width/thickness of each line segment. If the
corresponding BWlDTH is not present, the width/thickness for each line segment is assumed to be
unity.
Main Index
1280 BLSEG
Boundary Line Segments
2. ID must be unique with respect to all other BLSEG entries. Each line segment has a width in 3-D
sideline and a thickness in a 2-D slideline contact to calculate contact stresses. The width/thickness
of each line segment is defined via BWIDTH Bulk Data entry. The ID in BLSEG must be same as
the ID specified in the BWlDTH. That is, there must be a one to one correspondence between
BLSEG and BWlDTH. BWlDTH Bulk Data entry may be omitted only if the width/thickness of
each segment is unity.
3. For automatic generation of grid numbers, the default increment value is 1 if grid numbers are
increasing or -1 if grid numbers are decreasing (i.e., the user need not specify BY and the increment
value).
4. The normal to the segment is determined by the cross product of the slideline plane vector (i.e., the
Z direction of the coordinate system defined in the ‘ClD’ field of BCONP Bulk Data entry) and the
tangential direction of the segment. The tangential direction is the direction from node 1 to node 2
of the line segment.
5. A curve may be closed or open. A closed curve is specified by having the last grid point identification
number the same as the first grid number.
6. See BCBODY for use of BLSEG in 3D contact.
Main Index
BNDFIX 1281
Fixed Boundary Degrees-of-Freedom
BNDFIX Fixed Boundary Degrees-of-Freedom
Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized dynamic reduction or
component mode synthesis calculations.
Format:
1 2 3 4 5 6 7 8 9 10
BNDFIX ID1 C1 ID2 C2 ID3 C3 ID4 C4
Example:
BNDFIX 2 135 14 6
Describer Meaning
IDi Grid or scalar point identification number. (Integer > 0)
Ci Component number. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points. No embedded blanks.)
Remarks:
1. BNDFIX and BSET entries are equivalent to each other. Either one of them or any combination of
them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on BSETi/BNDFIXi entries form members of the mutually exclusive
b-set. They may not be specified on other entries that define mutually exclusive sets. See the Degree-
of-Freedom Sets for a list of these entries.
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
Main Index
1282 BNDFIX1
Fixed Boundary Degrees-of-Freedom, Alternate Form of BNDFIX Entry
BNDFIX1 Fixed Boundary Degrees-of-Freedom, Alternate Form of BNDFIX Entry
Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized dynamic reduction or
component mode synthesis calculations.
Format:
1 2 3 4 5 6 7 8 9 10
BNDFIX1 C ID1 ID2 ID3 ID4 ID5 ID6 ID7
ID8 ID9 ID10 -etc.-
Example:
BNDFIX1 2 135 14 6 23 24 25 26
122 127
Alternate Format and Example:
BNDFIX1 C ID1 “THRU” ID2
BNDFIX1 3 6 THRU 32
Describer Meaning
C Component numbers. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points with no embedded blanks.)
IDi Grid or scalar point identification numbers. (Integer > 0; For “THRU” option,
ID1< ID2)
Remarks:
1. BNDFIX1 and BSET1 entries are equivalent to each other. Either one of them or any combination
of them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on BSETi/BNDFIXi entries form members of the mutually exclusive
b-set. They may not be specified on other entries that define mutually exclusive sets. See the Degree-
of-Freedom Sets for a list of these entries.
Main Index
BNDFIX1 1283
Fixed Boundary Degrees-of-Freedom, Alternate Form of BNDFIX Entry
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
Main Index
1284 BNDFREE
Free Boundary Degrees-of-Freedom
BNDFREE Free Boundary Degrees-of-Freedom
Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during generalized dynamic reduction or
component modes calculations.
Format:
1 2 3 4 5 6 7 8 9 10
BNDFREE ID1 C1 ID2 C2 ID3 C3 ID4 C4
Example:
BNDFREE 124 1 5 23 6 16
Describer Meaning
IDi Grid or scalar point identification number. (Integer > 0)
Ci Component numbers. (Integer zero or blank for scalar points, or any unique
combination of the Integers 1 through 6 for grid points with no embedded blanks.)
Remarks:
1. BNDFREE and CSET entries are equivalent to each other. Either one of them or any combination
of them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on CSETi/BNDFREE/BNDFRE1 entries form members of the
mutually exclusive c-set. They may not be specified on other entries that define mutually exclusive
sets. See Degree-of-Freedom Sets for a list of these entries.
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
Main Index
BNDFRE1 1285
Free Boundary Degrees-of-Freedom, Alternate Form of BNDFREE Entry
BNDFRE1 Free Boundary Degrees-of-Freedom, Alternate Form of BNDFREE Entry
Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during generalized dynamic reduction or
component modes calculations.
Format:
1 2 3 4 5 6 7 8 9 10
BNDFRE1 C ID1 ID2 ID3 ID4 ID5 ID6 ID7
ID8 ID9 -etc.-
Example:
BNDFRE1 124 1 5 7 6 9 12 122
127
Alternate Formats and Examples:
BNDFRE1 C ID1 “THRU” ID2
BNDFRE1 3 6 THRU 32
BNDFRE1 “ALL”
BNDFRE1 ALL
Describer Meaning
C Component number. (Integer zero or blank for scalar points, or any unique
combination of the Integers 1 through 6 for grid points with no embedded blanks)
IDi Grid or scalar point identification number. (Integer > 0; For THRU option,
ID1 < ID2)
ALL All a-set degress-of-freedom will be set free (included in c-set).
Remarks:
1. BNDFRE1 and CSET1 entries are equivalent to each other. Either one of them or any combination
of them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on CSETi/BNDFREE/BNDFRE1 entries form members of the
mutually exclusive c-set. They may not be specified on other entries that define mutually exclusive
sets. See Degree-of-Freedom Sets for a list of these entries.
Main Index
1286 BNDFRE1
Free Boundary Degrees-of-Freedom, Alternate Form of BNDFREE Entry
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
Main Index
BNDGRID 1287
Boundary Grid Points
BNDGRID Boundary Grid Points
Specifies a list of grid point identification numbers on design boundaries or surfaces for shape optimization
(SOL 200).
Format:
1 2 3 4 5 6 7 8 9 10
BNDGRID C GP1 GP2 GP3 GP4 GP5 GP6 GP7
GP8 -etc.-
Example:
BNDGRID 123 41 42 43 44 45 46 47
49
Alternate Format and Example:
BNDGRID C GP1 “THRU” GP2
BNDGRID 123 41 THRU 49
Describer Meaning
C Component number (any unique combination of integers 1 through 6 with no
embedded blanks). See Remark 1.
GPi Shape boundary grid point identification number. (0 < Integer < 1000000; For
THRU option, GP1 < GP2)
Remarks:
1. C specifies the components for the listed grid points for which boundary motion is prescribed.
2. Multiple BNDGRID entries may be used to specify the shape boundary grid point identification
numbers.
3. Both fixed and free shape boundary grid point identification numbers are listed on this entry.
4. The degrees-of-freedom specified on BNDGRID entries must be sufficient to statically constrain the
model.
5. Degrees-of-freedom specified on this entry form members of the mutually exclusive s-set. They may
not be specified on other entries that define mutually exclusive sets. See Degree-of-Freedom Sets for a
list of these entries.
6. Fluid grids are not supported for BNDGRID.
Main Index
1288 BOLT
Defines the Multi-Point Constraints for a Bolt
BOLT Defines the Multi-Point Constraints for a Bolt
Defines a rigid bolt by a set of MPC constraints.
Format:
1 2 3 4 5 6 7 8 9 10
BOLT ID GRIDC
TOP GT1 GT2 GT3 GT4 GT5 GT6 GT7
GT8 GT9 etc.
BOTTOM GB1 GB2 GB3 GB4 GB5 GB6 GB7
GB8 GB9 etc.
Example:
BOLT 100 1025
TOP 101 102 103 104 105
BOTTOM 1 2 3 4 5
Describer Meaning
ID Element ID of the bolt. (Integer; Required)
GRIDC Control GRID ID where forces or displacements are applied. (Integer; Required)
TOP Indicate the start of the entry that defines all of the grids at the “top” of the bolt
intersection with the structure.
GT1, GT2, etc. Grid IDs of the grid points at the top of the bolt intersection. (Integer; no Default)
BOTTOM Indicate the start of the entry that defines all of the grids at the “bottom” of the bolt
intersection with the structure.
GB1, GB2, etc. Grid IDs of the grid points at the bottom of the bolt intersection. (Integer; no Default.
Do not enter the ID for GRIDC)
Remarks:
1. The GRIDS entries of the TOP and BOTTOM keywords are open-ended.
2. GRIDC is the control grid point and usually not connected to any element.
3. (GTi, GBi) are pairs of grid on top and bottom.
4. To each pair of (GTi, GBi) and GRIDC, MPCs are created internally to all 6 DOFs. Since the GBs
always belong to dependent-DOFs, they cannot be applied to any SPC, SPC1, SPCD and SPCR.
5. Same number of grid points in TOP and BOTTOM. They should be coincident but it is not
required. Users who do otherwise do so at their own risk since the current design does not consider
the initial offset between them.
Main Index
BOLT 1289
Defines the Multi-Point Constraints for a Bolt
6. Bolt loads, including enforced motion, are usually prescribed on GRIDC to represent the pre-tension,
overlap or loading of the bolt. BOLT relative displacements are given in the global coordinate system
of the control node.
7. Global Coordinate System may have to be defined at the Control Node if the bolt direction is not a
Basic Coordinate direction and the user wants to apply the loads along the shaft of the bolt.
8. Loads in directions other than the shaft of the bolt direction are possible.
9. The internally written MPC relationship is of the form:
u GB = u GT + u GC
10. In 3D Contact analysis, it replaces GBi (Bottom bolt segment) by GTi (Top bolt segment) on the
internally generated contact surface, which makes contact surface continuous across the mesh split
between them.
11. Force output is obtained through Case Control MPCFORCE.
12. The internal MPCs generated by the BOLT entry are valid for small rotations only.
13. The BOLT entry must be defined in the residual structure only.
14. Sufficient boundary conditions must be placed on the BOLT to prevent mechanisms.
15. In contact analysis, care should be taken that the preload displacement does not exceed the local
element width.
16. Pretension of a BOLT is a three step process in SOL 400:
SUBCASE 1
STEP 1
LOAD=n Applies a pretension load to the bolt on the control grid.
SPC=m If any required to prevent motion of structure do not include the
control grid.
STEP 2
LOAD=p1 Load entry pointing to a SPCR (relative value of 0.0) and any other
desired type of loading.
SPC=q1 SPC1 includes control grid and any other desired SPC requirements.
STEP 3
LOAD=p2 Load entry pointing to a SPCR and any other additional desired type of
loading.
SPC=q2 SPC1 includes control grid and any other additional desired SPC
requirements.
17. The BOLT may also be used in SOL101 and SOL103. In this case PARAM, AUTOMSET, YES is
recommended.
Main Index
1290 BOLT1
Bolt Model
BOLT1 Bolt Model
Defines an easy-to-use pre-tension bolt model that supports nonlinear analysis and large rotation. BOLT1
allows bolt forces or displacements to be applied at a layer of elements along a cross-section in the bolt, thus
modeling the effect of bolt pre-tension without the need for duplicating grid points or splitting the bolt finite
element mesh into top and bottom sections around the bolt cross-section. The bolt's local coordinate system
and axial direction are continuously updated to track bolt rotation. Used in SOL 400 with advanced
nonlinear elements only.
Format:
1 2 3 4 5 6 7 8 9 10
BOLT1 ID GRIDC FORM N1 N2 N3 OFFSET IDTYPE
"ELEM" E1 E2 E3 E4 E5 E6 E7
E8 E9 etc.
“GRID” G1 G2 G3 G4 G5 G6 G7
G8 G9 etc.
Example: Simple Method using FORM = 0
BOLT1 1 10
ELEM 1 2 3 4 5 6
Example: Cross-section method using FORM = 1
BOLT1 2 20 1 0.0 0.0 1.0 SET
ELEM 11
GRID 12
Describer Meaning
ID Unique bolt ID. (Integer; Required)
GRIDC Control grid ID where pre-tension loads or tightening displacements are applied.
(Integer; Required)
FORM Specify input format for bolt definition. ((Integer; Default = 0)
0: Simple method, enter the list of elements making the bolt, no need to enter
bolt axial direction or grid points forming the bolt cross-section.
1: Cross-section method, enter vector defining bolt axis, enter the list of grid
points forming the bolt cross-section and list of elements sharing cross-
section grid points and lying on the opposite side of the normal vector.
Ni Components of a vector defining bolt axis (direction normal to cross-section). (Real;
Required only if FORM = 1)
Main Index
BOLT1 1291
Bolt Model
Describer Meaning
OFFSET Cross-section offset in axial direction (fraction of bolt length). (Real; Used for FORM=0
only; Default = 0.0)
IDTYPE Method for defining a list of element and grid IDs. (Character; Default = "LIST" or
blank)
"LIST": Enter the character string LIST, or leave blank, to allow entering lists of
element IDs Ei and grid point IDs Gi.
"SET": Enter the character string SET to allow entering lists of element and grid
points as sets. E1 and G1 refer to SET3 entries with DES = "ELEM" and
"GRID", respectively.
ELEM Enter the character string ELEM to define a list of elements. (Character; Required)
Ei Element IDs (Integer; no Default)
If FORM = 0, list of element IDs of the bolt (must enter at least 2 elements along the
axis of the bolt).
If FORM = 1, list of element IDs sharing grid points in the bolt cross-section and lying
on the opposite side of the cross-section normal vector.
IF IDTYPE = “SET”, E1 is the ID of a SET3 entry with DES = “ELEM” used to define
a list of element IDs other Ei entries will be ignored.
GRID Enter the character string GRID to define a list of grid points. (Character; Required
only if FORM = 1)
Gi Grid IDs for the bolt cross-section. (Integer; Required only if FORM = 1; no Default)
IF IDTYPE = "SET", G1 is the ID of a SET3 entry with DES = "GRID", other Gi
entries will be ignored.
Remarks:
1. The bolt control grid point GRIDC is unique to each bolt and should be used only to apply bolt pre-
tension forces or enforced displacements. GRIDC is a special grid point that has a single degree-of-
freedom only aligned along the bolt axial direction and should not be connected to any element or
grid in the model. GRIDC should not have an associated displacement coordinate system CD defined
on the GRID entry. Applied loads and displacements should always be along the first degree-of-
freedom (T1) of the control grid. Output for bolt axial force and displacement are also along the first
degree-of-freedom (T1) of the control grid.
2. For the cross-section input format of the bolt definition, FORM=1, user must enter the initial
direction of the bolt axis, or bolt cross-section normal vector, Ni. User must give the list of grid points
defining the bolt cross-section, where pre-tension is applied, using GRID. User must also specify the
list of elements sharing grid points in the bolt cross-section and lying on the opposite side of the cross-
section normal vector using ELEM.
Main Index
1292 BOLT1
Bolt Model
3. Using the simple input format of bolt definition, FORM=0, the complete list of bolt elements is
specified using ELEM. The bolt axial direction is automatically computed by the program to be along
the principal axis of the bolt elements. The bolt cross-section is also internally selected by the program
to pass by the bolt center of mass by default. User can move the position of the bolt cross-section along
the bolt axis away from the center of mass using the OFFSET parameter if needed.
4. For FORM=1, the cross-section normal vector cannot be of zero length.
5. For FORM=0, the number of elements entered must be at least 2 in order to be able to compute the
bolt axis. In addition, bolt elements are not allowed to have a negative Jacobian in this case. The order
of element connectivity must follow element definition rules in order to correctly compute the bolt
axis.
6. The method for entering bolt element and grid IDs under ELEM and GRID can be controlled using
IDTYPE either as list of IDs or defining a list on SET3 entries.
7. BOLT1 is supported for advanced nonlinear elements in SOL 400 only. As such, nonlinear property
extensions should be defined for bolt elements. The program will attempt to internally map the
element properties used by BOLT1 elements to advanced nonlinear elements if possible.
Alternatively, MDLPPRM,BOLTCNEL,1 can be used to search for all elements connected to
BOLT1 elements and map their element properties. Automatic mapping is turned off if the user has
set NLMOPTS,SPROPMAP,-1 in the Bulk Data section. In this case nonlinear property extensions
must be defined for bolt elements.
8. Current limitations:
• BOLT1 does not support Herrmann elements.
• GPFORCE output for the control grid does not show contributions of cross-section elements.
9. Pretension of a BOLT1 is a three step process in SOL 400:
SUBCASE 1
STEP 1
LOAD=n Applies a pretension load to the bolt on the control grid.
SPC=m If any required to prevent motion of structure do not include the
control grid.
STEP 2
LOAD=p1 Load entry pointing to a SPCR (relative value of 0.0) and any other
desired type of loading.
SPC=q1 SPC1 includes control grid and any other desired SPC requirements.
STEP 3
LOAD=p2 Load entry pointing to a SPCR and any other additional desired type of
loading.
SPC=q2 SPC1 includes control grid and any other additional desired SPC
requirements.
Main Index
BOUTPUT 1293
Output for Slideline Contact
BOUTPUT Output for Slideline Contact
Defines secondary nodes at which output is requested.
Format:
1 2 3 4 5 6 7 8 9 10
BOUTPUT ID G1 G2 G3 G4 G5 G6 G7
Alternate Format:
BOUTPUT ID G1 “THRU” G2 “BY” INC
The Continuation Entry formats may be used more than once and in any order. They may also be used with
either format above.
Continuation Entry Format 1:
G8 G9 G10 G11 -etc.-
Continuation Entry Format 2:
G8 “THRU” G9 “BY” INC
Example:
BOUTPUT 15 5 THRU 21 BY 4
27 30 32 33
35 THRU 44
67 68 72 75 84 93
Format and Example Using “ALL” (No continuation entry is allowed):
BOUTPUT ID ALL
BOUTPUT 15 ALL
Describer Meaning
ID Contact region identification number of a BCONP entry for which output is desired,
or the contact Grid ID, in 3D contact. (Integer > 0)
Gi Secondary node numbers for which output is desired. (Integer > 0)
INC Grid point identification number increment. See Remark 1. (Integer or blank)
Main Index
1294 BOUTPUT
Output for Slideline Contact
Remark:
1. For automatic generation of grid numbers, the default increment value is 1 if grid numbers are
increasing or -1 if grid numbers are decreasing (i.e., the user need not specify BY and the increment
value).
Main Index
BRKPROP 1295
Specifies Property of Brake System for Brake Squeal Analysis Using SOL 400
BRKPROP Specifies Property of Brake System for Brake Squeal Analysis Using SOL 400
Defines property of brake system for brake squeal calculations.
Format:
1 2 3 4 5 6 7 8 9 10
BRKPROP ID Param_i Value Param_i Value Param_i Value
Param_i Value Param_i Value
Example:
1 2 3 4 5 6 7 8 9 10
BRKPROP 28 AVSTIF 1.0E7 FRICT 0.25
Describer Meaning
ID Identification ID of the Brake Property referred by the entry card BRKSYS
AVSTIF Approximate average stiffness per unit area between the two surfaces. AVSTIF is used as
penalty contact stiffness, it needs to be a large value but not so large that numerical instabilities
result. If AVSTIF is large enough, increasing it by a few orders of magnitude will not
appreciably affect the squeal modes. (Real; Required if TAVSTIF=0).
TAVSTIF Table ID of a TABL3Di providing temperature or spatial variation of the average stiffness
(Integer; Default = 0 which means AVSTIF should be defined).
FRICT Enter the friction coefficient. If 0, the friction coefficient is obtained from the CONTACT
TABLE option.
Remarks:
1. When TAVSTIF is 0, AVSTIF should be defined. Otherwise, Nastran will issue a fatal message and
stop.
Main Index
1296 BRKSYS
Specifies Data for Brake System for Brake Squeal Analysis Using SOL 400
BRKSYS Specifies Data for Brake System for Brake Squeal Analysis Using SOL 400
Defines data for brake system for brake squeal calculations involving one wheel or multiple wheels with one
axis or multi-axes.
Format:
1 2 3 4 5 6 7 8 9 10
BRKSYS ID OMETH IVEC BSONLY ISLIDEBS
Disk1 BD1_ID BD2_ID MT1_ID MT2_ID BProp_ID
Disk2 BD1_ID BD2_ID MT1_ID MT2_ID BProp_ID
Diski BD1_ID BD2_ID MT1_ID MT2_ID BProp_ID
Example:
1 2 3 4 5 6 7 8 9 10
BRKSYS 900 0.5 0 YES
INNER 8 9 18 19 28
OUTER 8 9 18 19 28
Describer Meaning
ID Identification ID of number of a corresponding BSQUEAL Case Control command
OMETH Specifies the corresponding load factor (or time step) where the brake squeal analysis is to be
performed. (Real; Default = 0.0)
BSONLY Brake-Squeal-Only flag to control whether or not to continue nonlinear iterations after brake
squeal analysis is performed. (Character; Default = YES)
YES: Means to perform brake squeal analysis only and exit nonlinear iteration immediately
NO: means to continue nonlinear analysis.
IVEC Flag specifying whether friction vector at center of primary contact body is in the same
direction as that of the nodes of the secondary body; See Figure 9-3. (Integer; Default = 0)
0: In same direction
1: In tangential direction
ISLIDEBS Flag indicating whether contact status is treated as sliding or general static contact for brake
disk/pad pairs. (Integer; Default = 0)
0: Sliding contact for brake disk/pad pairs
1: General static contact
Disk_i Name of the ith brake system
BD1_ID ID of BCBODY1 of the first body which is defined in this brake system
BD2_ID ID of BCBODY1 of the second body which is defined in this brake system
Main Index
BRKSYS 1297
Specifies Data for Brake System for Brake Squeal Analysis Using SOL 400
Describer Meaning
MT1_ID ID of MOTION which is defined for the first body with BD1_ID
MT2_ID ID of MOTION which is defined for the second body with BD2_ID. If blank, MT1_ID will be
used
BProp_ID ID of BRKPROP which defines the property of this brake system
Remark:
1. When modules are present, multiple BRKSYS entries with the same ID can be put in different
modules and selected by BSQUEAL Case Control command. In addition with this, MDBKSYS in
module 0 with the same ID can also be selected.
MSC Nastran only uses one set of fields in the first line of those entries (fields OMETH, IVEC,
BSONLY and ISLIDEBS).
• If not all the sets are identical:
- When MDBKSYS is selected, its fields will be used.
- If MDBKSYS doesn’t exist or isn’t selected and all the sets of those fields of BRKSYS entries
are not identical, use the default values.
If all the sets are identical, use the specified values.
Retained node
Tied node
Tied node
Tangential vector
Vector at retained node is the same as at tied node
rotation circle
Figure 9-3 Vectors of frictional stiffness at tied and retained node.
Main Index
1298 BSET
Fixed Analysis Degrees-of-Freedom
BSET Fixed Analysis Degrees-of-Freedom
Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized dynamic reduction or
component mode synthesis calculations.
Format:
1 2 3 4 5 6 7 8 9 10
BSET ID1 C1 ID2 C2 ID3 C3 ID4 C4
Example:
BSET 2 135 14 6
Describer Meaning
IDi Grid or scalar point identification number. (Integer > 0)
Ci Component number. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points. No embedded blanks.)
Remarks:
1. BSET and BNDFIX entries are equivalent to each other. Either one of them or any combination of
them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on BSETi/BNDFIXi entries form members of the mutually exclusive
b-set. They may not be specified on other entries that define mutually exclusive sets. See the Degree-
of-Freedom Sets for a list of these entries.
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
5. SOL 400 does not support OMITAX as well as ASETi, OMITi, BSETi, CSETi, SUPORTi, and
QSETi except in the some situations (See Remark 4. under ASET).
Main Index
BSET1 1299
Fixed Analysis Degrees-of-Freedom, Alternate Form of BSET Entry
BSET1 Fixed Analysis Degrees-of-Freedom, Alternate Form of BSET Entry
Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized dynamic reduction or
component mode synthesis calculations.
Format:
1 2 3 4 5 6 7 8 9 10
BSET1 C ID1 ID2 ID3 ID4 ID5 ID6 ID7
ID8 ID9 ID10 -etc.-
Example:
BSET1 2 135 14 6 23 24 25 26
122 127
Alternate Format and Example:
BSET1 C ID1 “THRU” ID2
BSET1 3 6 THRU 32
Describer Meaning
C Component numbers. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points with no embedded blanks.)
IDi Grid or scalar point identification numbers. (Integer > 0; For “THRU” option,
ID1< ID2)
Remarks:
1. BSET1 and BNDFIX1 entries are equivalent to each other. Either one of them or any combination
of them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on BSETi/BNDFIXi entries form members of the mutually exclusive
b-set. They may not be specified on other entries that define mutually exclusive sets. See the Degree-
of-Freedom Sets for a list of these entries.
Main Index
1300 BSET1
Fixed Analysis Degrees-of-Freedom, Alternate Form of BSET Entry
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
5. SOL 400 does not support OMITAX as well as ASETi, OMITi, BSETi, CSETi, SUPORTi, and
QSETi except in the some situations (See Remark 4. under ASET).
Main Index
BSQUEAL 1301
Specifies Data for Brake Squeal Analysis Using SOL 400
BSQUEAL Specifies Data for Brake Squeal Analysis Using SOL 400
Defines data for brake squeal calculations involving one wheel as well as other rotating objects used in SOL
400.
Format:
1 2 3 4 5 6 7 8 9 10
BSQUEAL ID OMETH AVSTIF BSONLY
RX RY RZ X Y Z
Example:
1 2 3 4 5 6 7 8 9 10
BSQUEAL 100 0.2 5.34E6 NO
0.0 0.0 1.0 2.0 3.0 4.0
Describer Meaning
ID Identification number of a corresponding BSQUEAL Case Control command
(Integer > 0).
OMETH Specifies the corresponding load factor (or time step) where the brake squeal analysis
is to be performed. (Real; Default = 0.0 in SOL 400, see Remark 5.
AVSTIF Approximate average stiffness per unit area between the two surfaces. AVSTIF is used a
penalty contact stiffness, it needs to be a large value but not so large that numerical
instabilities result. If AVSTIF is large enough, increasing it by a few orders of magnitude
will not appreciably affect the squeal modes. (Real; Required)
BSONLY Brake-Squeal-Only flag to control whether or not to continue nonlinear iterations after
brake squeal analysis is performed. BSONLY=YES means to perform brake squeal analysis
only and exit nonlinear iteration immediately; BSONLY=NO means to continue nonlinear
analysis. (Character; Default = YES)
RX X direction cosine (basic coordinate system) of axis of rotation (Real; or blank).
RY Y direction cosine (basic coordinate system) of axis of rotation (Real; or blank).
RZ Z direction cosine (basic coordinate system) of axis of rotation (Real; or blank).
X X coordinate in basic coordinate system of a point on the axis of rotation (Real; or blank).
Y Y coordinate in basic coordinate system of a point on the axis of rotation (Real; or blank).
Z Z coordinate in basic coordinate system of a point on the axis of rotation (Real; or blank).
Remarks:
1. This entry is used to perform brake squeal analysis or other contact with friction sets of bodies using
unsymmetric stiffness friction matrices.
Main Index
1302 BSQUEAL
Specifies Data for Brake Squeal Analysis Using SOL 400
2. The disks should not be glued with pads. When bodies are intended to be glued, turn on BCTABLE
/ IGLUE or BCONPRG/IGLUE for those contact bodies.
3. Brake squeal is not available with segment-to-segment contact.
4. For nonlinear static analysis, 0.0 < OMETH < 1.0, OMETH is overridden by the load factor from
Case Control command, NLIC or its default, when a brake squeal analysis is performed in a separate
SUBCASE-STEP other than ANALYSIS = NLSTATIC.
5. User subroutine UBSQUEAL is available using the BCONUDS entry.
Main Index
BSURF 1303
Contact Body or Surface
BSURF Contact Body or Surface
Defines a contact body or surface by Element IDs.
Format:
1 2 3 4 5 6 7 8 9 10
BSURF ID ELID1 ELID2 ELID3 ELID4 ELID5 ELID6 ELID7
ELID8 ELID9 etc.
Alternate Format:
BSURF ID ELID1 THRU ELID2 BY INC
ELID3 THRU ELID4 BY INC2
Example:
BSURF 15 5 THRU 21 BY 4
27 30 32 33
35 THRU 44
67 68 72 75 84 93
Describer Meaning
ID Identification of a deformable surface corresponding to a BSID value on the BCBODY
entry. See Remark 2. (Integer > 0)
ELIDi Element identification numbers. If the curve or surface is defined with element ids
only, the direction of the normal depends on the grid point numbering. Keywords
THRU and BY can be used to assist the listing. For SOL 700 the Alternate Format
must be used with Remarks 6. and 7.
INC Identification number increment. See Remark 3. (Integer or blank)
Remarks:
1. BSURF can be used in SOL101, 103, 105, 107, 108, 109, 110, 111, 112, 400 and 700.
2. ID must be unique with respect to all other BSURF, BCBOX, BCPROP, and BCMATL entries.
3. For automatic generation of element IDs, the default increment value is 1 if element numbers are
increasing or -1 if element numbers are decreasing (i.e., the user need not specify BY and the
increment value).
4. The deformable surface may alternately be defined using BCBOX, BCPROP, or BCMATL entries.
5. Only one kind of entry (BSURF, BCBOX, BCPROP, or BCMATL) may be used to define a
particular deformable surface.
Main Index
1304 BSURF
Contact Body or Surface
6. For SOL 700, Format 1 and the Alternate Format cannot be mixed for a particular BSURF entry.
7. For SOL 700 if the Alternate Format is used, THRU must be in column 4 for entries with the BSURF
header and in column 3 for continuation entries. If BY is not used, columns 6-9 of the BSURF entry
and columns 5-9 of continuation entries must be blank.
Main Index
BWIDTH 1305
Boundary Line Segment Width or Thickness
BWIDTH Boundary Line Segment Width or Thickness
Defines widths or thicknesses for line segments in 3-D or 2-D slideline contact defined in the corresponding
BLSEG Bulk Data entry for SOL 106 or SOL 129. SOL 400 general contact capability, defined with
BCONTACT, BCTABL1, etc. is the recommended approach for contact analysis.
Format:
1 2 3 4 5 6 7 8 9 10
BWIDTH ID W1 W2 W3 W4 W5 W6 W7
Alternate Format:
BWIDTH ID W1 “THRU” W2 “BY” INC
The continuation entry formats may be used more than once and in any order. They may also be used with
either format above.
Continuation Entry Format 1:
W8 W9 W10 W11 -etc.-
Continuation Entry Format 2:
W8 “THRU” W9 “BY” INC
Example:
BWIDTH 15 2.0 THRU 5.0 BY 1.0
2.0 2.0 2.0 2.0
35. THRU 44.
1.5 3.4 7.6 0.4 0.7
Describer Meaning
ID BLSEG entry identification number. (Integer > 0)
Wi Width values for the corresponding line segments defined in the BLSEG entry. See
Remark 1. (Real > 0.0)
INC Width value increment. See Remark 2. (Real or blank)
Remarks:
1. BWIDTH may be omitted if the width of each segment defined in the BLSEG entry is unity. The
number of widths to be specified is equal to the number of segments defined in the corresponding
BLSEG entry.
Main Index
1306 BWIDTH
Boundary Line Segment Width or Thickness
2. The default value for INC is 1.0 if the width is increasing or -1.0 if the width is decreasing. That is,
the user need not specify BY and the increment value. If the number of widths specified is less than
the number of segments defined in the corresponding BLSEG entry, the width for the remaining
segments is assumed to be equal to the last width specified.
3. If there is only one grid point in the corresponding BLSEG entry, there is no contributory area
associated with the grid point. To compute correct contact stresses an area may be associated with the
single grid point by specifying the area in field W1.
Main Index
CAABSF 1307
Frequency-Dependent Acoustic Absorber Element
Entries CA - CM
CAABSF Frequency-Dependent Acoustic Absorber Element
Defines a frequency-dependent acoustic absorber element in coupled fluid-structural analysis.
Format:
1 2 3 4 5 6 7 8 9 10
CAABSF EID PID G1 G2 G3 G4
Example:
CAABSF 44 38 1 10 20
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number that matches a PAABSF entry. (Integer > 0;
Default = EID)
Gi Grid point identification number of fluid connection points. (Integer > 0 or blank)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. If only G1 is specified then a point impedance is assumed. If G1 and G2 are specified then a line
impedance is assumed. If G1, G2, and G3 are specified, then an impedance is associated with the area
of the triangular face. If G1 through G4 are specified, then an impedance is associated with the
quadrilateral face. See Figure 9-4.
3. The CAABSF element must connect entirely to fluid points on the fluid-structure boundary.
4. This element is used only in frequency response and is ignored in all other solutions.
Main Index
1308 CAABSF
Frequency-Dependent Acoustic Absorber Element
G2 G3
G1
G2
G1 G4
G1
G1
G3
G2
Figure 9-4 Four Types of CAABSF Elements
Main Index
CACINF3 1309
Acoustic Conjugate Infinite Element Base Connection
CACINF3 Acoustic Conjugate Infinite Element Base Connection
Defines an acoustic conjugate infinite element with triangular base.
Format:
1 2 3 4 5 6 7 8 9 10
CACINF3 EID PID G1 G2 G3
Example:
CACINF3 111 10 1004 1008 1011
Describer Meaning
EID Element Identification Number. (0 < Integer < 100,000,000)
PID Property Identification Number of a PACINF entry. (Integer > 0)
Gi Grid Point Identification Numbers of Element Base Connection Points. (Integer > 0)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. The element must be connected to acoustic grid points.
3. The element normal is defined by the right-hand rule. If the normal does not point into the exterior
domain, the element orientation will be changed automatically, and an information message will be
written to the .f06 file.
4. Bulk Data entry, ACIFPRM, can be used to adjust some parameters related to infinite elements and
acoustic field point mesh
Main Index
1310 CACINF4
Acoustic Conjugate Infinite Element Base Connection
CACINF4 Acoustic Conjugate Infinite Element Base Connection
Defines an acoustic conjugate infinite element with quadrilateral base.
Format:
1 2 3 4 5 6 7 8 9 10
CACINF4 EID PID G1 G2 G3 G4
Example:
CACINF4 275 10 1027 1032 1056 1021
Describer Meaning
EID Element Identification Number. (0 < Integer < 100,000,000)
PID Property Identification Number of a PACINF entry. (Integer > 0)
Gi Grid Point Identification Numbers of Element Base Connection Points. (Integer > 0)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. The element must be connected to acoustic grid points.
3. The element normal is defined by the right-hand rule. If the normal does not point into the exterior
domain, the element orientation will be changed automatically, and an information message will be
written to the .f06 file.
4. Bulk Data entry, ACIFPRM, can be used to adjust some parameters related to infinite elements and
acoustic field point mesh.
Main Index
CAERO1 1311
Aerodynamic Panel Element Connection
CAERO1 Aerodynamic Panel Element Connection
Defines an aerodynamic macro element (panel) in terms of two leading edge locations and side chords. This
is used for Doublet-Lattice theory for subsonic aerodynamics and the ZONA51 theory for supersonic
aerodynamics.
Format:
1 2 3 4 5 6 7 8 9 10
CAERO1 EID PID CP NSPAN NCHORD LSPAN LCHORD IGID
X1 Y1 Z1 X12 X4 Y4 Z4 X43
Example:
CAERO1 1000 1 3 2 1
0.0 0.0 0.0 1.0 0.2 1.0 0.0 0.8
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PAERO1 entry; used to specify associated bodies.
Required even if there are no associated bodies. (Integer > 0)
CP Coordinate system for locating points 1 and 4. (Integer > 0; Default = 0)
NSPAN Number of spanwise boxes; if a positive value is given NSPAN, equal divisions are
assumed; if zero or blank, a list of division points is given at LSPAN, field 7.
(Integer > 0)
NCHORD Number of chordwise boxes; if a positive value is given NCHORD, equal divisions are
assumed; if zero or blank, a list of division points is given at LCHORD, field 8.
(Integer > 0)
LSPAN ID of an AEFACT entry containing a list of division points for spanwise boxes. Used
only if NSPAN, field 5 is zero or blank. (Integer > 0)
LCHORD ID of an AEFACT data entry containing a list of division points for chordwise boxes.
Used only if NCHORD, field 6 is zero or blank. (Integer > 0)
IGID Interference group identification; aerodynamic elements with different IGIDs are
uncoupled. (Integer > 0)
X1, Y1, Z1 Location of points 1 and 4, in coordinate system CP. (Real)
X4, Y4, Z4
X12, X43 Edge chord lengths in aerodynamic coordinate system. (Real > 0.0, but not both zero.)
Main Index
1312 CAERO1
Aerodynamic Panel Element Connection
Remarks:
1. The boxes and corner point nodes are numbered sequentially, beginning with EID. The user should
be careful to ensure that all box and corner point node numbers are unique. There can be overlapping
IDs between the structural and aerodynamic model, but MSC Patran will not then be able to display
any results. Also, non-unique corner IDs are allowed, but results cannot be visualized in MSC Patran.
2. The number of division points is one greater than the number of boxes. Thus, if NSPAN=3, the
division points are 0.0, 0.333, 0.667, 1.000. If the user supplies division points, the first and last
points need not be 0. and 1. (In which case the corners of the panel would not be at the reference
points.)
3. A triangular element is formed if X12 or X43=0.0
4. The element coordinate system is right-handed as shown in Figure 9-5.
5. The continuation is required.
6. It is recommended that NCHORD or LCHORD be chosen so that the typical box chord length x
satisfies the conditio x 0.08 V f (recent studies indicate that .02 V f is needed to get
converged stability derivatives) where V is the minimum velocity and f, in hertz, is the maximum
frequency to be analyzed (see the MSC Nastran Aeroelastic Analysis User’s Guide).
Zelem
1 Yelem
1000
1003
4
1001 1006
1004
1007
1002 1005 1008
2 3
Xaero = Xelem
Figure 9-5 Element Coordinate System for Aerodynamic Panel
7. This entry can be used for two different aerodynamic theories: Doublet-Lattice for subsonic and
ZONA51 for supersonic. The proper theory is selected based on the specification of Mach number
on the MKAEROi or TRIM entry.
Main Index
CAERO2 1313
Aerodynamic Body Connection
CAERO2 Aerodynamic Body Connection
Defines aerodynamic slender body and interference elements for Doublet-Lattice aerodynamics.
Format:
1 2 3 4 5 6 7 8 9 10
CAERO2 EID PID CP NSB NINT LSB LINT IGID
X1 Y1 Z1 X12
Example:
CAERO2 1500 2 100 4 99 1
-1.0 100. -30. 175.
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PAERO2 entry. (Integer > 0)
CP Coordinate system for locating point 1. (Integer > 0; Default = 0)
NSB Number of slender body elements. If NSB > 0, then NSB equal divisions are assumed;
if zero or blank, specify a list of divisions in LSB. (Integer > 0)
NINT Number of interference elements. If NINT > 0, then NINT equal divisions are
assumed; if zero or blank, specify a list of divisions in LINT. (Integer > 0)
LSB ID of an AEFACT Bulk Data entry for slender body division points; used only if NSB
is zero or blank. (Integer > 0)
LINT ID of an AEFACT data entry containing a list of division points for interference
elements; used only if NINT is zero or blank. (Integer > 0)
IGID Interference group identification. Aerodynamic elements with different IGIDs are
uncoupled. (Integer > 0)
X1, Y1, Z1 Location of point 1 in coordinate system CP. (Real)
X12 Length of body in the x-direction of the aerodynamic coordinate system. (Real > 0.0)
Remarks:
1. Point 1 is the leading point of the body.
2. All CAERO1 (panels) and CAERO2 (bodies) in the same group (IGID) will have aerodynamic
interaction.
3. At least one interference element is required for the aerodynamic body specified by this entry.
Main Index
1314 CAERO2
Aerodynamic Body Connection
4. The beams and connection points are numbered sequentially beginning with EID. The user should
be careful to ensure that all aero elements and connection point IDs are unique. Overlapping IDs
between structure and aerodynamic models are allowed, but will prevent results visualization in
Patran.
Old rules regarding numbering among Z, ZY, Y bodies and CAERO1 no longer apply: arbitrary
ordering is allowed.
5. At least two slender body elements are required for each aerodynamic body.
6. Interference elements are only intended for use with panels.
7. Determining the size of the j-set (i.e., the number of aerodynamic elements) is essential to input D1JE
and D2JE matrices. Use the following expressions for locating the proper row in the two matrices:
J=Number of boxes+ Number of I-elements, z
+ 2*(Number of I-elements, zy)
+ Number of I-elements, y
+ Number of S-elements, z
+ 2*(Number of S-elements, zy)
+ Number of S-elements, y
where I-elements denote interference and S-elements denote slender body.
Main Index
CAERO3 1315
Aerodynamic Panel Element Configuration
CAERO3 Aerodynamic Panel Element Configuration
Defines the aerodynamic edges of a Mach Box lifting surface. If no cranks are present, this entry defines the
aerodynamic Mach Box lifting surface.
Format:
1 2 3 4 5 6 7 8 9 10
CAERO3 EID PID CP LISTW LISTC1 LISTC2
X1 Y1 Z1 X12 X4 Y4 Z4 X43
Example:
CAERO3 2000 2001 0 22 33
1.0 0.0 0.0 100. 17. 130. 0. 100.
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PAERO3 entry. (Integer > 0)
CP Coordinate system for locating points 1 and 4. (Integer > 0; Default = 0)
LISTW Identification number of an AEFACT entry that lists (x,y) pairs for structural
interpolation of the wing. (Integer > 0)
LISTC1, Identification number of AEFACT entries that list (x,y) pairs for control surfaces, if they
LISTC2 exist. (Integer > 0)
X1, Y1, Z1 Location of points 1 and 4 in coordinate system CP. (Real)
X4, Y4, Z4
X12, X43 Edge chord lengths in the aerodynamic coordinate system. (Real > 0, X12 0 )
Remarks:
1. EID must be unique with respect to all other element identification numbers.
2. The (x,y) pairs on LISTW, LISTC1 and LISTC2 AEFACT entries are in the aero element coordinate
system (see Figure 9-6). The (x,y) pairs define a set of aerodynamic grid points that are independent
of Mach number and are selected by the user to be representative of the planform and motions of
interest. The (x,y) pairs must be sufficient in number and distribution such that: the surface spline
provides an accurate interpolation between them and the Mach Box centers that are variously located
on the planform as a function of Mach number (a complete description of the Mach Box Method is
given in the MSC Nastran Aeroelastic Analysis User’s Guide).
Main Index
1316 CAERO3
Aerodynamic Panel Element Configuration
3. The (x,y) pairs are numbered sequentially, beginning with EID for LISTW, then LISTC1, and finally
for LISTC2. On SPLINEi entries, the box numbers (BOX1 and BOX2 on SPLINE1, ID1 and ID2
on SPLINE2, and UKID on SPLINE3) refer to the (x,y) pair sequence number appropriate for the
surface (primary, or first or second control) being splined.
4. If cranks and/or control surfaces exist, their locations are given on the PAERO3 entry.
5. The numbering system and coordinate system are shown below:
zelem yelem
1 5
4
+ +
LISTW
+ grid points
+
7 +
9 11
2 8 +
+ + + 3
+ 10 + +
12
6
xaero = xelem
LISTC1 grid points
Figure 9-6 CAERO3 Element Configuration
Planform Corners Control
1 Leading edge, inboard 7 Hinge line, inboard
2 Trailing edge, inboard 8 On inboard edge (usually at trailing edge)
3 Trailing edge, outboard 9 Hinge line, outboard
4 Leading edge, outboard 10 On outboard edge (usually at trailing edge)
Cranks Control (if two)
5 Leading edge 9 Hinge line, inboard
6 Trailing edge 10 On inboard edge (usually at trailing edge)
11 Hinge line, outboard
12 On outboard edge (usually at trailing edge)
6. The CAERO3 entry is only supported in SOL 145, SOL 200 with ANALYSIS=FLUT and in
SOL 146 with mechanical loads. Gust response in SOL 146 is not supported for the CAERO3.
Main Index
CAERO4 1317
Aerodynamic Macro-Strip Element Connection
CAERO4 Aerodynamic Macro-Strip Element Connection
Defines an aerodynamic macro element for Strip theory.
Format:
1 2 3 4 5 6 7 8 9 10
CAERO4 EID PID CP NSPAN LSPAN
X1 Y1 Z1 X12 X4 Y4 Z4 X43
Example:
CAERO4 6000 6001 100 315
0.0 0.0 0.0 1.0 0.2 1.0 0.0 0.8
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PAERO4 entry. (Integer > 0)
CP Coordinate system for locating points 1 and 4. (Integer > 0; Default = 0)
NSPAN Number of strips; if a positive value is given, NSPAN equal strips are assumed. If zero
or blank, LSPAN must be specified. (Integer > 0)
LSPAN ID of an AEFACT entry containing a list of division points for strips. Used only if
NSPAN is zero or blank. (Integer > 0)
X1, Y1, Z1 Location of points 1 and 4 in coordinate system CP. (Real)
X4, Y4, Z4
X12, X43 Edge chord lengths in aerodynamic coordinate system. (Real > 0.0, and not both zero.)
Remarks:
1. The strips are numbered sequentially, beginning with EID. The user must ensure that all strip
numbers are unique and greater than structural grid, scalar, and extra point IDs.
2. The number of division points is one greater than the number of boxes. Thus, if NSPAN = 3, the
division points are 0.0, 0.333, 0.667, and 1.000. If the user supplies division points, the first and last
points need not be 0.0 and 1.0 (in which case the corners of the panel would not be at the reference
points).
3. A triangular element is formed if X12 or X43 = 0.
Main Index
1318 CAERO4
Aerodynamic Macro-Strip Element Connection
zelem
1 yelem
xaero = xelem
Figure 9-7 CAERO4 Element Connection
4. The CAERO4 entry is only supported in SOL 145, SOL 200 with ANALYSIS=FLUT and in
SOL 146 with mechanical loads. Gust response in SOL 146 is not supported for the CAERO4.
Main Index
CAERO5 1319
Aerodynamic Panel Element Configuration
CAERO5 Aerodynamic Panel Element Configuration
Defines an aerodynamic macro element for Piston theory.
Format:
1 2 3 4 5 6 7 8 9 10
CAERO5 EID PID CP NSPAN LSPAN NTHRY NTHICK
X1 Y1 Z1 X12 X4 Y4 Z4 X43
Example:
CAERO5 6000 6001 100 315 0 0
0.0 0.0 0.0 1.0 0.2 1.0 0. 0.8
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PAERO5 entry. (Integer > 0)
CP Coordinate system for locating points 1 and 4. (Integer > 0; Default = 0)
NSPAN Number of strips. (Integer. If a positive value is given, equal strips are assumed. If zero
or blank, then LSPAN must be specified.)
LSPAN ID of an AEFACT entry containing a list of division points for strips. Used only if
NSPAN is zero or blank. (Integer > 0)
NTHRY Parameter to select Piston or van Dyke’s theory. (Integer = 0, 1, or 2; Default = 0)
Blank or 0 Piston theory is used to compute C 1 and C 2
1 van Dyke’s theory is used to compute C 1 and C 2 with no sweep
correction (sec .
2 van Dyke’s theory is used to compute C 1 and C 2 with a sweep
correction based on the actual .
NTHICK Parameter to select thickness integrals input. (Integer > 0; Default = 0)
Blank or 0 Thickness integrals are computed internally.
>0 Thickness integrals are input directly and are the ID number of an
AEFACT entry that lists the I and/or J integrals.
X1,Y1, Z1 Location of points 1 and 4 in coordinate system CP. (Real)
X4,Y4, Z4
X12, X43 Edge chord lengths in aerodynamic coordinate system. (Real > 0; X12 and X43 cannot
both be zero.)
Main Index
1320 CAERO5
Aerodynamic Panel Element Configuration
zelem
1 yelem
4
3
2
xaero = xelem
Figure 9-8 CAERO5 Element Configuration
Remarks:
1. The strips are numbered sequentially, beginning with EID. The user must ensure that all strip
numbers are unique and different from structural grid IDs.
2. The number of division points is one greater than the number of boxes. Thus, if NSPAN=3, the
division points are 0.0, 0.333, 0.667, 1.000. If the user supplies division points, the first and last
points need not be 0.0 and 1.0 (in which case the corners of the panel would not be at the reference
points).
3. A triangular element is formed if X12 or X43 = 0.0.
2 2 12
C 1 = m m – sec
4.
4 2 2 2 2 2 2
C 2 = m + 1 – 4 sec m – sec 4 m – sec
where:
m = Mach number
= Specific heat ratio
= Leading edge sweep angle
Main Index
CAERO5 1321
Aerodynamic Panel Element Configuration
When sec = 0.0 , Piston theory coefficients are obtained (NTHRY = 1)
When sec = 1.0 , van Dyke’s coefficients are obtained (NTHRY = blank or 0)
When sec 0.0 or 1.0, sweep corrections are included (NTHRY = 2)
5. I and J thickness integral definitions:
2
g 2 h 2 Hinge Line
t 2
m
h
= 1
dg
g ------ = slope of airfoil semithickness
d
1 1
I1 = g d J1 = g d
0 h
1 1
I2 = g d J2 = g d
0 h
1 1
2 2
I3 = g d J3 = g d
0 h
1 1
2 2
I4 = g d J4 = g d
0 h
Main Index
1322 CAERO5
Aerodynamic Panel Element Configuration
1 1
2 2
I5 = g d J5 = g d
0 h
1 1
2 2 2 2
I6 = g d J6 = g d
0 h
Figure 9-9 CAERO5 I and J Thickness Integral Definitions
6. The CAERO5 entry is only supported in SOL 145, SOL 200 with ANALYSIS=FLUT and in
SOL 146 with mechanical loads. Gust response in SOL 146 is not supported for the CAERO5.
Main Index
CAMPBLL 1323
Campbell Diagram Parameters
CAMPBLL Campbell Diagram Parameters
Specifies the parameters for Campbell Diagram generation and mode tracking analysis.
Formats:
1 2 3 4 5 6 7 8 9 10
CAMPBLL CID VPARM DDVALID TYPE
MODTRK CORU SWITR NUMMOD PRTCOR
Examples:
CAMPBLL 15 SPEED 22 RPM
1 0.75 1 1
Describer Meaning
CID Identification number of entry (Integer > 0; Required).
VPARM Variable parameter, allowable entry is: ‘SPEED’.
‘SPEED’, reference rotor speed will be varied (rotordynamic option only).
DDVALID Identification number of DDVAL entry that specifies the values for the variable
parameter (Integer > 0; Required).
TYPE Allowable entries are: ‘FREQ’ and ‘RPM’.
MODTRK Perform mode tracking using either numerical approach (default) or eigenvector based
approach or both. (Default = 0). See remark 4.
CORU Threshold for mode correlation.
SWITR Option to use updated mode for mode tracking in case of failure. See remark 7.
NUMMODE Number of modes to track (Should be less than 0.5*Neig, where Neig is the number
of eigenvalues extracted in EIGC). See remark 4.
PRTCOR Option to print correlation matrix at each rotor speed (Default = 0). See remark 9.
Remarks:
1. CAMPBLL option is supported for SOL 107, SOL110, SOL200 and SOL400 analysis.
2. CAMPBLL option is supported in SOL 200 and SOL 400 for ANALYSIS = DCEIG/MCEIG.
3. Only the modes with positive imaginary part are used for mode tracking (to avoid repeated
eigenvalues.)
4. Following methods are available in MSC Nastran for mode tracking:
a. Numerical Mode tracking based on second derivative.
Obtain second derivative for the variation of eigenvalue with rotor speed and determine the
eigenfrequency with minimum slope.
Main Index
1324 CAMPBLL
Campbell Diagram Parameters
b. Mode tracking based on orthogonality of left and right eigenvectors.
This feature is available for analysis in fixed reference frame only.
MODTRK = 0: Perform numerical mode tracking only. (Default)
MODTRK = 1: Perform BOTH numerical and eigenvector based mode tracking.
MODTRK = 2: Perform eigenvector based mode tracking only.
5. The variables specified in the second row are relevant for eigenvector-based mode tracking only.
6. Ideally, for tracked pair of modes, the value of Normalized Cross Complex Orthogonality (NC2O)
parameter is very close to 1. However, for complex models involving large stator component and
dynamic reduction, this value can be significantly lower. Thus, the default value for CORU is set to
0.7. Based on the model complexity and NC2O matrix obtained for two rotor speeds, user may
change this value.
7. In case of mode tracking failure at a particular rotor speed, user has the option to continue mode
tracking for rest of the rotors speed by:
SWITR = 1: Updating modes corresponding to rotor speed with failed mode tracking, or
SWITR = 0: Using the modes from last rotor speed with successful mode tracking. (Default)
In case the Campbell diagram includes multiple mode switching and there are new modes entering
the analysis, use of SWITR=1 is recommended.
8. Only the complex eigenvalues with positive imaginary part are considered for mode tracking analysis.
As a result, the number of eigenvalues available for mode tracking may not be same at all the rotor
speeds considered in the analysis. This may lead to mode tracking failure. One way to avoid this issue
is to pick NUMMODE to be less than half of the number of complex eigenvalues extracted using
EIGC bulk data entry. Thus, the analysis uses only the first NUMMODE frequencies with positive
imaginary part for mode tracking at each rotor speed.
9. When PRTCOR parameter is turned to 1, the code prints NC2O matrix corresponding to each rotor
speed in the F06 file. This information can be very useful in identifying reasons for mode tracking
failure.
10. For both approaches, damping ratio is also tracked while tracking eigenfrequencies. The results
produced from mode tracking can be extracted in OP4 using following assign statements:
$ Extract results for numerical mode tracking
ASSIGN OUTPUT4='freq_nmt.op4',UNIT=71,FORM=FORMATTED,DELETE $ MODE FREQS
ASSIGN OUTPUT4='rot_nmt.op4',UNIT=72,FORM=FORMATTED,DELETE $ ROTOR SPEED
ASSIGN OUTPUT4='dmp_nmt.op4',UNIT=73,FORM=FORMATTED,DELETE $ DAMPING RATIO
$ Extract results for eigenvector based mode tracking
ASSIGN OUTPUT4='freq_evmt.op4',UNIT=81,FORM=FORMATTED,DELETE $ MODE FREQS
ASSIGN OUTPUT4='rot_evmt.op4',UNIT=82,FORM=FORMATTED,DELETE $ ROTOR SPEED
ASSIGN OUTPUT4='dmp_evmt.op4',UNIT=83,FORM=FORMATTED,DELETE $ DAMPING RATIO
These OP4 files can be imported in MSC PATRAN to produce Campbell Diagram.
11. DMP>1 is not supported for SOL 110 for generating Campbell diagram when ACMS option is not
used.
12. For Campbell diagram, the selected RGYRO Bulk Data entry must have the ASYNC option specified
in its SYNCFLG field. Otherwise, the program terminates the execution with an appropriate fatal
message.
Main Index
CAXIFi 1325
Fluid Element Connections
CAXIFi Fluid Element Connections
Defines an axisymmetric fluid element that connects i = 2, 3, or 4 fluid points.
Formats:
1 2 3 4 5 6 7 8 9 10
CAXIF2 EID IDF1 IDF2 RHO B
CAXIF3 EID IDF1 IDF2 IDF3 RHO B
CAXIF4 EID IDF1 IDF2 IDF3 IDF4 RHO B
Examples:
CAXIF2 11 23 25 0.25E-3
CAXIF3 105 31 32 33 6.47E-3
CAXIF4 524 421 425 424 422 0.5E-3 2.5+3
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
IDFi Identification numbers of connected GRIDF points. (Integer > 0)
RHO Fluid density in mass units. (Real > 0.0 or blank)
B Fluid bulk modulus. (Real > 0.0 or blank)
Remarks:
1. CAXIFi is allowed only if an AXSLOT entry is also present.
2. The element identification number (EID) must be unique with respect to all other fluid or structural
elements.
3. If RHO or B is blank, then the corresponding RHOD and BD fields must be specified on the
AXSLOT entry.
4. Plot elements are generated for these elements. Because each plot element connects two points, one
is generated for the CAXIF2 element, three are generated for the CAXIF3 element, and four plot
elements are generated for the CAXIF4 element. In the last case the elements connect the pairs of
points (1-2), (2-3), (3-4), and (4-1).
5. If B = 0.0, the fluid is incompressible.
Main Index
1326 CAXISYM
Axisymmetric Line Elements Connection - SOL 400
CAXISYM Axisymmetric Line Elements Connection - SOL 400
Defines two or three node axisymmetric thick shell elements.
Formats:
1 2 3 4 5 6 7 8 9 10
CAXISYM EID PID G1 G2 G3 NOFF
Example:
CAXISYM 22 98 8 16
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of PAXISYM entry. (Integers > 0)
G1, G2 Identification numbers at the two end grid points. Required data.
(Unique; Integers > 0)
G3 Identification number of the one grid in between G1 and G2. See Remark 2. (Unique
Integer > 0 or blank). If G3=0; this is a straight two node element.
NOFF Offset from the surface of the grid points to the element reference plane. (Real)
Remarks:
1. Element identification numbers should be unique with respect to all other identification numbers.
2. It is recommended that G3 be located within the middle third of the element.
3. The element must lie in the x-y plane of the basic system and is oriented as shown below.
Main Index
CAXISYM 1327
Axisymmetric Line Elements Connection - SOL 400
Z-element
Y-basic
G2
n
G3
G1
X-basic
-element R-element
Main Index
1328 CBAR
Simple Beam Element Connection
CBAR Simple Beam Element Connection
Defines a simple beam element.
Format:
1 2 3 4 5 6 7 8 9 10
CBAR EID PID GA GB X1 X2 X3 OFFT
PA PB W1A W2A W3A W1B W2B W3B
Example:
CBAR 2 39 7 3 0.6 18. 26. GOG
513
Alternate Format and Example:
CBAR EID PID GA GB G0 OFFT
PA PB W1A W2A W3A W1B W2B W3B
CBAR 2 39 7 6 105 GOG
513
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PBAR, PBARL or PBRSECT entry.
(Integer > 0 or blank*; Default = EID unless BAROR entry has nonzero entry in
field 3.)
GA, GB Grid point identification numbers of connection points. (Integer > 0;
GA GB )
X1, X2, X3 Components of orientation vector v , from GA, in the displacement coordinate
system at GA (Default), or in the basic coordinate system. See Remark 7. (Real)
G0 Alternate method to supply the orientation vector v using grid point G0. The
direction of v is from GA to G0. v is then translated to End A. (Integer > 0;
G0 GA or GB)
OFFT Offset vector interpretation flag. (character or blank) See Remark 7.
Main Index
CBAR 1329
Simple Beam Element Connection
Describer Meaning
PA, PB Pin flags for bar ends A and B, respectively. Used to remove connections between
the grid point and selected degrees-of-freedom of the bar. The degrees-of-
freedom are defined in the element’s coordinate system (see Figure 9-10). The bar
must have stiffness associated with the PA and PB degrees-of-freedom to be
released by the pin flags. For example, if PA = 4 is specified, the PBAR entry
must have a value for J, the torsional stiffness. (Up to 5 of the unique Integers 1
through 6 anywhere in the field with no embedded blanks; Integer > 0.) Pin flags
are not allowed in SOL 700.
Components of offset vectors w a and w b , respectively (see Figure 9-10) in
W1A,W2A, W3A displacement coordinate systems (or in element system depending upon the
W1B,W2B,W3B content of the OFFT field), at points GA and GB, respectively. See Remark 6.
and 7. (Real; Default = 0.0) Offsets are not allowed in SOL 700.
*See the BAROR entry for default options for field 3 and fields 6 through 9.
Remarks:
1. Figure 9-10 and Figure 9-11 define bar element geometry with and without offsets:
x elem
v
Plane 1
y elem End b
v wb
Grid Point GB
Plane 2
End a
z elem
wa
Grid Point GA
Figure 9-10 CBAR Element Geometry with Offsets
Main Index
1330 CBAR
Simple Beam Element Connection
v x elem
Plane 1
y elem End b
GB
Plane 2
End a
GA z elem
Figure 9-11 CBAR Element Geometry without Offsets
2. Figure 9-12 and Figure 9-13 define the elemental force and moment sign convention.
y v1
M 1a M 1b
T
x
Fx T
a Plane 1 b
v1
Figure 9-12 CBAR Element Internal Forces and Moments (x-y Plane)
z v2
M 2a M 2b
x
Plane 2
v2
Figure 9-13 CBAR Element Internal Forces and Moments (x-z Plane)
3. The continuation may be omitted if there are no pin flags or offsets.
4. For the case where field 9 is blank and not provided by the BAROR entry, if an integer is specified in
field 6, then G0 is used; if field 6 is blank or real, then X1, X2, X3 is used.
Main Index
CBAR 1331
Simple Beam Element Connection
5. See Grid Point and Coordinate System Definition in the MSC Nastran Reference Guide for a definition of
coordinate system terminology.
6. Offset vectors are treated internally like rigid elements. For solution sequences that require differential
stiffness such as SOL103 (with preloading), SOL105, and SOL400, the user is required to use
MDLPRM, OFFDEF, LROFF.
• Two methods are available for the computation of offsets: original and enhanced. The default
method is the original method. The enhanced method is requested by the Bulk Data entry
MDLPRM,OFFDEF,LROFF. For options of offsets, please refer to the Bulk Data entry
MDLPRM,OFFDEF,option.
• The length of offset vectors is not affected by thermal loads. But the thermal load changes due to
location changes by offsets are correctly computed if the enhanced method is used.
• BAR elements with offsets will give correct buckling results if the enhanced method is used.
• Masses are correctly transformed for offset effects if MDLPRM, OFFDEF, LROFF is used. In
SOL103, if the case control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is
present, then MDLPRM, OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF,
NOMASS.
• In nonlinear solution sequences, such as SOL 106 or SOL 400, BAR is treated as linear element.
If geometric nonlinear effects are required, please use Bulk Data entry MDLPRM,BRTOBM,1
to convert BAR to BEAM.
7. OFFT is a character string code that describes how the offset and orientation vector components are
to be interpreted. By default (string input is GGG or blank), the offset vectors are measured in the
displacement coordinate systems at grid points A and B and the orientation vector is measured in the
displacement coordinate system of grid point A. At user option, the offset vectors can be measured in
an offset coordinate system relative to grid points A and B, and the orientation vector can be measured
in the basic system as indicated in the following table:
String Orientation Vector End A Offset End B Offset
GGG Global Global Global
BGG Basic Global Global
GGO Global Global Offset
BGO Basic Global Offset
GOG Global Offset Global
BOG Basic Offset Global
GOO Global Offset Offset
BOO Basic Offset Offset
Main Index
1332 CBAR
Simple Beam Element Connection
Any attempt to specify invalid combinations results in a bulk data entry input error message. For
example, a value of OOO (indicating offset and orientation vectors are specified in an offset reference
system) results in a fatal error since the orientation vector cannot be specified in an offset system. The
offset system x-axis is defined from GA to GB. The orientation vector v and the offset system x-axis
are then used to define the z and y axes of the offset system. A vector is formed from a cross product
of a vector going from Grid A to Grid B and the orientation vector to create the offset coordinate z-
direction. To obtain a nonzero cross product the orientation vector must not be parallel to both
vectors from Grid A to Grid B for the offset coordinate system and End A and End B for the element
coordinate system. (Note: The character “O” in the table replaces the obsolete character “E”.)
8. For SOL 700, the OFFT field is ignored and a warning is issued.
Main Index
CBARAO 1333
Auxiliary Output Points Along Bar Element Axis (CBAR Entry)
CBARAO Auxiliary Output Points Along Bar Element Axis (CBAR Entry)
Defines a series of points along the axis of a bar element (CBAR entry) for stress and force recovery output.
This entry is applicable in static and normal modes analysis only.
Format:
1 2 3 4 5 6 7 8 9 10
CBARAO EID SCALE X1 X2 X3 X4 X5 X6
Example:
CBARAO 1065 FR 0.2 0.4 0.6 0.8
Alternate Format and Example:
CBARAO EID SCALE NPTS X1 DELTAX
CBARAO 1065 FR 4 0.2 0.2
Describer Meaning
EID Element identification of a CBAR entry. (0 < Integer < 100,000,000)
SCALE Defines scale of Xi values. (Character = “LE” or “FR”)
Xi Series of locations along element axis for stress and force data recovery. (Real > 0.0)
DELTAX Incremental distance along element axis. (Real)
NPTS Number of stress recovery points, not including the end points. (Integer > 0)
Remarks:
1. This entry defines intermediate locations on the axis of selected CBAR elements for additional data
recovery. The values of Xi are actual distances along the length if SCALE = “LE”. If SCALE = “FR”,
the values of Xi are ratios of actual distances to the bar length. A PLOAD1 Bulk Data entry for the
CBAR element in question must be present to obtain intermediate data recovery.
2. When the alternate format is used, a series of locations Xi = X[i-1]+DELTAX, i = 1, 2, ..., NPTS is
generated.
3. If a CBARAO or PLOAD1 entry is specified and stress and/or force output is requested, then the
stresses and/or forces will be calculated at each location Xi and output as a separate line. The force
and stress values at the end points of the beam will always be output. This output format will be used
for all beam and bar elements.
4. Intermediate loads on the element defined by the PLOAD1 entry will be accounted for in the
calculation of element stresses and forces. If no PLOAD1 entry is defined for the element, the shear
forces are constant, the moments are linear, and it is not necessary that the user define additional
points.
Main Index
1334 CBARAO
Auxiliary Output Points Along Bar Element Axis (CBAR Entry)
5. For each bar element, either the basic format or the alternate format, but not both, may be used. A
maximum of six internal points can be specified with the basic form. The end points must not be
listed because data will be generated for them, as explained in Remark 3. If more than six unequally
spaced internal points are desired, it is advisable to subdivide the bar into two or more elements.
Main Index
CBEAM 1335
Beam Element Connection
CBEAM Beam Element Connection
Defines a beam element.
Format:
1 2 3 4 5 6 7 8 9 10
CBEAM EID PID GA GB X1 X2 X3 OFFT
PA PB W1A W2A W3A W1B W2B W3B
SA SB
Example:
CBEAM 2 39 7 13 8.2 6.1 -5.6 GOG
513 3.0
8 5
Alternate Format and Example:
CBEAM EID PID GA GB G0 OFFT
PA PB W1A W2A W3A W1B W2B W3B
SA SB
CBEAM 2 39 7 13 105 GOG
513
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of PBEAM, PBCOMP, PBEAML or PBMSECT
entry. (Integer > 0; Default = EID)*
GA, GB Grid point identification numbers of connection points. (Integer > 0;
GA GB )
X1, X2, X3 Components of orientation vector v , from GA, in the displacement coordinate
system at GA (Default), or in the basic coordinate system. See Remark 8. (Real)
G0 Alternate method to supply the orientation vector v using grid point G0.
Direction of v is from GA to G0. v is then transferred to End A. (Integer > 0;
G0 GA or GB)
OFFT Offset vector interpretation flag. See Remark 8. (Character or blank)
Main Index
1336 CBEAM
Beam Element Connection
Describer Meaning
PA, PB Pin flags for beam ends A and B, respectively; used to remove connections between
the grid point and selected degrees-of-freedom of the beam. The degrees-of-
freedom are defined in the element’s coordinate system and the pin flags are
applied at the offset ends of the beam (see Figure 9-14). The beam must have
stiffness associated with the PA and PB degrees-of-freedom to be released by the
pin flags. For example, if PA = 4, the PBEAM entry must have a nonzero value
for J, the torsional stiffness. (Up to five of the unique Integers 1 through 6 with
no embedded blanks.) Pin flags are not presently allowed in SOL 700. Also, Pin
flags should not be used in nonlinear analysis when there is large displacement.
W1A, W2A, W3A Components of offset vectors from the grid points to the end points of the axis of
W1B, W2B, W3B the shear center. See Remarks 7., 8. and 8. (Real; Default = 0.0)
SA, SB Scalar or grid point identification numbers for the ends A and B, respectively. The
degrees-of-freedom at these points are the warping variables d dx .
(Integers 0 or blank)
*See the BEAMOR entry for default options for field 3 and fields 6 through 9.
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. For an additional explanation of the beam element, see the Beam Element (CBEAM) in the MSC Nastran
Reference Guide. Figure 9-14 defines beam element geometry:
yma
zelem
yna Nonstructural Mass
zma
zna Center of Gravity
yelem
Plane 2
Plane 1 v
End A (0, 0, 0)
Neutral Axis
w a offset xelem v ymb
Grid Point GA Shear Center ynb zmb
znb
End B (xb, 0, 0)
w b offset
Grid Point GB
Figure 9-14 CBEAM Element Geometry System
Main Index
CBEAM 1337
Beam Element Connection
zelem yelem
Plane 1
Plane 2
M1
V2 M2
Neutral Axis
V1
Fx
xelem
Shear Center
Tx
Figure 9-15 CBEAM Internal Element Forces and Moments
3. If field 6 is an integer, then G0 is used. If field 6 is blank or real, then X1, X2, X3 is used.
4. G0 cannot be located at GA or GB.
5. The rules for the continuations entries are:
• Both continuations may be omitted if there are no pin flags, offsets, or warping variables.
• If the second continuation is used, then the first continuation must be included, even if all fields
are blank.
• If the second continuation is omitted, torsional stiffness due to warping of the cross section will
not be considered.
6. If warping is allowed (SA and SB > 0), then SA and SB must be defined with SPOINT or GRID
entries. If GRID entries are used, the warping degree-of-freedom is attached to the first (T1)
component. In addition, SPOINT ID is recommended for SA and SB if GROUNDCHECK is
requested in case control.
7. Offset vectors are treated internally like rigid elements. Two methods are available for the
computation of offsets: original and enhanced. The default method is the original method. The
enhanced method is requested by the Bulk Data entry MDLPRM,OFFDEF,LROFF. For options of
offsets, please refer to the Bulk Data entry MDLPRM,OFFDEF,option.
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, the user is required to use MDLPRM, OFFDEF, LROFF. In SOL103, if the case
control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then MDLPRM,
OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
For SOLs 106, 129, 153, and 159 the differential stiffness for offset vectors will give incorrect results
with PARAM, LGDISP, 1.
Main Index
1338 CBEAM
Beam Element Connection
8. OFFT in field 9 is a character string code that describes how the offset and orientation vector
components are to be interpreted. By default (string input is GGG or blank), the offset vectors are
measured in the displacement coordinate systems at grid points A and B and the orientation vector is
measured in the displacement coordinate system of grid point A. At user option, the offset vectors can
be measured in an offset system relative to grid points A and B, and the orientation vector can be
measured in the basic system as indicated in the following table:
String Orientation Vector End A Offset End B Offset
GGG Global Global Global
BGG Basic Global Global
GGO Global Global Offset
BGO Basic Global Offset
GOG Global Offset Global
BOG Basic Offset Global
GOO Global Offset Offset
BOO Basic Offset Offset
Any attempt to specify invalid combinations results in a bulk data entry input error message. For
example, a value of OOO (indicating offset and orientation vectors are specified in an offset reference
system) results in a fatal error since the orientation vector cannot be specified in an offset system. The
offset system x-axis is defined from GA to GB. The orientation vector v and the offset system x-axis
are then used to define the z and y axes of the offset system. A vector is formed from a cross product
of a vector going from Grid A to Grid B and the orientation vector to create the offset coordinate z-
direction. To obtain a nonzero cross product the orientation vector must not be parallel to both
vectors from Grid A to Grid B for the offset coordinate system and End A and End B for the element
coordinate system. (Note: The character “O” in the table replaces the obsolete character “E”.)
Main Index
CBEAM3 1339
Three-Node Beam Element Connection
CBEAM3 Three-Node Beam Element Connection
Defines a three-node beam element.
Format:
1 2 3 4 5 6 7 8 9 10
CBEAM3 EID PID GA GB GC X1 X2 X3
W1A W2A W3A W1B W2B W3B W1C W2C
W3C TWA TWB TWC SA SB SC
Example:
CBEAM3 101 2 201 332 1000 1.0 3.5 -2.0
3.0 3.0 2.2 -1.0
2.5 10. 15. 20.0 206 301 312
Alternate Format and Example:
CBEAM3 EID PID GA GB GC G0
W1A W2A W3A W1B W2B W3B W1C W2C
W3C TWA TWB TWC SA SB SC
CBEAM3 101 2 201 332 1000 105
3.0 2.2 1.0
2.5 10. 15. 20.0 206 301 312
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of PBEAM3 or PBMSECT entries. See
Remark 7. (Integer > 0; Required)
GA, GB, GC Grid point identification numbers of connection points. GA and GB are grid
point identification numbers at the two ends of the beam element while GC
is the one at the grid point in between. (Integer > 0 or blank; GA, GB and
GC must be distinct from each other. See Remark 6.)
X1, X2, X3 Components of orientation vector v , from GA, in the displacement
coordinate system at GA. (Real)
G0 Alternate method to supply the orientation vector v using grid point G0.
The direction of v is from GA to G0. v is then transferred to End A.
(Integer > 0; G0 GA or GB or GC)
Main Index
1340 CBEAM3
Three-Node Beam Element Connection
Describer Meaning
WiA, WiB, WiC Components of offsets vectors, measured in the displacement coordinate
systems at grid points A, B, and C, from the grid points to the points on the
axis of shear center. See Remark 8. (Real; Default = 0.0)
TWA, TWB, TWC Pretwist angles in degrees at A, B, and C, respectively. (Real; Default = 0.0)
SA, SB, SC Scalar or grid point identification numbers for A, B, and C, respectively. The
degrees of freedom at these points are warping variables. (Integer > 0 or
blank)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. If field 7 is an integer, then G0 is used. If field 7 is blank or real, then X1, X2, X3 are used.
3. G0 cannot be located at GA or GB or GC.
4. If warping effect is included in the analysis (SA, SB and SC > 0), then SA, SB, and SC must be defined
with either SPOINT or GRID entries. If GRID entries are used, the warping degree of freedom is
attached to the first (T1) component. In addition, SPOINT ID is recommended for SA, SB and SC
if GROUNDCHECK is requested in case control.
5. BEAMOR cannot be used to set up default options for field 3 and fields 6 through 8 for CBEAM3
entries.
6. If GC is left blank, then the element degenerates to a formulation similar to the two-node straight
beam element. The two-node straight beam formulation is not the CBEAM formulation and will
result in overly stiff results with warping and shear center offset. This is because the CBEAM3 is a
Variational Asymptotic Beam Section that generalizes Timoshenko beam theory and requires the mid
node for accuracy.
7. For CBEAM3 referencing PBMSECT, the CORE/LAYER keywords are required or a Fatal message
is issued. For this composite case, it is recommended that CBEAM3 has 3 nodes and 3 warping
DOFs.
Main Index
CBEAM3 1341
Three-Node Beam Element Connection
Locus of Shear
Center
C eb
Z elem Y elem
et
V Wc
A en
X elem
Wa B
GC
GA Wb
GB
Figure 9-16 CBEAM3 Element Geometry System
eb
ez
ey
Shear
Center en
Figure 9-17 Local Coordinate System on Beam Cross-Section
8. Offset vectors are treated internally like rigid elements. Two methods are available for the
computation of offsets: original and enhanced. The default method is the original method. The
enhanced method is requested by the Bulk Data entry MDLPRM,OFFDEF,LROFF. For options of
offsets, please refer to the Bulk Data entry MDLPRM,OFFDEF,option.
Main Index
1342 CBEAM3
Three-Node Beam Element Connection
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, the user is required to use MDLPRM, OFFDEF, LROFF. In SOL103, if the case
control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then MDLPRM,
OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
Main Index
CBEND 1343
Curved Beam or Pipe Element Connection
CBEND Curved Beam or Pipe Element Connection
Defines a curved beam, curved pipe, or elbow element.
Format:
1 2 3 4 5 6 7 8 9 10
CBEND EID PID GA GB X1 X2 X3 GEOM
Example:
CBEND 32 39 17 19 6.2 5.1 -1.2 3
Alternate Format and Example:
CBEND EID PID GA GB G0 GEOM
CBEND 32 39 17 19 106 3
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PBEND entry. (Integer > 0; Default = EID)
GA, GB Grid point identification numbers of connection points. (Integer > 0; GA GB )
X1, X2, X3 Components of orientation vector v , from GA, in the displacement coordinate system
at GA. (Real)
G0 Alternate method to supply the orientation vector v using grid point G0. Direction of
v is from GA to G0. v is then translated to End A. (Integer > 0; G0 GA or GB)
GEOM Flag to select specification of the bend element. See Remark 3. (1 Integer 4; No
Default)
Remarks:
1. Element identification numbers must be unique with respect to all other element identification
numbers.
Main Index
1344 CBEND
Curved Beam or Pipe Element Connection
2. For an additional explanation of the CBEND element, see the PBEND entry description. Figure 9-18
and Figure 9-19 define the element coordinate system and internal forces and moments.
Arc of the
Geometric Centroid
Center of
Curvature
zelem Arc of the
Neutral Axis
B
Plane 2
End A GA
GB
Relem
v
elem N
Plane 1 ZC
End B RC RB
(Note that Plane 1 is parallel to the
plane defined by GA, GB, and v.)
Figure 9-18 CBEND Element Coordinate System
zelem
Plane 2
GA
M1
GB
Relem V2
v
elem
Plane 1 V1
M2 F M
Figure 9-19 CBEND Element Internal Forces and Moments
3. The options for element connection to GA, GB using GEOM are the following.
Main Index
CBEND 1345
Curved Beam or Pipe Element Connection
Table 2 GEOM Options
Configuration GEOM Description
O 1 The center of curvature lies on the line AO (or its
extension) or vector v .
A B
2 The tangent of centroid arc at end A is parallel to line
A B AO or vector v . Point O (or vector v ) and the arc
AB must be on the same side of the chord AB .
O
3 The bend radius (RB) is specified on the PBEND
RB entry: Points A, B, and O (or vector v ) define a plane
parallel or coincident with the plane of the element arc.
A B Point O (or vector v ) lies on the opposite side of line
AB from the center of the curvature.
O
4 THETAB is specified on the PBEND entry. Points A,
B, and O (or vector v ) define a plane parallel or
coincident with the plane of the element arc. Point O
THETAB
(or vector v ) lies on the opposite side of line AB from
A B the center of curvature.
Main Index
1346 CBUSH
Generalized Spring-and-Damper Connection
CBUSH Generalized Spring-and-Damper Connection
Defines a generalized spring-and-damper structural element that may be nonlinear or frequency dependent.
Format:
1 2 3 4 5 6 7 8 9 10
CBUSH EID PID GA GB GO/X1 X2 X3 CID
S OCID S1 S2 S3
Example 1: Noncoincident grid points.
CBUSH 39 6 1 100 75
Example 2: GB not specified.
CBUSH 39 6 1 0
Example 3: Coincident grid points ( GA GB ).
CBUSH 39 6 1 6
Example 4: Noncoincident grid points with fields 6 through 9 blank and a spring-damper offset.
CBUSH 39 6 1 600
0.25 10 0. 10. 10.
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PBUSH entry. (Integer > 0; Default = EID)
GA, GB Grid point identification number of connection points. See Remark 6. (GA > 0,
GB 0 or blank)
Xi Components of orientation vector v , from GA, in the displacement coordinate system
at GA. (Real)
GO Alternate method to supply vector v using grid point GO. Direction of v is from GA
to GO. v is then transferred to End A. See Remark 3. (Integer > 0)
CID Element coordinate system identification. A 0 value means the basic coordinate system
will be used. If CID is blank, then the element coordinate system is determined from
GO or Xi. See Figure 9-20 and Remark 3. (Integer > 0 or blank)
S Location of spring damper. See Figure 9-20. (Real; Default = 0.5)
Main Index
CBUSH 1347
Generalized Spring-and-Damper Connection
Describer Meaning
OCID Coordinate system identification of spring-damper offset. See Remark 9. (Integer > -1;
Default = -1, which means the offset point lies on the line between GA and GB
according to Figure 9-20)
S1, S2, S3 Components of spring-damper offset in the OCID coordinate system if OCID > 0. See
Figure 9-21 and Remark 9. (Real)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Figure 9-20 shows the bush element geometry. In geometric nonlinear analysis (SOL400), the element
axis (line GA to GB) follows the deformation of grids GA and GB.
3. CID ≥ 0 overrides GO and Xi. Then the element x-axis is along T1, the element y-axis is along T2,
and the element z-axis is along T3 of the CID coordinate system. If the CID refers to a cylindrical
coordinate system or a spherical coordinate system, then grid GA is used to locate the system. If for
cylindrical or spherical coordinate, GA falls on the z-axis used to define them, it is recommended that
another CID be selected to define the element x-axis.
4. For noncoincident grids ( GA GB ), when GO or (X1, X2, X3) is given and no CID is specified,
the line AB is the element x-axis and the orientation vector v lies in the x-y plane (similar to the
CBEAM element).
5. For noncoincident grids ( GA GB ), if neither GO or (X1, X2, X3) is specified and no CID is
specified, then the line AB is the element x-axis. This option is valid only when K1 (or B1) or K4 (or
B4) or both on the PBUSH entry are specified (but K2, K3, K5, K6 or B2, B3, B5, B6 are not
specified). If K2, K3, K5, or K6 (or B2, B3, B5, or B6) are specified, a fatal message will be issued.
6. If the distance between GA and GB is less than .0001, or if GB is blank, then CID must be specified.
GB blank implies that B is a grounded terminal, a gounded terminal is a point with a displacement
that is constrained to zero.
7. If PID references a PBUSHT entry, then the CBUSH element may only be defined in the residual
structure and cannot be attached to any omitted degrees-of-freedom.
8. Element impedance output is computed in the CID coordinate system. The impedances in this
system are uncoupled.
9. If OCID = -1 or blank (default) then S is used and S1, S2, S3 are ignored. If OCID > 0, then S is
ignored and S1, S2, S3 are used.
Main Index
1348 CBUSH
Generalized Spring-and-Damper Connection
z elem
GA v
Sl y elem
1 – S l
Bush location
GB
x elem
Figure 9-20 CBUSH Element
z elem y elem
Bush location
CID
x
S1, S2, S3 OCID elem
GB
GA
The material stiffness and damping properties of
the elastomer are located at (S1, S2, S3).
Figure 9-21 Definition of Offset S1, S2, S3
10. When CID > 0, the element x-axis is set as in Remark 3. This means that the element force is always
computed as Ke UB – UA ; if UA UB , a compressive force will result. This is unlike the
GO or Xi options, where relative positive elongation in tension and relative negative elongation is
compression.
Main Index
CBUSH 1349
Generalized Spring-and-Damper Connection
11. The CBUSH element is designed to satisfy rigid body equilibrium requirements. For noncoincident
grids, internal rigid links connect the bush location to the grid locations. This results in coupling
between translational and rotational degrees-of-freedom at the grids even when no rotational springs
or dampers are specified on the PBUSH.
12. CBUSH elements are not supported in thermal analysis.
Main Index
1350 CBUSH1D
Rod Type Spring-and-Damper Connection
CBUSH1D Rod Type Spring-and-Damper Connection
Defines the connectivity of a one-dimensional spring and viscous damper element.
Format:
1 2 3 4 5 6 7 8 9 10
CBUSH1D EID PID GA GB CID
Example:
CBUSH1D 35 102 108 112
Describer Meaning Default Values
EID Element identification number. (0 < Integer < 100,000,000) Required
PID Property identification number of a PBUSH1D entry. (Integer > EID
0)
GA Grid point id of first grid. Required
GB Grid point id of second grid blank
CID Coordinate system id. (Integer > 0) blank
Remarks:
1. For noncoincident grids GA GB and if CID is blank, the line GA to GB is the element axis. In
geometric nonlinear analysis, the element axis (line GA to GB) follows the deformation of grids GA
and GB. See Figure 9-22.
2. If CID > 0 is specified, the x-axis of the CID coordinate system is the element axis. In geometric
nonlinear analysis, the element axis (x-axis of CID) remains fixed.
3. If GA and GB are coincident or if GB is blank, then CID > 0 must be specified and the element axis
is the x-axis of CID.
GB
GA
Figure 9-22 Spring and Damper Element
Main Index
CBUSH2D 1351
2-D Linear-Nonlinear Connection
CBUSH2D 2-D Linear-Nonlinear Connection
Defines the connectivity of a two-dimensional Linear-Nonlinear element.
Format:
1 2 3 4 5 6 7 8 9 10
CBUSH2D EID PID GA GB CID PLANE
Example:
CBUSH2D 100 101 1001 2001 0 XY
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000; Required)
PID Property identification number of a PBUSH2D. (Integer > 0; Required)
GA Inner grid. (Integer > 0; Required)
GB Outer grid. (Integer > 0; Required)
CID Coordinate system used to define 2-D plane. (Integer > 0; Default = 0)
PLANE Orientation plane in CID: XY, YZ, ZX, see Remark 1. (Character; Default = ‘XY’)
Remarks:
1. The XY, YZ, and ZX planes are relative to the displacements coordinates of GA and GB. The planes
correspond to directions 1 and 2. GA and GB should be coincident grids with parallel displacement
coordinate systems. The coordinate systems are not checked. Wrong answers will be produced if this
rule is not followed.
2. The behavior is different if there is no rotor in the model and a CBUSH2D is used. When this
happens, for most cases, if there is no rotor the nominal stiffness values from the PBUSH2D will be
used, with no frequency-dependence. However, if an ELEMUDS is used, the CBUSH2D will be
ignored if there is no rotor in the model. Also, an ELEMUDS with CBUSH2DA call will require to
have a rotor in the model. A FATAL message will be used if there is no rotor, for ELEMUDS having
CBUSH2DA call.
Main Index
1352 CCONEAX
Axisymmetric Shell Element Connection
CCONEAX Axisymmetric Shell Element Connection
Defines a conical shell element.
Format:
1 2 3 4 5 6 7 8 9 10
CCONEAX EID PID RA RB
Example:
CCONEAX 1 2 3 4
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PCONEAX entry. (Integer > 0; Default = EID)
RA Identification number of a RINGAX entry. (Integer > 0; RA RB )
RB Identification number of a RINGAX entry. (Integer > 0; RA RB )
Remarks:
1. This element has limited capabilities. See the MSC Nastran Reference Guide, Section 5.3.3.
2. This entry is allowed only if an AXIC entry is also present.
3. In order to reference this entry on a SET Case Control command, the ID must be modified by
IDn = ID 1000 + n
where n is the harmonic number plus one and IDn is the value specified on the SET entry.
Main Index
CDAMP1 1353
Scalar Damper Connection
CDAMP1 Scalar Damper Connection
Defines a scalar damper element.
Format:
1 2 3 4 5 6 7 8 9 10
CDAMP1 EID PID G1 C1 G2 C2
Example:
CDAMP1 19 6 0 23 2
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PDAMP property entry. (Integer > 0;
Default = EID)
G1, G2 Geometric grid point identification number. (Integer > 0)
C1, C2 Component number. (0 ≤ Integer ≤ 6; blank or zero if scalar point.)
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2), must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. When CDAMP1 is used in heat transfer analysis, it generates a lumped heat capacity.
6. A scalar point specified on this entry need not be defined on an SPOINT entry.
7. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry.
Main Index
1354 CDAMP1D
Scalar Damper Connection for SOL 700 Only
CDAMP1D Scalar Damper Connection for SOL 700 Only
Defines a scalar damper connection for use in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CDAMP1D EID PID G1 C1 G2 C2
CORD FOLLOW
Example:
CDAMP1D 1001 101 55 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PDAMPn entry. (Integer > 0; Default = EID)
G1, G2 Geometric grid point identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; 0 or up to six unique integers, 1 through 6 may
be specified in the field with no embedded blanks. 0 applies to scalar points and 1
through 6 applies to grid points.)
CORD Number of a coordinate system in which the degree-of-freedom (C1,C2) is defined.
(Integer > 0)
FOLLOW Method to update the direction vector in which the damper acts: FOLLOW=CORD:
direction vector follows the motion of the coordinate system as specified under CORD.
Remark:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2), must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. When CDAMP1 is used in heat transfer analysis, it generates a lumped heat capacity.
6. A scalar point specified on this entry need not be defined on an SPOINT entry.
7. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry.Available in SOL 700 only.
Main Index
CDAMP2 1355
Scalar Damper Property and Connection
CDAMP2 Scalar Damper Property and Connection
Defines a scalar damper element without reference to a material or property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CDAMP2 EID B G1 C1 G2 C2
Example:
CDAMP2 16 2.98 32 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
B Value of the scalar damper. (Real)
G1, G2 Geometric grid point identification number. (Integer > 0)
C1, C2 Component number. (0 ≤ Integer ≤ 6; blank or zero if scalar point.)
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2), must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. When CDAMP2 is used in heat transfer analysis, it generates a lumped heat capacity.
6. A scalar point specified on this entry need not be defined on an SPOINT entry.
7. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry.
Main Index
1356 CDAMP2D
Scalar Damper Connection for SOL 700 Only
CDAMP2D Scalar Damper Connection for SOL 700 Only
Defines a scalar damper connection for use in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CDAMP2D EID B G1 C1 G2 C2
CORD FOLLOW
Example:
CDAMP2D 1001 101 55 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
B Value of the scalar damper. (Real)
G1, G2 Geometric grid point identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; 0 or up to six unique integers, 1 through 6 may
be specified in the field with no embedded blanks. 0 applies to scalar points and 1
through 6 applies to grid points.)
CORD Number of a coordinate system in which the degree-of-freedom (C1,C2) is defined.
(Integer > 0)
FOLLOW Method to update the direction vector in which the damper acts: FOLLOW=CORD:
direction vector follows the motion of the coordinate system as specified under CORD.
Remark:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2), must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. When CDAMP2 is used in heat transfer analysis, it generates a lumped heat capacity.
6. A scalar point specified on this entry need not be defined on an SPOINT entry.
7. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry. Available in SOL 700 only.
Main Index
CDAMP3 1357
Scalar Damper Connection to Scalar Points Only
CDAMP3 Scalar Damper Connection to Scalar Points Only
Defines a scalar damper element that is connected only to scalar points.
Format:
1 2 3 4 5 6 7 8 9 10
CDAMP3 EID PID S1 S2
Example:
CDAMP3 16 978 24 36
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PDAMP entry. (Integer > 0; Default = EID)
S1, S2 Scalar point identification numbers. (Integer > 0; S1 S2 )
Remarks:
1. S1 or S2 may be blank or zero, indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. Only one scalar damper element may be defined on a single entry.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. When CDAMP3 is used in heat transfer analysis, it generates a lumped heat capacity.
6. A scalar point specified on this entry need not be defined on an SPOINT entry.
Main Index
1358 CDAMP4
Scalar Damper Property and Connection to Scalar Points Only
CDAMP4 Scalar Damper Property and Connection to Scalar Points Only
Defines a scalar damper element that connected only to scalar points and without reference to a material or
property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CDAMP4 EID B S1 S2
Example:
CDAMP4 16 -2.6 4 9
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
B Scalar damper value. (Real)
S1, S2 Scalar point identification numbers. (Integer > 0; S1 S2 )
Remarks:
1. S1 or S2 may be blank or zero, indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. Only one scalar damper element may be defined on a single entry.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. If this entry is used in heat transfer analysis, it generates a lumped heat capacity.
6. A scalar point specified on this entry need not be defined on an SPOINT entry.
Main Index
CDAMP5 1359
Scalar Damper with Material Property
CDAMP5 Scalar Damper with Material Property
Defines a damping element that refers to a material property entry and connection to grid or scalar points.
This element is intended for heat transfer analysis only.
Format:
1 2 3 4 5 6 7 8 9 10
CDAMP5 EID PID G1 G2
Example:
CDAMP5 1 4 10 20
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Identification number of a PDAMP5 property entry. (Integer > 0; Default = EID)
G1, G2 Grid or scalar point identification numbers. (Integer > 0 and G1 G2 )
Remarks:
1. G1 or G2 may be blank or zero indicating a constraint.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. CDAMP5 generates a lumped heat capacity in heat transfer analysis.
4. A scalar point specified on CDAMP5 need not be defined on an SPOINT entry.
Main Index
1360 CDUMi
Dummy Element Connection
CDUMi Dummy Element Connection
Defines a dummy element (3 < i <7).
Format:
1 2 3 4 5 6 7 8 9 10
CDUMi EID PID G1 G2 G3 G4 -etc.-
A1 A2 -etc.-
Example:
CDUM3 114 108 2 5 6 8 11
2.4 3.E4 2 50
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PDUMi entry. See Remark 2. (Integer > 0)
Gi Grid point identification numbers of connection points. (Integer > 0; G1 G2
GN )
Ai Additional fields. (Real or Integer)
Remarks:
1. The user must write the associated element subroutines for matrix generation, stress recovery, etc.,
and perform a link edit to replace the dummy routines. See the MSC Nastran Programmer’s Manual.
2. If no property entry is required, PID may contain the material identification number.
3. Additional entries are defined in the user-written element routines.
4. The fields on this entry are required to be defined on the corresponding ADUMi entry. This entry
requires a license for "USER MODIFIABLE Nastran" Other than the EID field, all field checking
is the responsibility of the user supplied code.
Main Index
CELAS1 1361
Scalar Spring Connection
CELAS1 Scalar Spring Connection
Defines a scalar spring element.
Format:
1 2 3 4 5 6 7 8 9 10
CELAS1 EID PID G1 C1 G2 C2
Example:
CELAS1 2 6 8 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PELAS entry. (Integer > 0; Default = EID)
G1, G2 Geometric grid point identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; blank or zero if scalar point.)
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero. If only scalar points and/or ground are involved, it is more efficient to use the
CELAS3 entry.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2) must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry.
7. It is recommended that for most applications the grids connected by CELAS1 entries be coincident
and the displacement coordinate systems of each grid be conguent. Connecting non-coincident grids
and/or non-congruent coordinate systems can lead to models that do not pass strain energy checks
(see the GROUNDCHECK (Case)Case Control command).
Main Index
1362 CELAS1D
Scalar Spring Connection for SOL 700 Only
CELAS1D Scalar Spring Connection for SOL 700 Only
Defines a scalar spring connection for use in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CELAS1D EID PID G1 C1 G2 C2
CORD FOLLOW
Example:
CELAS1D 1001 101 55 1 8 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PELAS entry. (Integer > 0; Default = EID)
G1, G2 Geometric grid point identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; 0 or up to six unique, 1 through 6 may be
specified in the field with no embedded blanks. 0 applies to scalar points and 1 through
6 applies to grid points.)
CORD Number of a coordinate system in which the degree-of-freedom (C1,C2) is defined.
(Integer > 0) (SOL 700 only)
FOLLOW Method to update the direction vector in which the spring acts:
For SOL 700:
FOLLOW=CORD: Direction vector follows the motion of the coordinate system as
specified under CORD.
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero. If only scalar points and/or ground are involved, it is more efficient to use the
CELAS3 entry.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2) must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
Main Index
CELAS1D 1363
Scalar Spring Connection for SOL 700 Only
6. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry.
7. Available in SOL 700 only.
8. It is recommended that for most applications the grids connected by CELAS1D entries be coincident
and the displacement coordinate systems of each grid be conguent. Connecting non-coincident grids
and/or non-congruent coordinate systems can lead to models that do not pass strain energy checks
(see the GROUNDCHECK (Case) Case Control command).
Main Index
1364 CELAS2
Scalar Spring Property and Connection
CELAS2 Scalar Spring Property and Connection
Defines a scalar spring element without reference to a property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CELAS2 EID K G1 C1 G2 C2 GE S
Example:
CELAS2 28 6.2+3 32 19 4
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
K Stiffness of the scalar spring. (Real)
G1, G2 Geometric grid point or scalar identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; 0 blank or zero if scalar point.)
GE Damping coefficient. See Remarks 6. and 8. (Real)
S Stress coefficient. (Real)
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero. If only scalar points and/or ground are involved, it is more efficient to use the
CELAS4 entry.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2) must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. If PARAM,W4 is not specified, GE is ignored in transient analysis. See Parameters.
7. If Gi refers to a grid point then Ci refers to degrees-of-freedom in the displacement coordinate system
specified by CD on the GRID entry.
8. To obtain the damping coefficient GE, multiply the critical damping ratio C C 0 by 2.0.
Main Index
CELAS2D 1365
Scalar Spring Connection for SOL 700 Only
CELAS2D Scalar Spring Connection for SOL 700 Only
Defines a scalar spring connection for use in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CELAS2D EID K G1 C1 G2 C2
CORD FOLLOW
Example:
CELASD2 1001 101 55 1 8 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
K Stiffness of the scalar spring. (Real)
G1, G2 Geometric grid point identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; 0 or up to six unique, 1 through 6 may be
specified in the field with no embedded blanks. 0 applies to scalar points and 1 through
6 applies to grid points.)
CORD Number of a coordinate system in which the degree-of-freedom (C1,C2) is defined.
(Integer > 0)
FOLLOW Method to update the direction vector in which the spring acts:
FOLLOW=CORD: Direction vector follows the motion of the coordinate system as
specified under CORD.
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero. If only scalar points and/or ground are involved, it is more efficient to use the
CELAS4 entry.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2) must be distinct.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. If Gi refers to a grid point then Ci refers to degrees-of-freedom in the displacement coordinate system
specified by CD on the GRID entry.
Main Index
1366 CELAS2D
Scalar Spring Connection for SOL 700 Only
7. It is recommended that for most applications the grids connected by CELAS2D entries be coincident
and the displacement coordinate systems of each grid be congruent. Connecting non-coincident grids
and/or non-congruent coordinate systems can lead to models that do not pass strain energy checks
(see the GROUNDCHECK (Case) Case Control command).
Main Index
CELAS3 1367
Scalar Spring Connection to Scalar Points Only
CELAS3 Scalar Spring Connection to Scalar Points Only
Defines a scalar spring element that connects only to scalar points.
Format:
1 2 3 4 5 6 7 8 9 10
CELAS3 EID PID S1 S2
Example:
CELAS3 19 2 14 15
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PELAS entry. (Integer > 0; Default = EID)
S1, S2 Scalar point identification numbers. (Integer > 0; S1 S2 )
Remarks:
1. S1 or S2 may be blank or zero, indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. Only one scalar spring element may be defined on a single entry.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
Main Index
1368 CELAS4
Scalar Spring Property and Connection to Scalar Points Only
CELAS4 Scalar Spring Property and Connection to Scalar Points Only
Defines a scalar spring element that is connected only to scalar points, without reference to a property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CELAS4 EID K S1 S2
Example:
CELAS4 42 6.2-3 2
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
K Stiffness of the scalar spring. (Real)
S1, S2 Scalar point identification numbers. (Integer > 0; S1 S2 )
Remarks:
1. S1 or S2, but not both, may be blank or zero indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. A structural damping coefficient is not available with CELAS4. The value of g is assumed to be 0.0.
4. No stress coefficient is available with CELAS4.
5. Only one scalar spring element may be defined on a single entry.
6. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
7. A scalar point specified on this entry need not be defined on an SPOINT entry.
Main Index
CFAST 1369
A Shell Patch Fastener Connection
CFAST A Shell Patch Fastener Connection
Defines a fastener with material orientation connecting two surface patches. Large displacement and large
rotational effects are supported when in SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
CFAST EID PID TYPE IDA IDB GS GA GB
XS YS ZS
Example using PROP:
CFAST 3 20 PROP 21 24 206
Example using ELEM:
CFAST 7 70 ELEM 27 74 707
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PFAST entry. (Integer > 0; Default = EID)
TYPE Specifies the surface patch definition: (Character)
If TYPE = ‘PROP’, the surface patch connectivity between patch A and patch B is
defined with two PSHELL (or PCOMP) properties with property ids given by IDA and
IDB. See Remark 1. and Figure 9-23.
If TYPE = ‘ELEM’, the surface patch connectivity between patch A and patch B is
defined with two shell element ids given by IDA and IDB. See Remark 1. and
Figure 9-23.
IDA,IDB Property id (for PROP option) or Element id (for ELEM option) defining patches A
and B. IDA IDB (Integer > 0)
GS Grid point defining the location of the fastener. See Remark 2. (Integer > 0 or blank)
GA,GB Grid ids of piercing points on patches A and B. See Remark 2. (Integer > 0 or blank)
XS,YS,ZS Location of the fastener in basic. Required if neither GS nor GA is defined. See Remark
2. (Real or blank)
Remarks:
1. The CFAST defines a flexible connection between two surface patches. The number of unique
physical grids connected depends on the location for the piercing points GA and GB and the size of
the diameter D (see PFAST).
Main Index
1370 CFAST
A Shell Patch Fastener Connection
GS
PIDB
GB
PIDA
L
SHIDB GA
D SHIDA
Figure 9-23 Patches Defined with TYPE= ‘PROP’ or TYPE = ‘ELEM’
2. GS defines the approximate location of the fastener in space. GS is projected onto the surface patches
A and B. The resulting piercing points GA and GB define the axis of the fastener. GS does not have
to lie on the surfaces of the patches. GS must be able to project normals to the two patches. GA can
be specified in lieu of GS, in which case GS will be ignored. If neither GS nor GA is specified, then
(XS, YS, ZS) in basic must be specified.
If both GA and GB are specified, they must lie on or at least have projections onto surface patches A
and B respectively. If GA and GB are both specified, GS is ignored. By default, the locations of user
specified GA and GB will not be changed. If the user specifies "SWLDPRM, MOVGAB, 1,", then
the locations will be corrected so that they lie on the surface patches A and B within machine
precision. The length of the fastener is the final distance between GA and GB. If the length is zero,
the normal to patch A is used to define the axis of the fastener.
Diagnostic printouts, checkout runs and control of search and projection parameters are requested on
the SWLDPRM Bulk Data entry.
3. The use of param,cfdiagp,yes and param,cfrandel,real_fraction_value allows for the random removal
of a percentage of CFAST elements for failure studies.
4. This entry is not supported in SOL 700.
5. If used in a multi-physics coupled problem using SUBSTEP, they participate in the mechanical
substep but are ignored in the heat transfer subsstep through automatic deactivation. For more
information on deactivation, see the DEACTEL keyword under the NLMOPTS Bulk Data entry and
the associated Remark 10. for that entry.
6. In SOL400, the behavior of this element in regard to large rotation is affected by the Case Control
Command Rigid.
7. If partitioned superelements are present, then CFAST is supported in the main Bulk Data section
only.
Main Index
CFLUIDi 1371
Fluid Element Connections
CFLUIDi Fluid Element Connections
Defines three types of fluid elements for an axisymmetric fluid model.
Formats:
1 2 3 4 5 6 7 8 9 10
CFLUID2 EID IDF1 IDF2 RHO B
CFLUID3 EID IDF1 IDF2 IDF3 RHO B
CFLUID4 EID IDF1 IDF2 IDF3 IDF4 RHO B
Examples:
CFLUID2 100 11 14 .025 0.0
CFLUID3 110 15 13 12 1.2
CFLUID4 120 11 15 12 14
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
IDFi Identification number of a RINGFL entry. (Integer > 0;
IDF1 IDF2 IDF3 IDF4 ; all IDFi < 500000)
RHO Mass density. (Real > 0.0; Default is the value of DRHO on the AXIF entry)
B Bulk modulus, pressure per volume ratio. (Real; Default is the value of DB on the AXIF
entry)
Remarks:
1. CFLUIDi is allowed only if an AXIF entry is also present.
2. Element identification number must be unique with respect to all other fluid, scalar, and structural
elements.
Main Index
1372 CFLUIDi
Fluid Element Connections
3. The volume defined by IDFi is a body of revolution about the polar axis of the fluid coordinate system
defined by AXIF. CFLUID2 defines a thick disk with IDF1 and IDF2 defining the outer corners as
shown in Figure 9-24:
15
Polar
Axis
14
= 0.0
Element Element Element
100, 120, 110,
CFLUID2 CFLUID4 CFLUID3
11 12 13
Radius
Figure 9-24 CFLUIDi Examples
4. All interior angles must be less than 180.
5. The order of connected RINGFL points is arbitrary.
6. If B = 0.0, the fluid is incompressible.
Main Index
CGAP 1373
Gap Element Connection
CGAP Gap Element Connection
Defines a gap or friction element.
Format:
1 2 3 4 5 6 7 8 9 10
CGAP EID PID GA GB X1 X2 X3 CID
Example:
CGAP 17 2 110 112 5.2 0.3 -6.1
Alternate Format and Example:
CGAP EID PID GA GB GO CID
CGAP 17 2 110 112 13
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PGAP entry. (Integer > 0; Default = EID)
GA, GB Connected grid points at ends A and B. (Integers > 0; GA GB )
X1, X2, X3 Components of the orientation vector v , from GA, in the displacement coordinate
system at GA. (Real)
GO Alternate method to supply the orientation vector v using grid point GO. Direction of
v is from GA to GO. (Integer > 0)
CID Element coordinate system identification number. CID must be specified if GA and GB
–4
are coincident (distance from GA to GB 10 ). See Remark 6. (Integer > 0 or blank)
Remarks:
1. The CGAP element is intended for the nonlinear solution sequences 106, 129, 153, 159, and 400.
However, it will produce a linear stiffness matrix for the other solutions, but remains linear with the
initial stiffness. The stiffness used depends on the value for the initial gap opening (U0 field in the
PGAP entry).
2. The gap element coordinate system is defined by one of two following methods:
• If the coordinate system (CID field) is specified, the element coordinate system is established
using that coordinate system, in which the element x-axis is in the T1 direction and the y-axis in
the T2 direction. The orientation vector v will be ignored in this case.
• If the CID field is blank and the grid points GA and GB are not coincident (distance from A to
–4
B 10 ), then the line AB is the element x-axis and the orientation vector v lies in the x-y
plane (like the CBEAM element).
Main Index
1374 CGAP
Gap Element Connection
3. The element coordinate system does not rotate as a result of deflections.
4. Initial gap openings are specified on the PGAP entry and not derived from the separation distance
between GA and GB.
5. Forces are requested with the FORCE or NLSTRESS Case Control command. The NLSTRESS
command is only for nonlinear solutions, and the output also includes the gap STATUS. Forces are
output in the element coordinate system. The force F x is positive for compression.
6. If CID is being used to define the element coordinate system and the CID refers to either a cylindrical
or spherical coordinate system then grid GA will be used to locate the system. If grid GA lies on the
z-axis of the cylindrical or spherical coordinate system it is recommended that a different coordinate
system be used for this element.
7. See PARAM,CDITER for an alternative approach.
zelem
yelem
KA and KB in this
figure are from the
PGAP entry.
GA
xelem v
KB KA - KB
GB
Figure 9-25 CGAP Element Coordinate System
8. Since a large stiffness is used for KA (the closed GAP stiffness), param,g damping should be avoided.
Instead damping should be specified on the MATi entries and PARAM,W4 set.
Main Index
CHACAB 1375
Acoustic Absorber Element Connection
CHACAB Acoustic Absorber Element Connection
Defines the acoustic absorber element in coupled fluid-structural analysis.
Format:
1 2 3 4 5 6 7 8 9 10
CHACAB EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12
G17 G18 G19 G20
Example:
CHACAB 95 12 1 2 5 7 8 9
24 23
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PACABS entry. (Integer > 0)
Gi Grid point identification numbers of connection points. (Integer > 0 or blank)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Grid points G1 through G4 must be given in consecutive order about one quadrilateral face. G5
through G8 must be on the opposite face with G5 opposite G1, G6 opposite G2, etc.
3. The edge points, G9 to G20, are optional. Any or all of them may be deleted. If the ID of any edge
connection point is left blank or set to zero (as for G9 and G10 in the example), the equations of the
element are adjusted to give correct results for the reduced number of connections. Corner grid points
cannot be deleted.
4. It is recommended that the edge points be located within the middle third of the edge.
5. The face consisting of grid points G1 through G4 and G9 through G12 is assumed to be in contact
with the structure.
Main Index
1376 CHACAB
Acoustic Absorber Element Connection
G18
G7
G6
G19
G17
G20
G8
G2
G10 G5
G3
G11 G9
G4 G12
G1
Figure 9-26 CHACAB Element Connection
6. The mass is lumped to the face formed by grid points G5 through G8 and G17 through G20 and
defined to be in contact with the fluid. The opposite face has no mass contribution due to the
absorber element. Also, the face in contact with the fluid has only translational stiffness in the
direction normal to the face.
Main Index
CHACBR 1377
Acoustic Barrier Element Connection
CHACBR Acoustic Barrier Element Connection
Defines the acoustic barrier element.
Format:
1 2 3 4 5 6 7 8 9 10
CHACBR EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12
G17 G18 G19 G20
Example:
CHACBR 95 12 1 2 5 7 8 9
24 23
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PACBAR entry. (Integer > 0)
Gi Grid point identification numbers of connection points. (Integer > 0)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Grid points G1 through G4 must be given in consecutive order about one quadrilateral face. G5
through G8 must be on the opposite face with G5 opposite G1, G6 opposite G2, etc.
3. The edge points, G9 to G20, are optional. Any or all of them may be deleted. If the ID of any edge
connection point is left blank or set to zero (as for G9 and G10 in the example), the equations of the
element are adjusted to give correct results for the reduced number of connections. Corner grid points
cannot be deleted.
4. It is recommended that the edge points be located within the middle third of the edge.
5. The face consisting of grids G1 through G4 and G9 through G12 is assumed to be the backing that
corresponds to MBACK on the PACBAR entry.
6. The face consisting of grid points G5 through G8 and G17 through G20 is assumed to be the septum
that corresponds to MSEPTM on the PACBAR entry.
Main Index
1378 CHACBR
Acoustic Barrier Element Connection
G18
G7
G6
G19
G17
G20
G8
G2
G10 G5
G3
G11 G9
G4 G12
G1
Figure 9-27 CHACBR Element Connection
7. The face in contact with the fluid is defined to be the face formed by grid points G5 through G8 and
G17 through G20 and has only translational stiffness in the direction normal to the face.
Main Index
CHBDYE 1379
Geometric Surface Element Definition (Element Form)
CHBDYE Geometric Surface Element Definition (Element Form)
Defines a boundary condition surface element with reference to a heat conduction element.
Format:
1 2 3 4 5 6 7 8 9 10
CHBDYE EID EID2 SIDE IVIEWF IVIEWB RADMIDF RADMIDB
Example:
CHBDYE 2 10 1 3 3 2 2
Describer Meaning
EID Surface element identification number for a specific side of a particular element
(0 < Integer < 100,000,000). See Remarks 1. and 9.
EID2 A heat conduction element identification number. (Integer > 0)
SIDE A consistent element side identification number. See Remark 6. (1 < Integer < 6)
IVIEWF A VIEW entry identification number for the front face of surface element. See Remark
2. for default. (Integer > 0)
IVIEWB A VIEW entry identification number for the back face of surface element. See Remark
2. for default. (Integer > 0)
RADMIDF RADM identification number for front face of surface element. See Remark 2. for
default. (Integer > 0)
RADMIDB RADM identification number for back face of surface element. See Remark 2. for
default. (Integer > 0)
Remarks:
1. EID is a unique elemental ID associated with a particular surface element. EID2 identifies the general
heat conduction element being considered for this surface element.
2. The defaults for IVIEWF, IVIEWB, RADMIDF, and RADMIDB may be specified on the BDYOR
entry. If a particular field is blank both on the CHBDYE entry and the BDYOR entry, then the
default is zero.
3. For the front face of shell elements, the right-hand rule is used as one progresses around the element
surface from G1 to G2 to ... Gn. For the edges of shell elements or the ends of line elements, an
outward normal is used to define the front surface.
4. If the surface element is to be used in the calculation of view factors, it must have an associated VIEW
entry.
5. All conduction elements to which any boundary condition is to be applied must be individually
identified with the application of one of the surface element entries: CHBDYE, CHBDYG, or
CHBDYP.
Main Index
1380 CHBDYE
Geometric Surface Element Definition (Element Form)
6. Side conventions for solid elements.
The sides of the solid elements are numbered consecutively according to the order of the grid point
numbers on the solid element entry. The sides of solid elements are either quadrilaterals or triangles.
For each element type, tabulate the grid points (gp) at the corners of each side.
8-node or 20-node CHEXA
side gp gp gp gp
1 4 3 2 1
2 1 2 6 5
3 2 3 7 6
4 3 4 8 7
5 4 1 5 8
6 5 6 7 8
CPENTA
side gp gp gp gp
1 3 2 1
2 1 2 5 4
3 2 3 6 5
4 3 1 4 6
5 4 5 6
CTETRA
side gp gp gp
1 3 2 1
2 1 2 4
3 2 3 4
4 3 1 4
CPYRAM
Main Index
CHBDYE 1381
Geometric Surface Element Definition (Element Form)
side gp gp gp gp
1 3 2 5
2 1 4 5
3 2 1 5
4 3 5 4
5 4 1 2 3
7. Side conventions for shell elements.
Side 1 of shell elements (top) are of an AREA type, and additional sides (2 through a maximum of 5
for a QUAD) are of LINE type. (See CHBDYG for surface type definition.)
Area Type Sides -- The first side is that given by the right-hand rule on the shell elements grid points.
Line Type Sides -- The second side (first line) proceeds from grid point 1 to grid point 2 of the shell
element, and the remaining lines are numbered consecutively. The thickness of the line is that of the
shell element, and the normal to the line is outward from the shell element in the plane of the shell.
Note that any midside nodes are ignored in this specification.
For 3-D heat shell elements when used in combination with linear or quadratic nodal temperature
(see option TEMPP of the NLMOPTS entry), SIDE=6 refers to BOT surface. SIDE=1 refers to TOP
surface. The IVIEW and RADM should be filled in consistently in relation with the SIDE entry. E.g.,
when SIDE=1 or 6 then only IVIEWF makes sense.
8. Side conventions for line elements.
LINE elements have one linear side (side 1) with geometry that is the same as that of the element and
two POINT-type sides corresponding to the two points bounding the linear element (first grid point-
side 2; second grid point-side 3).
The TUBE-type element has two linear sides of type TUBE. The first side represents the outside with
diameters equal to that of the outside of the tube. The second side represents the inside with
diameters equal to that of the inside of the tube.
Point Sides -- Point sides may be used with any linear element. The direction of the outward normals
of these points is in line with the element axis, but pointing away from the element. The area assigned
to these POINT-type sides is consistent with the element geometry.
Rev Sides -- The CTRIAX6 element has associated with it three REV sides. The first side is associated
with Grid Points G1, G2, and G3. The positive face identification normals point away from the
element.
Main Index
1382 CHBDYE
Geometric Surface Element Definition (Element Form)
9. Application of boundary conditions to CHBDYE is referenced through the EID. Boundary
conditions can reference either the front or back face of the CHBDYE by specifying +EID or -EID
respectively. Correspondingly, the back face is minus the normal vector of the front face. Similarly,
IVIEWF and RADMIDF are associated with +EID and IVIEWB and RADMIDB with -EID. For
radiation problems, if the RADMIDF or RADMIDB is zero, default radiant properties assume
perfect black body behavior.
10. Starting with MSC Nastran 2004, axisymmetric view factors are supported CHBDYG of
TYPE=REV, but not supported CHBDYE. If CHBDYE is used for this, axisymmetric view factors
are not calculated.
Main Index
CHBDYG 1383
Geometric Surface Element Definition (Grid Form)
CHBDYG Geometric Surface Element Definition (Grid Form)
Defines a boundary condition surface element without reference to a property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CHBDYG EID TYPE IVIEWF IVIEWB RADMIDF RADMIDB
G1 G2 G3 G4 G5 G6 G7 G8
Example:
CHBDYG 2 AREA4 3 3 2 2
100 103 102 101
Describer Meaning
EID Surface element identification number. (Unique (0 < Integer < 100,000,000) among
all elemental entries)
TYPE Surface type. See Remark 3. (Character)
IVIEWF A VIEW entry identification number for the front face. See Remark 2. for default.
(Integer > 0)
IVIEWB A VIEW entry identification number for the back face. See Remark 2. for default.
(Integer > 0)
RADMIDF RADM identification number for front face of surface element. See Remark 2. for
default. (Integer > 0)
RADMIDB RADM identification number for back face of surface element. See Remark 2. for
default. (Integer > 0)
Gi Grid point IDs of grids bounding the surface. (Integer > 0)
Remarks:
1. EID is a unique ID associated with a particular surface element as defined by the grid points.
2. The defaults for TYPE, IVIEWF, IVIEWB, RADMIDF, and RADMIDB may be specified on the
BDYOR entry. If a particular field is blank on both the CHBDYG entry and the BDYOR entry,
then the default is zero.
3. TYPE specifies the kind of element surface; allowed types are: REV, REV1, AREA3, AREA4,
AREA6, and AREA8. See Figure 9-28, Figure 9-29, and Figure 9-30.
• TYPE = REV
Main Index
1384 CHBDYG
Geometric Surface Element Definition (Grid Form)
The “REV” type has two primary grid points that must lie in the x-z plane of the basic coordinate
system with x>0. A midside grid point G3 is optional and supports convection or heat flux from
the edge of the six-noded CTRIAX6 element. The defined area is a conical section with z as the
axis of symmetry. A property entry is required for convection, radiation, or thermal vector flux.
z
G2 n
T
G3
G1
x
y
Figure 9-28 Normal Vector for CHBDYG Element of Type “REV”
.
The unit normal lies in the x-z plane, and is given by
n = ey T ey T .
e y is the unit vector in the y direction.
• TYPE = REV1. The “REV1” type has two primary grid points that must lie in the x-y plane of
the basic coordinate system with x > 0. A midside grid point G3 is optional and supports
convection or heat flux from the edge of the CQUADX (4 or 8 node) and CTRIAX (3 or 6 node)
element. The defined are is a conical section with y as the axis of symmetry. A property entry is
required for convection, radiation, or thermal vector flux.
• TYPE = AREA3, AREA4, AREA6, or AREA8
These types have three and four primary grid points, respectively, that define a triangular or
quadrilateral surface and must be ordered to go around the boundary. A property entry is required
for convection, radiation, or thermal vector flux.
Main Index
CHBDYG 1385
Geometric Surface Element Definition (Grid Form)
G3 G4 G3
G1 G2 G1 G2
AREA3 AREA4
G3 G4 G7 G3
G6 G5 G8 G6
G1 G4 G2 G1 G5 G2
AREA6 AREA8
(Grid points G4 through G6 optional) (Grid points G5 through G8 optional)
Figure 9-29 TYPE Examples
G3 or G4
n
T 1x
G2
G1 T 12
Figure 9-30 Normal Vector for CHBDYG Element of Types “AREAi”
The unit normal vector is given by
T 12 T 1x
n = ----------------------------
T 12 T 1x
(G3 is used for triangles, and G4 is used for quadrilaterals.)
4. For defining the front face, the right-hand rule is used on the sequence G1 to G2 to ... Gn of grid
points.
Main Index
1386 CHBDYG
Geometric Surface Element Definition (Grid Form)
5. If the surface element is to be used in the calculation of view factors, it must have an associated VIEW
entry.
6. All conduction elements to which any boundary condition is to be applied must be individually
identified with one of the surface element entries: CHBDYE, CHBDYG, or CHBDYP.
7. See Remark 9. of CHBDYE for application of boundary conditions using CHBDYG entries and a
discussion of front and back faces.
Main Index
CHBDYP 1387
Geometric Surface Element Definition (Property Form)
CHBDYP Geometric Surface Element Definition (Property Form)
Defines a boundary condition surface element with reference to a PHBDY entry.
Format:
1 2 3 4 5 6 7 8 9 10
CHBDYP EID PID TYPE IVIEWF IVIEWB G1 G2 G0
RADMIDF RADMIDB GMID CE E1 E2 E3
Example:
CHBDYP 2 5 POINT 2 2 101 500
3 3 0.0 0.0 1.0
Describer Meaning
EID Surface element identification number. (Unique (0 < Integer < 100,000,000) among
all element identification numbers.)
PID PHBDY property entry identification numbers. (Integer > 0)
TYPE Surface type. See Remark 3. (Character)
IVIEWF VIEW entry identification number for the front face. (Integer > 0 or blank)
IVIEWB VIEW entry identification number for the back face. (Integer > 0 or blank)
G1, G2 Grid point identification numbers of grids bounding the surface. (Integer > 0)
GO Orientation grid point. (Integer > 0; Default = 0)
RADMIDF RADM entry identification number for front face. (Integer > 0 or blank)
RADMIDB RADM entry identification number for back face. (Integer > 0 or blank)
GMID Grid point identification number of a midside node if it is used with the line type
surface element.
CE Coordinate system for defining orientation vector. (Integer > 0; Default = 0)
Ei Components of the orientation vector in coordinate system CE. The origin of the
orientation vector is grid point G1. (Real or blank)
Remarks:
1. EID is a unique ID associated with a particular surface element as defined by the grid point(s).
2. The defaults for PID, TYPE, IVIEWF, IVIEWB, GO, RADMIDF, RADMIDB, CE, and Ei may be
specified on the BDYOR entry. If a particular field is blank on both the CHBDYP entry and the
BDYOR entry, then the default is zero.
Main Index
1388 CHBDYP
Geometric Surface Element Definition (Property Form)
3. TYPE specifies the kind of element surface; the allowed types are: “POINT,” “LINE,” “ELCYL,”
“FTUBE,” and “TUBE.” For TYPE = “FTUBE” and TYPE = “TUBE,” the geometric orientation
is completely determined by G1 and G2; the GO, CE, E1, E2, and E3 fields are ignored.
• TYPE = “POINT”
TYPE = “POINT” has one primary grid point, requires a property entry, and the normal vector
Vi must be specified if thermal flux is to be used.
V
n
G1
Figure 9-31 Normal Vector for CHBDYP Element of Type “POINT”
(See Remarks 4. and 5.)
The unit normal vector is given by n = V V where V is specified in the Ei field and given in
the basic system at the referenced grid point. See Remarks 4. and 5. for the determination of V .
• TYPE = “LINE,” “FTUBE,” or “TUBE”
The TYPE = “LINE” type has two primary grid points, requires a property entry, and the vector
is required. TYPE = “FTUBE” and TYPE = “TUBE” are similar to TYPE = “LINE” except they
can have linear taper with no automatic view factor calculations. GMID is an option for the
TYPE = “LINE” surface element only and is ignored for TYPE = “FTUBE” and “TUBE”.
G2
GMID
V
n T
G1
Figure 9-32 Normal Vector for CHBDYP Element with TYPE=”LINE”,
TYPE=“FTUBE”, or TYPE=“TUBE” (See Remarks 4. and 5.)
The unit normal lies in the plane V and T , is perpendicular to T , and is given by:
T V T
n = ------------------------------
T V T
Main Index
CHBDYP 1389
Geometric Surface Element Definition (Property Form)
• TYPE = “ELCYL”
TYPE = “ELCYL” (elliptic cylinder) has two connected primary grid points and requires a
property entry. The vector must be nonzero.
n
V
R1
R2
Figure 9-33 Normal Vector for CHBDYP Element of TYPE=“ELCYL”
(See Remarks 4. and 5.)
The same logic is used to determine n as for TYPE = LINE. The “radius” R1 is in the n
direction, and R2 is the perpendicular to n and T (see fields 7 and 8 of PHBDY entry).
4. For TYPE = “POINT,” TYPE = “LINE,” and TYPE = “ELCYL,” geometric orientation is required.
The required information is sought in the following order:
• If GO > 0 is found on the CHBDYP entry, it is used.
• Otherwise, if a nonblank CE is found on the CHBDYP continuation entry, this CE and the
corresponding vectors E1, E2, and E3 are used.
• If neither of the above, the same information is sought in the same way from the BDYOR entry.
• If none of the above apply, a warning message is issued.
5. The geometric orientation can be defined by either GO or the vector E1, E2, E3.
• If GO > zero:
For a TYPE = “POINT” surface, the normal to the front face is the vector from G1 to GO. For
the TYPE = “LINE” surface, the plane passes through G1, G2, GO and the right-hand rule is
used on this sequence to get the normal to the front face. For TYPE = “ELCYL” surface the first
axis of the ellipse lies on the G1, G2, GO plane, and the second axis is normal to this plane. For
TYPE = “FTUBE” or “TUBE” surface, no orientation is required, and GO is superfluous.
• If GO is zero:
For a TYPE = “POINT” surface, the normal to the front face is the orientation vector. For the
TYPE = “LINE” surface, the plane passes through G1, G2, and the orientation vector; the front
face is based on the right-hand rule for the vectors G2-G1 and the orientation vector. For
TYPE = “ELCYL” surface, the first axis of the ellipse lies on the G1, G2, orientation vector plane,
and the second axis is normal to this plane.
6. The continuation entry is optional.
Main Index
1390 CHBDYP
Geometric Surface Element Definition (Property Form)
7. If the surface element is to be used in the calculation of view factors, it must have an associated VIEW
entry.
8. All conduction elements to which any boundary condition is to be applied must be individually
identified with the application of one of the surface element entries: CHBDYE, CHBDYG, or
CHBDYP entries.
Main Index
CHEXA 1391
Six-Sided Solid Element Connection
CHEXA Six-Sided Solid Element Connection
Defines the connections of the six-sided solid element with eight to twenty grid points or the six-sided solid
shell element with eight grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CHEXA EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13 G14
G15 G16 G17 G18 G19 G20
Example:
CHEXA 71 4 3 4 5 6 7 8
9 10 0 0 30 31 53 54
55 56 57 58 59 60
Describer Meaning Type Default
EID Element identification number. (0 < Integer < 100,000,000) Required
PID Property identification number of a PSOLID, Integer > 0 Required
PLSOLID or PCOMPLS entry.
Gi Grid point identification numbers of Integer > 0 or blank Required
connection points.
G18
G7
G6
G19
G15 G17
G14
G20
G8
G2
G10 G5
G16 G3
G11 G13 G9
G4 G12
G1
Figure 9-34 CHEXA Element Connection
Main Index
1392 CHEXA
Six-Sided Solid Element Connection
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Grid points G1 through G4 must be given in consecutive order about one quadrilateral face. G5
through G8 must be on the opposite face with G5 opposite G1, G6 opposite G2, etc.
3. For Nastran conventional element, the edge points, G9 to G20, are optional. Any or all of them may
be deleted. If the ID of any edge connection point is left blank or set to zero (as for G9 and G10 in
the input example), the equations of the element are adjusted to give correct results for the reduced
number of connections. Corner grid points cannot be deleted. The element is an isoparametric
element (with shear correction) in all cases.
Note that for advanced nonlinear elements, partial specification of mid-points is not allowed. i.e.
Either none of the mid-points should be specified or all of the mid points should be specified.
4. Components of stress are output in the material coordinate system except for hyperelastic elements,
which are output in the basic coordinate system. The material coordinate system is defined on the
PSOLID entry.
5. The second continuation is optional.
6. For nonhyperelastic and non-composite elements, the element coordinate system for the CHEXA
element is defined in terms of the three vectors R, S, and T, which join the centroids of opposite faces.
R vector joins the centroids of faces G4-G1-G5-G8 and G3-G2-G6-G7.
S vector joins the centroids of faces G1-G2-G6-G5 and G4-G3-G7-G8.
T vector joins the centroids of faces G1-G2-G3-G4 and G5-G6-G7-G8.
The origin of the coordinate system is located at the intersection of these vectors. The X, Y, and Z
axes of the element coordinate system are chosen as close as possible to the R, S, and T vectors and
point in the same general direction. (Mathematically speaking, the coordinate system is computed in
such a way that if the R, S, and T vectors are described in the element coordinate system a 3 x 3
positive-definite symmetric matrix would be produced.)
Solid elements have both a material and an element coordinate system. Both systems are defined for
the initial geometry, and for geometric nonlinear analysis they will rotate with the element. The
material coordinate system is used to input anisotropic material properties and for stress output. The
material coordinate system is defined by the CORDM field of the PSOLID entry. The element
coordinate system is used for element stiffness integration (reduced shear for example) and optionally
to define the material coordinate system (only if PSOLID,CORDM=-1).
Main Index
CHEXA 1393
Six-Sided Solid Element Connection
T
G7
G6
G8 G5 R
S
G3
G4
G2
G1
Figure 9-35 CHEXA Element R, S, and T Vectors
7. It is recommended that the edge points be located within the middle third of the edge.
8. For hyperelastic elements, the plot codes are specified under the CHEXAFD element name in Item
Codes.
9. By default, all the twelve edges of the element are considered straight unless, any of G9 through G20
are specified.
10. This element may be used:
Element Type Property BEHi Code Integration Scheme Solution Type
Solid PSOLID N/A Refer to IN and ISOP All Solution Sequences
Nastran conventional element. Typically used for small strain, small / large
displacement solutions.
Below are advanced nonlinear elements.
Solid PSOLID+ SOLID L, Q, LRIH and QRI SOL 400
PSLDN1
Typically used for large strain, large displacement solutions in conjunction with
MATEP, MATS1, MATHE, etc.
Solid Shell PSOLID+ SLCOMP ASTN SOL 400
PSLDN1
Typically used for bending dominated large strain, large displacement solutions.
3D Solid PSOLID+ SLCOMP L SOL 400
Gasket PSLDN1
Used for gaskets with MATG.
Main Index
1394 CHEXA
Six-Sided Solid Element Connection
Element Type Property BEHi Code Integration Scheme Solution Type
Solid PCOMPLS SLCOMP L and Q SOL 400 and
Composite SOL 101 to SOL 112
Typically used for solid composite small strain / large strain / small displacement /
large displacement solutions.
Solid Shell PCOMPLS SLCOMP L and Q SOL 400 and
Composite SOL 101 to SOL 112
Typically used for bending dominated solid composite small strain / large strain /
small displacement / large displacement solutions.
11. When this element is used as a three-dimensional eight-node solid shell element or three-dimensional
eight-node composite solid shell element, the user should keep in mind that the layer orientation is
required to be in the element T-direction, when specifying grid order.
12. The internal coordinate system of the element is used internally and is based on eigenvalue techniques
to insure non bias in the element formulation. For stress/strain output this internal coordinate system
(CORDM=-1 on PSOLID entry) is hard to visualize. Thus a CORDM=-2 on the PSOLID is
available as shown in Figure 9-36.
Figure 9-36 PSOLID for CHEXA
Main Index
CIFHEX 1395
Solid InterFace Cohesive Zone Modeling Element
CIFHEX Solid InterFace Cohesive Zone Modeling Element
Linear/Quadratic, twenty-node, three-dimensional interface element used to simulate the onset and progress
of delamination in SOL 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
CIFHEX EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13 G14
G15 G16 G17 G18 G19 G20
Example:
CIFHEX 700 701 456 357 882 889 443 447
162 911
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property number of a PCOHE entry. (Integer > 0)
G1-G8 Identification number of connected corner grid points. Required data for all eight
corner grid points. (Unique Integer > 0)
G9-G12 Identification number of connected edge grid points. Optional data for bottom and top
G17-G20 edge grid points. (Unique Integer > 0)
G13-G16 Identification number of connected midside grid points. Optional data for midside grid
points used only to make the element compatible with twenty-noded hexahedral
elements. (Unique Integer > 0)
Remarks:
1. Element identification numbers should be unique with respect to all other element ID’s of any kind.
2. Grid points Gi must be numbered as shown in the following figure. Specify either G1-G8, or all G1-
G20.
3. The element is typically used to model the interface between different materials, where G1, G9, G2,
G10, G3, G11, G4 and G12 correspond to one side (called the bottom) and G5, G17, G6, G18, G7,
G19, and G20 correspond to the other side (called the top). The stress components are one normal
and two shear tractions. When only G1-G8 are specified, the element is linear. When in addition to
G1-G8, G9-G12, G17-G20 are specified, the element is quadratic.
4. The corresponding deformations are relative displacements between the top and bottom edge of the
element.
Main Index
1396 CIFHEX
Solid InterFace Cohesive Zone Modeling Element
5. The element is allowed to be infinitesimally thin; in which case edges defined by grids G1-G4 and
G5-G8 may coincide.
8
16
4 19
20
v1 12
11
7
˜ v3 15
˜ 3
5 18
13 v2
y 1
17
˜ 10
9 6
14
2
x
z
6. This element does not support thermal load. No thermal strain will be generated.
Main Index
CIFPENT 1397
Solid InterFace Cohesive Zone Modeling Element
CIFPENT Solid InterFace Cohesive Zone Modeling Element
Linear/Quadratic, fifteen-node, three-dimensional interface elelement used to simulate the onset and
progress of delamination in SOL 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
CIFPENT EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13 G14
G15
Example:
CIFPENT 700 701 456 357 882 889 443 447
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property number of a PCOHE entry. (Integer > 0)
G1-G6 Identification number of connected corner grid points. Required data for all four corner
grid points. (Unique Integer > 0)
G7-G9 Identification number of connected edge grid points. Optional data for bottom and top
G13-G15 edge grid points. (Unique Integer > 0)
G10-G12 Identification number of connected midside grid points. Optional data for midside grid
points used only to make the element compatible with fifteen-noded pentahedral
elements. (Unique Integer > 0)
Remarks:
1. Element identification numbers should be unique with respect to all other element ID’s of any kind.
2. Grid points Gi must be numbered as shown in the following figure. Specify either G1-G6 or all G1-
G15.
3. The element is typically used to model the interface between different materials, where G1, G7, G2,
G8, G3 and G9 correspond to one side (called the bottom) and G4, G13, G5, G14, G6, and G15
correspond to the other side (called the top). The stress components are one normal and one shear
tractions. When only G1-G6 are specified, the element is linear. When in addition to G1-G6, G7-
G9, G13-G15 are specified, the element is quadratic.
4. The corresponding deformations are relative displacements between the top and bottom edge of the
element.
Main Index
1398 CIFPENT
Solid InterFace Cohesive Zone Modeling Element
5. The element is allowed to be infinitesimally thin; in which case edges defined by grids G1-G3 and
G4-G6 may coincide.
v1 6
˜ v3 15 12
˜ 3
4 9 14
10
y 1 13 v2 8
˜
7 5
11
2
x
z
6. This element does not support thermal load. No thermal strain will be generated.
Main Index
CIFQDX 1399
Axisymmetric InterFace Cohesive Zone Modeling Element
CIFQDX Axisymmetric InterFace Cohesive Zone Modeling Element
Linear/Quadratic, eight-node, axisymmetric interface element used to simulate the onset and progress of
delamination in SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
CIFQDX EID PID G1 G2 G3 G4 G5 G6
G7 G8
Example:
CIFQDX 700 701 456 357 882 889 443 447
1612 911
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property number of a PCOHE entry. (Integer > 0)
G1-G4 Identification number of connected corner grid points. Required data for all four corner
grid points. (Unique Integer > 0)
G5, G7 Identification number of connected edge grid points. Optional data for bottom and top
edge grid points. (Unique Integer > 0)
G6, G8 Identification number of connected edge grid points. Optional data for side grid points
used only to make the element compatible with eight-noded quadrilateral axisymmetric
elements. (Unique Integer > 0)
Remarks:
1. Element identification numbers should be unique with respect to all other element ID’s of any kind.
2. Grid points Gi must be numbered as shown in the following figure.
3. The element is typically used to model the interface between different materials, where G1, G5, and
G2 correspond to one side (called the bottom) and G3, G7, and G4 correspond to the other side
(called the top). The stress components are one normal and one shear traction. Then only G1-G4 are
specified, the element is linear. When in addition to G1-G4, G5 and G7 are specified, the element is
quadratic.
4. The corresponding deformation are relative displacements between the top and bottom edge of the
element.
5. The element is allowed to be infinitesimally thin; in which case edges G1-G5-G2 and G3-G7-G4
may coincide.
6. The element must lie in the x-y plane of the basic system. Coordinate r is parallel to the x-basic and
coordinate z is parallel to y-basic.
Main Index
1400 CIFQDX
Axisymmetric InterFace Cohesive Zone Modeling Element
7. This element does not support thermal load. No thermal strain will be generated.
Main Index
CIFQUAD 1401
Planar InterFace Cohesive Zone Modeling Element
CIFQUAD Planar InterFace Cohesive Zone Modeling Element
Linear/Quadratic, eight-noded planar interface element used to simulate the onset and progress of
delamination in SOL 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
CIFQUAD EID PID G1 G2 G3 G4 G5 G6
G7 G8
Example:
CIFQUAD 700 701 456 357 882 889 443 447
1612 911
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property number of a PCOHE entry. (Integer > 0)
G1-G4 Identification number of connected corner grid points. Required data for all four corner
grid points. (Unique Integer > 0)
G5, G7 Identification number of connected edge grid points. Optional data for bottom and top
edge grid points. (Unique Integer > 0)
G6, G8 Identification number of connected edge grid points. Optional data for side grid points
used only to make the element compatible with eight-noded quadrilateral elements.
(Unique Integer > 0)
Remarks:
1. Element identification numbers should be unique with respect to all other element ID’s of any kind.
2. Grid points Gi must be numbered as shown in the following figure.
3. The element is typically used to model the interface between different materials, where G1, G5, and
G2 correspond to one side (called the bottom) and G3, G7, and G4 correspond to the other side
(called the top). The stress components are one normal and one shear traction. Then only G1-G4 are
specified, the element is linear. When in addition to G1-G4, G5 and G7 are specified, the element is
quadratic.
4. The corresponding deformation are relative displacements between the top and bottom edge of the
element.
5. The element is allowed to be infinitesimally thin; in which case edges G1-G5-G2 and G3-G7-G4
may coincide.
Main Index
1402 CIFQUAD
Planar InterFace Cohesive Zone Modeling Element
6. The element must lie in the x-y plane of the basic system.
7. This element does not support thermal load. No thermal strain will be generated.
Main Index
CINTC 1403
Line Interface Element Connection
CINTC Line Interface Element Connection
Defines a line interface element with specified boundaries.
Note that CINTC is not supported in NLPERF SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
CINTC EID TYPE
LIST = (BID1(INTP1), BID2(INTP2),...,BIDn(INTPn))
Example:
CINTC 1001 GRDLIS
T
LIST=(101,102(Q),-103(Q),104(L))
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
TYPE Connectivity. If TYPE = “GRDLIST” or blank (Default), the user will specify the
boundaries via Bulk Data entry, GMBNDC. See Remark 2. (Character; Default =
“GRDLIST”)
BIDi Boundary curve identification number, referenced to Bulk Data entry, GMBNDC. See
Remark 2. ( Integer 0 )
INTPi Interpolation scheme. (Character; Default = “L”)
INTP = “L”: Linear interpolation;
INTP = “Q”: Quadratic interpolation.
Remarks:
1. Line interface element identification numbers must be unique with respect to all other line interface
elements.
2. There must be at least two BIDi specified. If all BIDi are positive, by default, the degrees of freedom
associated with the grids on the boundary represented by the first BID will be taken as the
independent (n-set), and the degrees of freedom with the grids on the rest of boundaries are taken as
the dependent (m-set). If there is a single negative BID, the degrees of freedom associated with the
grids on the boundary represented by this BID will be taken as the independent (n-set), and the rest
of the degrees of freedom with other boundaries are used as the dependent (m-set). If there are two
or more negative BIDs, the degrees of freedom with the first negative one will be taken as the
independent.
3. Forces of multipoint constraints may be recovered with the MPCFORCE Case Control command.
4. The m-set degrees of freedom specified on the boundary grids by this entry may not be specified by
other entries that define mutually exclusive sets.
Main Index
1404 CLOAD
Static Load Combination for Superelement Loads (Superposition)
CLOAD Static Load Combination for Superelement Loads (Superposition)
Defines a static load as a linear combination of previously calculated superelement loads defined by the LSEQ
entry in nonlinear static analysis (SOLs 106 or 153).
Format:
1 2 3 4 5 6 7 8 9 10
CLOAD CID S S1 IDV1 S2 IDV2 S3 IDV3
S4 IDV4 -etc.-
Example:
CLOAD 25 1.0 25.0 10 -1.0 101 2.2-1 604
-62.0 62
Describer Meaning
CID Combination identification number. (Integer > 0)
S Scale factor. (Real)
Si Scale factors. (Real)
IDVi Identification numbers of load vectors (EXCITEID of a selected LSEQ entry)
calculated for a superelement loads entry. (Integer > 0)
Remarks:
1. The CLOAD entry must be selected in the residual solution subcases of the Case Control with
CLOAD = CID and must be used if loads are applied to upstream superelements in SOL 106 or 153.
2. The load vector defined is given by P = S Si PIDVi
i
3. The IDVi field refers to a previously calculated load vector for the superelement via the LSEQ
approach. That is, a LOADSET keyword must have been selected in Case Control that in turn refers
to one or more LSEQ entries in the Bulk Data Section. The IDVi refers to the EXCITEID of such
LSEQ entries. For more details, see the Case Control commands LSEQ Bulk Data entry and the
LOADSET (Case).
4. In the CID or IDV fields, a CLOAD entry may not reference an identification number defined by
another CLOAD entry.
Main Index
CMARKB2 1405
Two-Noded Marker Connectivity Definition
CMARKB2 Two-Noded Marker Connectivity Definition
Defines a 2-noded marker beam element by means of connecting two grid points. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CMARKB2 ID PID G1 G2
Example:
CMARKB2 7 1 9 10
Describer Meaning
ID Unique element number. (Integer > 0; Required)
PID Property ID referring to a PMARKER entry. (Integer > 0; Required)
G1 Grid point number connectivity 1. (Integer > 0; Required)
G2 Grid point number connectivity 2. (Integer > 0; Required)
Remarks:
1. A CMARKB2 element may refer to two types of grid points:
a. Structural grid points, thus grid points that are part of the connectivity of an element
b. Free grid points in space. These grid points do not have mass associated with them. The motion
of these grid points is specified by the PMARKER property
2. The ID must be unique in the model and may not be used as structural element ID.
Main Index
1406 CMARKN1
One-Noded Marker Connectivity Definition
CMARKN1 One-Noded Marker Connectivity Definition
Defines a 1-noded marker element on a grid point. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CMARKN1 ID PID G1
Example:
CMARKN1 7 1 9
Describer Meaning
ID Unique element number. (Integer > 0; Required)
PID Property ID referring to a PMARKER entry. (Integer > 0; Required)
G Grid point number. (Integer > 0; Required)
Remarks:
1. A CMARKB2 element may refer to two types of grid points:
a. Structural grid points, thus grid points that are part of the connectivity of an element
b. Free grid points in space. These grid points do not have mass associated with them. The motion
of these grid points is specified by the PMARKER property
2. The ID must be unique in the model and may not be used as structural element ID.
Main Index
CMASS1 1407
Scalar Mass Connection
CMASS1 Scalar Mass Connection
Defines a scalar mass element.
Format:
1 2 3 4 5 6 7 8 9 10
CMASS1 EID PID G1 C1 G2 C2
Example:
CMASS1 32 6 2 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PMASS entry. (Integer > 0; Default = EID)
G1, G2 Geometric grid or scalar point identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; blank or zero if scalar point)
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero. If only scalar points and/or ground are involved, it is more efficient to use the
CMASS3 entry.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2) must not be coincident.
4. For a discussion of the scalar elements, see the MSC Nastran Reference Guide, Section 5.6.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry.
7. Scalar elements input coupled mass matrices when the second pair of fields is entered. When
uncoupled point masses are desired input only the first pair of fields. When a coupled mass matrix is
requested the submatrix added has M on the diagonal, and -M on the off-diagonal. The element is
not checked for internal constraints, which is the user’s responsibility if desired. There are instances
where elements with internal constraints are desired, although not frequently. To identify the
presence of internal constraints caused by coupled mass, inspect GPWG output, OLOAD output due
to GRAV loads, and rigid body modes of free structures. Some forms of coupled mass will cause
coupling of rigid body translational mass terms in GPWG output, and poor rigid body modes in
modal analysis.
Main Index
1408 CMASS2
Scalar Mass Property and Connection
CMASS2 Scalar Mass Property and Connection
Defines a scalar mass element without reference to a property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CMASS2 EID M G1 C1 G2 C2
Example:
CMASS2 32 9.25 6 1
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
M Value of the scalar mass. (Real)
G1, G2 Geometric grid or scalar point identification number. (Integer > 0)
C1, C2 Component number. (0 < Integer < 6; blank or zero if scalar point)
Remarks:
1. Scalar points may be used for G1 and/or G2, in which case the corresponding C1 and/or C2 must be
zero or blank. Zero or blank may be used to indicate a grounded terminal G1 or G2 with a
corresponding blank or zero C1 or C2. A grounded terminal is a point with a displacement that is
constrained to zero. If only scalar points and/or ground are involved, it is more efficient to use the
CMASS4 entry.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. The two connection points (G1, C1) and (G2, C2) must be distinct. Except in unusual
circumstances, one of them will be a grounded terminal with blank entries for Gi and Ci.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
6. If Gi refers to a grid point then Ci refers to degrees-of-freedom(s) in the displacement coordinate
system specified by CD on the GRID entry.
7. See Remark 7 for CMASS1.
Main Index
CMASS3 1409
Scalar Mass Connection to Scalar Points Only
CMASS3 Scalar Mass Connection to Scalar Points Only
Defines a scalar mass element that is connected only to scalar points.
Format:
1 2 3 4 5 6 7 8 9 10
CMASS3 EID PID S1 S2
Example:
CMASS3 13 42 62
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PMASS entry. (Integer > 0; Default = EID)
S1, S2 Scalar point identification numbers. (Integer > 0; S1 S2 )
Remarks:
1. S1 or S2 may be blank or zero, indicating a constrained coordinate.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. Only one scalar mass element may be defined on a single entry.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
Main Index
1410 CMASS4
Scalar Mass Property and Connection to Scalar Points Only
CMASS4 Scalar Mass Property and Connection to Scalar Points Only
Defines a scalar mass element that is connected only to scalar points, without reference to a property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CMASS4 EID M S1 S2
Example:
CMASS4 23 14.92 23
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
M Scalar mass value. (Real)
S1, S2 Scalar point identification numbers. (Integer > 0; S1 S2 )
Remarks:
1. S1 or S2 may be blank or zero, indicating a constrained coordinate. This is the usual case.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. Only one scalar mass element may be defined on a single entry.
4. For a discussion of the scalar elements, see Scalar Elements (CELASi, CMASSi, CDAMPi) in the MSC Nastran
Reference Guide.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.
Main Index
1410 COHFRIC
Cohesive Friction
Entries CO - CY
COHFRIC Cohesive Friction
Allows friction and sticking during tensile conditions at the coupling surface. Use SOL700 only.
Format:
COHFRIC CID MAXSTRS FRIC REFVEL
Example:
COHFRIC 112 8e+10 8e+5 2
Describer Meaning
CID Unique number of a COHFRIC entry. (Integer>0; required)
MAXSTRS Maximal normal stress. Allows tensile stresses at the coupling surface as long as the
normal stress does not exceed MAXSTRS. (Real ≥ 0.0; default=0.0)
FRIC Friction stress under tensile conditions. (Real ≥ 0.0; default=0.0)
REFVEL Reference value for velocity. (Real ≥ 0.0; default=0.0)
Remarks:
1. If the cohesive friction parameters is uniform across the coupling surface then DYPARAM,
COHESION can be used instead.
2. During tension any relative tangential velocity between coupling surface and Eulerian material will
V
REL tan gential
yield a shear stress whose magnitude equals Fric min 1 -------------------------------------- . This is a viscous-
REFVEL
like friction law.
3. This shear force opposes the relative tangential movement along the coupling surface.
Main Index
COMPUDS 1411
Orthotropic Failure Model that allows to model Property Degradation
COMPUDS Orthotropic Failure Model that allows to model Property Degradation
Defines an orthotropic failure model for shell composites specified by a user subroutine. Used in SOL700
only.
Format:
1 2 3 4 5 6 7 8 9 10
COMPUDS MID GROUP UNAME +
+ E1 E2 N12 G12 G1,Z G2,Z RHO +
+ NV S ALPHA TRSFAIL F12 +
+ XT XT YT YC PFD VALUE PFDST +
+ FBTEN FBCOM MXTEN MXCOM MXSHR +
+ PRDFT PRDFC PRDMT PRDMC PRDSH +
Example:
In FMS Section of the MSC Nastran input stream:
CONNECT SERVICE excomp1 ' SCA.MDSolver.Obj.Uds.Dytran.Materials '
In Bulk Data:
COMPUD 1 EXCOMP1 +
S
+ 30E6 1.0E6 0.3 2.0E6 3.0E6 1.5E6 0.056 +
+ 5 100
+ 200 150 100 110
Field Contents
MID Unique material identification number. (Integer > 0; required)
GROUP The group name used for the FMS section CONNECT SERVICE statement.
(Character; required).
UNAME User subroutine name associated with the entry. (Character; default = blank).
E1 Modulus of elasticity in longitudinal direction (also defined as fiber direction or one-
direction). (Real > 0.0; required)
E2 Modulus of elasticity in lateral direction (also defined as matrix direction or two-
direction). (Real > 0.0; required)
Main Index
1412 COMPUDS
Orthotropic Failure Model that allows to model Property Degradation
Field Contents
N12 Poisson's ratio ( 2/ 1 for uniaxial loading in one-direction). Note that 21 = 1/ 2 for
uniaxial loading in two-direction is related to 12, E1, E2 by the relation 12 E2 = 21 E1.
(Real > 0.0; required)
G12 In-plane shear modulus R. (Real > 0.0; required)
G1,Z Transverse shear modulus for shear in 1-Z plane. (Real > 0.0; default= G12)
RHO Mass density. (R > 0.0; required)
NV Number of additional history variables for a user model. See Remark 8. (0 < Integer < 10;
default=0)
S Failure stress for in-plane shear. (Real ≥ 0.0; default=0.0)
ALPHA Nonlinear shear coefficient. (Real ≥ 0.0; default=0.0)
TRSFAIL Transverse shear failure. (Character; default = SUBL)
ELEM: Failure if element fails
SUBL: Failure if sublayer fails
F12 Interaction term in Tsai-Wu theory. (Real; default=0.0)
XT, XC Tensile compressive failure stress in the large structural direction. (Real > 0.0; required)
YT, YC Tensile compressive failure stress in the lateral direction. (Real > 0.0; required)
PFD Post-failure degradation model. (Character; default = STEPS)
STEPS: Degrade stresses by time steps
TIME: Degrade stresses by time
VELOC: Degrade stresses by velocity
VALUE Depending on PFD, VALUE gives the number of time steps, time interval, or
propagation velocity. (Integer or Real; default=100)
PFDST Post-failure degradation start. (Character; default=INDV)
INDV Stresses are degraded per distinct failure mode.
ALL Stresses are degraded if all elastic constants are zero.
FBTEN,FBCO Failure modes in fiber, matrix direction, and theory failure. (Character; default=blank)
N,MXTEN,M
XCOM,MXS
HR
PRDFT Property degradation due to fiber-tension failure. (Integer; default=1111)
Main Index
COMPUDS 1413
Orthotropic Failure Model that allows to model Property Degradation
Field Contents
PRDFC Property degradation due to fiber-compression failure. (Integer; default=1010)
PRDMT Property degradation due to matrix-tension failure. (Integer; default=0110)
PRDMC Property degradation due to matrix-compression failure. (Integer; default=0110)
PRDSH Property degradation due to in-plane shear failure. (Integer; default=0001)
Remarks:
11. Please check MAT8 and MAT8A cards about the details of each field. The field definition is identical
as MAT8 and MAT8A.
12. UNAME can be:
Subroutine Name Function
EXCOMP User defined orthotropic material models for shell composite
Main Index
1414 CONCTL
Parameter SWLDPRM override for CFAST, CSEAM, and CWELD Connector Elements
CONCTL Parameter SWLDPRM override for CFAST, CSEAM, and CWELD Connector
Elements
This entry provides local connector search algorithm control to override SWLDPRM values.
Format:
1 2 3 4 5 6 7 8 9 10
CONCTL SET3ID PARAM1 VALUE1 PARAM2 VALUE2 PARAM3 VALUE3
PARAM4 VALUE5 PARAM4 VALUE5 -etc.-
Example:
CONCTL 75 PROJTOL 0.2 PRTSW 1 GSMOVE 3
NREDIA 2
CONCTL 83 MOVGAB 1
Describer Meaning
SET3ID The ID of a SET3 entry using (DES= ELEM) to identify a group of connector elements.
(Integer>0)
PARAMi Name of the connector parameter. Allowable names are listed in Table 8-62 of
SWLDPRM. (Character)
VALUEi Value of the parameter. See Table 8-62 of SWLDPRM (Real or Integer)
Remarks:
1. Multiple CONCTL entries are allowed and ALL appearing will be used. If the user supplies a
PARAMi, VALUEi that refers to specific Element on one CONCTL entry and a same PARAMi with
VALUEj that refers to the same specific Element on another CONCTL, a fatal message will be issued.
2. For a given connector element ID, this entry will override the global default set by the SWLDPRM
entry.
3. The parameter CHKRUN can only be set on SWLDPRM and will be ignored on CONCTL entries.
4. A user fatal will be issued if DES on the SET3 entry is not "ELEM".
Main Index
CONM1 1415
Concentrated Mass Element Connection, General Form
CONM1 Concentrated Mass Element Connection, General Form
Defines a 6 x 6 symmetric mass matrix at a geometric grid point.
Format:
1 2 3 4 5 6 7 8 9 10
CONM1 EID G CID M11 M21 M22 M31 M32
M33 M41 M42 M43 M44 M51 M52 M53
M54 M55 M61 M62 M63 M64 M65 M66
Example:
CONM1 2 22 2 2.9 6.3
4.8 28.6
28.6 28.6
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000). See Remark 2.
G Grid point identification number. (Integer > 0). See Remark 3.
CID Coordinate system identification number for the mass matrix. (Integer > 0)
Mij Mass matrix values. (Real)
Remarks:
1. For a less general means of defining concentrated mass at grid points, see the CONM2 entry
description.
2. Element identification numbers should be unique with respect to all other element identification
numbers.
3. Unlike the CONM2 entry, the CONM1 entry does not allow for the specification of concentrated
mass at harmonic structural grid points. Therefore, grid point G must necessarily be a non-harmonic
structural grid point.
Main Index
1416 CONM2
Concentrated Mass Element Connection, Rigid Body Form
CONM2 Concentrated Mass Element Connection, Rigid Body Form
Defines a concentrated mass at a grid point.
Format:
1 2 3 4 5 6 7 8 9 10
CONM2 EID G CID M X1 X2 X3
I11 I21 I22 I31 I32 I33
Example:
CONM2 2 15 6 49.7
16.2 16.2 7.8
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000). See Remark 1.
G Grid point identification number. (Integer > 0). See Remark 7.
CID Coordinate system identification number. For CID of -1; see X1, X2, X3 below.
(Integer > -1; Default = 0). See Remarks 4., 6. and 7.
M Mass value. (Real). See Remarks 5. and 7.
X1, X2, X3 Offset distances from the grid point to the center of gravity of the mass in the
coordinate system defined in field 4, unless CID = -1, in which case X1, X2, X3 are the
coordinates, not offsets, of the center of gravity of the mass in the basic coordinate
system. (Real). See Remarks 4., 5., 6. and 7.
Iij Mass moments of inertia measured at the mass center of gravity in the coordinate
system defined by field 4. If CID = -1, the basic coordinate system is implied. (Real).
See Remarks 4., 5. and 7.
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. For a more general means of defining concentrated mass at grid points, see the CONM1 entry
description.
3. The continuation is optional.
4. If CID = -1, offsets are internally computed as the difference between the grid point location and X1,
X2, X3. The grid point locations may be defined in a nonbasic coordinate system. In this case, the
values of Iij must be in a coordinate system that parallels the basic coordinate system.
5. The form of the inertia matrix about its center of gravity is taken as:
Main Index
CONM2 1417
Concentrated Mass Element Connection, Rigid Body Form
M
M symmetric
M
I11
– I21 I22
– I31 – I32 I33
where
M =
dV
2 2
I11 =
x2 + x3 dV
2 2
I22 =
x1 + x3 dV
2 2
I33 =
x1 + x2 dV
I21 =
x1 x2 dV
I31 =
x1 x3 dV
I32 =
x2 x3 dV
and x 1 x 2 x 3 are components of distance from the center of gravity in the coordinate system
defined in field 4. The negative signs for the off-diagonal terms are supplied automatically. A warning
message is issued if the inertia matrix is non-positive definite, since this may cause fatal errors in
dynamic analysis modules.
6. If CID > 0, then X1, X2, and X3 are defined by a local Cartesian system, even if CID references a
spherical or cylindrical coordinate system. This is similar to the manner in which displacement
coordinate systems are defined.
7. MSC Nastran contains two kinds of structural grid points, namely, non-harmonic structural grid
points and harmonic structural grid points. The former have the standard three translational and
three rotational degrees of freedom while the latter have three symmetric components and three anti-
symmetric components dependent on the harmonic value.
Main Index
1418 CONM2
Concentrated Mass Element Connection, Rigid Body Form
Harmonic grid points are identified automatically as the grid points listed on CQUADX and
CTRIAX element entries that are associated with PAXSYMH entries.
For a harmonic grid point, the mass value M is the total mass. This value is not to be multiplied by
2. The mass matrix computed for harmonic grids is dependent on the harmonic value associated
with the PAXSYMH entry and will be automatically determined by the code. Only harmonic values
of 0 and 1 have contributions to grid point weight generator type calculations.
Any values specified in the CID, X1, X2, X3, I11, I21, I22, I31, I32, or I33 fields are ignored for a
harmonic grid.
Main Index
CONROD 1419
Rod Element Property and Connection
CONROD Rod Element Property and Connection
Defines a rod element without reference to a property entry.
Format:
1 2 3 4 5 6 7 8 9 10
CONROD EID G1 G2 MID A J C NSM
Example:
CONROD 2 16 17 4 2.69
Describer Meaning
EID Unique element identification number. (0 < Integer < 100,000,000)
G1, G2 Grid point identification numbers of connection points. (Integer > 0; G1 ≠ G2)
MID Material identification number. (Integer > 0)
A Area of the rod. (Real)
J Torsional constant. (Real)
C Coefficient for torsional stress determination. (Real)
NSM Nonstructural mass per unit length. (Real)
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. For structural problems, MID must reference a MAT1 material entry.
3. For heat transfer problems, MID must reference a MAT4 or MAT5 material entry.
X
T
P
G2
G1
P
T
Figure 9-37 CONROD Element Forces and Moments
Main Index
1420 CONTRLT
Thermal Control Element for Heat Transfer Analysis
CONTRLT Thermal Control Element for Heat Transfer Analysis
Defines the control mechanism for QVECT, QVOL, QBDY3, RADBC, CONV, and CONVM in heat
transfer analysis (SOL 159 and SOL 400 with analysis=htran).
Format:
1 2 3 4 5 6 7 8 9 10
CONTRLT ID SENSOR SFORM CTYPE PL PH PTYPE PZERO
DT DELAY TAUC
Example:
CONTRLT 100 20 T TSTAT 68. 73. 7 1.
0.1 0.01 0.
Describer Meaning
ID Controller identification node. See Remark 1. (Integer > 0; Required)
SENSOR Grid or scalar point ID of sensor. See Remark 2. (Integer > 0; Required)
SFORM Sensor output form. See Remark 3. (Character, T; Default = T)
CTYPE Control type. See Remark 4. (Character, Default TSTAT)
PL Minimum temperature. For PTYPE 9 through 11, set temperature. See Remark 5.
(Real; Required)
PH Maximum temperature. For PTYPE 9 through 11, unused. See Remark 5. (Real;
Required)
PTYPE Process type. See Remark 5. (Integer 1 through 11, 1 through 6 already defined;
no Default)
7 Bang-bang (a thermostat that is either on or off, a special case of a bang-
bang controller)
8 Proportional
9 Steady-state (special routine for steady state models)
10 Classical PID (proportional-integral-differential) and does not include
the time derivative of the set point )
11 Standard PID (Includes the time derivative of the set point)
PZERO Initial controller value. See Remark 4. (0. < Real < 1.; Default = 0)
DT Monitoring time interval or sampling period. (Real > 0.; Default = 0)
DELAY Time delay after the switch is triggered or time for delayed control action in PID
control. (Real > 0.; Default = 0.0)
TAUC Decay time constant for actuator response. (Real > 0.; Default = 0.0)
Main Index
CONTRLT 1421
Thermal Control Element for Heat Transfer Analysis
Remarks:
1. The CONTRLT ID is referenced by CNTRLND entry identified on any of the CONV, CONVM,
RADBC, QVECT, QVOL, and QBDY3 Bulk Data entries. If any grid or scalar point ID is the same
as the CONTRLT ID, then the combined logic associated with the controller and the control node
will be in force for the LBC referenced. Any number of CONTRLT statements may exist in a single
model.
2. Sensor point, where a feedback temperature or rate of change of temperature is measured. May be a
dependent DOF in a MPC relationship.
3. Sensor output may only be temperature (T)
4. Control type can only be TSTAT. The PZERO field cannot have any other value but 0.0 or 1.0.
5. The upper and lower limit values (PL and PH) define a dead band for a thermostat. The available
thermostat controller (TSTAT) formats are (PTYPE = 1 through 6).
On
On Off Off
1 Classical Heating
Thermostat
Sensor
PL PH Value
On
Off Off On
2 Classical Cooling
Thermostat
Sensor
PL PH Value
On
Off Off On
3
Sensor
PL PH Value
Main Index
1422 CONTRLT
Thermal Control Element for Heat Transfer Analysis
On
On Off Off
4
Sensor
PL PH Value
On Off On
5
Sensor
PL PH Value
Off On Off
6
Sensor
PL PH Value
Main Index
CONV 1423
Heat Boundary Element Free Convection Entry
CONV Heat Boundary Element Free Convection Entry
Specifies a free convection boundary condition for heat transfer analysis through connection to a surface
element (CHBDYi entry).
Format:
1 2 3 4 5 6 7 8 9 10
CONV EID PCONID FLMND CNTRLND TA1 TA2 TA3 TA4
TA5 TA6 TA7 TA8
Example:
CONV 2 101 3 201 301
Describer Meaning
EID CHBDYG, CHBDYE, or CHBDYP surface element identification number.
(0 < Integer < 100,000,000)
PCONID Convection property identification number of a PCONV entry. (Integer > 0)
FLMND Point for film convection fluid property temperature. (Integer > 0; Default = 0)
CNTRLND Control point for free convection boundary condition. (Integer > 0; Default = 0)
TAi Ambient points used for convection. (Integer > 0 for TA1 and Integer > 0 for TA2
through TA8; Default for TA2 through TA8 is TA1.)
Remarks:
1. The basic exchange relationship can be expressed in one of the following forms:
EXPF
• q = H T – TAMB T – TAMB , CNTRLND = 0
EXPF
• q = H u CNTRLND T – TAMB T – TAMB , CNTRLND 0
EXPF EXPF
• q = HT – TAMB , CNTRLND = 0
EXPF EXPF
• q = H u CNTRLND T – TAMB , CNTRLND 0
EXPF is specified on the PCONV entry.
(See PCONV entry for additional clarification of forms.)
2. The continuation entry is not required.
3. CONV is used with an CHBDYi (CHBDYG, CHBDYE, or CHBDYP) entry having the same EID.
Main Index
1424 CONV
Heat Boundary Element Free Convection Entry
4. The temperature of the film convection point provides the look up temperature to determine the
convection film coefficient. If FLMND=0, the reference temperature has several options. It can be
the average of surface and ambient temperatures, the surface temperature, or the ambient
temperature, as defined in the FORM field of the PCONV Bulk Data entry.
5. If only one ambient point is specified then all the ambient points are assumed to have the same
temperature. If midside ambient points are missing, the temperature of these points is assumed to be
the average of the connecting corner points.
6. See the Bulk Data entry, PCONV, for an explanation of the mathematical relationships involved in free
convection and the reference temperature for convection film coefficient.
Main Index
CONVM 1425
Heat Boundary Element Forced Convection Entry
CONVM Heat Boundary Element Forced Convection Entry
Specifies a forced convection boundary condition for heat transfer analysis through connection to a surface
element (CHBDYi entry).
Format:
1 2 3 4 5 6 7 8 9 10
CONVM EID PCONID FLMND CNTMDOT TA1 TA2 Mdot
Example:
CONVM 101 1 201 301 20 21
Describer Meaning
EID CHBDYP element identification number. (0 < Integer < 100,000,000)
PCONID Convection property identification number of a PCONVM entry. (Integer > 0)
FLMND Point used for fluid film temperature. (Integer > 0; Default = 0)
CNTMDOT Control point used for controlling mass flow. (Integer 0 or Blank). Blank or zero is
only allowed when Mdot > 0.0. See Remark 3.
TA1, TA2 Ambient points used for convection. (Integer > 0 for TA1 and Integer > 0 for TA2;
Default for TA2 is TA1.)
Mdot A multiplier for mass flow rate in case there is no point associated with the CNTRLND
field. (Real 0.0; Default = 1.0 if CNTMDOT > 0). See Remark 3.)
Remarks:
1. CONVM is used with an CHBDYP entry of type FTUBE having the same EID.
2. The temperature of the fluid film point may be specified to determine the material properties for the
fluid. If FLMND=0, the reference temperature has several options. It can be the average of surface
and ambient temperatures, the surface temperatures, or the ambient temperature, as defined in the
FORM field of the PCONVM Bulk Data entry.
3. The CNTMDOT has a dual function. It can reference the ID of the CONTRLT Bulk Data entry to
activate a thermostat controlled flux transfer. It can also reference a GRID or a scalar point which is
set to the desired mass flow rate (mdot) to effect the advection of energy downstream at an
mdot · Cp · T rate. If CNTMDOT is zero or is not specified (blank field), then the mass flow rate
must be specified on the Mdot field (8th field).
Main Index
1426 CONVM
Heat Boundary Element Forced Convection Entry
Case 1: Define a thermostat controller using the CONTRLT Bulk Data entry.
Total mass flow rate = CONTRLT · Mdot · CNTMDOT
where CONTRLT is the grid ID on the 2nd field of the CONTRLT Bulk Data entry that ties the
mass flow rate through this sensor grid.
Mdot is the 8th field of the CONVM Bulk Data entry.
CNTMDOT is the grid ID that has a mass flow rate associated with it.
Example: The thermostat controller controls GRID 5 (sensor grid) from 250 degrees to 300 degrees. If the
temperature exceeds 300 degrees, then the mass flow is turned ON. If the temperature is below 250 degrees,
then the mass flow is turned OFF.
CONTRLT,5,2,T,TSTAT,250.0,300.0,1,1.0 +
+,0.0,0.0,0.0
CONVM,100001,1,,5,4
Note that GRID 5 is also specified on the 5th field of the CONVM Bulk Data entry.
Case 2: There is no CONTRLT Bulk Data entry (more general case).
Total mass flow rate = Mdot · CNTMDOT
If the CNTMDOT (the 5th field of the CONVM Bulk Data entry) is specified, then the default Mdot value
is 1.0 and the mass flow rate is defined through CNTMDOT.
Example: Define a constant mass flow rate of 0.5 through CNTMDOT.
CONVM,100001,1,,5,4
SPC,1,5,1,0.5
To specify a time-varying mass flow rate, replace the SPC Bulk Data entry by TEMPBC,TRAN for SOL 159
or by SPC1 and SPCD for SOL 400.
For SOL 159:
TEMPBC,2,TRAN,1.0,5
DLOAD,700,1.0,1.0,9
TLOAD1,9,2,,,121
TABLED1,121
,0.0,0.3,100.0,0.5,endt
For SOL 400:
SPC = 111 (Case Control command)
SPC1,111,,5
SPCD,2,5,,1.0
DLOAD,700,1.0,1.0,9
TLOAD1,9,2,,1,121
TABLED1,121
,0.0,0.3,100.0,0.5,endt
If the CNTMDOT is not specified (zero or blank), then the mass flow rate must be constant and must be
defined on Mdot (the 8th field of the CONVM Bulk Data entry).
Main Index
CONVM 1427
Heat Boundary Element Forced Convection Entry
Example: Define a mass flow rate of 0.5 directly on Mdot without specifying CNTMDOT.
CONVM,100001,1,,,99,,0.5
4. If only the first ambient point is specified then, the second ambient point is assumed to have the same
temperature.
5. See the Bulk Data entry, PCONVM, for an explanation of the mathematical relationships available for
forced convection and the reference temperature for fluid material properties.
Main Index
1428 CORD1C
Cylindrical Coordinate System Definition, Form 1
CORD1C Cylindrical Coordinate System Definition, Form 1
Defines a cylindrical coordinate system using three grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CORD1C CIDA G1A G2A G3A CIDB G1B G2B G3B
Example:
CORD1C 3 16 32 19
Describer Meaning
CIDA, CIDB Coordinate system identification number. (Integer > 0)
GiA, GiB Grid point identification numbers. (Integer > 0; G1A G2A G3A ;
G1B G2B G3B )
Remarks:
1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,
CORD2C, CORD2S and CORD3G entries must be unique.
2. One or two coordinate systems may be defined on a single entry.
3. GiA and GiB must be defined in coordinate systems with definitions that do not involve the
coordinate system being defined. The first point is the origin, the second lies on the z-axis, and the
third lies in the plane of the azimuthal origin. The three grid points GiA (or GiB) must be noncolinear
and not coincident.
4. The location of a grid point (P in Figure 9-38) in this coordinate system is given by (R, , Z) where
is measured in degrees.
Main Index
CORD1C 1429
Cylindrical Coordinate System Definition, Form 1
uz
G2
G3
u
G1 P
Z
ur
x R y
Figure 9-38 CORD1C Definition
5. The displacement coordinate directions at P are dependent on the location of P as shown above by
u r u u z .
6. It is recommended that points on the z-axis not have their displacement directions defined in this
coordinate system. See the discussion of cylindrical coordinate systems in Grid Points and Coordinate
Systems in the MSC Nastran Reference Guide.
If CYLINDRICAL and point exactly on z-axis (r = 0.0 exactly) then R, , Z triad coordinates are
exactly aligned with the local defining system triad. User caution: if r 0.0 but not exactly 0.0
should be avoided as unexpected direction cosine matrix may result.
Main Index
1430 CORD1R
Rectangular Coordinate System Definition, Form 1
CORD1R Rectangular Coordinate System Definition, Form 1
Defines a rectangular coordinate system using three grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CORD1R CIDA G1A G2A G3A CIDB G1B G2B G3B
Example:
CORD1R 3 16 32 19
Describer Meaning
CIDA, CIDB Coordinate system identification number. (Integer > 0)
GiA, GiB Grid point identification numbers. (Integer > 0; G1A G2AG3A and G1B
G2BG3B)
Remarks:
1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,
CORD2C, CORD2S and CORD3G entries must be unique.
2. One or two coordinate systems may be defined on a single entry.
3. GiA and GiB must be defined in coordinate systems with definitions that do not involve the
coordinate system being defined. The first point is the origin, the second lies on the z-axis, and the
third lies in the x-z plane. The three grid points GiA (or GiB) must be noncolinear and not
coincident.
4. The location of a grid point (P in Figure 9-39) in this coordinate system is given by (X, Y, Z).
z
uz
G2
P
G3 uy
ux Z
G1 y
Y
x
Figure 9-39 CORD1R Definition
Main Index
CORD1R 1431
Rectangular Coordinate System Definition, Form 1
5. The displacement coordinate directions at P are shown above by u x u u u z .
Main Index
1432 CORD1S
Spherical Coordinate System Definition, Form 1
CORD1S Spherical Coordinate System Definition, Form 1
Defines a spherical coordinate system by reference to three grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CORD1S CIDA G1A G2A G3A CIDB G1B G2B G3B
Example:
CORD1S 3 16 32 19
Describer Meaning
CIDA, CIDB Coordinate system identification numbers. (Integer > 0)
GiA, GiB Grid point identification numbers. (Integer > 0; G1A G2A G3A and
G1B G2B G3B )
Remarks:
1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,
CORD2C, CORD2S and CORD3G entries must be unique.
2. One or two coordinate systems may be defined on a single entry.
3. GiA and GiB must be defined in coordinate systems with a definition that does not involve the
coordinate system being defined. The first point is the origin, the second lies on the z-axis, and the
third lies in the plane of the azimuthal origin. The three grid points GiA (or GiB) must be noncolinear
and not coincident.
4. The location of a grid point (P in Figure 9-40) in this coordinate system is given by (R, , ) where
and are measured in degrees.
Main Index
CORD1S 1433
Spherical Coordinate System Definition, Form 1
G2
u
ur
G3 P
G R
u
x
y
Figure 9-40 CORD1S Definition
5. The displacement coordinate directions at P are dependent on the location of P as shown above by
u r u u .
6. It is recommended that points on the z-axis not have their displacement directions defined in this
coordinate system. See the discussion of spherical coordinate systems in Grid Points and Coordinate
Systems in the MSC Nastran Reference Guide.
If SPHERICAL and R = 0.0 (point at origin) then R, , triad coordinates are exactly aligned with
the local defining system triad. User caution: if R 0.0 but not exactly 0.0 should be avoided as
unexpected direction cosine matrix may result.
If SPHERICAL and r in azimuth plane is r = 0.0 and z 0.0 then the coordinate system is defined
as R global along Z- local defining system triad according if z > 0. or z < 0., -global along X-local
defining system triad and -global along Y-local defining system triad. User caution: if r 0.0 but
not exactly 0.0 should be avoided as unexpected direction cosine matrix may result.
Main Index
1434 CORD2C
Cylindrical Coordinate System Definition, Form 2
CORD2C Cylindrical Coordinate System Definition, Form 2
Defines a cylindrical coordinate system using the coordinates of three points.
Format:
1 2 3 4 5 6 7 8 9 10
CORD2C CID RID A1 A2 A3 B1 B2 B3
C1 C2 C3
Example:
CORD2C 3 17 -2.9 1.0 0.0 3.6 0.0 1.0
5.2 1.0 -2.9
Describer Meaning
CID Coordinate system identification number. (Integer > 0)
RID Identification number of a coordinate system that is defined independently from this
coordinate system. (Integer > 0; Default = 0 is the basic coordinate system.)
Ai, Bi, Ci Coordinates of three points given with respect to the coordinate system defined by
RID. (Real)
Remarks:
1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,
CORD2C, CORD2S and CORD3G entries must be unique.
2. The three points [(A1, A2, A3), (B1, B2, B3), (C1, C2, C3)] must be unique and noncolinear.
Noncolinearity is checked by the geometry processor. The first point defines the origin. The second
point defines the direction of the z-axis. The third lies in the plane of the azimuthal origin. The
reference coordinate system must be independently defined.
3. The continuation entry is required.
4. If RID is zero or blank, the basic coordinate system is used.
5. The location of a grid point (P in Figure 9-41) in this coordinate system is given by (R, , Z), where
is measured in degrees.
Main Index
CORD2C 1435
Cylindrical Coordinate System Definition, Form 2
uz
B
u
P
C
A
Z
ur
x R
y
Figure 9-41 CORD2C Definition
6. The displacement coordinate directions at P are dependent on the location of P as shown above by
u r u u z .
7. It is recommended that points on the z-axis not have their displacement directions defined in this
coordinate system. See the discussion of cylindrical coordinate systems in Grid Points and Coordinate
Systems in the MSC Nastran Reference Guide. If CYLINDRICAL and point exactly on z-axis (r = 0.0
exactly) then R, , Z triad coordinates are exactly aligned with the local defining system triad. User
caution: if r 0.0 but not exactly 0.0 should be avoided as unexpected direction cosine matrix may
result.
8. If any CORD2C, CORD2R, or CORD2S entry is changed or added on restart, then a complete
re-analysis is performed. Therefore, CORD2C, CORD2R, or CORD2S changes or additions are not
recommended on restart.
9. An example of defining a coordinate system with respect to another coordinate system (RID) may be
found in the Linear Static Analysis manual Example.
Main Index
1436 CORD2R
Rectangular Coordinate System Definition, Form 2
CORD2R Rectangular Coordinate System Definition, Form 2
Defines a rectangular coordinate system using the coordinates of three points.
Format:
1 2 3 4 5 6 7 8 9 10
CORD2R CID RID A1 A2 A3 B1 B2 B3
C1 C2 C3
Example:
CORD2R 3 17 -2.9 1.0 0.0 3.6 0.0 1.0
5.2 1.0 -2.9
Describer Meaning
CID Coordinate system identification number. (Integer > 0)
RID Identification number of a coordinate system that is defined independently from this
coordinate system. (Integer > 0; Default = 0; which is the basic coordinate system.)
Ai, Bi, Ci Coordinates of three points given with respect to the coordinate system defined by RID.
(Real)
Remarks:
1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,
CORD2C, CORD2S, and CORD3G entries must be unique.
2. The three points [(A1, A2, A3), (B1, B2, B3), (C1, C2, C3)] must be unique and noncolinear.
Noncolinearity is checked by the geometry processor. The first point defines the origin. The second
defines the direction of the z-axis. The third point defines a vector which, with the z-axis, defines the
x-z plane. The reference coordinate system must be independently defined.
3. The continuation entry is required.
4. If RID is zero or blank, the basic coordinate system is used.
5. An example of defining a coordinate system with respect to another coordinate system (RID) may be
found in the Linear Static Analysis manual Example.
6. The location of a grid point (P in the Figure 9-42) in this coordinate system is given by (X, Y, Z).
Main Index
CORD2R 1437
Rectangular Coordinate System Definition, Form 2
uz
B
P
C uy
ux Z
A
y
Y
x
Figure 9-42 CORD2R Definition
7. The displacement coordinate directions at P are shown by u x u y u z .
8. If any CORD2C, CORD2R, or CORD2S entry is changed or added on restart, then a complete
re-analysis is performed. Therefore, CORD2C, CORD2R, or CORD2S changes or additions are not
recommended on restart.
Main Index
1438 CORD2S
Spherical Coordinate System Definition, Form 2
CORD2S Spherical Coordinate System Definition, Form 2
Defines a spherical coordinate system using the coordinates of three points.
Format:
1 2 3 4 5 6 7 8 9 10
CORD2S CID RID A1 A2 A3 B1 B2 B3
C1 C2 C3
Example:
CORD2S 3 17 -2.9 1.0 0.0 3.6 0.0 1.0
5.2 1.0 -2.9
Describer Meaning
CID Coordinate system identification number. (Integer > 0)
RID Identification number of a coordinate system that is defined independently from this
coordinate system. (Integer > 0; Default = 0 is the basic coordinate system.)
Ai, Bi, Ci Coordinates of three points given with respect to the coordinate system defined by
RID. (Real)
Remarks:
1. Coordinate system identification numbers on all CORD1R, CORD1C, CORD1S, CORD2R,
CORD2C, CORD2S, and CORD3G entries must all be unique.
2. The three points [(A1, A2, A3), (B1, B2, B3), (C1, C2, C3)] must be unique and noncolinear.
Noncolinearity is checked by the geometry processor. The first point defines the origin. The second
point defines the direction of the z-axis. The third lies in the plane of the azimuthal origin. The
reference coordinate system must be independently defined.
3. The continuation entry is required.
4. If RID is zero or blank, the basic coordinate system is used.
5. An example of defining a coordinate system with respect to another coordinate system (RID) may be
found in the Linear Static Analysis manual Example.
6. The location of a grid point (P in Figure 9-43) in this coordinate system is given by (R, , ), where
and are measured in degrees.
Main Index
CORD2S 1439
Spherical Coordinate System Definition, Form 2
B
u
ur
C P
A R
u
x
Figure 9-43 CORD2S Definition
7. The displacement coordinate directions at P are shown above by u r u u .
8. It is recommended that points on the z-axis not have their displacement directions defined in this
coordinate system. See the discussion of spherical coordinate systems in Grid Points and Coordinate
Systems in the MSC Nastran Reference Guide.
If SPHERICAL and R = 0.0 (point at origin) then R, , triad coordinates are exactly aligned with
the local defining system triad. User caution: if R 0.0 but not exactly 0.0 should be avoided as
unexpected direction cosine matrix may result.
If SPHERICAL and r in azimuth plane is r = 0.0 and z 0.0 then the coordinate system is defined
as R global along Z- local defining system triad according if z > 0. or z < 0., -global along X-local
defining system triad and -global along Y-local defining system triad. User caution: if r 0.0 but
not exactly 0.0 should be avoided as unexpected direction cosine matrix may result.
9. If any CORD2C, CORD2R, or CORD2S entry is changed or added on restart, then a complete
re-analysis is performed. Therefore, CORD2C, CORD2R, or CORD2S changes or additions are not
recommended on restart.
Main Index
1440 CORD3G
General Coordinate System
CORD3G General Coordinate System
Defines a general coordinate system using three rotational angles as functions of coordinate values in the
reference coordinate system. The CORD3G entry is used with the MAT9 entry to orient material principal
axes for 3-D composite analysis.
Format:
1 2 3 4 5 6 7 8 9 10
CORD3G CID METHOD FORM THETAID1 THETAID2 THETAID3 CIDREF
Example:
CORD3G 100 E313 EQN 110 111 112 0
Describer Meaning
CID Coordinate system identification number. See Remark 1. (Integer > 0)
METHOD E313 or S321 for Euler angle rotation in 313 sequence or space-fixed rotation in 321
sequence. See Remark 2. (Character; Default = “E313”)
FORM Specifies the Bulk Data entry which defines angles. FORM = “EQN” for DEQATN
entry or FORM = “TABLE” for TABLE3D entry. (Character; Default = “EQN”)
THETAID Identification number for DEQATN or TABLE3D Bulk Data entry which defines the
three angles (in radians) measured from reference coordinates to the general material
coordinate system. See Remark 3. (Integer > 0)
CIDREF Identification number for the coordinate system from which the orientation of the
general coordinate system is defined. (Integer > 0; Default = 0)
Remarks:
1. CID must be unique with respect to all other coordinate systems. CID cannot be referenced on
GRID entries.
2. Three Euler angles specify the rotation of the CORD3G coordinate axes (xyz) with respect to the local
Cartesian coordinate axes (XYZ) in CIDREF as follows: first rotate about Z-axis by 1 , next rotate
about rotated x-axis by 2 , and then rotate about rotated z-axis by 3 . On the other hand, the
space-fixed rotations in 321 sequence specify all the rotations about the fixed coordinate axes: first
rotate about Z by 1 , next about Y by 2 , then about X by 3 .
3. The three rotations define a coordinate transformation which transforms position vectors in the
reference coordinate system into the general coordinate system.
4. The DEQATN option must have three arguments representing the three axes of CIDREF, although
not all arguments are necessarily needed in the equation.
Main Index
CORD3G 1441
General Coordinate System
5. If FORM = EQN is used with CIDREF pointing to any CORD1k or CORD2k, k = C,S, and a
spatial relationship is required, then the equations are written using R, , as input variables. Non
spatial fixed values such as THETA1 (A,B,C)=PI(1.) may of course be entered for any type of
coordinate defined by the CIDREF.
If FORM = TABLE3D is used with CIDREF pointing to any CORD1k or CORD2k, k = C,S, and
a spatial relationship is required then the equations are written using the variables X,Y, Z defined at
the origin of the CIDREF as input values and not the variables R, ,Z or R, , input values. For
example, if a CORD1S is used then the table input value is X internally computed as
R SIN COS .
Whether the EQN or TABLE3D FORM is used, the equation must return an angle measure in
radians to have any meaning.
Main Index
1442 CORD3R
Moving Rectangular Coordinate System
CORD3R Moving Rectangular Coordinate System
Defines a moving rectangular coordinate system using three points in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CORD3R CID N1 N2 N3 CID N1 N2 N3
Example:
CORD3R 1001 1 144 300
Describer Meaning
CID Unique coordinate system number. (Integer > 0)
N1, N2, N3 Grid point numbers (must be unique). (Integer > 0)
Remarks:
1. Available in SOL 700 only.
2. Two different coordinate systems may be defined on one entry.
3. The grid points must be defined in an independent coordinate system.
4. The first grid point is the origin, the second lies on the z-axis and the third lies in the x-z plane.
5. The position and orientation of the coordinate system is updated as the grid points move.
6. The three grid points must not be colinear.
Main Index
COSMGRP 1443
Define the coupled area in Co-Simulation service
COSMGRP Define the coupled area in Co-Simulation service
COSMGRP defines the coupled area where Nastran will exchange input and output data with co-simulation
partner in Co-simulation analysis. It is supported in SOL 400 only.
Format 1: TYPE=SURFACE
1 2 3 4 5 6 7 8 9 10
COSMGRP GRPID TYPE
EID FaceID EID FaceID EID FaceID EID FaceID
EID FaceID ...
Examples 1: TYPE=SURFACE
1 2 3 4 5 6 7 8 9 10
COSMGRP 202 SURFACE
1001 5 1002 4
Format 2: TYPE=POINT
1 2 3 4 5 6 7 8 9 10
COSMGRP GRPID TYPE
GridID1 GridID2 ...
GridIDi ...
Examples 2: TYPE=POINT
1 2 3 4 5 6 7 8 9 10
COSMGRP 202 POINT
2001 2002 31002 31003
Format 3: TYPE=VOLUME
1 2 3 4 5 6 7 8 9 10
COSMGRP GRPID TYPE
EID1 EID2 EID3 ...
EIDi ...
Main Index
1444 COSMGRP
Define the coupled area in Co-Simulation service
Examples 3: TYPE=VOLUME
1 2 3 4 5 6 7 8 9 10
COSMGRP 202 VOLUME
2 7 8 9 10 21 32 35 39
40
Describer Meaning
GRPID Identification number of COSMGRP referenced by a COSMSRV Bulk Data Entry.
(Integer > 0)
TYPE The definition type of coupled area (Character; Default is SURFACE)
SURFACE: the couple area is defined by the element ID and its face ID
POINT: the coupled area is defined by a list of grid IDs
VOLUME: the couple area is defined by the set of elements with element IDs
EID Element identification number
FACEID Face identification number of element. Refer to the remarks 6. and 7. for the element face
identification of CHBDYE entry.
GRIDID Grid point identification numbers
Main Index
COSMINP 1445
Define the physical quantities of input in Co-Simulation service
COSMINP Define the physical quantities of input in Co-Simulation service
Defines the physical quantities of input which Nastran will receive from the co-simulation partner in Co-
simulation analysis. It is supported in SOL 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
COSMINP PHYIN
PHYQUA1 PHYQUA2
Example:
1 2 3 4 5 6 7 8 9 10
COSMINP 405
FORCE
Describer Meaning
PHYIN Identification number of COSMINP referenced by a COSMSRV Bulk Data Entry
(Integer > 0).
PHYQUAi Name of physical quantities which will be provided to Nastran as input in co-
simulation analysis (Character; Default: FORCE)
Remarks:
1. Currently, it supports FORCE and TEMP (temperature load) from CoSIM only.
2. Basically, all 2D (CQUAD4, CQUAD8, CQUADR, CTRIA3, CTRIA6, CTRIAR) and 3D
elements (CHEXA, CPENTA, CTETRA, CPYRAM) are supported for Temperature Load by
CoSim. However, some combinations of features are not supported as shown below:
Nonlinear Property PARM,LGDISP Element Type Temperature Note
Extensions*1 Load by
PSHLN1, PSLDN1, CoSim
etc.
No -1 Nastran Linear Not supported
No 1 or 2 Nastran Nonlinear Supported CQUAD8 and
CTRIA6 is not
supported
Yes Any Advanced Nonlinear Supported
*1 - Nonlinear Property Extensions may be automatically defined by the PROPMAP
feature of NLMOPTS
Main Index
1446 COSMOUT
Define the physical quantities of output in Co-Simulation service
COSMOUT Define the physical quantities of output in Co-Simulation service
Defines the physical quantities of output which Nastran will yield and provide to the co-simulation partner
in Co-simulation analysis. It is supported only in SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
COSMOUT PHYOUT
PHYQUA1 PHYQUA2 PHYQUA3
Example:
1 2 3 4 5 6 7 8 9 10
COSMOUT 506
DISP ACCE
Describer Meaning
PHYOUT Identification number of COSMOUT referenced by a COSMSRV Bulk Data Entry
(Integer > 0).
PHYQUAi Name of physical quantities which will be provided to partner software as input in
co-simulation analysis (Character)
One or any combination of the following physical quantities can be used:
DISP
VELO
ACCE
Remarks:
1. Currently, it supports only one or combination of DISP, VELO, and ACCE.
2. The displacement, velocity and acceleration from Nastran to co-simulation are always in basic
coordinate system, even these degree of freedom are defined in local rectangular coordinate system
like CORD2R. Note that only rectangular local coordinate system is supported; the cylindrical and
spherical local coordinate systems are not supported in co-simulation analysis.
Main Index
COSMSEL 1447
Specify the Co-Simulation service
COSMSEL Specify the Co-Simulation service
Specifies the selected co-simulation service for analysis through the COSMSRV. It is supported only in SOL
400.
Format:
1 2 3 4 5 6 7 8 9 10
COSMSEL SID
CSRVID1 CSRVID2 CSRVID3
Example:
1 2 3 4 5 6 7 8 9 10
COSMSEL 1
21
Describer Meaning
SID Identification number referenced by a COSMSEL Case Control command
(Integer > 0).
CSRVIDi Identification number of COSMSRV entry (Integer > 0).
Remarks:
1. Currently, it supports only one COSMSRV.
Main Index
1448 COSMSRV
Define the Co-Simulation service
COSMSRV Define the Co-Simulation service
Defines the co-simulation service for analysis on a coupled group and exchanged physical quantities. It is
supported only in SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
COSMSRV CSRVID SERV FOLFORCE
GRPID1 PHYINP GRPID2 PHYOUT
Example:
1 2 3 4 5 6 7 8 9 10
COSMSRV 21 scFlow FOLLOW
202 305 202 406
Describer Meaning
CSRVID Identification number referenced by a COSMSEL Bulk Data Entry (Integer > 0).
SERV Cosim service identifier (Character) (support scFLOW only now).
FOLFORCE Flag for how forces received from CoSim for scFLOW are processed.
NOFOLL Forces will be applied as received from CoSim over the entire increment.
(Default)
FOLLOW Forces received from CoSim will be treated as follower forces.
GRPID1 Identification number of COSMGRP Bulk Data Entry (Integer > 0).
It defines the coupled area in which Nastran receives the input from co-simulation
partner.
GRPID2 Identification number of COSMGRP Bulk Data Entry (Integer > 0).
It defines the coupled area in which Nastran provides output of analysis to
co-simulation partner.
PHYINP Identification number of COSMINP Bulk Data Entry (Integer > 0).
It defines the physical quantities which Nastran receives from co-simulation partner.
PHYOUT Identification number of COSMOUT Bulk Data Entry (Integer > 0).
It defines the physical quantities which Nastran provides to co-simulation partner.
Remarks:
1. Currently, it supports one set of coupled area only.
2. At present, GRPID1 should be same as GRPID2.
3. SERV is a mandatory input. Currently, any characters are acceptable; scFLOW is recommended.
Main Index
COUCOHF 1449
Cohesive Friction Model To Be Used For a COUPLE Entry
COUCOHF Cohesive Friction Model To Be Used For a COUPLE Entry
Defines a cohesive friction model suited for Euler Coupled analyses. The friction model is defined as part of
the coupling surface. Use SOL700 only.
Format:
COUCOHF CID COHFRID SUBID COHFRICID
Example:
COUCOHF 112 14 12 12
Describer Meaning
CID Unique number of a COUCOHF entry. (Integer ≥0; required)
COHFRID Number of a set of COUCOHF entries. COUCOHF must be referenced from a
COUPLE entry. (Integer ≥0; required)
SUBID BSURF, BCSEG or BCPROP id, which must be a part of the BSID field of the
COUPLE entry. See Remark 2. (Integer ≥0; default = blank)
COHFRICID Cohesive friction ID (Integer ≥0; required)
Remarks:
1. One couple entry can reference more than one COUCOHF entry. This allows a cohesive friction that
varies along the coupling surface.
2. When SUBID is left blank, then the cohesive friction applies to the whole coupling surface.
3. A coupling surface segment can only have one porosity or one cohesive friction definition assigned.
Main Index
1450 COUOPT
Coupling Surface Pressure Definition
COUOPT Coupling Surface Pressure Definition
Defines the interaction factor and a pressure load from the covered side acting on a BSURF, BCPROP,
BCMATL, BCSEG, BCBOX. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
COUOPT CID OPTID SUBID FACTOR FACTORV
PLCOVER PLCOVERV
Example:
COUOPT 1 80 42 CONSTANT
CONSTANT 1.E5
Describer Meaning
CID Unique number of a COUOPT entry. (Integer > 0; Required)
OPTID Number of a set of COUOPT entries. OPTID must be referenced from a COUPLE
entry. (Integer > 0; Required)
SUBID >0 Number of a BSURF, BCBOX, BCPROP, BCMATL or BCSEG,
which must be part of the surface as defined in the COUPLE entry.
(Integer > 0, 0)
=0 COUOPT definitions used for the entire surface as defined in the
COUPLE entry.
FACTOR Method of defining the interaction FACTORV with which the Eulerian pressure acting
on the surface is multiplied. (Character, CONSTANT)
CONSTANT The FACTOR is constant and specified in FACTORV
FACTORV The interaction factor. (Real, 1.)
PLCOVER Method of defining the pressure load exerted on the faces of the surface from the covered
side. The pressure load is applied only when the Eulerian pressure is greater than zero.
(Character, CONSTANT)
CONSTANT The PLCOVER is constant and specified in PLCOVERV.
TABLE The PLCOVER varies with time. PLCOVERV is the number of a
TABLED1 entry giving the variation of the PLCOVER (y-value) with
time (x-value).
PLCOVERV The pressure load or the number of a TABLED1 entry depending on the PLCOVER
entry. (Real > 0, 0.)
Main Index
COUOPT 1451
Coupling Surface Pressure Definition
Remarks:
1. The effect of specifying an interaction FACTOR is similar to specifying a porosity coefficient on a
COUPOR entry. The difference is that in this case the surface still acts as a wall boundary for the
Eulerian material.
2. Applying a PLCOVER instead of applying a pressure load on the faces through either a PLOAD,
PLOAD4, or DAREA entry gives the following differences:
a. PLCOVER is applied only when there is a balancing Eulerian pressure greater than zero.
b. Possible porosity as defined on a COUPOR entry is taken into account when applying the
PLCOVER.
c. With PARAM,PLCOVCUT you can define a cut-off time that is applied to PLCOVER.
3. The covered side of a surface lies on the side where there is no Eulerian material.
Main Index
1452 COUP1FL
Coupling Surface Failure
COUP1FL Coupling Surface Failure
Defines the surrounding variables when a segment of a coupling surface fails. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
COUP1FL CFID RHO SIE XVEL YVEL ZVEL PRESSURE MATERIAL
Example:
COUP1FL 3 1.225 204082. 900.
Describer Meaning
CFID Unique ID of a COUP1FL entry referenced from the COUPLE entry. (Integer > 0;
Required)
RHO Surrounding density. See Remark 2. (Real > 0)
SIE Surrounding specific internal energy. See Remark 2. (Real)
XVEL Surrounding x-velocity. See Remark 2. (Real)
YVEL Surrounding y-velocity. See Remark 2. (Real)
ZVEL Surrounding x-velocity. See Remark 2. (Real)
PRESSURE Surrounding pressure. See Remark 4. (Real)
MATERIAL MATDEUL ID. Only used when the multi-material Euler solver is active. (Blank)
Remarks:
1. This entry can only be used in combination with DYPARAM,FASTCOUP, ,FAIL and with either
the HYDRO, MMHYDRO or MMSTREN Euler Solver. For restrictions on the use of COUP1FL
refer to param,flow-method. The coupling surface failure is associated with the element failure of the
structure to which the surface is connected. Therefore, you have to define a failure model for the
structure for the entry to take effect in the analysis.
2. For the first order Euler solvers no restriction apply to the values of the surrounding variables. For the
Roe solver at least one of the surrounding variables should be defined. The default value of the density
(RHO) will be set equal to the reference density as defined on the MATDEUL entry. By default, the
other variables (SIE, XVEL, YVEL and ZVEL) are set equal to zero.
3. The coupling surface must only consist of CQUAD and/or CTRIA elements.
4. The field PRESSURE has to be left blank in combination with the Roe solver.
5. In combination with multi-material Euler only outflow of material is allowed. Each material in an
outflow Euler element is transported. The materials are transported in proportion to their relative
volume fractions.
Main Index
COUPINT 1453
Coupling Surface Interaction
COUPINT Coupling Surface Interaction
Defines the surrounding variables when a segment of a coupling surface fails. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
COUPINT CID CID1 CID2
Example:
COUPINT 33 2
Describer Meaning
CIID Unique number of a COUPINT entry.
CID1 Number of COUPLE entry 1.
CID2 Number of COUPLE entry 2.
Remarks:
1. This entry can only be used in combination with DYPARAM,FASTCOUP, ,FAIL and with either
the HYDRO, MMHYDRO or MMSTREN Euler Solver. The interaction will be activated when
failure of a Lagrangian structure with which the coupling surface is associated occurs. Therefore, you
have to define a failure model for the material of the structure.
2. The coupling surface must consist of CQUAD and/or CTRIA elements.
Main Index
1454 COUPLE
General Euler-Lagrange Coupling Surface
COUPLE General Euler-Lagrange Coupling Surface
Defines a coupling surface that acts as the interface between an Eulerian (finite volume) and a Lagrangian
(finite element) domain. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
COUPLE CID BSID COVER REVERSE CHECK PORID OPTID CTYPE
INFID HTRID FS FK EXP INTID
SET1ID MESHID TDEAC COUP1FL HYDSTAT SKFRIC COHFRI
D
Example:
COUPLE 100 37 INSIDE ON ON
0.3 0.0
Describer Meaning
CID Unique number of a COUPLE entry. (Integer > 0; Required)
BSID Number of a BSURF, BCBOX, BCPROP, BCMATL or BCSEG entry defining the
coupling surface. (Integer > 0; Required)
COVER The processing strategy for Eulerian elements inside and outside of the coupling surface.
(Character, INSIDE)
INSIDE The Eulerian elements inside the closed volume of the coupling surface
are not processed.
OUTSIDE The Eulerian elements outside the closed volume of the coupling
surface are not processed
NONE The Eulerian elements on both sides of the coupling surface are
processed.
REVERSE Auto-reverse switch for the coupling surface segments. (Character, ON)
ON If required, the normals of the coupling surface segments are
automatically reversed so that they all point in the same general
direction as to give a positive closed volume.
OFF The segments are not automatically reversed. The user is responsible
for defining the correct general direction of the segment normals.
CHECK Check switch for coupling surface segments. (Character, ON)
ON The normals of the segments are checked to verify that they all point in
the same general direction and yield a positive closed volume.
Main Index
COUPLE 1455
General Euler-Lagrange Coupling Surface
Describer Meaning
OFF The segments are not checked. It the responsibility of the user to ensure
that the direction of the segment normals yield a positive closed
volume.
When “REVERSE” is set to “ON”, the “CHECK” option will be automatically
activated.
PORID Number of a set of “LEAKAGE” entries that define the porosity for the BSURF entries.
(Integer > 0, 0 (no porosity))
OPTID Not available for the Roe solver
Number of a set of “COUOPT” entries that define special options for the BSURF
entries (Integer > 0, 0 (no special options))
CTYPE Not available for the Roe solver
Coupling surface type definition. (Character, STANDARD)
STANDARD Standard Euler-Lagrange interaction.
AIRBAG Coupling for airbag applications.
It is equivalent to the standard coupling algorithm with the following
exceptions that tailor the solution for airbag applications:
Inflow through a porous (sub)-surface will only occur when there is
already some material (gas) in the Eulerian element.
Almost empty Eulerian elements will be automatically eliminated. The
standard algorithm redistributes the small mass to the must suitable
neighbor elements.
INFID Number of a set of “ABINFL” entries that define the inflator(s) on the subsurface(s) of
the coupling surface. Not available for the Roe solver. (Integer > 0, 0 (no inflators))
HTRID Number of a set of “HEATLOS” entries that define the heat transfer definition(s) on the
subsurface(s) of the coupling surface. Not available for the Roe solver. (Integer > 0, 0 (no
heat transfer))
FS Static friction coefficient. See Remark 6. Not available for the Roe solver. (Real > 0.0,
0.0)
FK Kinetic friction coefficient. See Remark 6. Not available for the Roe solver. (Real > 0.0,
0.0)
EXP Exponential decay coefficient. See Remark 6. Not available for the Roe solver. (Real >
0.0, 0.0)
INTID ID of an INITGAS entry specifying initial gas composition for the Euler mesh. See
Remark 7. (Integer > 0, 0 (no initial gas composition))
SET1ID The number of a SET1 entry, which defines the Eulerian elements associated with this
coupling surface. See Remark 8. (Integer > 0; Default = blank)
MESHID ID of a MESH entry, which defines the Eulerian mesh associated with this coupling
surface. See Remark 8. (Integer > 0; Default = blank)
Main Index
1456 COUPLE
General Euler-Lagrange Coupling Surface
Describer Meaning
TDEAC Time of deactivation of the coupling surface and the associated Eulerian mesh. (Real >
0.0, 1.E20)
COUP1FL The number of a COUP1FL entry, which defines the surrounding variables for the
coupling surface when its segments fail. See Remark 9. (Integer > 0; Default = blank)
HYDSTAT The number of a HYDSTAT entry, which specifies a hydrostatic preset. The preset is
applied to all Euler element specified by the SET1ID and MESHID. See Remark 11.
(Integer > 0, 0 (no hydrostatic preset)
SKFRIC Skin friction value. See Remark 13. (Real > 0.0, 0.0)
COHFRID Number of a set of COUCOHF entries that define the cohesive friction on the
subsurface(s) of the coupling surface.(I> 0 Default = blank)
Remarks:
1. All coupling surfaces must form a multi-faceted closed volume. If necessary, additional segments must
be defined to achieve the closed volume. The closed volume must intersect at least one Euler element
initially.
2. All segments must de attached to the face of an element. Dummy elements can be used to define any
additional segments that are required to create the closed volume.
3. The normals of all segments that from the coupling surface must point in the same general direction
and result in a positive closed volume. Setting the “REVERSE” option to “ON” ensures that this
condition is satisfied, regardless of the initial definition of the segments.
4. The “COVER” field determines how Eulerian elements that are inside and outside of the coupling
surface are processed. The default setting of INSIDE is appropriate for most of the problems. In the
majority of analyses, the Eulerian material flows around the outside of the coupling surface.
Therefore, the Eulerian elements that fall within the coupling surface do not contain material. For
some specific applications, such as airbag inflation, the Eulerian material (gas) is completed contained
within the coupling surface. In these cases, the “COVER” definition should be set to OUTSIDE.
5. By default the fast coupling algorithm is used. The algorithm then used is substantially faster than the
general coupling. The restriction is that you cannot use an arbitrarily shaped Euler mesh with the fast
coupling algorithm. All element faces of the Euler mesh must have their normal pointing in any of
the three basic coordinate directions. If you want to use the general coupling algorithm, you can
define the parameter “DYPARAM,FASTCOUP,NO” in the input file.
6. The friction model implemented for the coupling algorithm is a simple Coulomb friction definition.
The friction coefficient is defined as:
–
= k + s – k e
where s is the static friction coefficient, k is the kinetic friction coefficient, the exponential
decay coefficient and the relative sliding at the point of contact.
Main Index
COUPLE 1457
General Euler-Lagrange Coupling Surface
7. An initial gas composition is for use with the single-material hydrodynamic Euler solver and an ideal-
gas equation of state (EOSGAM) only.
8. Multiple coupling surfaces are available when you associate one Eulerian domain with a single
coupling surface by either using the SET1ID or the MESHID option. Note that only one of the two
options may be set and will work only in combination with the fast coupling algorithm.
9. The COUP1FL option is available and valid only in combination with the fast coupling algorithm
with the failure option (DYPARAM,FASTCOUP, ,FAIL). If no number is given, the default values
of the surrounding variables will be used; the density (RHO) is set equal to the reference density as
defined on the MATDEUL entry. By default, the other variables (SIE, XVEL, YVEL and ZVEL) are
set equal to zero.
10. If an ACTIVE entry is present, its definition is ignored in case the TDEAC value is defined in
combination with the fast coupling algorithm.
11. If there is only one coupling surface and no adaptive meshing is used, the HYDSTAT field can be left
blank. To impose a boundary condition that matches the hydrostatic initialization, the PORHYDS
entry can be used.
12. A mixture of BSURF, BCBOX, BCPROP, BCMATL or BCSEG with the same BSID is allowed.
However multiple BSID of the same type is not allowed. When using this option, special care must
be taken to assure the same element is not part of multiple BSID definitions.
13. The skin friction is defined as:
w
C f = ---------------------
2
0.5 u
Here, w denotes the shear friction in an Euler element adjacent to a couple surface segment where
is the density and u is the tangential relative velocity in the Euler element that is adjacent to a
couple surface segment.
SKFRIC will only be used when VISC has been set on either an EOSGAM or an EOSPOL entry. If
VISC has been set and if SKFRIC has not been set then a no slip condition will be prescribed at the
interface between fluid and structure.
14. If the coupling surface is a structural solid then Sol700 can automatically create a coupling surface for
the solid. This coupling surface consists of the boundary faces of the solid. To activate this, a
BCPROP has to be created for the solid and the BCPROP has to be used for the BSID of the
COUPLE entry.
15. Option NONE requires the use of DYPARAM, AUTCOUP. For details refer to this DYPARAM.
16. When BSID refers to a ID of a BCPROP or BCMATL, only properties of shell elements can be
referenced. All solid elements referenced with the same PID or MID will be ignored. Use BCSEG to
reference faces of solid elements.
Main Index
1458 CPENTA
Five-Sided Solid Element Connection
CPENTA Five-Sided Solid Element Connection
Defines the connections of a five-sided solid element with six to fifteen grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CPENTA EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13 G14
G15
Example:
CPENTA 112 2 3 15 14 4 103 115
5 16 8 120 125
130
Describer Meaning Type Default
EID Element identification number. 0 < Integer < 100,000,000 Required
PID Property identification number of a PSOLID or Integer > 0 Required
PLSOLID entry.
Gi Identification numbers of connected grid Integer > 0 or blank Required
points.
G6
G15 G14
G12
G13
G4 G5
G10 G3
G11
G9 G8
G7
G1
G2
Figure 9-44 CPENTA Element Connection
Main Index
CPENTA 1459
Five-Sided Solid Element Connection
Remarks:
1. Element ID numbers must be unique with respect to all other element ID numbers.
2. The topology of the diagram must be preserved; i.e., G1, G2, and G3 define a triangular face, G1,
G10, and G4 are on the same edge, etc.
3. For Nastran conventional element, the edge grid points, G7 to G15, are optional. Any or all of them
may be deleted. In the example shown, G10, G11, and G12 have been deleted. The continuations
are not required if all edge grid points are deleted.
Note that for advanced nonlinear elements, partial specification of mid-points is not allowed. i.e.
either none of the mid-points should be specified or all of the mid points should be specified.
4. Components of stress are output in the material coordinate system except for hyperelastic elements,
which are output in the basic coordinate system.
5. For nonhyperelastic elements the element coordinate system for the CPENTA element is derived
accordingly. The origin of the coordinate system is located at the midpoint of the straight line
connecting the points G1 and G4. The Z axis points toward the triangle G4-G5-G6 and is oriented
somewhere between the line joining the centroids of the triangular faces and a line perpendicular to
the midplane. The midplane contains the midpoints of the straight lines between the triangular faces.
The X and Y axes are perpendicular to the Z axis and point in a direction toward, but not necessarily
intersecting, the edges G2 through G5 and G3 through G6, respectively.
Solid elements have both a material and an element coordinate system. Both systems are defined for
the initial geometry, and for geometric nonlinear analysis they will rotate with the element. The
material coordinate system is used to input anisotropic material properties and for stress output. The
material coordinate system is defined by the CORDM field of the PSOLID entry. The element
coordinate system is used for element stiffness integration (reduced shear for example) and optionally
to define the material coordinate system (only if PSOLID,CORDM=-1).
G6
z
G15
G14
G4 y
G13
G5
G12
G10
G11
x
G3 G8
G9
G7 G2
G1
Figure 9-45 CPENTA Element Coordinate System
Main Index
1460 CPENTA
Five-Sided Solid Element Connection
6. We recommend that the edge grid points be located within the middle third of the edge.
7. For hyperelastic elements, the plot codes are specified under the CPENTAFD element name in Item
Codes.
8. By default, all the nine edges of the element are considered straight unless, any of G7 through G15
are specified.
9. The internal coordinate system of the element is used internally and is based on eigenvalue techniques
to insure non bias in the element formulation. For stress/strain output this internal coordinate system
(CORDM=-1 on PSOLID entry) is hard to visualize. Thus a CORDM=-2 on the PSOLID is
available as shown in Figure 9-46.
Figure 9-46 PSOLID for CPENTA
Main Index
CPYRAM 1461
Five-Sided Solid Element Connection
CPYRAM Five-Sided Solid Element Connection
Defines the connections of the five-sided solid element with five or thirteen grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CPYRAM EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13
Example:
CPYRAM 7 4 15 16 17 18 40 21
22 23 24 31 32 33 34
Describer Meaning Type Default
EID Element identification number. 0 < Integer < 100,000,000 Required
PID Property identification number of a PSOLID Integer > 0 Required
entry.
Gi Identification numbers of connected grid Integer > 0 or blank Required
points.
Figure 9-47 CPYRAM Element Connection
Main Index
1462 CPYRAM
Five-Sided Solid Element Connection
Remarks:
1. Element ID numbers must be unique with respect to all other element ID numbers.
2. The topology of the diagram must be preserved, that is, G1, G2, G3, G4 define the quadrilateral base,
G5 defines the apex, G1, G5, G10 are on the same edge, etc.
3. For a 5 noded CPYRAM element, only G1 - G5 should be provided. For a 13 noded CPYRAM
element, all the corner and mid-side nodes (G1 - G13) should be provided. Note that partial
specification of mid-points is not allowed. i.e. either none of the mid-points should be specified or all
of the mid points should be specified.
4. The pyramid elements use the basic coordinate system as the element coordinate system when
CORDM = 0 or blank in corresponding PSOLID entry. CORDM=-1 is not supported, and Nastran
exits with UFM if CORDM=-1 is provided. CORDM=-2 can be used for element coordinate system
as shown below.
Xe = (G1+G2+G5)/3 - (G3+G4+G5)/3
V = (G2+G3+G5)/3 - (G1+G4+G5)/3
5. For CORDM > 0, the material coordinate system is defined with respect to the initial geometry and
is used to input orthotropic or anisotropic material properties and for stress output. For geometric
nonlinear analysis, the material coordinate system rotates with the element. Component of stresses
are output in the material coordinate system referenced by the CORDM field of PSOLID entry
(CORDM > 0).
6. Element type CPYRAM is not supported for random response.
Main Index
CQUAD 1463
Fully Nonlinear Plane Strain Element
CQUAD Fully Nonlinear Plane Strain Element
Defines a plane strain quadrilateral element with up to nine grid points for use in fully nonlinear (i.e., large
strain and large rotation) hyperelastic analysis.
Format:
1 2 3 4 5 6 7 8 9 10
CQUAD EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 THETA or
MCID
Example:
CQUAD 111 203 31 74 75 32
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PLPLANE or PLCOMP entry. (Integer > 0)
G1, G2, Identification numbers of connected corner grid points. Required data for all four grid
G3, G4 points. (Unique Integers > 0)
G5, G6, Identification numbers of connected edge grid points. Optional data for any or all four
G7, G8 grid points. (Integer > 0 or blank)
G9 Identification number of center grid point. Optional. (Integer > 0 or blank)
THETA Material property orientation angle in degrees. THETA is only applicable if PLCOMP
referenced, or the PLPLANE entry has an associated PSHLN2 entry which is honored
only in SOL 400. For PSHLN2 BEHi=PSTRS or PLSTRN codes, THETA is measured
relative to the line defined from G1-G2. For PSHLN2 or PLCOMP BEHi=COMPS
code the THETA value on the element connection entry will be ignored. (Real; Default
= 0.0)
MCID Material coordinate system identification number MCID is only applicable if the
PLPLANE entry has an associated PSHLN2 entry which is honored only in SOL 400.
The x-axis of the material coordinate system is determined by projecting the T1-axis of
the MCID coordinate system onto the surface of the shell element as follows:
CORD1R, x -axis of MCID the coordinate is projected onto shell surface and the
CORD2R material angle is measured from the G1-G2 line to the to the projected x-
axis
Main Index
1464 CQUAD
Fully Nonlinear Plane Strain Element
Describer Meaning
CORD1C, r-axis of MCID the coordinate is projected onto shell surface through the
CORD2C element center and the material angle is measured from the G1-G2 line to
CORD1S, the to the projected r-axis
CORD2S
For PSHLN2 (or PLCOMP) BEHi=COMPS code the MCID value on the element
connection entry will be ignored. (Integer > 0; if blank, then THETA = 0.0 is assumed.)
Remarks:
1. Element identification numbers should be unique with respect to all other element IDs of any kind.
2. Grid points G1 to G9 must be numbered as shown and must lie on a plane. G5 - G9 are Optional
data for any or all four grid points for Nastran conventional element only.
Note that for advanced nonlinear elements, partial specification of mid-points is not allowed. i.e.
either none of the mid-points should be specified or all of the mid points should be specified.
3. It is recommended that the edge points be located within the middle third of the edge.
4. The plot codes are specified under the CQUADFD element name in Item Codes.
5. Stresses and strains are output in the coordinate system identified by the CID field of the PLPLANE
entry.
= 1 G7
G4
G3
= constant
Lines of
= –1 = 1 Constant or
= 0
= 0 = constant
G8 G9
G6
= –1
G2
G5
G1
Figure 9-48 CQUAD Element Coordinate System
Main Index
CQUAD4 1465
Quadrilateral Plate Element Connection
CQUAD4 Quadrilateral Plate Element Connection
Defines an isoparametric membrane-bending or plane strain quadrilateral plate element.
Format:
1 2 3 4 5 6 7 8 9 10
CQUAD4 EID PID G1 G2 G3 G4 THETA or ZOFFS
MCID
TFLAG T1 T2 T3 T4
Example:
CQUAD4 111 203 31 74 75 32 2.6 0.3
1.77 2.04 2.09 1.80
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHELL, PCOMP, PCOMPG or PLPLANE or
PLCOMP entry. (Integer > 0; Default = EID)
Gi Grid point identification numbers of connection points.
(Integers > 0, all unique.)
THETA Material property orientation angle in degrees. THETA is ignored for hyperelastic
elements. See Figure 9-50. See Remark 9. (Real; Default = 0.0)
MCID Material coordinate system identification number. The x-axis of the material coordinate
system is determined by projecting the T1-axis of the MCID coordinate system onto the
surface of the shell element as follows:
CORD1R, x -axis of MCID the coordinate is projected onto shell surface and the
CORD2R material angle is measured from the G1-G2 line to the to the projected x-
axis
CORD1C, r-axis of MCID the coordinate is projected onto shell surface through the
CORD2C element center and the material angle is measured from the G1-G2 line
CORD1S, to the to the projected r-axis
CORD2S
Use DIAG 38 to print the computed THETA values. MCID is ignored for hyperelastic
elements. See Remark 9. (Integer > 0; If blank, then THETA = 0.0 is assumed.)
Main Index
1466 CQUAD4
Quadrilateral Plate Element Connection
x
MCID
Coordinate
System
z
G2
y G3
ymaterial
xmaterial
G4
G1
Figure 9-49 MCID Coordinate System Definition
ZOFFS Offset from the surface of grid points to the element reference plane. ZOFFS is ignored
for hyperelastic elements. See Remark 6. (Real)
TFLAG An integer flag, signifying the meaning of the Ti values. (Integer 0, 1, or blank)
Ti Membrane thickness of element at grid points G1 through G4. If “TFLAG” is zero or
blank, then Ti are actual user specified thicknesses. See Remark 4. for default. (Real > 0.0
or blank, not all zero.) If “TFLAG” is one, then the Ti are fractions relative to the T value
of the PSHELL. (Real > 0.0 or blank, not all zero. Default = 1.0) Ti are ignored for
hyperelastic elements.
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Grid points G1 through G4 must be ordered consecutively around the perimeter of the element.
3. All interior angles must be less than 180.
4. The continuation is optional. If it is not supplied, then T1 through T4 will be set equal to the value
of T on the PSHELL entry.
Main Index
CQUAD4 1467
Quadrilateral Plate Element Connection
yelement
G3
G4
+
= ------------ xelement
2
xmaterial
zelement
THETA
G1 G2
Figure 9-50 CQUAD4 Element Geometry and Coordinate Systems
5. The reference coordinate system for the output of stress, strain and element force depends on the
element type.
• For CQUAD4 elements which are not hyperelastic, the reference coordinate system is the default
for output is the element coordinate system. See PARAM,OMID for output in the material
system.
• For hyperelastic elements the stress and strain are output according to CID on the PLPLANE
entry.
6. Elements may be offset from the connection points by means of ZOFFS. Other data, such as material
matrices and stress fiber locations, are given relative to the reference plane. A positive value of ZOFFS
implies that the element reference plane is offset a distance of ZOFFS along the positive Z-axis of the
element coordinate system. If the ZOFFS field is used, then the MID1 and MID2 fields must be
specified on the PSHELL entry referenced both by PID.
Two methods are available for the computation of offsets: original and enhanced. The default method
is the original method. The enhanced method is requested by the Bulk Data entry
MDLPRM,OFFDEF,LROFF. For options of offsets, please refer to the Bulk Data entry
MDLPRM,OFFDEF,option.
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, it is highly recommended to use MDLPRM, OFFDEF, LROFF. In SOL103, if the
case control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then
MDLPRM, OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
For SOLs 106, 129, 153, and 159 the differential stiffness for offset vectors will give incorrect results
with PARAM, LGDISP, 1. In addition in SOLs 106 and 129 offset vectors will produce incorrect
results with thermal loading.
Main Index
1468 CQUAD4
Quadrilateral Plate Element Connection
7. For finite deformation hyperelastic analysis, the plot codes are given by the CQUADFD element
name in Item Codes.
8. By default, all of the four edges of the element are considered straight.
9. If element has an associated PSHLN2 or PLCOMP entry with BEHi=COMPS code, the
THETA/MCID value on the element connection entry will be ignored.
Main Index
CQUAD8 1469
Curved Quadrilateral Shell Element Connection
CQUAD8 Curved Quadrilateral Shell Element Connection
Defines a curved quadrilateral shell or plane strain element with eight grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CQUAD8 EID PID G1 G2 G3 G4 G5 G6
G7 G8 T1 T2 T3 T4 THETA or ZOFFS
MCID
TFLAG
Example:
CQUAD8 207 3 31 33 73 71 32 51
53 72 0.125 0.025 0.030 .025 30. .03
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHELL, PCOMP, PCOMPG or PLPLANE or
PLCOMP entry. (Integer > 0)
G1, G2, G3, G4 Identification numbers of connected corner grid points. Required data for all four grid
points. (Unique Integers > 0)
G5, G6, G7, G8 Identification numbers of connected edge grid points. Optional data for any or all four
grid points for Nastran conventional element only. (Integer > 0 or blank).
Note that for advanced nonlinear elements, partial specification of mid-points is not
allowed. i.e. either none of the mid-points should be specified or all of the mid points
should be specified.
Ti Membrane thickness of element at grid points G1 through G4. If “TFLAG” zero or
blank, then Ti are actual user specified thickness. See Remark 4. for default. (Real > 0.0
or blank, not all zero.) If “TFLAG” one, then the Ti are fraction relative to the T value
of the PSHELL. (Real > 0.0 or blank, not all zero. Default = 1.0) Ti are ignored for
hyperelastic elements.
THETA Material property orientation angle in degrees. See Figure 9-51. THETA is ignored for
hyperelastic elements. See Remark 10. (Real; Default = 0.0)
MCID Material coordinate system identification number. The x-axis of the material coordinate
system is determined by projecting the T1-axis of the MCID coordinate system onto the
surface of the shell element as follows:
CORD1R, x -axis of MCID the coordinate is projected onto shell surface and the
CORD2R material angle is measured from the G1-G2 line to the to the projected
x-axis
Main Index
1470 CQUAD8
Curved Quadrilateral Shell Element Connection
Describer Meaning
CORD1C, r-axis of MCID the coordinate is projected onto shell surface through the
CORD2C element center and the material angle is measured from the G1-G2 line
CORD1S, to the to the projected r-axis
CORD2S
(see Remark 3.) MCID is ignored for hyperelastic elements. See Remark 10. (Integer > 0;
if blank, then THETA = 0.0 is assumed.)
ZOFFS Offset from the surface of grid points to the element reference plane. See Remark 6.
ZOFFS is ignored for hyperelastic elements. (Real)
TFLAG An integer flag, signifying the meaning of the Ti values. (Integer 0, 1, or blank)
Remarks:
1. Element identification numbers should be unique with respect to all other element IDs of any kind.
2. Grid points G1 to G8 must be numbered as shown in Figure 9-51.
3. The orientation of the material property coordinate system is defined locally at each interior
integration point by THETA, which is the angle between xmaterial and the line of constant .
The definition of the material coordinate system by projection is used to calculate an angle THETA.
Please note that since xi changes directions throughout the element based on element shape, the
material coordinate system varies similarly. Because of this an orthotropic or anisotropic material will
cause the CQUAD8’s stiffness to be biased by both it’s shape and grid ordering. Use the QUAD4
element if a constant material coordinate system direction is desired with orthotropic and anisotropic
materials.
4. T1, T2, T3 and T4 are optional. If they are not supplied and no TFLAG, then T1 through T4 will
be set to the value of T on the PSHELL entry.
5. It is recommended that the midside grid points be located within the middle third of the edge. If the
edge point is located at the quarter point, the program may fail with a divide-by-zero error or the
calculated stresses will be meaningless.
6. Elements may be offset from the connection points by means of the ZOFFS field. Other data, such
as material matrices and stress fiber locations, are given relative to the reference plane. A positive value
of ZOFFS implies that the element reference plane is offset a distance of ZOFFS along the positive
z-axis of the element coordinate system. If the ZOFFS field is used, then both the MID1 and MID2
fields must be specified on the PSHELL entry referenced by PID.
Two methods are available for the computation of offsets: original and enhanced. The default method
is the original method. The enhanced method is requested by the Bulk Data entry
MDLPRM,OFFDEF,LROFF. For options of offsets, please refer to the Bulk Data entry
MDLPRM,OFFDEF,option.
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, it is highly recommended to use MDLPRM, OFFDEF, LROFF. In SOL103, if the
case control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then
MDLPRM, OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
Main Index
CQUAD8 1471
Curved Quadrilateral Shell Element Connection
7. If all midside grid points are deleted, then the element will be excessively stiff and the transverse shear
forces incorrect. A User Warning Message is printed, and a CQUAD4 element is recommended
instead. If the element is hyperelastic, then it is processed identically to the hyperelastic CQUAD4
element.
8. For a description of the element coordinate system, see Shell Elements (CTRIA3, CTRIA6, CTRIAR, CQUAD4,
CQUAD8, CQUADR) in the MSC Nastran Reference Guide. Stresses and strains are output in the local
coordinate system identified by x l and y l in Figure 9-51. However, for hyperelastic elements the
stress and strain are output in the coordinate system identified by the CID field on the PLPLANE
entry.
9. For hyperelastic elements the plot codes are specified under the CQUADFD element name in Item
Codes.
yl yl
G7 yl
G3 xmaterial
G4 xl
yl
xl + THETA
4
xl
Gi/4
i=1 xl
Center
G8
G6
yl yl
xl
G5
THETA G2 xl
G1
Stress output at each
Gi local system
where
e is tangent to at Gi
e is tangent to at Gi
A is formed by bisection of e and e
B and A are perpendicular
y l is formed by bisection of A and B
x l is perpendicular to y l
Main Index
1472 CQUAD8
Curved Quadrilateral Shell Element Connection
e
yl
B e
A
2
= 45 – ---
45 2
Gi
xl
Figure 9-51 CQUAD8 Element Geometry and Coordinate Systems
10. If element has an associated PSHLN2 or PLCOMP entry with BEHi=COMPS code, the
THETA/MCID value on the element connection entry will be ignored.
Main Index
CQUADR 1473
Quadrilateral Plate Element Connection
CQUADR Quadrilateral Plate Element Connection
Defines an isoparametric membrane and bending quadrilateral plate element. This element has a normal
rotational (drilling) degrees-of-freedom. It is a companion to the CTRIAR element.
Format:
1 2 3 4 5 6 7 8 9 10
CQUADR EID PID G1 G2 G3 G4 THETA or ZOFFS
MCID
TFLAG T1 T2 T3 T4
Example:
CQUADR 82 203 31 74 75 32 2.6
1.77 2.04 2.09 1.80
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHELL, PCOMP or PCOMPG entry.
(Integer > 0; Default = EID)
Gi Grid point identification numbers of connection points.
(Integers > 0, all unique)
THETA Material property orientation angle in degrees. See Figure 9-75. (Real; Default = 0)
MCID Material coordinate system identification number. The x-axis of the material coordinate
system is determined by projecting the T1-axis of the MCID coordinate system onto the
surface of the shell element as follows:
CORD1R, x -axis of MCID the coordinate is projected onto shell surface and the
CORD2R material angle is measured from the G1-G2 line to the to the projected
x-axis
CORD1C, r-axis of MCID the coordinate is projected onto shell surface through the
CORD2C element center and the material angle is measured from the G1-G2 line
CORD1S, to the to the projected r-axis
CORD2S
Use DIAG 38 to print the computed THETA values. (Integer > 0; If blank, then
THETA = 0.0 is assumed.)
ZOFFS Offset from the surface of grid point to the element plane. See Remark 7.
Main Index
1474 CQUADR
Quadrilateral Plate Element Connection
x
MCID
Coordinate
System
z
G2
y G3
ymaterial
xmaterial
G4
G1
Figure 9-52 MCID Coordinate System Definition
TFLAG An integer flag, signifying the meaning of the Ti values. (Integer 0, 1, or blank)
Ti Membrane thickness of element at grid points G1 through G4. If “TFLAG” zero or
blank, then Ti are actual user specified thickness. (Real > 0.0 or blank, not all zero.
See Remark 4. for default.) If “TFLAG” one, then the Ti are fraction relative to the T
value of the PSHELL. (Real > 0.0 or blank, not all zero. Default = 1.0) Ti are ignored
for hyperelastic elements.
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Grid points G1 through G4 must be ordered consecutively around the perimeter of the element.
3. All the interior angles must be less than 180.
4. The continuation is optional. If it is not supplied, then T1 through T4 will be set equal to the value
of T on the PSHELL entry.
5. Stresses and strains are output in the element coordinate system at the centroid and grid points G1
through G4.
6. Inaccurate results will be obtained if interior grids have the rotation normal (drilling) to the element
constrained. At the boundary of a model, the drilling degrees-of-freedom must be constrained if the
user wants a fixed boundary. Also, for this element it is critical that consistent membrane (in plane)
edge loads be applied. Reference the PLOAD4 entry (SORL option) and the Consistent Surface and Edge
Loads in the MSC Nastran Reference Guide for additional information.
Main Index
CQUADR 1475
Quadrilateral Plate Element Connection
yelement
G3
G4
+
= ------------ xelement
2
xmaterial
zelement
THETA
G1 G2
Figure 9-53 CQUADR Element Geometry and Coordinate Systems
7. Elements may be offset from the connection points by means of ZOFFS. Other data, such as material
matrices and stress fiber locations, are given relative to the reference plane. A positive value of ZOFFS
implies that the element reference plane is offset a distance of ZOFFS along the positive Z-axis of the
element coordinate system. If the ZOFFS field is used, then the MID1 and MID2 fields must be
specified on the PSHELL entry referenced both by PID.
Two methods are available for the computation of offsets: original and enhanced. The default method
is the original method. The enhanced method is requested by the Bulk Data entry
MDLPRM,OFFDEF,LROFF. For options of offsets, please refer to the Bulk Data entry
MDLPRM,OFFDEF,option.
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, it is highly recommended to use MDLPRM, OFFDEF, LROFF. In SOL103, if the
case control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then
MDLPRM, OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
For SOLs 106, 129, 153, and 159 the differential stiffness for offset vectors will give incorrect results
with PARAM, LGDISP, 1. In addition in SOLs 106 and 129 offset vectors will produce incorrect
results with thermal loading.
Main Index
1476 CQUADX
Axisymmetric Quadrilateral Element (Fully Nonlinear or Linear Harmonic)
CQUADX Axisymmetric Quadrilateral Element (Fully Nonlinear or Linear Harmonic)
Defines an axisymmetric quadrilateral element with up to nine grid points for use in fully nonlinear (i.e., large
strain and large rotations) analysis or a linear harmonic or rotordynamic analysis. The element has between
four and nine grid points
Format:
1 2 3 4 5 6 7 8 9 10
CQUADX EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 THETA or
MCID
Example:
CQUADX 111 203 31 74 75 32
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000). See Remark 1.
PID Property identification number of a PLPLANE or PAXSYMH or PLCOMP entry.
(Integer > 0). See Remark 2.
G1, G2 Identification numbers of connected corner grid points. Required data for all four grid
G3, G4 points. (Unique Integers > 0). See Remark 3., 6., 7.
G5, G6 Identification numbers of connected edge grid points. Optional data for any or all four
G7, G8 grid points. (Integer > 0 or blank). See Remark 3., 4., 6., 7.
G9 Identification number of center grid point. Optional. (Integer > 0 or blank). Not used
for linear harmonic elements. See Remark 3., 6., 7.
THETA Material property orientation angle in degrees. THETA is only applicable if PLCOMP
referenced, or the PLPLANE entry has an associated PSHLN2 entry which is honored
only in SOL 400. For PSHLN2 BEHi=AXSOLID code, THETA is measured relative
to the R axis of the element. For PSHLN2 or PLCOMP BEHi=AXCOMP code the
THETA value on the element connection entry will be ignored. (Real; Default = 0.0).
THETA is ignored if PID refers to a PAXSYMH entry.
MCID Material coordinate system identification number, MCID is only applicable if
PLCOMP referenced, or the PLPLANE entry has an associated PSHLN2 entry which
is honored only in SOL 400. The x-axis of the material coordinate system is determined
by projecting the x-axis of the MCID coordinate system onto the surface of the
element. For PSHLN2 BEHi=AXSOLID the resulting angle is measured relative to the
R axis of the element. For PSHLN2 (or PLCOMP) BEHi=AXCOMP code the MCID
value on the element connection entry will be ignored. (Integer > 0; If blank, then
THETA = 0.0 is assumed.)
Main Index
CQUADX 1477
Axisymmetric Quadrilateral Element (Fully Nonlinear or Linear Harmonic)
Remarks:
1. Element identification numbers should be unique with respect to all other element IDs of any kind.
2. If PID refers to a PLPLANE or PLCOMP entry, CQUADX defines an element for use in fully
nonlinear analysis. If PID refers to a PAXSYMH entry, CQUADX defines a linear harmonic element
for use in rotordynamic or harmonic analysis.
3. Gi must be numbered as shown in Figure 9-54.
4. It is recommended that the edge points be located within the middle third of the edge.
5. The plot codes are specified under the CQUADXFD element name in Item Codes.
6. All Gi must lie on the x-y plane of the basic coordinate system. Stress and strain are output in the
basic coordinate system.
7. A concentrated load (e.g., FORCE entry) at Gi is multiplied by the radius to Gi and then applied as
a force per unit circumferential length. For example, in order to apply a load of 100 N/m on the
circumference at G1, which is located at a radius of 0.5 m, then the magnitude specified on the static
load entry must result in:
(100 N/m) (0.5 m) = 50 N
z = ybasic
= 1 G7
G4
G3
= constant
Lines of
= –1 = 0 = 1
Constant or
= 0 = constant
G8 G9 G6
= –1
G5 G2
G1
r = xbasic
Figure 9-54 CQUADX Element Coordinate System
Main Index
1478 CRAC2D
Two-Dimensional Crack Tip Element
CRAC2D Two-Dimensional Crack Tip Element
Defines a two-dimensional crack tip element.
Format:
1 2 3 4 5 6 7 8 9 10
CRAC2D EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13 G14
G15 G16 G17 G18
Example:
CRAC2D 114 108 2 5 6 8 7 11
12 14 16 17 20 22
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PRAC2D entry. (Integer > 0)
Gi Grid point identification numbers of connection points. (Integer > 0; G11 through
G18 may be blank.)
Remarks:
1. CRAC2D is a dummy element and requires the presence of this Bulk Data entry:
ADUM8 18 0 5 0 CRAC2D
2. The element should be planar. Significant deviations will produce fatal errors.
3. Grid points G1 through G10 are required while grid points G11 through G18 are optional for the
quadrilateral form of the element.
4. The stresses and stress intensity factors are calculated assuming that G2 and G10 are coincident.
Deviations from this will produce erroneous results.
5. For the symmetric half-crack option, grid points G1 through G7 are required while grid points G11
through G14 are optional. Grid points G8 through G10 and G15 through G18 must not be present
for this option.
6. The ordering conventions for the full-crack and half-crack options are shown in Figure 9-55.
7. The ratio of the element dimensions in the y to x axis shown for the element coordinate system in
Figure 9-55 should be in the range 2.0 to 0.5.
8. The stress output is interpreted as shown in Crack Tip Elements (CRAC2D, CRAC3D) in the MSC Nastran
Reference Guide.
Main Index
CRAC2D 1479
Two-Dimensional Crack Tip Element
G3 G12 G4 G13 G5
G11 G14
G2 G1 G6
x
G10
G18 G15
G9 G17 G8 G16 G7
(a) Full Crack Option
G3 G12 G4 G13 G5
G11 G14
x
G2 G1 G7 G6
(b) Symmetric Half-Crack Option
Figure 9-55 CRAC2D Element Connection for Full and Symmetric Options
Main Index
1480 CRAC3D
Three-Dimensional Crack Tip Element
CRAC3D Three-Dimensional Crack Tip Element
Defines a three-dimensional crack tip element.
Format:
1 2 3 4 5 6 7 8 9 10
CRAC3D EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13 G14
G15 G16 G17 G18 G19 G20 G21 G22
G23 G24 G25 G26 G27 G28 G29 G30
G31 G32 G33 G34 G35 G36 G37 G38
G39 G40 G41 G42 G43 G44 G45 G46
G47 G48 G49 G50 G51 G52 G53 G54
G55 G56 G57 G58 G59 G60 G61 G62
G63 G64
Example:
CRAC3D 113 101 2 5 7 8 4 10
11 14 15 17 3 6 9
12 16 102 105 107 108
104 110 111 114 115 117 103
106 109 112 116 202 205
207 208 204 210 211 214 215 217
225 226
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PRAC3D entry. (Integer < 0)
Gi Grid point identification numbers of connection points. (Integer > 0)
Remarks:
1. CRAC3D is a dummy element and requires the presence of this Bulk Data entry:
ADUM9 64 0 6 0 CRAC3D
2. Element identification numbers should be unique with respect to all other element identification
numbers.
Main Index
CRAC3D 1481
Three-Dimensional Crack Tip Element
3. This element, including grid point numbering conventions, is shown in Figure 9-56 and Figure 9-57.
Grid points G1 through G10, and G19 through G28 are required; midside and surface grid points
G11 through G18, G29 through G36, and G37 through G64 are optional. Either all or none of grid
points G37 through G46 should be present. A fatal error message will be issued for partial
connectivity.
4. The ratio of the element dimensions in the y to x axis shown for the element coordinate system in
Figure 9-56 should be in the range 2.0 to 0.5.
5. For the symmetric half-crack option Grid Points G1 through G7, and G19 through G25 are
required, whereas grid points G11 through G14, G29 through G32, and G37 through G42 are
optional. Grid points G8 through G10, G15 through G18, G26 through G28, G33 through G36,
G43 through G46, G51 through G55, and G60 through G64 should not be specified to invoke this
option.
6. It is recommended that both the faces (formed by grid points G2 through G18 and grid points G20
through G36) and the midplane (formed by grid points G37 through G46 and grid points G37
through G46) be planar. It is also recommended that midside grid points G37 through G46 be
located within the middle third of the edges.
7. The midside nodes on both the faces should be defined in pairs. For example, if grid point G11 is
not defined, then grid point G29 should not be defined and vice versa.
8. The stresses and stress intensity factors are calculated with the assumptions that grid points G2 and
G10, G20 and G28, and G38 and G46 are coincident. Deviation from this condition will produce
erroneous results.
9. The stress output is interpreted as shown in Crack Tip Elements (CRAC2D, CRAC3D) in the MSC Nastran
Reference Guide.
10. As depicted in Figure 9-56 and Figure 9-57, the element is a right-handed element. Thus define the
vectors G1G9 and G1G3 , then the cross-product G1G9 G1G3 points to the face defined by
G19, G20, ...
Main Index
1482 CRAC3D
Three-Dimensional Crack Tip Element
G21 G22
G23
G20
G19 G24
G28
G27 G26 G25
y
G4 G5
G3
(a) Brick Crack Option with Required
G2 G6 Connection Points Only.
x
G10 G1
G9 G8 G7 G21 G22 G23
G25
G20 G24
G19
G4 G5 (b) Symmetric Half-Crack Option
G3 with Required Connection Points
Only.
x
G2 G1 G7 G6
Figure 9-56 CRAC3D Solid Crack Tip Element with Required Connection Points Only
Main Index
CRAC3D 1483
Three-Dimensional Crack Tip Element
G21 G30 G22 G31 G23
YB G57 G58 G59
G29 G32
G56
G20 G19 G60
G24
G39 G64
G40 G28
G41
y Y1 G36 G63 G61
G33
X1 G62
G25
G38 G27 G35 G26 G34
G37 G42
XB
G46
G12 G4 G13
G3 G5
G48 G50
G11 G14 G45 G44 G43
G49
G1
G47 G51
G2 x
G10 G55 G6
G54 G52
G18
G53
G15 (a) Brick Crack Option
G9 G17 G8 G16 G7
G21 G30 G22 G31 G23
G29 G57 G58 G59 G32
G20 G19 G25 G24
G56
G40
G39 G41
G38
G37 G42
G3 G12 G4 G13
G5
G48 G50
G11 G14 (b) Symmetric Half-Crack Option
G49
G2 G47 G1 G7 G6
Figure 9-57 CRAC3D Solid Crack Tip Element with All Connection Points
Main Index
1484 CREEP
Creep Characteristics
CREEP Creep Characteristics
Defines creep characteristics based on experimental data or known empirical creep law. This entry will be
activated if a MAT1, MAT2, or MAT9 entry with the same MID is used and the NLPARM entry is prepared
for creep analysis. The creep formulation is principally suited for isotropic materials and, in general, when
used with anisotropic materials may produce incorrect results. However, slightly anisotropic materials may
produce acceptable results.
Format:
1 2 3 4 5 6 7 8 9 10
CREEP MID T0 EXP FORM TIDKP TIDCP TIDCS THRESH
TYPE a b c d e f g
Example:
CREEP 8 1100. CRLAW
121 6.985-6 2.444 7.032-4 0.1072 6.73-9 0.1479 3.0
Describer Meaning
MID Material identification number of a MAT1, MAT2, or MAT9 entry. (Integer > 0)
T0 Reference temperature at which creep characteristics are defined. See Remark 2. (Real;
Default = 0.0)
– H R T0
EXP Temperature-dependent term, e , in the creep rate expression. See
Remark 2. (0.0 < Real < 1.0; Default = 1.0E-9)
FORM Form of the input data defining creep characteristics. (Character: “CRLAW” for
empirical creep law, or “TABLE” for tabular input data of creep model parameters.)
TIDKP, Identification number of a TABLES1 entry, which defines the creep model parameters
TIDCP, K p , C p , and C s , respectively. See Remarks 3. through 4. (Integer > 0)
TIDCS
THRESH Threshold limit for creep process. Threshold stress under which creep does not occur
is computed as THRESH multiplied by Young’s modulus. (0.0 < Real < 1.0E-3;
Default = 1.0E-5)
TYPE Identification number of the empirical creep law type. See Remark 1. (Integer: 111,
112, 121, 122, 211, 212, 221, 222, or 300)
a through g Coefficients of the empirical creep law specified in TYPE. Continuation should not be
specified if FORM = “TABLE”. See Remark 1. (Real)
Remarks:
1. Two classes of empirical creep law are available.
Creep Law Class 1
Main Index
CREEP 1485
Creep Characteristics
The first creep law class is expressed as:
c – R t
t = A 1 – e + K t (9-3)
Parameters A , R , and K are specified in the following form, as recommended by Oak
Ridge National Laboratory:
Parameter Function 1 Digit Function 2 Digit
b
A a i=1 b i=2
ae
d
R ce j=1 d j=2
c
g
K e sinh f k=1 f k=2
ee
TYPE=ijk where i, j, and k are digits equal to 1 or 2, according to the desired function in the table
b d f
above. For example, TYPE=122 defines A = a , R = c , and K = ee .
Creep Law Class 2
The second creep law class (TYPE=300) is expressed as:
c b d
t = a t (9-4)
where the values of b and d must be defined as follows:
The above expression is determined by curve fitting using a Newton-Raphson procedure based on the
expressions:
c 1 d
= C p K pi = --------- (9-5)
a b
where is the effective stress and the nonlinear equation:
2 to 2
e – 1 – t 0 – t 0 d = 0
Then the creep model parameters are determined by:
c
1-
----- e d 1 – d
= -------- 1 – --------------------
Cs t0 t0
c t0 c
1- 2
----- = ---- ----- 1 – d d – ------ + -----
Kp t Cs
0
Main Index
1486 CREEP
Creep Characteristics
C p = K p
To keep the solution of these expressions stable, the values of b and d are recommended to be defined
as follows:
1.0 < b < 8.0
and
0.2 < d < 2.0
The coefficient g should be blank if TYPE = 112, 122, 222, or 212 and c, e, f, and g should be blank
if TYPE = 300. The coefficients a through g are dependent on the structural units; caution must be
exercised to make these units consistent with the rest of the input data.
2. Creep law coefficients a through g are usually determined by least squares fit of experimental data,
obtained under a constant temperature. This reference temperature at which creep behavior is
characterized must be specified in the T0 field if the temperature of the structure is different from this
reference temperature. The conversion of the temperature input (F or C) to K (degrees Kelvin)
must be specified in the PARAM,TABS entry as follows:
PARAM,TABS,273.16 (If Celsius is used.)
PARAM,TABS,459.69 (If Fahrenheit is used.)
When the correction for the temperature effect is required, the temperature distribution must be
defined in the Bulk Data entries (TEMP, TEMPP1 and/or TEMPRB), which are selected by the Case
Control command TEMP(LOAD) = SID within the subcase.
From the thermodynamic consideration, the creep rate is expressed as:
·C · – H RT
= A e (9-6)
where:
H = energy of activation
R = gas constant (= 1.98 cal/mole
T = absolute temperature
·
A = strain/sec per activation
If the creep characteristics are defined at temperature T0, the creep rate at temperature T is corrected
by a factor
T0
------ – 1
·c T
-----
= EXP (9-7)
·c
o
where:
Main Index
CREEP 1487
Creep Characteristics
·c
= corrected creep rate
·c
o = creep rate at T0
T0
------ – 1
T = correction factor
EXP
3. Creep model parameters Kp, Cp, and Cs represent parameters of the uniaxial rheological model as
shown in Figure 9-58.
Tabular values (Xi, Yi) in the TABLES1 entry correspond to (i,Kpi), (i,Cpi), and (i,Csi) for the
input of Kp, Cp, and Cs, respectively. For linear viscoelastic materials, parameters Kp, Cp, and Cs are
constant and two values of i must be specified for the same value of Kpi, Cpi, and Csi.
Primary
Elastic Creep Secondary Creep
Kp
Cp t
Ke Cs
Figure 9-58 CREEP Parameter Idealization
Creep model parameters, as shown in Figure 9-59 through Figure 9-61, must have positive values. If the
table look-up results in a negative value, the value will be reset to zero and a warning message (TABLE
LOOK-UP RESULTS IN NEGATIVE VALUE OF CREEP MODEL PARAMETER IN
ELEMENT ID=****) will be issued.
5000
4000
3000
2
K p Kips in
2000
1000
0
5 10 15 20 25 30
ksi
Main Index
1488 CREEP
Creep Characteristics
Figure 9-59 K p Versus Example for CREEP
6
250 10
6
200 10
Kips-hours 6
C p -------------------------- 150 10
2
in 6
100 10
6
50 10
0
5 10 15 20 25 30
ksi
Figure 9-60 C p Versus Example for CREEP
6
50,000 10
6
40,000 10
Kips-hours 6
C s -------------------------- 30,000 10
2
in
6
20,000 10
6
10,000 10
0
5 10 15 20 25 30
ksi
Figure 9-61 C s Versus Example for CREEP
4. Creep analysis requires an initial static solution at t = 0, which can be obtained by specifying a subcase
that requests an NLPARM entry with DT = 0.0.
Main Index
CROD 1489
Rod Element Connection
CROD Rod Element Connection
Defines a tension-compression-torsion element.
Format:
1 2 3 4 5 6 7 8 9 10
CROD EID PID G1 G2
Example:
CROD 12 13 21 23
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PROD entry. (Integer > 0; Default = EID)
G1, G2 Grid point identification numbers of connection points. (Integer > 0; G1 G2 )
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. See CONROD for alternative method of rod definition.
3. Only one element may be defined on a single entry.
Main Index
1490 CROD
Rod Element Connection
P
G2
G1
T
Figure 9-62 CROD Element Internal Forces and Moments
Main Index
CSEAM 1491
A Shell Patch SEAM Connection
CSEAM A Shell Patch SEAM Connection
Defines a SEAM connecting two surface patches.
Format:
1 2 3 4 5 6 7 8 9 10
CSEAM EID PID SMLN CTYPE IDAS IDBS IDAE IDBE
GS GE
Alternate Format:
1 2 3 4 5 6 7 8 9 10
CSEAM EID PID CTYPE IDAS IDBS IDAE IDBE
XS YS ZS XE YE ZE
Example:
CSEAM 552 297 43 48
30422 77987
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSEAM entry. (Integer > 0)
SMLN SEAM line identification. See Remark 2. (CHAR or blank)
CTYPE Connectivity search type. (Character)
If CTYPE = “PSHELL”, IDAS and IDBS are property identification numbers of
PSHELL’s. (Default)
If CTYPE = “ELEM”, IDAS and IDBS are element identification numbers.
IDAS,IDBS Used to define patch A and B or the start of patch A or B for a tailored blank. See
Remark 4. (Integer > 0)
If CTYPE = “PSHELL”, required property id defining patches A and B. If
CTYPE = “PSHELL” and IDAS = IDBS or IDBS = blank the patch will be considered
as two-sided and the property identification numbers of PSHELL’s will be the same for
both the top and bottom. See Remark 6.
If CTYPE = “ELEM”, required element id defining patches A and B. IDAS IDBS.
IDAE,IDBE Used to define the end of patch A and the end of patch B for a tailored blank. See
Remark 4. (Integer > 0 or blank)
If CTYPE = “PSHELL”, property id defining patches A and B. If CTYPE = ‘PSHELL’
and IDAE = IDBE or IDBE=blank the patch will be considered as two-sided and the
property identification numbers of PSHELL’s will be the same for both the top and
bottom.
If CTYPE = “ELEM”, element id defining patches A and B. IDAE IDBE.
Main Index
1492 CSEAM
A Shell Patch SEAM Connection
Describer Meaning
GS, GE Grid ids of piercing points on patches A and B of the Start and End of the SEAM.
(Integer > 0)
XS,YS,ZS Location of the SEAM Start. (Real or blank)
XE,YE,ZE Location of the SEAM End. (Real or blank)
Remarks:
1. Element ID numbers must be unique with respect to all other element ID numbers.
2. With no embedded blanks any combination of up to eight of the acceptable characters in MSC
Nastran may be employed for the SMLN entry.
The seam line will be considered continuous between each connected element and where any two
elements have a common face, the faces of the resulting internal CHEXA’s will be adjusted to a single
common face. If a CSEAM’s GS or GE is not common to the GE or GS of any other CSEAM the
faces will not be adjusted.
A SMLN cannot have a branch.
3. GS and GE define the start and end points of the SEAM element. At these points and using the value
W specified on the PSEAM entry, surface patches A and B are determined. Points are projected onto
the surface patches A and B with the four points at end GS and the four points at end GE then used
to form faces of a CHEXA element.
The auxiliary points forming the faces of the CHEXA element are then connected to the physical
grids of the patches. The number of unique physical grids per patch ranges from a possibility of 6 to
64 grids.
The auxiliary points must have a projection on patches A and B, but they do not have to lie on patch
A or B.
A maximum of three shell elements of patch A and three shell elements of patch B can be connected
with one CSEAM element, see Figure 9-63.
Figure 9-63 Connected Shell Elements for a CSEAM Element
Main Index
CSEAM 1493
A Shell Patch SEAM Connection
4. For CTYPE = ‘PSHELL’
If patch A is uniform in thickness, then only its IDAS is needed to define it.
If patch B is uniform in thickness, then only its IDBS is needed to define it.
If patch A has stepped tapering, then IDAS and IDAE are used to define it.
If patch B has stepped tapering, then IDBS and IDBE are used to define it.
5. Projection Algorithms for the CSEAM Elements
Because of complex geometry, the user supplied start point GS may not have a projection SA and SB,
and the end point GE may not have a projection EA and EB. Even though these four projection
points are found, the program still has to find projections for the eight auxiliary points SA1, SA2, …,
EB2, and EB1 of the HEXA. The default projection strategy can be changed by overwriting the
default values of the flags and parameters in the SWLDPRM Bulk Data entry.
a. Find Projections for SA, SB, EA, and EB
For CTYPE = “PSHELL”, the program finds the closest shell grids to GS and GE. The shell
elements that are connected to these closest grids are defined as the candidate shell elements.
While looping through each candidate shell element to compute the projection of GS and GE
onto that element, the program always tries to get the most accurate projection. Even though a
projection is found with PROJTOL > 0.0, the program still continues the projection calculations
using PROJTOL=0.0. If a projection is found with PROJTOL=0.0, that shell element will be
selected as the connecting element. Otherwise, the shell element that gets projection with
PROJTOL>0.0 is selected as EIDSA, EIDSB, EIDEA, or EIDEB. For CTYPE = “ELEM”, the
above processes are skipped, because EIDSA, EIDSB, EIDEA, and EIDEB have already been
specified by the user.
If GSTOL > 0.0 and the distance GS-SA, GS-SB, GE-EA, or GE-EB is greater than GSTOL, a
UFM 7549 is issued and the CSEAM element is rejected.
If the projection of GS or GE lies outside the shell sheet, or the connected shell elements fail the
geometry check with GMCHK > 0, the program will issue a UFM and the CSEAM element will
be rejected.
If GMCHK > 0, the program checks errors of CSEAM across a cutout or over a corner with
elements in plane. The program also computes the angle between the shell normal vectors of
EIDSA and EIDEA and the angle between the shell normal vectors of EIDSB and EIDEB to
check a corner with elements out of plane.
For CTYPE = “PSHELL”, if there is an error detected, the program loops back to compute the
other possibility of projection until a correct connection is found or all candidate shell elements
are processed. In the latter case, either UFM 7638 (the seam spans a cutout) or UFM 7667 (the
seam spans a corner) will be issued. If GMCHK=2, the program also lists all candidate shell
elements with their projection status for each connecting type after issuing a UFM. This will help
the user to select the correct shell elements for EIDSA, EIDSB, EIDEA, and EIDEB.
For CTYPE=”ELEM”, the program only checks errors and issues UFM 7638 or 7667 for the kind
of error encountered. No looping back will be performed.
Main Index
1494 CSEAM
A Shell Patch SEAM Connection
If GMCHK > 0 and GSPROJ > 0.0, the program also computes the angle between the shell
normal vectors of EIDSA and EIDSB and the angle between the shell normal vectors of EIDEA
and EIDEB. A UFM 7595 is issued if the angle between the shell normal vectors is greater than
GSPROJ. By default, GSPROJ = 20o, that means the shell patches A and B can be tilted relative
to each other by not more than 20o.
b. Find Projections of the Eight Auxiliary Points SA1, SA2, …, EB2, and EB1
After the projections for SA, SB, EA, and EB have been found, eight auxiliary points for an
internal hexagonal polygon are formed. If the GS or GE of a CSEAM element is connected to the
GE or GS of another CSEAM element, then the internal HEXA elements are adjusted to a
common face.
If GSPROJ > 0.0 and the angle between the face vectors parallel to the thickness direction of the
internal HEXA and the normal vector of the shell element that gets projection exceeds GSPROJ,
the program will skip picking this shell element and will proceed to process next candidate shell
element.
The most common error condition occurs when the seam lies on the edge of the shell patches.
Under this situation, half of the seam hangs outside the shell sheets (Figure 9-64). It is required that
each of the eight points has a projection. If at least one point does not have a projection and
GSMOVE > 0, GS will be moved by W/2. Same algorithms apply to end E. The move will be
repeated until either all projections are found or the number of moves reaches GSMOVE.
Shell B
SB1 SB2
S
SA1 SA2
Shell A
W/2 W/2
Figure 9-64 Seam Weld at an Edge
c. Error Checks by GMCHK Parameter
The GMCHK parameter specified in the SWLDPRM Bulk Data entry checks the errors of
CSEAM elements across cutouts or over corners. There are three allowable values of GMCHK.
• GMCHK = 0 (Default) Do not check errors
• GMCHK = 1 Check errors
• GMCHK = 2 Check errors and output all candidate shell elements if there is an error encountered
If GMCHK is turned on, Nastran will perform the following checking while searching for the
projected shell elements. Note that EIDSA is the shell element that gets projection from GS on
shell A; EIDEA is the shell element that gets projection from GE on shell A. Same algorithms are
applied to EIDSB and EIDEB for shell B.
d. Check the CSEAM Across a Cutout or Over a Corner with Elements in Plane
• If EIDSA is equal to EIDEA, the seam lies within one element. No checks are required.
Main Index
CSEAM 1495
A Shell Patch SEAM Connection
• If EIDSA and EIDEA share two corner grids, these elements are adjacent. No checks are required.
• If EIDSA and EIDEA share only one corner grid, the seam is over a corner. There are two
exceptions:
There exists a shell element (EIDMA) that shares two corner grids with EIDSA and EIDEA. Also,
either the angle between vector S1S2 and vector E1E4 is greater than CNRAGLI degrees or the
middle point (M) of line segment S2E4 projects to EIDSA, EIDMA, or EIDEA.
S1 E1
S2
E4
EIDSA M
EIDMA
EIDEA
S4
S3 E2
E3
( > CNRAGLI).
This model is acceptable - CONVEX
S2 E4
M
S1 E1
EIDSA
EIDEA
S3
EIDMA
E3
S4
E2
( < CNRAGLI and point M does not project
This model fails - not CONVEX
to EIDSA, EIDMA or EIDEA.
This shared grid is a shell grid of another two different shell elements.
Main Index
1496 CSEAM
A Shell Patch SEAM Connection
S3 S2
S4 E4
S1 E1
E2 E3
• If EIDSA and EIDEA do not share any corner grid, Nastran will check if there is an element
(EIDMA) lying between EIDSA and EIDEA. EIDMA must share two corner grids with EIDSA
and another different one corner grid with EIDEA, or vice versa. The following five examples
demonstrate the acceptable and failed cases.
EIDMA shares one edge with EIDSA and shares one corner grid with EIDEA. This case is
acceptable.
S1 S4
S2 E4
S3 E1
E2 E3
EIDMA shares one edge with IEDEA and shares one corner grid with EIDSA. This case is
acceptable.
E1 E4
S1 E3
S4 E2
S2 S3
Main Index
CSEAM 1497
A Shell Patch SEAM Connection
EIDMA shares one corner grid with EIDSA and shares another corner grid with EIDEA. An error
is detected because the seam spans a cutout.
S1 E4
S4 E1
S2 S3 E2 E3
EIDMA shares one edge with EIDSA and shares another edge with EIDEA. This case is
acceptable.
S1 S4 E1 E4
S2 S3 E2 E3
There does not exist a single element that shares an edge or corner grid with EIDSA or EIDEA.
An error is detected because the length of the seam spans more than three elements.
S1 S4 E1 E4
S2 S3 E2 E3
e. Check the CSEAM Over a Corner with Elements Out of Plane
Main Index
1498 CSEAM
A Shell Patch SEAM Connection
The CNRAGLO parameter is used to check the error of a seam over a corner with EIDSA and
EIDEA not lying on a same plane. An error is detected if the angle between the shell normal
vectors of EIDSA and EIDEA is greater than CNRAGLO. The default value of CNRAGLO is
20o. No angles will be checked if CNRAGLO = -1.
This model fails.( > CNRAGLO)
EIDSA
EIDEA
f. Modeling Guidelines
When there exist multiple pairs of connections, it is recommended that either the GMCHK and
GSPROJ flags be turned on to filter out tilted connections or the ELEM option be used to specify
the IDs of the connected shell elements directly. For example, if EIDA1 is connected to EIDB2
or EIDA2 is connected to EIDB1, the element tangent vectors will be computed wrong and the
auxiliary points will not be able to find connected shell elements.
EIDB1 EIDA 1
GS EIDA2
EIDB 2
6. The projection algorithm for the two-sided option will be the same as in Remark 5. above once the
two patches A and B have been established. The program will find the closest shell grids to GS and
GE as usual for candidate shell elements for patch A.
It will compute the normal for the candidate patch A (similar for GE) and for the candidate patch B.
If the normals are approximately aligned (within a tolerance) the algorithm will proceed as in Remark
5.
If the normals of the candidate patch’s A and B do not align within a specified tolerance, the
algorithm will use another set of pairs of grids for candidate patches to find a new patch A and B. If
their normals align within a specified tolerance it will proceed as in Remark 5. If after processing all
reasonable pairs of patches, no alignment of normals are found or the patches A and B at GE have
different normal alignment from the patches A and B at GB, a user fatal will be issued.
Main Index
CSEAM 1499
A Shell Patch SEAM Connection
Note: For the two-sided option, GS and GB must lie between patches A and B. Also, the shell
elements that get projections from GS/GE cannot share a common shell grid. This
option always selects the patch with the shell grids closest to GS/GE as patch A. Avoid
having GS/GE exactly midway between the two patches.
7. If used in a multi-physics coupled problem using SUBSTEP, they participate in the mechanical
substep but are ignored in the heat transfer subsstep through automatic deactivation. For more
information on deactivation, see the DEACTEL keyword under the NLMOPTS Bulk Data entry and
the associated Remark 10. for that entry.
8. The CSEAM contributes to MASS if its PSEAM entry has an associated MATi entry with a non-zero
density. PARAM,COUPMASS effects the mass calculation. In SOL400, the behavior of this element
in regard to large rotation is affected by the Case Control Command Rigid.
9. If partitioned superelements are present, then CSEAM is supported in the main Bulk Data section
only.
Main Index
1500 CSET
Free Boundary Degrees-of-Freedom
CSET Free Boundary Degrees-of-Freedom
Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during generalized dynamic reduction or
component mode synthesis calculations.
Format:
1 2 3 4 5 6 7 8 9 10
CSET ID1 C1 ID2 C2 ID3 C3 ID4 C4
Example:
CSET 124 1 5 23 6 16
Describer Meaning
IDi Grid or scalar point identification number. (Integer > 0)
Ci Component number. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points. No embedded blanks.)
Remarks:
1. CSET and BNDFREE entries are equivalent to each other. Either one of them or any combination
of them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on CSETi/BNDFREE/BNDFRE1 entries form members of the
mutually exclusive c-set. They may not be specified on other entries that define mutually exclusive
sets. See the Degree-of-Freedom Sets for a list of these entries.
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
5. SOL 400 does not support OMITAX as well as ASETi, OMITi, BSETi, CSETi, SUPORTi, and
QSETi except in some situations (See Remark 4. under ASET).
Main Index
CSET1 1501
Free Boundary Degrees-of-Freedom, Alternate Form of CSET Entry
CSET1 Free Boundary Degrees-of-Freedom, Alternate Form of CSET Entry
Defines analysis set (a-set) degrees-of-freedom to be free (c-set) during generalized dynamic reduction or
component mode synthesis calculations.
Format:
1 2 3 4 5 6 7 8 9 10
CSET1 C ID1 ID2 ID3 ID4 ID5 ID6 ID7
ID8 ID9 ID10 -etc.-
Example:
CSET1 124 1 5 7 6 9 12 122
127
Alternate Formats and Examples:
CSET1 C ID1 “THRU” ID2
CSET1 3 6 THRU 32
CSET1 “ALL”
CSET1 ALL
Describer Meaning
C Component numbers. (Integer zero or blank for scalar points, or any unique
combinations of the Integers 1 through 6 for grid points with no embedded blanks.)
IDi Grid or scalar point identification numbers. (Integer > 0; For “THRU” option,
ID1< ID2)
Remarks:
1. CSET1 and BNDFRE1 entries are equivalent to each other. Either one of them or any combination
of them may be employed.
2. If there are no BSETi/BNDFIXi or CSETi/BNDFREE/BNDFRE1 entries present, all a-set points
are considered fixed during component mode analysis. If there are only BSETi/BNDFIXi entries
present, any a-set degrees-of-freedom not listed are placed in the free boundary set (c-set). If there are
only CSETi/BNDFREE/BNDFRE1 entries present or both BSETi/BNDFIXi and
CSETi/BNDFREE/BNDFRE1 entries present, the c-set degrees-of-freedom are defined by the
CSETi/BNDFREE/BNDFRE1 entries, and any remaining a-set points are placed in the b-set.
3. Degrees-of-freedom specified on CSETi/BNDFREE/BNDFRE1 entries form members of the
mutually exclusive c-set. They may not be specified on other entries that define mutually exclusive
sets. See the Degree-of-Freedom Sets for a list of these entries.
Main Index
1502 CSET1
Free Boundary Degrees-of-Freedom, Alternate Form of CSET Entry
4. If PARAM,AUTOSPC is YES, then singular b-set and c-set degrees-of-freedom will be reassigned as
follows:
• If there are no o-set (omitted) degrees-of-freedom, then singular b-set and c-set degrees-of-
freedom are reassigned to the s-set.
• If there are o-set (omitted) degrees-of-freedom, then singular c-set degrees-of-freedom are
reassigned to the b-set. Singular b-set degrees-of-freedom are not reassigned.
5. SOL 400 does not support OMITAX as well as ASETi, OMITi, BSETi, CSETi, SUPORTi, and
QSETi except in some situations (See Remark 4. under ASET).
Main Index
CSHEAR 1503
Shear Panel Element Connection
CSHEAR Shear Panel Element Connection
Defines a shear panel element and effective extensional stiffener rods.
Format:
1 2 3 4 5 6 7 8 9 10
CSHEAR EID PID G1 G2 G3 G4
Example:
CSHEAR 3 6 1 5 3 7
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHEAR entry. (Integer > 0; Default = EID)
Gi Grid point identification numbers of connection points. (Integer > 0;
G1 G2 G3 G4 )
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Grid points G1 through G4 must be ordered consecutively around the perimeter of the element.
3. All interior angles must be less than 180.
G3
G4
Yelem
Xelem
G1 G2
Figure 9-65 CSHEAR Element Connection and Coordinate System
Main Index
1504 CSHEAR
Shear Panel Element Connection
K4 F41
K3
F32
F43 q3
G4 G3
F34
q4
q2
K2
K1
F21
G2
q1
F12 G1
F23
F14
Figure 9-66 CSHEAR Element Corner Forces and Shear Flows
4. The parameter entry MDLPRM,SHEARP,GARVEY(default) selects the standard Garvey shear
panel. MDLPRM,SHEARP,HARDER selects the Harder shear panel: The Harder panel is based on
the following:
Consider the following quadrilateral shear panel.
The shear stress is related to the shear strain by the relationship = G where G is the shear modulus.
Determining the value for shear for the general quadrilateral shown is a heuristic process. For the Harder
element it is determined in the following manner. The strain along a diagonal such as L13 is found from the
expression (or Mohr's circle):
Main Index
CSHEAR 1505
Shear Panel Element Connection
13 = x cos 2 13 + x sin 2 13 + xy cos 13 sin 13
With a similar expression for 24 , where 24 = 180 – 13 + . For shear panels, the direct strains are
negligible compared to the shear strain. For a rectangular shear panel 24 = 13 and we have
= 13 – 24 = sin or = 13 – 24 sin .
In the above, the subscripts have been dropped from the term for shear strain. The Harder shear panel uses
this definition for the measure of shear strain in the general quadrilateral. For a rectangular panel it is exact.
For a reasonable panel it is within an error of < 1 degree. To insure reasonableness, all the geometry checks
required by the Garvey element are still performed.
Stress Recovery:
The output for either the Garvey or the Harder panel is the same with the following exception:
MAX SHEAR AVG SHEAR SHEARP
MAX( 1 2 3 4 ) 1 + 2 + 3 + 4 4 GARVEY
MAX( 1 2 3 4 ) (q-Equiv) / t HARDER
For both Garvey and Harder panels, q-Equiv is the shear flow on which all stress calculations are based.
Main Index
1506 CSLOT3
Three Point Slot Element Connection
CSLOT3 Three Point Slot Element Connection
Defines an element connecting three points that solve the wave equation in two dimensions. Used in the
acoustic cavity analysis for the definition of evenly spaced radial slots.
Format:
1 2 3 4 5 6 7 8 9 10
CSLOT3 EID IDS1 IDS2 IDS3 RHO B M
Example:
CSLOT3 100 1 3 2 3.0-3 6
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
IDSi Identification number of connected GRIDS points. (Integer > 0)
RHO Fluid density in mass units. (Real > 0.0; Default is the value of RHOD on the AXSLOT
entry)
B Fluid bulk modulus. (Real > 0.0; Default is the value of BD on the AXSLOT entry)
M Number of slots in circumferential direction. (Integer > 0; Default is the value of MD
on the AXSLOT entry)
Remarks:
1. CSLOT3 is allowed only if an AXSLOT entry is also present.
2. This element identification number (EID) must be unique with respect to all other fluid or structural
elements.
3. If RHO, B, or M are blank, then the RHOD, BD, or MD fields on the AXSLOT entry must be
specified.
4. This element generates three plot elements, connecting points IDS1 to IDS2, IDS2 to IDS3, and
IDS3 to IDS1.
5. If B=0.0, then the slot is considered to be an incompressible fluid.
6. If M=0, then no matrices for CSLOT3 elements are generated.
Main Index
CSLOT4 1507
Four Point Slot Element Connection
CSLOT4 Four Point Slot Element Connection
Defines an element connecting four points that solve the wave equation in two dimensions. Used in acoustic
cavity analysis for the definition of evenly spaced radial slots.
Format:
1 2 3 4 5 6 7 8 9 10
CSLOT4 EID IDS1 IDS2 IDS3 IDS4 RHO B M
Example:
CSLOT4 101 1 3 2 4 6.2+4 3
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
IDSi Identification number of connected GRIDS points. (Integer > 0)
RHO Fluid density in mass units. (Real > 0.0; Default is the value of RHOD on the
AXSLOT entry.)
B Fluid bulk modulus. (Real > 0.0; Default is the value of BD on the AXSLOT entry.)
M Number of slots in circumferential direction. (Integer > 0; Default is the value of MD
on the AXSLOT entry.)
Remarks:
1. This entry is allowed only if an AXSLOT entry is also present.
2. This element identification number (EID) must be unique with respect to all other fluid or structural
elements.
3. If RHO, B, or M are blank, then the RHOD, BD, or MD fields on the AXSLOT entry must be
specified.
4. This element generates four plot elements connecting points IDS1 to IDS2, IDS2 to IDS3, IDS3 to
IDS4, and IDS4 to IDS1.
5. If B = 0.0, then the slot is considered to be an incompressible fluid.
6. If M = 0, then no matrices for CSLOT4 elements are generated.
Main Index
1508 CSPR
Springs With Offsets
CSPR Springs With Offsets
Springs for use in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CSPR EID PID G1 G2
Example:
CSPR 1 22 456 457
Describer Meaning Type Default
EID Element ID. A unique number has to be used. I>0 Required
PID Property ID of PSPRMAT entry I>0 Required
G1 Gridpoint 1 I>0 Required
G2 Gridpoint 2. I>0 Required
Main Index
CSSCHD 1509
Aerodynamic Control Surface Schedule Input
CSSCHD Aerodynamic Control Surface Schedule Input
Defines a scheduled control surface deflection as a function of Mach number and angle of attack.
Format:
1 2 3 4 5 6 7 8 9 10
CSSCHD SlD AESID LALPHA LMACH LSCHD
Example:
CSSCHD 5 50 12 15 25
Describer Meaning
SID Set identification number. (Integer > 0)
AESID ID of an AESURF Bulk Data entry to which the schedule is being attached.
LALPHA ID of an AEFACT Bulk Data entry containing a list of angles of attack (in radians) at
which schedule information is provided. (Integer > 0: Default = no angle information
provided.
LMACH ID of an AEFACT Bulk Data entry containing a list of Mach numbers at which schedule
information is provided. (Integer > 0; Default = no Mach information provided)
LSCHD ID of an AEFACT Bulk Data entry which contains the scheduling information. See
Remarks 4. and 5. (Integer > 0; no Default)
Remarks:
1. Control system schedules must be selected with the Case Control command CSSCHD = SID.
2. The AESID cannot appear on an AELINK or TRIM Bulk Data entry for the same subcase.
3. The control surface deflection is computed using a linear interpolation for the Mach number
provided on the associated TRIM entry and the angle of attack derived as part of the trim calculation.
4. The LSCHD data are provided as a list of deflections (in radians) as a function of Mach numbers and
angles of attack. If there are NMACH Mach numbers and NALPHA angles of attack, the first
NALPHA deflections are for the first Mach number, the next NALPHA are for the second Mach
number, and so on, until the last NALPHA deflections are for the final Mach number.
5. If LALPHA is blank, LSCHD contains NMACH deflections to define the Mach schedule. If
LMACH is blank, LSCHD contains NALPHA deflections to define the angle of attack schedule.
6. LALPHA and LMACH cannot be simultaneously blank. If LALPHA or LMACH are not blank, at
least two values of angle of attack or Mach number must be defined in order to perform interpolation.
7. If the Mach number or angle of attack is outside the range specified by the tabulated values, the value
at the table end is used. That is, data are not extrapolated.
Main Index
1510 CSUPER
Secondary Superelement Connection
CSUPER Secondary Superelement Connection
Defines the grid or scalar point connections for identical or mirror image superelements or superelements
from an external source. These are all known as secondary superelements.
Format:
1 2 3 4 5 6 7 8 9 10
CSUPER SSlD PSID GP1 GP2 GP3 GP4 GP5 GP6
GP7 GP8 -etc.-
Example:
CSUPER 120003 21 3 6 4 10
Describer Meaning
SSID Coded identification number for secondary superelement. See Remark 1. (Integer > 0)
PSID Identification number for referenced primary superelement. See Remark 2. (Integer > 0
or blank)
GPi Grid or scalar point identification numbers of the exterior points of the secondary
superelement. See Remark 3. (Integer > 0)
Remarks:
1. The value of SSID is written in the form XXX0000 + n, where n is the referenced secondary
superelement identification number and n must be less than 10000 and XXX is a displacement
component sign reversal code as follows:
The sign reversal code specifies the displacement component(s) normal to the plane of the mirror
through which the reflection is to be made
Blank or 0 no reversal for identical superelement. If PSID is preceded by a minus sign
and there is no xxx code on SSID, then a z-reversal mirror is generated.
1 x-reversal
2 y-reversal Mirror Images
3 z-reversal
12 x and y-reversal
23 y and z-reversal Identical Images
31 z and x-reversal
123 x, y and z-reversal } Mirror Images
Main Index
CSUPER 1511
Secondary Superelement Connection
2. If PSID = 0 or blank, the superelement boundary matrices are obtained from an external source (such
as a database or external file). See also PARAM, EXTDRUNT.
If PSID 0 , the secondary superelement is identical to, or is a mirror image of, a primary
superelement.
3. For identical or mirror image superelements, the grid point IDs, GPi, may appear in any order.
However, if they are not in the same order as the external GRIDs of the primary superelement, then
the SEQSEP entry is also required. In case of external superelements, the GRID IDs must be in the
order that the terms in the associated matrices occur in.
4. Image superelements and their primaries must be congruent. The identical or mirror image
superelement must have the same number of exterior grid points as its primary superelement. The
exterior grid points of the image superelement must have the same relative location to each other as
do the corresponding points of the primary superelement. The global coordinate directions of each
exterior grid point of the image superelement must have the same relative alignment as those of the
corresponding grid points of the primary superelement. If congruency is not satisfied because of
round-off, then the tolerance may be adjusted with PARAM,CONFAC or DIAG 37.
5. For superelements from an external source, please refer to PARAMS EXTDR, EXTDRUNT and EXTUNIT.
Main Index
1512 CSUPEXT
Superelement Exterior Point Definition
CSUPEXT Superelement Exterior Point Definition
Assigns exterior points to a superelement.
Format:
1 2 3 4 5 6 7 8 9 10
CSUPEXT SEID GP1 GP2 GP3 GP4 GP5 GP6 GP7
Example:
CSUPEXT 2 147 562 937
Alternate Format and Example:
CSUPEXT SEID GP1 “THRU” GP2
CSUPEXT 5 12006 THRU 12050
Describer Meaning
SEID Identification number of a primary superelement. (Integer > 0)
GPi Grid or scalar point identification number in the downstream superelement or residual
structure. (Integer > 0 or “THRU”; for “THRU” option, GP1 < GP2)
Remarks:
1. Grid or scalar points are connected (that is, are exterior) to a superelement only if they are connected
by structural, rigid, or plot elements. MPC entries are not regarded as elements. This entry is a means
of providing connectivity for this purpose.
2. Open sets are allowed with the “THRU” option.
3. Scalar points may be interior to the residual structure (SEID = 0) only.
4. This entry may be applied only to the primary superelements. The CSUPER entry is used for
secondary superelements (identical image, mirror image, and external superelements).
Main Index
CTETRA 1513
Four-Sided Solid Element Connection
CTETRA Four-Sided Solid Element Connection
Defines the connections of the four-sided solid element with four to ten grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CTETRA EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10
Example:
CTETRA 112 2 3 15 14 4 103 115
5 16 8 27
Describer Meaning Type Default
EID Element identification number. 0 < Integer < 100,000,000 Required
PID Property identification number of a PSOLID Integer > 0 Required
or PLSOLID entry.
Gi Identification numbers of connected grid Integer > 0 or blank Required
points.
G4
G8
G10
G9
G3
G7
G1
G6
G5
G2
Figure 9-67 CTETRA Element Connection
Main Index
1514 CTETRA
Four-Sided Solid Element Connection
Remarks:
1. Element ID numbers must be unique with respect to all other element ID numbers.
2. The topology of the diagram must be preserved, i.e., G1, G2, G3 define a triangular face; G1, G8,
and G4 are on the same edge, etc.
3. The edge points, G5 to G10, are optional. For Nastran conventional elements, any or all of them may
be deleted. If the ID of any edge connection point is left blank or set to zero, the equations of the
element are adjusted to give correct results for the reduced number of connections. Corner grid points
cannot be deleted. The element is an isoparametric element in all cases.
Note that for advanced nonlinear elements, partial specification of mid-points is not allowed. i.e.
either none of the mid-points should be specified or all of the mid points should be specified.
4. Components of stress are output in the material coordinate system, except hyperelastic elements
which outputs stress in the basic coordinate system.
5. For nonhyperelastic elements, the element coordinate system is derived from the three vectors R, S,
and T, which join the midpoints of opposite edges.
R vector joins midpoints of edges G1-G2 and G3-G4.
S vector joins midpoints of edges G1-G3 and G2-G4.
T vector joins midpoints of edges G1-G4 and G2-G3.
The origin of the coordinate system is located at G1. The element coordinate system is chosen as
close as possible to the R, S, and T vectors and points in the same general direction. (Mathematically
speaking, the coordinate system is computed in such a way that, if the R, S, and T vectors are
described in the element coordinate system, a 3x3 positive definite symmetric matrix would be
produced.)
Solid elements have both a material and an element coordinate system. Both systems are defined for
the initial geometry, and for geometric nonlinear analysis they will rotate with the element. The
material coordinate system is used to input anisotropic material properties and for stress output. The
material coordinate system is defined by the CORDM field of the PSOLID entry. The element
coordinate system is used for element stiffness integration (reduced shear for example) and optionally
to define the material coordinate system (only if PSOLID,CORDM=-1).
S
G4
G3
G1
T
G2
Main Index
CTETRA 1515
Four-Sided Solid Element Connection
Figure 9-68 CTETRA Element R, S, and T Vectors
6. It is recommended that the edge points be located within the middle third of the edge.
7. For hyperelastic elements, the plot codes are specified under the CTETRAFD element name in Item
Codes.
8. By default, all of the six edges of the element are considered straight unless, any of G5 through G10
are specified.
9. The internal coordinate system of the element is used internally and is based on eigenvalue techniques
to insure non bias in the element formulation. For stress/strain output this internal coordinate system
(CORDM=-1 on PSOLID entry) is hard to visualize. Thus a CORDM=-2 on the PSOLID is
available as shown in Figure 9-69.
Figure 9-69 PSOLID on CTETRA
Main Index
1516 CTRIA3
Triangular Plate Element Connection
CTRIA3 Triangular Plate Element Connection
Defines an isoparametric membrane-bending or plane strain triangular plate element.
Format:
1 2 3 4 5 6 7 8 9 10
CTRIA3 EID PID G1 G2 G3 THETA or ZOFFS
MCID
TFLAG T1 T2 T3
Example:
CTRIA3 111 203 31 74 75 3.0 0.98
1.77 2.04 2.09
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHELL, PCOMP, PCOMPG or PLPLANE
entry. (Integer > 0; Default = EID)
Gi Grid point identification numbers of connection points. (Integers > 0, all unique)
THETA Material property orientation angle in degrees. THETA is ignored for hyperelastic
elements. (Real; Default = 0.0)
MCID Material coordinate system identification number. The x-axis of the material coordinate
system is determined by projecting the T1-axis of the MCID coordinate system onto
the surface of the shell element as follows:
CORD1R, x -axis of MCID the coordinate is projected onto shell surface and the
CORD2R material angle is measured from the G1-G2 line to the to the projected
x-axis
CORD1C, r-axis of MCID the coordinate is projected onto shell surface through
CORD2C the element center and the material angle is measured from the G1-G2
CORD1S, line to the to the projected r-axis
CORD2S
Use DIAG 38 to print the computed THETA values. MCID is ignored for hyperelastic
elements. (Integer > 0; if blank, then THETA = 0.0 is assumed.)
Main Index
CTRIA3 1517
Triangular Plate Element Connection
x MCID
Coordinate
System
y z
G3
ymaterial
G1 G2
xmaterial
Figure 9-70 MCID Coordinate System Definition
ZOFFS Offset from the surface of grid points to the element reference plane. See Remark 3.
ZOFFS is ignored for hyperelastic elements. (Real)
TFLAG An integer flag, signifying the meaning of the Ti values. (Integer 0, 1, or blank)
Ti Membrane thickness of element at grid points G1 through G3. If “TFLAG” zero or
blank, then Ti are actual user specified thickness. (Real > 0.0 or blank, not all zero. See
Remark 4. for default.) If “TFLAG” one, then the Ti are fraction relative to the T value
of the PSHELL. (Real > 0.0 or blank; not all zero. Default = 1.0) Ti are ignored for
hyperelastic elements.
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. The continuation is optional. If it is not supplied, then T1 through T3 will be set equal to the value
of T on the PSHELL entry.
3. Elements may be offset from the connection points by means of the ZOFFS field. Other data, such
as material matrices and stress fiber locations, are given relative to the reference plane. A positive value
of ZOFFS implies that the element reference plane is offset a distance of ZOFFS along the positive
Z-axis of the element coordinate system. If the ZOFFS field is used, then both the MID1 and MID2
fields must be specified on the PSHELL entry referenced by PID.
Main Index
1518 CTRIA3
Triangular Plate Element Connection
Two methods are available for the computation of offsets: original and enhanced. The default method
is the original method. The enhanced method is requested by the Bulk Data entry
MDLPRM,OFFDEF,LROFF. For options of offsets, please refer to the Bulk Data entry
MDLPRM,OFFDEF,option.
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, it is highly recommended to use MDLPRM, OFFDEF, LROFF. In SOL103, if the
case control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then
MDLPRM, OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
For SOLs 106, 129, 153, and 159 the differential stiffness for offset vectors will give incorrect results
with PARAM, LGDISP, 1. In addition in SOLs 106 and 129 offset vectors will produce incorrect
results with thermal loading.
yelement G3
xmaterial
THETA
xelement
G1 G2
Figure 9-71 CTRIA3 Element Geometry and Coordinate Systems
4. The reference coordinate system for the output of stress, strain and element force depends on the
element type.
• For CTRIA3 elements, which are not hyperelastic, the reference coordinate system for output is
the element coordinate system.
• For hyperelastic elements the stress and strain are output according to CID on the PLPLANE
entry.
5. For hyperelastic elements, the plot codes are specified under the CTRIAFD element name in Item
Codes.
6. SYSTEM(218), alias T3SKEW, allows the user to control the minimum vertex angle for TRIA3
elements at which USER WARNING MESSAGE 5491 is issued. The default value is 10. degrees.
7. By default, all of the three edges of the element are considered straight.
Main Index
CTRIA6 1519
Curved Triangular Shell Element Connection
CTRIA6 Curved Triangular Shell Element Connection
Defines a curved triangular shell element or plane strain with six grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CTRIA6 EID PID G1 G2 G3 G4 G5 G6
THETA ZOFFS T1 T2 T3 TFLAG
or MCID
Example:
CTRIA6 302 3 31 33 71 32 51 52
45 .03 .020 .025 .025
Describer Meaning
EID Element Identification number. (0 < Integer < 100,000,000)
PID Property identification number of PSHELL, PCOMP, PCOMPG or PLPLANE entry.
(Integer > 0)
G1, G2, G3 Identification numbers of connected corner grid points. (Unique Integers > 0)
G4, G5, G6 Identification number of connected edge grid points. Optional data for any or all three
points for Nastran conventional element only. (Integer > 0 or blank)
Note that for advanced nonlinear elements, partial specification of mid-points is not
allowed. i.e. either none of the mid-points should be specified or all of the mid points
should be specified.
THETA Material property orientation angle in degrees. THETA is ignored for hyperelastic
elements. (Real; Default = 0.0)
MCID Material coordinate system identification number. The x-axis of the material coordinate
system is determined by projecting the T1-axis of the MCID coordinate system onto the
surface of the shell element as follows:
CORD1R, x -axis of MCID the coordinate is projected onto shell surface and the
CORD2R material angle is measured from the G1-G2 line to the to the projected x-
axis
CORD1C, r-axis of MCID the coordinate is projected onto shell surface through the
CORD2C element center and the material angle is measured from the G1-G2 line
CORD1S, to the to the projected r-axis
CORD2S
MCID is ignored for hyperelastic elements. (Integer > 0; if blank, then THETA = 0.0 is
assumed)
Main Index
1520 CTRIA6
Curved Triangular Shell Element Connection
x MCID
Coordinate
System
y z
G3
ymaterial
G1 G2
xmaterial
Figure 9-72 MCID Coordinate System Definition
ZOFFS Offset from the surface of grid points to the element reference plane; see Remark 6.
ZOFFS is ignored for hyperelastic elements. (Real)
Ti Membrane thickness of element at grid points G1 through G4. If “TFLAG” zero or
blank, then Ti are actual user specified thickness. (Real > 0.0 or blank, not all zero. See
Remark 4. for default.) If “TFLAG” one, then the Ti are fraction relative to the T value
of the PSHELL. (Real > 0.0 or blank, not all zero. Default = 1.0) Ti are ignored for
hyperelastic elements.
TFLAG An integer flag, signifying the meaning of the Ti values. (Integer 0, 1, or blank)
Remarks:
1. Element identification numbers should be unique with respect to all other element IDs.
2. Grid points G1 through G6 must be numbered as shown in Figure 9-73.
3. The orientation of the material property coordinate system is defined locally at each interior
integration point by THETA, which is the angle between xmaterial and the line of constant .
4. T1, T2, and T3 are optional. If they are not supplied and no TFLAG, then T1 through T3 will be
set equal to the value of T on the PSHELL entry.
5. It is recommended that the midside grid points be located within the middle third of the edge.
Main Index
CTRIA6 1521
Curved Triangular Shell Element Connection
6. Elements may be offset from the connection points by means of the ZOFFS field. Other data, such
as material matrices and stress fiber locations, are given relative to the reference plane. A positive value
of ZOFFS implies that the element reference plane is offset a distance of ZOFFS along the positive
z-axis of the element coordinate system. If the ZOFFS field is used, then both the MID1 and MID2
fields must be specified on the PSHELL entry referenced by PID.
Two methods are available for the computation of offsets: original and enhanced. The default method
is the original method. The enhanced method is requested by the Bulk Data entry
MDLPRM,OFFDEF,LROFF. For options of offsets, please refer to the Bulk Data entry
MDLPRM,OFFDEF,option.
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, it is highly recommended to use MDLPRM, OFFDEF, LROFF. In SOL103, if the
case control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then
MDLPRM, OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
7. If all midside grid points are deleted, then the element will be excessively stiff and the transverse shear
forces will be incorrect. A User Warning Message is printed. A CTRIA3 element entry is
recommended instead. If the element is hyperelastic, then the element is processed identically to the
hyperelastic CTRIA3 element.
8. For a description of the element coordinate system, see Shell Elements (CTRIA3, CTRIA6, CTRIAR, CQUAD4,
CQUAD8, CQUADR) in the MSC Nastran Reference Guide. Stresses and strains are output in the local
coordinate system identified by x l and y l in Figure 9-73. For hyperelastic elements, stresses and
strains are output in the coordinate system defined by the CID field on the PLPLANE entry.
Main Index
1522 CTRIA6
Curved Triangular Shell Element Connection
yl
Lines of Constant or
G3 xl
= 1, = 1
= constant
y material
yl
x material
= 0.5 G5
THETA
G6
xl
yl
yl
= constant
xl G4 = 0.5
THETA
= 0
G1
G2
xl
Figure 9-73 CTRIA6 Element Geometry and Coordinate Systems
9. For hyperelastic elements, the plot codes are specified under the CTRIAFD element name in Item
Codes.
Main Index
CTRIAR 1523
Triangular Plate Element Connection
CTRIAR Triangular Plate Element Connection
Defines an isoparametric membrane-bending triangular plate element. This element has a normal rotational
(drilling) degrees-of-freedom. It is a companion to the CQUADR element.
Format:
1 2 3 4 5 6 7 8 9 10
CTRIAR EID PID G1 G2 G3 THETA or ZOFFS
MCID
TFLAG T1 T2 T3
Example:
CTRIAR 111 203 31 74 75 3.0
1.77 2.04 2.09
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHELL, PCOMP or PCOMPG entry. (Integer > 0;
Default = EID)
G1, G2, G3 Grid point identification numbers of connection points. (Integers > 0; all unique)
THETA Material property orientation angle in degrees. (Real; Default = 0.0)
MCID Material coordinate system identification number. The x-axis of the material coordinate
system is determined by projecting the T1-axis of the MCID coordinate system onto the
surface of the shell element as follows:
CORD1R, x -axis of MCID the coordinate is projected onto shell surface and the
CORD2R material angle is measured from the G1-G2 line to the to the projected x-
axis
CORD1C, r-axis of MCID the coordinate is projected onto shell surface through the
CORD2C element center and the material angle is measured from the G1-G2 line to
CORD1S, the to the projected r-axis
CORD2S
Use DIAG 38 to print the computed THETA values. (Integer > 0; if blank, then
THETA = 0.0 is assumed)
ZOFFS Offset from the surface of grid points to the element reference plane. See Remark 5.
Main Index
1524 CTRIAR
Triangular Plate Element Connection
x MCID
Coordinate
System
y z
G3
ymaterial
G1 G2
xmaterial
Figure 9-74 MCID Coordinate System Definition
TFLAG An integer flag, signifying the meaning of the Ti values. (Integer 0, 1, or blank)
Ti Membrane thickness of element at grid points G1 through G4. If “TFLAG” zero or
blank, then Ti are actual user specified thickness. (Real > 0.0 or blank, not all zero. See
Remark 4. for default.) If “TFLAG” one, then the Ti are fraction relative to the T value
of the PSHELL. (Real > 0.0 or blank, not all zero. Default = 1.0) Ti are ignored for
hyperelastic elements.
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. The continuation is optional. If it is not supplied, then T1 through T3 will be set equal to the value
of T on the PSHELL entry.
3. Stresses are output in the element coordinate system at the centroid and grid points G1 through G3.
4. Inaccurate results will be obtained if interior grids have the rotation normal (drilling) to the element
constrained. At the boundary of a model, the drilling degrees-of-freedom must be constrained if the
user wants a fixed boundary. Also, for this element it is critical that consistent membrane (in plane)
edge loads be applied. Reference the PLOAD4 entry (SORL option) and the Consistent Surface and Edge
Loads in the MSC Nastran Reference Guide for additional information.
Main Index
CTRIAR 1525
Triangular Plate Element Connection
G3
yelement
xmaterial
THETA
xelement
G1 G2
Figure 9-75 CTRIAR Element Geometry and Coordinate Systems
5. Elements may be offset from the connection points by means of the ZOFFS field. Other data, such
as material matrices and stress fiber locations, are given relative to the reference plane. A positive value
of ZOFFS implies that the element reference plane is offset a distance of ZOFFS along the positive
Z-axis of the element coordinate system. If the ZOFFS field is used, then both the MID1 and MID2
fields must be specified on the PSHELL entry referenced by PID.
Two methods are available for the computation of offsets: original and enhanced. The default method
is the original method. The enhanced method is requested by the Bulk Data entry
MDLPRM,OFFDEF,LROFF. For options of offsets, please refer to the Bulk Data entry
MDLPRM,OFFDEF,option.
For solution sequences that require differential stiffness such as SOL103 (with preloading), SOL105,
and SOL400, it is highly recommended to use MDLPRM, OFFDEF, LROFF. In SOL103, if the
case control ADAMSMNF FLEXBODY=YES or AVLEXB EXBBODY=YES is present, then
MDLPRM, OFFDEF, LROFF must be replaced by MDLPRM, OFFDEF, NOMASS.
For SOLs 106, 129, 153, and 159 the differential stiffness for offset vectors will give incorrect results
with PARAM, LGDISP, 1. In addition in SOLs 106 and 129 offset vectors will produce incorrect
results with thermal loading.
6. The CTRIAR element is the triangular companion to the CQUADR element and should be used
instead of CTRlA3 or CTRlA6.
Figure 9-76
Main Index
1526 CTRIAX
Axisymmetric Triangular Element (Fully Nonlinear or Linear Harmonic)
CTRIAX Axisymmetric Triangular Element (Fully Nonlinear or Linear Harmonic)
Defines an axisymmetric triangular element with up to six grid points for use in fully nonlinear (i.e., large
strain and large rotations) hyperelastic analysis or a linear harmonic or rotordynamic analysis. The element
has between three and six grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CTRIAX EID PID G1 G2 G3 G4 G5 G6
THETA or
MCID
Example:
CTRIAX 111 203 31 74 75
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000) See Remark 1.
PID Property identification number of a PLPLANE or PAXSYMH entry. (Integer > 0). See
Remark 2.
G1, G2, G3 Identification numbers of connected corner grid points. Required data for all three grid
points. (Unique Integers > 0). See Remark 3., 6., 7.
G4, G5, G6 Identification numbers of connected edge grid points. Optional data for any or all four
grid points for Nastran conventional element only. (Integer > 0 or blank). See Remark
3., 4., 6., 7.
Note that for advanced nonlinear elements, partial specification of mid-points is not
allowed. i.e. either none of the mid-points should be specified or all of the mid points
should be specified
THETA Material property orientation angle in degrees. THETA is only applicable if the
PLPLANE entry has an associated PSHLN2 entry which is honored only in SOL 400.
For PSHLN2 BEHi=AXSOLID code, THETA is measured relative to the R axis of the
element. (Real; Default = 0.0)
MCID Material coordinate system identification number, MCID is only applicable if the
PLPLANE entry has an associated PSHLN2 entry which is honored only in SOL 400.
The x-axis of the material coordinate system is determined by projecting the x-axis of
the MCID coordinate system onto the surface of the element. The resulting angle is
measured relative to the R axis of the element. For PSHLN2 BEHi=AXSOLID code,
THETA is measured relative to the R axis of the element. (Integer > 0; if blank, then
THETA = 0.0 is assumed.) THETA is ignored if PID refers to a PAXSYMH entry.
Remarks:
1. Element identification numbers must be unique with respect to all other element IDs of any kind.
Main Index
CTRIAX 1527
Axisymmetric Triangular Element (Fully Nonlinear or Linear Harmonic)
2. If PID refers to a PLPLANE entry, CTRIAX defines an element for use in fully nonlinear analysis. If
PID refers to a PAXSYMH entry, CTRIAX defines a linear harmonic element for use in
rotordynamic or harmonic analysis.
3. Gi must be numbered as shown in Figure 9-77.
4. It is recommended that the edge points be located within the middle third of the edge.
5. The plot codes are specified under the CTRIAXFD element name in Item Codes.
6. The grid points of the axisymmetric element must lie on the x-y plane of the basic coordinate system.
Stress and strain are output in the basic coordinate system.
7. A concentrated load (e.g., FORCE entry) at Gi is divided by the radius to Gi and then applied as a
force per unit circumferential length. For example, in order to apply a load of 100 N/m on the
circumference at G1, which is located at a radius of 0.5 m, then the magnitude specified on the static
load entry must result in:
100 N/m 0.5m = 50N
z = ybasic
G3 Lines of Constant or
= 1, = 1
= constant
= 0.5 G5
G6
= constant
= 0.5
G4
= 0
G1
G2
r = xbasic
Figure 9-77 CTRIAX Element Coordinate System
Main Index
1528 CTRIAX6
Axisymmetric Triangular Element Connection
CTRIAX6 Axisymmetric Triangular Element Connection
Defines an isoparametric and axisymmetric triangular cross section ring element with midside grid points.
Format:
1 2 3 4 5 6 7 8 9 10
CTRIAX6 EID MID G1 G2 G3 G4 G5 G6
TH
Example:
CTRIAX6 22 999 10 11 12 21 22 32
9.0
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
MID Material identification number. (Integer > 0)
Gi Grid point identification numbers of connected points (unique Integers > 0, or blank
for deleted nodes.)
TH Material property orientation angle in degrees. (Real; Default = 0.0)
Remarks:
1. The grid points must lie in the x-z plane of the basic coordinate system, with x = r ≥ 0. The grid
points must be listed consecutively beginning at a vertex and proceeding around the perimeter in
either direction. Corner grid points G1, G3, and G5 must be present. Any or all edge grid points G2,
G4, or G6 may be deleted for Nastran conventional element. Note that the alternate corner-edge grid
point pattern is different from the convention used on the CTRIA6 element.
Note that for advanced nonlinear elements, partial specification of mid-points is not allowed. i.e.
either none of the mid-points should be specified or all of the mid points should be specified.
2. For structural problems, the MID may refer to a MAT1 or MAT3 entry.
3. The continuation is optional.
4. Material properties (if defined on a MAT3 entry) and stresses are given in the (rm, zm) coordinate
system shown in Figure 9-79.
5. A concentrated load (e.g., FORCE entry) at Gi is multiplied by 2 times the radius to Gi and then
applied as a force per unit circumferential length. (which is located at a radius of 0.5 m), the
magnitude of the load specified on the static load entry must result in:
(100 N/m) 2 (0.5m) = 314.159 N
Main Index
CTRIAX6 1529
Axisymmetric Triangular Element Connection
Figure 9-78 CTRIAX6 Element Idealization
z = zbasic
zm
rm
G5
axial G4
G3
G6
TH
G2
G1
radial r = xbasic
Figure 9-79 CTRIAX6 Element Geometry and Coordinate Systems
6. For thermal problems, the MID may refer to a MAT4 or MAT5 entry. In order to model the
convection or radiation along the edges the CHBDYG with TYPE=REV must be used.
7. To model axi-symmetric view factor computations using the CTRIAX6 elements, the normal
direction for the CTRIAX6 element must point in the negative Y direction. The reason for this is to
set up PATRAN for the correct nodal specification on the CHBDYG with REV option
Main Index
1530 CTRIAX6
Axisymmetric Triangular Element Connection
3
6
9
2
2
5
8
1
1
Z 4
Y 2
X
Figure 9-80 Normal Vectors That Point in a Negative Y Direction.
3 6 4 12 15 18
2
2 11 14 17
5 8
1
13 16
7 10
1 4
Z
Figure 9-81 View Factor Boundary Conditions.
$ CHBDYG Surface Elements
CHBDYG 100001 REV 1 1
7 9 8
CHBDYG 100002 REV 2 2
12 10 11
Please note that on the CHBDYG, REV option, the nodal connectivity specification is in the
clockwise fashion. In this case the CHBDYG with element ID of 100001 is defined by grids 7,9,8
which means the normal vector of the edge is pointing towards right. On the other hand the edges
define by grid 12,10,11 means the normal vector of the edge is pointing towards left. If you have not
reverse the element direction to a negative Y direction on the CTRIAX6 element, the view factor
computation will result a net view factor of zero.
Main Index
CTUBE 1531
Tube Element Connection
CTUBE Tube Element Connection
Defines a tension-compression-torsion tube element.
Format:
1 2 3 4 5 6 7 8 9 10
CTUBE EID PID G1 G2
Example:
CTUBE 12 13 21 23
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PTUBE entry. (Integer > 0; Default = EID)
G1, G2 Grid point identification numbers of connection points. (Integer > 0; G1 G2 )
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Only one tube element may be defined on a single entry.
Main Index
1532 CVISC
Viscous Damper Connection
CVISC Viscous Damper Connection
Defines a viscous damper element.
Format:
1 2 3 4 5 6 7 8 9 10
CVISC EID PID G1 G2
Example:
CVISC 21 6327 29 31
Describer Meaning
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PVISC entry. (Integer > 0; Default = EID)
G1, G2 Grid point identification numbers of connection points. (Integer > 0; G1 G2 )
Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Only one viscous damper element may be defined on a single entry.
3. Grids G1 and G2 must not be coincident. If coincident grids are required, use either the CDAMP or
CBUSH entry.
Main Index
CWELD 1533
Weld or Fastener Element Connection
CWELD Weld or Fastener Element Connection
Defines a weld or fastener connecting two surface patches or points. Large displacement and large rotational
effects are supported when using SOL 400 only.
Format PARTPAT:
1 2 3 4 5 6 7 8 9 10
CWELD EWID PWID GS “PARTPAT” GA GB MCID
PIDA PIDB
XS YS ZS
Example:
CWELD 101 8 203 PARTPAT
21 33
Alternate formats and examples:
Format ELPAT:
CWELD EWID PWID GS “ELPAT” GA GB MCID
SHIDA SHIDB
XS YS ZS
Example:
CWELD 103 5 403 ELPAT
309 511
Format ELEMID:
CWELD EWID PWID GS “ELEMID” GA GB MCID
SHIDA SHIDB
Example:
CWELD 103 5 403 ELEMID
309 511
Main Index
1534 CWELD
Weld or Fastener Element Connection
Format GRIDID:
CWELD EWID PWID GS “GRIDID” GA GB SPTYP MCID
GA1 GA2 GA3 GA4 GA5 GA6 GA7 GA8
GB1 GB2 GB3 GB4 GB5 GB6 GB7 GB8
Example:
CWELD 7 29 233 GRIDID QT
15 28 31 35 46 51 55 60
3 5 8
Format ALIGN:
CWELD EWID PWID “ALIGN” GA GB MCID
Example:
CWELD 7 29 ALIGN 103 259
Describer Meaning Type Default
EWID CWELD element identification number. See Remark 1. 0 < Integer < Required
100,000,000
PWID Property identification number of a PWELD entry. Integer > 0 Required
GS Identification number of a grid point which defines the Integer > 0 or
location of the connector. See Remarks 2. and 3. blank
“PARTPAT” Character string indicating the type of connection. The Character Required
format of the subsequent entries depends on the type.
“PARTPAT”, for example, indicates that the
connectivity of surface patch A to surface patch B is
defined with two property identification numbers of
PSHELL entries, PIDA and PIDB, respectively. The
“PARTPAT” format connects, depending on the
diameter, many elements per patch. See Remark 4.
GA, GB Grid point identification numbers of piercing points on Integer > 0 or blank
surface A and surface B, respectively. See Remark 5. blank
MCID Specifies the element stiffness coordinate system. See Integer > -1 or Default = -1
Remark 16. blank
PIDA, PIDB Property identification numbers of PSHELL entries Integer > 0 Required for
defining surface A and B respectively. “PARTPAT”
XS, YS, ZS Coordinates of spot weld location in basic. See Remark Real Required if
2. GS and GA
are not
defined.
Main Index
CWELD 1535
Weld or Fastener Element Connection
For the alternate formats, the describer meaning are described below:
Describer Meaning Type Default
“ELPAT” Character string indicating that the connectivity of Character Required
surface patch A to surface patch B is defined with two
shell element identification numbers, SHIDA and
SHIDB, respectively. The “ELPAT” format connects,
depending on the diameter, many elements per patch.
See Remark 6.
SHIDA, Shell element identification numbers of elements on Integer > 0 Required for
SHIDB patch A and B, respectively. “ELPAT”
“ELEMID” Character string indicating that the connectivity of Character Required
surface patch A to surface patch B is defined with two
shell element identification numbers, SHIDA and
SHIDB, respectively. The “ELEMID” format connects
one shell element per patch. See Remark 7.
SHIDA, Shell element identification numbers of elements on Integer > 0 Required for
SHIDB patch A and B, respectively. “ELEMID”
“GRIDID” Character string indicating that the connectivity of Character Required
surface patch A to surface patch B is defined with two
sequences of grid point identification numbers, GAi and
GBi, respectively. The “GRIDID” format connects the
surface of any element. See Remark 8.
SPTYP Character string indicating types of surface patches A Character Required for
and B. SPTYP = “QQ”, “TT”, “QT”, “TQ”, “Q” or “GRIDID”
“T”. See Remark 9.
GAi Grid identification numbers of surface patch A. GA1 to Integer > 0 Required for
GA3 are required. See Remark 10. “GRIDID”
GBi Grid identification numbers of surface patch B. See Integer > 0
Remark 10.
“ALIGN” Character string indicating that the connectivity of Character Required
surface A to surface B is defined with two shell vertex
grid points GA and GB, respectively. See Remark 11.
GA, GB Vertex grid identification number of shell A and B, Integer > 0 Required for
respectively. “ALIGN”
Remarks:
1. CWELD defines a flexible connection between two surface patches, between a point and a surface
patch, or between two shell vertex grid points. See Figure 9-82 through Figure 9-86.
Main Index
1536 CWELD
Weld or Fastener Element Connection
2. Grid point GS defines the approximate location of the connector in space. GS is projected on surface
patch A and on surface patch B. The resulting piercing points GA and GB define the axis of the
connector. GS must have a normal projection on surface patch A and B. GS does not have to lie on
the surface patches. GS is ignored for format “ALIGN”. GA is used instead of GS if GS is not
specified. For the formats “ELPAT” and “PARTPAT,” if GS and GA are not specified, then XS, YS,
and ZS will be assumed.
3. The connectivity between grid points on surface patch A and grid points on surface patch B is
generated depending on the location of GS and the cross sectional area of the connector. Diagnostic
print outs, checkout runs and non default settings of search and projection parameters are requested
on the SWLDPRM Bulk Data entry. It is recommended to start with the default settings.
4. The format “PARTPAT” defines a connection of two shell element patches A and B with PSHELL
property identification numbers PIDA and PIDB, respectively. The two property identification
numbers must be different, see Figure 9-82. The number of connected elements depends on the
location of the piercing points GA, GB and the size of the diameter D. The diameter D is defined on
the PWELD property entry. For this option, shell element patches A and B are allowed to share a
common grid.
GS
PIDB
GB
PIDA
L
SHIDB GA
D SHIDA
Figure 9-82 Patch to Patch Connection Defined with the Formats PARTPAT or
ELPAT
5. The definition of the piercing grid points GA and GB is optional for all formats with the exception
of the format “ALIGN”. If GA and GB are given, GS is ignored. If GA and GB are not specified, they
are generated from the normal projection of GS on surface patches A and B and internal identification
numbers are generated for GA and GB starting with 101e+6 by default. The offset number can be
changed with PARAM,OSWPPT. If GA and GB are specified, they must lie on or at least have a
projection on surface patches A and B, respectively. By default, the locations of user specified GA and
Main Index
CWELD 1537
Weld or Fastener Element Connection
GB will not be changed. If the user specifies "SWLDPRM, MOVGAB, 1," then the locations will be
corrected so that they lie on surface patches A and B within machine precision accuracy. The length
of the connector is the distance of grid point GA to GB, subject to being adjusted to the effective
length defined in PWELD entry.
6. The format “ELPAT” defines a connection of two shell element patches A and B with shell element
identification numbers SHIDA and SHIDB, see Figure 9-82. The connectivity is similar to the format
“PARTPAT”. The number of connected elements depends on the location of the piercing points GA,
GB and the size of the diameter D. For this option, shell element patches A and B are allowed to share
a common grid.
7. The format “ELEMID” defines a connection of two shell element patches A and B with shell element
identification numbers SHIDA and SHIDB, see Figure 9-83. The connectivity is restricted to a single
element per patch regardless of the location of GA, GB and regardless of the size of the diameter of
the connector. In addition, the format “ELEMID” can define a point to patch connection if SHIDB
is left blank, see Figure 9-84. Then grid GS is connected to shell SHIDA.
GS
GB4 SHIDB
GA3
GB3
GB
GB1
GA2
GB2
GA
SHIDA
GA1
Figure 9-83 Patch to Patch Connection Defined with Format ELEMID or GRIDID
Main Index
1538 CWELD
Weld or Fastener Element Connection
GS
GA4
GA3
GA
GA1
GA2
Figure 9-84 Point to Patch Connection Defined with Format ELEMID or GRID.
8. The format “GRIDID” defines a connection of two surface patches A and B with a sequence of grid
points GAi and GBi, see Figure 9-83. In addition, the format “GRIDID” can define a point to patch
connection if all GBi fields are left blank, see Figure 9-84. Then grid GS is connected to grids GAi. The
grids GAi and GBi do not have to belong to shell elements.
9. SPTYP defines the type of surface patches to be connected. SPTYP is required for the format
“GRIDID” to identify quadrilateral or triangular patches. The combinations are:
SPTYP Description
QQ Connects a quadrilateral surface patch A (Q4 to Q8) with a quadrilateral surface
patch B (Q4 to Q8).
QT Connects a quadrilateral surface patch A (Q4 to Q8) with a triangular surface patch
B (T3 to T6).
TT Connects a triangular surface patch A (T3 to T6) with a triangular surface patch B
(T3 to T6).
TQ Connects a triangular surface patch A (T3 to T6) with a quadrilateral surface patch
B (Q4 to Q8).
Q Connects the shell vertex grid GS with a quadrilateral surface patch A (Q4 to Q8)
if surface patch B is not specified.
T Connects the shell vertex grid GS with a triangular surface patch A (T3 to T6) if
surface patch B is not specified.
10. GAi are required for the format “GRIDID”. At least 3 and at most 8 grid IDs may be specified for
GAi and GBi, respectively. The rules of the triangular and quadrilateral elements apply for the order
of GAi and GBi, see Figure 9-85. Missing midside nodes are allowed.
Main Index
CWELD 1539
Weld or Fastener Element Connection
GA4 GA7 GA3
GA3
GA6
GA6 GA5
GA8
GA1 GA2 GA1 GA4 GA2
GA5
Figure 9-85 Quadrilateral and Triangular Surface Patches defined with
Format GRIDID
11. The format “ALIGN” defines a point to point connection, see Figure 9-86. GA and GB are required,
they must be existing vertex nodes of shell elements. For the other formats, GA and GB are not
required. Two shell normals in the direction GA-GB are generated at GA and GB, respectively.
GB
GA
Figure 9-86 Point to Point Connection Defined with Format ALIGN
12. Forces and moments are output in the element coordinate system, see Figure 9-87. The element
coordinate system is constructed using the following rules:
The element x-axis points from GA to GB.
xB – xA
e 1 = ---------------------- element x-axis
xB – xA
In case of zero length, the normal of shell A is taken. All vector components are in basic if not noted
otherwise.
Find the smallest component j of e 1
Main Index
1540 CWELD
Weld or Fastener Element Connection
i i
ce 1 = e 1
j min i
ce 1 = ce .
i = 1 2 3 1
i –6 i –6
Note that ce 1 will be set to 10 if ce 1 10 .
In case of two equal components we take the one with the smaller i . The corresponding basic vector
0
b j , e.g., for j = 3, b 3 = 0
1
provides a good directional choice for e 2 . In addition, the vector e 2 must be orthogonal to e 1 .
e˜2
T
e1 bj
e˜2 = b j – ----------- e 1 e 2 = ---------- element y-axis
T
e1 e1 e˜2
and e 3 is just the cross product
e3 = e1 e2 element z-axis
The final transformation matrix is
T be = e 1 e 2 e 3
Figure 9-87 Element Coordinate System and Sign Convention of
Element Forces
13. If "PARAM, OLDWELD, YES", in a SOL 400 analysis the CWELD element using method
ELEMID, GRIDID, ELPAT or PARTPAT internally gets decomposed in a CBEAM element and a
number of RBE3 elements. For method ALIGN the CWELD element internally gets replaced by a
CBEAM element. The CBEAM element obtains a circular cross section with its diameter and
material properties taken from the PWELD input and its length is determined by the final locations
Main Index
CWELD 1541
Weld or Fastener Element Connection
mx
fx
m zB
xe
fz
GB
fy
m yA m yB
Plane 2
fy
GA
ze
Plane 1 fx Axial force
fy Shear force, plane 1
fz
ye fz Shear force, plane 2
m zA
mx Torque
fx
m yA Bending moment end A, plane 2
m yB Bending moment end B, plane 2
zb
yb m zA Bending moment end A, plane 1
mx m zB Bending moment end B, plane 1
xb
Basic
of the GA and GB grids of the CWELD. The RBE3 elements connect the GA and GB grids to the
plate structures. For methods ELEMID and GRIDID one RBE3 element is used on each side to
establish the connection. For methods ELPAT and PARTPAT five RBE3 elements are used on each
side to establish the connection.
14. The output format of the forces and moments including the sign convention is identical to the CBAR
element, see Element Force Item Codes.
Main Index
1542 CWELD
Weld or Fastener Element Connection
15. This entry is not supported in SOL 700.
16. MCID = -1 or blank (Default), then the coordinate system is as defined in Remark 12.
If MCID > 0, then a “beam” like coordinate system is defined. The x elem axis direction of the
connector defined as
xB – xA
e 1 = ----------------------
xB – xA
The T2 direction defined by MCID will be used to define the orientation vector of the connector.
Then the z elem element axis will be defined as
e1
e 3 = -------------------
e1
The element y elem axis is defined as
e2 = e3 e1
17. If used in a multi-physics coupled problem using SUBSTEP, they participate in the mechanical
substep but are ignored in the heat transfer subsstep through automatic deactivation. For more
information on deactivation, see the DEACTEL keyword under the NLMOPTS Bulk Data entry and
the associated Remark 10. for that entry.
18. In SOL400, the behavior of this element in regard to large rotation is affected by the Case Control
Command Rigid.
19. If partitioned superelements are present, then CWELD is supported in the main Bulk Data section
only.
Main Index
CYAX 1543
Grid Points on Axis of Symmetry
CYAX Grid Points on Axis of Symmetry
Lists grid points that lie on the axis of symmetry in cyclic symmetry analysis.
Format:
1 2 3 4 5 6 7 8 9 10
CYAX G1 G2 G3 G4 G5 G6 G7 G8
G9 G10 -etc.-
Example:
CYAX 27 152 THRU 160 192 11
Describer Meaning
Gi A list of grid points on the axis of symmetry. (Integer > 0 or Character “THRU”)
Remarks:
1. The displacement coordinate system (see CD field on GRID entry) for a grid point lying on the axis
of symmetry must be a rectangular system with the z-component of motion aligned with the axis of
symmetry. The positive axis of symmetry is defined so that the azimuthal angle from positive side 1
to side 2 of a segment is in the same direction as the angle from T1 to T2 for the axis point. This is
consistent with left- or right-hand rule.
2. If the dihedral symmetry option (STYPE = “DIH” on the CYSYM entry) is selected, the y-axis must
be perpendicular to side 1.
3. Grid points lying on the axis of symmetry may be constrained by SPCs but not by MPCs. If the
number of segments is three or more, SPCs must be applied to both components 1 and 2 or to neither,
and SPCs must be applied to both components 4 and 5 or to neither in order to satisfy symmetry. In
addition, the degrees-of-freedom (not constrained by SPCs, if any) at these grid points must be in the
analysis set (a-set). If all degrees-of-freedom of grid points on the axis of symmetry are constrained
by SPCs (including heat transfer, where there is only one degree-of-freedom), the grid point should
not be listed on the CYAX entry.
4. Grid points lying on the axis of symmetry must not be defined on side 1 or on side 2 by means of a
CYJOIN entry.
5. The word “THRU” must not appear in fields 2 or 9.
Main Index
1544 CYJOIN
Cyclic Symmetry Boundary Points
CYJOIN Cyclic Symmetry Boundary Points
Defines the boundary points of a segment in cyclic symmetry problems.
Format:
1 2 3 4 5 6 7 8 9 10
CYJOIN SIDE C G1 G2 G3 G4 G5 G6
G7 G8 G9 -etc.-
Example:
CYJOIN 1 T2 7 9 16 THRU 33 64
72 THRU 89
Describer Meaning
SIDE Side identification. (Integer 1 or 2)
C Type of coordinate system used on boundaries of dihedral or axisymmetry problems.
See Remark 3. (Character: “T1”, “T2”, “T3”, “R”, “C”, “S”)
Gi Grid or scalar point identification numbers. (Integer > 0 or Character “THRU”)
Remarks:
1. CYJOIN entries are used only for cyclic symmetry problems. The CYSYM entry must be used to
specify rotational, dihedral, or axisymmetry.
2. For rotational or axisymmetry problems, there must be one logical entry for SIDE = 1 and one for
SIDE = 2. The two lists specify grid points to be connected; therefore, both lists must have the same
length.
3. For dihedral problems, side 1 refers to the boundary between segments and side 2 refers to the middle
of a segment. For dihedral and/or AXI type of symmetry, the grid point degree-of-freedom that is
normal to the boundary must be specified in field 3 as “T1”, “T2”, or “T3” (“R”, rectangular, and
“C”, cylindrical, are the same as “T2” while “S”, spherical, is the same as “T3”). For scalar and extra
points with one degree-of-freedom, these should be specified as blank, “T2”, or “T3” if they are to
have the same sign, and “T1”, if the two connected points are to be opposite in sign.
4. All components of displacement at boundary points are connected to adjacent segments except those
constrained by SPCi, MPC, or OMITi entries.
5. The points on the axis of symmetry of the model, defined in the CYAX entry must not be defined as
a side 1 or side 2 point by means of this entry.
6. The word “THRU” may not appear in fields 4 or 9 of the parent entry and fields 2 or 9 on the
continuation entries.
7. All grid points that are implicitly or explicitly referenced must be defined.
Main Index
CYJOIN 1545
Cyclic Symmetry Boundary Points
8. For rotational and axisymmetry problems, the displacement coordinate systems must be consistent
between sides 1 and 2. This is best satisfied by the use of a spherical or cylindrical coordinate system.
Main Index
1546 CYLINDR
Defines the Shape of a Cylinder
CYLINDR Defines the Shape of a Cylinder
Cylindrical shape used in the initial condition definition on the TICEUL1 entry. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
CYLINDR VID XC1 YC1 ZC1 XC2 YC2 ZC2
RAD
Example:
CYLINDR 4 0. 0. 0. 1. 1. 1.
.5
Describer Meaning
VID Unique cylinder number. (Integer > 0; Required)
XC1, YC1, ZC1 Coordinates of point 1, See Remark 1. (Real; Required)
XC2, YC2, ZC2 Coordinates of point 2. See Remark 1. (Real; Required)
RAD Radius of the cylinder. (Real; Required)
Remarks:
1. A cylinder is defined by the two end points of the cylinder axis and a radius.
2. Initial conditions are defined for the elements that are fully or partially inside the cylinder.
3. See also the TICEUL1 Bulk Data entry.
Main Index
CYSUP 1547
Fictitious Supports for Cyclic Symmetry
CYSUP Fictitious Supports for Cyclic Symmetry
Defines fictitious supports for cyclic symmetry analysis.
Format:
1 2 3 4 5 6 7 8 9 10
CYSUP GID C
Example:
CYSUP 16 1245
Describer Meaning
GID Grid point identification number. (Integer > 0)
C Component numbers. (Any unique combination of the Integers 1 through 6 with no
embedded blanks.)
Remarks:
1. Components of motion defined on this entry may not appear on SPC, SPC1, OMIT, OMIT1
entries, or in rigid elements or multipoint constraints as dependent degrees-of-freedom.
2. Supports are applied at the grid point identified in field 2 to prevent rigid body motions in static
analysis, or to define rigid body modes in eigenvalue analysis. All degrees-of-freedom should be at a
single grid point. In other words, there can only be one such supported grid point in the model. The
supports are applied only to the cyclic components of order k=0 or k=1. In order to satisfy conditions
of symmetry, certain restrictions are placed on the location of the grid point and the orientation of its
displacement coordinate system, as shown in the following table:
Symmetry Option (STYPE ROT ROT DIH DIH DIH
on the CYSYM entry)
Number of Segments, N 2 >3 1 2 >3
Location of Grid Point See Note c. See Note d. Side 1 Side 1 Side 1
Special Restrictions on See Notes See Note b. None See Note a. See Note b.
Displacement Coordinate a. and e.
System
Notes:
a. T3 axis must be parallel to axis of symmetry.
b. Displacement coordinate system at the referenced grid point must be cylindrical with z-axis along
the axis of symmetry.
Main Index
1548 CYSUP
Fictitious Supports for Cyclic Symmetry
c. Any location except on side 2.
d. Any location except on the axis of symmetry or on side 2.
e. If the grid point is on the axis of symmetry, the displacement coordinate system must be
rectangular.
3. If the number of segments, N, is 1 (in the case of DIH symmetry) or 2 (in the case of ROT or AXI
symmetry), it is important that the rotational components referenced in field 3 be elastically
connected to the structure. If N > 2 (in the case of DIH symmetry) or N > 3 (in the case of ROT or
AXI symmetry), it is not important, because in this case the supports for rigid body rotation are
actually applied to translational motions.
4. If N > 3, supports will be applied to both the 1 and 2 (inplane-translational) components, if either is
referenced, and to both the 4 and 5 (out-of-plane rotational) components, if either is referenced. If
component 6 is supported, component 2 should not appear on OMIT or OMIT1 entries.
5. The restrictions noted in Remarks 2. and 4. are related to symmetry requirements. For N > 3,
symmetry requires that the supports be symmetrical (or antisymmetrical), with respect to any plane
passing through the axis of symmetry. For the DIH options, N = 1 and N = 2, symmetry requires
that the supports be symmetrical (or antisymmetrical) with respect to the plane(s) of symmetry. For
the ROT option, N = 2, symmetry requires that a support be either parallel or perpendicular to the
axis of symmetry.
6. GID must be a grid point and not a scalar point.
Main Index
CYSYM 1549
Cyclic Symmetry Parameters
CYSYM Cyclic Symmetry Parameters
Defines parameters for cyclic symmetry analysis.
Format:
1 2 3 4 5 6 7 8 9 10
CYSYM NSEG STYPE
Example:
CYSYM 6 ROT
Describer Meaning
NSEG Number of segments. (Integer > 0)
STYPE Symmetry type. (Character: “ROT”, “DIH”, or “AXI”)
Remarks:
1. STYPE = “AXI” is a special case of STYPE = “ROT” used to model axisymmetric structures.
2. If STYPE = “AXI”, then all grid points must lie on side 1, side 2, or the axis. Also, plate elements
with midside grid points may not be defined.
Main Index
DAMPING 1551
Parameter and Hybrid Damping Specification
Entries D - E
DAMPING Parameter and Hybrid Damping Specification
Specifies the values for parameter damping and/or selects optional HYBRID damping.
Format:
1 2 3 4 5 6 7 8 9 10
DAMPING ID G ALPHA1 ALPHA2 HYBRID GEFACT ROTSEP
W3 W4 WH
Example:
DAMPING 100 .02 NO
Describer Meaning
ID Damping entry identification number. (Integer > 0; Required)
G Structural damping coefficient, see Remark 1. (Real; Default = 0.0)
ALPHA1 Scale factor for mass portion of Rayleigh damping, see Remark 4. (Real; Default = 0.0)
ALPHA2 Scale factor for stiffness portion of Rayleigh damping, see Remark 4. (Real; Default =
0.0)
HYBRID Identification number of HYBDAMP entry for hybrid damping, see Remarks 5. and 6.
(Integer > 0; Default = 0)
GEFACT Scale factor for material damping. See Remark 1.and Remark 3. (Real; Default = 1.0)
ROTSEP Remove rotor stiffness, mass, and structural damping from the hybrid damping
calculation (Character: YES or NO; Default=YES)
W3 Average frequency for calculation of structural damping in transient response, see
Remark 7. (Real > 0.0; Default = 0.0)
W4 Average frequency for calculation of material damping in transient response, see
Remark 7. (Real > 0.0; Default = 0.0)
WH Average frequency for calculation of hybrid ‘structural’ damping in transient response,
see Remark 7. (Real > 0.0; Default = 0.0)
Remarks:
1. The DAMPING entry is referenced by the RSDAMP or SEDAMP Case Control commands. If a
DAMPING entry is selected in the Case Control, the DAMPING values, including defaults, will
override parameter inputs.
2. All damping selections are cumulative.
3. Structural damping specified by the G and GEFACT entries will replace any structural damping by:
Main Index
1552 DAMPING
Parameter and Hybrid Damping Specification
K4 NEW = G K + GFACT K4
The GFACT value used is GFACT = GE (default=0.0) * GEFACT (default=1.0) where GE is the
structural damping value on the material entry.
4. Rayleigh viscous damping is calculated as:
B Rayleigh = 1 M + 2 K
5. Hybrid damping on the residual structure is only active for direct solution sequences. For modal
solution sequences, the SDAMP Case Control request should be used.
6. Hybrid damping for superelements uses modes that are calculated using the superelement mass and
stiffness matrices before upstream superelements are added and before SPC or MPC constriants are
imposed. These matrices are known as the JJ-type matrices.
7. The W3, WR4 and WH values are used in transient response only. A zero value (default) will result
in no damping. The equivalent viscous damping is calculated as:
G GFACT 1
B equiv = -------- K + -------------------- K4 + --------- KH
W3 W4 WH
8. For rotordynamic analyses (RGYRO in the Case Control Section), the DAMPING calculations for
the residual structure (RSDAMP) are performed without any rotor contributions (support structure
only).
9. Rayleigh damping is designed to be applied only at Superelement, Part Superelement, or External
Superelement residual assembly time. It is not applied in individual Parts or External superelements.
10. If Modules are present then this entry may only be specified in the main Bulk Data section.
11. The units of W3, W4, and WH are radians per unit time.
Examples:
1. Specify a structural damping coefficient of 0.03 for the residual structure for frequency response.
Case Control:
RSDAMP=100
Bulk Data:
DAMPING, 100, 0.03
2. Specify a structural damping coefficient of 0.03 for the residual structure for transient response (use
a “natural” frequency of 100 Hz)
Case Control:
RSDAMP=100
Bulk Data:
DAMPING, 100, 0.03,
, 628.3
Main Index
DAMPING 1553
Parameter and Hybrid Damping Specification
3. Specify hybrid damping for superelement 1. Use modal damping of two percent critical for the first
6 modes.
Case Control:
SUBCASE 1
SUPER=1
SEDAMP=100
Bulk Data:
DAMPING, 100, , , , 101
HYBDAMP, 101, 102, 1001
EIGRL, 102, , , 6
TABDMP1, 1001, CRIT,
, 0.0, 0.02, 1000.0, 0.02, ENDT
Main Index
1554 DAREA
Load Scale Factor
DAREA Load Scale Factor
Defines scale (area) factors for static and dynamic loads. In dynamic analysis, DAREA is used in conjunction
with ACSRCE, RLOADi and TLOADi entries.
Format:
1 2 3 4 5 6 7 8 9 10
DAREA SID P1 C1 A1 P2 C2 A2
Example:
DAREA 3 6 2 8.2 15 1 10.1
Describer Meaning
SID Identification number. (Integer > 0)
Pi Grid, extra, or scalar point identification number. (Integer > 0)
Ci Component number. (Integer 1 through 6 for grid point; blank or 0 for extra or scalar
point.)
Ai Scale (area) factor. (Real)
Remarks:
1. One or two scale factors may be defined on a single entry.
2. Refer to RLOAD1, RLOAD2, TLOAD1, TLOAD2, or ACSRCE entries for the formulas that
define the scale factor Ai in dynamic analysis.
3. Component numbers refer to the displacement coordinate system.
4. In dynamic analysis, DAREA entries may be used with LSEQ Bulk Data entries if LOADSET is
specified in Case Control. The LSEQ and static load entries will be used to internally generate
DAREA entries.
5. If DAREA is referenced by a GUST entry, Pi must be defined. However, it is only used if selected
through a DLOAD Case Control command. WG from the GUST entry is used instead of Ai when
requested via a GUST entry.
6. All DAREA entries corresponding to all grid and scalar points are automatically converted internally
by the program to equivalent FORCE/MOMENT/SLOAD entries (as appropriate) if there are no
LSEQ Bulk Data entries.
7. In superelement analysis, DAREA may be used to specify loads not only on the interior points of the
residual, but also on the interior points of upstream superelements if there are no LSEQ Bulk Data
entries.
8. In static analysis, DAREA entries may be used only if there are no LSEQ Bulk Data entries. They are
ignored if there are any LSEQ Bulk Data entries.
Main Index
DCONADD 1555
Design Constraint Set Combination
DCONADD Design Constraint Set Combination
Defines the design constraints for a subcase as a union of DCONSTR entries.
Format:
1 2 3 4 5 6 7 8 9 10
DCONADD DCID DC1 DC2 DC3 DC4 DC5 DC6 DC7
DC8 -etc.-
Example:
DCONADD 10 4 12
Describer Meaning
DCID Design constraint set identification number. (Integer > 0)
DCi DCONSTR entry identification number. (Integer > 0)
Remarks:
1. The DCONADD entry is selected by a DESSUB or DESGLB Case Control command.
2. All DCi must be unique from other DCi.
3. For PART SE, DCi from different PART SEs can be referenced on a single DCONADD and only
DCONADD in the main Bulk Data Section, starts with ‘BEGIN BULK’ or ‘BEGIN SUPER=0’, will
be considered as part of design constraints. Note that DCONADD entries in ‘BEGIN SUPER=seid’
where seid>0 will be ignored.
Main Index
1556 DCONSTR
Design Constraints
DCONSTR Design Constraints
Defines design constraints.
Format:
1 2 3 4 5 6 7 8 9 10
DCONSTR DCID RID LALLOW/LI UALLOW/UID LOWFQ HIGHFQ
D
Example:
DCONSTR 10 4 1.25
Describer Meaning
DCID Design constraint set identification number. (Integer > 0)
RID DRESPi entry identification number. (Integer > 0)
LALLOW/LID Lower bound on the response quantity or the set identification ID of a number of
a TABLEDi entry that supplies the lower bound as a function of frequency. (Real;
Default = -1.0E20)
UALLOW/UID Upper bound on the response quantity or the set identification ID of a number of
a TABLEDi entry that supplies the upper bound as a function of frequency. (Real;
Default = 1.0E20)
LOWFQ Low end of frequency range in Hertz (Real > 0.0; Default = 0.0). See Remark 8.
HIGHFQ High end of frequency range in Hertz (Real > LOWFQ; Default = 1.0E+20). See
Remark 8.
Remarks:
1. The DCONSTR entry may be selected in the Case Control Section by the DESSUB or DESGLB
command.
2. DCID may be referenced by the DCONADD Bulk Data entry.
3. For a given DCID, the associated RID can be referenced only once.
4. The units of LALLOW and UALLOW must be consistent with the referenced response defined on
the DRESPi entry. If RID refers to an “EIGN” response, then the imposed bounds must be expressed
in units of eigenvalue, (radian/time)2. If RID refers to a “FREQ” response, then the imposed bounds
must be expressed in cycles/time.
5. LALLOW and UALLOW are unrelated to the stress limits specified on the MATi entry.
6. Constraints are computed as follows:
LALLOW – r
g = --------------------------------- for lower bound constraints
GNORM
Main Index
DCONSTR 1557
Design Constraints
r – UALLOW
g = ---------------------------------- for upper bound constraints
GNORM
LALLOW for lower bounds if LALLOW GSCAL
GNORM = UALLOW for upper bounds if UALLOW GSCAL
GSCAL otherwise
GSCAL is specified on the DOPTPRM entry (Default = 0.001)
7. As Remark 6. indicates, small values of UALLOW and LALLOW require special processing and
should be avoided. Bounds of exactly zero are particularly troublesome. This can be avoided by using
a DRESP2 entry that offsets the constrained response from zero.
8. LOWFQ and HIGHFQ fields are functional only for frequency response RTYPE’s, including
DYSTIFF or those with a 'AC', 'AF', 'FR' or 'PS' prefix. (FREQ is not a frequency response). The
LOWFQ and HIGHFQ fields are also functional when they are applied to a DRESP2 or DRESP3
that inherit the frequency values from these RTYPES. The bounds provided in LALLOW and
UALLOW are applicable to a response only when the value of the forcing frequency of the response
falls between LOWFQ and HIGHFQ. The behavior varies depending on the value of ATTB on the
DRESP1 entry.
a. If the field is blank, the LOWFQ/HIGHFQ fields are honored. If the DCONSTR with
LOWFQ/HIGHFQ refers to a DRESP2 that invokes a DRESP1 with ATTB blank, the fields are
not honored.
b. If the field is a character, the LOWFQ/HIGHFQ fields are honored.
c. If the field is a real number, the LOWFQ/HIGHFQ fields are honored even when the
DCONSTR refers to a DRESP2 that references the DRESP1.
9. LID and UID are optional inputs that identify tabular input to specify the lower and upper bounds
as a function of frequency. They are applicable to the 'FR' and 'PSD' responses of Remark 8. and to
DRESP2 and DRESP3 responses that inherit the frequency value from these RTYPES.
10. For PART SE, DCONSTR entries can reside in each individual PART SE Bulk Data Section starting
with ‘BEGIN SUPER=seid’. If DCID is different from a PART SE to the next, DCONADD in the
residual (or main Bulk Data Section) can be utilized to group DCONSTR entries together for a single
subcase.
Main Index
1558 DDVAL
Discrete Design Variable Values
DDVAL Discrete Design Variable Values
Defines real, discrete design variable values for use in discrete variable optimization, topometry optimization
or rotordynamics.
Format:
1 2 3 4 5 6 7 8 9 10
DDVAL ID DVAL1 DVAL2 DVAL3 DVAL4 DVAL5 DVAL6 DVAL7
Alternate Format:
DDVAL ID DVAL1 THRU DVAL2 BY INC
The Continuation Entry formats may be used more than once and in any order. They may also be used with
either format above.
Continuation Entry Format 1:
DVAL8 DVAL9 DVAL10 DVAL11 -etc.-
Continuation Entry Format 2:
:
DVAL8 THRU DVAL9 BY INC
Example:
1 2 3 4 5 6 7 8 9 10
DDVAL 110 0.1 0.2 0.3 0.5 0.6 0.4
.7 THRU 1.0 BY 0.05
1.5 2.0
Describer Meaning
ID Unique set identification number (Integer > 0) See Remark 1.
DVALi Discrete values (Real, or THRU or BY) See Remarks 2. through 5.
INC Discrete value increment (Real) See Remarks 2., 4., 5.
Remarks:
1. DDAVAL entries may be referenced by a DESVAR entry in its DDVAL field (field 8), a TOMVAR
entry in its DSVID field, a entry in its DDVALID field (field 4) or a RSPINR entry in its SPTID
field (field 6).
Main Index
DDVAL 1559
Discrete Design Variable Values
2. Trailing fields on a DDVAL record can be left blank if the next record is of type DVALi THRU
DVALj BY INC. Also fields 7 - 9 must be blank when the type DVALi THRU DVALj BY INC is
used in fields 2 - 6 and fields
8 - 9 must be blank when the type DVALi “THRU” DVALj “BY” INC is used in fields 3 - 7 for the
first record. Embedded blanks are not permitted in other cases.
3. The DVALi values in a sequence need not be in an ascending or descending order. They can be in
any order.
4. If the format DVALi THRU DVALj BY INC is employed, INC must be a positive real value if
DVALi < DVALj and INC must be a negative real value if DVALi > DVALj. The program
terminates the execution with an appropriate fatal error if this requirement is not satisfied.
5. The format DVALi THRU DVALj BY INC defines a list of discrete values given by DVALi,
DVALi+INC, DVALi+2.0*INC, …., DVALj. The last discrete value of DVALj is always included,
even if the range is not evenly divisible by INC.
6. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1560 DEACTEL
Elements To Be Deactivated for SOL 400 Analysis
DEACTEL Elements To Be Deactivated for SOL 400 Analysis
This entry identifies the elements that do not participate in the analysis or do not participate in a particular
physics pass of a coupled analysis. SOL 400 for NLSTATIC, and NLTRAN, as well Perturbation analyses
only.
Format:
1 2 3 4 5 6 7 8 9 10
DEACTEL ID ISET
Example:
DEACTEL 2 200
Describer Meaning
ID ID of the DEACTEL entry. This is referenced by a DEACTEL=ID Case Control
command. (Integer; no Default)
ISET SID of a list of elements defined by a SET3 entry. (Integer; no Default)
Remarks:
1. DEACTEL can only be referenced before the first subcase and/or inside the first subcase and/or inside
the first step of the first subcase and/or inside each substep of the first step of the first subcase.
References that are made anywhere else are currently ignored. It is referenced by the Case Control
command DEACTEL=ID.
2. The description field (DES) of the SET3 entry referenced by ISET can only be of type ELEM.
3. Element IDs in the list originating from some set that do not exist are ignored.
Main Index
DEFORM 1561
Static Element Deformation
DEFORM Static Element Deformation
Defines enforced axial deformation for one-dimensional elements for use in statics problems.
Format:
1 2 3 4 5 6 7 8 9 10
DEFORM SID EID1 D1 EID2 D2 EID3 D3
Example:
DEFORM 1 535 .05 536 -.10
Describer Meaning
SID Deformation set identification number. (Integer > 0)
EIDi Element number. (Integer > 0)
Di Deformation. (Real; positive value represents elongation.)
Remarks:
1. The referenced element must be one-dimensional (CROD, CONROD, CTUBE, CBAR, CBEAM).
2. Deformation sets must be selected in the Case Control Section with DEFORM = SID.
3. One to three enforced element deformations may be defined on a single entry.
4. The DEFORM entry, when called by the DEFORM Case Control command, is applicable to linear
static, inertia relief, differential stiffness, and buckling (Solutions 101, 105, 114, and 200) and will
produce fatal messages in other solution sequences. Use SPCD to apply enforced displacements in
solution sequences for which DEFORM does not apply.
Main Index
1562 DEFUSET
Degree-of-Freedom Set Name Definition
DEFUSET Degree-of-Freedom Set Name Definition
Defines new names for degree-of-freedom sets.
Format:
1 2 3 4 5 6 7 8 9 10
DEFUSET OLD1 NEW1 OLD2 NEW2 OLD3 NEW3 OLD4 NEW4
Example:
DEFUSET U2 X U4 Y U3 Z
Describer Meaning
OLDi Default set name. (One to four characters)
NEWi New set name. (One to four characters)
Remarks:
1. From one to four set names may be specified on a single entry.
2. OLDi must refer to any of the set names given in Degree-of-Freedom Sets. It is recommended that
OLDi refer only to the set names U1 through U6. If sets PA or PS are referenced, a user fatal message
is issued.
3. All NEWi names must be unique with respect to all other set names.
4. The DEFUSET entry is optional since default set names exist for all displacement sets.
5. The DEFUSET entry must be present in the Bulk Data Section in all restarts.
Main Index
DELAY 1563
Dynamic Load Time Delay
DELAY Dynamic Load Time Delay
Defines the time delay term in the equations of the dynamic loading function.
Format:
1 2 3 4 5 6 7 8 9 10
DELAY SID P1 C1 T1 P2 C2 T2
Example:
DELAY 5 21 6 4.25 7 6 8.1
Describer Meaning
SID Identification number of the DELAY entry. (Integer > 0)
Pi Grid, extra, or scalar point identification number. (Integer > 0)
Ci Component number. (Integer 1 through 6 for grid point, blank or 0 for extra point or
scalar point.)
Ti Time delay for designated point Pi and component Ci. (Real)
Remarks:
1. One or two dynamic load time delays may be defined on a single entry.
2. SID must also be specified on a RLOAD1, RLOAD2, TLOAD1, TLOAD2, or ACSRCE entry. See
those entry descriptions for the formulas that define the manner in which the time delay is used.
3. A DAREA, LSEQ or static load entry should be used to define a load at Pi and Ci.
4. In superelement analysis, DELAY entries may only be applied to loads on points in the residual
structure.
Main Index
1564 DEQATN
Equation Definition
DEQATN Equation Definition
Defines one or more equations for use in analysis.
Format:
1 2 3 4 5 6 7 8 9 10
DEQATN EQID EQUATION
EQUATION (Cont.)
Example:
DEQATN 14 F1 A, B, C, D, R = A + B C – D ** 3 + 10.0 + sin PI 1 R
+ A**2 B – C ; F = A + B – F1 D
Describer Meaning
EQID Unique equation identification number. (Integer > 0)
EQUATION Equation(s). See Remarks. (Character)
Remarks:
1. EQUATION is a single equation or a set of nested equations and is specified in fields 3 through 9 on
the first entry and may be continued on fields 2 through 9 on the continuation entries. On the
continuation entries, no commas can appear in columns 1 through 8. All data in fields 2 through 9
must be specified in columns 9 through 72. The large-field format is not allowed.
A single equation has the following format:
variable-1 (x1, x2, ..., xn)=expression-1
A set of nested equations is separated by semicolons and has the format:
variable-1 (x1, x2, ..., xn)=expression-1;
variable-2=expression-2;variable-3=expression-3;
etc.
variable-m=expression-m
Expression-i is a collection of constants, real variables, and real functions, separated by operators, and
must produce a single real value. (x1, x2, ..., xn) is the list of all the variable names (except variable-i)
that appear in all expressions. Variable-i may be used in subsequent expressions. The last equation,
variable-m=expression-m, provides the value that is returned to the Bulk Data entry that references
EQID; e.g., DRESP2. The example above represents the following mathematical equations:
2
3 A
F1 = A + B C – D + 10 + sin R + -------------
B–C
F = A + B + F1 D
Main Index
DEQATN 1565
Equation Definition
where SIN and PI are intrinsic functions. See Remark 4.
2. EQUATION may contain embedded blanks. EQUATION must contain less than 32,000 nonblank
characters. If more characters are required for use with a DRESP2 entry, the DRESP2 can be divided
into two or more DRESP2 entries with a master DRESP2 referencing subsequent DRESP2s.
3. The syntax of the expressions follows FORTRAN language standards. The allowable arithmetic
operations are shown in Table 8 in the order of execution precedence. Parenthesis are used to change
the order of precedence. Operations within parentheses are performed first with the usual order of
precedence being maintained within the parentheses.
Table 8 DEQATN Entry Operators
Sample
Operator Operation Expressions Interpreted As
-, + Negative or Positive immediately X * * -Y X * * (-Y)
preceded by exponentiation
** Exponentiation -X * * Y (-X * * Y)
-, + Negative or Positive -X-Y (-X)-Y
*, / Multiplication or Division X * Y-Z (X * Y)-Z
+, - Addition or Subtraction X+Y X+Y
4. The expressions may contain intrinsic functions. Table 9 contains the format and descriptions of
functions that may appear in the expressions. The use of functions that may be discontinuous must
be used with caution because they can cause discontinuous derivatives. These are ABS, DIM, MAX,
MIN, and MOD. For examples and further details see the MSC Nastran DMAP Programmer’s Guide.
Table 9 DEQATN Entry Functions
Format Description Mathematical Expressions
ABS(x) absolute value x
ACOS(x) arccosine cos-1 x
ACOSH(x) hyperbolic arccosine cosh-1 x
ASIN(x) arcsine sin-1 x
ASINH(x) hyperbolic arcsine sinh-1 x
ATAN(x) arctangent tan-1 x
ATAN2(x,y) arctangent of quotient tan-1 (x/y)
ATANH(x) hyperbolic arctangent tanh-1 x
ATANH2(x,y) hyperbolic arctangent tanh-1 (x/y)
of quotient
Main Index
1566 DEQATN
Equation Definition
Table 9 DEQATN Entry Functions (continued)
Format Description Mathematical Expressions
AVG(X1, X2, .., Xn) average n
1---
n Xi
i=1
COS(x) cosine cos x
COSH(x) hyperbolic cosine cosh x
DB(P, PREF) sound pressure in P
decibel 20.0 log ---------------
PREF
DBA(P, PREF, F) sound pressure in P
decibel (perceived) 20.0 log --------------- + 10.0 log Ta1 +
PREF
10.0 log Ta2
DIM(x,y) positive difference x-MIN(x,y)
EXP(x) exponential ex
INVDB(DB, PREF) inverse Db DB-
--------- + logPREF
20.0
10
INVDBA(DBA, PREF, inverse Dba DBA – 10.0 log Ta1 – 10.0 log Ta2 -
---------------------------------------------------------------------------------------------------
F) 20.0
10
LOG(x) natural logarithm loge x
LOG10(x) common logarithm log10 x
LOGX(x,y) base x logarithm logx y
MAX(x1, x2, ...) maximum maximum of x1, etc.
MIN(x1, x2, ...) minimum minimum of x1, etc.
MOD(x,y) remainder (modulo) x – y INT x y
PI(x) multiples of pi () x
RSS X 1 X 2 Xn square root of sum of n
squares 2
Xi
i=1
SIN(x) sine sin x
SINH(x) hyperbolic sine sinh x
SQRT(x) square root x
Main Index
DEQATN 1567
Equation Definition
Table 9 DEQATN Entry Functions (continued)
Format Description Mathematical Expressions
SSQ X 1 X 2 Xn sum of squares n
2
Xi
i=1
SUM X 1 X 2 Xn summation n
Xi
i=1
TAN(x) tangent tan x
TANH(x) hyperbolic tangent tanh x
where
X1, X2, .., Xn,P = structure responses or acoustic pressure
PREF = reference pressure
F = forcing frequency
DB = acoustic pressure in decibel
DBA = perceived acoustic pressure in decibel
4
K3 F
------------------------------------------------------
Ta1 =
2 2 2 2
F + P2 F + P3
4
K1 F
-----------------------------------------------------------
-
Ta2 =
2 2 2 2 2 2
F + P1 F + P4
K1 = 2.242882e+16
K3 = 1.562339
P1 = 20.598997
P2 = 107.65265
P3 = 737.86223
P4 = 12194.22
5. If the DEQATN entry is referenced by the:
• DVCREL2, DVMREL2, or DVPREL2 entry, then X i represents the DVIDj and LABLk fields.
Main Index
1568 DEQATN
Equation Definition
X i represents the DVIDj, LABLk, NRm, Gp, DPIPq, DCICr, DMIMs,
• DRESP2 entry, then
DPI2Pt, DCI2Cu, DMI2Mv, and NRRw fields in that order.
6. If the DEQATN entry is referenced by DRESP2, DVCREL2, DVMREL2 or DVPREL2 entries,
constants must be specified in single precision regardless of your machine’s word length.
7. The DMAP logical operators NOT, AND, OR, XOR, and XQV cannot be used as Xi names.
8. Input errors on the DEQATN entry often result in poor messages. Substituting a “[” for a parenthesis
or violating the restriction against large field format are examples. Known messages are UFM 215,
SFM 233 and UFM 5199. If any of these messages are encountered then review the DEQATN entry
input.
9. Intrinsic functions AVG, MAX, MIN, RSS, SSQ and SUM are limited to <97 arguments. If more
arguments are desired, the functions may be divided up. For example, to perform a sum of squares on
170 items, use:
SSQ(X1,X2,…X95) + SSQ(X96,X97,…X170).
For MAX/MIN, the following concatenation can be used:
MAX1 = MAX(X1,X2,..X95), MAX2=MAX(X96,X97…X170); MAXT=MAX(MAX1,MAX2).
For AVG, an example to average 170 terms is:
AVG1=AVG(X1,X2,…X95);AVG2=AVG(X96,X97..X170); AVGT = (95. * AVG1 + 75. * AVG2) /
170.
10. Arithmetic is carried out using the type of the input data. For example, in the expression:
X = A** 1 2
both values in the exponent are integers so that the value returned for the exponent is calculated using
integer arithmetic or 1 2 = 0 . In this case 1/2 should be replaced by (.5).
Main Index
DESVAR 1569
Design Variable
DESVAR Design Variable
Defines a design variable for design optimization.
Format:
1 2 3 4 5 6 7 8 9 10
DESVAR ID LABEL XINIT XLB XUB DELXV DDVAL
Example:
DESVAR 2 BARA1 35.0 10. 100. 0.2
Describer Meaning
ID Unique design variable identification number. (Integer > 0)
LABEL User-supplied name for printing purposes. (Character)
XINIT Initial value. (Real; XLB < XINIT < XUB)
XLB Lower bound. (Real; Default = -1.0E+20)
XUB Upper bound. (Real; Default = +1.0E+20)
DELXV Fractional change allowed for the design variable during approximate optimization.
(Real > 0.0; for Default see Remark 2.)
DDVAL ID of a DDVAL entry that provides a set of allowable discrete values. (Blank or Integer
> 0; Default=blank for continuous design variables. See Remark 3.)
Remarks:
1. DELXV can be used to control the change in the design variable during one optimization cycle.
2. If DELXV is blank, the default is taken from the specification of the DELX parameter on the
DOPTPRM entry. If DELX is not specified, then the default is 0.5.
3. If the design variable is to be discrete (Integer > 0 in DDVAL field), and if either of the XLB and/or
XUB bounds are wider than those given by the discrete list of values on the corresponding DDVAL
entry, XLB and/or XUB will be replaced by the minimum and maximum discrete values.
Main Index
1570 DETSPH
Spherical Detonation Wave
DETSPH Spherical Detonation Wave
Defines the ignition point from which a spherical detonation wave travels, causing the reaction of high
explosive materials. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
DETSPH DID MID X Y Z VEL TIME
Example:
DETSPH 100 10 96.5 177.6 37.4 2379. 1.7E-6
Describer Meaning
DID Unique detonation number. (Integer > 0; Required)
MID References MATDEUL id of the exploding material. (Integer > 0; Required)
X, Y, Z Coordinates of the ignition point. (Real, 0.0)
VEL Velocity of the detonation wave. (Real > 0.0, 0.0)
TIME Detonation time. (Real > 0.0, 0.0)
Remark:
1. An element detonates when a spherical detonation wave originating from the detonation point at the
specified time reaches the element.
Main Index
DIVERG 1571
Divergence Analysis Data
DIVERG Divergence Analysis Data
Defines Mach numbers (m) for a static aeroelastic divergence analysis.
Format:
1 2 3 4 5 6 7 8 9 10
DIVERG SID NROOT M1 M2 M3 M4 M5 M6
M7 M8 -etc.-
Example:
DIVERG 70 2 .5 .8 .9
Describer Meaning
SID Unique set identifier. (Integer > 0)
NROOT Number of divergence roots that are to be output and their eigenvectors printed.
(Integer; Default = 1)
Mi Mach number. (Real > 0.0)
Remarks:
1. The DIVERG entry is referenced in Case Control by “DIVERG = SID”.
2. The NROOT lowest divergence dynamic pressures are printed. If there are fewer than NROOT
pressures, all available dynamic pressures are printed.
3. Mi values must be distinct.
4. A blank Mach number field terminates the input.
Main Index
1572 DLINK
Multiple Design Variable Linking
DLINK Multiple Design Variable Linking
Relates one design variable to one or more other design variables.
Format:
1 2 3 4 5 6 7 8 9 10
DLINK ID DDVID C0 CMULT IDV1 C1 IDV2 C2
IDV3 C3 -etc.-
Example:
DLINK 10 2 0.1 0.33 4 2.0 6 -1.0
8 7.0
Describer Meaning
ID Unique identification number. (Integer > 0)
DDVID Dependent design variable identification number. (Integer > 0)
C0 Constant term. (Real; Default = 0.0)
CMULT Constant multiplier. (Real; Default = 1.0)
IDVi Independent design variable identification number. (Integer > 0)
Ci Coefficient i corresponding to IDVi. (Real)
Remarks:
1. DLINK defines the relationship
DDVID = C0 + CMULT* Ci* IDVi
i
2. This capability provides a means of linking physical design variables such as element thicknesses to
nonphysical design variables such as the coefficients of interpolating functions.
3. CMULT provides a simple means of scaling the Ci. For example if Ci = 1/7, 2/7, 4/7, etc. is desired,
then CMULT = 1/7 and Ci = 1, 2, 4, etc., may be input.
4. An independent IDVi must not occur on the same DLINK entry more than once.
5. ID is for user reference only.
6. If a design variable is specified as dependent on a DLINK entry, then it cannot be specified as
independent on another DLINK entry.
Main Index
DLOAD 1573
Dynamic Load Combination or Superposition
DLOAD Dynamic Load Combination or Superposition
Defines a dynamic loading condition for frequency response or transient response problems as a linear
combination of load sets defined via RLOAD1, RLOAD2, TLOAD1, TLOAD2 and ACSRCE entries for
frequency response or TLOAD1 or TLOAD2 entries for transient response.
Format:
1 2 3 4 5 6 7 8 9 10
DLOAD SID S S1 L1 S2 L2 S3 L3
S4 L4 -etc.- *
Examples:
DLOAD 17 1.0 2.0 6 -2.0 7 2.0 8
-2.0 9
Describer Meaning
SID Load set identification number. See Remarks 1. and 4. (Integer > 0)
S Scale factor. See Remarks 2. and 8. (Real)
Si Scale factors. See Remarks 2., 7. and 8. (Real)
Li Load set identification numbers of RLOAD1, RLOAD2, TLOAD1, TLOAD2, and
ACSRCE entries. See Remarks 3. and 7. (Integer > 0)
Remarks:
1. Dynamic load sets must be selected in the Case Control Section with DLOAD = SID.
2. The load vector being defined by this entry is given by
P = S Si P i
i
3. Each Li must be unique from any other Li on the same entry.
4. SID must be unique from all ACSRCE, RLOAD1, RLOAD2, TLOAD1 and TLOAD2 dynamic
load entries.
5. Nonlinear transient load sets (NOLINi entries) may not be specified on DLOAD entries. NOLINi
entries are selected separately in the Case Control Section by the NONLINEAR command.
6. A DLOAD entry may not reference a set identification number defined by another DLOAD entry.
7. The scale factor Si will apply to all dynamic load entries with load set identification number of Li.
8. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1574 DMI
Direct Matrix Input
DMI Direct Matrix Input
Defines matrix data blocks. Generates a matrix of the following form:
X 11 X 12 X 1n
X 21 X 22 X 2n
NAME =
· · · ·
X m1 X mn
where the elements X ij may be real X ij = A ij or complex X ij = A ij + iB ij . The matrix is defined by
a single header entry and one or more column entries. Only one header entry is required. A column entry is
required for each column with nonzero elements.
Header Entry Format:
1 2 3 4 5 6 7 8 9 10
DMI NAME “0” FORM TIN TOUT M N
Column Entry Format for Real Matrices:
DMI NAME J I1 A(I1,J) A(I1+1,J) -etc.- I2
A(I2,J) -etc.-
Column Entry Format for Complex Matrices:
DMI NAME J I1 A(I1,J) B(I1,J) A(I1+1,J) B(I1+1,J) -etc.-
I2 A(I2,J) B(I2,J) -etc.-
Example of a Real Matrix:
DMI BBB 0 2 1 1 4 2
DMI BBB 1 1 1. 3. 5.
DMI BBB 2 2 6. 4 8.
1.0 0.0
BBB = 3.0 6.0
5.0 0.0
0.0 8.0
Main Index
DMI 1575
Direct Matrix Input
Example of a Complex Matrix:
DMI QQQ 0 2 3 3 4 2
DMI QQQ 1 1 1.0 2.0 3.0 0.0 3
5.0 6.0
DMI QQQ 2 2 6.0 7.0 4 8.0 9.0
1.0 + 2.0i 0.0 + 0.0i
QQQ = 3.0 + 0.0i 6.0 + 7.0i
5.0 + 6.0i 0.0 + 0.0i
0.0 + 0.0i 8.0 + 9.0i
Describer Meaning
NAME Name of the matrix. See Remark 1. Name is used to reference the data block in the
DMAP sequence. (One to eight alphanumeric characters, the first of which must be
alphabetic.)
FORM Form of matrix, as follows: (Integer)
1 Square matrix (not symmetric)
2 General rectangular matrix
3 Diagonal matrix (M=number of rows, N = 1)
4 Lower triangular factor
5 Upper triangular factor
6 Symmetric matrix
8 Identity matrix (M=number of rows, N = M)
TIN Type of matrix being input, as follows: (Integer)
1 Real, single precision (one field used/element)
2 Real, double precision (one field used/element)
3 Complex, single precision (two fields used/element)
4 Complex, double precision (two fields used/element)
Main Index
1576 DMI
Direct Matrix Input
Describer Meaning
TOUT Type of matrix being output, as follows: (Integer)
0 Set by precision cell
1 Real, single precision
2 Real, double precision
3 Complex, single precision
4 Complex, double precision
M Number of rows in NAME. (Integer > 0)
N Number of columns in NAME. Except for FORM 3 and 8. (Integer > 0)
"0" Indicates the header entry.
J Column number of NAME. (Integer > 0)
I1, I2, etc. Row number of NAME, which indicates the beginning of a group of nonzero elements
in the column. See Remark 13. (Integer > 0)
A(Ix,J) Real part of element (see TIN). (Real)
B(Ix,J) Imaginary part of element (see TIN). (Real)
Remarks:
1. In order to use the DMI feature, the user must write a DMAP, or make alterations to a solution
sequence that includes the DMIIN module. See the MSC Nastran DMAP Programmer’s Guide. All of the
rules governing the use of data blocks in DMAP sequences apply.
2. The total number of DMIs and DTIs may not exceed 1000.
3. Field 3 of the header entry must contain an integer of zero (0).
4. For symmetric matrices, the entire matrix must be input.
5. Only nonzero terms need be entered.
6. Leading and trailing zeros in a column do not have to be entered. However, a blank field between
nonzero fields on this entry is not equivalent to a zero. If a zero input is required, the appropriate type
zero must be entered (i.e., 0.0 or 0.0D0).
7. Complex input must have both the real and imaginary parts entered if either part is nonzero; i.e., the
zero component must be input explicitly.
8. If A(Ix,J) is followed by “THRU” in the next field and an integer row number “IX” after the THRU,
then A(lx,J) will be repeated in each row through IX. The “THRU” must follow an element value.
For example, the entries for a real matrix RRR would appear as follows:
1 2 3 4 5 6 7 8 9 10
DMI NAME J I1 A(I1,J) I1 A(I2,J)
DMI RRR 1 2 1.0 THRU 10 12 2.0
Main Index
DMI 1577
Direct Matrix Input
These entries will cause the first column of the matrix RRR to have a zero in row 1, the values 1.0 in
rows 2 through 10, a zero in row 11, and 2.0 in row 12.
9. Each column must be a single logical entry. The terms in each column must be specified in increasing
row number order.
10. The “FORM” options 4, 5, and 8 are nonstandard forms and may be used only in conjunction with
the modules indicated in Table 10.
Table 10 DMI FORM Options
Modules
FORM Matrix Description ADD FBS MATPRN MPYAD
4 Lower Triangular Factor X X
5 Upper Triangular Factor X X
8 Identity X X X X
11. Form 3 matrices are converted to Form 6 matrices, which may be used by any module.
12. Form 7 matrices may not be defined on this entry.
13. I1 must be specified. I2, etc. are not required if their matrix elements follow the preceding element
in the next row of the matrix. For example, in the column entry for column 1 of QQQ, neither I2
nor I3 is specified.
14. The DMIG entry is more convenient for matrices with rows and columns that are referenced by grid
or scalar point degrees-of-freedom.
15. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1578 DMIAX
Direct Matrix Input for Axisymmetric Analysis
DMIAX Direct Matrix Input for Axisymmetric Analysis
Defines axisymmetric (fluid or structure) related direct input matrix terms.
The matrix is defined by a single header entry and one or more column entries. Only one header entry is
required. A column entry is required for each column with nonzero elements.
Header Entry Format:
1 2 3 4 5 6 7 8 9 10
DMlAX NAME “0" IFO TIN TOUT
Column Entry Format:
DMlAX NAME GJ CJ NJ
G1 C1 N1 A1 B1
G2 C2 -etc.-
Example:
Remarks:
DMIAX B2PP 0 1 3 4
DMIAX B2PP 32
1027 3 4.25+6 2.27+3
Describer Meaning
NAME Name of the matrix. See Remark 2. (One to eight alphanumeric characters, the first of
which is alphabetic.)
IFO Form of matrix: (Integer)
1 Square matrix
2 General rectangular matrix
6 Symmetric matrix
TIN Type of matrix being input: (Integer)
1 Real, single precision (One field is used per element.)
3 Complex, single precision (Two fields are used per element.)
Main Index
DMIAX 1579
Direct Matrix Input for Axisymmetric Analysis
Describer Meaning
TOUT Type of matrix that will be created: (Integer)
1 Real, single precision
2 Real, double precision
3 Complex, single precision
4 Complex, double precision
GJ, Gi Grid, scalar, RINGFL fluid point, PRESPT pressure point, FREEPT free surface
displacement, or extra point identification number. (Integer > 0)
CJ, Ci Component number for GJ or Gi grid point (0 < Integer < 6; Blank or zero if GJ or Gi
is a scalar, fluid, or extra point.)
NJ, Ni Harmonic number of RINGFL point. Must be blank if a point type other than
RINGFL is used. A negative number implies the “sine” series; a positive number implies
the “cosine” series. (Integer)
Ai, Bi Real and imaginary parts of matrix element; row (Gi, Ci, Ni) column (GJ, CJ, NJ). If
the matrix is real (TIN = 1), then Bi must be blank.
1. This entry is allowed only if an AXIF entry is also present.
2. Matrices defined on this entry may be used in dynamics by selection with the Case Control
commands K2PP = NAME, B2PP = NAME, or M2PP = NAME for K pp 2 , B 2 , or M 2 ,
pp pp
respectively. See Superelement Analysis in the MSC Nastran Reference Guide.
3. Field 3 or the header entry must contain an integer 0.
4. For symmetric matrices, either the upper or the lower triangle terms may be specified, but not both.
5. Only nonzero terms need be entered.
6. If any DMIAX entry is changed or added on restart then a complete re-analysis may be performed.
Therefore, DMIAX entry changes or additions are not recommended on restart.
Main Index
1580 DMIG
Direct Matrix Input at Points
DMIG Direct Matrix Input at Points
Defines direct input matrices related to grid, extra, and/or scalar points. The matrix is defined by a single
header entry and one or more column entries. A column entry is required for each column with nonzero
elements.
Header Entry Format:
1 2 3 4 5 6 7 8 9 10
DMIG NAME “0" IFO TIN TOUT POLAR NCOL
Column Entry Format:
DMIG NAME GJ CJ G1 C1 A1 B1
G2 C2 A2 B2 -etc.-
Example:
DMIG STIF 0 1 3 4
DMIG STIF 27 1 2 3 3.+5 3.+3
2 4 2.5+10 0. 50 1.0 0.
Describer Meaning
NAME Name of the matrix. See Remark 1. (One to eight alphanumeric characters, the first of
which is alphabetic.)
IFO Form of matrix input. IFO = 6 must be specified for matrices selected by the K2GG,
M2GG, and B2GG Case Control commands. (Integer)
1 Square
2 or 9 Rectangular
6 Symmetric
TIN Type of matrix being input: (Integer)
1 Real, single precision (One field is used per element.)
2 Real, double precision (One field is used per element.)
3 Complex, single precision (Two fields are used per element.)
4 Complex, double precision (Two fields are used per element.
TOUT Type of matrix that will be created: (Integer)
0 Set by precision system cell (Default)
1 Real, single precision
2 Real, double precision
3 Complex, single precision
Main Index
DMIG 1581
Direct Matrix Input at Points
Describer Meaning
4 Complex, double precision
POLAR Input format of Ai, Bi. (Integer=blank or 0 indicates real, imaginary format; Integer > 0
indicates amplitude, phase format.)
NCOL Number of columns in a rectangular matrix. Used only for IFO = 9. See Remarks 5. and
6. (Integer > 0)
GJ Grid, scalar or extra point identification number for column index. (Integer > 0)
CJ Component number for grid point GJ. (0 < Integer < 6; blank or zero if GJ is a scalar or
extra point.)
Gi Grid, scalar, or extra point identification number for row index. (Integer > 0)
Ci Component number for Gi for a grid point. (0 < CJ < 6; blank or zero if Gi is a scalar
or extra point.)
Ai, Bi Real and imaginary (or amplitude and phase) parts of a matrix element. If the matrix is
real (TIN = 1 or 2), then Bi must be blank. See Remarks 11. (Real)
Remarks:
1. Matrices defined on this entry may be used in dynamics by selection in the Case Control with
K2PP = NAME, B2PP = NAME, M2PP = NAME for K , B , or M , respectively.
Matrices may also be selected for all solution sequences by K2GG = NAME, B2GG = NAME, and
M2GG = NAME. The g-set matrices are added to the structural matrices before constraints are
applied, while p-set matrices are added in dynamics after constraints are applied. Load matrices may
be selected by P2G = NAME for dynamic and superelement analyses.
2. The header entry containing IFO, TIN and TOUT is required. Each nonnull column is started with
a GJ, CJ pair. The entries for each row of that column follows. Only nonzero terms need be entered.
The terms may be input in arbitrary order. A GJ, CJ pair may be entered more than once, but input
of an element of the matrix more than once will produce a fatal message.
3. Field 3 of the header entry must contain an integer 0.
4. For symmetric matrices (IFO = 6), a given off-diagonal element may be input either below or above
the diagonal. While upper and lower triangle terms may be mixed, a fatal message will be issued if an
element is input both below and above the diagonal.
5. The recommended format for rectangular matrices requires the use of NCOL and IFO = 9. The
number of columns in the matrix is NCOL. (The number of rows in all DMIG matrices is always
either p-set or g-set size, depending on the context.) The GJ term is used for the column index. The
CJ term is ignored.
6. If NCOL is not used for rectangular matrices, two different conventions are available:
• If IFO = 9, GJ and CJ will determine the sorted sequence, but will otherwise be ignored; a
rectangular matrix will be generated with the columns submitted being in the 1 to N positions,
where N is the number of logical entries submitted (not counting the header entry).
Main Index
1582 DMIG
Direct Matrix Input at Points
• If IFO = 2, the number of columns of the rectangular matrix will be equal to the index of the
highest numbered non-null column (in internal sort). Trailing null columns of the g- or p-size
matrix will be truncated.
7. The matrix names must be unique among all DMIGs.
8. TIN should be set consistent with the number of decimal digits required to read the input data
adequately. For a single-precision specification on a short-word machine, the input will be truncated
after about eight decimal digits, even when more digits are present in a double-field format. If more
digits are needed, a double precision specification should be used instead. However, note that a
double precision specification requires a “D” type exponent even for terms that do not need an
exponent. For example, unity may be input as 1.0 in single precision, but the longer form 1.0D0 is
required for double precision.
9. On long-word machines, almost all matrix calculations are performed in single precision and on
short-word machines, in double precision. It is recommended that DMIG matrices also follow these
conventions for a balance of efficiency and reliability. The recommended value for TOUT is 0, which
instructs the program to inspect the system cell that measures the machine precision at run time and
sets the precision of the matrix to the same value. TOUT = 0 allows the same DMIG input to be used
on any machine. If TOUT is contrary to the machine type specified (for example, a TOUT of 1 on
a short-word machine), unreliable results may occur.
10. If any DMIG entry is changed or added on restart then a complete re-analysis is performed.
Therefore, DMIG entry changes or additions are not recommended on restart.
11. The matrix at points is defined under the global coordinate system, which is the CD coordinate
system defined on the grid point entries
Main Index
DMIG,UACCEL 1583
Direct Matrix Input of Enforced Static Acceleration
DMIG,UACCEL Direct Matrix Input of Enforced Static Acceleration
Defines rigid body accelerations in the basic coordinate system.
Format:
1 2 3 4 5 6 7 8 9 10
DMIG UACCEL “0" “9" TIN NCOL
DMIG UACCEL L G1 C1 X1
G1 C2 X2 G1 C3 X3
Example:
DMIG UACCEL 0 9 1 4
DMIG UACCEL 2 2 3 386.4
DMIG UACCEL 3 2 4 3.0
DMIG UACCEL 4 2 6 1.0
Describer Meaning
TIN Type of matrix being input. (Integer 1 or 2)
1 Real, single precision (One field is used per element.)
2 Real, double precision (One field is used per element.)
NCOL Number of columns, see Remark 2. Default is the number of columns specified.
(Integer > 0)
L Load sequence number. (Integer > 0)
G1 Grid point identification number of a single reference point. (Integer > 0)
Ci Component number for Gi in the basic coordinate system. See Remark 4.
(0 < Integer < 6)
Xi Value of enforced acceleration term in the basic coordinate system. (Real)
Remarks:
1. DMIG,UACCEL is an optional entry when PARAM,INREL,-1 is specified in SOLs 101 or 200. If
DMIG,UACCEL is present, the loads applied to the structure are the sum of the conventional
applied loads plus the inertia loads resulting from the rigid body accelerations defined on this entry.
If it is not present, conventional inertia relief calculations are performed.
2. The load sequence number interpretation depends on the value of the NCOL field. The
recommended method is to set it equal to the number of loading conditions. The load sequence
number L is then the sequence number of the subcase to which the applied acceleration will be
applied.
Main Index
1584 DMIG,UACCEL
Direct Matrix Input of Enforced Static Acceleration
3. The grid point identification number listed on Gi defines a single grid point on the model where loads
will be applied to cause the enforced acceleration state. Gi must also appear on a SUPORT Bulk Data
entry. It must also appear on a PARAM,GRDPNT entry. In superelement analysis, it must be a
residual structure point exterior to all superelements.
4. The Xi value is the enforced acceleration at grid point Gi. The translation and rotation components
are in consistent units and will be applied in the basic coordinate system regardless of the
displacement coordinate system specified for Gi (CD field on GRID entry).
5. Only nonzero terms need be entered.
6. See Superelement Analysis in the MSC Nastran Reference Guide for the theoretical basis of inertia relief
with superelements.
7. If any DMIG entry is changed or added on restart then a complete re-analysis is performed.
Therefore, DMIG entry changes or additions are not recommended on restart.
Main Index
DMIJ 1585
Direct Matrix Input at js-Set of the Aerodynamic Mesh
DMIJ Direct Matrix Input at js-Set of the Aerodynamic Mesh
Defines direct input matrices related to collation degrees-of-freedom (js-set) of aerodynamic mesh points for
CAERO1, CAERO3, CAERO4 and CAERO5 and for the slender body elements of CAERO2. These
include W2GJ, FA2J and input pressures and downwashes associated with AEPRESS and AEDW entries.
The matrix is described by a single header entry and one or more column entries. A column entry is required
for each column with nonzero elements. For entering data for the interference elements of a CAERO2, use
DMIJI or DMI.
Header Entry Format:
1 2 3 4 5 6 7 8 9 10
DMIJ NAME “0” IFO TIN TOUT POLAR NCOL
Column Entry Format:
DMIJ NAME GJ CJ G1 C1 A1 B1
G2 C2 A2 B2 -etc.-
Example:
DMIJ ALPH1 0 9 2 0 1
DMIJ ALPH1 1 1 1 1 .1
2 1 .1
Describer Meaning
NAME Name of the matrix. See Remark 1. (One to eight alphanumeric characters, the first of which
is alphabetic.)
IFO Form of matrix being input. (Integer)
1 Square
9 or 2 Rectangular
6 Symmetric
TIN Type of matrix being input: (Integer)
1 Real, single precision (One field is used per element)
2 Real, double precision (One field is used per element)
3 Complex, single precision (Two fields are used per element)
4 Complex, double precision (Two fields are used per element)
TOUT Type of matrix being created: (Integer)
0 Set by precision system cell (Default)
1 Real, single precision
Main Index
1586 DMIJ
Direct Matrix Input at js-Set of the Aerodynamic Mesh
Describer Meaning
2 Real, double precision
3 Complex, single precision
4 Complex, double precision
POLAR Input format of Ai, Bi. (Integer = blank or 0 indicates real, imaginary format. Integer > 0
indicated magnitude, phase format.)
NCOL Number of columns in a rectangular matrix. Used only for IFO = 9. (Integer > 0)
GJ Grid, scalar or extra point identification number for column index. (Integer > 0)
CJ Component number for grid point GJ. (0 < Integer < 6; blank or zero if GJ is a scalar or
extra point.)
Gi Grid, scalar, or extra point identification number for row index. (Integer > 0)
Ci Component number for Gi for a grid point. (0 < CJ < 0; blank or zero if Gi is a scalar or extra
point.)
Ai, Bi Real and imaginary (or amplitude and phase) parts of a matrix element. If the matrix is real
(TIN = 1 or 2), then Bi must be blank. (Real)
Remarks:
1. Matrices defined on this entry are referenced in static aeroelastic analysis by reference on AEDW
and/or AEPRESS entries. In that paradigm, a single column is required. Also, DMIJ may also be used
for the W2GJ and FA2J entries. Again, a single column is required. If both DMI and DMIJ are
specified for W2GJ or FA2J, the DMI entry will be used. DMI may NOT be used for AEDW and
AEPRESS.
2. The js-set DOF’s for each aerodynamic theory are limited to the six-DOF paradigm (3 translations
and 3 rotations). However, particular DOF’s are permanently SPC’d based on the theory’s ability to
support those degrees-of-freedom. Unlike the DMIG entry, DMIJ data will be partitioned to the j-
set, not reduced. No warnings are issued about truncated data.The j-set DOF’s for each aerodynamic
element/grid are highly method dependent. The following data define the known set, but the j-set
definition is somewhat arbitrary in the general (external aerodynamics) paradigm.
COMP
Entry Type 1 2 3 5 6
CAERO1 X
CAERO2-Y X
CAERO2-Z X
CAERO2-ZY X X
Main Index
DMIJ 1587
Direct Matrix Input at js-Set of the Aerodynamic Mesh
3. The header entry containing IFO, TIN and TOUT is required. Each nonnull column is started with
a GJ, CJ pair. The entries for each row of that column then follow. Only nonzero terms need be
entered. The terms may be input in arbitrary order. A GJ, CJ pair may be entered more than once,
but the input of an element of the matrix more than once results in a fatal message.
4. Field 3 of the header entry must contain an integer 0.
5. For symmetric matrices (very rare in the j-set!) (IFO=6), a given off-diagonal element may be input
either below or above the diagonal. While upper and lower triangle terms may be mixed, a fatal
message will be issued if an element is input both above and below the diagonal.
6. The recommended format for rectangular matrices requires the use of NCOL and IFO = 9. the
number of columns in the matrix is NCOL. (The number of rows in all DMIJ matrices is always the
js-set size--the union of the j-set and the permanently SPC’d partition). The GJ term is used for the
column index. the CJ term is ignored.
7. If NCOL is not used for rectangular matrices, two different conventions are available:
• If IFO = 9, GJ and CJ will determine the sorted sequence, but will otherwise be ignored; a
rectangular matrix will be generated with the columns submitted being in the 1 to N positions,
where N is the number of logical entries submitted (not counting the header entry).
• If IFO = 2, the number of columns of the rectangular matrix will be equal to the index of the
highest numbered non-null column (in internal sort). Trailing null columns of the js-size matrix
will be truncated.
8. The matrix names must be unique among all DMIJ.
9. TIN should be consistent with the number of decimal digits required to read the input data
adequately. For a single precision specification on a short word machine, the input will be truncated
after about eight decimal digits, even when more digits are present in a double field format. If more
digits are needed, a double precision specification should be used instead. However, not that a double
precision specification requires a “D” type exponent even for terms that do not need an exponent. For
example, unity may be input as 1.0 in single precision, but the longer form 1.0D0 is required for
double precision.
10. On long word machines, almost all matrix calculations are performed in single precision and, on short
word machines, in double precision. It is recommended that DMIJ matrices also follow these
conventions for a balance of efficiency and reliability. The recommended value for TOUT is 0, which
instructs the program to inspect the system cell that measures the machine precision at run time and
sets the precision of the matrix to the same value. TOUT = 0 allows the same DMIJ input to be used
on any machine. If TOUT is contrary to the machine type specified, unreliable results may occur.
11. If any DMIJ entry is changed or added on restart then a complete reanalysis is performed. Therefore,
DMIJ entry changes or additions are not recommended on restart.
Main Index
1588 DMIJI
Direct Matrix Input at js-Set of the Interference Body
DMIJI Direct Matrix Input at js-Set of the Interference Body
Defines direct input matrices related to collation degrees-of-freedom (js-set) of aerodynamic mesh points for
the interference elements of CAERO2. These include W2GJ, FA2J and input pressures and downwashes
associated with AEPRESS and AEDW entries. The matrix is described by a single header entry and one or
more column entries. A column entry is required for each column with nonzero elements. For entering data
for the slender elements of a CAERO2, or a CAERO1, 3, 4 or 5 use DMIJ or DMI.
Header Entry Format:
1 2 3 4 5 6 7 8 9 10
DMIJI NAME “0” IFO TIN TOUT POLAR NCOL
Column Entry Format:
DMIJ NAME GJ CJ G1 C1 A1 B1
G2 C2 A2 B2 -etc.-
Example:
DMIJI ALPH1 0 9 2 0 1
DMIJI ALPH1 1 1 1 1 .1
2 1 .1
Describer Meaning
NAME Name of the matrix. See Remark 1. (One to eight alphanumeric characters, the first of
which is alphabetic.)
IFO Form of matrix being input. (Integer)
1 Square
9 or 2 Rectangular
6 Symmetric
TIN Type of matrix being input: (Integer)
1 Real, single precision (One field is used per element)
2 Real, double precision (One field is used per element)
3 Complex, single precision (Two fields are used per element)
4 Complex, double precision (Two fields are used per element)
TOUT Type of matrix being created: (Integer)
0 Set by precision system cell (Default)
1 Real, single precision
2 Real, double precision
Main Index
DMIJI 1589
Direct Matrix Input at js-Set of the Interference Body
Describer Meaning
3 Complex, single precision
4 Complex, double precision
POLAR Input format of Ai, Bi. (Integer = blank or 0 indicates real, imaginary format. Integer > 0
indicated magnitude, phase format.)
NCOL Number of columns in a rectangular matrix. Used only for IFO = 9. (Integer > 0)
GJ Grid, scalar or extra point identification number for column index. (Integer > 0)
CJ Component number for grid point GJ. (0 < Integer < 6; blank or zero if GJ is a scalar or
extra point.)
Gi Grid, scalar, or extra point identification number for row index. (Integer > 0)
Ci Component number for Gi for a grid point. (0 < CJ < 6; blank or zero if Gi is a scalar or
extra point.)
Ai, Bi Real and imaginary (or amplitude and phase) parts of a matrix element. If the matrix is real
(TIN = 1 or 2), then Bi must be blank. (Real)
Remarks:
1. Matrices defined on this entry are referenced in static aeroelastic analysis by reference on AEDW
and/or AEPRESS entries. In that paradigm, a single column is required. DMI may NOT be used for
AEDW and AEPRESS.
2. The js-set DOF’s for each aerodynamic theory are limited to the six-DOF paradigm (3 translations
and 3 rotations). However, particular DOF’s are permanently SPC’d based on the theory’s ability to
support those degrees-of-freedom. Unlike the DMIG entry, DMIJI data will be partitioned to the j-
set, not reduced. No warnings are issued about truncated data. The j-set DOF’s for each aerodynamic
element/grid are highly method dependent. The following data define the known set, but the j-set
definition is somewhat arbitrary in the general (external aerodynamics) paradigm.
COMP
Entry Type 1 2 3 5 6
CAERO2-Y X
CAERO2-Z X
CAERO2-ZY X X
3. The header entry containing IFO, TIN and TOUT is required. Each nonnull column is started with
a GJ, CJ pair. The entries for each row of that column then follow. Only nonzero terms need be
entered. The terms may be input in arbitrary order. A GJ, CJ pair may be entered more than once,
but the input of an element of the matrix more than once results in a fatal message.
4. Field 3 of the header entry must contain an integer 0.
Main Index
1590 DMIJI
Direct Matrix Input at js-Set of the Interference Body
5. For symmetric matrices (very rare in the j-set!) (IFO=6), a given off-diagonal element may be input
either below or above the diagonal. While upper and lower triangle terms may be mixed, a fatal
message will be issued if an element is input both above and below the diagonal.
6. The recommended format for rectangular matrices requires the use of NCOL and IFO = 9. the
number of columns in the matrix is NCOL. (The number of rows in all DMIJI matrices is always the
js-set size--the union of the j-set and the permanently SPC’d partition). The GJ term is used for the
column index. the CJ term is ignored.
7. If NCOL is not used for rectangular matrices, two different conventions are available:
• If IFO = 9, GJ and CJ will determine the sorted sequence, but will otherwise be ignored; a
rectangular matrix will be generated with the columns submitted being in the 1 to N positions,
where N is the number of logical entries submitted (not counting the header entry).
• If IFO = 2, the number of columns of the rectangular matrix will be equal to the index of the
highest numbered nonnull column (in internal sort). Trailing null columns of the js-size matrix
will be truncated.
8. The matrix names must be unique among all DMIJI.
9. TIN should be consistent with the number of decimal digits required to read the input data
adequately. For a single precision specification on a short word machine, the input will be truncated
after about eight decimal digits, even when more digits are present in a double field format. If more
digits are needed, a double precision specification should be used instead. However, not that a double
precision specification requires a “D” type exponent even for terms that do not need an exponent. For
example, unity may be input as 1.0 in single precision, but the longer form 1.0D0 is required for
double precision.
10. On long word machines, almost all matrix calculations are performed in single precision and, on short
word machines, in double precision. It is recommended that DMIJ matrices also follow these
conventions for a balance of efficiency and reliability. The recommended value for TOUT is 0, which
instructs the program to inspect the system cell that measures the machine precision at run time and
sets the precision of the matrix to the same value. TOUT = 0 allows the same DMIJI input to be used
on any machine. If TOUT is contrary to the machine type specified, unreliable results may occur.
11. If any DMIJ entry is changed or added on restart then a complete reanalysis is performed. Therefore,
DMIJ entry changes or additions are not recommended on restart.
Main Index
DMIK 1591
Direct Matrix Input at ks-Set of the Aerodynamic Mesh
DMIK Direct Matrix Input at ks-Set of the Aerodynamic Mesh
Defines direct input matrices related to physical (displacement) degrees-of-freedom (ks-set) of aerodynamic
grid points. These include WKK, WTFACT and input forces associated with AEFORCE entries. The matrix
is described by a single header entry and one or more column entries. A column entry is required for each
column with nonzero elements.
Header Entry Format:
1 2 3 4 5 6 7 8 9 10
DMIK NAME “0” IFO TIN TOUT POLAR NCOL
Column Entry Format:
DMIK NAME GJ CJ G1 C1 A1 B1
G2 C2 A2 B2 -etc.-
Example:
DMIK ALPH1 0 9 2 0 1
DMIK ALPH1 1 1 1 1 1.0
2 1 1.0
Describer Meaning
NAME Name of the matrix. See Remark 1. (One to eight alphanumeric characters, the first of
which is alphabetic.)
IFO Form of matrix being input. (Integer)
1 Square
9 or 2 Rectangular
6 Symmetric
TIN Type of matrix being input: (Integer)
1 Real, single precision (One field is used per element)
2 Real, double precision (One field is used per element)
3 Complex, single precision (Two fields are used per element)
4 Complex, double precision (Two fields are used per element)
TOUT Type of matrix being created: (Integer)
0 Set by precision system cell (Default)
1 Real, single precision
2 Real, double precision
3 Complex, single precision
Main Index
1592 DMIK
Direct Matrix Input at ks-Set of the Aerodynamic Mesh
Describer Meaning
4 Complex, double precision
POLAR Input format of Ai, Bi. (Integer = blank or 0 indicates real, imaginary format. Integer > 0
indicated magnitude, phase format.)
NCOL Number of columns in a rectangular matrix. Used only for IFO = 9. (Integer > 0)
GJ Grid, scalar or extra point identification number for column index. (Integer > 0)
CJ Component number for grid point GJ. (0 < Integer < 6; blank or zero if GJ is a scalar or
extra point.)
Gi Grid, scalar, or extra point identification number for row index. (Integer > 0)
Ci Component number for Gi for a grid point. (0 < CJ < 6; blank or zero if Gi is a scalar or
extra point.)
Ai, Bi Real and imaginary (or amplitude and phase) parts of a matrix element. If the matrix is real
(TIN = 1 or 2), then Bi must be blank. (Real)
Remarks:
1. Matrices defined on this entry are referenced in static aeroelastic analysis by reference on AEFORCE
entries. In that paradigm, a single column is required. Also, DMIK may also be used for the WKK
and WTFACT entries. Matrices defined on this entry are referenced in static aeroelastic analysis by
reference on AEFORCE entries. In that paradigm, a single column is required. Also, DMIK may also
be used for the WKK and WTFACT entries. If both DMI and DMIK are specified for WKK or
WTFACT, the DMI entry will be used. DMI may NOT be used for AEFORCE.
2. The ks-set DOF’s for each aerodynamic theory are limited to the six-DOF paradigm (3 translations
and 3 rotations). However, particular DOF’s are permanently SPC’d based on the theory’s ability to
support those degrees-of-freedom. Unlike the DMIG entry, DMIK data will be partitioned to the k-
set, not reduced. No warnings are issued about truncated data. The k-set DOF’s for each aerodynamic
element/grid are highly method dependent. The following data define the known set, but the j-set
definition is somewhat arbitrary in the general (external aerodynamics) paradigm.
COMP
Entry Type 1 2 3 5 6
CAERO1 X X
CAERO2-Y X X
CAERO2-Z X X
CAERO2-ZY X X X X
3. The header entry containing IFO, TIN and TOUT is required. Each nonnull column is started with
a GJ, CJ pair. The entries for each row of that column then follow. Only nonzero terms need be
entered. The terms may be input in arbitrary order. A GJ, CJ pair may be entered more than once,
but the input of an element of the matrix more than once results in a fatal message.
Main Index
DMIK 1593
Direct Matrix Input at ks-Set of the Aerodynamic Mesh
4. Field 3 of the header entry must contain an integer 0.
5. For symmetric matrices (IFO=6), a given off-diagonal element may be input either below or above
the diagonal. While upper and lower triangle terms may be mixed, a fatal message will be issued if an
element is input both above and below the diagonal.
6. The recommended format for rectangular matrices requires the use of NCOL and IFO = 9. The
number of columns in the matrix is NCOL. (The number of rows in all DMIK matrices is always the
ks-set size--the union of the k-set and the permanently SPC’d partition). The GJ term is used for the
column index. The CJ term is ignored.
7. If NCOL is not used for rectangular matrices, two different conventions are available:
• If IFO = 9, GJ and CJ will determine the sorted sequence, but will otherwise be ignored; a
rectangular matrix will be generated with the columns submitted being in the 1 to N positions,
where N is the number of logical entries submitted (not counting the header entry).
• If IFO = 2, the number of columns of the rectangular matrix will be equal to the index of the
highest numbered non-null column (in internal sort). Trailing null columns of the js-size matrix
will be truncated.
8. The matrix names must be unique among all DMIK.
9. TIN should be consistent with the number of decimal digits required to read the input data
adequately. For a single precision specification on a short word machine, the input will be truncated
after about eight decimal digits, even when more digits are present in a double field format. If more
digits are needed, a double precision specification should be used instead. However, not that a double
precision specification requires a “D” type exponent even for terms that do not need an exponent. For
example, unity may be input as 1.0 in single precision, but the longer form 1.0D0 is required for
double precision.
10. On long word machines, almost all matrix calculations are performed in single precision and, on short
word machines, in double precision. It is recommended that DMIK matrices also follow these
conventions for a balance of efficiency and reliability. The recommended value for TOUT is 0, which
instructs the program to inspect the system cell that measures the machine precision at run time and
sets the precision of the matrix to the same value. TOUT = 0 allows the same DMIK input to be used
on any machine. If TOUT is contrary to the machine type specified, unreliable results may occur.
11. If any DMIK entry is changed or added on restart then a complete reanalysis is performed. Therefore,
DMIK entry changes or additions are not recommended on restart.
Main Index
1594 DOPTPRM
Design Optimization Parameters
DOPTPRM Design Optimization Parameters
Overrides default values of parameters used in design optimization.
Format:
1 2 3 4 5 6 7 8 9 10
DOPTPRM PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3 PARAM4 VAL4
PARAM5 VAL5 -etc.-
Example:
DOPTPRM IPRINT 5 DESMAX 10
Describer Meaning
PARAMi Name of the design optimization parameter. Allowable names are given in Table 11.
(Character)
VALi Value of the parameter. (Real or Integer, see Table 11.)
Table 11 PARAMi Names and Descriptions
Name Description, Type, and Default Value
APRCOD Approximation method to be used. (Integer 1, 2, or 3; Default = 2)
1 Direct Linearization. APRCOD = 1 is recommended for shape,
topology and topography optimization problems.
2 Mixed Method based on response type
3 Convex Linearization
AUTOSE Flag to request an AESO job. AUTOSE = 1 activates an AESO creation run.
(Integer > 0; Default = 0)
CONV1 Relative criterion to detect convergence. If the relative change in objective between
two optimization cycles is less than CONV1, then optimization is terminated.
Topology optimization can be terminated with CONV1<5.00E-3 (Real > 0.0;
Default = 0.001).
CONV2 Absolute criterion to detect convergence. If the absolute change in objective
between two optimization cycles is less than CONV2, then optimization is
terminated. (Real > 0.0; Default = 1.0E-20)
CONVDV Relative convergence criterion on design variables. (Real > 0.0; Default = 0.001 for
non-topology; Default = 0.0001 for topology optimization)
CONVPR Relative convergence criterion on properties. (Real > 0.0; Default = 0.001)
Main Index
DOPTPRM 1595
Design Optimization Parameters
Table 11 PARAMi Names and Descriptions (continued)
Name Description, Type, and Default Value
CT Constraint tolerance. Constraint is considered active if current value is greater than
CT. (Real < 0.0; Default = -0.03)
CTMIN Constraint is considered violated if current value is greater than CTMIN.
(Real > 0.0; Default = 0.003)
DABOBJ Maximum absolute change in objective between two consecutive iterations to
indicate convergence at optimizer level. F0 is the initial objective function value.
(Real > 0.0; Default = MAX[0.001*ABS(F0), 0.0001])
DELB Relative finite difference move parameter. (Real > 0.0; Default = 0.0001; 0.001 for
fatigue responses)
DELOBJ Maximum relative change in objective between two consecutive iterations to
indicate convergence at optimizer level. (Real > 0.0; Default = 0.001)
DELP Fractional change allowed in each property during any optimization design cycle.
This provides constraints on property moves. (Real, 0.0<DELP<1.0, default=0.2)
DELX Fractional change allowed in each design variable during any optimization cycle.
(Real > 0.0; Default = .5 for sizing/shape/topometry optimization; Default = 0.2 for
topology and topography optimization)
DELXESL Fractional change allowed in each design variable during the ESLNRO loop. (Real
> 0.0, Default = 0.5)
DESMAX Maximum number of design cycles (not including FSD cycle) to be performed.
(Integer > 0; Default = 5 for sizing/shape optimization; Default = 30 for topology,
topography, and topometry optimization
DISCOD Discrete Processing Method: (Integer 0, 1, 2, 3 or 4; Default = 1)
0 No Discrete Optimization
1 Design of Experiments
2 Conservative Discrete Design
3 Round up to the nearest design variable
4 Round off to the nearest design variable
DISBEG Design cycle ID for discrete variable processing initiation. Discrete variable
processing analysis is carried out for every design cycle after DISBEG. (Integer > 0;
Default = 0=the last design cycle)
DPMAX Maximum fraction of change on designed property (Default = 0.5), used by Trust
Region Method.
DPMIN Minimum move limit imposed. (Real > 0.0; Default = 0.01)
DRATIO Theshold value that can be used to turn off an active AESO job. An AESO job is
terminated if the ratio of the size of a design model to that of an analysis model is
greater than DRATIO. (Real > 0.; Default = 0.1)
Main Index
1596 DOPTPRM
Design Optimization Parameters
Table 11 PARAMi Names and Descriptions (continued)
Name Description, Type, and Default Value
DSMXESL Maximum number of design cycles applied to the ESLNRO loop. (Integer > 0;
Default = 20)
DXMAX Maximum fraction of change on design variable (Default = 1.0), used by Trust
Region Method.
DXMIN Minimum design variable move limit. (Real > 0.0; Default = 0.05 for
sizing/shape/topometry optimization; Default = 1.0E-5 for topology and
topography optimization)
ETA1 ( 1 ) the cutting ratio 1 (Default = 0.01), used by Trust Region Method.
ETA2 ( 2 ) the cutting ratio 2 (Default = 0.25), used by Trust Region Method.
ETA3 ( 3 ) the cutting ratio 3 (Default = 0.7), used by Trust Region Method.
FSDALP Relaxation parameter applied in Fully Stressed Design. (Real, 0.0 < FSDALP < 1.0;
Default = 0.9)
FSDMAX Specifies the number of Fully Stressed Design Cycles that are to be performed.
(Integer; Default = 0)
GMAX Maximum constraint violation allowed at the converged optimum. (Real > 0.0;
Default = 0.005)
GSCAL Constraint normalization factor. See Remarks under the DSCREEN and
DCONSTR entries. (Real > 0.0; Default = 0.001)
IGMAX If IGMAX = 0, only gradients of active and violated constraints are calculated. If
IGMAX > 0, up to IGMAX gradients are calculated including active, violated, and
near active constraints. For many constraint problems, a reasonable value of
IGMAX = 2*NDV (number of design variables). A smaller IGMAX has a faster
performance of MSCADS. (Integer > 0; Default = 0)
IPRINT Print control during approximate optimization phase. Increasing values represent
increasing levels of optimizer information. (0 < Integer < 7; Default = 0)
0 No output (Default)
1 Internal optimization parameters, initial information, and results
2 Same, plus objective function and design variables at each
iterations
3 Same, plus constraint values and identification of critical
constraints
4 Same, plus gradients
5 Same, plus search direction
6 Same, plus scaling factors and miscellaneous search information
7 Same, plus one dimensional search information
ISCAL Design variables scaling. (Integer > -1; Default = 0) =-1 no scaling; > 0 scaling
Main Index
DOPTPRM 1597
Design Optimization Parameters
Table 11 PARAMi Names and Descriptions (continued)
Name Description, Type, and Default Value
METHOD Optimization Method: (Integer > 0; Default = 0)
0 Automatic selection for a better performance based on number of
design variables, number of constraints, number of active/violated
constraints and computer memory.
1 Modified Method of Feasible Directions for MSCADS.
2 Sequential Linear Programming for MSCADS
3 Sequential Quadratic Programming for MSCADS
4 SUMT method for MSCADS
IJK See Remark 3.
NASPR0 First cycle analysis output control. (Integer 0 or 1)
0 Print analysis output of first cycle. (Default)
1 Do NOT print analysis output of first cycle.
OBJMOD Objective function modification. (Integer; Default = 0)
0 Objective function will not be modified.
1 Objective function will be reset to 0.0. Subsequently, printed
objective function value represents the change of objective
function.
OPTCOD OPTCOD. See Remark 2. (Character; Default = Blank)
Blank Taken from system cell number 413
“MSCADS” MSCADS is used
“IPOPT” IPOPT is used
“External Optimizer SCA Service Identifier”
Must be defined in the CONNECT Service statement (see MSC
Nastran User Defined Services User’s Guide)
P1 Print control items specified for P2. (Integer > 0; Default = 0) Initial results are
always printed prior to the first approximate optimization. If an optimization task
is performed, final results are always printed for the final analysis unless
PARAM,SOFTEXIT,YES is specified. These two sets of print are not controllable.
n Print at every n-th design cycle.
Main Index
1598 DOPTPRM
Design Optimization Parameters
Table 11 PARAMi Names and Descriptions (continued)
Name Description, Type, and Default Value
P2 Items to be printed according to P1: (Integer; Default = 1)
0 No print.
1 Print objective and design variables. (Default for sizing/shape
optimization)
Print objective. (Default for topology optimization)
See P3 for the print of design variables for topology/topography
and tomography optimization.
2 See P3 for the print of designed properties for
topology/topography and tomography optimization.
4 Print constraints.
8 Print responses.
16 Print weight as a function of a material ID (note that this is not a
design quantity so that only inputs to the approximate design are
available).
n Sum of desired items. For example, P2 = 10 means print properties
and responses.
P2CALL Maximum number of retained constraints of all categories to be printed per
category. This single parameter can be used in place of the individual parameters
P2CBL, P2CC, P2CDDV, P2CM, P2CP and P2CR. If any of these six parameters
are non-zero, the P2CALL value is overridden for that constraint type. (Integer > 0;
default is to print all retained constraints.)
P2CBL Maximum number of constraints on beam library dimensions to be printed.
(Integer > 0; default is to print all beam library constraints.)
P2CC Maximum number of constraints on connectivity properties to be printed.
(Integer > 0; default is to print all connectivity property constraints.)
P2CDDV Maximum number of constraints on dependent design variables to be printed.
(Integer > 0; default is to print all dependent design variable constraints.)
P2CM Maximum number of constraints on material properties to be printed. (Integer > 0;
default is to print all material property constraints.)
P2CP Maximum number of constraints on element properties to be printed. (Integer > 0;
default is to print all element property constraints.)
P2CR Maximum number of constraints on design responses to be printed. (Integer > 0;
default is to print all retained design response constraints.)
Main Index
DOPTPRM 1599
Design Optimization Parameters
Table 11 PARAMi Names and Descriptions (continued)
Name Description, Type, and Default Value
P2RSET ID of a SET1 Bulk Data entry to identify the set of retained responses (DRESP1,
DRESP2 and/or DRESP3) to be printed. (Integer; Default is to print all responses
associated with printed constraints. If P2CR is > 0, the set associated P2RSET > 0
will be printed independent of the responses associated with the printed constraint.
If P2CR > 0 and PR2SET = -1, all retained responses will be printed.
P3 Conttrols prints of design variables and designed properties for topology,
topography and tomography optimization
0 No print
1 Print design variables and design properties for topology,
topography and tomography based on the value of P2
PENAL Penalty parameter used to transform an infeasible approximate optimization task to
a feasible one. Setting this parameter to; e.g., 2.0 may improve optimizer
performance when the starting design is infeasible. (Real; Default = 0.0)
PLVIOL Flag for handling of property limit violation. By default, the job will terminate with
a user fatal message if the property derived from design model (DVPRELi,
DVMRELi, DVCRELi) exceeds the property limits. Setting PLVIOL to a non-zero
number will cause the program to issue a user warning message by ignoring the
property limits violation and proceed with the analysis. (Integer; Default = 0)
PTOL Maximum tolerance on differences allowed between the property values on property
entries and the property values calculated from the design variable values on the
DESVAR entry (through DVPRELi relations). PTOL is provided to trap ill-posed
design models. (The minimum tolerance may be specified on user parameter
DPEPS. See Parameters) (Real > 0.0; Default = 1.0E+35)
STPSCL Scaling factor for shape finite difference step sizes, to be applied to all shape design
variables. (Real > 0.0; Default = 1.0)
TCHECK Topology Checkerboarding/minimum member size control option. (Integer > -1)
1 Filtering algorithm
2 Density constraint
0 No control
-1 Automatic selection of filtering or density constraint algorithm for
a better performance. (Default)
TDMIN Minimum diameter of members in topology optimization. This option is applied
on 2 and 3D elements only. (Real > 0.0)
Main Index
1600 DOPTPRM
Design Optimization Parameters
Table 11 PARAMi Names and Descriptions (continued)
Name Description, Type, and Default Value
TREGION Flag to invoke Trust Region method.
0 Don’t employ trust regions (Default)
1 Turn Trust Region on
UPDFAC1 Updating factor 1 (Default = 2.0), used by Trust Region Method.
UPDFAC2 Updating factor 2 (Default = 0.5), used by Trust Region Method.
Remarks:
1. Only one DOPTPRM entry is allowed in the Bulk Data Section. All defaults recommended.
2. OPTCOD specifies which optimization code to be used in SOL 200 and METHOD specifies which
optimization method to be used. The default is recommended.
3. METHOD = IJK enables a user selectable optimization strategy as documented in Vanderplaats, G.
N., ADS -- A Fortran Program for Automated Design Synthesis -- Version 1.10, NASA CR 177985,
1985. The default is recommended.
The I selects one of ten available strategy options:
0 None -- Go directly to the optimizer
1 Sequential unconstrained minimization using the exterior penalty function method
2 Sequential unconstrained minimization using the linear extended interior penalty
function method
3 Sequential unconstrained minimization using the quadratic extended interior penalty
function method
4 Sequential unconstrained minimization using the cubic extended interior penalty function
method
5 Augmented Lagrange multiplier method
6 Sequential linear programming
7 Method of centers
8 Sequential quadratic programming
9 Sequential convex programming
The J selects one of five available optimizer options:
Main Index
DOPTPRM 1601
Design Optimization Parameters
1 Fletcher-Reeves algorithm for unconstrained minimization
2 Davidon-Fletcher-Powell (DFP) variable metric method for unconstrained minimization
3 Broydon-Fletcher-Goldfarb-Shanno (BFGS) variable metric method for unconstrained
minimization
4 Method of feasible directions for constrained minimization
5 Modified method of feasible directions for constrained minimization
And K selects one of eight available one-dimensional search strategies:
1 Find the minimum of an unconstrained function using the Golden Section method
2 Find the minimum of an unconstrained function using the Golden Section method
followed by polynomial interpolation
3 Find the minimum of an unconstrained function by first finding bounds and then using
the Golden Section method followed by polynomial interpolation
4 Find the minimum of an unconstrained function by polynomial
interpolation/extrapolation without first finding bounds on the solution
5 Find the minimum of a constrained function using the Golden Section method
6 Find the minimum of a constrained function using the Golden Section method followed
by polynomial interpolation
7 Find the minimum of a constrained function by first finding bounds and then using
polynomial interpolation
8 Find the minimum of a constrained function by polynomial interpolation/extrapolation
without first finding bounds on the solution
Main Index
1602 DPHASE
Dynamic Load Phase Lead
DPHASE Dynamic Load Phase Lead
Defines the phase lead term in the equation of the dynamic loading function.
Format:
1 2 3 4 5 6 7 8 9 10
DPHASE SID P1 C1 TH1 P2 C2 TH2
Example:
DPHASE 4 21 6 2.1 8 6 7.2
Describer Meaning
SID Identification number of DPHASE entry. (Integer > 0)
Pi Grid, extra, or scalar point identification number. (Integer > 0)
Ci Component number. (Integers 1 through 6 for grid points; zero or blank for extra or
scalar points)
THi Phase lead in degrees. (Real)
Remarks:
1. One or two dynamic load phase lead terms may be defined on a single entry.
2. SID must be referenced on a RLOADi entry. Refer to the RLOAD1 or RLOAD2 entry for the
formulas that define how the phase lead is used.
3. A DAREA, LSEQ or static load entry should be used to define a load at Pi and Ci.
4. In superelement analysis, DPHASE entries may only be applied to loads on points in the residual
structure.
Main Index
DRESP1 1603
Design Sensitivity Response Quantities
DRESP1 Design Sensitivity Response Quantities
Defines a set of structural responses that is used in the design either as constraints or as an objective.
Format:
1 2 3 4 5 6 7 8 9 10
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATT1
ATT2 -etc.-
Example:
DRESP1 1 DX1 STRESS PROD 2 3 102
103
DRESP1 10 BMWW WMPID PSHELL 10 10
20 30
Describer Meaning
ID Unique entry identifier. (Integer > 0)
LABEL User-defined label. (Character, no default)
RTYPE Response type. See Table 12. (Character)
PTYPE Element flag (PTYPE = “ELEM”) or property entry name. Used with element type
responses (stress, strain, force, etc.) to identify the property type, since property
entry IDs are not unique across property types. (Character: “ELEM”, “PBAR”,
“PSHELL”, etc.)
REGION Region identifier for constraint screening. See Remark 10. for defaults. (Integer > 0)
ATTA, ATTB, Response attributes. See Table 12. (Integer > 0 or Real or blank)
ATTi
Main Index
1604 DRESP1
Design Sensitivity Response Quantities
Table 12 Design Sensitivity Response Attributes
Response Attributes
ATTB (Integer > 0 or
Response Type (RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
WEIGHT Row Number Column Number SEIDi or All or blank. See
(1 < ROW < 6) (1 < COL < 6) Remark 12.
See Remark 23.
VOLUME Blank Blank SEIDi or ALL or blank.
See Remark 12.
FRMASS Blank Blank Blank or Property ID
See Remarks 27. & 28. (PID). See Remark 36.
COMP Blank Blank Blank
See Remark 27.
EIGN Normal Modes Mode Approximation Code. Blank
Number. See Remark 32. See Remark 19.
CEIG Complex Eigenvalue Mode ALPHA or OMEGA Blank
Number. (Integer > 0) (Default = ALPHA)
FREQ Normal Modes Mode Approximation Code. Blank
Number. See Remark 19.
See Remarks 18. and 32.
LAMA Buckling Mode Number Approximation Code. Blank
See Remark 19.
DISP Displacement Component Blank or Mode Grid ID
Number
STRAIN Strain Item Code Blank or Mode Property ID (PID) or
Number Element ID (EID)
ESE Strain Energy Item Code Blank or Mode Property ID (PID) or
See Remark 20. Number Element ID (EID)
STRESS Stress Item Code Blank or Mode Property ID (PID) or
Number Element ID (EID)
FORCE Force Item Code Blank or Mode Property ID (PID) or
Number Element ID (EID)
FATIGUE Fatigue Item Code. ID of a FATIGUE case Property ID (PID) or
(pseudo-static) See Remark 42. control. Element ID (EID)
See Remark 38. See Remark 39.
Main Index
DRESP1 1605
Design Sensitivity Response Quantities
Table 12 Design Sensitivity Response Attributes
Response Attributes
ATTB (Integer > 0 or
Response Type (RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
FRFTG Fatigue Item Code. ID of a FATIGUE case Property ID (PID) or
(frequency response - See Remark 42. control. Element ID (EID)
random vibration fatigue) See Remark 39.
See Remark 38.
SPCFORCE SPC Force Component Blank Grid ID
CSTRAIN Strain Item Code LAMINA Number or Property ID (PID) or
See Remark 2. GPLYIDi Element ID (EID)
(Integer; Default = 1)
CSTRESS Stress Item Code LAMINA Number or Property ID (PID) or
See Remark 2. GPLYIDi Element ID (EID)
(Integer; Default = 1)
CFAILURE Failure Indices Item Code LAMINA Number or Property ID (PID) or
See Remark 2. GPLYIDi Element ID (EID)
(Integer; Default = 1)
CSTRAT Composite Strength Ratio LAMINA Number or Property ID (PID) or
See Remark 2. Item Code GPLYIDi Element ID (EID)
(Integer; Default = 1)
TOTSE Blank Blank or Mode SEIDi or All or blank. See
(Total Strain Energy) Number Remark 12.
See remark 45.
GPFORCE GPFORCE Component Blank Element ID
Code (1-6; see Remark 24.)
GPFORCP Grid Point (see Remark 25.) Blank Grid ID connected to
ATTA grid to specify
orientation.
ABSTRESS Arbitrary Beam Stress Item Blank Property ID (PID) or
Code (see Remark 29.) Element ID (EID)
FRDISP Displacement Component Frequency Value. Grid ID
(Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
PRES Acoustic Pressure Frequency Value. Grid ID
Component (= 1 or 7) (Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
Main Index
1606 DRESP1
Design Sensitivity Response Quantities
Table 12 Design Sensitivity Response Attributes
Response Attributes
ATTB (Integer > 0 or
Response Type (RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
FRVELO Velocity Component Frequency Value. Grid ID
(Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
FRACCL Acceleration Component Frequency Value. Grid ID
(Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
FRSPCF SPC Force Component Frequency Value. Grid ID
(Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
FRSTRE Stress Item Code Frequency Value. Property ID (PID) or
(Blank; Real > 0.0 or Element ID (EID)
Character)
See Remarks 15. and
20.
FRFORC Force Item Code Frequency Value. Property ID (PID) or
(Blank; Real > 0.0 or Element ID (EID)
Character)
See Remarks 15. and
20.
PSDDISP Displacement Component Frequency Value. Grid ID
(see Remarks 26. and 30.) (Blank; Real > 0.0 or
Character). See
Remarks 15. and 20.
PSDVELO Velocity Component (see Frequency Value Grid ID
Remarks 26. and 30.) (Blank; Real > 0.0 or
Character). See
Remarks 15. and 20.
PSDACCL Acceleration Component Frequency Value. Grid ID
(see Remarks 26. and 30.) (Blank; Real > 0.0 or
Character). See
Remarks 15. and 20.
Main Index
DRESP1 1607
Design Sensitivity Response Quantities
Table 12 Design Sensitivity Response Attributes
Response Attributes
ATTB (Integer > 0 or
Response Type (RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
RMSDISP Displacement Component RANDPS ID Grid ID
(see Remark 30.)
RMSVELO Velocity Component (see RANDPS ID Grid ID
Remark 30.)
RMSACCL Acceleration Component RANDPS ID Grid ID
(see Remark 30.)
ACPWR Blank Frequency Value. Blank
(Acoustic Power radiated (Blank; Real > 0.0 or
through a panel) Character)
See Remark 33. See Remarks 15. and
20.
ACINTS Blank Frequency Value. Grid ID of wetted surface.
(Acoustic Intensity) (Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
AFPRES Acoustic Pressure Frequency Value. Grid ID of AFPMID.
(Acoustic Pressure for Component (Blank; Real > 0.0 or
AFPM) (Integer = 1 or 7) Character)
See Remark 34. See Remarks 15. and
20.
AFINTS Component Code - Frequency Value. Grid ID of AFPMID.
(Acoustic Intensity for 0 - normal to AFPM, (Blank; Real > 0.0 or
AFPM) 1 - x-dir Character)
See Remark 34. 2 - y-dir See Remarks 15. and
3 - z-dir 20.
AFVELO Component Code - Frequency Value. Grid ID of AFPMID.
Velocity for AFPM) 11 - Real/Mag in x-dir (Blank; Real > 0.0 or
See Remark 34. 12 - Real/Mag in y-dir Character)
13 - Real/Mag in z-dir See Remarks 15. and
71 - Img/Ph in x-dir 20.
72 - Img/Ph in y-dir
73 - Img/Ph in z-dir
AFPWR Blank Frequency Value. Blank
(Acoustic Power for (Blank; Real > 0.0 or
AFPM) See Remark 34. Character) See
Remarks 15. and 20.
Main Index
1608 DRESP1
Design Sensitivity Response Quantities
Table 12 Design Sensitivity Response Attributes
Response Attributes
ATTB (Integer > 0 or
Response Type (RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
DYSTIFF Dynamic Stiffness Frequency Value. Grid ID
Component (Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
ERP ERP Item Code Frequency Value. Set3 ID or Blank
See Remarks 40. and 41. (Blank; Real > 0.0 or
Character)
See Remarks 15. and
20.
TDISP Displacement Component Time Value. (Blank; Grid ID
Real; or Character)
See Remarks 16. and
TVELO Velocity Component Time Value. (Blank; Grid ID
Real, or Character)
See Remarks 16. and
TACCL Acceleration Component Time Value. (Blank; Grid ID
Real, or Character)
See Remarks 16. and
TSPCF SPC Force Component Time Value. (Blank; Grid ID
Real, or Character)
See Remarks 16. and
TSTRE Stress Item Code Time Value. (Blank; Property ID (PID) or
Real, or Character) Element ID (EID)
See Remarks 16. and
TFORC Force Item Code Time Value. (Blank; Property ID (PID) or
Real, or Character) Element ID (EID)
See Remarks 16. and
STMONP1 Component Blank Blank
Structural See Remark 35.
MONPNT1
STMOND1 Component Blank Blank
Structural See Remark 35.
MONDSP1
MONPNT3 Component Blank Blank
See Remark 35.
Main Index
DRESP1 1609
Design Sensitivity Response Quantities
Table 12 Design Sensitivity Response Attributes
Response Attributes
ATTB (Integer > 0 or
Response Type (RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
AEMONP1 Component Blank Blank
Aerodynamic See Remark 35.
MONPNT1
AEMOND1 Component Blank Blank
Aerodynamic See Remark 35.
MONDSP1
TRIM AESTAT or AESURF entry Blank Blank
ID
STABDER AESTAT or AESURF entry Restraint Flag. Component
ID (Integer 0 or 1) See
Remark 13.
FLUTTER Blank Blank See Remark 14.
DIVERG Divergence Root Number Blank Mach No.
See remark 37.
WMPID MID SEID PID
See Remarks 43. and 44.
Remarks:
1. Stress, strain, force, fatigue and ERP item codes can be found in Item Codes. For stress or strain item
codes that have dual meanings, such as von Mises or maximum shear, the option specified in the Case
Control Section will be used; i.e., STRESS(VONM) or STRESS(MAXS).
2. RTYPE = “CSTRESS”, “CSTRAIN”, “CFAILURE”, and “CSTRAT” are used only with the
PCOMP/PCOMPG entry. “CSTRESS” and “CSTRAIN” item codes are described under Table 1
(Element Stress/Strain Item Codes) in Item Codes. “CFAILURE” and “CSTRAT” item codes are
described under Table 2 (Element Force Item Codes) in Item Codes. Only force item codes that refer
to failure indices of direct stress and interlaminar shear stress are valid.
The CFAILURE and CSTRAT response types requires the following specifications on the applicable
entries:
• Failure theory in the FT field on PCOMP/PCOMPG entry.
• Allowable bonding shear stress in the SB field on PCOMP/PCOMPG entry.
• Stress limits in the ST, SC, and SS fields on all MATi entries.
• When the PCOMPG is invoked, there is no default for the ATTB field.
3. ATTB can be used for responses of weight, composite laminae, dynamics, real and complex
eigenvalues, WMPID and stability derivatives. For eigenvector responses, such as DISP, the ATTB
identifies the mode of interest. For other responses, this field must be blank.
Main Index
1610 DRESP1
Design Sensitivity Response Quantities
4. All grids associated with a DRESP1 entry are considered to be in the same region for screening
purposes. Only up to NSTR displacement constraints (see DSCREEN entry) per group per load case
will be retained in the design optimization phase.
5. DRESP1 identification numbers must be unique with respect to DRESP2 identification numbers.
6. If PTYPE = “ELEM”, the ATTi correspond to element identification numbers.
7. If RTYPE = “DISP”, “SPCFORCE”, “GPFORCE”, “TDISP”, “TVELO”, “TACCL” or “TSPCF”,
multiple component numbers (any unique combination of the digits 1 through 6 with no embedded
blanks) may be specified on a single entry. Multiple response components may not be used on any
other response types.
8. If RTYPE = “FRDISP”, “FRVELO”, “FRACCL”, or “FRSPCF” only one component number may
be specified in the ATTA field. Numbers 1 through 6 correspond to real (or magnitude) components
and 7 through 12 imaginary (or phase) components. If more than one component for the same grid
is desired, then a separate entry is required.
9. Real/imaginary representation is the default for complex response types. Magnitude/phase
representation must be requested by the corresponding Case Control command; e.g.,
DlSP(PHASE) = ALL for FRDISP type responses.
10. REGION is used for constraint screening. The NSTR field on DSCREEN entries gives the
maximum number of constraints retained for each region per load case.
IF RTYPE = “WEIGHT”, “VOLUME”, “LAMA”, “EIGN”, “FREQ”, “CEIG”, “TOTSE”,
“RMSDISP”, “RMSVELO”, “RMSACCL”, no REGION identification number should be specified.
If the region field is left blank for a grid response, one region is created for each DRESP1 ID. If the
region field is left blank for an element response, one region is created for each property ID invoked.
Usually, the default value is appropriate.
If the REGION field is not blank, all the responses on this entry as well as all responses on other
DRESP1 entries that have the same RTYPE and REGION identification number will be grouped
into the same region.
11. REGION is valid only among the same type of responses. Responses of different types will never be
grouped into the same region, even if they are assigned the same REGION identification number by
the user.
12. If RTYPE = “WEIGHT”, “VOLUME”, or “TOTSE” field ATTi = “ALL” implies total
weight/volume/total strain energy of all superelements except external superelements, 0 implies
residual only and i implies SEID=i. Default=“ALL”. RTYPE=“TOTSE” is not supported for shape
optimization.
13. RTYPE = “STABDER” identifies a stability derivative response. ATTB is the restraint flag for the
stability derivative. ATTB = 0 means unrestrained, and ATTB = 1 means restrained. For example,
ATTA = 4000, ATTB = 0, and ATT1 = 3 reference the unrestrained Cz derivative for the AESTAT
(or AESURF) entry ID = 4000.
14. RTYPE = “FLUTTER” identifies a set of damping responses. The set is specified by ATTi:
ATT1 = Identification number of a SET1 entry that specifies a set of modes.
ATT2 = Identification number of an FLFACT entry that specifies a list of densities.
Main Index
DRESP1 1611
Design Sensitivity Response Quantities
ATT3 = Identification number of an FLFACT entry that specifies a list of Mach numbers.
ATT4 = Identification number of an FLFACT entry that specifies a list of velocities.
If the flutter analysis is type PKNL, it is necessary to put PKNL in the PTYPE field of this entry.
15. For RTYPE = “FRXXXX”, “PSDXXXX” , “PRES” and “ERP” a real value for ATTB specifies a
frequency value in cycles per unit time. If a real ATTB value is specified, then the responses are
evaluated at the closest excitation frequency. The default for ATTB is all excitation frequencies. See
Remark for additional ATTB options. The OFREQ Case Control command has no effect on the
selection of the frequencies.
16. For RTYPE = “TDISP”, “TVELO”, “TACCL”, “TSPCF”, “TFORC”, and “TSTRE”, ATTB
specifies a time value. If ATTB is specified, then the responses are evaluated at the closest time
selected by the OTIME command. The default for ATTB is all time steps selected by the OTIME
command.
17. Intermediate station responses on CBAR elements due to PLOAD1 and/or CBARAO entries may
not be defined on the DRESP1 entry.
18. RTYPE = “EIGN” refers to normal modes response in terms of eigenvalue (radian/time)**2 while
RTYPE = “FREQ” refers to normal modes response in terms of natural frequency or units of cycles
per unit time.
19. For RTYPE = LAMA, EIGN or FREQ, the response approximation used for optimization can be
individually selected using the ATTB field when APRCOD = 1 is being used.
For RTYPE = LAMA, ATTB = blank or 1 selects direct linearization, ATTB = 2 = inverse
linearization.
For RTYPE = EIGEN or FREQ, ATTB = blank = Rayleigh Quotient Approximation, = 1 = direct
linearization, = 2 = inverse approximation.
The default Rayleigh Quotient Approximation should be preferred in most cases.
Character input for ATTB is available for RTYPE of “FRXXXX”, “PSDXXXX”, “TXXXX”, “PRES”,
“ERP”, “ACPWR”, “ACINTS”, “AFPRES”, “AFINTS”, “AFVELO”, “AFPWR” and “DYSTIFF”.
The character input represents a mathematical function and the options for character input are SUM,
AVG, SSQ, RSS, MAX and MIN. The expression of mathematical function is shown as follows:
n
SUM X 1 X 2 Xn = Xi
i=1
n
AVG X 1 X 2 Xn = Xi n
i=1
n
2
SSQ X 1 X 2 Xn = Xi
i=1
Main Index
1612 DRESP1
Design Sensitivity Response Quantities
n
2
RSS X 1 X 2 Xn = Xi
i=1
MAX X 1 X 2 Xn = Maximum value among X i i=1 to n
MIN X 1 X 2 Xn = Minimum value among X i i=1 to n
where X i is the response for a forcing frequency or time step. For example
DRESP1,10,DX1,FRSTRE,ELEM,,3,AVG,10
yields a response which is equal to the average stress for element 10 across all forcing frequencies.
CAUTION! 1. If the ID of a DRESP1 with ATTB character input is referenced by a
DRESP2 using the "DRESP2" flag, the results of the mathematical function
are used to evaluate the DRESP2.
2. If the ID of a DRESP1 with ATTB character input is referenced by a
DRESP2 using the "DRESP1" flag, the individual values of the DRESP1 are
used to compute individual DRESP2 values and the mathematical function
is not used by the DRESP2.
20. Element strain energy item codes can be found under Table 7-12 in Item Codes. Only element strain
energy and element strain energy density can be referenced on a DRESP1 entry. RTYPE=”ESE” is
not supported for shape optimization.
21. For RTYPE=RMSDISP, RMSVELO, or RMSACCL the ATTB specifies the appropriate RANDPS
ID.
22. Input other than 1 or 7 of ATTA field, acoustic pressure component, for PRES response type will be
reset to 1 (if less than 7) or 7 (if greater than 6 and less than 13).
23. Design response weight is obtained from Grid Point Weight Generator for a reference point
GRDPNT (see parameter GRDPNT). If GRDPNT is either not defined, equal to zero, or not a
defined grid point, the reference point is taken as the origin of the basic coordinate system. Fields
ATTA and ATTB refer to the row and column numbers of the rigid body weight matrix, which is
partitioned as follows:
Main Index
DRESP1 1613
Design Sensitivity Response Quantities
W x W 12 W 13 W 14 W 15 W 16
W 21 W y W 23 W 24 W 25 W 26
W 31 W 32 W z W 34 W 35 W 36
W =
W 41 W 42 W 43 I x W 45 W 46
W 51 W 52 W 53 W 54 I y W 56
W 61 W 62 W 63 W 64 W 65 I z
66
The default values of ATTA and ATTB are 3, which specifies weight in the Z direction. Field ATT1
= “ALL” implies total weight of all superelements except external superelements. SEIDi refers to a
superelement identification number. SEIDi = “0” refers to the residual superelement. The default of
ATT1 is blank which is equivalent to “ALL”.
24. For RTYPE = GPFORCE, the PTYPE field is used to designate the GRID ID at which the force is
defined. Output that is produced using PARAM NOELOF > 0 is not supported for the DRESP1
entry.
25. For RTYPE = GPFORCP, the PTYPE field is blank. The grid point force is for the sum of all
elements from the GRID ID listed in ATTA to the GRID (orient ID) listed in ATTi. This response
corresponds to that produced with PARAM NOELP > 0. It is not necessary to set PARAM NOELP
> 0 to compute the GPFORCP response.
26. For RTYPE = PSDXXXX, the PTYPE field specifies the RANDPS ID.
T
27. RTYPE=COMP (compliance of structures = P u ) and FRMASS (mass fraction of topology
designed elements) entries are used for topology optimization or combined topology, sizing/shape
optimization.
28. RTYPE=FRMASS can be used for topology and topometry optimization. For topology, FRMASS, is
the mass divided by the mass calculated if all topology design variables are 1.0. FRMASS is calculated
for designed elements only. FRMASS = 1.0 if all design variables are 1.0. For topometry, the initial
FRMASS is defined as 1.0 for the initial design specified on the TOMVAR entries. For non-volume
elements like CELAS, an artificial mass = 1.0 is assumed for each element.
29. Response type ABSTRESS is for element type code of 238 (CBAR) and 239 (CBEAM) only.
30. If a PSDxxxx or RMSxxxx response is being applied with RANDPS Bulk Data entries that include
multiple subcases, the DESSUB or DESOBJ Case Control command that invokes the PSDxxxx or
RMSxxxx response must be in the first subcase used by the RANDPS entry.
31. Response types, ESE, TOTSE, GPFORCE and GPFORCP are not supported for shape
optimization.
32. For RTYPE=EIGN or FREQ, PTYPE field can be utilized to identify the source of the mode. Valid
options are ‘STRUC’ or ‘FLUID’. The default is ‘STRUC’.
33. For RTYPE=ACPWR, PTYPE field can be utilized to identify the panel name. The default is ‘total’
which covers the whole interface between structural and fluid field.
Main Index
1614 DRESP1
Design Sensitivity Response Quantities
34. For RTYPE=AFxxxx, PTYPE field can be utilized to specified the ID of Acoustic Field Point Mesh,
AFPM.
35. For monitor point responses (RTYPE = STMONP1, STMOND1, MONPNT3 AEMONP1 or
AEMOND1) the ATTA field specifies the components to be extracted. These can be any subset of
the integers 1 through 6 that appear on the monitor quantity with the NAME provided in the PTYPE
field. All of these responses can be invoked in a static aeroelastic (ANALYSIS=SAERO) subcase.
STMOND1 and MONPNT3 can be invoked from a static (ANALYSIS=STAT) subcase. The
responses are not available in a dynamic response or normal modes subcase. The response types have
the following meaning:
a. STMONP1 – A structural MONPNT1
b. STMOND1 – A structural MONDSP1
c. MONPNT3 – A MONPNT3
d. AEMONP1 – An aerodynamic MONPNT1
e. AEMOND1 – An aerodynamic MONDSP1
For all but the STMONP1, the response is the elastic monitor point value. For the STMONP1, it is
the elastic “minus” inertial “plus” elastic applied load value.
36. For RTYPE-FRMASS, if the PID in the ATTi field is not blank, the PTYPE field must specify the
type of property the PID references.
37. RTYPE=DIVERG is for subcases with ANALYSIS=DIVERG (aeroelastic static divergence). Only a
single Mach number can be specified for this RTYPE.
38. For RTYPE = FATIGUE (pseudo-static fatigue), PTYPE must be set to ELEM or PSOLID,
PSHELL, PBAR, PBEAM, or PWELD. For RTYPE = FRFTG (frequency response fatigue), PTYPE
must be set to ELEM or PSOLID o r PSHELL. ATTB is the FID of a FATIGUE case control and
must be the same FID for all RTYPEs of type FATIGUE or FRFTG. RTYPEs of type FATIGUE
and FRFTG cannot be mixed; either all are RTYPE=FATIGUE or all are RTYPE=FRFTG.
39. If a FATIGUE case control references a SET ID, then ATTB must reference one of the IDs referenced
by the SET. Design optimization using fatigue responses is currently limited to one fatigue analysis,
that is, one loading sequence. Multiple fatigue responses referencing different loading sequences, i.e.,
FATIGUE case control IDs, will result in an error.
40. For the ERP response, the PTYPE field must be ERPPNL.
41. If the ATT1 field is blank for the ERP response, all panels are invoked.
42. Fatigue Item Codes can be found in Fatigue Item Codes. Item codes that are available as design responses
are 4-9 and 12 for the element centroid or first node/layer/location and the comparable items for
ensuing nodes/layers/locations. The use of NODA on the FTGPARM entry is not supported.
43. For the WMPID (weight as a function of material and property ID), the following conventions apply:
a. If ATTA is specified, PTYPE and ATTi are optional.
b. If ATTA is blank, PTYPE and ATTi are required.
c. ATTB specifies the superelement with ATTB=0 indicating the residual, >0, indicates
superelement ATTB and ATTB = ALL or blank means all superelements)
Main Index
DRESP1 1615
Design Sensitivity Response Quantities
d. The ATTi fields designate the property ID's of interest. If ATTi is specified, the associated
property type (e.g., PSHELL) must be specified by the PTYPE input of field 5 on the DRESP1
entry.
e. If there is no ATTi, all material with MID=ATTA will be used to generate the response.
f. If there are multiple ATTi, a single scalar weight is calculated that is the sum of the all the
properties
g. Materials that are supported with this entry are: MAT1,MAT2, MAT3, MAT8, MAT9 and
MAT10
h. Properties that are supported are: PSHELL, PROD, PBEAM, PTUBE, PSHEAR, PBAR,
PSOLID, PBEND,PCOMP, PCOMPG, PBARL, PBEAML, PBRSECT and PBMSECT.
i. PARAM WTMASS is not applied to this response.
44. Certain restrictions apply for RTYPE=WMPID
a. The density of the material referenced on the ATTA field cannot also be designed using a
DVMRELx entry
b. The property referenced on the ATTI field cannot also be invoked by a TOMVAR entry.
c. The WMPID response is supported for topology optimization or for shape sizing optimization,
but not for both topology and shape sizing optimization.
45. RTYPE=TOTSE should not be used in conjunction with a TOPVAR entry that contains a STRESS
limit. RTYPE=COMP is recommended to provide an equivalent functionality.
Main Index
1616 DRESP2
Design Sensitivity Equation Response Quantities
DRESP2 Design Sensitivity Equation Response Quantities
Defines equation responses that are used in the design, either as constraints or as an objective.
Format:
1 2 3 4 5 6 7 8 9 10
DRESP2 ID LABEL EQID or REGION METHOD C1 C2 C3
FUNC
“DESVAR” DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7
DVID8 -etc.-
“DTABLE” LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7
LABL8 -etc.-
“DRESP1” NR1 NR2 NR3 NR4 NR5 NR6 NR7
NR8 -etc.-
“DNODE” G1 C1 G2 C2 G3 C3
G4 C4 etc.
“DVPREL1” DPIP1 DPIP2 DPIP3 DPIP4 DPIP5 DPIP6 DPIP7
DPIP8 DPIP9 -etc.-
“DVCREL1” DCIC1 DCIC2 DCIC3 DCIC4 DCIC5 DCIC6 DCIC7
DCIC8 DCIC9 -etc.-
“DVMREL1” DMIM1 DMIM2 DMIM3 DMIM4 DMIM5 DMIM6 DMIM7
DMIM8 DMIM9 -etc.-
“DVPREL2” DPI2P1 DPI2P2 DPI2P3 DPI2P4 DPI2P5 DPI2P6 DPI2P7
DPI2P8 DPI2P9 -etc.-
“DVCREL2” DCI2C1 DCI2C2 DCI2C3 DCI2C4 DCI2C5 DCI2C6 DCI2C7
DCI2C8 DCI2C9 -etc.-
“DVMREL2” DMI2M1 DMI2M2 DMI2M3 DMI2M4 DMI2M5 DMI2M6 DMI2M7
DMI2M8 DMI2M9 -etc.-
“DRESP2” NRR1 NRR2 NRR3 NRR4 NRR5 NRR6 NRR7
NRR8 -etc.-
“DVLREL1” DLIL1 DLIL2 DLIL3 DLIL4 DLIL5 DLIL6 DLIL7
DLIL8 -etc.-
Example:
DRESP2 1 LBUCK 5 3
DESVAR 101 3 4 5 1 205 209
201
DTABLE PI YM L
DRESP1 14 1 4 22 6 33 2
Main Index
DRESP2 1617
Design Sensitivity Equation Response Quantities
DNODE 14 1 4 1 22 3
2 1 43 1
DVPREL1 101 102
DVCREL1 201 202
DVMREL1 301
DVPREL2 401 402
DVCREL2 501
DVMREL2 601 602 603
DRESP2 50 51
Describer Meaning
ID Unique identification number. (Integer > 0)
LABEL User-defined label. (Character, no default)
EQID DEQATN entry identification number. (Integer > 0)
FUNC Function to be applied to the arguments. See Remark 8. (Character)
REGION Region identifier for constraint screening. See Remark 5. (Integer > 0)
METHOD When used with FUNC = BETA, METHOD = MIN indicates a minimization task
while MAX indicates a maximization task. (Default = MIN)
When used with FUNCT = MATCH, METHOD = LS indicated a least squares
while METHOD = BETA indicated minimization of the maximum difference.
(Default = LS)
Ci Constants used when FUNC = BETA or FUNC = MATCH in combination with
METHOD = BETA. See Remark 8. (Real; Defaults: C1 = 1.0., C2 = .005, and
C3=10.0)
“DESVAR” Flag indicating DESVAR entry identification numbers. (Character)
DVIDi DESVAR entry identification number. (Integer > 0)
“DTABLE” DTABLE flag. Indicates that the LABLs for the constants in a DTABLE or
DTABLE2 entry follow. This field may be omitted if there are no constants involved
in this relation. (Character)
LABLi Label for a constant on the DTABLE or DTABLE2 entry. (Character)
“DRESP1” Flag indicating DRESP1 entry identification numbers. (Character). See Remark 13.
NRk DRESP1 entry identification number. (Integer > 0)
“DNODE” Flag indicating grid point and component identification numbers. (Character)
Gm Identification number for any grid point in the model. (Integer > 0)
Cm Component number of grid point Gm. (1 < Integer < 3)
“DVPREL1” Flag indicating DVPREL1 entry identification number. (Character)
DPIPi DVPREL1 entry identification number. (Integer > 0)
Main Index
1618 DRESP2
Design Sensitivity Equation Response Quantities
Describer Meaning
“DVCREL1” Flag indicating DVCREL1 entry identification number. (Character)
DCICi DVCREL1 entry identification number. (Integer > 0)
“DVMREL1” Flag indicating DVREL1 entry identification number. (Character)
DMIMi DVMREL1 entry identification number. (Integer > 0)
“DVPREL2” Flag indicating DVPREL2 entry identification number. (Character)
DPI2Pi DVPREL2 entry identification number. (Integer > 0)
“DVCREL2” Flag indicating DVCREL2 entry identification number. (Character)
DCI2Ci DVCREL2 entry identification number. (Integer > 0)
“DVMREL2” Flag indicating DVMREL2 entry identification number. (Character)
DMI2Mi DVMREL2 entry identification number. (Integer > 0)
“DRESP2” Flag indicating other DRESP2 entry identification number. (Character). See
Remark 13.
NRRk DRESP2 entry identification number. (Integer > 0)
“DVLREL” Flag indicating DVLREL1 identification numbers. (Character)
DLILi DVLREL1 entry identification number. (Integer > 0)
Remarks:
1. DRESP2 entries may only reference DESVAR, DTABLE, DRESP1, DNODE, DVPREL1,
DVCREL1, DVMREL1, DVPREL2, DVCREL2, DVMREL2 and DVLREL1 entries. They may
also reference other DRESP2 entries. However, a DRESP2 entry cannot reference itself directly or
recursively.
2. a) If the referenced DRESP1 or DRESP2 entries span subcases, the DRSPAN Case Control
command is required to identify DRESP1/DRESP2 IDs for each subcase. DRESP2 entries that span
subcases must be invoked above the subcase level by DESGLB on DESOBJ commands.
b) Referenced DRESP entries that span superelements are supported automatically.
3. DRESP2 entries must have unique identification numbers with respect to DRESP1 entries.
4. The “DESVAR”, “DTABLE”, "DRESP1", “DNODE”, “DVPREL1”, “DVCREL1” and
“DVMREL1”, “DVPREL2”, “DVCREL2”, “DVMREL2”, “DRESP2” and DVLREL1 flags in field
2 must appear in the order given above. Any of these words, along with the identification numbers
associated with them, may be omitted if they are not involved in this DRESP2 relationship.
However, at least one of these ten types of arguments must exist.
5. The REGION field follows the same rules as for the DRESP1 entries. DRESP1 and DRESP2
responses will never be contained in the same region, even if they are assigned the same REGION
identification number. The default is to put all responses referenced by one DRESP2 entry in the
same region.
Main Index
DRESP2 1619
Design Sensitivity Equation Response Quantities
6. The variables identified by DVIDi, LABLj, NRk, the Gm, CMPM pairs, DPIPi, DCICm, DMIMn,
DPI2Po, DCI2Cp, DMI2Mq, and NRRu are assigned (in that order) to the variable names (x1, x2,
x3, etc.) specified in the left-hand side of the first equation on the DEQATN entry referenced by
EQID. In the example below,
DESVARs 101 and 3 are assigned to arguments A and B.
DTABLEs PI and YM are assigned to arguments C and D.
Grid 14, Component 1 is assigned to argument R.
DRESP2 1 LBUCK 5 3
DESVAR 101 3
DTABLE PI YM
DNODE 14 1
DEQATN 5 F1(A, B, C, D, R)=A+B*C-(D**3+10.0)+sin(C*R)
7. (Gm, Cm) can refer to any grid component and is no longer limited to a designed grid component.
8. The FUNC attributes can be used in place of the EQID and supports the functions shown in the
following table:
Function Description
SUM Sum of the arguments
SFMAX Minimization of compliance and maximization of frequency. See remark 14.
AVG Average of the arguments
SSQ Sum of the squares of the arguments
RSS Square root of the sum of the squares of the arguments
MAX The maximum value of the argument list
MIN The minimum value of the argument list
BETA Minimize the maximum response. See Remark 10.
MATCH Match analysis results with user specified values. See Remark 11.
When EQID has character input, the DEQATN entry is no longer needed. The functions are applied
to all arguments on the DRESP2 regardless of the type. See Remark of the DRESP1 entry for the
explanations of SUM, AVG, SSQ, RSS, MAX and MIN.
9. The number of arguments of a DEQATN can be more than the number of values defined on the
DRESP2 if the DRESP1s referenced have RTYPE with ‘FR’ or ‘PSD’ prefix. Arguments are still
positional. The extra arguments in the DEQATN must appear at the end of the argument list. The
discrepancy is resolved internally with the forcing frequency(ies) associated with DRESP1s. An
example is shown as follows:
DRESP1 10 FDISP1 FRDISP 1 10. 1001
DRESP1 20 FDISP2 FRDISP 1 20. 1001
Main Index
1620 DRESP2
Design Sensitivity Equation Response Quantities
DRESP2 30 AVGFD 100
DRESP1 10 20
DEQATN 100 AVG(D1,D2,F1,F2) = (D1/F1+D2/F2)*0.5
In the above example, the DEQATN has two more additional terms than have been defined on the
DRESP2. The first additional term is the forcing frequency (in hertz) of the first DRESP1 ID on the
DRESP2. The second additional term is the forcing frequency of second DRESP1 ID in the list.
When all DRESP1s involved have the same frequency, the user is not required to name all the
additional terms in the argument list of DEQATN.
10. FUNC = BETA facilitates a design task where the objective is to minimize the maximum response.
Only DRESP1 entries can be invoked by DRESP2 and the DRESP’s cannot span subcases. The
BETA function creates the following design task:
Minimize = C 1 X
r j – X
Subject to g = ------------------- 0
C3
where is determined from
C 2 = r jmax – X C 3
User input parameters C 1 C 2 C 3 therefore have the following meaning:
C 1 (Default = 1.0) weights the spawned design variable, X , to create the objective. Since X starts
at 1.0, C 1 is the initial objective.
C 2 sets the initial value of the maximum constraint created by this process. The default values of
0.005 is equal to DOPTPRM parameter GMAX.
C 3 (Default = 10.0) is an offset value to avoid dividing by zero when creating constraints.
11. FUNC = MATCH creates a response from the difference between analysis results, r j , that are
T
associated with DRESP1s and target values, r j , that are input using DTABLE data. Only DRESP1
entries and DTABLE entries can be invoked by the DRESP2 entry.
When METHOD = LS, a least square minimization is performed where the response is
m 2
r – r T
j j
r 2 = ---------------
T
j = 1
rj
When METHOD = BETA, the design task becomes one of minimizing an objective that is the
maximum normalized difference between the analysis and target values
Main Index
DRESP2 1621
Design Sensitivity Equation Response Quantities
T
rj – rj
---------------
T
rj
in the same manner as outlined in Remark 10.
12. With FUNC=MATCH, if the DTABLE LABLj invokes an integer VALUi on the DTABLE entry,
the integer points to a TABLEDi entry that provides tabular input as a function of frequency or time.
This is used in conjunction with a single DRESP1 NRk that provides a response across a range of
frequencies or times (i.e., RTYPE=FRxxxx, PSDxxxx, ACxxxx or Txxxx). When the TABLEDi
option is invoked, the response can only be constrained, it cannot be the objective. This further
implies that FUNC=MATCH, METHOD=BETA is not supported with TABLEDi.
13. If the mathematical function from a DRESP1 that has character input in the ATTB field (see remark
20 of the DRESP1) is to be used in the DRESP2 evaluation, the DRESP1 must be referenced under
the “DRESP2” flag, not the “DRESP1” flag. If the “DRESP1” flag is used in this situation, it will
result in a DRESP2 being evaluated for each of the individual values that contribute to the
mathematical function.
14. The function SFMAX requires n+1 DRESP1 IDs. The first ‘n’ IDs correspond to compliance
constraints for the first ‘n’ static subcases. The final ID refers to a DRESP1 with RTYPE=FREQ and
mode=1. The function minimizes the sum of the compliance constraints while maximizing the
fundamental frequency.
Main Index
1622 DRESP3
Design Sensitivity Response using user-supplied routine(s)
DRESP3 Design Sensitivity Response using user-supplied routine(s)
Defines an external response using user-supplied routine(s).
Format:
1 2 3 4 5 6 7 8 9 10
DRESP3 ID LABEL GROUP TYPE REGION
“DESVAR” DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7
DVID8 etc.
“DTABLE” LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7
LABL8 etc.
“DRESP1” NR1 NR2 NR3 NR4 NR5 NR6 NR7
NR8 etc.
“DNODE” G1 C1 G2 C2 G3 C3
G4 C4 etc.
“DVPREL1” DPIP1 DPIP2 DPIP3 DPIP4 DPIP5 DPIP6 DPIP7
DPIP8 DPIP9 etc.
“DVCREL1” DCIC1 DCIC2 DCIC3 DCIC4 DCIC5 DCIC6 DCIC7
DCIC8 DCIC9 -etc.-
“DVMREL1” DMIM1 DMIM2 DMIM3 DMIM4 DMIM5 DMIM6 DMIM7
DMIM8 DMIM9 -etc.-
“DVPREL2 DPI2P1 DPI2P2 DPI2P3 DPI2P4 DPI2P5 DPI2P6 DPI2P7
DPI2P8 DPI2P9 -etc.-
‘DCREL2” DCI2C1 DCI2C2 DCI2C3 DCI2C4 DCI2C5 DCI2C6 DCI2C7
DCI2C8 DCI2C9 -etc.-
“DVMREL2” DMI2M1 DMI2M2 DMI2M3 DMI2M4 DMI2M5 DMI2M6 DMI2M7
DMI2M8 DMI2M9 -etc.-
“DRESP2” NRR1 NRR2 NRR3 NRR4 NRR5 NRR6 NRR7
NRR8 -etc.-
DVLREL1 DLIL1 DLIL2 DLIL3 DLIL4 DLIL5 DLIL6 DLIL7
DLIL8 DLIL9 -etc.-
“USRDATA” String
-etc.-
Example:
DRESP3 1 LBUCK TAILWNG BUCK
DESVAR 101 3 4 5 1 205 209
201
Main Index
DRESP3 1623
Design Sensitivity Response using user-supplied routine(s)
DTABLE PI YM L
DRESP1 14 1 4 22 6 33 2
DNODE 14 1 4 1 22 3
2 1 43 1
DVPREL1 101 102
DVCREL1 201 202
DVMREL1 301
DVPREL2 401 402
DVCREL2 501
DVMREL2 601 602 603
DRESP2 50 51
USRDATA Constants: 12345.6 789.0 99.
Describer Meaning
ID Unique identification number. (Integer > 0)
LABEL User-defined label. (Character, no default)
GROUP Group name the external response type belongs to (Character). See Remark 2.
TYPE External response type (Character). See Remark 3.
“DESVAR” Flag indicating DESVAR entry identification numbers. (Character)
DVIDi DESVAR entry identification number. (Integer > 0)
“DTABLE” DTABLE flag. Indicates that the LABLs for the constants in a DTABLE or
DTABLE2 entry follow. This field may be omitted if there are no constants involved
in this relation. (Character)
LABLi Label for a constant on the DTABLE or DTABLE2 entry. (Character)
“DRESP1” Flag indicating DRESP1 entry identification numbers. (Character)
NRk DRESP1 entry identification number. (Integer > 0)
“DNODE” Flag signifying that the following fields are grid points.
Gm Grid point identification number. (Integer > 0)
Cm Degree-of-freedom number of grid point Gm. (1 < Integer < 3)
“DVPREL1” Flag indicating DVPREL1 entry identification number. (Character)
DPIPi DVPREL1 entry identification number. (Integer > 0)
“DVCREL1” Flag indicating DVCREL1 entry identification number. (Character)
DCICi DVCREL1 entry identification number. (Integer > 0)
“DVMREL1” Flag indicating DVMREL1 entry identification number. (Character)
DMIMi DVMREL1 entry identification number. (Integer > 0)
“DVPREL2” Flag indicating DVPREL2 entry identification number. (Character)
Main Index
1624 DRESP3
Design Sensitivity Response using user-supplied routine(s)
Describer Meaning
DPI2Pi DVPREL2 entry identification number. (Integer > 0)
“DVCREL2” Flag indicating DVCREL2 entry identification number. (Character)
DCI2Ci DVCREL2 entry identification number. (Integer > 0)
“DVMREL2” Flag indicating DVMREL2 entry identification number. (Character)
DMI2Mi DVMREL2 entry identification number (Integer > 0)
“DRESP2” Flag indicating other DRESP2 entry identification number. (Character)
NRRk DRESP2 entry identification number. (Integer > 0)
“DVLREL1” Flag indicating DVLREL1 identification number (character)
DLILi DVLREL1 entry identification number (integer)
“USRDATA” Flag indicating user input data (Character). See Remark 8.
Remarks:
1. DRESP3 entries may reference DESVAR, DTABLE, DRESP1, DNODE, DVPREL1, DVCREL1,
DVMREL1, DVPREL2, DVCREL2, DVMREL2, DRESP2 and DVLREL1entries. However, a
DRESP3 entry cannot reference another DRESP3 entry.
2. The group name must be referenced by an FMS CONNECT entry.
3. Multiple types of external responses can be defined in one group. Each type name identifies a specific
external response evaluated in the user-supplied routines. See Building and Using the Sample Programs
MSC Nastran Utilities Guide for a discussion of how to incorporate external responses.
4. a) If referenced DRESP1 or DRESP2 entries span subcases, the DRSPAN Case Control command is
required to identify the DRESP1/DRESP2 IDs for each subcase. DRESP3 entries that span subcases
must be invoked above the subcase level by DESGLB or DESOBJ commands.
b) Referenced DRESP1/DRESP2 entries that span superelements are supported automatically.
5. DRESP3 entries must have unique identification numbers with respect to DRESP2 and DRESP1
entries.
6. The “DESVAR”, “DTABLE”, “DNODE”, “DVPREL1”, “DVCREL1” and “DVMREL1”,
“DVPREL2”, DVCREL2”, “DVMREL2”, “DRESP2”, “DVLREL1” and “USRDATA” keywords
on the continuation entries must appear in the order given above. Any of these words, along with the
subsequent data associated with them, may be omitted if they are not involved in this DRESP3
relationship. However, at least one of these types of arguments must exist.
7. The REGION field follows the same rules as for the DRESP1 entries. DRESP1 and DRESP3
responses will never be contained in the same region, even if they are assigned the same REGION
identification number. The default is to put all responses referenced by one DRESP3 entry in the
same region.
8. The data in the USRDATA field is character string based. It provides a convenient way to pass
constants to the external response server routines. The maximum number of characters allowed is
32000.
Main Index
DSCREEN 1625
Design Constraint Screening Data
DSCREEN Design Constraint Screening Data
Defines screening data for constraint deletion.
Format:
1 2 3 4 5 6 7 8 9 10
DSCREEN RTYPE TRS NSTR
Example:
DSCREEN STRESS -0.7 2
Describer Meaning
RTYPE Response type (or ALL, See Remark 9.) for which the screening criteria apply.
(Character)
TRS Truncation threshold. (Real; Default = -0.5)
NSTR Maximum number of constraints to be retained per region per load case. See Remark
3. (Integer > 0; Default = 20)
Remarks:
1. Grid responses associated with one particular load case are grouped by the specification of DRESP1
entries. From each group, a maximum of NSTR constraints are retained per load case.
2. Element responses are grouped by the property; i.e., all element responses for one particular load case
belonging to the set of PIDs specified under ATTi on a DRESPi entry are regarded as belonging to
the same region. In superelement sensitivity analysis, if the property (PID) is defined in more than
one superelement, then separate regions are defined. A particular stress constraint specification may
be applied to many elements in a region generating many stress constraints, but only up to NSTR
constraints per load case will be retained.
3. For aeroelastic responses, that is RTYPE = “TRIM”, “STABDER”, and “FLUTTER”, the NSTR
limit is applied to all DRESP1 IDs that are the same RTYPE and have the same REGION specified.
4. For responses that are not related to grids or elements, that is RTYPE = “WEIGHT”, “VOLUME”,
“EIGN”, “FREQ”, “LAMA”, CEIG”, FRMASS, COMP, and TOTSE”, NSTR is not used. TRS is
still applicable.
5. The RTYPE field is set to EQUA if constraints that are associated with DRESP2 entries are to be
screened. The RTYPE field is set to DRESP3 if constraints that are associated with DRESP3 entries
are to be screened. If the REGION field on the DRESP2 or DRESP3 is blank, one region is
established for each DRESP2/DRESP3 entry.
6. If a certain type of constraint exists but no corresponding DSCREEN entry is specified, all the
screening criteria used for this type of constraint will be furnished by the default values.
7. Constraints can be retained only if they are greater than TRS. See the Remarks under the DCONSTR
entry for a definition of constraint value.
Main Index
1626 DSCREEN
Design Constraint Screening Data
8. Constraint screening is applied to each superelement.
9. RTYPE=ALL specifies that the specified TRS and NSTR applies to all response types and other
DSCREEN entries are ignored.
Main Index
DTABLE 1627
Table Constants
DTABLE Table Constants
Defines a table of real constants that are used in equations (see DEQATN entry).
Format:
1 2 3 4 5 6 7 8 9 10
DTABLE LABL1 VALU1 LABL2 VALU2 LABL3 VALU3 LABL4 VALU4
LABL5 VALU5 LABL6 VALU6 LABL7 VALU7 LABL8 VALU8
-etc.-
Example:
DTABLE PI 3.142 H 10.1 E 1.0E6
G 5.5E5 B 100.
Describer Meaning
LABLi Label for the constant. (Character)
VALUi Value of the constant or TABLEDx ID. (Real or Integer, respectively)
Remarks:
1. Multiple DTABLE entries may be specified in the Bulk Data Section.
2. LABLi are referenced by the LABj on the DRESP2, DRESP3, DVCREL2, DVMREL2, or
DVPREL2 entries.
3. Trailing blank fields are permitted at the end of each line of LABLi/VALUi pairs, but intermediate
blanks are not. (See the example above for permitted trailing blanks.)
4. For PART SE, if LABLi is referenced on SEDRSP2 and/or SEDRSP3, DTABLE entries must be
placed in a PART SE where companion design model entries, such as DESVAR, DRESP1 and etc,
are available.
5. If the VALUi is an integer, this points to the ID of a TABLEDx Bulk Data entry that lists the
constants as a function of frequency or time. See Remark 12. on the DRESP2 entry.
6. LABLi must be unique across all DTABLE and DTABLE2 entries.
Main Index
1628 DTABLE2
Table Constants
DTABLE2 Table Constants
Defines real constants from a field of property, material or connections bulk data entries which then can be
invoked by a DVxREL2, DRESP2, or DRESP3 entry.
Format:
1 2 3 4 5 6 7 8 9 10
DTABLE2 LABL1 PNAME1 PID1 FNAME1 LABL2 PNAME2 PID2 FNAME2
LABL3 PNAME3 PID3 FNAME3
Example:
DTABLE2 PTHK10 PSHELL 10 T MATIE MAT1 38 E
CBARX1 CBAR 3888 X1
Describer Meaning
LABLi Label for the constant. (Character)
PNAMEi Property, material or connection bulk data entry name. (Character)
PIDi ID of PNAMEi entry. (Integer > 0)
FNAMEi Field name of PNAMEi. (Character)
Remarks:
1. LABLi on DTABLE2 and DTABLE must be unique.
2. LABLi on DTABLE2 can be referenced under DTABLE flag of DVxREL2 (where x=P, M or
C)/DRESP2/DRESP3.
3. Values for the FNAMEi field of the PNAMEi Bulk Data entry with the ID of PIDi are taken from
analysis model before updating of analysis values with the designed value. If the updated value is
desired, use the DVxREL2 flag on DRESP2 or DRESP3 entries instead.
4. FNAMEi must be the same as the character string that appears on the PNAMEi Bulk Data entry.
5. DTABLE2 must be utilized along with ‘NASTRAN SYSTEM(444)=1’ in input file or ‘sys444=1’
during job submittal.
Main Index
DTI 1629
Direct Table Input
DTI Direct Table Input
Defines table data blocks.
Format:
1 2 3 4 5 6 7 8 9 10
DTI NAME “0" T1 T2 T3 T4 T5 T6
V01 V02 -etc.-
DTI NAME IREC V1 V2 V3 V4 V5 V6
V7 V8 V9 V10 -etc.- “ENDREC”
Example: (The first logical entry is the header entry.)
DTI XXX 0 3 4 4096 1 0
1.2 2.3
DTI XXX 1 2.0 -6 ABC 6.000 -1 2
4 -6.2 2.9 1 DEF -1 ENDREC
Describer Meaning
NAME Any character string that will be used in the DMAP sequence to reference the data
block. See Remark 1. (Character; the first character must be alphabetic.)
Ti Trailer values. (Integer > 0; Default = 32767)
IREC Record number. (Integer > 1)
V0i, Vi Value. (Integer, Real, Character or blank)
“ENDREC” Flags the end of the string of values (V0i or Vi) that constitute record IREC.
(Character)
Remarks:
1. The user defines the data block and therefore must write a DMAP (or ALTER a solution sequence),
which includes the DTIIN modules, in order to use the DTI feature. See the MSC Nastran DMAP
Programmer’s Guide. All of the rules governing the use of data blocks in DMAP sequences apply.
2. All fields following ENDREC must be blank.
3. The entry using IREC = 0 is called the header entry and is an optional entry. The values T1 through
T6 go to a special record called the trailer. Other values on the optional continuation go to the header
record. If the header entry or the trailer is not specified, T1 through T6 = 32767. On this entry,
“ENDREC” may be used only if there is at least one continuation.
4. In addition to the optional header entry, there must be one logical entry for each record in the table.
Null records require no entries.
Main Index
1630 DTI
Direct Table Input
5. “ENDREC” is used to input blank values at the end of a record. If “ENDREC” is not specified, the
string for a record ends with the last nonblank field.
6. The maximum number of DMI and DTI data blocks is 1000.
7. If Ti is not an integer, a machine-dependent error will be issued that may be difficult to interpret.
8. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
DTI,ESTDATA 1631
Superelement Estimation Data Overrides
DTI,ESTDATA Superelement Estimation Data Overrides
Provides override data for time and space estimation for superelement processing operations.
Format:
1 2 3 4 5 6 7 8 9 10
DTI ESTDATA “0"
kd1 vd1 kd2 vd2 -etc.-
The next entries are repeated for any superelement for which estimate data overrides are desired. IREC must
be incremented by 1.
DTI ESTDATA IREC SEFLAG SEID k1 v1 k2 v2
k3 v3 -etc.-
Example:
DTI ESTDATA 0
NOMASS -1
DTI ESTDATA 1 SE 10 C1 5.5 C3 4.5
C7 7.3
Describer Meaning
kdi Keyword for estimation parameter. (Character from Table 9-9.)
vdi Value assigned to the estimation parameter kdi. (The type given in Table 9-9.)
IREC Record number beginning with 1. (Integer > 0)
SEFLAG SEFLAG = “SE” or “SEID” indicates the next field containing a superelement
identification number. (Character)
SEID Superelement identification number. (Integer > 0)
ki Keyword for override of estimation parameter for indicated superelement. (Character
from Table 9-9.)
vi Value for keyword ki. (Type depends on ki as shown in the Table 9-9.)
Main Index
1632 DTI,ESTDATA
Superelement Estimation Data Overrides
Table 9-9 DTI,ESTDATA Input Parameter Descriptions
Input Parameters
Default Math
Keyword Type Value Symbol Meaning and Comments
CRMS* Real -1.0 C Number of active columns in [Koo].
FCRMS* Real 0.10 If FCRMS < 0.0, FCRMS is used (c/o).
C1 Real 6.0 c1 Average number of degrees-of-freedom per grid
point in o-set.
C3 Real 8.0 c3 Average number of connections per grid point.
C4 Real 0.15 c4 I/O time (seconds) per block transferred.
C5 Real 6.0 c5 Average number of effective degrees-of-freedom
per grid point in a-set.
C6 Real 1.2 c6 Total CPU factor.
C7 Real 6.0 c7 Number of equivalent KGG data blocks for space
estimation.
WF Real -1.0 W If WF < 0.0 then use available working storage in
units of single-precision words.
NOMASS Integer 1 If NOMASS 1 then exclude mass terms from
estimates.
TSEX Real 0.5 (min) Threshold limit for CPU.
SSEX Real 50.0 Threshold limit for space.
(blocks)
TWALLX Real 5.0 (min) Threshold limit for wall time.
BUFSIZ Integer Machine B Buffsize. See The NASTRAN Statement (Optional) in the
Buffsize MSC Nastran Reference Guide.
ML Real Machine M Arithmetic time for the multiply/add loop. See the
Loop Time SOL 700 Explicit Nonlinear User’s Guide.
CONIO Integer Machine l/O count/CPU equivalence
I/O ratio
PREC Integer 1 or 2 Machine Word Length (1 = long, 2 = short). See
The NASTRAN Statement (Optional) in the MSC Nastran
Reference Guide.
NLOADS Integer 1 NL Number of loading conditions
SETYPE Character “T” Superelement type (T = Tip)
CMAX Real -1.0 Cmax Maximum bandwidth
Main Index
DTI,ESTDATA 1633
Superelement Estimation Data Overrides
Parameters Obtained from SEMAP
NGI Number of interior grid points.
NPE Number of exterior grid points.
NS Number of scalar points
NE Number of elements.
Derived Parameters
O = C1 + NGI Size of o-set.
A = C5 NPE – NS + NS Size of a-set.
T = BUFFSIZE/PREC Number of matrix terms in a buffer.
Estimation Equations
For each superelement, estimates of CPU time and disk space are made using the following equations.
Table 9-10 Equations Used for CPU Time and Disk Space Estimate
Printout Math
Symbol Symbol Equations
2
TD T1 T1 = 1 2 M O C
TFBS T2 T2 = 2 M C O a
2
TMAA T3 T 3 = M O a (set to 0.0 if NOMASS +1)
TSE TSE T SE = C 6 T 1 + T 2 + T 3
PREC
SLOO S1 S 1 = O C ---------------
b
PREC
SGO S2 S 2 = O a ---------------
B
PREC
SKGG S3 S 3 = 36 NG i + NG e – NS c 3 + 1.0 ---------------
B
Main Index
1634 DTI,ESTDATA
Superelement Estimation Data Overrides
Table 9-10 Equations Used for CPU Time and Disk Space Estimate
Printout Math
Symbol Symbol Equations
SSE SSE S SE = S 1 + S 2 + c 7 S 3
PREC
PASSES p FBS passes = p = a O ---------------
WF
BKSTRN BT Blocks Transferred = BT = 2 p S 1 + S 2 + p S 2 . (Last term
omitted if NOMASS +1 )
TWALL TW Wall Time = T W = T SE + c 4 BT
Remarks:
1. In the superelement solution sequences, this data is stored automatically.
2. The header record continuation entries are optional if no global override data is to be specified. In
this case, the complete header entry is optional.
• Active column data can come from one of several places. The value for CRMS is determined as
follows:
• RMS from the entry when IREC > 0 and field 4 is “SE”.
• RMS from entries with IREC = 0.
• Computed bandwidth when PARAM,OLDSEQ is specified.
• If FCRMS is specified when IREC > 0 and field 4 is “SE”, then CRMS = FCRMS O .
• If FCRMS is specified when IREC = 0, then CRMS = FCRMS O .
• CRMS = 0.1 O .
3. If CMAX is not specified, then it is defaulted to CRMS.
4. In the example above, mass terms are excluded for all superelements and new values are given for
parameters C1, C3, and C7 for Superelement 10 only.
5. The estimates for TSEX, SSEX, and TWALLX are not printed unless at least one estimate exceeds
the threshold.
Main Index
DTI,INDTA 1635
Stress, Strain and/or Force Sort/Filter Item Code Override
DTI,INDTA Stress, Strain and/or Force Sort/Filter Item Code Override
Specifies or overrides default item codes for the sorting and filtering of element stresses, strains, and forces.
Format:
1 2 3 4 5 6 7 8 9 10
DTI INDTA “0"
To specify/override items for a sort of stress quantities:
DTI INDTA “1" B1 C1 B2 C2 “ENDREC”
To specify/override items for a sort of force quantities:
DTI INDTA “2" B1 C1 B2 C2 “ENDREC”
Examples:
DTI INDTA 0
To specify/override items for a sort of stress quantities:
DTI INDTA 1 64 18 75 18 ENDREC
To specify/override items for a sort of force quantities:
DTI INDTA 2 34 2 2 4 ENDREC
Describer Meaning
Bi Element type identification number. See the table in Item Codes for allowable values.
(Integer > 0)
Ci Item code identification number for the stress, strain, or force quantity on which the
sort or filter is to be performed. See the table in the Item Codes for allowable values.
(Integer)
Remarks:
1. This table is recognized only in SOLs 101, 103, 105, 106, 108, 109, 111, 112, 114, 115, 144, 153,
and for stress, strain or force quantities only. One or more of the user parameters S1, S1G, or S1M
must be specified with a value greater then or equal to zero in order to request sorting and/or filtering.
See user parameter S1 in Parameters. In order to sort force or strain quantities, a DMAP Alter is
required.
Main Index
1636 DTI,INDTA
Stress, Strain and/or Force Sort/Filter Item Code Override
2. If the Ci value is -1, the element type will be suppressed on the output file. An example of this feature
could be as follows: If an element type is to be sorted on two different values and output twice, this
can be accomplished by two calls to the STRSORT module with two unique DTI tables. However,
other element types will be printed twice. This additional print can be suppressed by setting their sort
codes to -1.
3. Table 13 lists the elements currently that are sortable. In addition, the element type identification
number, the default stress output quantity, and the associated stress code identification numbers are
provided. If this entry is not specified, then the stresses are sorted based on the default quantity given
in Table 13.
The following should be noted:
a. The element type identification number is used internally by the program to differentiate element
types.
b. The stress code identification number is merely the word number in the standard printed output
for the stress quantity of interest. For example, the thirteenth word of stress output for the
CHEXA element is the octahedral shear stress. For this element type, the element identification
number and the grid point ID each count as a separate word. Stress codes for the elements are
tabulated in Item Codes.
c. By default, stress sorting for the membrane and plate elements will be performed on the
Hencky-von Mises stress. For maximum shear stress, the STRESS (MAXS) Case Control
command should be specified.
Main Index
DTI,INDTA 1637
Stress, Strain and/or Force Sort/Filter Item Code Override
Table 13 Sortable Elements
Default Stress Output
Quantity and Identification Number
Element Type ID Stress Code ID
Element Number Quantity Number
CBAR 34 Maximum stress at end B 14
CBEAM 2 Maximum stress at end B 108
CBEND 69 Maximum stress at end B 20
CONROD 10 Axial stress 2
CELAS1 11 Stress 2
CELAS2 12 Stress 2
CELAS3 13 Stress 2
CHEXA 67 Hencky-von Mises or Octahedral stress 13
CQUAD4 33 Maximum shear or Hencky-von Mises 17
stress at Z2
CQUAD4* 144 Maximum shear or Hencky-von Mises 19
stress at Z2
CQUAD8 64 Maximum shear or Hencky-von Mises 19
stress at Z2
CQUADR 82 Maximum shear or Hencky-von Mises 19
stress at Z2
CPENTA 68 Octahedral stress 13
CROD 1 Axial stress 2
CSHEAR 4 No default ---
CTETRA 39 No default ---
CTRIA3 74 Maximum shear or Hencky-von Mises 17
stress at Z2
CTRIA6 75 Maximum shear or Hencky-von Mises 19
stress at Z2
CTRIAR 70 Maximum shear or Hencky-von Mises 19
stress at Z2
CTRIAX6 53 No default ---
CTUBE 3 Axial stress 2
*CORNER output
Main Index
1638 DTI,SETREE
Superelement Tree Definition
DTI,SETREE Superelement Tree Definition
Defines a superelement tree that determines the superelement processing order.
Format:
1 2 3 4 5 6 7 8 9 10
DTI SETREE “1” SEUP1 SEDOWN1 SEUP2 SEDOWN2 SEUP3 SEDOWN3
SEUP4 SEDOWN4 SEUP5 SEDOWN5 -etc.-
Example:
DTI SETREE 1 1 14 2 14 3 14
4 14 14 0
Describer Meaning
SEUPi Identification number of the superelement upstream from SEDOWNi. (Integer > 0)
SEDOWNi Identification number of the superelement into which SEUPi is assembled.
(Integer > 0)
Remarks:
1. SETREE entries or the DTI,SETREE entry are required for multi-level superelement configurations.
2. If an DTI,SETREE entry is provided, then SETREE entries are not required.
3. If both SETREE entries and a DTI,SETREE entry exist, then the DTI,SETREE entry will be
ignored.
4. If a superelement is not referenced on the DTI,SETREE or SETREE entry, then the manner in which
it is handled depends on the type of that superelement. If it is a PART superelement, then the residual
will be regarded as its downstream superelement and the undefined superelement will therefore be
placed immediately above the residual in the tree. If it is a Main Bulk Data superelement, then it will
also be handled like an undefined PART superelement as above if all of its exterior points belong to the
residual. However, if one or more of its exterior points do not belong to the residual, then the program
will terminate with a user fatal error complaining that one of more of the superelements are not in the
same path.
5. If this entry is not present, the superelement tree and the processing order are determined
automatically.
6. A superelement identification may appear only once in a SEUPi field.
7. On restart, if a superelement identification does not appear in a SEUPi field, its matrices will not be
assembled, even though they may be present in the database.
8. See the MSC Nastran Superelements and Modules User’s Guide for a description of user-designated
trees.
Main Index
DTI,SETREE 1639
Superelement Tree Definition
9. This entry is stored in the database automatically. Once stored, the Bulk Data entry may be removed
from the input file.
10. In the example above, the following superelement tree is defined:
1 2 3 4
14
Figure 9-88 Sample Superelement Tree
Main Index
1640 DTI,SPECSEL
Response Spectra Input Correlation Table
DTI,SPECSEL Response Spectra Input Correlation Table
Correlates spectra lines specified on TABLED1 entries with damping values.
Format:
1 2 3 4 5 6 7 8 9 10
DTI SPECSEL RECNO TYPE TIDl DAMP1 TID2 DAMP2
TID3 DAMP3 TID4 DAMP4 TID5 DAMP5 -etc.-
Example:
DTI SPECSEL 1 A 1 .02 2 .04
3 .06
DTI SPECSEL 3 V 4 .01
Describer Meaning
RECNO Spectrum number. (Integer > 0)
TYPE Type of spectrum. (Character: “A” for acceleration, “V” for velocity, or “D” for
displacement.)
TIDi TABLED1 entry identification number. (Integer > 0)
DAMPi Damping value assigned to TIDi. (Real)
Remarks:
1. The RECNO is the number of the spectrum defined by this entry. It is referenced on DLOAD Bulk
Data entries.
2. The TIDi, DAMPi pairs list the TABLEDl entry, which defines a line of the spectrum and the
damping value assigned to it. The damping value is in the units of fraction of critical damping.
3. This entry is placed in the database automatically. Once stored, the Bulk Data entry may be removed
from the input file.
Main Index
DTI,SPSEL 1641
Response Spectra Generation Correlation Table
DTI,SPSEL Response Spectra Generation Correlation Table
Correlates output requests with frequency and damping ranges.
Format:
1 2 3 4 5 6 7 8 9 10
DTI SPSEL RECNO DAMPL FREQL G1 G2 G3 G4
G5 G6 G7 -etc.-
Example:
DTI SPSEL 1 2 1 11 12
DTI SPSEL 2 4 3 1 7 11 12
13 14
Describer Meaning
DAMPL Identification number of the FREQ, FREQ1, or FREQ2 Bulk Data entry that specifies
the list of damping values. (Integer > 0)
FREQL Identification number of the FREQi Bulk Data entry that specifies the list of
frequencies. (Integer > 0)
Gi Grid point number where response spectra will be calculated. (Integer > 0)
RECNO Record number of spectra to be generated. (Sequential integer beginning with 1.)
Remarks:
1. This table is used in SOLs 109 and 112.
2. Damping values are in the units of fraction of critical damping.
3. Output of response spectra requires the use of the XYPLOT...SPECTRA(RECNO)/Gi... command,
where Gi is restricted to the grid points listed on the (RECNO) record of this entry.
4. The SPSEL table is stored in the database automatically in SOLs 109 and 112. Once stored, the Bulk
Data entry may be removed from the input file.
5. There must be case control output request for displacements and velocities of the points to be output.
For example you could use case control commands:
DISP(PLOT) = ALL
VELO(PLOT) = ALL
Main Index
1642 DTI,UNITS
Unit Definitions
DTI,UNITS Unit Definitions
Defines units necessary for conversion during the analysis for the Nastran/ADAMS interface or a Nastran
fatigue analysis.
Format:
1 2 3 4 5 6 7 8 9 10
DTI UNITS 1 MASS FORCE LENGTH TIME STRESS
Example:
DTI UNITS 1 KG N M S MPA
Remarks:
1. The DTI,UNITS Bulk Data entry is required for a ADAMSMNF FLEXBODY=YES run. See the
ADAMSMNF* (Case) case control entry. ADAMS is not a unitless code (as is Nastran). Units must be
specified. A DTI Bulk Data entry provides ‘UNITS’ (a unique identifier) input as the above example
illustrates. Once identified, the units will apply to all superelements in the model. Acceptable
character input strings are listed in the table below. MASS, FORCE, LENGTH, and TIME are
required for ADAMS interface.
2. MSC Nastran is a unitless code and it is the user’s responsibility to ensure compatible units. During
a fatigue analysis, stress is converted to SI units of MPa because the fatigue material property stress
parameters as defined on the MATFTG entry are internally converted to standard SI units of MPa.
The stresses from the analysis must match. Thus it is necessary for the user to use DTI,UNITS to
define the stress units to ensure proper conversion. The default units are MPa and this entry is only
necessary if stresses are not in MPa.
Mass Force Length Time Stress*
KG - kilogram N - newton KM - kilometer H - hour MPA -
megapascal
LBM - pound- LBF - pounds-force M - meter MIN - minute PA - pascal
mass
SLUG - slug KGF - kilograms- CM - centimeter S - second PSI - pound per
force square inch
GRAM - gram OZF - ounce-force MM - millimeter MS - millisecond KSI - kilo
pound per
square inch
OZM - ounce- DYNE - dyne MI - mile US - microsecond PSF - pound
mass per square foot
Main Index
DTI,UNITS 1643
Unit Definitions
Mass Force Length Time Stress*
KLBM - kilo KN - kilonewton FT - foot NANOSEC - KSF - kilo
pound-mass (1000 nanosecond pound per
lbm) square foot
MGG - megagram KLBF - kilo pound- IN- inch D - day DYNECM2 -
force (1000 lbf ) dyne per square
centimeter
SLINCH - 12 slugs MN - millinewton UM - micrometer BAR - bar
UG - microgram UN - micronewton NM - nanometer ATM - physical
atmosphere
NG - nanogram NN - nanonewton ANG - angstrom
USTON - US ton YD - yard
MIL - milli-inch
UIN - micro-inch
* For fatigue analysis of spot welds, only MPA, PA, PSI, KSI, PSF, and KSF are supported.
For random vibration fatigue analysis using SOL 108 or 111, only MPA, PA, PSI, and KSI are sup-
ported.
Main Index
1644 DVBSHAP
Design Variable to Boundary Shapes
DVBSHAP Design Variable to Boundary Shapes
Associates a design variable identification number to a linear combination of boundary shape vectors from a
particular auxiliary model.
Format:
1 2 3 4 5 6 7 8 9 10
DVBSHAP DVID AUXMOD COL1 SF1 COL2 SF2 COL3 SF3
Example:
DVBSHAP 4 1 1 1.6
Describer Meaning
DVID Design variable identification number of a DESVAR entry. (Integer > 0)
AUXMOD Auxiliary model identification number. (Integer > 0)
COLi Load sequence identification number from AUXMODEL Case Control command.
(Integer > 0)
SFi Scaling factor for load sequence identification number. (Real; Default = 1.0)
Remarks:
1. Design variable DVID must be defined on a DESVAR entry.
2. Multiple references to the same DVID and/or COLi will result in the vector addition of the
referenced boundary shape vectors.
3. Multiple DVBSHAP entries may be specified.
Main Index
DVCREL1 1645
Design Variable to Connectivity Property Relation
DVCREL1 Design Variable to Connectivity Property Relation
Defines the relation between a connectivity property and design variables.
Format:
1 2 3 4 5 6 7 8 9 10
DVCREL1 ID TYPE EID CPNAME CPMIN CPMAX C0
DVID1 COEF1 DVID2 COEF2 DVID3 COEF3 -etc.-
Example:
DVCREL1 5 CQUAD4 1 ZOFFS 1.0
1 1.0
Describer Meaning
ID Unique identification number. (Integer > 0)
TYPE Name of an element connectivity entry, such as “CBAR”, “CQUAD4”, etc. (Character)
EID Element Identification number. (Integer > 0)
CPNAME Name of connectivity property, such as “X1”, “X2”, “X3”, “ZOFFS”, etc. (Character)
CPMIN Minimum value allowed for this property. If CPNAME references a connectivity property
that can only be positive, then the default value of CPMIN is 1.0E-15. Otherwise, it is -
1.0E35. See Remark 4. (Real)
CPMAX Maximum value allowed for this property. See Remark 4. (Real; Default =1.0E+20)
C0 Constant term of relation. (Real; Default = 0.0)
DVIDi DESVAR entry identification number. (Integer > 0)
COEFi Coefficient of linear relation or keyword = “PVAL”. (If i = 1, Real or Character; if i > 1,
Real)
Remarks:
1. The relationship between the connectivity property and design variables is given by:
CP j = C 0 + COEF i X DVID
i
i
2. The continuation entry is required.
3. The fifth field of the entry, CPNAME, only accepts string characters. These string values must be the
same as those given in the connectivity entry descriptions in this Guide. For example, if the plate
offset is to be designed (CQUAD4, CTRIA3, etc), ZOFFS (case insensitive) must be specified on the
CPNAME field.
Main Index
1646 DVCREL1
Design Variable to Connectivity Property Relation
4. The default values for CPMIN and CPMAX are not applied when the linear property is a function
of a single design variable and C0=0. It is expected that the limits applied on the associated DESVAR
entry will keep the designed property within meaningful bounds.
5. When "PVAL" is used for the COEF1 field, this is a flag to indicate that the COEF1 value is to be
obtained from the connectivity bulk data entry. If a DVCREL1 entry references more than one design
variable with the PVAL option, a User Fatal Message will be issued.
6. If the user inputs CQUAD4/CTRIA3 entries and then uses QRMETH = 5 to convert them to
CQUADR/CTRIAR entries, the design of items on these entries using the DVCREL1 entry should
refer to the converted type (i.e., CQUADR/CTRIAR). Similarly, if QRMETH=2 or 3 is used, the
DVCREL1 entry should refer to CQUAD4/CTRIA3 types.
Main Index
DVCREL2 1647
Design Variable to Connectivity Property Relation
DVCREL2 Design Variable to Connectivity Property Relation
Defines the relation between a connectivity property and design variables with a user-supplied equation.
Format:
1 2 3 4 5 6 7 8 9 10
DVCREL2 ID TYPE EID CPNAME CPMIN CPMAX EQID
“DESVAR” DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7
DVID8 -etc.-
“DTABLE” LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7
LABL8 -etc.-
Example:
DVCREL2 1 CBAR 100 X1 0.05 1.0 100
DESVAR 1001
DTABLE X10
Describer Meaning
ID Unique identification number. (Integer > 0)
TYPE Name of an element connectivity entry, such as “CBAR”, “CQUAD4”, etc. (Character)
EID Element Identification number. (Integer > 0)
CPNAME Name of connectivity property, such as “X1”, “X2”, “X3”, “ZOFFS”, etc. (Character)
CPMIN Minimum value allowed for this property. If CPNAME references a connectivity
property that can only be positive, then the default value of CPMIN is 1.0E-15.
Otherwise, it is -1.0E35. (Real)
CPMAX Maximum value allowed for this property. (Real; Default =1.0E+20)
EQID DEQATN entry identification number. (Integer > 0)
“DESVAR” DESVAR flag. Indicates that the IDs of DESVAR entries follow. (Character)
DVIDi DESVAR entry identification number. (Integer > 0)
“DTABLE” DTABLE flag. Indicates that the LABLs for the constants in a DTABLE or DTABLE2
entry follow. This field may be omitted if there are no constants involved in this
relation. (Character)
LABLi Label for a constant on the DTABLE or DTABLE2 entry. (Character)
Main Index
1648 DVCREL2
Design Variable to Connectivity Property Relation
Remarks:
1. The variable identified by DVIDi and LABLi correspond to variable names (x1, x2, etc.) listed in the
left-hand side of the first equation on the DEQATN entry identified by EQID. The variable names
x1 through xN (where N = m + n ) are assigned in the order DVID1, DVID2, ..., DVIDm, LABL1,
LABL2, ..., LABLn.
2. If both “DESVAR” and “DTABLE” are specified in field 2, “DESVAR” must appear first.
3. The fifth field of the entry, CPNAME, only accepts string characters. These string values must be the
same as those given in the connectivity entry descriptions in this Guide. For example, if the plate
offset is to be designed (CQUAD4, CTRIA3, etc.), ZOFFS (case insensitive) must be specified on
the CPNAME field.
4. If the user inputs CQUAD4/CTRIA3 entries and then uses QRMETH = 5 to convert them to
CQUADR/CTRIAR entries, the design of items on these entries using the DVCREL2 entry should
refer to the converted type (i.e., CQUADR/CTRIAR). Similarly, if QRMETH=2 or 3 is used, the
DVCREL2 entry should refer to CQUAD4/CTRIA3 types.
Main Index
DVGRID 1649
Design Variable to Grid Point Relation
DVGRID Design Variable to Grid Point Relation
Defines the relationship between design variables and grid point locations.
Format:
1 2 3 4 5 6 7 8 9 10
DVGRID DVID GID CID COEFF N1 N2 N3
Example:
DVGRID 3 108 5 0.2 0.5 0.3 1.0
Describer Meaning
DVID DESVAR entry identification number. (Integer > 0)
GID Grid point (GRID) or geometric point (POINT) identification number. (Integer > 0)
CID Coordinate system identification number. (Integer > 0; Default = 0)
COEFF Multiplier of the vector defined by Ni. (Real; Default = 0.0)
Ni Components of the vector measured in the coordinate system defined by CID. (Real;
at least one Ni 0.0)
Remarks:
1. A CID of zero or blank (the default) references the basic coordinate system.
2. Multiple references to the same grid ID and design variable result in vectorial addition of the
participation vectors defined by CID, COEFF, and Ni. There is no restriction on the number of
DVGRID entries that may reference a given grid (GID) or design variable (DVID).
3. The coordinate update equation is given as
0 0
g i – g i = COEFFj XDVIDj –XDVIDj N j
j
T
where g i is the location of the i-th grid, g x g y g z .
T
The vector N = N x N y N z is determined from CID and Ni. Note that it is a change in a
0
design variable from its initial value X , and not the absolute value of the design variable itself, that
0
represents a change in a grid point location, g i – g i .
4. The DVGRID entry defines the participation coefficients (basis vectors) of each design variable for
each of the coordinates affected by the design process in the relationship
Main Index
1650 DVGRID
Design Variable to Grid Point Relation
g i = T ij Xj
j
5. DVGRID entries that reference grid points on MPCs or RSSCON entries produce incorrect
sensitivities. Often the sensitivities are 0.0 which may result in a warning message indicating zero
gradients which may be followed by UFM 6499. Other rigid elements produce correct results.
Main Index
DVLREL1 1651
Defines the linear relation between analysis model loading and design variables in SOL 200 with Analysis = STATICS
DVLREL1 Defines the linear relation between analysis model loading and design variables in SOL
200 with Analysis = STATICS
Format:
1 2 3 4 5 6 7 8 9 10
DVLREL1 ID TYPE SID LNAME LMIN LMAX C0
ATT1 ATT2 ATT3 ATT4 ATT5
DVID COEF DVID2 COEF2 DVID3 Etc
Example: Design the N1 FORCE at GRID 100 to be equal to DESVAR=10
DVLREL1 10 FORCE 300 N1
100
10 1.0
Describer Meaning
ID Unique identification number (Integer>0)
TYPE Name of Load, such as FORCE, see Remark 2. for supported types (Character)
SID Load set ID (Integer>0)
LNAME Load Name, such as F or N1 on the FORCE entry. See Remark 2. (Character)
LMIN Minimum value for the load. See Remark 5. (Real, default=-1.0e35)
LMAX Maximum value for the load (Real, Default=1.0e20)
C0 Constant term of relation (Real, Default=0.0)
ATTi Attributes of the designed load, see Remark 2. (Integer>0 or blank)
DVIDi DESVAR entry identification number. (Integer>0)
COEFi Coefficient of linear relation or keyword=”PVAL”, See Remark 3. (If i=1, Real or
Character; if i>1, Real )
Remarks:
1. The relationship between the analysis model load and the design variables is given by:
L i = C 0 + COEFF i X DVID
i
Main Index
1652 DVLREL1
Defines the linear relation between analysis model loading and design variables in SOL 200 with Analysis = STATICS
2. Supported TYPEs and their ATTi meaning are given in the following table:
LNAME ATT1 ATT2 ATT3 ATT4 ATT5
Load Type (character) (integer) (integer) (integer) (integer) (integer)
FORCE F, N1, N2 or N3 G CID
(see remark 6)
LOAD S or Si 0 if LNAME
is S, Li
otherwise
MOMENT M, N1, N2 or N3 G CID (see
remark 6)
3. When "PVAL" is used for the COEF1 field, this is a flag to indicate that the COEF1 value is to be
obtained from the load bulk data entry. If a DVLREL1 entry references more than one design variable
with the PVAL option, a User Fatal Message will be issued.
4. If there are multiple loads that satisfy the designation of the request (for example two FORCE entries
with identical SID, GRID and CID values), it is a user input error.
5. The default values of LMIN and LMAX are not applied when the linear property is a function of a
single design variable and C0=0. It is expected that the limits applied on the DESVAR entry will keep
the designed property within reasonable bounds
6. Input of these data is optional. It most cases, leaving it off will result in a single load that qualifies with
the remaining attributes. If there are multiple instances that qualify, it is a user input error.
7. The use of this entry is limited to statics and buckling analyses in SOL 200.
Main Index
DVMREL1 1653
Design Variable to Material Relation
DVMREL1 Design Variable to Material Relation
Defines the relation between a material property and design variables.
Format:
1 2 3 4 5 6 7 8 9 10
DVMREL1 ID TYPE MID MPNAME MPMIN MPMAX C0
DVID1 COEF1 DVID2 COEF2 DVID3 COEF3 -etc.-
Example:
DVMREL1 5 MAT1 1 RHO 0.05 1.0
1 1.0
Describer Meaning
ID Unique identification number. (Integer > 0)
TYPE Name of a material property entry, such as “MAT1”, “MAT2”, etc. (Character)
MID Material Identification number. (Integer > 0)
MPNAME Name of material property, such as “E” or “RHO”. (Character)
MPMIN Minimum value allowed for this property. If MPNAME references a material property
that can only be positive, then the default value for MPMIN is 1.0E-15. Otherwise, it
is -1.0E35. See Remark 4. (Real)
MPMAX Maximum value allowed for this property. See Remark 4. (Real; Default = 1.0E+20)
C0 Constant term of relation. (Real; Default = 0.0)
DVIDi DESVAR entry identification number. (Integer > 0)
COEFi Coefficient of linear relation or keyword = “PVAL”. (If i = 1, Real or Character; if i >
1, Real)
Remarks:
1. The relationship between the material property and design variables is given by:
MP i = C 0 + COEF i X DVID
i
i
2. The continuation entry is required.
3. The fifth field of the entry, MPNAME, only accepts string characters. It must be the same as the name
that appears in the Bulk Data Entries for various material properties. For example, if the isotropic
material density is to be designed, RHO (case insensitive) must be specified on the MPNAME field.
Main Index
1654 DVMREL1
Design Variable to Material Relation
4. The default value for MPMIN and MPMAX are not applied when the linear property is a function
of a single design variable and C0=0.0. It is expected that the limits applied to the DESVAR entry
will keep the designed property within reasonable bounds.
5. When "PVAL" is used for the COEF1 field, this is a flag to indicate that the COEF1 value is to be
obtained from the material bulk data entry. If a DVMREL1 entry references more than one design
variable with the PVAL option, a User Fatal Message will be issued.
Main Index
DVMREL2 1655
Design Variable to Material Relation
DVMREL2 Design Variable to Material Relation
Defines the relation between a material property and design variables with a user-supplied equation.
Format:
1 2 3 4 5 6 7 8 9 10
DVMREL2 ID TYPE MID MPNAME MPMIN MPMAX EQID
DESVAR DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7
DVID8 -etc.-
DTABLE LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7
LABL8 -etc.-
Example:
DVMREL2 5 MAT1 1 E 0.05 1.0 100
DESVAR 1 2
DTABLE E0
Describer Meaning
ID Unique identification number. (Integer > 0)
TYPE Name of a material property entry, such as “MAT1”, “MAT2”, etc. (Character)
MID Material Identification number. (Integer > 0)
MPNAME Name of material property, such as “E” or “RHO”. (Character)
MPMIN Minimum value allowed for this property. If MPNAME references a material property
that can only be positive, then the default value for MPMIN is 1.0E-15. Otherwise, it
is -1.0E35. (Real)
MPMAX Maximum value allowed for this property. (Real; Default = 1.0E+20)
EQID DEQATN entry identification number. (Integer > 0)
DESVAR DESVAR flag. Indicates that the IDs of DESVAR entries follow. (Character)
DVIDi DESVAR entry identification number. (Integer > 0)
DTABLE DTABLE flag. Indicates that the LABLs for the constants in a DTABLE or DTABLE2
entry follow. This field may be omitted if there are no constants involved in this
relation. (Character)
LABLi Label for a constant on the DTABLE or DTABLE2 entry. (Character)
Main Index
1656 DVMREL2
Design Variable to Material Relation
Remarks:
1. The variables identified by DVIDi and LABLi correspond to variable names (x1, x2, etc.) listed in the
left-hand side of the first equation on the DEQATN entry identified by EQID. The variable names
x1 through xN (where N = m + n ) are assigned in the order DVID1, DVID2, ..., DVIDm, LABL1,
LABL2, ..., LABLn.
2. If both “DESVAR” and “DTABLE” are specified in field 2, “DESVAR” must appear first.
3. The fifth field of the entry, MPNAME, only accepts string characters. It must be the same as the name
that appears in the Bulk Data Entries for various material properties. For example, if the isotropic
material density is to be designed, RHO (case insensitive) must be specified on the MPNAME field.
Main Index
DVPREL1 1657
Design Variable to Property Relation
DVPREL1 Design Variable to Property Relation
Defines the relation between an analysis model property and design variables.
Format:
1 2 3 4 5 6 7 8 9 10
DVPREL1 ID TYPE PID PNAME/ PMIN PMAX C0
FID
DVID1 COEF1 DVID2 COEF2 DVID3 -etc.-
Example:
DVPREL1 12 PBAR 612 6 0.2 3.0
4 0.25 20 20.0 5 0.3
Describer Meaning
ID Unique identification number. (Integer > 0)
TYPE Name of a property entry, such as “PBAR”, “PBEAM”, etc. (Character)
PID Property entry identification number. (Integer > 0)
PNAME/FlD Property name, such as “T”, “A”, or field position of the property entry, or word
position in the element property table of the analysis model. Property names that
begin with an integer such as 12I/T**3 may only be referred to by field position.
(Character or Integer 0)
PMIN Minimum value allowed for this property. If PMIN references a property that can
only be positive, then the default value for PMIN is 1.0E-15. Otherwise, it is -
1.0E35. See Remark 6. (Real)
PMAX Maximum value allowed for this property. (Real; Default = 1.0E+20)
C0 Constant term of relation. (Real; Default = 0.0)
DVIDi DESVAR entry identification number. (Integer > 0)
COEFi Coefficient of linear relation or keyword = “PVAL”. See Remark 7. (If i = 1, Real or
Character; if i > 1, Real)
Remarks:
1. The relationship between the analysis model property and design variables is given by:
P j = C 0 + COEF i X DVID
i
i
2. The continuation entry is required.
3. TYPE=“PBEND” is not supported. TYPE=“PBEAML” supports only PNAME and not FID.
Main Index
1658 DVPREL1
Design Variable to Property Relation
4. FID may be either a positive or a negative number. If FID > 0, it identifies the field position on a
property entry. If FID < 0, it identifies the word position of an entry in the element property table.
For example, to specify the area of a PBAR, either PNAME=A, FID=+4 or FID=-3 can be used. In
general, use of PNAME is recommended. For Type "PBUSH", PNAME is recommended, if FID is
used it must be < 0.
5. Designing PBEAML or PBEAM requires specification of both property name and station. Table 14
shows several examples.
Table 14
Property
PTYPE Name END A END B i-th Station
PBEAML DIM1 DIM1 or DIM1(B) DIM1(i)
DIM1(A)
PBEAM A A or A(A) A(B) A(i)
Only stations that are input on a PBEAM or PBEAML entry can be referenced by a DVPREL1. For
example, referencing an END B property name on a DVPREL1 entry when the referenced PBEAM
does not explicitly specify the END B station, is not allowed.
6. The default values of PMIN and PMAX are not applied when the linear property is a function of a
single design variable and C0=0. It is expected that the limits applied on the DESVAR entry will keep
the designed property within reasonable bounds.
7. When "PVAL" is used for the COEF1 field, this is a flag to indicate that the COEF1 value is to be
obtained from the property bulk data entry. If a DVPREL1 entry references more than one design
variable with the PVAL option, a User Fatal Message will be issued.
8. With GPLY for TYPE field and GPLYID for PID field, a ply identified with GPLYID across all
PCOMPG entries in the model can be designed. Internally, a DVPREL1 will be spawned for each
PCOMPG has a ply ID of GPLYID. For TYPE=GPLY, the relationship between the analysis model
property and design variables is given by.
P i = C0 + T0 i or THETA0 i COEF j X DVID for PNAME=T or THETA
j
j
Where T0 and THETA0 are value of thickness and theta angle on the original PCOMPG. Note that
non-zero C0 is not recommended for TYPE=GPLY or PCOMPG. For THETA0 with original value
equal to 0.0, THETA0 is taken as 1.0 and it is recommended to have XINIT of DVID set to 0.0.
Main Index
DVPREL2 1659
Design Variable to Property Relation
DVPREL2 Design Variable to Property Relation
Defines the relation between an analysis model property and design variables with a user-supplied equation.
Format:
1 2 3 4 5 6 7 8 9 10
DVPREL2 ID TYPE PID PNAME/ PMIN PMAX EQID
FID
“DESVAR” DVID1 DVID2 DVID3 DVID4 DVID5 DVID6 DVID7
DVID8 -etc.-
“DTABLE” LABL1 LABL2 LABL3 LABL4 LABL5 LABL6 LABL7
LABL8 -etc.-
Example:
DVPREL2 13 PBAR 712 5 0.2 0.4 50
DESVAR 4 11 13 5
DTABLE PI YM
Describer Meaning
ID Unique identification number. (Integer > 0)
TYPE Name of a property entry, such as PBAR, PBEAM, etc. (Character)
PID Property entry identification number. (Integer > 0)
PNAME/FID Property name, such as “T”, “A”, or field position of the property entry, or word
position in the element property table of the analysis model. Property names that
begin with an integer such as 12I/T**3 may only be referred to by field position.
(Character or Integer 0)
PMIN Minimum value allowed for this property. If FID references a stress recovery
location field, then the default value for PMIN is -1.0+35. PMIN must be
explicitly set to a negative number for properties that may be less than zero (for
example, field ZO on the PCOMP entry). (Real; Default = 1.E-15)
PMAX Maximum value allowed for this property. (Real; Default = 1.0E20)
EQID DEQATN entry identification number. (Integer > 0)
“DESVAR” DESVAR flag. Indicates that the IDs of DESVAR entries follow. (Character)
DVIDi DESVAR entry identification number. (Integer > 0)
“DTABLE” DTABLE flag. Indicates that the LABLs for the constants in a DTABLE or
DTABLE2 entry follow. This field may be omitted if there are no constants
involved in this relation. (Character)
LABLi Label for a constant on the DTABLE or DTABLE2 entry. (Character)
Main Index
1660 DVPREL2
Design Variable to Property Relation
Remarks:
1. The variables identified by DVIDi and LABLi correspond to variable names (x1, x2, etc.) listed in the
left-hand side of the first equation on the DEQATN entry identified by EQID. The variable names
x1 through xN (where N = m+n) are assigned in the order DVID1, DVID2, ..., DVIDn, LABL1,
LABL2, ..., LABLm.
2. If both “DESVAR” and “DTABLE” are specified in field 2, “DESVAR” must appear first.
3. FID may be either a positive or a negative number. If FID > 0, it identifies the field position on a
property entry. If FID < 0, it identifies the word position of an entry in EPT. For example, to specify
the area of a PBAR, either PNAME=A, FID = +4 or FID = -3 may be used. In general, use of
PNAME is recommended. For Type "PBUSH", PNAME is recommended, if FID is used it must be
< 0.
4. Types “PBEND”, “PBARL” and “PBEAML” are not supported for the DVPREL2.
5. Designing PBEAM requires specification of both property name and station. Table 15 shows one
example.
Table 15
PTYPE Property Name END A END B i-th Station
PBEAM A A or A(A) A(B) A(i)
Only stations that are input on a PBEAM entry can be referenced by a DVPREL2. For example,
referencing an END B property name on a DVPREL2 entry when the referenced PBEAM does not
explicitly specify the END B station, is not allowed.
Main Index
DVSHAP 1661
Design Variable to Basis Vector(s)
DVSHAP Design Variable to Basis Vector(s)
Defines a shape basis vector by relating a design variable identification number (DVID) to columns of a
displacement matrix.
Format:
1 2 3 4 5 6 7 8 9 10
DVSHAP DVID COL1 SF1 COL2 SF2 COL3 SF3
Example:
DVSHAP 2 1 2.0 4 1.0
Describer Meaning
DVID Design variable identification number on the DESVAR entry. (Integer > 0)
COLi Column number of the displacement matrix. See Remark 2. (1 < Integer < maximum
column number in the displacement matrix.)
SFi Scaling factor applied to the COLi-th column of the displacement matrix. (Real;
Default = 1.0)
Remarks:
1. DVID must be defined on a DESVAR entry.
2. COLi must be a valid column number in the displacement matrix.
3. Multiple references to the same DVID and/or COLi will result in a linear combination of
displacement vectors. In the example above, the shape basis vector is a linear combination of the
fourth column and twice the second column.
4. The displacement matrix must have been created by SOL 101 or 200 with analysis = statics and be
available on a database, which is attached via the DBLOCATE FMS statement shown below:
ASSIGN DISPMAT=’ physical filename of MASTER DBset ’
DBLOCATE DATABLK=(UG/UGD,GEOM1/GEOM1D,GEOM2/GEOM2D) ,
LOGICAL=DISPMAT
Main Index
1662 DVPSURF
Design Variable to Control Surface Setting Relation
DVPSURF Design Variable to Control Surface Setting Relation
Defines the relationship between a control surface setting in a particular subcase and a design variable.
Format:
1 2 3 4 5 6 7 8 9 10
DVPSURF ID AELABEL TRIMID DVID COEF
Example:
DVPSURF 10 OBDFLAP 1 100 0.01746
Describer Meaning
ID Unique identification number (Integer>0)
AELABEL LABEL of the AESURF entry that is being designed (Character ,no default)
TRIMID Associated trim set identification number (Integer>0)
DVID DESVAR entry identification number (Integer>0)
COEF Coefficient of linear relation (Real)
Remarks:
1. The relationship between the control surface setting and the design variable is given by SURF =
COEF * XDVID
2. The surface called out by AELABEL must also appear on the trim entry specified by TRIMID. The
value specified on the trim entry will be overwritten by the value obtained from the relationship of
Remark 1.
3. Limits on the control deflection are not provided on this entry but can be specified on the underlying
DESVAR
4. The DVID called out on this entry cannot be associated with any other designed property.
5. Note that since the DVPSURF calls out a TRIM ID, it is associated only with a single subcase.
Main Index
DYFSISW 1663
Fluid Structure Interaction Activation Switch
DYFSISW Fluid Structure Interaction Activation Switch
Allows activating or deactivating Fluid Structure Interaction and Eulerian solver. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
DYFSISW SWID TID INITV
Example:
DYFSISW 14 10
Describer Meaning
SWID Unique number of a DYFSISW entry. (Integer > 0; Required)
TID TABLED1 ID. Fluid Structure Interface and Euler solver are switched on and off,
depending on the y-value of the table. The x-value of the table represents the time; the
y-value denotes:
ON y > 0.0
OFF y < 0.0
INITV Euler element initialization flag. See remark 3. (Character, Default=NO)
NO Element initialization at cycle 0
YES Element initialization when the elements becomes active
Remarks:
1. The default is that COUPLE, AIRBAG and Euler solver is active at all times.
2. When Euler solver is deactivated, no output will be generated for the Eulerian elements.
3. For simulations involving a prestress phase the Euler elements can be initially deactivated. When the
Euler elements are activated the Eulerian masses still originate from the Euler initiation at cycle 0. If
during prestressing the structure did not move much, then these Eulerian masses of cycle 0 can give
a stable run. But if there has been substantial movement of the structure then Eulerian masses can be
erroneously compressed. This shows up by large pressures and velocities in the Euler elements and a
time step too small. To avoid this instability the Euler initialization can be postponed until the Euler
elements become active.
Main Index
1664 DYPARAM, ATBAOUT
Output Frequency to Main Output File of ATB - SOL 700
DYPARAM, ATBAOUT Output Frequency to Main Output File of ATB - SOL 700
Defines the frequency at which output is written to the main output file of ATB. Used in SOL700 only.
Format:
DYPARAM, ATBAOUT, value
Example:
DYPARAM, ATBAOUT, 5.0E-3
Option Content
Value Every multiple of ATBAOUT seconds, the main output file of ATB is updated. (Real
> 0.0; default=10.0E-3)
Remarks:
1. Only active when field 3 on the A5 card of the ATB input file is set to a value of -1.
2. Controls the frequency of the output of segment acceleration, velocity and displacement, joint forces
and moments.
Main Index
DYPARAM, ATBHOUT 1665
Write ATB Output to Time history files - SOL 700
DYPARAM, ATBHOUT Write ATB Output to Time history files - SOL 700
A time-history file is created containing the output as requested in the ATB input file on cards H.1 to H.11.
Used in SOL700 only.
Format:
DYPARAM, ATBHOUT, option
Example:
DYPARAM, ATBHOUT, NO
Option Content
Option Flag of ATBHOUT. (Character; default=YES)
YES: The time history files are created.
NO: The time history files are not created.
Main Index
1666 DYPARAM, ATBTOUT
Output Frequency to Time-History Files of ATB - SOL 700
DYPARAM, ATBTOUT Output Frequency to Time-History Files of ATB - SOL 700
Defines the frequency at which output is written to the time-history files of ATB. Used in SOL700 only.
Format:
DYPARAM, ATBTOUT, value
Example:
DYPARAM, ATBTOUT, 1.0E-4
Option Content
Value Every multiple of ATBTOUT seconds, the time-history files of ATB are updated.
(Real > 0.0; default=1.0E-3)
Remarks:
1. Only active when field 26 on the A5 card of the ATB input file is set to a value of -1.
2. Controls the frequency of all output requested on the H-cards, and of the tabular time-histories that
are controlled by field 18 on the A5 card of the ATB input file.
Main Index
DYPARAM,AUTOCOUP 1667
Automatic Coupling
DYPARAM,AUTOCOUP Automatic Coupling
Defines the automatic coupling algorithm. Used in Sol700 only.
Format:
DYPARAM,AUTOCOUP,ACTIVE,CLEAN,DUMMY, TOL_AREA, OUTPUT, FAIL
Example:
DYPARAM, AUTOCOUP, ON
Describer Meaning
ACTIVE Flag of activation of the sub element approach. (Character; default=OFF)
ON Turn on the sub element approach.
OFF Turn off the sub element approach.
CLEAN Flag of cleaning obsolete sub elements. (Character; default=OFF)
ON Cleans obsolete sub elements
OFF Obsolete elements will not be removed from memory.
DUMMY Flag of putting dummy segments on coupling surface archives. (Character; default=OFF)
ON Puts dummy segments on the coupling surface archive
OFF Does not put dummy segments on the coupling surface archive.
TOL_AREA If the area of a hole is smaller than TOL_AREA a 1D flow computation method is used.
(Real ≥ 0.0; default=0.0).
OUTPUT Determines how results of Euler elements that are intersected by the structure are written
to the Euler archive. (Character, Default = ZERO).
ZERO Write zero for the results of these intersected elements.
AVERAGE Average across sub elements. Each sub element has the same weight.
AVEREAGEU Average across sub element using the uncover fraction as weights.
MAXUNC The results are taken from the sub element with the largest volume
uncover fraction.
COVER Uses the cover field of COUPLE to select the proper sub element. Only
supported for COVER=OUTSIDE or COVER=INSIDE. Not
supported for COVER =NONE.
FAIL Activates fluid flow through failed shell segments in the coupling surface. (Character;
there is no default, if failure is not used, then FAIL should be left blank)
POROUS Makes failed segment porous. This is the fast coupling approach.
REMOVE Removes the failed segments from the coupling surface.
Main Index
1668 DYPARAM,AUTOCOUP
Automatic Coupling
Remarks:
1. Features that are not supported are:
• Multiple Euler domain
• Adaptive Euler meshes
• Fluid flow through failed segments in the coupling surface failure can only be defined by option
FAIL of DYPARAM, AUTOCOUP. Defining this failure by use of COUP1FL and COUPINT
is not supported.
• COUPLE with option AIRBAG
• Graded meshes
• Euler import
• Viscosity
• Porosity
• Option FAIL=POROUS and REMOVE are not supported by DMP.
• Markers
2. With automatic coupling fluid can be defined on both sides of the coupling surface. To do this option
COVER of the COUPLE entry has to be set to NONE. When using COVER = OUTSIDE fluid is
only initialized in the inside region of the coupling surface. For COVER = INSIDE the opposite
applies. When the coupling surface is not closed, only COVER=NONE is allowed.
3. In the auto coupling approach holes in the coupling surface are meshed with dummy segments. For
holes with large deformations PARAM DUMSEGS, ON can be used to maintain good dummy
segments.
4. For adding FAIL = POROUS failed segments have to be made fully porous. This is straightforward.
5. FAIL = REMOVE. When the structure fails, holes in the coupling surface are formed. For a closed
coupling surface each side of a segment is connected to another segment. Therefore, the segments
have no free edges. But a segment adjacent to a hole has a free edge. At this edge it is not connected
to any other segment. A list of free edges of the coupling surface specifies the holes.By maintaining a
list of free edges auto coupling handles these holes automatically. If a segment fails, this list of free
edges has to be updated. Also the failed segment has to be removed from the coupling surface.
Note: This entry also supports DMP. While using for DMP, no changes to input is
needed. In the auto coupling method Euler elements that are intersected by the
structure are split into sub elements. For details refer to [1]. To enable dmp for auto
coupling some of the properties of sub elements have to be communicated across
CPU's.If holes in the coupling surface extend across multiple CPUs, also
communication across CPU's is needed.
Main Index
DYPARAM,AXIALSYM 1669
Axial Symmetric Analyses - SOL 700
DYPARAM,AXIALSYM Axial Symmetric Analyses - SOL 700
Enables an efficient and accurate 2-D axial symmetry for Eulerian materials. A much larger time step becomes
possible by not taking into account the mesh-size in circumferential direction. Used in SOL 700 only.
Format:
DYPARAM,AXIALSYM,MESHTYPE,AXIALAXIS,SYMPLAN,PHI,ALIGN,PHI2
Example:
DYPARAM,AXIALSYM,RECT,X,XY,2.5,YES,0.0
Describer Meaning
MESHTYPE Two types of Euler meshes are supported: (Character; Required)
AXIAL Axial symmetric meshes.
RECT Rectangular meshes
AXIAL AXIS X X-Axis (Character; Required)
Y Y-Axis
Z Z-Axis
SYMPLAN The approximate symmetry plan of the Euler mesh. On for MESHTYPE=AXIAL. See
Remark 7. (Character; Required)
XY XY-Plane
YZ YZ-Plane
ZX ZX-Plane
PHI Only used for MESHTYPE = RECT. Used to create a 2D axial symmetric mesh with
angles +PHI/2 and -PHI/2. (Real; Default = 0.0)
ALIGN Only used for MESHTYPE = AXIAL. (Character; Default = YES)
YES Align normals of oblique Euler element faces. This prevents errors in
strains that can arise from small errors in Euler face normals.
NO Do not align normals.
PHI2 As a final operation rotate the mesh around the axial axis by the angle PHI2. See
Remark 6. (Real; Default = 0.0)
Remarks:
1. Only available for Eulerian elements and does not support Lagrange elements. The effect of this
parameter is not limited to the solvers. Also Euler archives will reflect the modified Euler mesh
geometry.
Main Index
1670 DYPARAM,AXIALSYM
Axial Symmetric Analyses - SOL 700
2. The Euler mesh can already be symmetric but also a rectangular mesh comprising of one layer can be
used. Using the angle specified by PHI this Euler mesh is mapped into a 2d axial symmetric mesh.
3. The Euler mesh has to consist of one layer.
4. Rectangular meshes that can be made 2d symmetric using the angle PHI should satisfy:
• All boundary Euler faces are aligned with a coordinate direction
• Only one layer thick.
• The axial symmetry axis is either on the boundary of the Euler mesh or outside the Euler mesh.
It is not allowed that the axial axis is inside the Euler mesh.
Initialization of Euler element using geometric regions as defined by the TICEUL entry is carried
out onto the transformed 2d axial mesh.
5. In the time step computation the circumferential mesh-size will not be taken into account.
6. Use option PHI2 with caution. Euler initialization is done using the mesh rotated by the angle PHI2.
So after including the angle PHI2 or modifying its value the Euler initialization should be revised.
7. It is assumed that one of the coordinate planes is an approximate symmetry plane of the Euler mesh.
Although approximate symmetry is sufficient, the coordinate plane can always be made an exact
symmetry plane by the use of PHI2. If for example the Euler mesh has angles 0 and 2.5, PHI2 has to
be set to -1.25 to get exact symmetry.
Main Index
DYPARAM,AXREMAP 1671
2D Axial symmetric Euler archive remap - SOL 700
DYPARAM,AXREMAP 2D Axial symmetric Euler archive remap - SOL 700
Allows import of a 2D axial symmetric Euler archive into a 3D simulation.
Format:
1 2 3 4 5 6 7 8 9 10
DYPARAM AXREMAP x0 y0 z0 xn yn zn range
Example:
DYPARAM AXREMAP 0.0 0.5 0.5 1. 0. 0.
Describer Meaning
x0,y0,z0 x,y,z-coordinate of the point at which the 2D axial symmetric mesh is remapped. (Real;
Default = 0.0)
xn,yn,zn Unit vector that specifies the direction of the axial axis of the 2D axial symmetric mesh
as viewed in the 3D mesh. (Real; Default = (1.0. , 0.0, 0.0 )
range Only material whose distance from the axial axis is smaller than "range" will be
initialized with the 2D axi-symmetric Euler archive. (Real, Default = 1e+20)
Remarks:
1. Since 2D axial symmetric simulations run much faster than 3D simulation it can save much cpu time
to do the first part of the simulation with a 2D axial symmetric mesh. Afterwards the 2D-axial
symmetric Euler archive is imported into the 3D simulation. By default the 2D axial symmetric
archive will not be expanded in 3D. To enable this expansion DYPARAM, AXREMAP has to be
used. It is useful for blast wave simulations. The 2D axial symmetric simulation has to be terminated
before the blast wave approaches any 3D structure.
2. This import of Euler archives is done by means of the eid option in the pth file.
3. To generate axial symmetric meshes DYPARAM,AXIALSYM can be used.
Main Index
1672 DYPARAM,BULKL
Linear Bulk Viscosity Coefficient- SOL700
DYPARAM,BULKL Linear Bulk Viscosity Coefficient- SOL700
Defines the default value of the linear bulk viscosity coefficient.
Format:
DYPARAM,BULKL,VALUE
Example:
DYPARAM,BULKL,0.1
Describer Meaning
value Value of the linear coefficient in the bulk viscosity equation. (Real ≥ 0.0; default=0.0)
Remarks:
1. The default value works well for the majority of problems.
2. The value defined on this entry is used as the default whenever BULKL is blank on the MATBV
material entry.
3. When BULKL is specified on a material definition entry, the default value is overridden for that
specific material.
Main Index
DYPARAM,BULKQ 1673
Quadratic Bulk Viscosity Coefficient - SOL700
DYPARAM,BULKQ Quadratic Bulk Viscosity Coefficient - SOL700
Defines the default value of the quadratic bulk viscosity coefficient.
Format:
DYPARAM,BULKQ,VALUE
Example:
DYPARAM, BULKQ,1.6
Describer Meaning
value Value of the quadratic coefficient in the bulk viscosity equation. (Real ≥ 0.0; default=0.0)
Remarks:
1. The default value works well in the majority of situations.
2. The value defined on this entry is used as the default whenever BULKQ is blank on the MATBV
material entry.
3. When BULKQ is specified on a material definition entry, the default value is overridden for that
specific material.
Main Index
1674 DYPARAM,BULKTYP
Bulk Viscosity Type - SOL700
DYPARAM,BULKTYP Bulk Viscosity Type - SOL700
Defines the default type of bulk viscosity.
Format:
DYPARAM,BULKTYP,option
Example:
DYPARAM, BULKTYP,DYNA
Describer Meaning
Option bulk viscosity type. (Character; Default=DYNA)
DYNA Standard DYNA3D model
DYTRAN Enhanced DYNA model
Remarks:
Main Index
DYPARAM,CFULLRIG 1675
Converts 123456 Constraints to FULLRIG on RBE2 - SOL700
DYPARAM,CFULLRIG Converts 123456 Constraints to FULLRIG on RBE2 - SOL700
Converts all 123456 constraints to the FULLRIG option on all entries. Used in SOL 700 only.
Format:
DYPARAM,CFULLRIG,value
Example:
DYPARAM,CFULLRIG,NO
Describer Meaning
value Activation flag. (Character; Default=YES)
YES 123456 constraints are converted to FULLRIG.
NO 123456 constraints are not converted to FULLRIG.
Main Index
1676 DYPARAM,CLUFLIM
Limiter of Volume Stain Rate for Clumps - SOL700
DYPARAM,CLUFLIM Limiter of Volume Stain Rate for Clumps - SOL700
In some cases, airbag runs become instable. Often, this is caused by a much too large volume strain rate
in a clump that consists of too many elements. These clumps typically have a small average volume
uncovered fraction. The large volume strain rate causes a huge compression work and this blows up the
specific internal energy. When this happens it is clearly visible in the OUT file and in the results. This
DYPARAM activates a limiter that scales down the volume strain rate for clumps with a small average
uncovered fraction. It can keep an instable airbag run stable, just like PARAM, VELMAX can keep
runs stable. Used in SOL 700 only.
Format:
DYPARAM,CLUFLIM,value
Example:
DYPARAM,CLUFLIM,0.22
Describer Meaning
value The volume strain rate in a clump will be reduced when the average Uncovered Fraction
of elements in a CLump falls below CLUFLIM. CLUFLIM has to be smaller than
FBLEND. The default value of FBLEND is 0.66 giving a value of 0.22 for CLUFLIM.
For more details on FBLEND refer to PARAM,FBLEND. (0<Real<FLBEND;
default=FBLEND/3)
Remarks:
DIV
1. The Volume strain rate ---------- in clumps will be limited by
t
DIV
----------
U DIV
= MIN 1 --------------------------- ----------
t Lim CLUFLIM t
Here, U is the average uncovered fraction of elements in the clump as given by
eleclump Uncf el Vol el
U = ----------------------------------------------------------
eleclump
Here Uncf and Vol denote the uncovered fraction and volume of an element inside the clump.
Therefore, only when the average uncover fraction falls below CLUFLIM, the volume strain rate is
limited.
Main Index
DYPARAM,CLUMPENR 1677
Switch for Kinetic Energy Calculation Scheme of Blended Clumps - SOL700
DYPARAM,CLUMPENR Switch for Kinetic Energy Calculation Scheme of Blended
Clumps - SOL700
Sets the definition of the kinetic energy calculation method for Eulerian blended clumps. Used in SOL 700
only.
Format:
DYPARAM,CLUMPENR,value
Example:
DYPARAM,CLUMPENR,SUM
Describer Meaning
value Flag for CLUMPENR.(Character; default=AVERAGE)
AVERAGE The kinetic energy of a Eulerian blended clump is calculated from the
average velocity of the clump. The average velocity of the blended clump
is computed as the sum of the momentum of each member of the clump
divided by the total clump mass.
SUM The kinetic energy of a Eulerian blended clump is calculated as the sum of
the kinetic energy of each member of the clump.
Main Index
1678 DYPARAM,CONM2OUT
CONM2 Summary Output - SOL700
DYPARAM,CONM2OUT CONM2 Summary Output - SOL700
Determines if a summary of concentrated masses and their energy and momentum is written to the output
file. Used in SOL 700 only.
Format:
DYPARAM,CONM2OUT,value
Example:
DYPARAM,CONM2OUT,NO
Describer Meaning
value Flag for COMN2OUT. (Character; default=NO)
NO No information about concentrated masses is written to the cycle and
material summaries on the output file.
YES A complete summary of concentrated masses including the associated
mass, momentum, and energy is written to the output file.
Remarks:
1. When DYPARAM,CONM2OUT is set to NO, there is no summary of the concentrated mass. This
means that the mass, momentum, and energy of the concentrated masses, is not added to the material
and cycle summaries. Setting DYPARAM,CONM2OUT,NO saves memory and CPU time.
Main Index
DYPARAM,CONTACT 1679
Sets Defaults for CONTACT - SOL700
DYPARAM,CONTACT Sets Defaults for CONTACT - SOL700
Defines certain defaults for the contact definitions. Used in SOL 700 only.
Format:
DYPARAM,CONTACT,option,value1,value2,value3,value4,value5,value6
Example:
DYPARAM,CONTACT,VERSION,V4
Describer Meaning
VERSION Defined the default version of contact. Only support value1. (Character; required)
V4 General Contact algorithm of SOL700
BELT Suited for modeling contact between a belt element and a rigid structure.
Primary secondary contact only.
The contact logic doesn't apply a contact force, but applies an enforced
displacement and velocity that keeps the secondary nodes exactly on top of
the primary face.
The secondary node does not slide relative to the primary face when the
friction coefficient (FS) is set to 1E20.
BELT1 Identical to BELT algorithm, except that the secondly nodes are initially
repositioned on top of the closest primary face.
DRAWBEAD Suited for modeling a drawbead.
THICK Defines the default value for THICK. Only support vaule1. (Real>0.0; required.)
GAP Defines the default value for GAP. Only support vaule1. (Real>0.0; required.)
LIMITS Definition of a three dimensional contact region where contact in the analysis model takes
place. Significant CPU time savings can be achieved when used in adaptive contact. 6
values are used to define area.
The format of this option is
DYPARAM,CONTACT,LIMITS,xmin,xmax,ymin,ymax,zmin.zmax.
(Real; default=1.0E20 for xmax, ymax and zmax and -1.0E20 for xmin, ymin and zmin)
XMIN(value1) Lower limit in x-direction where main contact occurs
XMAX(value2) Upper limit in x-direction where main contact occurs
YMIN(value3) Lower limit in y-direction where main contact occurs
YMAX(value4) Upper limit in y-direction where main contact occurs
ZMIN(value5) Lower limit in z-direction where main contact occurs
ZMAX(value6) Upper limit in z-direction where main contact occurs
DAMPING Defines the default for usage of damping. Only support value1. (Character; required)
YES Use damping in CONTACT
Main Index
1680 DYPARAM,CONTACT
Sets Defaults for CONTACT - SOL700
Describer Meaning
NO Not use damping in CONTACT
COPOR Activates contact based porosity. Only support value1. (Character; default=NO)
YES Use porosity in CONTACT
NO Not use porosity in CONTACT
DAMPFOR Defines whether the noncontact forces acting on the grid points need to be taken into
account in the contact damping. This option is only used if DAMPING is set to YES. This
option prevents large penetrations that might occur when the forces acting on the grid
points tend to push them into the contact surface. This happens, for example, in airbag
analyses, where a large pressure exists inside the bag. Only support value1. (Character;
required)
YES Damping is considered in noncontact forces
NO Damping is not considered in noncontact forces
DYNA The following parameters of the contact definition get the default values consistent with
Dyna. (Character ; required)
THICK 1.0
THICKOF 0.0
INFO Information on the contact state of grid points G1,G2,... is printed to ASCII files, named
CNT. This information can be useful in debugging models with contacts. Supports many
values as you want. (Integer > 0; required.)
EVIEW Defines the default value of the view angle of Edge to Edge contacts. The value of the angle
must be in degrees. Only support value1. (Real > 0.0; required)
FORCE Controls the contact forces on the grid points. Supports value1, value2, value3. See
Remark 1. (value1: Integer > 0; default=10, value2: Real > 0; default=10.0; value3:
Character; default=ZERO)
NMCYC Frequency check of contact force; applied on each grid point. (Integer > 0;
(value1) default = 100).
SCALE Scale factor for maximum allowable contact force.
(value2) F max = SCALE F last check (Integer > 0; default = 10)
TYPE Contact force limitation. (Character; default=ZERO)
(value3)
ZERO 0.0
FMAXF Update contact limit forces using new contact forces (where
non allowable forces are not taken into account)
Main Index
DYPARAM,CONTACT 1681
Sets Defaults for CONTACT - SOL700
Remarks:
1. The DYPARAM,FORCE check takes up some CPU time and, therefore, do not make this value too
small. Furthermore, when the check is performed at each cycle, the force will be too limited and the
bag will not unfold. Recommended values are between 5 and 200. The same problems can occur for
SCALE(value2). In case this value is too small, the bag will not unfold either. The minimum
value for air bags that should be used is about 5. The maximum is about 20. When this value is too
big a difference will not be noticed. TYPE(value3)=ZERO is a bigger restriction. In some cases,
TYPE=FMAXF might yield better results.
Main Index
1682 DYPARAM,COSUBMXT
Time-dependent Subcycle Limit in Euler/Lagrange Coupling - SOL700
DYPARAM,COSUBMXT Time-dependent Subcycle Limit in Euler/Lagrange Coupling - SOL700
Defines the maximum number of subcycles that can occur in Euler/Lagrange coupling. During a subcycle,
the geometry of the coupling surface is not updated. This number can vary in time and is given by a table.
Used in SOL 700 only.
Format:
DYPARAM,COSUBMXT,value
Example:
DYPARAM,COSUBMAT,10
Describer Meaning
value TABLED1 ID that specifies for each time the maximum number of time steps between
updating the coupling surface geometry in the coupling calculations. (Integer > 0;
required)
Remarks:
1. Updating the coupling geometry takes a lot of CPU time. Subcycling gives substantial savings in CPU
time for coupled calculations.
2. The smaller the value of this parameter, the greater the accuracy of the analysis and the greater the
cost. Conversely, larger values offer significant CPU savings, but very large values give incorrect
results.
3. If the geometry of the coupling surface is changing rapidly, smaller values on the table should be used.
Main Index
DYPARAM,COUFRIC 1683
Coupling Surface Friction for Nonmetallic Eulerian Solids - SOL700
DYPARAM,COUFRIC Coupling Surface Friction for Nonmetallic Eulerian Solids - SOL700
Defines the Coulomb friction scheme. Please check DYPARAM,COHESION too. Used in SOL 700 only.
Format:
DYPARAM,COUFRIC,value
Example:
DYPARAM,COUFRIC,NO-METAL
Describer Meaning
value Flag for COUFRIC usage. (Character; default=METAL)
METAL A tensile condition will result in zero load on the structure part on cohesive
coupling.
NO- a tensile load was applied in tensile condition on cohesive coupling.
METAL
Remarks:
1. Only used when Coulomb friction coefficients have been specified for a COUPLE entry.
Main Index
1684 DYPARAM,COHESION
Cohesion for Coulomb Friction - SOL 700
DYPARAM,COHESION Cohesion for Coulomb Friction - SOL 700
Allows friction and sticking during tensile conditions at the coupling surface.
Format:
DYPARAM,COHESION,MAXSTRS,FRIC,REFVEL
Example:
DYPARAM,COHESION,8.0e+10,8.0e+5,20.0
Describer Meaning
MAXSTRS Maximal normal stress. Allows tensile stresses at the coupling surface as long as the normal
stress does not exceed MAXSTRS. (Real > 0)
FRIC Friction stress under tensile conditions. (Real > 0)
REFVEL Reference value for velocity. (Real > 0)
Remarks:
1. Only used when coulomb friction coefficients have been specified for a COUPLE entry.
2. During tension any relative tangential velocity between coupling surface and Eulerian material will
yield a shear stress whose magnitude equals:
V rel,tangential
FRIC min 1 -----------------------------
REFVEL
This is a viscous-like friction law.
3. This shear force opposes the relative tangential movement along the coupling surface.
Main Index
DYPARAM,DMPOPT 1685
Sets DMP option - SOL700
DYPARAM,DMPOPT Sets DMP option - SOL700
Sets DMP option. Used in SOL 700 only.
Format:
PARAM,DMPOPT,value1,value2,value3,value4
Example:
PARAM,DMPOPT,2,1
Describer Meaning
Value1 Set dmp option. (Integer>0, default=1)
1 Only Euler dmp is activated,
2 Only Lagrangian dmp is activated.
3 Both, Euler and Lagrangian dmp are activated.
Value2 Set contact dmp type. (Integer>0, default=1).
1 Serial mode in contact
2 Parallel mode in contact (check value4)
Value3 Set number of printing summary for each item. (Integer ≥ 0, default=0).
0 Print all summaries (see Remark 2.)
Value4 Set parallel mode type in contact. (Integer>0, default=not used).
-1 Use the same contact domain partitioning as the element domain
partitioning and all primary surfaces must be made by MATRIG definition
(see Remark 3.)
Remarks:
1. To set partitioning manually, check DYPARAM,EULERPR for Euler partitioning and
DYPARAM,LAGPR for Lagrangian partitioning.
2. Printing out too large summaries of each item can cause unexpected failure of job under certain
conditions. This option can limit to certain number of summary information to avoid such failure.
3. When the same contact domain partitioning as the element domain partitioning is used, the dmp
performance of contact may not be enhanced. However, when all deformable grid points are assigned
in secondary body and they are involved to contact at the similar time, the dmp performance of
contact will be enhanced as expected. For example, stamping of sheet metal may show a good
performance.
Main Index
1686 DYPARAM, DUMSEGS
Creating dummy segments for the auto coupling approach - SOL700
DYPARAM, DUMSEGS Creating dummy segments for the auto coupling approach - SOL700
Specifies how holes in the coupling surface are meshed. It is only used for the auto coupling approach. This
approach is activated by DYPARAM, AUTOCOUP.
Format and Example:
DYPARAM,DUMSEGS,INTERNAL
Describer Meaning
INTERNAL Meshes internal holes with a triangular dummy segment mesh [YES,NO] Default NO
Remarks:
1. With the auto coupling method, holes are partially or completely meshed with dummy segments.
With option NO the standard method of creating dummy segment is used. For details see chapter 8
of the SOL700 User’s Guide. In this standard method holes are partially meshed with dummy
segments. For an example refer to Figure 20 of Chapter 8. For holes that rotate, have arbitrary form
or show large deformations, the standard method of creating dummy segments can cause the
simulation to terminate with messages like
%E-P4307807-P4_SUBELM_MESH_CURVED_HOLES, , ,(13), DUMMY SURFACE
CANNOT BE TRIANGULATED THIS IS PROGRAM ERROR. PLEASE CONTACT
MSC. USING PARAM,DUMSEGS,ON CAN SOLVE THIS TRIANGULATION
PROBLEM.
%E-P4309907-V4_SUBELEM_CONNECT_EXTENDED_GPS, , DUMMY SURFACE
CANNOT BE TRIANGULATED THIS IS PROGRAM ERROR. PLEASE CONTACT
MSC. USING PARAM,DUMSEGS,ON CAN SOLVE THIS TRIANGULATION
PROBLEM.
In that case PARAM,DUMSEGS,ON can maintain a good dummy surface. The quality of the
dummy surface can be checked by requesting a coupling surface archive. This is done by using the
CPLSURFS command and by putting option DUMMY of DYPARAM, AUTOCOUP to ON. For
all holes that are not internal holes, the standard method is used.
Main Index
DYPARAM,ELDLTH 1687
- SOL700
DYPARAM,ELDLTH - SOL700
Print initial time step sizes for elements in the first cycle in SOL 700.
Format:
DYPARAM,ELDLTH,<value>
Example:
DYPARAM,ELDLTH,1
Describer Meaning
value Number of elements to be output. (Integer)
0 First 100 elements with the smallest time step sizes are printed.
1 The governing time step sized for all elements are printed. (Default)
Main Index
1688 DYPARAM,EULERCB
Euler Domain Decomposition Control - SOL700
DYPARAM,EULERCB Euler Domain Decomposition Control - SOL700
Divides a Euler domain into several cubes. For SOL 700 only
Format:
DYPARAM,EULERCB,NELCUBE,NBX,NBY,NBZ
Example:
DYPARAM,EULERCB,2000,2,2,2
Describer Meaning
NELCUBE The number of elements per cube. (Integer; Default = 0)
NBX The number of cubes in the x-direction. See Remark 2. (Integer; Default = 0)
NBY The number of cubes in the y-direction. (Integer; Default = NBX)
NBZ The number of cubes in the z-direction. (Integer; Default = NBX)
Remarks:
1. By setting NELCUBE equal to 2000 optimal use is made of memory caching during Euler
computation. This may give a speedup of 1.5. When using adaptive meshing with dmp additional
Euler cubes are created during the simulation. To keep the total number of cubes that are created
within bounds the initial number of cubes should be limited to 100.
2. Defining NBX overrules the definition of NELCUBE.
3. Only supports Euler domains created by MESH,BOX. Limitations are:
• No PEULERx/CHEXA's
• No FLOW or BARRIER that use the BCID option are allowed. All FLOW and BARRIER
entries must use either the DIR option or the XMIN,YMIN,ZMIN, XMAX,YMAX,ZMAX
option to define the Euler MESH boundaries.
Main Index
DYPARAM,EULERPR 1689
Euler Cube Partition Control - SOL700
DYPARAM,EULERPR Euler Cube Partition Control - SOL700
Divides a Euler domain into several cubes. For SOL 700 only
Format:
DYPARAM,EULERPR,PROCDIR,NPX,NPY,NPZ
Example:
DYPARAM,EULERPR,USER,2,2,2
Describer Meaning
PROCDIR This directive controls the way cubes are distributed across processors. The effect can be
checked by checking the Eulerian output variable PARTITION. (Character; Default = X)
X Partition in global X direction first.
Y Partition in global Y direction first.
Z Partition in global Z direction first.
USER Define user defined partitioning
SIMPLE Partition Euler cubes in a simple pattern.
ORB Partitions using orthogonal recursive bisection
NPX The number of cubes in the x-direction. Required for PROCDIR=USER. (Integer;
Default = 0)
NPY The number of cubes in the y-direction. (Integer; Default = NPX)
NPZ The number of cubes in the z-direction. (Integer; Default = NPX)
Remarks:
1. There are several ways to distribute cubes across processors. Some ways may lead to bad load
balancing. To avoid this it is possible to control the way Euler cubes are distributed across processors
by defining PROCDIR.
2. When option PROCDIR=USER, the values for NBX, NBY and NBZ must be such that NBX is
equal or a multiple of NPX, NBY is equal or a multiple of NPY and NBZ is equal or a multiple of
NPZ. Also for this option, NPX*NPY*NPZ must be equal to the number of processors used in the
cluster.
3. For option PROCDIR=SIMPLE, the values NBX, NBY and NBZ on DYPARAM,EULERCB must
be such that NBX*NBY*NBZ is equal or a multiple of the number of processors used. For instance,
if the number of processors in the cluster is 4, NBX*NBY*NBZ must be equal to either 4 or 8 or 12,
etc. Otherwise the calculation will terminate prematurely with an error message.
4. Only supports Euler domains created by MESH,BOX. Limitations are:
• No MESH,ADAPT and no PEULERx/CHEXA’s
Main Index
1690 DYPARAM,EULERPR
Euler Cube Partition Control - SOL700
• No FLOW or BARRIER that use the BCID option are allowed. All FLOW and BARRIER
entries must use either the DIR option or the XMIN,YMIN,ZMIN, XMAX,YMAX,ZMAX
option to define the Euler MESH boundaries.
5. With the orthogonal recursive bisection method the mesh is repeatedly cut in half. Each cut is along
a coordinate direction and the direction of the cut is chosen to minimize the communication cost. To
illustrate this method consider for example a mesh with 200,150 and 50 elements in respectively the
x,y and z-direction. When split in x-direction the number of Euler faces at the split will be 150*50 =
7500. When splitting across the y-direction it will be 200*50=10000 and for the z-direction it will be
200*150=30000. Since the x-split has the smallest number of faces at the split, the x-split has the
smallest communication cost. Therefore the ORB scheme will select the x-split. At the x-split there
are two mesh parts. Both have 100*150*50 elements. Now a split in y-direction will give the minimal
communication costs. This process of bisecting is continued until the number of sub meshes equals
the number of CPU's.
Main Index
DYPARAM,EULTRAN 1691
Switch for Euler Transport Scheme of the Multi-Material Solver and the Single Material Strength Solver - SOL700
DYPARAM,EULTRAN Switch for Euler Transport Scheme of the Multi-Material Solver and the Single
Material Strength Solver - SOL700
Sets the definition of the face velocity used in the transport scheme of the Multi-material solver and the single
material strength solver. Used in SOL 700 only.
Format:
DYPARAM,EULTRAN,option1,option2
Example:
DYPARAM,EULTRAN,AVERAGE,FAIL
Describer Meaning
Option1 IMPULSE The face velocity is impulse weighted. (Character; Default = IMPULSE)
AVERAGE The face velocity is a simple average.
Option2 NOFAIL Failure is transported. See Remark 5. and 6. (Character; Default =
NOFAIL)
FAIL Failure is transported. See Remark 5. and 6.
Remarks:
1. The default value of IMPULSE is sufficient for most Euler problems. Especially problems where the
reference density of the different materials varies widely (e.g., orders of magnitude) are required to use
the default option.
2. In case the IMPULSE option (default) is used, the Euler transport scheme computes that the face
velocity uses an impulse weighted average of the material velocity in the left and the right element
adjacent to the face.
3. In case the AVERAGE option is used, the Euler transport scheme computes the face velocity as one-
half times the sum of the material velocity in the left and the right element adjacent to the face.
4. Does not apply to the single material hydrodynamic solver and the Roe solver.
5. The option FAIL requires a failure model for at least one Eulerian material. In case of the default
NOFAIL then failed Euler material can support shear stress again as soon as new material enters the
Euler element. Thus the information that part of the material inside the Euler element has failed is
lost. The option FAIL activates transport of fail fraction and thereby keeps track of material that has
failed. In this way only the failed part of the element can no longer supports shear stresses. In more
detail, the yield stress in the material is scaled by (1-failfrac), where failfrac denotes the fail fraction of
the material. The fail fraction of the first material in an element can be retrieved from Euler archive
or time-history results files in the variable DAMAGE. The value of fail fraction DAMAGE is between
zero and one.
6. Option FAIL cannot be combined with the Johnson-Cook failure model (FAILJC).
Main Index
1692 DYPARAM,EUSUBMAX
- SOL700
DYPARAM,EUSUBMAX - SOL700
Defines the maximum number of subcycles that can occur in the Euler solver. During a subcycle, the Euler
computations are skipped. Used in SOL 700 only.
If coupling surface computations are more expensive than Euler computations than use of
PARAM,COSUBMAX should be considered first. In that case the optimal setting of EUSUBMAX is
LINKCS=BOTH and DFVUMAX is blank.
As with PARAM,COSUBMAX use of EUSUBMAX can lead to loss of accuracy for certain simulations. It is
recommended to validate the use of EUSUBMAX by comparing the difference in results between using
EUSUBMAX and not using EUSUBMAX for some typical target simulations.
Format
DYPARAM,EUSUBMAX,NSUBMAX,DFVUMAX,LINKCS
Example:
DYPARAM,EUSUBMAX,5
Describer Meaning
NSUBMAX NSUBMAX, The maximum number of time steps between updating Euler variables.
(Integer > 0; Default = 0)
DFVUMAX Maximum allowed increase in uncovered volume fraction between to subsequent Eulerian
computations. (Real > 0; Required when COSUBMAX is present. Leave blank when
COSUBMAX is not present.)
LINKCS Specifies interactions between Euler subcycling and coupling surface subcycling.
EUSUBMAX can be used with COSUBMAX. LINKCS specifies how the two subcycling
processes influence each other. (Character; Default = BOTH)
BOTH The Euler computations will not be skipped when the coupling surface
computations has been done. On the other hand if an Euler computation
is to be done, also a coupling surface computation is done. The number
of time that the Euler computation I skipped equals the number of times
that the coupling surface computation has been done.
COUPLE If an Euler computation is to be done, also a coupling surface
computation is done.
EULER If a coupling surface computation is to be done, also a Euler computation
is done.
NONE The Euler subcycling and coupling surface subcycling are independent.
DFVUMAX has to be defined.
Main Index
DYPARAM,EUSUBMAX 1693
- SOL700
Remarks:
1. Updating the coupling geometry takes a lot of CPU time. Subcycling gives substantial savings in CPU
time for coupled calculations.
2. The smaller the value of DFVUMAX, the greater the accuracy of the analysis and the greater the cost.
Conversely, larger values offer significant CPU savings, but very large values give incorrect results.
3. When the Euler time step is considerably larger than the Lagrange time step it can be worthwhile to
skip the Euler computation for several cycles. This can reduce computational costs considerable.
4. Skipping the Euler computation for several cycles, leads to postponed time steps. When the Euler
computations are done these have to be taken into account by fluxing with an accumulated time step.
Skipping the Euler computation is stopped as soon as the accumulated time step will become larger
than the stable Euler time step. The total number of skipped cycles is limited by NSUBMAX.
NSUBMAX is required input.
5. In skipping the Euler computation also the movement of the coupling surface has to be monitored.
To estimate this movement the change in uncovered fraction of the elements is used. If the change in
uncovered volume fraction from one cycle to the other is larger than DFVUMAX than the Euler
computation is not skipped that cycle. DFVUMAX has to be left blank if coupling surface subcycling
is used. Coupling surface subcycling already monitors the movement of the coupling surface.
Choosing too large values for DFVUMAX can make results inaccurate.
6. EUSUBMAX is only supported by the multi-material Euler solver and the standard single material
Euler solver. It is not supported by the Roe solver.
Main Index
1694 DYPARAM,EUSUBCYC
Growth or Subcycling Interval in Euler Computations - SOL700
DYPARAM,EUSUBCYC Growth or Subcycling Interval in Euler Computations - SOL700
Controls the growth of the subcycling interval in Euler computations. Used in SOL 700 only.
Format:
DYPARAM,EUSUBCYC,value
Example:
DYPARAM,EUSUBCYC,100
Describer Meaning
value Maximum growth of the subcycling interval. (Integer > 0; default=1)
Remarks:
1. The subcycling algorithm automatically estimates the number of subcycles to be used. This is updated
throughout the calculation. This parameter controls how much the number of subcycles can grow.
For example, EUSUBCYC is set to 1, and the current number of time steps between updates of the
Euler variables. If Dytran estimates that the subcycling interval should be 7, the subcycling interval is
increased by 1 until a value of 7 is reached.
2. There is no control on the amount by which the subcycling interval can decrease.
Main Index
DYPARAM,FAILDT 1695
Element Time-step Based Failure Model - SOL700
DYPARAM,FAILDT Element Time-step Based Failure Model - SOL700
Defines the property of a failure model where element failure occurs when the element’s time step falls below
the specified limit. Used in SOL 700 only
Format:
DYPARAM,FAILDT,value
Example:
DYPARAM,FAILDT,1.0E-3
Describer Meaning
value Minimum time-step. (Real > 0.0; default=1.0E-20)
Remarks:
1. This failure model is valid for all Lagrangian solid (CHEXA)and shell (CQUAD4) elements.
2. All elements for which the time step falls below the specified value are removed from the
computation.
3. Although it is not usually necessary to limit the element time-step for Lagrangian elements, there are
occasions where specifying a minimum time-step can be advantageous for computational
performance, for example, when adaptive contact is used.
4. Note that this parameter should be used with care as you may influence the results of the analysis
when you set the time-step criterion to a too high value. You then run the risk that elements are
removed from the analysis while they may still be relevant.
Main Index
1696 DYPARAM,FAILOUT
Failed Element Output Parameter - SOL700
DYPARAM,FAILOUT Failed Element Output Parameter - SOL700
Defines whether failed elements are written to the output file (ARCHIVES). Used in SOL700 only.
Format:
DYPARAM,FAILOUT,value
Example:
DYPARAM,FAILOUT,NO
Describer Meaning
value Flag for FAILOUT. (Character; default=YES)
NO Failed elements are not written to the archive files.
YES Failed elements are written to the archive files.
Remarks:
1. When the NO option is chosen, the archives are written out as one file per requested time step
regardless of the number set in the SAVE command for the archive files that appear in the Case
Control Section. Please check $S700.
Main Index
DYPARAM,FLOWMETH 1697
Flow-Method Between Two Euler Domains Across Open Areas in Coupling Surfaces - SOL700
DYPARAM,FLOWMETH Flow-Method Between Two Euler Domains Across Open
Areas in Coupling Surfaces - SOL700
Defines the method for simulating material flow between two Euler domains across open areas in coupling
surfaces. Used in SOL 700 only.
Format:
DYPARAM,FLOWMETH,value
Example:
DYPARAM,FLOWMETH,POLPACK
Describer Meaning
value Flag for FLOWMETH. (Character; default=NO)
POLPACK The facets in the coupling surfaces that represent an open area are
subdivided into smaller facets, with each connecting exactly to one Euler
element in the first Euler domain and to exactly one Euler element in the
second Euler domain. Material flow takes place across these smaller,
subdivided facets (POLPACKs). This is the most accurate method.
FACET The facets in the coupling surfaces that represent an open area are not
subdivided. Material flow takes place across the original facets. If these
facets are too large in relation with the Euler elements, the method
becomes inaccurate. Material flow across one facet can involve several Euler
elements on both sides of the hole and averaging occurs.
Remarks:
1. This parameter applies to simulations where:
• Two coupling surfaces share a common set of facets.
• Each coupling surface has own Euler domain.
• Material flows from one Euler domain into the other through the open area represented by the
common set of facets.
Flow only occurs if:
• The common facets are defined as ‘open’, using PORFCPL.
• The common facets open up due to failure of a shell structure, using COUP1INT.
Examples simulations are:
• Holes between air bag compartments.
• Holes between containers filled with gas or liquid.
• Open area between the top of a fuel-tank baffle and the fuel-tank skin.
Main Index
1698 DYPARAM,FLOWMETH
Flow-Method Between Two Euler Domains Across Open Areas in Coupling Surfaces - SOL700
• Open area in-between wide straps inside an air bag.
• Failure of walls in between aircraft wing compartments.
• Failure of tank armor by a blast wave.
• Etc.
2. The following table summarizes what input cards support the simulation of material flow between
two Euler domains across open areas in coupling surfaces:
Material
flow COUP1INT/ COUP1FL
through a FLOW- FLOW- PORFLCPL PORFLCPL (Failure of shell
coupling METOD= METHOD (velocity (Pressure elements creates the
Euler Solver surface POLPACK =FACET based) based) opening)
HYDRO YES YES NO YES YES Only for flow
method = polpack
HYDRO-Roe YES YES YES YES YES YES
solver-1st
Order
HYDRO-Roe YES YES YES YES YES YES
solver- 2nd
Order
MMHYDRO YES YES NO YES NO Only for flow
method = polpack
STRENGTH NO - - - - -
MMSTREN YES YES NO YES NO Only for flow
method = polpack
3. The Euler domains are shown below with the support types for each:
FLOW-METHOD=POLACK FLOW METHOD = FACET
YES No
MESH TYPE = ADAPT
MESH TYPE = BOX YES YES
Modeling of CHEXA elements No YES
4. A Euler domain is associated with a coupling surface by specifying the MESHID or SET1ID on the
COUPLE option.
5. FLOWMETH = POLPACK has the following limitations:
The entries NSTGP and NSTEL on all MESH entries should be left blank. It is not allowed to
specify for any MESH entry the starting element number or starting grid point number.
• There are restrictions on output requests.
Main Index
DYPARAM,FLOWMETH 1699
Flow-Method Between Two Euler Domains Across Open Areas in Coupling Surfaces - SOL700
• Flow faces and wallets are not supported while FLOWDEF is supported.
• Viscosity is not supported
A case where these limitations require the use of FLOWMETH = FACET is when the Euler
elements are generated in Patran, not using the MESH option, and one or more of the following
options is used:
• FLOW boundaries are defined on some Euler faces.
• WALLET boundaries are defined on some Euler faces.
• Viscosity is defined.
Main Index
1700 DYPARAM,GEOCHECK
Define Geometry Consistency Check - SOL700
DYPARAM,GEOCHECK Define Geometry Consistency Check - SOL700
This parameter forces a check of the geometry for consistent connectivity of the defined hexagonal elements
and correction if needed. Used in SOL 700 only.
Format:
DYPARAM,GEOCHECK,value
Example:
DYPARAM,GEOCHECK,ON
Describer Meaning
value Flag for activating GEOCHECK. (Character; default=OFF)
ON Geometry consistency check is performed.
OFF No geometry consistency check is performed.
Remarks:
1. The defined geometry is checked for consistent connectivity of the hexagonal elements. If an
inconsistency is detected, the connectivity is corrected. CFACE entries with references to elements
that have been corrected are corrected as well.
2. If a hexagonal mesh is generated with other commercial preprocessors, this parameter can correct the
connectivity of the hexagonal elements in case problems are encountered with face generation or
volume computation.
Main Index
DYPARAM,FASTCOUP 1701
Fast Coupling Algorithm - SOL700
DYPARAM,FASTCOUP Fast Coupling Algorithm - SOL700
Defines the fast coupling algorithm. Used in SOL 700 only.
Format:
DYPARAM,FASTCOUP,option1,option2,option3,option4,option5,option6,option7
Example:
DYPARAM,FASTCOUP,INPLANE,FAIL
Describer Meaning
Option1 NO Fast coupling interaction is turned off. (Character; Default = INPLANE)
INPLANE Small offset for inplane coupling surface segments.
NOFFSET No offset for inplane coupling surface segments
Option2 NOFAIL No failure of the coupling surface. (Character; Default = NOFAIL)
FAIL Failure of the coupling surface will be taken into account.
Option3 Euler check algorithm. (Character; Default = NOCHKEUL)
CHKEUL Checking whether all segments of the coupling surface are fully inside Euler
elements.
NOCHKEU No checking
L
Option4 Euler update algorithm. (Character; Default = ALL)
NEARONLY Do the full coupling surface only in the first cycle. In subsequent cycles
only update elements and faces that are near the coupling surface.
ALL Do the full coupling surface computation each cycle.
Option5 Controls coupling surface computations when there are multiple cubes defined with
DYPARAM,EULERCB. (Character; Default = NONE)
NONE All coupling surface computations are done for each cube.
FACES The face cover fraction computation is done in one go for all cubes. The
other coupling computations are still done per cube.
POLPK The polpack computation efficiently handles multiple cubes. The other
coupling computations are still done per cube.
ALL All coupling surface computations efficiently handle cubes.
Main Index
1702 DYPARAM,FASTCOUP
Fast Coupling Algorithm - SOL700
Describer Meaning
Option6 In the coupling surface computations it is determined which structural segments intersect
the Euler mesh. This is done by looping across all structural segments. For dmp each cpu
has only part of the Euler mesh. Therefore for many segments it is known beforehand that
they will not intersect the Euler mesh of the cpu and can be skipped at an early stage of the
computation. Option 6 activates this skipping. (Character; Default = ON)
OFF For dmp each CPU goes over all segments.
ON Each CPU skips all segments that do not intersect the Euler mesh of the
CPU.
Option7 Each coupling surface segment has to be intersected with the Euler elements and Euler
faces. For large Euler meshes a substantial amount of checking has to be done do find the
intersecting elements and faces. By dividing the Euler mesh in search boxes the costs of this
checking is kept to a minimum. Especially for large Euler meshes combined with large
coupling surface this checking can become expensive and then the use of search boxes can
significantly reduce the costs. For Euler meshes of less than 100000 elements the use of
search will boxes have little effect. (Character; Default = ON)
OFF Search boxes are not used.
ON Search boxes are used.
Remarks:
1. The fast coupling algorithm is always turned on by default. In order to use general coupling,
option1=NO should be used.
2. When option1 is set to INPLANE or when option 1 is blank, a small offset is given to coupling
surface segments that are on top of a face of an Eulerian element. This is done because coupling
surfaces segments on Eulerfaces make the Euler element volume computation invalid. Also boundary
conditions on these segments are not correctly imposed. The net effect of these problems is
unpredictable. The problem can either run correctly, or remain stable but give false results or become
instable.
3. Option2 can only be used in combination with either PARAM,LIMITER,ROE or MMHYDRO or
MMSTREN. The coupling surface must consist of CQUADs and/or CTRIAs and a failure model
for the material of the surface must be defined.
4. This parameter can only be used when the Eulerian mesh is aligned with the basic coordinate system
axes.
Main Index
DYPARAM,HYDROBOD 1703
Hydro Body Force - SOL700
DYPARAM,HYDROBOD Hydro Body Force - SOL700
Defines a body force for single hydro material in Euler. Used in MSC Nasran SOL 700 only.
Format:
DYPARAM,HYDROBOD,XACC,YACC,ZACC
Example:
DYPARAM,HYDROBOD,-300.,0.,150.
Describer Meaning
XACC X-acceleration (Real; Default = 0.0)
YACC Y-acceleration. (Real; Default = 0.0)
ZACC Z-acceleration. (Real; Default = 0.0)
Remark:
1. This parameter defines a constant body force load in Euler for single hydro material only.
Main Index
1704 DYPARAM,HGCMEM
Shell Membrane Hourglass Damping Coefficient Parameters - SOL700
DYPARAM,HGCMEM Shell Membrane Hourglass Damping Coefficient
Parameters - SOL700
Defines the default membrane damping coefficient for shell elements. Used in SOL 700 only.
Format:
DYPARAM,HGCMEM,value
Example:
DYPARAM,HGCMEM,0.07
Describer Meaning
value Hourglass damping coefficient. (0.0 ≤ Real ≤ 0.15; default=See remark 3.)
Remarks:
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression method
for shell elements is either equal to the default value of 0.1 or is equal to the default value defined on
a DYPARAM,HGCOEFF entry.
Main Index
DYPARAM,HGCOEFF 1705
Hourglass Damping Coefficient - SOL700
DYPARAM,HGCOEFF Hourglass Damping Coefficient - SOL700
Defines the global default hourglass damping coefficient. Used in SOL 700 only.
Format:
DYPARAM,HGCOEFF,value
Example:
DYPARAM,HGCOEFF,0.14
Describer Meaning
value Hourglass damping coefficient. (0.0 ≤ Real ≤ 0.15; default=See remark 3.)
Remarks:
1. The default applies to all types of hourglass suppression methods and should be used unless there is
good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficients are not explicitly defined on
HGSUPPR entries or on a HGCMEM HGCWRP, HGCTWS, or HGCSOL entry.
3. If this entry is omitted, the default value of the hourglass damping coefficients is either equal to the
default value of 0.1 or is equal to the value specified on a HGCMEM, HGCTWS, HGCWRP, or
HGCSOL DYPARAM entry.
4. The value of the coefficients can be explicitly defined for each property by using an HGSUPPR entry.
Main Index
1706 DYPARAM,HGCSOL
Solid Hourglass Damping Coefficient - SOL700
DYPARAM,HGCSOL Solid Hourglass Damping Coefficient - SOL700
Define the default damping coefficient for solid elements. Used in SOL 700 only.
Format:
DYPARAM,HGCSOL,value
Example:
DYPARAM,HGCSOL,0.11
Describer Meaning
value Hourglass damping coefficient. (0.0 ≤ Real ≤ 0.15; default=See remark 3.)
Remarks:
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression method
for solid elements is either equal to the default value of 0.1 or is equal to the default value defined on
a DYPARAM,HGCOEFF entry.
Main Index
DYPARAM,HGCTWS 1707
Shell Twisting Hourglass Damping Coefficient - SOL700
DYPARAM,HGCTWS Shell Twisting Hourglass Damping Coefficient - SOL700
Defines the default twisting damping coefficient for shell elements. Used in SOL 700 only.
Format:
DYPARAM,HGCTWS,value
Example:
DYPARAM,HGCTWS,0.02
Describer Meaning
value Hourglass damping coefficient. (0.0 ≤ Real ≤ 0.15; default=See remark 3.)
Remarks:
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression method
for shell elements is either equal to the default value of 0.1 or is equal to the default value defined on
a DYPARAM,HGCOEFF entry.
Main Index
1708 DYPARAM,HGCWRP
Shell Warping Hourglass Damping Coefficient - SOL700
DYPARAM,HGCWRP Shell Warping Hourglass Damping Coefficient - SOL700
Defines the default warping damping coefficient for shell elements. Used in SOL 700 only.
Format:
DYPARAM,HGCWRP,value
Example:
DYPARAM,HGCWRP,0.0
Describer Meaning
value Hourglass damping coefficient. (0.0 ≤ Real ≤ 0.15; default=See remark 3.)
Remarks:
1. The default value applies to all types of hourglass suppression methods and should be used unless
there is a good reason to define the hourglass damping coefficient by another means.
2. The value specified on this entry is used whenever the coefficient is not explicitly defined on the
HGSUPPR entry.
3. If this entry is omitted, the default value of the coefficient used in the hourglass suppression method
for shell elements is either equal to the default value of 0.1 or is equal to the default value defined on
a DYPARAM,HGCOEFF entry.
Main Index
DYPARAM,HGSHELL 1709
Shell Hourglass Suppression Method - SOL700
DYPARAM,HGSHELL Shell Hourglass Suppression Method - SOL700
Defines the default hourglass suppression method for shell elements. Used in SOL 700 only.
Format:
DYPARAM,HGSHELL,value
Example:
DYPARAM,HGSHELL,DYNA
Describer Meaning
value Type of HGSHELL. (Character; default=See remark 2.)
FBV Flanagan-Belytschko viscous hourglass damping
DYNA Viscous hourglass damping
Remarks:
1. The type of hourglass suppression method defined on this entry is used as the default whenever the
type fields on the HGSUPPR for shell properties are left blank.
2. If this entry is omitted, the default suppression method used for shell elements is either FBV or the
default method defined on the DYPARAM,HGTYPE entry.
Main Index
1710 DYPARAM,HGSOLID
Solid Hourglass Suppression Method - SOL700
DYPARAM,HGSOLID Solid Hourglass Suppression Method - SOL700
Defines the default hourglass suppression method for solid elements. Used in SOL 700 only.
Format:
DYPARAM,HGSOLID,value
Example:
DYPARAM,HGSOLID,FBS
Describer Meaning
value Type of HGSOLID. (Character; default=See remark 2.)
FBS Flanagan-Belytschko stiffness hourglass damping
DYNA Viscous hourglass damping
Remarks:
1. The type of hourglass suppression method defined on this entry is used as the default whenever the
type fields on the HGSUPPR for solid properties are left blank.
2. If this entry is omitted, the default suppression method used for solid elements is either FBS or the
default method defined on the DYPARAM,HGTYPE entry.
Main Index
DYPARAM,HGTYPE 1711
Hourglass Suppression Method - SOL700
DYPARAM,HGTYPE Hourglass Suppression Method - SOL700
Defines the default type of hourglass suppression method. Used in SOL 700 only.
Format:
DYPARAM,HGTYPE,value
Example:
DYPARAM,HGTYPE,FBS
Describer Meaning
value Type of HGTYPE. (Character; default=See remark 2.)
FBS Flanagan-Belytschko stiffness hourglass damping.
FBV Flanagan-Belytschko viscous hourglass damping.
DYNA Viscous hourglass damping.
Remarks:
1. The type of the hourglass suppression method defined on this entry is used as the default whenever
the type fields in the HGSUPPR entries are left blank.
2. If this entry is omitted, the type can be defined on a DYPARAM,HGSHELL entry for shell elements,
a DYPARAM,HGSOLID entry for solid elements, or on the HGSUPPR entries; otherwise the
defaults apply. For shell elements the default is FBV; for solid elements, the default is FBS.
Main Index
1712 DYPARAM,HICGRAV
Gravity Used by HIC Calculations - SOL700
DYPARAM,HICGRAV Gravity Used by HIC Calculations - SOL700
Defines the value of the gravity to be used by the HIC calculations. Used in SOL 700 only.
Format:
DYPARAM,HICGRAV,value
Example:
DYPARAM,HICGRAV,980.7
Describer Meaning
value Gravity used by HIC Calculations. (Real > 0.0; default=9.80665)
Remarks:
1. The value set by this parameter will be used by all HIC output requests.
2. This parameter can only be set once in the input deck.
Main Index
DYPARAM,HVLFAIL 1713
Failure at Hydrodynamic Volume Limit - SOL700
DYPARAM,HVLFAIL Failure at Hydrodynamic Volume Limit - SOL700
Defines element failure on the hydrodynamic volume limit. Used in SOL 700 only.
Format:
DYPARAM,HVLFAIL,value
Example:
DYPARAM,HVLFAIL,YES
Describer Meaning
value Flag of HVLFAIL. (Character; default=NO)
YES Element failure on hydrodynamic volume limit
NO No element failure on hydrodynamic volume limit
Remarks:
1. Lagrangian elements (CHEXA) that have a material model with a failure model fail when the
hydrodynamic volume limit is reached and the parameter is set to YES.
The elements can fail only when the following items are presented in the input:
a. The material model has a hydrodynamic volume limit (HVL).
b. A failure model is defined.
c. DYPARAM, HVLFAIL, YES
2. The hydrodynamic volume limit by default allows for 10% expansion.
Main Index
1714 DYPARAM,IMM
Initial Metric Method Formulation - SOL700
DYPARAM,IMM Initial Metric Method Formulation - SOL700
The option allows to specify the IMM method to be used. Used in SOL 700 only.
Format:
DYPARAM,IMM,OPTION1,OPTION2,VALUE1,VALUE2
Example:
DYPARAM,IMM,ZERO,YES,1.0E-3,1.0E-3
Describer Meaning
OPTION1 Flag for element condition under compression. (Character; default=FULL)
FULL While elements are under IMM condition, they will carry stresses when under
compression.
REDUCED While elements are under IMM condition they will carry a reduced stress
when under compression. The relative area factor SMDFER is used to reduce
the Young’s modulus.
ZERO While elements are under IMM condition they do not carry any compressive
stresses. Use material damping to avoid excessive nodal velocities.
OPTION2 Flag for recalculation of IMM strain. (Character; default=See remark 2.)
NO or OFF Do not recalculate IMM strains during the calculation.
YES or ON Recalculate IMM strains during the calculation.
VALUE1 Start time of recalculation of IMM strains. See remark 3.(Real > 0.0; Default is 1.0E-3)
VALUE2 Times between recalculation of IMM strains. See remark 3.(Real > 0.0; Default is 1.0E-3)
Remarks:
1. Method ZERO is best suitable when initially more than a couple of elements with zero or near zero
area are present in the model.
2. The default for Option2 depends on Option1.
Option1 Default for Option2
FULL OFF
REDUCED OFF
ZERO ON
3. When Option2 is OFF or NO, STREC and DTREC are neglected.
Main Index
DYPARAM,INFOBJ 1715
List the Generated BJOINs and Spotwelds - SOL700
DYPARAM,INFOBJ List the Generated BJOINs and Spotwelds - SOL700
Additional information about the BJOIN and spotweld connectivity will be listed in the output file. Used in
SOL 700 only.
Format:
DYPARAM,INFOBJ,value
Example:
DYPARAM,INFOBJ,0.14
Describer Meaning
value Flag of activation of writing BJOIN information. (Character; default=NO)
YES Information is issued.
NO Information is not issued.
Remarks:
1. The information listed is:
• Grid point pairs forming a BJOIN or a spotweld.
• BJOINs and spotwelds initially connected.
Main Index
1716 DYPARAM,INISTEP
Initial Time Step - SOL700
DYPARAM,INISTEP Initial Time Step - SOL700
Defines the time step used at the start of the analysis. Used in SOL 700 only.
Format:
DYPARAM,INISTEP,value
Example:
DYPARAM,INISTEP,1.0E-6
Describer Meaning
value Time step (in analysis time units) used for the first iteration. (Real > 0.0; required)
Remarks:
1. This parameter is required to start an analysis.
Main Index
DYPARAM,LAGPR 1717
Lagrangian Partitioning Control - SOL700
DYPARAM,LAGPR Lagrangian Partitioning Control - SOL700
Controls the partitions of the Lagrangian elements on the processors. Used in SOL 700 only.
Format:
PARAM,LAGPR, IOPT,xvec,yvec,zvec,xcen,ycen,zcen
Example:
PARAM,LAGPR, 6, 1.0, 0.0, 0.0, 0.0, -100.0, 0.0
Describer Meaning
IOPT Set partitioning type. See remark 1. (Integer > 0, default=1).
1 Metis best partitioning
2 Metis Decomposition on element based
3 Metis Decomposition on node based
4 Vector Decomposition with Specified User Direction. xvec, yvec and zvec are
required.
5 Radial Decomposition with User Direction. xvec, yvec, zvec, xcen, ycen and
zcen are required.
6 Angular Decomposition with User Direction. xvec, yvec, zvec, xcen, ycen and
zcen are required.
7 Recursive Coordinate Bisection Decomposition
xvec X-component of directional vector. (Real, default=0.0)
yvec Y-component of directional vector. (Real, default=0.0)
zvec Z-component of directional vector. (Real, default=0.0)
xcen X-coordinate of the origin of axis. (Real, default=0.0)
ycen Y-coordinate of the origin of axis. (Real, default=0.0)
zcen Z-coordinate of the origin of axis. (Real, default=0.0)
Remark:
1. To use the option, check DYPARAM,DMPOPT.
Main Index
1718 DYPARAM,LIMCUB
Contact Cube Sort Algorithm - SOL700
DYPARAM,LIMCUB Contact Cube Sort Algorithm - SOL700
Defines the maximum number of cubes used to sort the grid points in a contact definition. Used in SOL 700
only.
Format:
DYPARAM,LIMCUB,value
Example:
DYPARAM,LIMCUB,2300
Describer Meaning
value Maximum number of cubes. (Integer > 0; default=200)
Remarks:
1. Each secondary node has to search for primary nodes that are close enough to have potential contact.
It is too expensive to have each secondary node check each primary node. To limit the number of
checks, the space in which the nodes reside is subdivided into cubes. This subdivision is done so that
the secondary nodes have to check only the primary nodes in their own cube and those in the
neighboring cubes. The maximum number of cubes used to subdivide the space is equal to the value
of LIMCUB.
Main Index
DYPARAM,MATRMERG 1719
Merges MATRIG and RBE2-FULLRIG Assemblies - SOL700
DYPARAM,MATRMERG Merges MATRIG and RBE2-FULLRIG Assemblies - SOL700
Merges MATRIG and/or RBE2-FULLRIG rigid bodies into a new FULLRIG assembly. Used in SOL 700
only.
Format:
DYPARAM,MATRMERG,FR<id1>,MR<id2>,MR<id3>,FR<id4>,…
DYPARAM,MATRMERG,AUTO
Example:
DYPARAM,MATRMERG,FR1,MR2,MR6,MR7,FR4,MR8
Describer Meaning
FR<id1> Name of the new FULLRIG assembly. (Character; required.)
MR<idi> or FR<idi> Names of MATRIG and/or RBE2-FULLRIG rigid bodies merged into a new
FULLRIG assembly with name FR<id1>. No names can be supplied for the
AUTO option.
AUTO Automatic merge. See remark 2. (Character; required.)
Remarks:
1. FR<id1> must be a nonexisting RBE2-FULLRIG. The properties of FR<id1> (as mass, center of
gravity, and moments of inertia) are computed by solver from the properties of each rigid body
mentioned on the entry. Rigid body output can be asked for FR<id1>, and loads or rigid body
constraints can be applied to FR<id1>. The other MATRIGs and RBE2-FULLRIGs mentioned on
the MATRMERG entry disappear after they have been merged.
2. Instead of supplying rigid body names, the AUTO option can be used. After all the normal
DYPARAM,MATRMERG and DYPARAM,MATRMRG1 entries have been applied, a
DYPARAM,MATRMERG,AUTO merges all the resulting MATRIGs and RBE2-FULLRIGs which
have common grid points into a new rigid assembly called FM<id>, where the id is a new FM number
starting from 1. As it is not known at the start of an analysis how many FM assemblies will be created,
no rigid body output can be asked for FM<id>, and no constraints or loads can be applied to FM<id>.
The MATRIGs and RBE2-FULLRIGs, which have been merged by the AUTO option into a new
FM<id> assembly, disappear.
3. To supply predefined properties for the merged assembly, DYPARAM,MATRMRG1 can be used,
where the first rigid body mentioned on the entry must be an existing RBE2-FULLRIG or MATRIG.
Main Index
1720 DYPARAM,MATRMRG1
Merges MATRIG and RBE2-FULLRIG Assemblies - SOL700
DYPARAM,MATRMRG1 Merges MATRIG and RBE2-FULLRIG Assemblies - SOL700
Merges MATRIG and/or RBE2-FULLRIG rigid bodies into one existing MATRIG or RBE2-FULLRIG
assembly with predefined properties. Used in SOL 700 only.
Format:
DYPARAM,MATRMRG1,MR<id1>,MR<id2>,MR<id3>,FR<id4>,...
DYPARAM,MATRMRG1,FR<id1>,MR<id2>,MR<id3>,FR<id4>,...
Example:
DYPARAM,MATRMRG1,MR1,MR2,MR6,MR7,FR4,MR8
Describer Meaning
MR<id1> or FR<id1> Name of the existing MATRIG or FULLRIG assembly (must be an
existing one). (Character; required.)
MR<idi> or FR<idi> Names of MATRIG and/or RBE2-FULLRIG rigid bodies, which are
merged with the existing MR<id1> or FR<id1> into a new MATRIG
assembly, with name MR<id1> or FR<id1>. (Character; required.)
Remarks:
1. MR<id1> or FR<id1> must be an existing MATRIG or RBE2-FULLRIG, respectively. For a
FULLRIG, the properties of FR<id1> (as mass, center of gravity and moments of inertia) are
computed by solver from the properties of each rigid body mentioned on the entry. For a MATRIG,
the mass of MR<id1> is either the predefined mass on the MATRIG (id1) entry or the predefined
density on the MATRIG (id1) entry times the total volume of all MATRIG members in the
MATRMRG1 entry. The center of gravity and moments of inertia of MR<id1> are either predefined
on the MATRIG (id1) entry, or are otherwise computed from the properties of each rigid body on
the entry. The other MATRIGs and RBE2 FULLRIGs mentioned on the MATRMRG1 entry
disappear after they have been merged.
Main Index
DYPARAM,MAXSTEP 1721
Maximum Time Step - SOL700
DYPARAM,MAXSTEP Maximum Time Step - SOL700
Defines the maximum allowable time step. Used in SOL 700 only.
Format:
DYPARAM,MAXSTEP,value
Example:
DYPARAM,MAXSTEP,1.E-3
Describer Meaning
value The maximum time step. (Real > 0.0; default=1.0E20)
Remarks:
1. If the time step calculated by solver is greater than MAXSTEP, the time step is set to MAXSTEP.
Main Index
1722 DYPARAM,MESHPLN
Mesh Density for Covering Rigid Planes - SOL700
DYPARAM,MESHPLN Mesh Density for Covering Rigid Planes - SOL700
Defines Mesh density for covering rigid planes. Used in SOL 700 only.
Format:
DYPARAM,MESHPLN,value
Example:
DYPARAM,MESHPLN,4
Describer Meaning
value Rigid planes will be meshed with MESHPLN times MESHPLN dummy quad elements.
(Integer > 0; default=3)
Remarks:
1. The default is sufficient in most cases.
Main Index
DYPARAM,MINSTEP 1723
Minimum Time Step - SOL700
DYPARAM,MINSTEP Minimum Time Step - SOL700
Defines the minimum time step that causes the analysis to terminate. Used in SOL 700 only.
Format:
DYPARAM,MINSTEP,value
Example:
DYPARAM,MINSTEP,1.E-6
Describer Meaning
value When the time step is less than the MINSTEP value, the analysis terminates. (Real > 0.0;
default=10% of DYPARAM,INISTEP)
Remarks:
1. When the elements become very distorted, in a poorly designed mesh for example, or when they have
endured a very large distortion, the time step may drop dramatically. The analysis continues, however,
and a lot of computer resources may be wasted. This option allows you to specify a minimum time
step that causes the analysis to terminate.
Main Index
1724 DYPARAM,MIXGAS
Controls Updating of Gas Fractions - SOL700
DYPARAM,MIXGAS Controls Updating of Gas Fractions - SOL700
Specifies whether the gas constants of the Euler material or of gas bags are updated based on the gas
composition and temperature. Used in SOL 700 only.
Format:
DYPARAM,MIXGAS,value
Example:
DYPARAM,MIXGAS,YES
Describer Meaning
value Flag of MIXGAS. (Character; default=NO)
YES The gas constants for the Euler material and any gas bags are recalculated
based on temperature and gas composition.
NO Euler and gas bag gas constants are not recalculated.
Remarks:
1. This parameter is only defined for use with GBAG gas bag definitions and/or the single-material Euler
solver.
2. This parameter can be used in conjunction with INFLTR and INFLHB inflator definitions and with
PORHOLE, PERMEAB, PORFGBG, and PERMGBG porosity definitions.
3. By default, DYPARAM,MIXGAS is set to YES if any INFLHB or INFLGAS entries are present.
Main Index
DYPARAM,NZEROVEL 1725
Auto Constrain Failed Nodes - SOL700
DYPARAM,NZEROVEL Auto Constrain Failed Nodes - SOL700
Set the velocity of a node to zero in case all attached elements have failed. Used in SOL 700 only.
Format:
DYPARAM,NZEROVEL,value
Example:
DYPARAM,NZEROVEL,YES
Describer Meaning
value Flag of NZEROVEL. (Character; default=NO)
YES Perform check and set the velocity to zero if all attached elements have
failed.
NO Do not perform check.
Remarks:
1. This parameter applies only to nodes of Lagrangian elements.
2. Specifying NO reduces the CPU overhead time.
3. When the velocity of a node is set to zero, effectively the node is constraint, like an SPC or SPC1.
4. Special attention is necessary for the contact definition. If the failed node is not taken out of the
contact, it behaves as a rigid boundary constraint.
Main Index
1726 DYPARAM,OLDLAGT
Use Collapsed Hexahedron Scheme for CTETRA - SOL700
DYPARAM,OLDLAGT Use Collapsed Hexahedron Scheme for CTETRA - SOL700
Activate the collapsed hexahedron scheme as default for lagrangian CTETRA elements. Used in SOL 700
only.
Format:
DYPARAM,OLDLAGT,value
Example:
DYPARAM,OLDLAGT,1
Describer Meaning
value Flag of OLDLAGT. (Integer ≥ 0; default=See remark 1.)
0 Deactivate collapsed hexahedron scheme
1 Activate
Remarks:
1. The current default integration scheme for Lagrangian CTETRA elements use linear tetrahedron FE
one. It is more consistent (in terms of accuracy) and efficient (both in memory and CPU time)
compared with the collapsed hexahedron scheme. The old scheme based on collapsed hexahedron
with reduced integration is deactivated. If the old scheme is activated, it is used as default. But, it is
still possible to use the new scheme for CTETRA by using separate PSOLID with IN = 1 and ISOP
= 1 combination.
Main Index
DYPARAM,JWLDET 1727
Hydro Body Force - SOL700
DYPARAM,JWLDET Hydro Body Force - SOL700
Specifies whether the blast wave of one explosive can ignite another explosive. Here it assumed that the
explosives are modeled by a combination of EOSJWL and DETSPH entries.
Format:
PARAMJWLDET,OPTION
Example:
PARAM,JWLDET,NOLINK
Describer Meaning
LINK Multiple denotations with EOSJWL are LINKED.
The detonation wave of one explosive can ignite another explosive.
NOLINK Multiple denotations with EOSJWL are NOT LINKED.
The detonation wave of one explosive cannot ignite another explosive.
Default NOLINK
Remark:
1. Option NOLINK: TDET is set to -1 for elements that have no JWL material. The "NOLINK"
option is only valid with true JWL materials - not valid for the "Static Detonation/Ideal Gas" model.
2. Setting this parameter as "NOLINK" will prevent "sympathetic ignition". Each charge will ignite at
the specified "TDET" in its own DETSPH card.
Main Index
1728 DYPARAM,LIMITER
Original Roe-Type Euler Solver Scheme - SOL700
DYPARAM,LIMITER Original Roe-Type Euler Solver Scheme - SOL700
Defines the type and the spatial accuracy of scheme used in the Euler solver based on the ideas of Prof. Philip
Roe. Used in SOL 700 only.
Format:
DYPARAM,LIMITER,TYPE,OPTION
Example:
DYPARAM,LIMITER,ROE
Describer Meaning
TYPE Type of scheme. (Character; Default = ROE)
ROE Roe solver for single hydrodynamic materials.
OPTION blank Second order in space. (Character; Default = blank)
NONE First order in space.
Remarks:
1. By default, when the parameter is not set, the solver is used that is defined on the PEULER or the
PEULER1 entry. In case “2ndOrder” or “1stOrder” was defined on the PEULER or PEULER1
entry, the parameter setting has no effect.
2. By default, second order spatial accuracy is used. The temporal accuracy is automatically defined
according to the spatial accuracy that you select.
3. Note that 2nd order spatial accuracy in the Roe solver involves the internal flow field only. We
recommend that you use the full 2nd order improved fluid-and gas Euler solver. You can activate the
improved solver by putting the “2ndOrder” field on the PEULER or PEULER1 entry.
4. When type ROE is defined, no void elements are allowed and it cannot be used in combination with
EOSJWL. Also options concerning air-bag analyses are not supported.
5. For more details on fluid- and gas Euler solvers, refer to the Getting Started and the Theory Manuals.
Main Index
DYPARAM,PARALLEL 1729
Parallel Execution Information - SOL700
DYPARAM,PARALLEL Parallel Execution Information - SOL700
The option allows you to gather information on the parallel section. Used in SOL 700 only.
Format:
DYPARAM,PARALLEL,INFPAR,value
Example:
DYPARAM,PARALLEL,INFPAR,ON
Describer Meaning
INFPAR A report is written on the actual amount of work done at the reported parallel levels.
(Character; required)
Value Flag for INFPAR. (Character; default=OFF)
ON Activate writing information.
OFF Deactivate writing information.
Remarks:
1. A summary on the parallel operation when using the shared-memory mode can be requested by
including a DYPARAM,PARALLEL,INFPAR,ON entry in the input file.
2. Currently, the information on the parallel sections is available for the shell solver only.
Main Index
1730 DYPARAM,PLCOVCUT
Pressure Cut Off Time - SOL700
DYPARAM,PLCOVCUT Pressure Cut Off Time - SOL700
Defines time when PLCOVER is cut off. Used in SOL 700 only.
Format:
DYPARAM,PLCOVCUT,value
Example:
DYPARAM,PLCOVCUT,3.E-3
Describer Meaning
value If there are one or more COUPLE definitions with a PLCOVER specified on the
COUOPT entry, a cut off is applied to the PLCOVER until time = PLCOVCUT. From
time = 0 to time = PLCOVCUT, the PLCOVER is cut off to the pressure in the
intersected Eulerian element.
For times greater than PLCOVCUT, the full PLCOVER is applied to the coupling
surface.
This parameter is useful in air-bag analyses, where PLCOVER is used to model the
environment pressure. During the early stages of the deployment of the air bag, the
pressure inside the bag may drop. Applying the full PLCOVER may lead to an unstable
deployment of the air bag. (Real ≥ 0.0; default=0.
Remarks:
1. See also the COUPLE and COUOPT Bulk Data entries.
Main Index
DYPARAM,PMINFAIL 1731
Switches Failure at Spall Limit - SOL700
DYPARAM,PMINFAIL Switches Failure at Spall Limit - SOL700
Defines Lagrangian solid element failure on reaching the spall limit. Used in SOL 700 only.
Format:
DYPARAM,PMINFAIL,value
Example:
DYPARAM,PMINFAIL,YES
Describer Meaning
VALUE Flag of PMINFAIL. (Character; default=NO)
YES Element failure on spall limit
NO No element failure on spall limit
Remarks:
1. Lagrangian elements (CHEXA) that have a material definition with a failure model will fail when the
parameter is set to YES and the spall limit (minimum pressure) is reached, even when the other failure
criterion is not yet reached.
2. The spall limit is set on the PMINC entry.
Main Index
1732 DYPARAM,RBE2INFO
Lists MATRIG and RBE2 Grid Points - SOL700
DYPARAM,RBE2INFO Lists MATRIG and RBE2 Grid Points - SOL700
The grid points attached to MATRIG and RBE2assemblies are listed to the output file. Used in SOL 700
only.
Format:
DYPARAM,RBE2INFO,value
Example:
DYPARAM,RBE2INFO,GRIDON
Describer Meaning
VALUE Flag of PBE2INFO. (Character; default=GRIDOFF)
GRIDON Information is issued C
GRIDOFF No information is issued
Main Index
DYPARAM,RHOCUT 1733
Global Density Cutoff Value - SOL700
DYPARAM,RHOCUT Global Density Cutoff Value - SOL700
Defines the minimum density for all Eulerian elements. Used in SOL 700 only.
Format:
DYPARAM,RHOCUT,value
Example:
DYPARAM,RHOCUT,1.E–10
Describer Meaning
value Density cutoff. (Real > 0.0; default=See remark 4.)
Remarks:
1. Any Eulerian element with a density less than RHOCUT is considered to be empty. All of its variables
are set to zero, and the equation of state is bypassed.
2. In the Eulerian transport calculation, if the material is flowing from element A to element B, and
a. If the density of element B after transport is less than RHOCUT, then no transport is done.
b. If the density of element A after transport is less than RHOCUT, then all of the mass is
transported to element B.
3. A reasonable value of RHOCUT is 1.E–5 times the initial density.
4. If only RHOCUT is defined, all Eulerian elements use the RHOCUT value as cutoff density. If
RHOCUT is omitted, all Eulerian elements use a cutoff density automatically set to 1.E–5 times a
characteristic density. For single-material Eulerian elements, this characteristic density is the reference
density.
Main Index
1734 DYPARAM,RJSTIFF
Rigid-joint Stiffness - SOL700
DYPARAM,RJSTIFF Rigid-joint Stiffness - SOL700
Defines the stiffness of a rigid joint. Used in SOL 700 only.
Format:
DYPARAM,RJSTIFF,value
Example:
DYPARAM,RJSTIFF,100.
Describer Meaning
value Multiplication factor for the stiffness of all rigid joints. (Real > 0.0; default=1.0)
Remarks:
1. The absolute stiffness of rigid joints is calculated automatically by solver. The stiffness of joints is
taken so that a stable solution is guaranteed. The stiffness calculation takes into account the fact that
a rigid body can be constrained by more than one joint.
2. This parameter can be used to increase or decrease the stiffness of the joints. Care must be taken
because too high a value may lead to an unstable calculation.
Main Index
DYPARAM,SCALEMAS 1735
Mass Scaling Definition - SOL 700
DYPARAM,SCALEMAS Mass Scaling Definition - SOL 700
Defines the activation of mass scaling.
Format:
DYPARAM,SCALEMAS,DTMIN,MXPERC,STEPS.
Example:
DYPARAM,SCALEMAS,1.0E-6,100.0,1
Describer Meaning
DTMIN Minimum allowable time step. (Real > 0.0; required)
MXPERC Maximum percentage of added numerical mass with respect to original mass. (Real > 0.0;
required)
STEPS Number of steps. (Integer > 0; required)
Remarks:
1. Numerical mass is added to all Lagrangian solid, triangular, quadrilateral, rod, bar and beam elements
such that its time step never becomes less than:
dt = STEPFCT*DTMIN.
Where,
dt = time step of calculation
STEPFCT = time step safety factor (see PARAM,STEPFCT)
DTMIN = value specified on the PARAM,SCALEMAS entry
If the added mass of a certain element exceeds the maximum percentage (MXPERC) of its original
mass, no more mass will be added, and subsequently, the time step may decrease again.
2. The value of STEPS determines the checking frequency against the mass scaling criterion; the check
is done for every defined number of STEPS. STEPS = 1 is recommended.
3. By requesting MSMASS in an ELOUT output request, the ratio of scaled mass to original mass of the
elements can be retrieved. By making fringe plots of this parameter, a check can be made if mass has
not been added in a critical area.
4. See MSC Nastran Explicit Nonlinear (SOL 700) User's Guide, Chapter 4: Special Modeling
Techniques, Mass Scaling Definition for instructions on how to use this entry
Main Index
1736 DYPARAM,SHELLFRM
Sets the Default of the Shell Formulation - SOL700
DYPARAM,SHELLFRM Sets the Default of the Shell Formulation - SOL700
Sets the default for the shell formulation for quadrilateral elements. Used in SOL 700 only.
Format:
DYPARAM,SHELLFORM,value
Example:
DYPARAM,SHELLFORM,BLT
Describer Meaning
value Flag for default of shell formulation. (Character; default=KEYHOFF)
BLT The shell-formulation default is BLT.
KEYHOFF The shell-formulation default if KEYHOFF.
Remarks:
1. The DYPARAM,SHELLFORM changes the default formulation for quadrilateral shell elements. All
shell properties entries that do not explicitly define the formulation, use the default as specified on
the DYPARAM entry.
2. Triangular shell elements have only one formulation (C0-TRIA). Therefore, the DYPARAM is
ignored for triangular elements.
Main Index
DYPARAM,SHELMSYS 1737
Shell Element System Definition - SOL700
DYPARAM,SHELMSYS Shell Element System Definition - SOL700
Defines the shell element system for the BLT shells. Used in SOL 700 only.
Format:
DYPARAM,SHELMSYS,value
Example:
DYPARAM,SHELMSYS,SIDE21
Describer Meaning
value Type of shell element system. (Character; default=MIDSIDES)
SIDE21 x-axis along side21.
MIDSIDES x-axis connecting midpoints.
Remarks:
1. SIDE21 puts the x-axis along side21 of the element, whereas MIDSIDES puts the x-axis along the
vector connecting the midpoints of the side14 and side32.
2. Using the SIDE21 option for the BLT shell will result in the same Belytschko-Lin-Tsay
implementation as BELY.
Main Index
1738 DYPARAM,SHPLAST
Type of Plane-Stress Plasticity for Shells - SOL700
DYPARAM,SHPLAST Type of Plane-Stress Plasticity for Shells - SOL700
Specifies the type of calculation used to determine the plane-stress plasticity method for shells. Used in SOL
700 only.
Format:
DYPARAM,SHPLAST,value
Example:
DYPARAM,SHPLAST,VECT
Describer Meaning
value Type of Plain-stress plasticity for shells. (Character; default=ITER)
RADIAL Noniterative, approximate radial return.
VECT Iterative, vectorized with three iterations.
ITER Nonvectorized iterations.
Remarks:
1. The RADIAL approach does not require iterations and, therefore, is the most efficient. It is, however,
an approximation.
2. The other two approaches iterate to find the solution. ITER is the best since it takes as many iterations
as are necessary. On vector machines, such as CRAY, this is inefficient since it cannot be vectorized.
VECT always performs three vectorized iterations, which is more efficient. However, three iterations
may not be enough, and inaccuracies could occur.
Main Index
DYPARAM,SHSTRDEF 1739
Composite Shell Stress and Strain Output Definition - SOL700
DYPARAM,SHSTRDEF Composite Shell Stress and Strain Output Definition - SOL700
Specifies the default coordinate system for the stress and strain output of composite shells. Used in SOL 700
only.
Format:
DYPARAM,SHSTRDEF,value
Example:
DYPARAM,SHSTRDEF,ELEM
Describer Meaning
value Type of output. (Character; default=FIBER)
FIBER Stresses and strains are output in the fiber and matrix directions.
ELEM Stresses and strains are output in the element coordinate system.
Remarks:
1. The default setting can be overruled per property on a PCOMPA entry on the STRDEF field.
Main Index
1740 DYPARAM,SHTHICK
Shell-Thickness Modification Option - SOL700
DYPARAM,SHTHICK Shell-Thickness Modification Option - SOL700
Specifies whether or not the thickness of the shell changes with membrane straining. Used in SOL 700 only.
Format:
DYPARAM,SHTHICK,value
Example:
DYPARAM,SHTHICK,YES
Describer Meaning
value Flag of shell thickness modification. (Character; default=YES)
YES Shell thickness is modified according to the membrane strain.
NO Shell thickness is constant.
Remarks:
1. The YES option gives a true large-strain shell but requires some extra computation.
2. The NO option should give adequate results as long as the membrane strains are not very large (i.e.,
not more than 5–10%).
3. This option applies to all the formulations of the shell elements, except for the PCOMP. The
thickness of PCOMP shell elements will always remain constant.
Main Index
DYPARAM,SLELM 1741
Store Shell Sublayer Variables - SOL700
DYPARAM,SLELM Store Shell Sublayer Variables - SOL700
Defines whether shell sublayer variables are to be stored in the element arrays. Used in SOL 700 only.
Format:
DYPARAM,SLELM,value
Example:
DYPARAM,SLELM,NO
Describer Meaning
value Flag of storing shell sublayer variables. (Character; default=YES)
YES Store as an element variable.
NO Do not store as an element variable.
Remarks:
1. This parameter applies only to shell elements.
2. The shell sublayer variables are primarily stored in sublayer arrays. They can be copied into the
element arrays only for specific output purposes.
3. Specifying NO reduces the CPU overhead time.
4. Irrespective of the entry on this parameter, sublayer variables are accessible in the sublayer arrays. For
example, requesting TXX1 retrieves the stress from the element array, whereas TXX01 retrieves it
from the sublayer arrays.
Main Index
1742 DYPARAM,SMP,BATCHSIZ
SMP Batchsize and CPULOOP Definition - SOL700
DYPARAM,SMP,BATCHSIZ SMP Batchsize and CPULOOP Definition - SOL700
Define batch size and number of CPU loops, per entity type. Used in SOL 700 only.
Format:
DYPARAM,SMP,<entity>,BATCHSIZ,<value1>,CPULOOPS,<value2>
Example:
DYPARAM,SMP,BEAMS,BATCHSIZ,AUTOMAT
DYPARAM,SMP,BEAMS,BATCHSIZ,256
Describer Meaning
ENTITY Define the batchsize for the following entities. (Character; required)
BEAMS Beam elements
SHELLS Shell elements
SOLIDS Solid elements
CONTACT Contacts
VALUE1 The batchsize for this entity (Integer number) or AUTOMAT (character). See Remarks
1.and 3. (Character or Integer >0; default = 63)
VALUE2 If value1 is defined as AUTOMATIC, the user may define the number of loops per CPU
See Remark 2.(Integer > 0; default=2)
Remarks:
1. The batchsize may be defined per entity type. The SMP parts uses the batchsize to assign a certain
number of batches to each CPU. Example:
• Batchsize = 63 (default)
• Number of Beam elements = 580
• Number of CPUs = 4
As a results,
• Needs to process 10 batches (9x63 + 1x13)
• To spread this evenly over four CPUs, a solver increases this to 12 batches because then each
CPU can process 3 batches.
• As a result, the batch size is recalculated for 12 batches to: batchsize = 49
• This means that:
CPU# 1,2,3 process three batches of 49 elements each (3x3x49 = 441 elements)
CPU# 4 processes two batches of 49 elements and one batch of 41
Main Index
DYPARAM,SMP,BATCHSIZ 1743
SMP Batchsize and CPULOOP Definition - SOL700
It is clear that the user-defined batchsize may not be used ultimately. The reason for this is that each
CPU is allocated the same number of batches in order to optimize the work done by each processor.
2. When the batchsize is set to AUTOMAT, a solver computes an initial batchsize based on the number
of batches processed by each CPU. By default, processes two batches per CPU.
In the example above, this means that based on:
• Batchsize = AUTOMAT
• Number of batches per CPU = 2 (default)
• Number of Beam elements = 580
• Number of CPUs = 4
As a result,
• Computes an initial batchsize of 72 (=580/(4*2))
• Increases this batchsize to a higher number to make sure the number of batches fits in the fixed
number of CPU’s: batchsize = 72 + (580 – 4*2*72) = 72 + 4 = 76 elements
• Based on this initial batchsize, the number of batches would be: 1 + (580-1)/76 = 8 batches
• This fits nicely on four CPU’s as expected
• The CPUs process:
CPU# 1,2,3 processes two batches of 76 elements each (3x2x76 = 456 elements)
CPU# 4 processes one batch of 76 elements and 1 batch of 48 elements.
3. By default, a solver does not use the AUTOMAT batchsize algorithm. Testing has shown that an
initial batchsize of 63 yields the fastest results. This may vary depending on the problem simulated
and the number of elements and may be worth adjusting.
The reason for this may be found in the fact, that with many elements in the model, the number of
elements per batch increases significantly when the AUTOMAT batchsize algorithm is used. Each
CPU will have to process two batches (by default) with many elements. Based on the cache memory,
this is usually not optimal for a CPU processor. Shorter batchsizes (< 128) will do a better job.
Main Index
1744 DYPARAM,SMP,CPUINFO
SMP CPU Information - SOL700
DYPARAM,SMP,CPUINFO SMP CPU Information - SOL700
Define the CPU information per entity type. Used in SOL 700 only.
Format:
DYPARAM,SMP,<entity>,CPUINFO,<value1>
Example:
DYPARAM,SMP,CONTACT,CPUINFO,ON
Describer Meaning
ENTITY Define the CPUINFO for the following entities. (Character; required)
BEAMS Beam elements
SHELLS Shell elements
SOLIDS Solid elements
CONTACT Contacts
MEMBR Membrane elements
EULT9 Eulerian Roe Solver
FSCOUP Fast coupling algorithm
ALL Output for all of the above
VALUE1 Flag for writing CPU information. (Character; required)
ON Ask for parallel CPU time information C
OFF No CPU time information (default)
Remarks:
1. By default, a solver does not give any SMP CPU timings per entity. In order to judge the efficiency
of the different algorithms, this parameter may be used to judge the speedup acquired by processing
on multiple CPUs.
Main Index
DYPARAM,SNDLIM 1745
Sound Speed Minimum Value - SOL700
DYPARAM,SNDLIM Sound Speed Minimum Value - SOL700
Defines the minimum value for the speed of sound. Used in SOL 700 only.
Format:
DYPARAM,SNDLIM,value
Example:
DYPARAM,SNDLIM,1.E-6
Describer Meaning
value Minimum value of speed of sound. (Real > 0.0; default=1.0E-3)
Remarks:
1. This parameter is used to avoid the possibility of division by zero in the time step calculation.
2. SNDLIM has the units of velocity.
Main Index
1746 DYPARAM,SPREMAP
1-D Spherical Symmetric Euler Archive Remap - SOL700
DYPARAM,SPREMAP 1-D Spherical Symmetric Euler Archive Remap - SOL700
Allows a 1-D spherical symmetric Euler archive importation to a 3-D simulation. Used in SOL 700 only.
Format:
DYPARAM,SPREMAP,X0,Y0,Z0,range
Example:
DYPARAM,SPREMAP,0.0,0.5,0.5
Describer Meaning
X0,Y0,Z0 X, Y, Z coordinate of the point at which the 1-D spherical symmetric mesh is remapped.
(Real; default=0.0)
RANGE Only material whose distance to (X0,Y0,Z0) is smaller than “range” will be initialized with
the 1-D spherical symmetric Euler archive. (Real > 0.0; default = 1.0E20)
Remarks:
1. Since 1-D spherical symmetric simulations run much faster than 3-D simulation, it can save much
CPU time to do the first part of the simulation with a 1-D axial symmetric mesh. Afterwards, the 1-
D spherical symmetric Euler archive is imported into the 3-D simulation. By default, the 1-D
spherical symmetric archive will not be expanded in 3-D. To enable this expansion,
DYPARAM,SPREMAP has to be used. It is useful for blast wave simulations. The 1-D spherical
symmetric simulation has to be terminated before the blast wave approaches any 3-D structure.
2. This import of Euler archives is done by means of the EID option in the pth file.
3. To generate axial symmetric meshes DYPARAM,SPHERSYM can be used.
4. The remap of 1-D spherical symmetric to axial symmetric Euler meshes is supported.
Main Index
DYPARAM,SPHERSYM 1747
Spherical Symmetric Analyses - SOL700
DYPARAM,SPHERSYM Spherical Symmetric Analyses - SOL700
Enables an efficient and accurate 1D spherical symmetric solution for Eulerian materials. A much larger time
step becomes possible by basing the time step only on the mesh-size in radial direction. Used in SOL 700
only.
Format:
DYPARAM,SPHERSYM,MESHTYPE,RADAXIS,PHI
Example:
PARAM,SPHERSYM,RECT,X,2.0
Describer Meaning
MESHTYPE Two types of Euler meshes are supported. (Character; required)
SPHERIC Axial symmetric meshes
RECT Rectangular meshes
RADAXIS Radial Axis. (Character; required.)
X Global x direction
Y Global y direction
Z Global z direction
PHI Only used for MESHTYPE = RECT. Used to creates a 1d Spherical mesh with angles
+PHI/2 and –PHI/2. (Real ≥ 0; default=0.0)
Remarks:
1. Only available for Eulerian elements and does not support Lagrange elements. The effect of this
parameter is not limited to the solvers. Also Euler archives will reflect the modified Euler mesh
geometry.
2. The Euler mesh can already be symmetric but also a rectangular mesh comprising of one row of
elements can be used. Using the angle specified by PHI this Euler mesh is mapped into a 1D spherical
symmetric mesh.
3. The Euler mesh has to consist of one row of elements.
4. In the time step computation only the mesh-size in radial direction will be taken into account.
Main Index
1748 DYPARAM,STRNOUT
Shell Sublayer Strain Output - SOL700
DYPARAM,STRNOUT Shell Sublayer Strain Output - SOL700
Saves the total strains and equivalent effective stress (von Mises stress) at shell sublayers for output. Used in
SOL 700 only.
Format:
DYPARAM,STRNOUT,value
Example:
DYPARAM,STRNOUT,YES
Describer Meaning
value Flag for writing strain results. (Character; default=YES)
YES Save
NO Do not save.
Remarks:
1. A limited output set saves memory.
2. Perfectly elastic materials only have the limited output set.
3. Total strain output for shell composite materials can be requested from the PCOMPA Bulk Data
entry.
Main Index
DYPARAM,TOLCHK 1749
Tolerance for Fast Coupling - SOL700
DYPARAM,TOLCHK Tolerance for Fast Coupling - SOL700
Fast coupling requires that Euler elements are orthogonal. This means that normals of Euler element faces
have to be in a coordinate direction. In practice there can be small errors in the geometry of the Euler element
and Euler face normals do not always exactly point into a coordinate direction. Small deviations from the
coordinate direction do not give problems and are allowed by fast coupling.
To check the direction of an Euler face, the face normal vector is projected onto the closest coordinate
direction. If this projection is 1, the normal is exactly in the coordinate direction. When this projection is
within a sufficient small tolerance of 1, the face can be handled by fast coupling. The tolerance used is
TOLCHK. If the projection is smaller than 1-TOLCHK, the face cannot be handled by fast coupling and
the analysis terminates. Options are then to slightly increase TOLCHK , write out double precision format
in PATRAN, use general coupling, or use the MESH entry. Increasing TOLCHK too much can make the
coupling surface computation less accurate. To keep the computation accurate, the maximal allowed value of
TOLCHK is 1e-6. If DYPARAM,TOLCHK is not used, the tolerance used is 1e-14. Used in SOL 700 only.
Format:
DYPARAM,TOLCHK,value
Example:
DYPARAM,TOLCHK,1e-10
Describer Meaning
value Tolerance in accepting faces by fast coupling. (Real > 0.0; required.)
Main Index
1750 DYPARAM,VDAMP
Dynamic Relaxation Parameter - SOL700
DYPARAM,VDAMP Dynamic Relaxation Parameter - SOL700
Controls the global damping in the dynamic relaxation. Used in SOL 700 only.
Format:
DYPARAM,VDAMP,value
Example:
DYPARAM,VDAMP,0.001
Describer Meaning
value Dynamic relaxation parameter. (Real ≥ 0.0; default=0.0)
0.0 No dynamic relaxation.
Remarks:
1. The dynamic relaxation parameter is connected to the system natural frequency, ?, as ?=s??t, where s
denotes a percentage of critical damping. The damping occurs by factoring the velocities every time
step as follows:
F1=(1-?)/(1+?)
F2=1/(1+?)
vn+1/2=F1 vn-1/2+F2 an?tn
where v is the velocity, is the acceleration, and ? is the dynamic relaxation parameter.
Main Index
DYPARAM,VELMAX 1751
Maximum Velocity - SOL700
DYPARAM,VELMAX Maximum Velocity - SOL700
Defines the maximum velocity in Eulerian and Lagrangian meshes. Used in SOL 700 only.
Format:
DYPARAM,VELMAX,value,option
Example:
DYPARAM,VELMAX,1.E6
Describer Meaning
VALUE Maximum velocity. (Real > 0.0; default=1.0E10)
OPTION Flag for removing Euler elements. (Character; default=YES)
YES Remove the mass in Eulerian elements in which the velocity exceeds the
maximum specified velocity.
NO Do not remove the mass in Eulerian elements in which the velocity exceeds
the maximum specified velocity.
Remarks:
1. For Eulerian elements, VELMAX is applied to the velocity components separately. Therefore, the
magnitude of the velocity vector is limited to VELMAX. For Lagrangian elements, all components
are scaled down by the same factor to ensure that the maximal magnitude of the velocity vector does
not exceed VELMAX.
2. Although it is not usually necessary to limit the velocity in Eulerian meshes, there are occasions in
regions of near-vacuous flow for example, where specifying a maximum velocity can be advantageous.
The same applies to Lagrangian meshes in contact regions for example. This parameter should be used
with care.
3. Because very high velocities occur mostly in Eulerian elements with very small mass, the mass in these
elements can be removed to keep the analysis stable. This option is not available for Lagrangian solid
elements.
4. VELMAX must be greater than the minimum velocity specified by PARAM,VELCUT.
Main Index
1752 DYPARAM,VELMAX1
Maximum Translational and Angular Velocity - SOL700
DYPARAM,VELMAX1 Maximum Translational and Angular Velocity - SOL700
Defines the maximum translational and angular velocity in Eulerian and Lagrangian meshes. Used in SOL
700 only.
Format:
DYPARAM,VELMAX1,VELMAXT,option,VELMAXA
Example:
DYPARAM,VELMAX1,1.E6
Describer Meaning
VELMAXT Maximum translational velocity. (Real > 0.0; default=1.0E20)
OPTION Flag for removing Euler elements. (Character; default=YES)
YES Remove the mass in Eulerian elements in which the velocity exceeds the
maximum specified velocity.
NO Do not remove the mass in Eulerian elements in which the velocity exceeds
the maximum specified velocity.
VELMAXA Maximum angular velocity. (Real > 0.0; default=1.0E20)
Remarks:
1. For Eulerian elements, VELMAXT is applied to the velocity components separately. Therefore, the
magnitude of the velocity vector is limited to VELMAXT. For Lagrangian elements, all components
are scaled down by the same factor to ensure that the maximal magnitude of the velocity vector does
not exceed VELMAXT.
2. VELMAXA is used to limit the angular velocity of grid points. By default, the angular velocities are
not limited. In general, there is no need to limit angular grid point velocities.
3. Although it is not usually necessary to limit the velocity in Eulerian meshes, there are occasions in
regions of near-vacuous flow for example, where specifying a maximum velocity can be advantageous.
The same applies to Lagrangian meshes in contact regions for example. This parameter should be used
with care.
4. Because very high velocities occur mostly in Eulerian elements with very small mass, the mass in these
elements can be removed to keep the analysis stable. This option is not available for Lagrangian solid
elements.
5. VELMAXT must be greater than the minimum velocity specified by PARAM,VELCUT.
6. DYPARAM, VELMAX, and DYPARAM,VELMAX1 can be used in the same input deck. The values
set by DYPARAM,VELMAX1 will overrule the values set by DYPARAM,VELMAX.
For example, when using
DYPARAM,VELMAX,1000,YES
Main Index
DYPARAM,VELMAX1 1753
Maximum Translational and Angular Velocity - SOL700
DYPARAM,VELMAX1,,YES,1e+10
In the OUT file shows:
%I-INIT 02-p3_set_velmaxat, , ,(13),
SUMMARY VELMAX SETTINGS:
MAXIMAL VALUE TRANSLATIONAL VELOCITY = 0.100000E+04
MAXIMAL VALUE ANGULAR VELOCITY = 0.100000E+11
REMOVE EULERIAN MASS WHEN VELOCUITY EXCEEDS LIMIT: YES
Main Index
1754 DYPARAM,VISCPLAS
Use Overstress Formula to Update Strain-rate Dependent Plasticity - SOL700
DYPARAM,VISCPLAS Use Overstress Formula to Update Strain-rate Dependent
Plasticity - SOL700
Activate the overstress formula to update strain-rate dependent plasticity. This formula is normally used for
viscous-plastic material. Used in SOL 700 only.
Format:
DYPARAM,VISCOPLAS,value
Example:
DYPARAM,VISCOPLAS,1
Describer Meaning
VALUE Flag of updating overstress formula. (Integer ≥ 0; default=0)
0 Use scaling-up scheme
1 Use overstress formula
Remarks:
1. The strain rate dependent plasticity is normally calculated by scaling up the basic yield stress without
strain rate effect. Then the trial stresses are mapped back to the scaled-up yield surface. This algorithm
may lead to premature instability. Another technique is to calculate the so-called viscous-plastic strain
rate using “overstress” formula. And then the stresses are updated based on this viscous-plastic strain.
This technique seems to be more stable then the previous one. For shell elements, this option works
when combined with DYPARAM,SHPLAST,RADIAL. Only MATEP and Johnson-Cook models
are supported. For solid elements, this option works only for MATEP.
2. For shell elements, DYPARAM,VISCOPLAS,1, in combination with
DYPARAM,SHPLAST,RADIAL, will use consistent plane stress plasticity algorithm both for strain
rate dependent and independent plasticity. This new algorithm is more accurate than 3-D approach.
Main Index
ECHOOFF 1755
Deactivate Printed Echo
ECHOOFF Deactivate Printed Echo
Marks the point or points in the input file to deactivate printed echo of the input file.
Format:
1 2 3 4 5 6 7 8 9 10
ECHOOFF
Example:
ECHOOFF
Remarks:
1. This entry may also be used in the Executive Control and Case Control Sections. It is described in
the Case Control command, ECHO (Case).
2. The companion to this entry is the ECHOON entry.
3. The ECHOOFF command is BEGIN BULK or BEGIN SUPER = n dependent. Its last time used
does carry over between changes in BEGIN BULK or BEGIN SUPER = n commands. Also, the Case
Control ECHO command should be above subcase level and the following is recommended:
ECHO=UNSORT.
Main Index
1756 ECHOON
Activate Printed Echo
ECHOON Activate Printed Echo
Marks the point or points in the input file to activate printed echo of the input file.
Format:
1 2 3 4 5 6 7 8 9 10
ECHOON
Example:
ECHOON
Remarks:
1. This entry may also be used in the Executive Control and Case Control Sections. It is described in
the Case Control command, ECHO (Case).
2. The companion to this entry is the ECHOOFF entry.
3. The ECHOON command is BEGIN BULK or BEGIN SUPER = n dependent. Its last time used
does carry over between changes in BEGIN BULK or BEGIN SUPER = n commands. Also, the Case
Control ECHO command should be above subcase level and the following is recommended:
ECHO=UNSORT.
Main Index
EIGB 1757
Buckling Analysis Set
EIGB Buckling Analysis Set
Defines data needed to perform buckling analysis.
Format:
1 2 3 4 5 6 7 8 9 10
EIGB SID METHOD L1 L2 NEP NDP NDN
NORM G C
Example:
EIGB 13 INV 0.1 2.5 2 1 1
MAX
Describer Meaning
SID Set identification number. (Unique Integer > 0)
METHOD Method of eigenvalue extraction. (Character: “INV” for inverse power method or
“SINV” for enhanced inverse power method.)
L1, L2 Eigenvalue range of interest. (Real, L1 < L2)
NEP Estimate of number of roots in positive range not used for METHOD = “SINV”.
(Integer > 0)
NDP, NDN Desired number of positive and negative roots. (Integer>0; Default = 3*NEP)
NORM Method for normalizing eigenvectors. (Character: “MAX” or “POINT”; Default =
“MAX”)
MAX Normalize eigenvectors to the unit value of the largest component in the
analysis set. (Default).
POINT Normalize eigenvectors to the unit value of the component defined in G
and C fields. The value for NORM defaults to MAX if the defined
component is zero.
G Grid or scalar point identification number. Required only if NORM=“POINT”.
(Integer > 0)
C Component number. Required only if NORM=“POINT” and G is a geometric grid
point. (1 < Integer < 6)
Remarks:
1. The EIGB entry must be selected with the Case Control command METHOD = SID.
2. Each eigenvalue is the factor by which the pre-buckling state of stress is multiplied to produce
buckling in the shape defined by the corresponding eigenvector.
Main Index
1758 EIGB
Buckling Analysis Set
3. The continuation entry is optional. If the continuation is not specified, than NORM = “MAX”
normalization is performed.
4. If NORM = “MAX”, components that are not in the analysis set may have values larger than unity.
5. The SINV method is an enhanced version of the INV method. It uses Sturm sequence techniques to
ensure that all roots in the range have been found. It is generally more reliable and more efficient
than the INV method.
6. Convergence is achieved at 10-6.
7. For buckling solutions, the Lanczos algorithm is most reliable if it is allowed to compute the lowest
mode first, then the remainder in increasing order of magnitude. The lowest mode is usually the mode
of most interest. If the L1 and L2 fields are left blank, an estimate of the first mode eigenvalue is found
by a robust, efficient inverse iteration. If NDP and NDN are set to 1, there is a high probability that
the first mode will be computed reliably. If more modes are needed it is easier to fill out the other
fields correctly once the location of the lowest mode is known.
8. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
EIGC 1759
Complex Eigenvalue Extraction Data
EIGC Complex Eigenvalue Extraction Data
Defines data needed to perform complex eigenvalue analysis.
Format:
1 2 3 4 5 6 7 8 9 10
EIGC SID METHOD NORM G C E ND0
The following continuation is repeated for each desired search region. (J = 1 to n, where n is the number of
search regions.
)
ALPHAAJ OMEGAAJ ALPHABJ OMEGABJ LJ NEJ NDJ
Alternate Format for Continuation Entry for Block Complex Lanczos:
ALPHAAJ OMEGAAJ MBLKSZ IBLKSZ KSTEPS NJi
Examples:
EIGC 14 CLAN
+5.6 4
EIGC 15 HESS 6
Describer Meaning
SID Set identification number. (Unique Integer > 0)
METHOD Method of complex eigenvalue extraction. (Character: “INV”, “HESS”, or “CLAN”)
INV Inverse power.
HESS Upper Hessenberg. For linear perturbation of ANALYSIS= DCEIG with
large displacement, please don't use HESS. See Remarks 2. and 3.
CLAN Complex Lanczos. For linear perturbation of ANALYSIS= DCEIG with
large displacement, CLAN is recommended. See Remark 8.
IRAM Implicitly Restarted Arnoldi Method. See Remark 12.
NORM Method for normalizing eigenvectors. See Remark 7. (Character: “MAX” or “POINT”;
Default = “MAX”)
MAX Normalize the component having the largest magnitude to a unit value for
the real part and a zero value for the imaginary part.
POINT Normalize the component defined in fields 5 and 6 to a unit value for the
real part and a zero value for the imaginary part. The value for NORM
defaults to "MAX" if the magnitude of the defined component is zero.
G Grid or scalar point identification number. Required if and only if NORM = “POINT”.
(Integer > 0)
Main Index
1760 EIGC
Complex Eigenvalue Extraction Data
Describer Meaning
C Component number. Required if and only if NORM=“POINT” and G is a geometric
grid point. (0 < Integer < 6)
E Convergence criterion. (Real > 0.0. Default values are: 10-4 for METHOD = “INV”, 10-
15
for METHOD = “HESS”, E is machine dependent for METHOD = “CLAN”.)
MBLKSZ Maximum block size. See Remark 10. (Default = 7; Real > 0.0)
IBLKSZ Initial block size. See Remark 10. (Default = 2; Real > 0.0)
KSTEPS Frequency of solve. (Default = 5; Integer > 0)
Table 9-11 Relationship Between METHOD Field and Other Fields
METHOD Field
Field HESS INV CLAN
NDj (Integer > 0) Desired number of Desired number of roots and Desired number of roots
eigenvalues and eigenvectors in j-th search and eigenvectors to be
eigenvectors. (No region. extracted at j-th shift
Default) (Default = 3*NEj) point. (No Default)
ALPHAAj Not used End point Aj of j-th search j-th shift point.
OMEGAAj region in complex plane. (Default = 0.0)
Real and imaginary (Default = 0.0)
parts of Aj in radians
per unit time. (Real).
ALPHABj Not used End point Bj of j-th search See alternate definitions in
OMEGABj region in complex plane. fields MBLKSZ and
Real and imaginary (Default = 0.0) IBLKSZ below; see also
parts of Bj in radians Remark 10.
per unit time. (Real).
Lj (Real > 0.0) Not used Width of j-th search region. See alternate definitions in
(Default = 1.0) fields MBLKSZ and
IBLKSZ below; see also
Remark 10.
NEj (Integer > 0) Not used Estimated number of roots Not used
in j-th search region.
MBLKSZ Maximum Block Size
For block CLAN only Default = 7
IBLKSZ Initial Block Size
For block CLAN only Default = 2
Main Index
EIGC 1761
Complex Eigenvalue Extraction Data
OMEGA
A1
B2
L2
ALPHA
L1
A2
B1
Figure 9-89 Sample Search Regions
Remarks:
1. The EIGC entry must be selected in the Case Control Section with the command
CMETHOD = SID. Methods of solution are also controlled by SYSTEM(108) on the NASTRAN
statements.
SYSTEM(108) Specification
0 QZ HESS method or CLAN block Lanczos, as selected by EIGC entry or
(Default) equivalent PARAM input. Default value.
1 Force Householder QR (Hessenberg with spill, mass matrix must be
nonsingular)
2 Force old single vector complex Lanczos
4 Force new block complex Lanczos
8 Debugging output for Lanczos methods
16 Turn off block reduction in block complex Lanczos
32 Turn off block augmentation in block complex Lanczos
64 Turn of full orthogonality in block complex Lanczos
Main Index
1762 EIGC
Complex Eigenvalue Extraction Data
SYSTEM(108) Specification
128 Turn off preprocessing of initial vectors in block complex Lanczos
256 Force LR method (Hessenberg, no spill, mass matrix must be invertible)
512 Force QZ method
65536 Use semi-algebraic sort on imaginary part of roots (pre-V70.6 sort)
The word “force” above implies that the method selected by the system cell will be used even when
another method has been selected on an EIGC entry. Sums of these values will produce two or more
actions at once, when feasible. As the numbers get larger, the function is more developer-oriented
than user-oriented.
2. When using METHOD = “HESS”, the following should be noted:
The “HESS” method is generally more reliable and economical for small and moderate-size problems.
It computes ND eigenvalues and eigenvectors.
For linear perturbation of ANALYSIS= DCEIG with large displacement (param, lgdisp, 1) in SOL
400, HESS may yield incorrect results. Therefore, please avoid to use HESS in linear perturbation
analysis with large displacement.
3. The EIGC entry may or may not require continuations as noted below.
• For the “HESS” method, continuations are not required; and their contents are ignored when
present, except for ND1. However, it is recommended that continuations are not used.
• For the “CLAN” method when the continuation entry is not used a shift is calculated
automatically. When a shift is input on the first continuation entry it is used as the initial shift.
Only one shift is used. Data on other continuation entries is ignored.
• For METHOD = “INV”, each continuation defines a rectangular search region. Any number of
regions may be used and they may overlap. Roots in overlapping regions will not be extracted
more than once.
• For all methods, if no continuation is present, then ND0 must be specified on the first entry. If
a continuation is present, then NDj must be specified on the continuation and not on the first
entry.
4. The units of ALPHAAJ, OMEGAAJ, ALPHABJ, and OMEGABJ are radians per unit time.
5. DIAG 12 prints diagnostics for the inverse power method, the complex Lanczos method and the QZ
HESS method.
6. If METHOD = “HESS” and the LR or QR methods (non-default methods) are selected by system
cell 108 the mass matrix must be nonsingular. The default QZ method does not require a nonsingular
mass matrix.
7. The normalized eigenvectors may be output with the SDISPLACEMENT and/or
DISPLACEMENT Case Control commands.
Main Index
EIGC 1763
Complex Eigenvalue Extraction Data
8. When using METHOD = CLAN, the following should be noted. The modern CLAN method
(default for METHOD entry of CLAN) has been enhanced to include a block complex Lanczos
approach. This method is more reliable and will not accept inaccurate roots which the old method
had a tendency to do. Thus, given the same input, the new method may often accept fewer roots. For
continuity the old method has been maintained and may be selected by setting SYSTEM(108). For
linear perturbation of ANALYSIS= DCEIG with large displacement (param, lgdisp, 1) in SOL 400,
CLAN is recommended.
9. The SVD method is provided for DMAP applications. If used in solution 107 or 110, and mass or
damping terms are present, a user fatal exit is taken. See the MSC Web site for the Flight Loads
Product examples on the use of the SVD method. The SVD operation decomposes the input stiffness
matrix K into the factors U, S, and V. U and V are collections of vectors of orthogonal functions. S
is a rectangular matrix with terms on the diagonal of its left partition. The factors satisfy the equation
K = U*S*V’, where “ ’ ” implies complex conjugate transpose. The ND1 value has a meaning for the
SVD functions which differs from eigensolution.
ND1 OUTPUT
>0 All vectors of U and V are output.
=0 U and V are returned in a purged state.
<0 S is returned as a square matrix whose number of columns is equal to the minimum
number of rows or columns of the input matrix. U and V are truncated to be
commensurate with S. This is a method to reduce the costs of solving very
rectangular input matrices by providing a partial solution for the most interesting
vectors.
10. The MBLKSZ and IBKLSZ parameters are integers in concept, but must be input at real numbers
(that is, with a decimal point.) They represent maximum sizes, and may be reduced internally for
small size problems.
11. The IRAM method is an out-of-core implementation of the public domain ARPACK complex
eigenvalue solver. To use IRAM, the mass matrix has to be symmetric or Hermitian, and the number
of modes desired can be at most the order of the generalized eigenproblem minus one. IRAM does
not compute the left eigenvectors and thus is not suitable for SOL200 design optimization analysis.
12. For the “IRAM” method, only the fields that contain EIGC, SID, METHOD, NORM, ND0, NDJ
are meaningful. The user selects the method by specifying IRAM in the METHOD field, the
eigenvector normalization scheme in the NORM field, and the number of desired modes in the ND0
or the NDj field. The other fields are irrelevant.
13. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1764 EIGP
Poles in Complex Plane
EIGP Poles in Complex Plane
Defines poles that are used in complex eigenvalue extraction by the Determinant method.
Format:
1 2 3 4 5 6 7 8 9 10
EIGP SID ALPHA1 OMEGA1 M1 ALPHA2 OMEGA2 M2
Example:
EIGP 15 -5.2 0.0 2 6.3 5.5 3
Describer Meaning
SID Set identification number. (Integer > 0)
ALPHAi,OMEGAi Coordinates of point in complex plane. (Real)
Mi Multiplicity of complex root at pole defined by point at ALPHAi and OMEGAi.
(Integer > 0)
Remarks:
1. The EIGP entry defines poles in the complex plane that are used with an associated EIGC entry
having the same set number.
2. The units of ALPHAi and OMEGAi are radians per unit time.
3. Poles are used only in the determinant method. (METHOD = “DET” on the EIGC entry).
4. One or two poles may be defined on a single entry.
5. See The NASTRAN Theoretical Manual, Section 10.3.4, for details.
6. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
EIGR 1765
Real Eigenvalue Extraction Data
EIGR Real Eigenvalue Extraction Data
Defines data needed to perform real eigenvalue analysis.
Format:
1 2 3 4 5 6 7 8 9 10
EIGR SID METHOD F1 F2 NE ND
NORM G C
Example:
EIGR 13 LAN 12
Describer Meaning
SID Set identification number. (Unique Integer > 0)
METHOD Method of eigenvalue extraction. (Character)
Modern Methods:
LAN Lanczos Method
AHOU Automatic selection of HOU or MHOU method. See Remark 13.
Obsolete Methods:
INV Inverse Power method.
SINV Inverse Power method with enhancements.
GIV Givens method of tridiagonalization.
MGIV Modified Givens method.
HOU Householder method of tridiagonalization.
MHOU Modified Householder method.
AGIV Automatic selection of METHOD = “GIV” or “MGIV”. See Remark 13.
NORM Method for normalizing eigenvectors. (Character: “MASS,” “MAX,” or “POINT”;
Default = “MASS”)
MASS Normalize to unit value of the generalized mass. (Default)
MAX Normalize to unit value of the largest component in the analysis set.
POINT Normalize to a positive or negative unit value of the component defined
in fields 3 and 4. The POINT option is not supported for
METHOD=LAN. (Defaults to “MASS” if defined component is zero.)
Main Index
1766 EIGR
Real Eigenvalue Extraction Data
Describer Meaning
G Grid or scalar point identification number. Required only if NORM = “POINT”.
(Integer > 0)
C Component number. Required only if NORM = “POINT” and G is a geometric grid
point. (1 < Integer < 6)
Table 9-12 Relationship Between METHOD Field and Other Fields for
Obsolete Methods
METHOD Field
Field INV or SINV GIV, MGIV, HOU, or MHOU
F1, F2 Frequency range of interest. F1 must be Frequency range of interest. If ND is not blank, F1
input. If METHOD = “SINV” and and F2 are ignored. If ND is blank, eigenvectors are
ND, is blank, then F2 must be input. found with natural frequencies that lie in the range
See also Remark 21. between F1 and F2. (Real > 0.0; F1 < F2)
(Real > 0.0)
NE Estimate of number of roots in range Not used.
(Required for METHOD = “INV”).
Not used by “SINV” method.
(Integer > 0)
ND Desired number of roots. If this field is Desired number of eigenvectors. If ND is zero, the
blank and METHOD = “SINV”, then number of eigenvectors is determined from F1 and
all roots between F1 and F2 are F2. If all three are blank, then ND is automatically
searched and the limit is 600 roots. set to one more than the number of degrees-of-
(Integer > 0, Default is 3 NE for freedom listed on SUPORTi entries. (Integer > 0;
METHOD = “INV” only.) Default = 0)
Remarks:
1. The EIGR entry must be selected with the Case Control command METHOD = SID.
2. See Real Eigenvalue Analysis in the MSC Nastran Dynamic Analysis Guide for a discussion of method
selection.
3. The units of F1 and F2 are cycles per unit time.
4. The continuation entry is optional. If the continuation entry is not specified, then mass normalization
is performed.
5. The contemporary methods are LAN and AHOU. The other methods are in a maintenance-only
status, with no enhancements planned for them. They may be eliminated in a future release
of Nastran.
Main Index
EIGR 1767
Real Eigenvalue Extraction Data
6. The LAN method is the most general-purpose method, and may be used on both small- and large-
size problems. It takes advantage of sparsity of input matrices, leading to greater efficiency on large-
size problems. Because Lanczos performance is tuned for medium to large problems, this has caused
difficulties with very small problems. Thus, by default, on problems with fewer than 20 degrees-of-
freedom when the LAN method is selected, the method is switched to AHOU. The criteria for
automatic switching is controlled by SYSTEM(359) on the NASTRAN entry. The NE, G, and C
fields are ignored for the LAN method. The NORM field may be set to MASS (the default value) or
MAX. The conventions used when both the Fi and ND fields are specified are described in Table 9-13
of the EIGRL entry description. The EIGRL entry is an alternate method to select the LAN method.
It has several other input options for special cases. When both and EIGRL and EIGR have the same
SID and that SID is selected by a METHOD command the EIGRL entry takes precedence.
7. The AHOU method is competitive with the LAN method when there are small, dense matrices and
many eigenvectors are required. This most commonly occurs when static or dynamic reduction is
performed. The AHOU method does not take advantage of matrix sparsity, so that computation cost
rises with the cube of the number of DOFs. The AHOU method responds to all permitted values for
all the other fields except NE, which is ignored.
8. All methods require a positive semi-definite (psd) mass matrix for stable solutions. The mass matrix
may be tested for this condition for all methods of solution by setting SYSTEM(303). A value of “-
4” should be sufficient to identify problem matrices. A fatal error exit is taken when it is not met. All
Nastran metric elements are designed to produce psd mass matrices. CMASSi elements, DMIG
matrices selected by the M2GG command, and matrices input via INPUTT4 are special methods
that allow addition of non-psd terms by use of non-metric element input. If none of this type of
special input is present and the fatal error exit is taken you may have encountered an error in a metric
element. Contact your local MSC technical representative for corrective action in this case.
9. The LAN and AHOU methods allow singular but positive semi-definite mass matrices.
10. The tridiagonal methods include the xGIV and xHOU methods, where “x” is described in the
following comments. All tridiagonal methods compute all eigenvalues, and the number of
eigenvectors specified by the Fi and Nd fields, as described in Table 9-12.
11. If “x” is blank (for example, the HOU method is selected) the mass matrix must be non-singular.
12. If “x” is M (for example, the MHOU method is selected) the mass matrix may be singular. A
modified, shifted problem is solved in an inverse basis with this method. Some precision in the
solution and longer computation time is exchanged for a more stable solution.
13. If “x” is A (for example, the AHOU method is selected) an attempt is made to solve the problem
without shifting, in the interest of cost reduction and maximum precision. If the mass matrix is
determined to be poorly conditioned for inversion the basis is automatically shifted with the modified
method.
14. If NORM = “MAX”, components that are not in the analysis set may have values larger than unity.
15. If NORM = “POINT”, the selected component should be in the analysis set (a-set). (The program
uses NORM = “MAX” when it is not in the analysis set.) The displacement value at the selected
component will be positive or negative unity.
Main Index
1768 EIGR
Real Eigenvalue Extraction Data
16. The “SINV” method is an enhanced version of the “INV” method. It uses Sturm sequence number
techniques to make it more likely that all roots in the range have been found. It is generally more
reliable and more efficient than the “INV” method.
–6
17. For the “INV” and “SINV” methods, convergence is achieved at 10 . Convergence is tested by
other criteria for the other methods.
18. For the “SINV” method only, if F2 is blank, the first shift will be made at F1, and only one
eigensolution above F1 will be calculated. If there are no modes below F1, it is likely that the first
mode will be calculated. If there are modes below F1 (including rigid body modes defined by
SUPORT entries), a mode higher than the first mode above F1 may be calculated.
19. When F1, F2, and ND are all zero or blank, ND is reset to 1. A User Warning Message is produced
for this condition, which is interpreted as likely to be due to an inadvertent omission by the user.
20. For buckling solutions, the Lanczos algorithm is most reliable if it is allowed to compute the lowest
mode first, then the remainder in increasing order of magnitude. The lowest mode is usually the mode
of most interest. If the F1 and F2 fields are left blank, an estimate of the first mode eigenvalue is found
by a robust, efficient inverse iteration. If ND is set to 1, there is a high probability that the first mode
will be computed reliably. If more modes are needed it is easier to fill out the other fields correctly
once the location of the lowest mode is known.
21. F2 must be specified if DOMAINSOLVER ACMS or DOMAINSOLVER MODES is also specified
in the Executive Control Section.
22. For large sized problems, Lanczos is the most efficient and is the recommended method for large
problems.
23. It is not recommended to use AHOU, HOU, MHOU if RIGID=LAGRAN case control.
24. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
EIGRL 1769
Real Eigenvalue Extraction Data, Lanczos Method
EIGRL Real Eigenvalue Extraction Data, Lanczos Method
Defines data needed to perform real eigenvalue (vibration or buckling) analysis with the Lanczos method.
Format:
1 2 3 4 5 6 7 8 9 10
EIGRL SID V1 V2 ND MSGLVL MAXSET SHFSCL NORM
option_1 = value_1 option_2 = value_2, etc.
Example:
EIGRL 1 0.1 3.2 10
NORM=MAX NUMS=2
Describer Meaning
SID Set identification number. (Unique Integer > 0)
V1, V2 For vibration analysis: frequency range of interest. For buckling analysis: eigenvalue
16 16
range of interest. See Remark 4. (Real or blank, – 5 10 V1 V2 5. 10 )
ND Number of roots desired. See Remark 4. (Integer > 0 or blank)
MSGLVL Diagnostic level. (0 < Integer < 4; Default = 0)
MAXSET Number of vectors in block or set. See Remark 13.
SHFSCL Estimate of the first flexible mode natural frequency. See Remark 9. (Real or blank)
NORM Method for normalizing eigenvectors (Character: “MASS” or “MAX”)
MASS Normalize to unit value of the generalized mass. Not available for buckling
analysis. (Default for normal modes analysis.)
MAX Normalize to unit value of the largest displacement in the analysis set.
Displacements not in the analysis set may be larger than unity. (Default for
buckling analysis.)
ALPH Specifies a constant for the calculation of frequencies (Fi) at the upper boundary
segments for the parallel method based on the following formula. See Remark 12.
(Real > 0.0; Default = 1.0):
i
1 – ALPH
ALPH< 1.0, Fi = V1 + V2 – V1 ----------------------------------------
NUMS
1. – ALPH
i
ALPH = 1.0, Fi = V1 + V2 – V1 -----------------
NUMS
NUMS Number of frequency segments for the parallel method. (Integer > 0; Default = 1)
Main Index
1770 EIGRL
Real Eigenvalue Extraction Data, Lanczos Method
Describer Meaning
Fi Frequency at the upper boundary of the i-th segment. See Remark 12. (Real or blank;
V1 F1 F2 F15 V2 )
option_i= Assigns a value to the fields above except for SID. ALPH, NUMS, and Fi must be
value_i specified in this format. V1, V2, ND, MSGLVL, MAXSET, SHFSCL, and NORM
may be specified in this format as long as their corresponding field is blank in the
parent entry.
Remarks:
1. Real eigenvalue extraction data sets must be selected with the Case Control command
METHOD = SID.
2. The units of V1 and V2 are cycles per unit time in vibration analysis, and are eigenvalues in buckling
analysis. Each eigenvalue is the factor by which the prebuckling state of stress is multiplied to produce
buckling in the shape defined by the corresponding eigenvector.
3. NORM = “MASS” is ignored in buckling analysis and NORM = “MAX” will be applied.
4. The roots are found in order of increasing magnitude; that is, those closest to zero are found first.
The number and type of roots to be found can be determined from Table 9-13.
Table 9-13 Number and Type of Roots Found with EIGRL Entry
V1 V2 ND Number and Type of Roots Found
V1 V2 ND Lowest ND or all in range, whichever is smaller.
V1 V2 blank All in range
V1 blank ND Lowest ND in range [V1,+]
V1 blank blank Lowest root in range [V1,+]
blank blank ND Lowest ND roots in [-,+]
blank blank blank Lowest root. See Remark 10.
blank V2 ND Lowest ND roots below V2
blank V2 blank All below V2
5. In vibration analysis, if V1 < 0.0, the negative eigenvalue range will be searched. (Eigenvalues are
proportional to Vi squared; therefore, the negative sign would be lost.) This is a means for diagnosing
improbable models. In buckling analysis, negative V1 and/or V2 require no special logic.
6. Eigenvalues are sorted on order of magnitude for output. An eigenvector is found for each eigenvalue.
7. MSGLVL controls the amount of diagnostic output during the eigenvalue extraction process. The
default value of zero suppresses all diagnostic output. A value of one prints eigenvalues accepted at
each shift. Higher values result in increasing levels of diagnostic output.
Main Index
EIGRL 1771
Real Eigenvalue Extraction Data, Lanczos Method
8. In vibration analysis, if V1 is blank, all roots less than zero are calculated. Small negative roots are
usually computational zeroes which indicate rigid body modes. Finite negative roots are an indication
of modeling problems. If V1 is set to zero, negative eigenvalues are not calculated.
9. A specification for SHFSCL may improve performance, especially when large mass techniques are
used in enforced motion analysis. Large mass techniques can cause a large gap between the rigid body
and flexible frequencies. If this field is blank, a value for SHFSCL is estimated automatically.
10. On occasion, it may be necessary to compute more roots than requested to ensure that all roots in the
range have been found. However, this method will not output the additional roots.
11. NASTRAN SYSTEM(146) (also known as FBSMEM) provides options for I/O reduction during
FBS operations according to the following table.
Table 16 SYSTEM(146) Options
SYSTEM(146)
(default=0) Description
-1 or 0 Use available memory to store as much of the factor matrix as possible
during FBS operations. System Information Message 4199 is printed in
the F04 file.
1 Disable all special memory operations for FBS.
2 Increase memory reserved for sparse method by approximately 200%.
3 Increase memory reserved for sparse method by approximately 300%.
4 Increase memory reserved for sparse method by approximately 400%.
12. For the distributed parallel method, the frequency range between V1 and V2 may be subdivided into
segments that can then be analyzed in parallel. V1 and V2 must be specified for the parallel method.
NUMS must be specified greater than 1 to take advantage of the parallel method. NUMS may also
be specified on the NUMSEG keyword of the NASTRAN statement. Currently, NUMSEG must
equal the number of processors and by default NUMSEG is set to the number of processors requested
by the DMP keyword. If both are specified, then NUMS takes precedence.
The upper frequencies of each segment may be generated automatically by ALPH or specified directly
in Fi. If both are specified, then Fi takes precedence over ALPH as long as they are consistent. ALPH
if multiplied by 100 may also be specified on FRQSEQ keyword of the NASTRAN statement.
13. Increasing MAXSET may improve performance for large problems where a large number of
eigenvalues are being found. The default is 7 on all machines. SYSTEM(263) may be set in an rcfile
to effectively modify the default; however the setting on the EIGRL entry always takes precedence.
The optimal MAXSET, also known as Lanczos block size, should be at least one more than the
number of repeated eigenvalues. For example, for a model that has six rigid body modes (six zero-
frequency eigenvalues), the recommended block size is 7. Additionally, the MAXSET value can also
be increased to help with numerical orthogonalization during the Lanczos recurrence, for models with
many closely spaced roots. Note that there must be sufficient memory to keep 'MAXSET' vectors in
memory; otherwise, the MAXSET (Lanczos block size) will be reduced automatically. Maximum
Main Index
1772 EIGRL
Real Eigenvalue Extraction Data, Lanczos Method
value for MAXSET is 50. Activate Lanczos message level 1 (EIGRL field 6) to see Lanczos diagnostic
messages. Note also that DIAG 16 is equivalent to Lanczos message level 1.
Note that MAXSET can be also defined in the command line if EIGRL does not include it. When
MAXSET in command line is set, new block size will be limited to problem size/2.
14. SYSTEM(196), keyword SCRSAVE, controls reuse of scratch files when segment logic is invoked.
SYSTEM(196) is useful only when multiple frequency segments are requested on a Lanczos run.
(Multiple frequency segments can be requested via the NUMS field in the EIGRL entry and by
SYSTEM(197).) Each frequency segment requires a minimum of three scratch files. When multiple
frequency segments are used on a single processor computer then each frequency segment is solved
serially. In this case, it makes sense to let segment #2 use the scratch files which were used by segment
#1 since work for segment #1 has been completed (otherwise it wouldn’t be working on #2).
Similarly, when work for segment #2 is finished, segment #3 should be able to use #2’s scratch files.
SYSTEM(196)=1 allows such file reuse and is considered a safe default on Version 70 and later
systems.
15. The new buckling shift logic in Version 70.5 tends to shift to 1.0 first. The logic may have difficulty
finding the lowest ND roots if a problem requests a small number of roots (ND) when there are
thousands of roots below 1. In this case either the loading should be scaled, SHFSCL specified, or a
smaller frequency range requested.
16. Because Lanczos performance is tuned for medium to large problems, this has caused difficulties with
very small problems. Thus, by default, on problems with fewer than 20 degrees-of-freedom when the
LAN method is selected, the method is switched to AHOU. The criteria for automatic switching is
controlled by SYSTEM(359) on the NASTRAN entry.
17. V2 must be specified if DOMAINSOLVER ACMS or DOMAINSOLVER MODES is also specified
in the Executive Control Section.
18. For buckling solutions, the Lanczos algorithm is most reliable if it is allowed to compute the lowest
mode first, then the remainder in increasing order of magnitude. The lowest mode is usually the mode
of most interest. If the V1 and V2 fields are left blank, an estimate of the first mode eigenvalue is
found by a robust, efficient inverse iteration. If ND is set to 1, there is a high probability that the first
mode will be computed reliably. If more modes are needed it is easier to fill out the other fields
correctly once the location of the lowest mode is known.
19. For buckling solutions, if V1 is explicitly set to 0.0, negative eigenvalues will be calculated based on
a negative shift value. This is done to avoid singularities resulting from a shift at 0.0. If V1 is set to a
small positive value, then negative eigenvalues will not be calculated. This behavior was changed with
the MSC Nastran 2010 release whereas before setting V1 to 0.0 yielded no negative eigenvalues. The
best approach, however, is to follow the suggestion from Remark 19.
20. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
ELEMUDS 1773
Element Property User Defined Service or Subroutine
ELEMUDS Element Property User Defined Service or Subroutine
Allows the user to provide element property routines for use with specified Nastran elements.
Format:
1 2 3 4 5 6 7 8 9 10
ELEMUDS PID PTYPE GROUP UNAME DEPEN NMLSPD
“INT” IDATA1 IDATA2 IDATA3 IDATA4 IDATA5 IDATA6 IDATA7
IDATA8 IDATA9 ... ... IDATAn
“REAL” RDATA1 RDATA2 RDATA3 RDATA4 RDATA5 RDATA6 RDATA7
RDATA8 RDATA9 ... ... RDATAn
“CHAR” CDATA1 CDATA2 ... ... CDATAn
Examples:
In FMS Section of Nastran input stream:
CONNECT SERVICE ELEMENT ‘SCA.MDSolver.Util.Ums’
In Bulk Data:
ELEMUDS 17 PBUSH2D ELEMENT THPAD FREQ
Describer Meaning
PID Element property identification number that matches the identification number on a
PBUSH2D element property entry. (Integer > 0)
PTYPE The name of the element entry. Currently supported element property entry is:
PBUSH2D. (Character; no Default)
GROUP The group name used for the FMS section CONNECT SERVICE statement. (Character;
no Default)
UNAME User subroutine name associated with the entry. See Remark 6.(Character)
DEPEN Specifies if element is frequency dependent. DEPEN=NOM or blank; user element is not
frequency dependent. DEPEN=FREQ; user element is frequency dependent. (Character
default=NOM)
NMLSPD Nominal speed (cycles per second) used by the CBUSH2DA to calculate nominal
stiffness, mass and damping terms. Nominal terms will be used during reduction and real
eigenvalue solution. In a frequency-dependent problem, updated values will be calculated
at each frequency.
“INT” Keyword indicating that the following data is integer. (Character)
IDATAi Additional user supplied Integer data not already existing on the specified property entry.
(Integer; no Default)
“REAL” Keyword indicating that the following data is real. (Character)
Main Index
1774 ELEMUDS
Element Property User Defined Service or Subroutine
RDATAi Additional user supplied Real data not already existing on the specified property entry.
(Real; no Default)
“CHAR” Keyword indicating that the following data is Character. (Character)
CDATAi Additional user supplied Character data not already existing on the specified property
entry. (Character; no Default)
Remarks:
1. This entry triggers the call to a user element property subroutine for advanced nonlinear materials.
The GROUP must match the GROUP field of the CONNECT SERVICE FMS statement.
2. On the FMS CONNECT statement, only the CONNECT SERVICE can be used with this entry.
3. PID must match an existing PID.
4. A CDATAi entry cannot be the Character “REAL”, “INT”, or “CHAR”.
5. Certain user subroutines may require integer, real, or character data input as specified in the User
Defined Services manual.
6. UNAME must be truncated to 8 characters in the bulk data field
7. If the ROMAC interface is being used then UNAME=THPAD is required. See the THPAD Bulk
Data entry (p. 2920) for a description of ROMAC service. (http://www.virginia.edu/romac/)
Main Index
ELIST 1775
Element List
ELIST Element List
Defines a list of CQUAD4 and CTRIA3 structural elements for virtual fluid mass.
Format:
1 2 3 4 5 6 7 8 9 10
ELIST LID E1 E2 E3 E4 E5 E6 E7
E8 E9 E10 -etc.-
Example:
ELIST 3 51 -62 68 THRU 102 122
Describer Meaning
LID Identification number of list. (Integer > 0)
Ei Identification number of a structural element. See Remark 1. for the meaning of the
negative sign. The string “THRU” may be used to indicate that all existing elements
between those referenced in the preceding and succeeding fields are in the list.
(Integer 0 or “THRU”)
Remarks:
1. If the ELIST entry is referenced by field 6 of an MFLUID entry, the wetted side of the element is
determined by the presence or absence of a minus sign preceding the element’s ID on the ELIST
entry. A minus sign indicates that the fluid is on the side opposite to the element’s positive normal
as determined by applying the right-hand rule to the sequence of its corner points. If the “THRU”
option is used, then immediately preceding and succeeding elements must have the same sign.
2. Large open “THRUs” should be avoided.
3. The word “THRUs” must not appear in field 2 or 9 on the parent entry or on any continuations.
4. If any ELIST entry is changed or added on restart then a complete re-analysis may be performed.
Therefore, ELIST entry changes or additions are not recommended on restart.
Main Index
1776 ENDDATA
Bulk Data Delimiter
ENDDATA Bulk Data Delimiter
Designates the end of the Bulk Data Section.
Format:
ENDDATA
Remark:
1. ENDDATA is optional.
Main Index
ENDDYNA 1777
Defines the End of Direct Text to Dytran
ENDDYNA Defines the End of Direct Text to Dytran
All entries between TODYNA and ENDDYNA will be passed directly by SOL 700 to Dytran. Used in SOL
700 only.
Format:
1 2 3 4 5 6 7 8 9 10
ENDDYNA
Example:
TODYNA
MAT1 345 29.0E6 0.285 0.0004
ENDDYNA
Describer Meaning
TODYNA
MAT1
ENDDYNA
Remarks:
See TODYNA for details of how this entry is used.
Main Index
1778 EOSDEF
Deflagration - SOL 700 only
EOSDEF Deflagration - SOL 700 only
EOSDEF defines the properties of the deflagration equation of state, and the reaction rate to model the
burning of solid propellants. The burning of the solid propellant produces hot gas.
With limitati ons of Dytran solver, the solid propellant is no t modeled, and only the hot gas i s model ed. During burning hot gas flows into the Euler elements
Format
1 2 3 4 5 6 7 8 9 10
EOSDEF MID GAMMA B R Cv Cp E RHOS
RHOF W BETA SAVR X Y
Example
1 2 3 4 5 6 7 8 9 10
EOSDEF 3 1.123 0.001 304 IE+6 1600
0.1 4E-8 0.85 6000 0.6 0.0
Field Contents
MID Unique material number. (Integer > 0; Required).
GAMMA Constant . (Real>0; Required)
B Gas co-volume. (Real≥0; Required)
R Gas constant. (Real>0; Refer to remark 2.)
CV Specific heat at constant volume. (Real>0; Refer to remark 3.)
CP Specific heat at constant pressure. (Real>0; Refer to remark 3.)
E Chemical energy per unit burned mass. (Real>0.0; Required)
RHOS Reference density of propellant. (Real>0; Required).
RHOF Density of powder
------------------------------------------------------------------------
- (Real>0; Refer to remark 5.)
reference density of propellant
W Burning rate coefficient (Real≥0; Required).
BETA Burning rate exponent. (Real≥0; Required).
SAVR Initial surface area divided by volume (Real>0; Required).
X Parameter form function(Real>0; Required).
Y Parameter form function(Real>0; Required).
Main Index
EOSDEF 1779
Deflagration - SOL 700 only
Remarks
1. EOSDEF – The deflagration Equation of State is explained in Dytran Theory Manual, Chapter 4:
Models.
2. This equation of state is used with Eulerian elements.
3. The temperature of gas is calculated when one of the constants R, C v or C p are specified. When
temperature is not mentioned in an output request, omit the he constants .
4. The pressure in the reaction products is defined by the Noble-Abel equation of state as follows:
= – 1 --------------- e for reacted product,
1 – b
– 1 e
T = -------------------- where , b are constants and R is the gas constant.
R
The chemical reaction rate for conversion of un-reacted explosive to reaction products is mentioned
the relation below:
= wSAVR vivacity
X form function
= 1 – F + YF
dF- time derivative of burn fraction
------ = p
dt
where;
w= burning rate coefficient
= burning rate exponent
SAVR = initial surface area divided by volume
Y= parameter form function
S= parameter form function
5. RHOF allows taking into account the air between gunpowder grains. Also, it allows taking into
account air inside the combustion chamber. For example If the chamber is filled with 10% real
propellant and the rest is filled with air then RHOF = 0.1.
6. To indicate what Eulerian regions can burn, the variable DEFMAT can be used. In regions that can
burn DEFMAT=1. DEFMAT can be set on the TICVAL card:
TICVAL,14,,DENSITY,1.14,SIE,300000.2,DEFMAT,1.0
7. Ignition of the propellant approached by setting SIE to the flame temperature in specific areas:
TICVAL,15,DENSITY,1.14,SIE,4231908.591,DEFMAT,1.0
Where SIEignition = Flame Temp x Cv
Main Index
1780 EOSDEF
Deflagration - SOL 700 only
Flame Temp can be extracted from Chemical Energy per unit burned mass and Gas constant: Tflame
=E/R.
Main Index
EOSGAM 1781
Gamma Law Gas Equation of State - SOL 700 only
EOSGAM Gamma Law Gas Equation of State - SOL 700 only
Defines the properties of a Gamma Law equation of state where the pressure p is defined as:
p = – 1 e
where:
e = specific internal energy per unit mass
= overall material density
= A constant
Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
EOSGAM EID GAMMA R CV CP VISC
Example:
EOSGAM 2 1.4 287.0
Describer Meaning
EID Unique equation of state number. (Integer > 0, Required)
GAMMA Constant . (Real > 0, default=blank)
R Gas constant. See Remarks 1. and 3. (Real > 0, default=blank)
CV Specific heat at constant volume. See Remarks 1. and 3. (Real > 0, default=blank)
CP Specific heat at constant pressure. See Remarks 1. and 3. (Real > 0, default=blank)
VISC Viscosity coefficient. If zero, no viscosity. See Remarks 4., 5., and 6. (Real > 0,
default=blank)
Remarks:
1. The temperature of the gas will be calculated when one of the gas constants, R, C v or C p is specified.
2. The Euler variable name for temperature is TEMPTURE.
3. , R, C v and C p have the following relationships:
cp
= ----- R = cp – c
c
Main Index
1782 EOSGAM
Gamma Law Gas Equation of State - SOL 700 only
4. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
gradient. The SI-unit of viscosity is
Ns kg
Pa s = ------- = -------
M
2 ms
5. If possible, use (in coupled analysis) the FASTCOUP coupling algorithm because viscous fluxes are
computed more accurately for fast coupling than for general coupling.
6. For the single mat solver, viscous stresses can be requested by the use of TXX through TZX. Also,
EFFSTS is available. For the multi-material solver, viscous stresses are stored in TXX-VIS, TYY-VIS,
TZZ-VIS, TXY-VIS, TYZ-VIS, TZX-VIS. This viscous stresses depend only on the current velocity
gradients. The stresses like TXX are elastic-plastic stresses and depend on past stress. The total stress
tensor in the element is given by the average of the viscous stress and elastic-plastic stress. The weight
factors are the material fraction of viscous fluid and the remaining materials.
Main Index
EOSIG 1783
Ignition and Growth Equation of State - SOL 700 only
EOSIG Ignition and Growth Equation of State - SOL 700 only
Defines the properties of Ignition and Growth equation of state and the reaction rate equation used to model
high explosives. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
EOSIG EID UNITDEF DBEXPL UNITCNV +
+ AE BE R1E R2E OMGE I G +
+ A AP BP R1P R2P OMGP X Y +
+ Z R ECHEM PRSTOL ITRMAX
Example:
EOSIG 10 LX17 SI
Describer Meaning
EID Unique equation of state number referenced from MATDEOL. (Integer > 0; Required)
UNITDEF User-defined default unit for the inputs: See Remarks 2. and 3. (Character)
CCGMS m/g/ s units
SI International System units
METRIC Metric units
IMPER imperial units
MMMG mm/mg/ s units
DBEXPL Use explosive material from the database (See Remarks 4. and 6.) (Character, NO). The
following detonation materials are available in the data base:
NO The database is not used. See Remark 5.
P94A PBX-9404 (a) explosive
TATB TATB explosive
PENT PETN explosive
CTNT Cast TNT explosive
LCOMPB LANL COMP B explosive
MCOMPB Military COMP B explosive
P94B PBX-9404 (b) explosive
LX17 LX-17 explosive
UNITCNV User defined conversion units: (Character; see Remarks 2. and 3.)
CGMS cm/g/ s units
Main Index
1784 EOSIG
Ignition and Growth Equation of State - SOL 700 only
Describer Meaning
SI International System units
METRIC Metric units
IMPER Imperial units
MMMGS mm/mg/ s units
AE Constant A e for un-reacted explosive. See Remark 5. (Real; Required)
BE Constant B e for un-reacted explosive. See Remark 5. (Real; Required)
R1E Constant R 1e for un-reacted explosive. See Remark 5. (Real; Required)
R2E Constant R 2e for un-reacted explosive. See Remark 5. (Real; Required)
OMGE Constant e for un-reacted explosive
I First ignition coefficient. See Remark 5. (Real; Required)
G Second ignition coefficient. See Remark 5. (Real; Required)
A Density ignition coefficient. See Remark 5. (Real; Required)
AP Constant Ap for reacted product. See Remark 5. (Real; Required)
BP Constant Bp for reacted product. See Remark 5. (Real; Required)
R1P Constant R1p for reacted product. See Remark 5. (Real; Required)
R2P Constant R2p for reacted product. See Remark 5. (Real; Required)
OMGP Constant p for reacted product. See Remark 5. (Real; Required)
X Surface burning exponent. See Remark 5. (Real, 2./9.)
Y Surface burning exponent. See Remark 5. (Real, 2./3.)
Z Pressure exponent. See Remark 5. (Real; Required)
R Relative density exponent. See Remark 5. (Real, .4)
ECHEM Chemical energy of high explosive per unit mass. See Remark 5. (Real; Required)
PRSTOL Tolerance for pressure equilibrium iterations in mixed phase elements. (Real > 0, 1.E-6)
ITRMAX Maximum number of iterations in pressure equilibrium iterations. (Integer > 0, 16)
Remarks:
1. This equation of state can only be used with solid Eulerian elements.
2. The definition of the unit system in which the input values are defined is required information only
in case you wish to have an automatic conversion to a different unit system as defined by the
UNITCNV field. In case you are using the conversion mechanism, note that the density RHO in the
corresponding MATDEUL entry will be interpreted in the unit system defined here. Table 9-14
defines sets of units available:
Main Index
EOSIG 1785
Ignition and Growth Equation of State - SOL 700 only
Table 9-14 Sets of Units Used in the IG Model
Quantity CGµs SI Metric Imperial MMMGµs
Length Centimeter (cm) Meter (m) Centimeter Inch (in) Millimeter
(cm) (mm)
Time Microsecond (µs) Second (s) Second (s) Second (s) Microsecond
(µs)
Mass Gram (g) Kilogram Gram (g) Slug (lbf-s2/in) Milligram
(kg) (mg)
Force Teradyne Newton (N) Dyne Pound force kN
(lbf)
Density g/cm3 Kg/m3 g/cm3 lbf-s2/in4 mg/ mm3
Stress Mbar Pascal (Pa) µbar Lbf/in2 GPa
Energy 1012 erg (Mbars-cm3) Joule (J) Erg Lbf-in J
Temperature Kelvin (K) Kelvin (K) Kelvin (K) Kelvin (K) Kelvin (K)
3. The UNITCNV field defines the unit system to which the material parameters are converted. In case
you are not using one of the database material models, you also have to define the default unit system
(UNITDEF) in which you supplied the data.
4. You can use the database containing several detonation materials to start the analysis. The material
data are taken from Lee/Tarver (Ref. 1) and Murphy/Lee (Ref. 2) papers in the Theory Manual. The
equations of state parameters are given in the Table 9-15.
5. The default setting for DBEXPL is NO, which means you should define the values in the input fields
(fields 12 to 36). If the database material name is defined, all values in the input fields will be
overridden. The reference density RHO defined on the corresponding MATDEUL entry will be set
to the value from the database.
6. The default unit system for the material database parameters is the CGMS unit system. If you wish
to use the material base data in a different unit system, you can specify this by defining the target unit
system in the UNITCNV field.
7. You can define the shear property and yield model of the material with respectively SHXXX and
YLDXX entry. Note that the unit system of data required in these entries should be consistent with
the unit system defined in the UNITCNV field.
8. The IG equation of state cannot be used in combination with a spallation model.
9. The following JWL equation of state is used to calculate the pressure of the un-reacted explosive (in
“solid” state):
Main Index
1786 EOSIG
Ignition and Growth Equation of State - SOL 700 only
– R 1e – R 2e
e e ----------
e
-
e e ----------
e
-
p e = A e 1 – ------------ e + B e 1 – ------------ e + e e e Ee
R 1e R 2e
where:
e = e 0 the relative density of the unreacted explosive.
Ee the specified internal energy per unit mass of the unreacted
explosive
0 the initial density of the explosive
A e B e e R 1e R 2e the input constants of the unreacted explosive
Similarly, the pressure in the reaction products (in “gas” state) is defined by another JWL form as
follows:
– R 1p – R 2p
1 p p ----------
p
-
p p ----------
p
-
p p = A p 1 – ------------- e + B p 1 – ------------- e + p p p Ep
R 1p R 2p
where:
p = p 0 = the relative density of the unreacted explosive
Ep = the specified internal energy per unit mass of the unreacted explosive
A p B p p R 1p R= 2p the input constants of the reaction product. The chemical reaction rate
for conversion of un-reacted explosive to reaction products is described
by the following reaction rate equation:
F x r x y z
------ = I 1 – F e – 1 – a + G 1 – F F P
t
here F denotes the burn fraction that is defined as the fraction of the
explosive that has already reacted. For more details concerning the
implementation of this equation of state, please refer to the Theory
Manual
Main Index
EOSIG 1787
Ignition and Growth Equation of State - SOL 700 only
10. You can access the results of the un-reacted explosive and reaction products for IG elements. These
EOSIG specific output variables are
Keyword Description
SIE-E Specific internal energy per unit mass of un-reacted explosive part
SIE-P Specific internal energy per unit mass of reaction products part
FMAT Volume fraction
RHO-E Density of un-reacted explosive part
RHO-P Density of reaction products part
MASS-E Mass of un-reacted explosive part
MASS-P Mass of reaction products part
The output variables for the burn fraction are
Keyword Type of Elements Description
Solid Lagrangian Burn fraction of EOSIG material
Elements
FBURN
Euler Elements Not applicable for EOSIG materials. Burn fraction for
EOSJWL material
Solid Lagrangian Not available
IGBURN Elements
Euler Elements Burn fraction of EOSIG MATERIAL
11. The ignition of IG material can be initiated by:
a. Compression of the IG material in a small region, where the compression originates from outside
that region. This is the most physical method to initiate ignition. Examples are a shock wave
entering the region, a flow boundary that supplies mass to the region and a plate or other
structural part that compresses the region. In all these cases the IG material should be initialized
with zero pressures. This can be achieved by not specifying the specific energy on the TICVAL
entry that prescribes the initial state of the IG material. The specific energy will be computed such
that the initial pressure is zero.
b. Compression of the IG material in a small region where the compression originates within that
region. This can be done by specifying either a density that exceeds the compression limit or a
specific energy that gives rise to a sufficiently large pressure.
Main Index
1788 EOSIG
Ignition and Growth Equation of State - SOL 700 only
Table 9-15 Coefficients for the IG Model of Several Explosions in the Database.
PBX- LANL Military PBX-
Explosive 9404 (a) TATB PETN Case TNT COMP B COMP B 9404 (b) LX-17
Unreacted Equation of State and Constitutive Values:
RHO 1.842 1.90 1.842 1.61 1.712 1.630 1.842 1.903
(g/cm3)
AE (Mbar) 69.69 108.2 37.42 17.98 778.1 1479. 9522. 778.1
BE (Mbar) -1.727 -2.406 -1.313 -0.931 -0.05031 -0.05261 -0.5944 -0.05031
R1E 7.8 8.2 7.2 6.2 11.3 12. 14.1 11.3
R2E 3.9 4.1 3.6 3.1 1.13 1.2 1.41 1.13
OMGE 0.8578 1.251 1.173 0.8926 0.8938 0.9120 0.8867 0.8938
Reacted Product Equation of State Values:
AP (Mbar) 8.524 6.5467 6.17 3.712 5.242 5.5748 8.524 6.5467
BP (Mbar) 0.1802 0.071236 0.16926 0.032306 0.07678 0.0783 0.1802 0.071236
R1P 4.6 4.45 4.4 4.15 4.2 4.5 4.6 4.45
R2P 1.3 1.2 1.2 0.95 1.1 1.2 1.3 1.2
OMGP 0.38 0.35 0.25 0.30 0.34 0.34 0.38 0.35
ECHEM 0.0554 0.0363 0.0548 0.0433 0.0496 0.04969 0.0554 0.03626
(Mbar-cm
3/g)
Reaction Rate Parameters:
I ( s-1) 44.0 50.0 20.0 50.0 44.0 44.0 44.0 50.0
G (Mbar- 200.0 125.0 400.0 40.0 414.0 514.0 850.0 500.0
z s-1)
A 0.01 0.01 0.01 0.01 0.01 0.01 0.01 0.0
Z 1.6 2.0 1.4 1.2 2.0 2.0 2.0 3.0
X 2/9 2/9 2/9 2/9 2/9 2/9 2/9 2/9
Y 2/3 2/3 2/3 2/3 2/3 2/3 2/3 2/3
R 4.0 4.0 4.0 4.0 4.0 4.0 4.0 4.0
12. EID must unique among all EOSxx entries in one model.
Main Index
EOSJWL 1789
JWL Explosive Equation of State - SOL700
EOSJWL JWL Explosive Equation of State - SOL700
Defines the properties of a JWL equation of state commonly used to calculate the pressure p of the
detonation products of high explosives
–R1 –R2
--------- --------- Q
p = p 0 + A 1 – -------- e + B 1 – -------- e + 0 e + ----------------
R R
1 2 0
d- m n
----- = a1 – p
dt
e = specific internal energy per unit mass
0 = reference density
= overall material density
= 0
p0 = initial pressure
= fraction that describes the afterburning. It ranges from 0 to 1
A , B , R 1 , R 2 , a, m, n and Q are constants.
Q
The last term: ---------------- models afterburning.
0
Format:
1 2 3 4 5 6 7 8 9 10
EOSJWL MID A B R1 R2 OMEGA P0 Q
a m N
Example:
EOSJWL 37 5.2E11 0.77E11 4.1 1.1 0.34 0.0
0.0 0.0 0.0
Main Index
1790 EOSJWL
JWL Explosive Equation of State - SOL700
Format and Example
EOSJWL MID A B R1 R2 OMEGA P0 Q +
EOSJWL 37 5.2E11 0.77E11 4.1 1.1 0.34 0.0 +
+ a m n
+ 0.0 0.0 0.0
Describer Meaning
EID Unique equation of state number referenced from MATDEUL. (Integer > 0; Required)
A Constant A. (Real, 0.0)
B Constant B. (Real, 0.0)
R1 Constant R1. (Real, 0.0)
Constant R2. (Real, 0.0)
OMEGA Constant . (Real, 0.0)
P0 Initial pressure. See Remark 3. (Real, 0.0)
Q Initial pressure. (Real, ≥ 0.0). see Remark 6.
a Initial pressure (Real, 0.0). see Remark 6.
m Initial pressure (Real, 0.0). see Remark 6.
n Initial pressure (Real, 0.0). see Remark 6.
Remarks:
1. This equation of state can be used only with Eulerian elements.
2. A DETSPH entry must be used to specify the detonation model.
3. This equation of state is discussed in Dytran Theory Manual, Chapter 4: Models, EOSJWL – JWL Equation
of State.
4. In simulations with ideal gases, the JWL material needs to have an initial pressure to counter balance
the pressure of the ideal gas. Similarly, in case of under calculations where an explosive is located at a
certain depth, P0 should be preset to equal the initial hydrostatic pressure.
5. The DETSPH definition of one EOSJWL material also applies to all other EOSJWL materials.
Therefore, the blast wave of one explosive can ignite other explosives. To prevent this linked ignition,
PARAM,JWLDET,NOLINK can be used.
6. By default the constants a,m,n and Q are zero, and afterburning is not taken into account. To model
afterburning all the variables Q, a, m and n have to be set to positive constants. The extent of the
afterburning can be checked by requesting the Euler element variable AFTERBURN. This variable
equals . If the afterburning in an Euler element is complete then AFTERBURN = 1.0.
Main Index
EOSMG 1791
Mie-Gruneisen Equation of State - SOL 700 only
EOSMG Mie-Gruneisen Equation of State - SOL 700 only
Defines the properties of a Mie-Gruneisen equation of state commonly used to calculate the pressure p in
high strain rate processes. Used in SOL 700 only.
2
0 c n 0
p = ---------------------- 1 – ---------- + 0 0 e
2 2
1 – s
0
= 1 – -----
1
1 = min RM
where
e = specific internal energy per unit mass. For material at zero pressure, e has to be initialized as zero.
0 = reference density
= overall material density
0 = Gruneisen parameter at reference density.
s = defined by U s = c 0 + sU p ,where U s and U p are respectively the linear shock velocity and
particle velocity as obtained from shock data.
c = sound speed at reference density
RM = Cut-off value for density.
Format:
1 2 3 4 5 6 7 8 9 10
EOSMG EID c S R1 RM
Example:
EOSMG 37 2000 1.5 2.0 3000
Describer Meaning
EID Unique equation of state number referenced from MATDEUL. (Integer > 0; Required)
c Sound speed at reference density. (Real; Required)
s Constant s. (Real; Required)
0 Gruneisen gamma. (Real; Required)
RM Cut off value for density. (Real; Required)
Main Index
1792 EOSMG
Mie-Gruneisen Equation of State - SOL 700 only
Remarks:
1. This equation of state can be used only with Eulerian elements.
2. This equation of state is discussed in Equations of State.
3. The cut off value RM is only used for limiting the pressure. To prevent division by zero RM should
be less than s s – 1 ref . RM can be set slightly below this value. In case the simulation gets instable
because of too large pressures RM can be decreased.
4. EID must unique among all EOSxx entries in one model.
Main Index
EOSNA 1793
Noble-Abel equation of state - SOL700
EOSNA Noble-Abel equation of state - SOL700
Defines the properties of Noble-Abel equation of state where the pressure p is defined as:
p = – 1 --------------- e
1 – b
where:
e = specific internal energy per unit mass
= overall material density
= a constant
b = Gas co-volume
Format and Example
1 2 3 4 5 6 7 8 9 10
EOSNA EID GAMMA B R CV CP
EOSNA 35 1.2363 0.001 314.46
Field Contents Type Default
EID Unique equation of state number. I>0 Required
GAMMA Constant . R≥ 0.0 Required
B Gas co-volume . R≥ 0.0 0.0
Refer to Remark 3.
R Gas constant. R>0.0 Refer to remark 4.
CV Specific heat at constant volume. R>0.0 Refer to remark 4.
CP Specific heat at constant pressure R>0.0 Refer to remark 4.
Main Index
1794 EOSNA
Noble-Abel equation of state - SOL700
Remarks
1. Refer to Dytran Theory Manual: Chapter 4-Models, for EOSNA – Noble-Abel Equation of State.
2. EOSNA – Noble-Abel Equation of State is used with Eulerian elements only.
3. The parameter B models the interactions between gas particles.
4. The temperature of the gas is calculated when one of the gas constants, R , C v , and C p is
mentioned.
5. The Euler variable name for temperature is TEMPTURE.
6. The relation between Gamma, R , C v , and C p is shown below:
Cp
= ------ R = C p – C v
Cv
Main Index
EOSPOL 1795
Polynomial Equation of State for Solids - SOL 700 only
EOSPOL Polynomial Equation of State for Solids - SOL 700 only
Defines the properties of a polynomial equation of state where the pressure p is defined in SOL 700 as follows:
In compression 0 ,
2 3 2 3
p = a 1 + a 2 + a 3 + b 0 + b 1 + b 2 + b 3 0 e
In tension i 0 ,
p = a 1 + b 0 + b 1 0 e
Where
= –1
= 0
p = overall material density
p 0 = reference density
e = specific internal energy per unit mass
Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
EOSPOL EID A1 A2 A3 B0 B1 B2 B3
HVL VISC
Example:
EOSPOL 100 80.E6
1.1
Describer Meaning
EID Unique equation of state member. (Integer > 0; Required)
A1 Coefficient a1 or Bulk Modulus. (Real; Default = 0.0)
A2 Coefficient a2. (Real; Default = 0.0)
A3 Coefficient a3. (Real; Default = 0.0)
B0 Coefficient b0. (Real; Default = 0.0)
B1 Coefficient b1. (Real; Default = 0.0)
Main Index
1796 EOSPOL
Polynomial Equation of State for Solids - SOL 700 only
Describer Meaning
B2 Coefficient b2. (Real; Default = 0.0)
B3 Coefficient b3. (Real; Default = 0.0)
HVL Hydrodynamic volume limit. (Real > 1.0; Default = 1.1)
VISC Viscosity coefficient.(Real; Default = 0.0)
Remarks:
1. When the relative volume 0 exceeds HVL, the pressure is cut off to
P HVL = f HVL
with
1
HVL = ------------ – 1
HVL
e.g., for p = a1 , the pressure behavior is as follows:
a1
mHVL
m
2. When the PARAM,HVLFAIL is set to YES, the elements where the relative volume 0 exceeds
HVL fail completely. Their stress state is zero.
Main Index
EOSUDS 1797
User-defined Equation of State - SOL 700 only
EOSUDS User-defined Equation of State - SOL 700 only
Defines the frequency dependent properties for an isotropic poroelastic material. Use in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
EOSUDS EID GROUP UNAME VISC
Example:
In FMS Section of the MSC Nastran input stream:
CONNECT SERVICE water ' SCA.MDSolver.Obj.Uds.Dytran.Materials '
In Bulk Data:
1 2 3 4 5 6 7 8 9 10
EOSUDS 12 WATER EXEOS .01
Describer Meaning
EID Unique equation of state number. (Integer > 0; Required)
GROUP The group name used for the FMS section CONNECT SERVICE statement.
(Character; no Default)
UNAME User subroutine name associated with the entry. (Character; default=EXEOS)
VISC Viscosity coefficient R > 0 No viscosity. See Remarks 4.and 5.
Remarks:
1. The EID must be referenced by a MATDEUL or MAT1 entry.
2. The equation of state name is passed to method usrEOS of the SCAIMDSolver700 interface and can
be used to identify the equation of state.
3. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
gradient.
4. For the single mat solver viscous stresses will be stored in the output files by the use of TXX through
TZX. Also, EFFSTS is available. For the multi-material solver viscous stresses are stored in TXX-VIS,
TYY-VIS, TZZ-VIS, TXY-VIS, TYZ-VIS, TZX-VIS. These viscous stresses only depend on the
current velocity gradients. The stresses like TXX are elastic-plastic stresses and depend on past stresses.
The total stress tensor in the element is given by the average of the viscous stress and elastic-plastic
stress. The weight factors are the material fraction of viscous fluid and the remaining materials.
5. UNAME can be:
Subroutine Name Function
EXEOS Standard user defined Equation of State
Main Index
1798 EPOINT
Extra Point List
EPOINT Extra Point List
Defines extra points for use in dynamics problems.
Format:
1 2 3 4 5 6 7 8 9 10
EPOINT ID1 ID2 ID3 ID4 ID5 ID6 ID7 ID8
Example:
EPOINT 3 18 1 4 16 2
Alternate Format and Example:
EPOINT ID1 “THRU” ID2
EPOINT 17 THRU 43
Describer Meaning
IDi Extra point identification number. (100,000,000 > Integer > 0; for “THRU” option,
ID1 < ID2).
Remarks:
1. All extra point identification numbers must be unique with respect to all other structural, scalar, and
fluid points for direct methods of solution. For modal methods, they must be larger than the number
of eigenvectors retained for analysis.
2. EPOINT is used to define coordinates used in transfer function definitions (see the TF and DMIG
entries).
3. If the alternate format is used, extra points ID1 through ID2 are also defined to be extra points.
4. See the MSC Nastran Dynamic Analysis User’s Guide for a discussion of extra points.
Main Index
ERPPNL 1799
Equivalent Radiated Power Definition
ERPPNL Equivalent Radiated Power Definition
Defines one or more panels by referencing sets of elements or properties.
Format:
1 2 3 4 5 6 7 8 9 10
ERPPNL NAME1 SETID1 NAME2 SETID2 NAME3 SETID3 NAME4 SETID4
NAME5 SETID5
Example:
ERPPNL ROOF 1 DOORLF 16
Describer Meaning
NAMEi Panel label. (CHAR)
SETIDi Identification number of a SET3 Bulk Data entry that lists the panel property entries
or the panel elements. (Integer > 0)
Remarks:
1. The SET3 entries can only refer to 2D and/or 3D structural element types, such as QUAD4, TRIA3,
QUADR, CTRIAR, QUAD8, TRIA6, HEXA, PENTA, PYRAM and TETRA, or PSHELL,
PCOMP, PCOMPG and PSOLID entry associated with those element types.
2. NAMEi are used in a Case Control SET definition defining setp to select the panels in the Case
Control command ERP.
3. Duplicate Element IDs are removed if they occur on the referencing SET3 entries prior to the ERP
calculation.
4. User does not need to specify the outer face(s) of 3D elements. The outer face(s) or exposed face(s)
of 3D elements will be determined automatically. Interior 3D element(s) which has no exposed
face(s) will not be included for ERP computation.
Main Index
1800 EULFOR
Body Force Loading on Euler Elements - SOL 700 only
EULFOR Body Force Loading on Euler Elements - SOL 700 only
Defines a body force loading (acceleration) on Euler elements per unit mass. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
EULFOR BID CID VALUE TID N1 N2 N3
Example:
EULFOR 100 5 13 1. 0. 0.
Describer Meaning
BID Unique body force number. (Integer > 0; Required)
CID ID of a coordinate system. (Integer > 0; Default = 0)
VALUE Scale factor for the vector. See Remark 1. (Real > 0.0)
TID TABLED1 ID describing the scale factor for the load as function of time. See Remark
1. (Integer)
N1, N2, N3 Components of a vector giving the load (acceleration) direction defined in coordinate
system CID. At lease one must be nonzero. See Remark 2. (Real; Default = 0.0)
Remarks:
1. Either VALUE or TID must be nonzero.
2. By default the components are zero, but at least one of them should be nonzero.
Main Index
EULFOR1 1801
Body force for Eulerian Regions - SOL700
EULFOR1 Body force for Eulerian Regions - SOL700
Alternative way to define an acceleration within a geometric region of the Euler model regions are defined
by geometric shapes which are defined by EULFREG entries.
Format:
EULFOR1 SID ESID
Example:
EULFOR1 300 1
Describer Meaning
SID Unique EULFOR1 number referenced from a PEULER1 entry .(Integer >0, required)
ESID Group of geometric region EULFREG ID. (Integer > 0; Required)
Remarks:
1. EULFOR1 and EULFREG are only available for the multi-material Euler solver.
2. The combination of Eulerian region and material ID determines where the acceleration field is
applied.
3. It is allowed to cover only part of the Euler domain with EULFOR1 definitions.
4. To increase the accuracy of the region definition parameter MICRO can be used.
Main Index
1802 EULFREG
Body force for Eulerian Regions - SOL700
EULFREG Body force for Eulerian Regions - SOL700
Defines the acceleration field for sets of Eulerian regions, The Eulerian regions are defined by geometric
shapes. For each coordinate direction a time-depended acceleration can be defined.
Format:
EULFREG ERID ESID TYPE1 VID1 MID1 ACCX ACCY ACCZ
LEVEL
Example:
EULFREG 300 1 BOX 400 100 100 200 300
0.0
Describer Meaning
ERID Unique ERID number. (Integer > 0; Required)
ESID ID of group of Euler regions referenced from the EULFOR1 entry. (Integer > 0; Required)
TYPEi The type of Eulerian region. (Character; Required)
SURF Region inside or outside a multifaceted surface.
SPHERE Region inside a sphere.
CYLINDER Region inside a cylinder.
BOX Region inside a box.
ELEM Region defined by element list.
VIDi Number of a geometric entity, a SET1 number, or number of a SURFINI entry. (Integer >
0; Required)
MIDi Number of a MATDEUL entry to which the acceleration field will be applied. (Integer > 0;
Required)
ACCi Unique table number that defines the variation of acceleration in time. ACCX, ACCY and
ACCZ respectively denote the acceleration in the x-, y- and z-direction. (Integer > 0; Re-
quired)
LEVELi Level indicator for this material and initial values. (Real; default=0.0)
Remarks:
1. EULFOR1 and EULFREG are only available for the multi-material Euler solver.
2. The combination of Eulerian region and material ID determines where the acceleration field is
applied.
3. It is allowed to cover only part of the Euler domain with EULFOR1 definitions.
Main Index
EULFREG 1803
Body force for Eulerian Regions - SOL700
4. All level indicators LEVELi must have different values. The level indicator can be negative.
5. To increase the accuracy of the region definition parameter MICRO can be used.
Main Index
1804 EXCLUDE
Ignore Bulk Data entries from primary to secondary Module
EXCLUDE Ignore Bulk Data entries from primary to secondary Module
Specifies Bulk Data entries in the primary Module to be ignored in the secondary (or copied) Module.
Format:
1 2 3 4 5 6 7 8 9 10
EXCLUDE ENTRY1 ENTRY2 ENTRY3 -etc.,
Example:
EXCLUDE SPC FORCE
Describer Meaning
ENTRYi Name of a Bulk Data entry to be ignored.
Remarks:
1. A secondary Module may have its own BEGIN MODULE section but it is not required as long as
the user is willing to accept all modeling data from the reference Module because, by default, all
entries in the reference Module will be copied to the secondary Module. However, if the user wishes
to exclude and/or replace some of the entries from the reference Module in the copy then he simply
specifies at least one instance of the entry to be ignored. For example, if the user wants to ignore all
FORCE entries from the reference Module then specify a single FORCE entry in the secondary
Module's Bulk Data section. Alternatively, the user may specify a list of Bulk Data entries to ignore
on the EXCLUDE Bulk Data entry in the secondary Module's Bulk Data section.
2. EXCLUDE must be specified in the secondary (or copied) Module's Bulk Data section.
3. GRID entries cannot be ignored or replaced and EXCLUDE,GRID will cause a fatal error.
4. See MDBULK for the definition of secondary (or copied) Modules.
Main Index
EXTRN 1805
Partitioned External Superelement Connection
EXTRN Partitioned External Superelement Connection
Defines a boundary connection for an external superelement.
Format:
1 2 3 4 5 6 7 8 9 10
EXTRN GID1 C1 GID2 C2 GID3 C3 GID4 C4
-etc.- GID6 “THRU” GID7 C6 -etc.-
Example:
EXTRN 1001 123 1120 123456 1201 123
Describer Meaning
GIDi Grid identification number to which the exterior superelement matrices will be
connected.
Ci Component numbers. (Integer 0, blank, or 1 for scalar points; Integers 1 through 6
with no embedded blanks for grids.)
Remarks:
1. EXTRN can only be specified in partitioned Bulk Data Sections and is ignored in the main Bulk Data
Section.
2. Connection grids must be specified in the partitioned Bulk Data Section following
BEGIN SUPER = SEID.
3. “THRU” may be specified only in fields 3, 5, or 7.
4. Pairs of blank fields may be entered to allow easier modification of the EXTRN entry.
5. The order of the GIDi and Ci pairs must be in the internal order of the grids set in the creation run.
But since Nastran no longer re-sequences grids then the pairs are specified in ascending GRID ID
order. However, if PARAM,OLDSEQ or the SEQGP entry is specified then the proper order may
not be ascending. To determine the internal grid order, add PARAM,USETPRT,0 and
PARAM,USETSTR1,A.
Main Index
FAILJC 1805
Johnson-Cook Failure Model - SOL 700 only
Entries F - L
FAILJC Johnson-Cook Failure Model - SOL 700 only
Defines the properties of the Johnson-Cook failure model. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FAILJC FID D1 D2 D3 D4 D5 ·0 TROOM
pl
TMELT CP MTH
Example:
FAILJC 1 .05 3.44 -2.12 0.002 0.16 1.0 297.0
1495 450 CONT
Describer Meaning
FID Unique failure model number. Referenced from MATDEUL. (Integer > 0; Required)
D1...D5 Parameters. See Remark 4. (Real; Default = 0.0)
·0
pl Reference plastic strain rate. (Real; Default = 1.0)
TROOM Room temperature. (Real; 0.0)
TMELT Melt temperature. (Real; 1.E+20)
CP Heat capacity. (Real; 1.E+20)
MTH Specifies how failure is applied. (Character; CONT)
CONT Continuous failure
DISC Discrete failure
NOFAIL Damage is not used for failure
Remarks:
1. This failure model is only available for Eulerian materials using the multi-material solver with
strength.
2. The use of coupling surfaces is not supported.
3. The variable D can be visualized by adding DAMAGE to the Output request for Euler elements.
4. Defines the properties of a failure model where failure is determined by a damage model. The
damage model is given by:
Main Index
1806 FAILJC
Johnson-Cook Failure Model - SOL 700 only
p
D = ----------
frac
-
time
·
frac * pl *
= D 1 + D 2 exp D 3 1 + D 4 In ------ 1 + D 5 T
· 0
pl
* m
= -------
* T – T room
T = ---------------------------------
T melt – T room
The summation is performed over all past time increments. The variable D measures the damage; T
is the temperature, is the mean stress, the effective stress and is the fracture strain. The fracture
· ·0
strain depends on a non-dimensional plastic strain rate pl pl . If D exceeds one it set equal to one.
The damage variable D is transported along with the Eulerian material.
There are two methods to determine when elements fail:
• Continuous failure: The yield stress is reduced by a factor (1-D). When D exceeds 1 the yield
stress equals zero and the element fails.
• Discrete failure: the element fails when D equals one.
This failure model applies to high-strain rate deformation of metals. It is less suitable for quasi-static
problems.
Main Index
FAILMPS 1807
Maximum Plastic Strain Failure Model - SOL 700 only
FAILMPS Maximum Plastic Strain Failure Model - SOL 700 only
Defines the properties of a failure model where failure occurs when the equivalent plastic strain exceeds the
specified value. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FAILMPS FID MPS
Example:
FAILMPS 1 .15
Describer Meaning
FID Unique failure model number referenced from MATDEUL. (Integer > 0; Required)
MPS Maximum plastic strain that causes failure. (Real; Required)
Main Index
1808 FAILUDS
User Defined Failure For Nonlinear Explicit Analysis - SOL 700 only
FAILUDS User Defined Failure For Nonlinear Explicit Analysis - SOL 700 only
User defined simple failure of Eulerian materials. Use in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FAILUDS FID GROUP UNAME
Example:
In FMS Section of the MSC Nastran input stream:
CONNECT SERVICE usrfail ' SCA.MDSolver.Obj.Uds.Dytran.Materials '
In Bulk Data:
1 2 3 4 5 6 7 8 9 10
FAILUDS 200 usrfail EXFAIL
Describer Meaning
FID Unique output number. (Integer > 0; Required)
GROUP The group name used for the FMS section CONNECT SERVICE statement.
(Character; no Default)
UNAME User subroutine name associated with the entry. (Character; default=EXFAIL)
Remarks:
1. Only can be used for SOL 700.
2. FID has to be referenced by a MATDEUL, MAT1 or MATORT entry.
3. UNAME can be:
Subroutine Name Function
EXFAIL Standard user defined failure
EXFAIL1 Alternative 1 user defined failure
EXFAIL2 Alternative 2 user defined failure
4. For option UNAME=EXFAIL2, for each material and for each Euler element a variable will be
created that monitors the degree of failure of the material. This variable is denoted by DAMAGE and
is between 0 and 1. The EXFAIL2 routine allows updating this damage variable due to the plastic
strain increment of the current cycle.
5. For option UNAME=EXFAIL2 there are three ways in which this damage variable can model failure.
These are:
Main Index
FAILUDS 1809
User Defined Failure For Nonlinear Explicit Analysis - SOL 700 only
• Continuous failure: The yield stress is reduced by a factor (1-D). When D exceeds 1.0, the yield
stress equals zero and the element fails.
• Discrete failure: the element fails when D equals one.
• No failure: positive damage values will not lead to failure. This is useful if the failure modeling is
done by an YLDUDS routine. Then the yield stress can be reduced depending on the magnitude
of the damage variable.
6. UNAME=EXFAIL2 is only supported by the multi-material Euler solver with strength.
7. UNAME=EXFAIL1 is only supported with MATORT.
8. For Lagrangian materials, UNAME=EXFAIL or EXFAIL1 are only available.
Main Index
1810 FBADLAY
Dynamic Load Time Delay for FRF Based Assembly (FBA)
FBADLAY Dynamic Load Time Delay for FRF Based Assembly (FBA)
Defines the time delay term in the equations of motion of the dynamic loading function for frequency
dependent loads in an FRF Based Assembly (FBA) process.
Format:
1 2 3 4 5 6 7 8 9 10
FBADLAY SID COMPID/ PNTID C DELAY
COMPNAME
Examples:
FBADLAY 15 BODY 10 3 0.5
FBADLAY 25 30 5 2 0.1
Describer Meaning
SID Identification number. See Remark 1. (Integer > 0)
COMPID Identification number of the FRF component whose FRFs have been generated in a
previous Nastran execution. (Integer > 0)
COMPNAME Name of the FRF component whose FRFs have been generated in a a previous Nastran
execution. (Up to 8 characters; no blank allowed)
PNTID Grid or scalar point identification number. See Remark 3. (Integer > 0)
C Component number. See Remark 3. (Integer 1 through 6 for grid point; blank or 0 for
scalar point)
DELAY Time delay term . See Remark 4. (Real)
Remarks:
1. SID is referenced by RLOAD1, RLOAD2 and ACSRCE entries.
2. This entry is ignored if the specified COMPID/COMPNAME is not part of the FBA process. A user
warning message is issued in this case.
3. The component C of the point PNTID specified in this entry must be among the excitation degrees
of freedom of the FBA process. If not, the program terminates the job with a user fatal message.
4. Refer to RLOAD1, RLOAD2 and ACSRCE entries for the formulas that define the time delay term
in frequency response analysis.
5. All FBADLAY entries specified in an FBA process are automatically converted internally by the
program to equivalent DELAY entries by replacing the grid/scalar point IDs referenced in these
entries by equivalent internal point IDs.
Main Index
FBALOAD 1811
Load Scale Factor Specification for FRF Based Assembly (FBA) Process
FBALOAD Load Scale Factor Specification for FRF Based Assembly (FBA) Process
Defines the scale factor for frequency dependent loads in an FRF Based Assembly (FBA) process.
Format:
1 2 3 4 5 6 7 8 9 10
FBALOAD SID COMPID/ PNTID C A
COMPNAME
Examples:
FBALOAD 10 WING 20 3 2.5
FBALOAD 20 30 25 1 1.5
Describer Meaning
SID Identification number. See Remark 1. (Integer > 0)
COMPID Identification number of the FRF component whose FRFs have been generated in
a previous Nastran execution. (Integer > 0)
COMPNAME Optional name of the FRF component whose FRFs have been generated in a
previous Nastran execution. (Up to 8 characters; no blank allowed).
PNTID Grid or scalar point identification number. See Remark 3. (Integer > 0)
C Component number. See Remark 3. (Integer 1 through 6 for grid point; blank or
0 for scalar point)
A Scale factor. See Remark 4. (Real)
Remarks:
1. SID is referenced by RLOAD1, RLOAD2 and ACSRCE entries.
2. This entry is ignored if the specified COMPID/COMPNAME is not part of the FBA process. A user
warning message is issued in this case.
3. The component C of the point PNTID specified in this entry must be among the excitation degrees
of freedom of the FBA process. If not, the program terminates the job with a user fatal message.
4. Refer to RLOAD1, RLOAD2 and ACSRCE entries for the formulas that define the scale factor A in
frequency response analysis.
5. All FBALOAD entries specified in an FBA process are automatically converted internally by the
program to equivalent DAREA entries by replacing the grid/scalar point IDs referenced in these
entries by equivalent internal point IDs.
Main Index
1812 FBAPHAS
Dynamic Load Phase Lead for FRF Based Assembly (FBA)
FBAPHAS Dynamic Load Phase Lead for FRF Based Assembly (FBA)
Defines the phase lead term in the equations of motion of the dynamic loading function for frequency
dependent loads in an FRF Based Assembly (FBA) process.
Format:
1 2 3 4 5 6 7 8 9 10
FBAPHAS SID COMPID/ PNTID C PHASE
COMPNAME
Examples:
FBAPHAS 25 FRAME 40 1 10.0
FBAPHAS 30 50 10 2 5.0
Describer Meaning
SID Identification number. See Remark 1. (Integer > 0)
COMPID Identification number of the FRF component whose FRFs have been generated in a
previous Nastran execution. (Integer > 0)
COMPNAME Name of the FRF component whose FRFs have been generated in a previous Nastran
execution. (Up to 8 characters; no blank allowed)
PNTIDi Grid or scalar point identification numbers. See Remark 3. (Integer > 0)
C Component number. See Remark 3. (Integers 1 through 6 for grid points; blank or 0 for
scalar points.)
PHASE Phase lead term . See Remark 4. (Real)
Remarks:
1. SID is referenced by RLOAD1, RLOAD2 and ACSRCE entries.
2. This entry is ignored if the specified COMPID/COMPNAME is not part of the FBA process. A user
warning message is issued in this case.
3. The component C of the point PNTID specified in this entry must be among the excitation degrees
of freedom of the FBA process. If not, the program terminates the job with a user fatal message.
4. Refer to RLOAD1, RLOAD2 and ACSRCE entries for the formulas that define the phase lead term
in frequency response analysis.
5. All FBAPHAS entries specified in an FBA process are automatically converted internally by the
program to equivalent DPHASE entries by replacing the grid/scalar point IDs referenced in these
entries by equivalent internal point IDs.
Main Index
FBODYLD 1813
Equilibrated Free-Body Applied Load Case Definition
FBODYLD Equilibrated Free-Body Applied Load Case Definition
Defines an equilibrated free-body applied load case.
Format:
1 2 3 4 5 6 7 8 9 10
FBODYLD NAMEL FBODYSB
LABEL
Example:
FBODYLD WINGLD WINGSB
LOAD ON THE RIGHT WING
Describer Meaning
NAMEL User defined name identifying the load case. (Character; Required)
FBODYSB Name of a FBODYSB Bulk Data entry that defines the subsystem for this load.
(Character; Required)
LABEL A string comprising no more than 64 characters (fields 2 through 9) that identifies and
labels the load case. (Character; optional)
Remarks:
1. NAMEL must be unique.
2. The Label is optional.
Main Index
1814 FBODYSB
Equilibrated Free-Body Subsystems Definition
FBODYSB Equilibrated Free-Body Subsystems Definition
Defines an equilibrated free-body subsystem.
Format:
1 2 3 4 5 6 7 8 9 10
FBODYSB NAMES GRIDSET ELEMSET XFLAG
LABEL
Example:
FBODYSB WING 1 1 ADM
RIGHT WING
Describer Meaning
NAMES User defined name identifying the submodel. (Character; Required)
GRIDSET Identification number of a SET1 entry that has a list of Grid Point Force grids to
include in defining the subsystem. (Integer > 0)
ELEMSET Identification number of a SET1 entry that has a list of elements to include in the
system (Integer > 0 or blank)
XFLAG Exclusion flag. Exclude the indicated Grid Point Force types.
Default Blank (no type excluded)
S SPC forces
M MPC forces
A, L, or P Applied loads
D DMIG’s (and any other type not described above)
Label An optional string of up to 64 characters (fields 2 through 9) that identifies the
subsystem.
Remarks:
1. Only those Grid Point Forces which have both an included grid point and element (or Grid Point
Force type) will be taken into account.
2. If ELEMSET is blank, no contributions are made from the set of elements attached to the grid.
3. Fictitious grids or elements do not produce error or warning messages.
4. The XFLAG data can be any combination of the letters S,M,A,L,P and D (e.g., MAD).
5. The continuation is optional.
Main Index
FFCONTR 1815
Closed Volume Intended for Fluid Filled Containers
FFCONTR Closed Volume Intended for Fluid Filled Containers
Defines the pressure within a closed volume. Intended for the use in (partially) filled containers, where
dynamic fluid effects are negligible, e.g. top loading and hot filling. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FFCONTR FFID SID FVOL PATM TEMPTAB DENSTAB TACTIVE
Example:
FFCONTR 1 2 1.50E-03 0.1E6 10 20
Describer Meaning
FFID Unique FFCONTR identification number. (Integer > 0; Required)
SID Number of a BSURF, BCBOX, BCPROP, BCMATL or BCSEG entry defining the
closed surface. (Integer > 0; Required)
FVOL Fluid volume in the container. (Real > 0.0; Required)
PATM Atmospheric pressure. Used for determination of the constant C for p V = C .
(Real > 0.0; Required)
TEMPTAB A reference to a TABLED1 ID that specifies how temperature of the container changes
in time. (Integer > 0; Blank)
DENSTAB A reference to a TABLED1 ID that specifies how density of the container changes with
temperature. (Integer > 0; Blank)
TACTIVE Time at which the pressure computation of the bottle is started. Until this time the
pressure inside the bottle equals the ambient pressure. The volume of the bottle at
TACTIVE will be used for the initial pressure computation of the gas in the bottle.
Remarks:
1. If TEMPTAB is not set, the gas above the fluid is assumed to be an ideal, iso-thermal gas:
p V = C , where C is a constant. If TEMPTAB is set, the temperature is applied to both the fluid
as well as the gas. Then the gas satisfies p V T = C , where T is the temperature of the fluid.
2. The fluid is assumed incompressible.
3. The pressure is based on the uniform pressure gasbag algorithm, where the pressure is uniform in the
volume, but variable in time.
4. Output for the fluid-filled container is available through a SURFOUT definition. The available
variables are: PRESSURE, VOLUME, TEMPTURE, VOLGAS, VOLFLUID, GAUGEPRES and
RHOFLUID.
5. The normals of the surface referenced by SID are reversed automatically if required.
Main Index
1816 FFCONTR
Closed Volume Intended for Fluid Filled Containers
6. Modeling guidelines are described in the “Getting Started” Section.
7. If DENSTAB is set then volume of the fluid changes according to
Fluid
Fluid T 0 V 0
V = ------------------------------
T
Fluid
Here T 0 and V 0 are initial values for temperature and fluid volume, is the fluid density and
T denotes the current temperature. If TEMPTAB is not set the DENSTAB entry will not be used.
8. At time=TACTIVE the gas is assumed to be in contact with the ambient pressure for the last time.
This means that at Time = TACTIVE the pressure in the bottle equals the ambient pressure. After
TACTIVE the bottle has been closed and there is no longer contact between ambient and gas inside
the bottle. Any change in volume of the bottle or temperature or fluid will result in change of pressure
of the gas inside the bottle.
Main Index
FLFACT 1817
Aerodynamic Physical Data
FLFACT Aerodynamic Physical Data
Used to specify density ratios, Mach numbers, reduced frequencies, and velocities for flutter analysis.
Format:
1 2 3 4 5 6 7 8 9 10
FLFACT SID F1 F2 F3 F4 F5 F6 F7
F8 F9 -etc.-
Example:
FLFACT 97 .3 .7 3.5
Alternate Format and Example:
FLFACT SID F1 “THRU” FNF NF FMID
FLFACT 201 .200 THRU .100 11 .133333
Describer Meaning
SID Set identification number. (Unique Integer > 0)
Fi Aerodynamic factor. (Real)
FNF Final aerodynamic factor. (Real)
NF Number of aerodynamic factors. (Integer > 0)
FMID Intermediate aerodynamic factors. See Remark 4. (Real)
Remarks:
1. Only the factors selected by a FLUTTER entry will be used.
2. Embedded blank fields are not allowed in the first format above.
3. The factors must be specified in the order in which they are to be used within the looping of flutter
analysis.
4. FMID must lie between F1 and FNF ; otherwise, FMID will be set to F1 + FNF 2 .
Then
F1 FNF – FMID NF – i + FNF FMID – F1 i – 1
Fi = -------------------------------------------------------------------------------------------------------------------------------------
FNF – FMID NF – i + FMID – F1 i – 1
where i = 1, 2, ..., NF
The use of FMID (middle factor selection) allows unequal spacing of the factors.
Main Index
1818 FLFACT
Aerodynamic Physical Data
2 F1 FNF
FMID = ------------------------------- gives equal values to increments of the reciprocal
F1 + FNF
of Fi .
5. If method = PK and this entry specifies velocities, then the velocities must be non-zero. Input of
negative values produces eigenvector results at a velocity equal to the positive value of the input. Input
of positive values provide eigenvalues results without eigenvectors.
Main Index
FLOW 1819
Flow Boundary Condition
FLOW Flow Boundary Condition
Defines the properties of a material for the boundaries of an Eulerian mesh. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FLOW LID BCID MESH DIR
XMIN XMAX YMIN YMAX ZMIN ZMAX
TYPE1 VALUE1 TYPE2 VALUE2 TYPE3 VALUE3 TYPE4 VALUE4
TYPE5 VALUE5
Example:
FLOW 120 122
XVEL 100.0
Describer Meaning
LID Number of a set of flow boundary conditions. (Integer > 0; Required)
BCID Number of a set of segments, specified by BCSEG entries, where the flow boundary is
located. See Remark 5. (Integer > 0)
MESH Denotes the ID of the Euler mesh to which the boundary condition has to be applied.
See Remark 6. (Integer > 0)
DIR Allowed values are: NEGX, POSX, NEGY, POSY, NEGZ and POSZ. See Remark 7.
(Character)
XMIN-ZMAX Defines a square by specifying the ranges of the x,y,z coordinates. For a square in for
example the x-plane it is required that either XMIN = XMAX or that XMAX is left
blank. See Remark 8. (Real)
TYPEi The flow boundary property being defined. (Character)
Material The MATDEUL ID number.
XVEL The material velocity in the x-direction.
YVEL The material velocity in the y-direction.
ZVEL The material velocity in the z-direction.
PRESSURE The pressure of the material at the boundary.
DENSITY The density of the material at inflow.
SIE The specific internal energy at inflow
Main Index
1820 FLOW
Flow Boundary Condition
Describer Meaning
FLOW The type of flow boundary required.
HYDSTAT A Hydrostatic pressure profile using a HYDSTAT entry.
VALUEi The value for the property defined. (Real; Integer or Character; Required)
For TYPEi set to FLOW, the value is a character entry being either IN, OUT, BOTH or
SYM defining that the flow boundary is defined as an inflow, outflow, possibly an in-
or outflow or symmetry boundary. The default is BOTH.
VALUEi is required data only if one or more of the TYPEi entries are defined. The
TYPEi entries are not required. Thus, a flow boundary by default allows for in- or
outflow of the material adjacent to the boundary.
For TYPE = HYDSTAT, the value is an integer entry denoting the HYDSTAT entry to
be used.
Remarks:
1. LID must be referenced by a TLOAD1 entry.
2. Any material properties not specifically defined have the same value as the element with the flow
boundary condition.
3. TLOAD entries referencing FLOW entries must have the TID field blank or zero.
4. In the case of material flow into a multi-material Euler mesh, the density and specific energy have to
be set. On the other hand when material flows out of a multi-material Euler mesh it is assumed that
each of the materials present in the outflow Euler element contributes to the out flow of mass. The
materials are transported in proportion to their relative volume fractions.
5. BCID is optional. If used, all other inputs are ignored. If not used, the flow boundary can be defined
by either using DIR or by using XMIN, XMAX, YMIN, etc.
6. The MESH-ID is only used when multiple Euler domains have been defined and when BCID is
blank. If multiple Euler domains have been defined but if the MESH-ID is blank all Euler domains
will be considered in assigning the boundary condition.
7. DIR is optional. It will only be used when BCID is blank. When DIR is used XMIN, XMAX, YMIN
etc. are ignored.
8. XMIN, XMAX, YMIN, etc. are only used when both BCID and DIR are blank. If neither the MIN
nor MAX value has been set the default value is respectively -1E+20 and 1E+20 for the MIN and
MAX value. If the MIN value has been set the default value of the MAX value is the Min value.
9. Prescribing both pressure and velocity may lead to the instabilities.
10. For TYPE = HYDSTAT, the pressure is set using HYDSTAT, the velocity equals the element
velocity. In case of inflow the density follows from the hydrostatic pressure by using the equation of
state.
Main Index
FLOWC 1821
Cyclic Flow Boundary Condition
FLOWC Cyclic Flow Boundary Condition
Defines the properties of a material for the boundaries of a Eulerian mesh.
Inflow values can be taken from another boundary condition. This allows cyclic or periodic boundary
conditions. Likewise, the outflow of material goes into the other boundary condition.
FLOWC entries have to be defined in pairs. The FID on one entry has to be equal to FID2 of the other
entry. For example
FLOWC,10,30,20
FLOWC,20,40,10
For FLOWC boundaries, mass flow summaries can be created as time history. Used in SOL700 only
Format:
1 2 3 4 5 6 7 8 9 10
FLOWC FID BCID TYPE MESH DIR FID2 +
+ XMIN XMAX YMIN YMAX ZMIN ZMAX +
+ METHOD TID
Example:
FLOWC 1 122 2
+
+ 2 1
Field Contents
FID Unique number of a FLOWC entry. (Integer > 0; Required)
BCID Number of a set of segments specified by the BCSEG entries where the flow boundary
is located. See Remark 3. (Integer > 0)
Main Index
1822 FLOWC
Cyclic Flow Boundary Condition
Field Contents
TYPE Flow boundary types. See Remarks 2.and 3. (Character; Required)
IN: Only inflow is allowed. The inflow velocity and pressure can be optionally specified.
If not given, the values in the adjacent Euler element will be used. The same holds for
the density and sie.
OUT: Only outflow is allowed. The inflow velocity and pressure can be optionally
specified. If not given, the values in the adjacent Euler element will be used. The outflow
boundary will always use material mixture as present in the adjacent Euler element.
BOTH: Material is allowed to flow in or out. In or outflow is based on the direction of
the velocity in the adjacent Euler element. Only pressure can be optionally defined. If
not given the pressure in the adjacent Euler element will be taken.
MESH Denotes the ID of the Euler mesh to which the boundary condition has to be applied.
See Remark 4. (Integer > 0)
DIR Allowed values are: NEGX, POSX, NEGY, POSY, NEGZ and POSZ. See Remark 5.
(Character; no default)
FID2 Referenced FLOWC id from which inflow and outflow values will be taken from.
(Integer > 0; Required)
XMIN-ZMAX Defines a square by specifying the ranges of the x,y,z coordinates. For a square in for
example the x-plane it is required that either XMIN = XMAX or that XMAX is left
blank. See Remark 6. (Real))
METHOD Method describing how material properties and pressure are mapped going from one
boundary to the other. (Integer > 0; Default=1)
1. Map both velocity, material flow properties, and pressure loads one-to-one.
2. Map velocity, material flow one-to-one. Pressure is given by element pressures.
3. Inflow is taken as the average of outflow properties. This applies to both velocity
and material properties. Pressure is given by element pressures.
TID TABLED1 ID that specifies a time dependent scale factor by which the amount of
inflow is multiplied. This will not conserve total mass. (Integer > 0. Default = not used).
Remarks:
1. LID must be referenced by a TLOAD1 entry.
2. TLOAD entries referencing FLOW entries must have the TID field blank or zero.
3. BCID is optional. If used, all other inputs are ignored. If not used, the flow boundary can be defined
by either using DIR or by using XMIN, XMAX, YMIN, etc.
4. The MESH-ID is only used when multiple Euler domains have been defined and when BCID is
blank. If multiple Euler domains have been defined but if the MESH-ID is blank all Euler domains
will be considered in assigning the boundary condition.
Main Index
FLOWC 1823
Cyclic Flow Boundary Condition
5. DIR is optional. It will only be used when BCID is blank. When DIR is used XMIN, XMAX, YMIN
etc. are ignored.
6. XMIN, XMAX, YMIN, etc. are only used when both BCID and DIR are blank. If neither the MIN
nor MAX value has been set the default value is respectively -1E+20 and 1E+20 for the MIN and
MAX value. If the MIN value has been set the default value of the MAX value is the Min value.
7. FLOWC can be used to specify flow boundaries for CHEXA's and also for Euler element created by
the MESH,BOX option.
8. FLOWC is only supported by the multi-material Euler solver.
9. To enable using the outflow values of FID2 as the inflow values for FID, the boundary faces of FID
and FID2 are mapped onto each other. For this mapping, only translations and rotations around
coordinate axes are permitted.
10. Consider a cubic Euler mesh and that material flows from the left to the right. At the right side, the
boundary condition is imposed
FLOWC,4,30,,5
and at the left side
FLOWC,5,40,,4
These definitions cause all material that flows out of the right side boundary into the left side
boundary. Moreover, the Euler element pressures on the right side are put on the Euler elements of
the left boundary condition.
In practice, it may be useful to skip the coupling between the two boundaries with regard to pressure.
This can be done by setting METHOD equal to 2.
With these definitions, material from boundary 4 still flows into boundary 5 but pressure boundaries
are transmitting.
11. TID is useful if several objects have identical outflow that is used as inflow by another object. Then
only one object has to be modeled. To account for the other objects when defining inflow, the scale
factor can be used. It can also be used to turn off in and outflow. When TID is set, either
METHOD=2 or METHOD=3 are recommended and METHOD=1 should not be used.
12. It is allowed that the definition of the FLOWC entry overlaps with FLOW definitions. In that case,
the FLOWC definition overrules the other ones
Main Index
1824 FLOWDEF
Default Flow Boundary
FLOWDEF Default Flow Boundary
Definition of default Eulerian flow boundary condition. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FLOWDEF FID TYPEM
TYPE1 VALUE1 TYPE2 -etc.-
Example:
FLOWDEF 25 HYDRO
DENSITY 1000
Describer Meaning
FID Unique FLOWDEF number. (Integer > 0; Required
TYPEM HYDRO, STRENGTH, MMHYDRO, or MMSTREN. (Character, HYDRO)
TYPEi The flow boundary property being defined. (Character)
Material The MATDEUL ID number.
XVEL The material velocity in the x-direction.
YVEL The material velocity in the y-direction.
ZVEL The material velocity in the z-direction.
PRESSURE The pressure of the material at the boundary.
DENSITY The density of the material at inflow.
SIE The specific internal energy at inflow
FLOW The type of flow boundary required.
HYDSTAT A Hydrostatic pressure profile using a HYDSTAT entry.
VALUEi The value for the property defined. (Real; Integer or Character; Required)
For TYPEi set to flow the value is a character entry being either IN, OUT, or BOTH,
defining that the flow boundary is defined as an inflow, outflow, or possibly an in- or
outflow boundary. The default is BOTH.
VALUEi is required data only if one or more of the TYPEi entries are defined. The
TYPEi entries are not required. Thus, a flow boundary by default allows for in- or
outflow of the material adjacent to the boundary.
For TYPE = HYDSTAT, the value is an integer entry denoting the HYDSTAT entry to
be used.
Main Index
FLOWDEF 1825
Default Flow Boundary
Remark:
1. If this entry is not specified, a default wall boundary condition is applied to all Eulerian free faces.
2. For TYPE = HYDSTAT, the pressure is set using HYDSTAT, the velocity equals the element
velocity. In case of inflow the density follows from the hydrostatic pressure by using the equation of
state.
Main Index
1826 FLOWT
Time Dependent Flow Boundary
FLOWT Time Dependent Flow Boundary
Defines the material properties for the in- or outflow of material trough the boundary of an Euler mesh.
Inflow velocity and material properties can be chosen time dependent. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FLOWT FID BCID TYPE MESH DIR
XMIN XMAX YMIN YMAX ZMIN ZMAX
VELTYPE VELOCITY PRESTYP PRES
MID DENSTYP DENSITY SIETYPE SIE
Example:
FLOWT 2 122 IN
TABLE 101 TABLE 102
91 TABLE 104 TABLE 107
Describer Meaning
FID Unique number of a FLOWT entry. (Integer > 0; Required)
BCID Number of a set of segments specified by the BCSEG entries where the flow boundary
is located. See Remark 3. (Integer > 0)
TYPE IN Inflow boundary. See Remarks 2.and 3. (Character; Required)
Only inflow is allowed. The inflow velocity and pressure can be
optionally specified. If not given, the values in the adjacent Euler
element will be used. The same holds for the density and sie.
OUT Only outflow is allowed. The inflow velocity and pressure can be
optionally specified. If not given, the values in the adjacent Euler
element will be used. The outflow boundary will always use material
mixture as present in the adjacent Euler element.
BOTH Material is allowed to flow in or out. In or outflow is based on the
direction of the velocity in the adjacent Euler element. Only pressure
can be optionally defined. If not given the pressure in the adjacent
Euler element will be taken.
MESH Denotes the ID of the Euler mesh to which the boundary condition has to be applied.
See Remark 4. (Integer > 0)
DIR Allowed values are: NEGX, POSX, NEGY, POSY, NEGZ and POSZ. See Remark 5.
(Character)
Main Index
FLOWT 1827
Time Dependent Flow Boundary
Describer Meaning
XMIN-ZMAX Defines a square by specifying the ranges of the x,y,z coordinates. For a square in for
example the x-plane it is required that either XMIN = XMAX or that XMAX is left
blank. See Remark 6. (Real)
VELTYPE Type of velocity definition. (Character, Element)
ELEMENT Value of Euler Element
CONSTANT Value is constant in time
TABLE Value varies in time
VELOCITY Value of inflow or outflow velocity. If VELTYPE = TABLE it refers to a TABLED1. The
velocity direction is normal to the coupling surface or subsurface. A positive velocity
corresponds with inflow. See Remark 6. (Integer or Real)
PRESTYP Type of pressure definition (Character, Element)
ELEMENT Value of Euler element
CONSTANT Value is constant in time
TABLE Value varies in time
PRES Value of inflow or outflow pressure. If PRESTYPE = TABLE it refers to a TABLED1
ID. (Integer or Real)
MID MATDEUL ID of inflowing material. Input is not allowed for TYPE = OUT.
When MID is specified, it is required to also define density and sie for the inflowing
material. (Integer)
DESTYP Type of density definition. (Character, Default is required when MID is given.)
ELEMENT Value of Euler element
CONSTANT Value is constant in time
TABLE Value varies in time
DENSITY Value of density. If DENSTYP = TABLE it refers to a TABLED1 ID. (Character;
Default is required when MID is given.)
SIETYPE Type of density definition. (Character; Default is required when MID is given.)
ELEMENT Value of Euler element
CONSTANT Value is constant in time
TABLE Value varies in time.
SIE Value of specific internal energy. If SIETYPE = TABLE it refers to a TABLED1 ID.
(Integer or Real; Default is required when MID is given.)
Remarks:
1. LID must be referenced by a TLOAD1 entry.
2. TLOAD entries referencing FLOW entries must have the TID field blank or zero.
Main Index
1828 FLOWT
Time Dependent Flow Boundary
3. BCID is optional. If used, all other inputs are ignored. If not used, the flow boundary can be defined
by either using DIR or by using XMIN, XMAX, YMIN, etc.
4. The MESH-ID is only used when multiple Euler domains have been defined and when BCID is
blank. If multiple Euler domains have been defined but if the MESH-ID is blank all Euler domains
will be considered in assigning the boundary condition.
5. DIR is optional. It will only be used when BCID is blank. When DIR is used XMIN, XMAX, YMIN
etc. are ignored.
6. XMIN, XMAX, YMIN, etc. are only used when both BCID and DIR are blank. If neither the MIN
nor MAX value has been set the default value is respectively -1E+20 and 1E+20 for the MIN and
MAX value. If the MIN value has been set the default value of the MAX value is the Min value.
7. Any material properties not specifically defined have the same value as the element that with the
boundary conditions.
8. In the case of material flow into a multi-material Euler mesh, the material number, the density and
specific energy have to be set. On the other hand when material flows out of a multi-material Euler
mesh it is assumed that each of the materials present in the outflow Euler element contributes to the
out flow of mass. The materials are transported in proportion to their relative volume fractions
9. The boundary condition initiates/determines a wave in compressible material like gas and water. This
can be either an outgoing or an ingoing wave. For stability it is important that the waves created are
compatible with the flow type near the boundary. Relevant flow types are subsonic inflow, subsonic
outflow, supersonic inflow and supersonic outflow. For example for subsonic inflow prescribing both
pressure and velocity would initiate outgoing waves. Outgoing waves for an inflow boundary
condition is known to be instable. However, for supersonic inflow one can specify both pressure and
velocities there are no outgoing waves at a supersonic inflow boundary.
Main Index
FLOWUDS 1829
User Defined Flow Boundary.
FLOWUDS User Defined Flow Boundary.
Defines a flow boundary on an Eulerian mesh specified by a user subroutine. Use in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FLOWUDS LID GROUP UNAME BCID MESH DIR
+ XMIN XMAX YMIN YMAX ZMIN ZMAX
Example:
In FMS Section of the MSC Nastran input stream:
CONNECT SERVICE myflow ' SCA.MDSolver.Obj.Uds.Dytran.Flow '
In Bulk Data:
1 2 3 4 5 6 7 8 9 10
FLOWUDS 12 MYFLOW EXFLOW 300
Describer Meaning
LID Unique output number. (Integer > 0; Required)
GROUP The group name used for the FMS section CONNECT SERVICE statement.
(Character; no Default)
UNAME User subroutine name associated with the entry. (Character; default=EXFLOW)
BCID Number of a set of segments, specified by BCSEG entries, where the flow boundary is
located. See Remark 6. (Integer > 0)
MESH Denotes the ID of the Euler mesh to which the boundary condition has to be applied.
See Remark 7. (Integer > 0)
DIR Allowed values are: NEGX, POSX, NEGY, POSY, NEGZ and POSZ. See Remark 8.
(Character)
XMIN-ZMAX Defines a square by specifying the ranges of the x,y,z coordinates. For a square in for
example the x-plane it is required that either XMIN = XMAX or that XMAX is left
blank. See Remark 9. (Real)
Remarks:
1. Only can be used for SOL 700.
2. UNAME can be:
Subroutine Name Function
EXFLOW Standard user defined flow boundary on the Euler mesh
Main Index
1830 FLOWUDS
User Defined Flow Boundary.
3. For multi material models EXFLOW allows for the definition of any material to flow into the
Eulerian mesh. The outflow can only be of materials present in the mesh.
4. TLOAD1 entries referencing FLOWUDS entries must have the TID field blank or zero.
5. BCID is optional. If used, all other inputs are ignored. If not used, the flow boundary can be defined
by either using DIR or by using XMIN, XMAX, YMIN, etc.
6. The MESH-ID is only used when multiple Euler domains have been defined and when BCID is
blank. If multiple Euler domains have been defined but if the MESH-ID is blank all Euler domains
will be considered in assigning the boundary condition.
7. DIR is optional. It will only be used when BCID is blank. When DIR is used XMIN, XMAX, YMIN
etc. are ignored.
8. XMIN, XMAX, YMIN, etc. are only used when both BCID and DIR are blank. If neither the MIN
nor MAX value has been set the default value is respectively -1E+20 and 1E+20 for the MIN and
MAX value. If the MIN value has been set the default value of the MAX value is the MIN value.
Main Index
FLSYM 1831
Axisymmetric Symmetry Control
FLSYM Axisymmetric Symmetry Control
Defines the relationship between the axisymmetric fluid and a structural boundary having symmetric
constraints. The purpose is to allow fluid boundary matrices to conform to structural symmetry definitions.
Format:
1 2 3 4 5 6 7 8 9 10
FLSYM M S1 S2
Example:
FLSYM 12 S A
Describer Meaning
M Number of symmetric sections of structural boundary around the circumference of the
fluid being modeled by the set of structural elements. (Even Integers > 2)
S1, S2 Description of boundary constraints used on the structure at the first and second planes
of symmetry. (Character: “S” means symmetric, “A” means antisymmetric.)
Remarks:
1. This entry is allowed only if an AXIF entry is also present.
2. Only one FLSYM entry is allowed.
3. This entry is not required if there are no planes of symmetry.
4. First plane of symmetry is assumed to be at = 0 . Second plane of symmetry is assumed to be at
= 360 M .
5. Symmetric and antisymmetric constraints for the structure must, in addition, be provided by the
user.
6. The solution is performed for those harmonic indices listed on the AXIF entry that are compatible
with the symmetry conditions.
7. For example, if FLSYM is used to model a quarter section of structure at the boundary, M = 4. If the
boundary constraints are “SS”, the compatible cosine harmonics are 0, 2, 4, ..., etc. If “SA” is used,
the compatible cosine harmonics are 1, 3, 5, ..., etc.
Main Index
1832 FLUTTER
Aerodynamic Flutter Data
FLUTTER Aerodynamic Flutter Data
Defines data needed to perform flutter analysis.
Format:
1 2 3 4 5 6 7 8 9 10
FLUTTER SID METHOD DENS MACH RFREQ IMETH NVALUE/ EPS
OMAX
Example:
FLUTTER 19 K 119 219 319 S 5 1.-4
Describer Meaning
SID Set identification number. (Integer > 0)
METHOD Flutter analysis method. (Character: “K” for K method, “PK” for PK method, “PKNL”
for PK method with no looping, “PKS” for PK sweep method, “PKNLS” for PK sweep
method with no looping, “KE” for the K method restricted for efficiency.) See Remark
9.
DENS Identification number of an FLFACT entry specifying density ratios to be used in
flutter analysis. (Integer > 0)
MACH Identification number of an FLFACT entry specifying Mach numbers m to be used
in flutter analysis. (Integer > 0)
RFREQ (or Identification number of an FLFACT entry specifying reduced frequencies k to be
VEL) used in flutter analysis; for the “PKx” methods, the velocities FLFACT entry is specified
in this field. (Integer > 0)
IMETH Choice of interpolation method for aerodynamic matrix interpolation. See Remark 6.
(Character: “L” = linear, “S” = surface; “TCUB” = termwise cubic; Default = “L”.)
NVALUE Number of eigenvalues beginning with the first eigenvalue for output and plots.
(Integer > 0; Default is the number of modal degrees-of-freedom (uh).)
OMAX For the PKS and PKNLS methods, OMAX specifies the maximum frequency, in Hz.,
to be used in he flutter sweep. (Real > 0.0; Default = maximum normal mode
eigenfrequency)
EPS Convergence parameter for k. Used in the PK and PKNL methods only. See Remark 4.
–3
(Real > 0.0; Default = 10 .) See Remark 9. for the meaning of EPS when the PKS or
PKNLS methods are being used.
Remarks:
1. The FLUTTER entry must be selected with the Case Control command FMETHOD = SID.
Main Index
FLUTTER 1833
Aerodynamic Flutter Data
2. The density is given by DENS RHOREF , where RHOREF is the reference value specified on the
AERO entry and DENS is the density ratio specified on the FLFACT entry.
3. The reduced frequency is given by k = REFC 2 V , where REFC is given on the AERO
entry, is the circular frequency, and V is the velocity. If k = 0.0 , as specified on the FLFACT
entry, then only the K method may be specified and the Inverse Power method of eigenvalue
extraction (INV on the EIGC entry) must be used. Aeroelastic divergence analysis is more
appropriately performed using one of the “PKx” methods.
4. For the PK and PKNL methods, an eigenvalue is accepted when:
k – k estimate EPS for k estimate 1.0
k – k estimate EPS k estimate
for k estimate 1.0
5. When one of the “PKx” methods is selected, physical displacements will only be generated for the
velocities on the FLFACT that are specified as negative values of the requested velocity. Also,
structural damping as specified on the GE field of MATi entries is ignored.
6. If IMETH = “L”, a linear interpolation is performed on reduced frequencies at the Mach numbers
specified on the FLFACT entry using the MKAEROi entry Mach number that is closest to the
FLFACT entry Mach number. For IMETH = “S”, a surface interpolation is performed across Mach
numbers and reduced frequencies. For IMETH = “TCUB” a termwise cubic interpolation on
reduced frequency is used. IMETH = “S” is only available for the “K” and “KE” flutter methods.
IMETH = “TCUB” is only available for the “PKx” methods. For the “PKx” methods, IMETH = “S”
or “L” or blank provides linear interpolation while “TCUB” provides a termwise cubic interpolation.
7. For the “K”, “KE”, “PK”, and “PKS” methods, all combinations of the FLFACT entry are analyzed.
For the “PKNL” and “PKNLS” methods, only ordered pairs are analyzed; i.e.,
1 M 1 V 1 2 M 2 V 2 n M n V n . For the PKNL and PKNLS methods, equal
number of densities, Mach numbers and velocities must be specified.
8. “K” and “KE” methods are not supported for design sensitivity and optimization.
9. The PKS and PKNLS methods determine flutter eigenvalues by performing a sweep of equally spaced
reduced frequencies ranging from k est = 0.0 through k est = REFC OMAX/Velocity .
The number of intervals is calculated using NINT = INT(1.0/EPS).
10.
• The PK method uses only real matrix terms for computing the flutter solution. This means any
imaginary terms in any of the matrices, M, B, or K are ignored with the PK method and the
imaginary part of the aerodynamic matrix is added as a real matrix to the viscous damping matrix
B.
• For the KE method, the B matrix is ignored while complex stiffness forms of structural damping
are supported. Modal viscous damping (TABDMP1 input) will be included when the KDAMP
parameter is set to -1.
• The K method supports all forms of damping.
Main Index
1834 FLUTTER
Aerodynamic Flutter Data
11. METHOD=K requires a CMETHOD in Case Control pointing to an EIGC Bulk Data entry. It is
recommended that the number of roots requested on the EIGC entry be twice the number of normal
modes used in the modal flutter analysis.
Main Index
FORCE 1835
Static Force
FORCE Static Force
Defines a static concentrated force at a grid point by specifying a vector.
Format:
1 2 3 4 5 6 7 8 9 10
FORCE SID G CID F N1 N2 N3
Example:
FORCE 2 5 6 2.9 0.0 1.0 0.0
Describer Meaning
SID Load set identification number. (Integer > 0)
G Grid point identification number. (Integer > 0)
CID Coordinate system identification number. (Integer > 0; Default = 0)
F Scale factor. (Real)
Ni Components of a vector measured in coordinate system defined by CID. (Real; at least
one Ni 0.0. unless F is zero)
Remarks:
1. The static force applied to grid point G is given by
f = FN
where N is the vector defined in fields 6, 7 and 8. The magnitude of f is equal to F times the
magnitude of N .
2. In the static solution sequences, SID must be selected by the LOAD Case Control command.
In the dynamic solution sequences, if there is a LOADSET Case Control command, then SID must
be referenced in the LID field of a selected LSEQ entry. If there is no LOADSET Case Control
command, then SID must be referenced in the EXCITEID field of an RLOADi or TLOADi entry.
3. A CID of zero or blank (the default) references the basic coordinate system.
4. For scalar points see SLOAD.
5. For TYPE=12 or TYPE=13 on the TLOAD1, G is the ID of a rigid body: the MID of a rigid material
MATRIG or the EID of a RBE2. The MID of a rigid material and the EID of RBE2 must be
different when both of a RBE2 and a rigid material are used with these TYPEs. SOL 700 only.
6. For axisymmetric elements, the point loads to be entered on the card should be obtained by
integrating over 1 radian of the circumference.
Main Index
1836 FORCE1
Follower Force, Alternate Form 1
FORCE1 Follower Force, Alternate Form 1
Defines a concentrated force at a grid point by specification of a magnitude and two grid points that
determine the direction.
Format:
1 2 3 4 5 6 7 8 9 10
FORCE1 SID G F G1 G2
Example:
FORCE1 6 13 -2.93 16 13
Describer Meaning
SID Load set identification number. (Integer > 0)
G Grid point identification number. (Integer > 0)
F Magnitude of the force. (Real)
G1, G2 Grid point identification numbers. (Integer > 0; G1 and G2 may not be coincident.)
Remarks:
1. The force applied to grid point G is given by
f = Fn
where n is a unit vector parallel to a vector from G1 to G2.
2. In the static solution sequences, SID must be selected by the LOAD Case Control command.
In the dynamic solution sequences, if there is a LOADSET Case Control command, then SID must
be referenced in the LID field of a selected LSEQ entry. If there is no LOADSET Case Control
command, then SID must be referenced in the EXCITEID field of an RLOADi or TLOADi entry.
3. The follower force effects due to loads from this entry are included in the stiffness in all linear solution
sequences that calculate a differential stiffness. The solution sequences are SOLs 103, 105, 107 to
112, 115 and 116 (see also the parameter FOLLOWK). In addition, follower force effects are included
in the force balance in the nonlinear static and nonlinear transient dynamic solution sequences, SOLs
106, 129, 153, 159, 400, if geometric nonlinear effects are turned on with PARAM,LGDISP,1. The
follower force stiffness is included in the nonlinear static solution sequences (SOLs 106, 153 and 400)
but not in the nonlinear transient dynamic solution sequences (SOLs 129 and 159).
4. For axisymmetric elements, the point loads to be entered on the card should be obtained by
integrating over 1 radian of the circumference.
Main Index
FORCE2 1837
Follower Force, Alternate Form 2
FORCE2 Follower Force, Alternate Form 2
Defines a concentrated force at a grid point by specification of a magnitude and four grid points that
determine the direction.
Format:
1 2 3 4 5 6 7 8 9 10
FORCE2 SID G F G1 G2 G3 G4
Example:
FORCE2 6 13 -2.93 16 13 17 13
Describer Meaning
SID Load set identification number. (Integer > 0)
G Grid point identification number. (Integer > 0)
F Magnitude of the force. (Real)
Gi Grid point identification numbers. (Integer > 0; G1 and G2 may not be coincident; G3
and G4 cannot be coincident.)
Remarks:
1. The direction of the force is parallel to the cross product of vectors from G1 to G2 and G3 to G4.
2. In the static solution sequences, SID must be selected by the LOAD Case Control command.
In the dynamic solution sequences, if there is a LOADSET Case Control command, then SID must
be referenced in the LID field of a selected LSEQ entry. If there is no LOADSET Case Control
command, then SID must be referenced in the EXCITEID field of an RLOADi or TLOADi entry.
3. The follower force effects due to loads from this entry are included in the stiffness in all linear solution
sequences that calculate a differential stiffness. The solution sequences are SOLs 103, 105, 107 to
112, 115 and 116 (see also the parameter FOLLOWK). In addition, follower force effects are included
in the force balance in the nonlinear static and nonlinear transient dynamic solution sequences, SOLs
106, 129, 153, 159, and 400 if geometric nonlinear effects are turned on with PARAM,LGDISP,1.
The follower force stiffness is included in the nonlinear static solution sequences (SOLs 106, 153 and
400) but not in the nonlinear transient dynamic solution sequences (SOLs 129 and 159).
4. For axisymmetric elements, the point loads to be entered on the card should be obtained by
integrating over 1 radian of the circumference.
Main Index
1838 FORCEAX
Conical Shell Static Force
FORCEAX Conical Shell Static Force
Defines a static concentrated force on a conical shell ring.
Format:
1 2 3 4 5 6 7 8 9 10
FORCEAX SID RID HID S FR FP FZ
Example:
FORCEAX 1 2 3 2.0 0.1 0.2 0.3
Describer Meaning
SID Load set identification number. (Integer > 0)
RID RINGAX entry identification number. (Integer > 0)
HID Harmonic identification number or a sequence of harmonics. See Remark 5.
(Integer > 0)
S Scale factor for the force. (Real)
FR, FP, FZ Force components in r z directions. (Real)
Remarks:
1. FORCEAX is allowed only if an AXIC entry is also present.
2. Axisymmetric shell loads must be selected with the Case Control command LOAD = SID.
3. A separate entry is needed for the definition of the force associated with each harmonic.
4. See Conical Shell Element (RINGAX) in the MSC Nastran Reference Guide for further discussion.
5. If a sequence of harmonics is to be placed in HID, the form is as follows: “Sn1Tn2” where n1 is the
start of the sequence and n2 is the end of the sequence (e.g., for harmonics 0 through 10, the field
would contain “S0T10”).
Main Index
FORCUDS 1839
User-defined Enforced Motion at Grid Points
FORCUDS User-defined Enforced Motion at Grid Points
Defines enforced motion at grid points specified by a user subroutine. Used in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
FORCUDS LID GROUP UNAME
+ G1 G2 THRU G3
Example:
In FMS Section of the MSC Nastran input stream:
CONNECT SERVICE extvel ' SCA.MDSolver.Obj.Uds.Dytran.Loads '
In Bulk Data:
FORCUD 1 EXTVEL
+ 1 2 3 5
Describer Meaning
LID Number of a set of loads.(Integer>0;required)
GROUP The group name used for the FMS section CONNECT SERVICE statement.
(Character; required)
UNAME User subroutine name associated with the entry. (Character; default=EXTVEL)
Gi Numbers of the grid points that are constrained. If the word THRU appears between
two numbers, all the numbers in the range are included in the list. BY indicates the
increment to be used within this range. (Integer or character; required.)
Remarks:
1. LID must be referenced by a TLOAD1 entry.
2. FORCUDS can only be used to specify enforced velocities for grid points. The TYPE field on the
TLOAD1 entry must be set to two. The TID on the TLOAD1 entry must be set to zero or blank
(no time variation).
3. The GROUP name must be unique from all other GROUP names if more than one FORCUDS is
used. Therefore each FORCUDS must have its own group name in a FMS section CONNECT
SERVICE statement.
4. The constraint name is passed to the subroutine and can be used to identify the constraint.
5. A THRU specification, including the start and finish points in the range, must be on one line.
Main Index
1840 FORCUDS
User-defined Enforced Motion at Grid Points
6. If the THRU specification is used, all the points in the sequence do not have to exist. Those that do
not exist are ignored. The first point in the THRU specification must be a valid grid point. BY can
be used to exclude grid points.
7. None of the fields in the list of grid points can be blank or zero, since this designation marks the end
of the list.
8. Any number of continuation lines can be used to define the list of grid points.
9. UNAME can be:
Subroutine Name Function
EXTVEL user defined velocities on grid points
Main Index
FREEPT 1841
Fluid Free Surface Point
FREEPT Fluid Free Surface Point
Defines the location of points on the surface of a fluid for recovery of surface displacements in a gravity field.
Format:
1 2 3 4 5 6 7 8 9 10
FREEPT IDF IDP1 PHI1 IDP2 PHI2 IDP3 PHI3
Example:
FREEPT 3 301 22.5 302 90.0 303 370.0
Describer Meaning
IDF RINGFL entry identification number. (Integer > 0)
IDPi Free surface point identification number. (Integer > 0)
PHIi Azimuthal position on fluid point (RINGFL entry) in the fluid coordinate system.
(Real)
Remarks:
1. FREEPT is allowed only if an AXIF entry is also present.
2. All free surface point identification numbers must be unique with respect to other scalar, structural,
and fluid points.
3. The free surface points are used for the identification of output data only.
4. Three points may be defined on a single entry.
5. The referenced fluid point (IDF) must be included in a free surface list (FSLIST entry).
6. Output requests for velocity and acceleration can be made at these points.
Main Index
1842 FREQ
Frequency List
FREQ Frequency List
Defines a set of frequencies to be used in the solution of frequency response problems.
Format:
1 2 3 4 5 6 7 8 9 10
FREQ SID F1 F2 F3 F4 F5 F6 F7
F8 F9 F10 -etc.-
Example:
FREQ 3 2.98 3.05 17.9 21.3 25.6 28.8 31.2
29.2 22.4 19.3
Describer Meaning
SID Set identification number. (Integer > 0)
Fi Frequency value in units of cycles per unit time. (Real > 0.0)
Remarks:
1. Frequency sets must be selected with the Case Control command FREQUENCY = SID.
2. All FREQi entries with the same frequency set identification numbers will be used. Duplicate
frequencies will be ignored. f N and f N – 1 are considered duplicated if
f N – f N – 1 DFREQ f MAX – f MIN ,
–5
where DFREQ is a user parameter, with a default of 10
. f MAX and f MIN are the maximum and
minimum excitation frequencies of the combined FREQi entries.
3. In modal analysis, solutions for modal DOFs from rigid body modes at zero excitation frequencies
may be discarded. Solutions for nonzero modes are retained.
4. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
FREQ1 1843
Frequency List, Alternate Form 1
FREQ1 Frequency List, Alternate Form 1
Defines a set of frequencies to be used in the solution of frequency response problems by specification of a
starting frequency, frequency increment, and the number of increments desired.
Format:
1 2 3 4 5 6 7 8 9 10
FREQ1 SID F1 DF NDF
Example:
FREQ1 6 2.9 0.5 13
Describer Meaning
SID Set identification number. (Integer > 0)
F1 First frequency in set. (Real > 0.0)
DF Frequency increment. (Real > 0.0)
NDF Number of frequency increments. (Integer > 0; Default = 1)
Remarks:
1. FREQ1 entries must be selected with the Case Control command FREQUENCY = SID.
2. The units for F1 and DF are cycles per unit time.
3. The frequencies defined by this entry are given by
f i = F1 + DF i – 1
where i = 1 to (NDF + 1).
4. All FREQi entries with the same frequency set identification numbers will be used. Duplicate
frequencies will be ignored. f N and f N – 1 are considered duplicated if
f N – f N – 1 DFREQ f MAX – f MIN ,
–5
where DFREQ is a user parameter, with a default of 10
. f MAX and f MIN are the maximum and
minimum excitation frequencies of the combined FREQi entries.
5. In modal analysis, solutions for modal DOFs from rigid body modes at zero excitation frequencies
may be discarded. Solutions for nonzero modes are retained.
6. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1844 FREQ2
Frequency List, Alternate Form 2
FREQ2 Frequency List, Alternate Form 2
Defines a set of frequencies to be used in the solution of frequency response problems by specification of a
starting frequency, final frequency, and the number of logarithmic increments desired.
Format:
1 2 3 4 5 6 7 8 9 10
FREQ2 SID F1 F2 NF
Example:
FREQ2 6 1.0 8.0 6
Describer Meaning
SID Set identification number. (Integer > 0)
F1 First frequency. (Real > 0.0)
F2 Last frequency. (Real > 0.0, F2 > F1)
NF Number of logarithmic intervals. (Integer > 0; Default = 1)
Remarks:
1. FREQ2 entries must be selected with the Case Control command FREQUENCY = SID.
2. The units for F1 and F2 are cycles per unit time.
3. The frequencies defined by this entry are given by
i – 1 d
f i = F1 e
1 F2
where d = -------- ln ------- and i = 1 2 NF + 1
NF F1
In the example above, the list of frequencies will be 1.0, 1.4142, 2.0, 2.8284, 4.0, 5.6569 and 8.0
cycles per unit time.
4. All FREQi entries with the same frequency set identification numbers will be used. Duplicate
frequencies will be ignored. f N and f N – 1 are considered duplicated if
f N – f N – 1 DFREQ f MAX – f MIN
,
–5
where DFREQ is a user parameter, with a default of 10
. f MAX and f MIN are the maximum and
minimum excitation frequencies of the combined FREQi entries.
5. In modal analysis, solutions for modal DOFs from rigid body modes at zero excitation frequencies
may be discarded. Solutions for nonzero modes are retained.
Main Index
FREQ2 1845
Frequency List, Alternate Form 2
6. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1846 FREQ3
Frequency List, Alternate 3
FREQ3 Frequency List, Alternate 3
Defines a set of excitation frequencies for modal frequency-response solutions by specifying number of
excitation frequencies between two modal frequencies.
Format:
1 2 3 4 5 6 7 8 9 10
FREQ3 SID F1 F2 TYPE NEF CLUSTER
Example:
FREQ3 6 20.0 2000.0 LINEAR 10 2.0
Describer Meaning
SID Set identification number. (Integer > 0)
F1 Lower bound of modal frequency range in cycles per unit time. (Real > 0.0 for
TYPE = LINEAR and Real = 0.0 for TYPE = LOG)
F2 Upper bound of modal frequency range in cycles per unit time. (Real > 0.0; F2 > F1;
Default = F1)
TYPE LINEAR or LOG. Specifies linear or logarithmic interpolation between frequencies.
(Character; Default = “LINEAR”)
NEF Number of excitation frequencies within each subrange including the end points. The
first subrange is between F1 and the first modal frequency within the bounds. The
second subrange is between first and second modal frequencies between the bounds.
The last subrange is between the last modal frequency within the bounds and F2.
(Integer > 1; Default = 10)
CLUSTER Specifies clustering of the excitation frequency near the end points of the range. See
Remark 6. (Real > 0.0; Default = 1.0)
Remarks:
1. FREQ3 applies only to modal frequency-response solutions (SOLs 111, 146, and 200) and is ignored
in direct frequency response solutions.
2. FREQ3 entries must be selected with the Case Control command FREQUENCY = SID.
3. In the example above, there will be 10 frequencies in the interval between each set of modes within
the bounds 20 and 2000, plus 10 frequencies between 20 and the lowest mode in the range, plus 10
frequencies between the highest mode in the range and 2000.
4. Since the forcing frequencies are near structural resonances, it is important that some amount of
damping be specified.
Main Index
FREQ3 1847
Frequency List, Alternate 3
5. All FREQi entries with the same set identification numbers will be used. Duplicate frequencies will
be ignored. f N and f N – 1 are considered duplicated if
f N – f N – 1 DFREQ f MAX – f MIN
–5
where DFREQ is a user parameter, with a default of 10. f MAX an f MIN are the maximum and
minimum excitation frequencies of the combined FREQi entries.
6. CLUSTER is used to obtain better resolution near the modal frequencies where the response varies
the most. CLUSTER > 1.0 provides closer spacing of excitation frequency towards the ends of the
frequency range, while values of less than 1.0 provide closer spacing towards the center of the
frequency range. For example, if the frequency range is between 10 and 20, NEF = 11,
TYPE = “LINEAR”; then, the excitation frequencies for various values of CLUSTER would be as
shown in Table 17.
1 1 1 CLUSTER
f̂ k = --- f̂ 1 + f̂ 2 + --- f̂ 2 – f̂ 1 SIGN
2 2
where
= – 1 + 2 k – 1 NEF – 1 is a parametric coordinate between -1 and 1
k = varies from 1 to NEF (k = 1, 2, ..., NEF)
f̂ 1 = is the lower limit of the frequency subrange
f̂ 2 = is the upper limit of the subrange
f̂ k = is the k-th excitation frequency
f̂ = is the frequency, or the logarithm of the frequency, depending on the value specified for
TYPE
Table 17 CLUSTER Usage Example
CLUSTER
c=0.25 c-0.50 c-1.0 c-2.0 c-4.0
Excitation
Frequency Number Excitation Frequencies in Hertz
1 -1.0 10.00 10.0 10.0 10.00 10.00
2 -0.8 12.95 11.8 11.0 10.53 10.27
3 -0.6 14.35 13.2 12.0 11.13 10.60
4 -0.4 14.87 14.2 13.0 11.84 11.02
5 -0.2 14.99 14.8 14.0 12.76 11.66
6 0.0 15.00 15.0 15.0 15.00 15.00
7 0.2 15.01 15.2 16.0 17.24 18.34
Main Index
1848 FREQ3
Frequency List, Alternate 3
Table 17 CLUSTER Usage Example
CLUSTER
c=0.25 c-0.50 c-1.0 c-2.0 c-4.0
Excitation
Frequency Number Excitation Frequencies in Hertz
8 0.4 15.13 15.8 17.0 18.16 18.98
9 0.6 15.65 16.8 18.0 18.87 19.40
10 0.8 17.05 18.2 19.0 19.47 19.73
11 1.0 20.00 20.0 20.0 20.00 20.00
7. In design optimization (SOL 200), the excitation frequencies are derived from the natural frequencies
computed at each design cycle.
8. In modal analysis, solutions for modal DOFs from rigid body modes at zero excitation frequencies
may be discarded. Solutions for nonzero modes are retained.
9. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
FREQ4 1849
Frequency List, Alternate Form 4
FREQ4 Frequency List, Alternate Form 4
Defines a set of frequencies used in the solution of modal frequency-response problems by specifying the
amount of “spread” around each natural frequency and the number of equally spaced excitation frequencies
within the spread.
Format:
1 2 3 4 5 6 7 8 9 10
FREQ4 SID F1 F2 FSPD NFM
Example:
FREQ4 6 20.0 2000.0 0.30 21
Describer Meaning
SID Set identification number. (Integer > 0)
F1 Lower bound of frequency range in cycles per unit time. (Real > 0.0; Default = 0.0)
F2 Upper bound of frequency range in cycles per unit time. (Real > 0.0; F2 > F1;
Default = 1.0E20)
FSPD Frequency spread, +/- the fractional amount specified for each mode which occurs in
the frequency range F1 to F2. (1.0 > Real > 0.0; Default = 0.10)
NFM Number of evenly spaced frequencies per “spread” mode. (Integer > 0; Default = 3; If
NFM is even, NFM + 1 will be used.)
Remarks:
1. FREQ4 applies only to modal frequency-response solutions (SOLs 111, 146, and 200 and is ignored
in direct frequency-response solutions.
2. FREQ4 entries must be selected with the Case Control command FREQUENCY = SID.
3. There will be NFM excitation frequencies between 1 – FSPD f N and 1 + FSPD f N , for
each natural frequency in the range F1 to F2.
4. In the example above there will be 21 equally spaced frequencies across a frequency band of 0.7 f N
to 1.3 f N for each natural frequency that occurs between 20 and 2000. See Figure 9-90 for the
definition of frequency spread.
Main Index
1850 FREQ4
Frequency List, Alternate Form 4
1 – FSPD f N fN 1 + FSPD f N
Figure 9-90 Frequency Spread Definition
Excitation frequencies may be based on natural frequencies that are not within the range (F1 and F2)
as long as the calculated excitation frequencies are within the range. Similarly, an excitation frequency
calculated based on natural frequencies within the range (F1 through F2) may be excluded if it falls
outside the range.
5. The frequency spread can be used also to define the half-power bandwidth. The half-power
bandwidth is given by 2 f N , where is the damping ratio. Therefore, if FSPD is specified equal
to the damping ratio for the mode, NFM specifies the number of excitation frequency within the
half-power bandwidth. See Figure 9-91 for the definition of half-power bandwidth.
Peak Response
2 fN
Half-Power Point (.707 Peak)
Amplitude
fN Frequency
Half-Power
Bandwidth
Figure 9-91 Half-Power Bandwidth Definition
6. Since the forcing frequencies are near structural resonances, it is important that some amount of
damping be specified.
Main Index
FREQ4 1851
Frequency List, Alternate Form 4
7. All FREQi entries with the same set identification numbers will be used. Duplicate frequencies will
be ignored. f N and f N – 1 are considered duplicated if
f N – f N – 1 DFREQ f MAX – f MIN
–5
where DFREQ is a user parameter with a default of 10 . The values f MAX and f MIN are the
maximum and minimum excitation frequencies of the combined FREQi entries.
8. In design optimization (SOL 200), the excitation frequencies are derived from the natural frequencies
computed at each design cycle.
9. In modal analysis, solutions for modal DOFs from rigid body modes at zero excitation frequencies
may be discarded. Solutions for nonzero modes are retained.
10. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1852 FREQ5
Frequency List, Alternate Form 5
FREQ5 Frequency List, Alternate Form 5
Defines a set of frequencies used in the solution of modal frequency-response problems by specification of a
frequency range and fractions of the natural frequencies within that range.
Format:
1 2 3 4 5 6 7 8 9 10
FREQ5 SID F1 F2 FR1 FR2 FR3 FR4 FR5
FR6 FR7 -etc.-
Example:
FREQ5 6 20.0 2000.0 1.0 0.6 0.8 0.9 0.95
1.05 1.1 1.2
Describer Meaning
SID Set identification number. (Integer > 0)
F1 Lower bound of frequency range in cycles per unit time. (Real > 0.0; Default = 0.0)
F2 Upper bound of frequency range in cycles per unit time. (Real > 0.0; F2 > F1;
Default = 1.0E20)
FRi Fractions of the natural frequencies in the range F1 to F2. (Real > 0.0)
Remarks:
1. FREQ5 applies only to modal frequency-response solutions (SOLs 111, 146, and 200) and is ignored
in direct frequency response solutions.
2. FREQ5 entries must be selected with the Case Control command FREQUENCY = SID.
3. The frequencies defined by this entry are given by
f i = FRi f N
i
where f N are the natural frequencies in the range F1 through F2.
i
4. In the example above, the list of frequencies will be 0.6, 0.8, 0.9, 0.95, 1.0, 1.05, 1.1, and 1.2 times
each natural frequency between 20 and 2000. If this computation results in excitation frequencies
less then F1 and greater than F2, those computed excitation frequencies are ignored.
Excitation frequencies may be based on natural frequencies that are not within the range (F1 and F2)
as long as the calculated excitation frequencies are within the range. Similarly, an excitation frequency
calculated based on natural frequencies within the range (F1 through F2) may be excluded if it falls
outside the range.
5. Since the forcing frequencies are near structural resonances, it is important that some amount of
damping be specified.
Main Index
FREQ5 1853
Frequency List, Alternate Form 5
6. All FREQi entries with the same set identification numbers will be used. Duplicate frequencies will
be ignored. f N and f N – 1 are considered duplicated if
f N – f N – 1 DFREQ f MAX – f MIN
–5
where DFREQ is a user parameter with a default of 10 . The values f MAX and f MIN are the
maximum and minimum excitation frequencies of the combined FREQi entries.
7. In design optimization (SOL 200), the excitation frequencies are derived from the natural frequencies
computed at each design cycle.
8. In modal analysis, solutions for modal DOFs from rigid body modes at zero excitation frequencies
may be discarded. Solutions for nonzero modes are retained.
9. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1854 FRFCOMP
Frequency Response Function (FRF) Component Specification for FRF Based Assembly (FBA)
FRFCOMP Frequency Response Function (FRF) Component Specification for FRF Based
Assembly (FBA)
Specifies the FRF components that are to be assembled as part of an FRF Based Assembly (FBA) process.
Format:
1 2 3 4 5 6 7 8 9 10
FRFCOMP COMPID COMPNAME MEDIUM UNITNO LSCALFAC FSCALFAC
Examples:
FRFCOMP 10 LEFTWING OP2 25
FRFCOMP 20 FRAME UF 30 1000.0
Describer Meaning
COMPID ID of the component whose FRFs have been generated in a previous Nastran
execution. (Integer > 0)
COMPNAME Name of the COMPID FRF component. See Remark 1. (Up to 8 characters).
MEDIUM Medium on which the FRF matrices and other related data are stored. Acceptable
character values are DB (for database), OP2 (for OUTPUT2 file) or UF (for
Universal file). See Remarks 2., 3. and 4.
UNITNO Fortran unit number for the OP2 and UF options. (Integer > 0). See Remarks 3.
and 4.
LSCALFAC Length scale factor for the UF option. (Real > 0.0; Default = 1.0). See Remarks 7.,
8., 9., 10. and 11.
FSCALFAC Force scale factor for the UF option. (Real > 0.0; Default = 1.0). See Remarks 7.,
8., 9., 10., and 11.
Remarks:
1. COMPNAME may be referenced by the ASMOUT keyword in the FRF Case Control command in
order to request output for a specific FRF component in the FBA process. Accordingly,
COMPNAME may not have the values of CONNINFO, ALL, COMP or ASSEMBLY as these are
all reserved words for use with the ASMOUT keyword in the FRF Case Control command.
2. If the DB option is specified, then the following type of ASSIGN should be specified in the FMS
section of the FBA job to access information on the database for the specified FRF component:
ASSIGN dbname = ’frfgen_job.MASTER
DBLOCATE DATABLK = (FRFDB) LOGICAL = dbname
Main Index
FRFCOMP 1855
Frequency Response Function (FRF) Component Specification for FRF Based Assembly (FBA)
3. If the OP2 option is specified, then the following type of ASSIGN should be specified in the FMS
section of the FBA job to access information on the OUTPUT2 file for the specified FRF
component:
ASSIGN INPUTT2 = ’frfgen_job_op2’ UNIT = 25
4. If the UF option is specified, then the following type of ASSIGN should be specified in the FMS
section of the FBA job to access information on the Universal file for the specified FRF component:
ASSIGN UNVFILE = ’frfgen_job_unv’ UNIT = 26
5. Component ID of 0 is assigned to the assembled FRF configuration resulting from the FBA process.
6. An FRF generation job using an FRF Case Control command with GEN/GENASM and COMPID
and COMPNAME keywords specified in it will automatically generate and save an FRFCOMP Bulk
Data entry on the assembly punch (.asm) file for that FRF component for subsequent use in an FBA
process.
7. LSCALFAC and FSCALFAC are meaningful only for the UF option. They are ignored for the DB
and OP2 options.
8. The FRF and other information on the Universal File (UF) is grouped by so-called Universal Dataset
Numbers (UDNs). The heart of the information on the UF for a test FRF component is in UDN
58 which contains FRF data for that component. Also of interest, if present, is UDN 15 which
contains grid point coordinate data in single precision or UDN 2411 which contains grid point
coordinate data in double precision. Further, if UDN 15 or UDN 2411 is present, the data therein
may reference definition or displacement coordinate systems. Such coordinate system data is resident
in UDN 18.
Details of the various UDNs and their formats can be obtained from the following websites:
http://www.sdrl.uc.edu/universal-file-formats-for-modal-analysis-testing-1
http://www.sdrl.uc.edu/universal-file-formats-for-modal-analysis-testing-1/file-format-storehouse/file-formats
9. The points of a test FRF component that are considered by the FBA process are those that are defined
in UDN 58 either as response points or as excitation points. Any such point that appears both as a
response point and as an excitation point is regarded as a potential connection point of the test FRF
component.
10. Connections between test FRF components and other FRF components are determined by what is
supplied on the UF as indicated below.
a. If UDN 15 or UDN 2411 is supplied on the UF, then connections between the test FRF
component grid points and those of other FRF components will be based on matching
coordinates.
b. If neither UDN 15 nor UDN 2411 is supplied, then normally, connections between the test FRF
component grid points and those of other FRF components will be based on matching grid point
IDs. However, the user can override this by specifying FRFCONN entries, thereby causing
connections between user specified grid points. In any case, when the connections are based on
matching grid point IDs or based on FRFCONN entries, it is the user's responsibility to ensure
that the connection grid points have the same physical locations in space so that correct results
are obtained from the FBA process. The program clearly cannot check for this condition since the
coordinates of one or more of the points are not available.
Main Index
1856 FRFCOMP
Frequency Response Function (FRF) Component Specification for FRF Based Assembly (FBA)
11. For the UF option, LSCALFAC and FSCALFAC are used as follows:
• For Universal Dataset No. (UDN) 15 or 2411 (if present) on the Universal File:
The X, Y, and Z coordinate values in the UDN are multiplied by LSCALFAC before they are
used in the FBA process.
• For Universal Dataset No. (UDN) 58 on the Universal File:
The FRF response quantities in the UDN are multiplied by appropriate factors as shown in the
following table before they are used in the FBA process.
Table 9-16 Multiplication Factors for FRF Response Quantities in UDN 58 of the Universal File
Factor by Which FRF Response Quantity
is Multiplied Before It is Used in the FBA
FRF Response Quantity Type of Excitation Process
Translational displacement, Unit force at an excitation LSCALFAC/FSCALFAC
velocity or acceleration at a point
structural point Unit moment at an excitation 1.0/FSCALFAC
point
Rotational displacement, Unit force at an excitation 1.0/FSCALFAC
velocity or acceleration at a point
structural point Unit moment at an excitation 1.0/(LSCALFAC*FSCALFAC)
point
Pressure at an acoustic point Unit force at an excitation 1.0/(LSCALFAC**2)
point
Unit moment at an excitation 1.0/(LSCALFAC**3)
point
Main Index
FRFCONN 1857
FRF Component Explicit Connection for FRF Based Assembly (FBA)
FRFCONN FRF Component Explicit Connection for FRF Based Assembly (FBA)
Defines explicit connection data for FRF components in an FRF Based Assembly (FBA) process.
Format:
1 2 3 4 5 6 7 8 9 10
FRFCONN CONNID COMPID1/ POINT1 COMPID2/ POINT2
COMPNAM1 COMPNAM2
Examples:
FRFCONN 10 5 100 15 200
FRFCONN 20 STRUT 25 WING 35
Describer Meaning
CONNID Unique identification number of the FRFCONN entry. (Integer > 0)
COMPIDi Identification number of an FRF component whose FRFs have been generated in a
previous Nastran execution. See Remark 1. (Integer > 0)
COMPNAMi Name of an FRF component whose FRFs have been generated in a previous Nastran
execution. See Remark 1. (Up to 8 characters; no blank allowed)
POINTi Grid or scalar point identification number. See Remarks 2. through 6. (Integer > 0)
Remarks:
1. If neither of the FRF components COMPID1/COMPNAM1 and COMPID2/COMPNAM2 is
part of the FBA process, then this entry is ignored. However, if one of them is part of the FBA process
but not the other, the program terminates the job with a user fatal message.
2. POINTi must be among the connection points of the corresponding FRF component
COMPIDi/COMPNAMi. If not, the program terminates the job with a user fatal message.
3. It is, in general, not necessary to have FRFCONN entries when the connections in the FBA process
involve only grid points. In the FBA process, all connection grid points of FRF components that
have the same basic coordinates are normally connected automatically without any user intervention
or specification.
4. If the connection points of an FRF component in the FBA process consist of coincident grid points,
the program identifies such points via a user information message. All such coincident grid points
must be referenced on FRFCONN or FRFRELS entries in order to ensure proper connections in the
FBA process. In the absence of such specifications for coincident connection grid points, the program
terminates the job with a user fatal error.
5. FRFCONN entries are required if the user wants to specify explicit connections between test FRF
component grid points whose coordinates are not available and those of other FRF components. See
Remark 10. under the description of the FRFCOMP entry for further details.
Main Index
1858 FRFCONN
FRF Component Explicit Connection for FRF Based Assembly (FBA)
6. FRFCONN entries are also required if the user wants to combine scalar points of FRF components
in the FBA process.
Main Index
FRFFLEX 1859
FRF Component Flexible Connection Specification for FRF Based Assembly (FBA)
FRFFLEX FRF Component Flexible Connection Specification for FRF Based Assembly (FBA)
Defines properties for flexible connections between FRF components in an FRF Based Assembly (FBA)
process.
Format:
1 2 3 4 5 6 7 8 9 10
FRFFLEX FLEXID C COMPID1/ POINT1 COMPID2/ POINT2 KVALUE/ BVALUE/
COMPNAM1 COMPNAM2 KTABID BTABID
GEVALUE/
GETABID
Examples:
FRFFLEX 10 1 100 15 200 25 100.0 150
0.02
FRFFLEX 20 4 STRUT 120 WING 260 10 0.25
Describer Meaning
FLEXID Unique identification number of the FRFFLEX entry. (Integer > 0)
C A single component number. (Any integer between 1 and 6 for grid points; integer 0 or
blank for scalar points.)
COMPIDi Identification number of an FRF component whose FRFs have been generated in a
previous Nastran execution. See Remark 1. (Integer > 0)
COMPNAMi Name of an FRF component whose FRFs have been generated in a previous Nastran
execution. See Remark 1. (Up to 8 characters; no blank allowed)
POINTi Grid or scalar point identification number. See Remark 2. (Integer > 0)
KVALUE Elastic property value (force per unit displacement). See Remark 3. (Real > 0.0 or
blank)
KTABID Identification number of a TABLEDi entry that defines the elastic property value (force
per unit displacement) as a function of frequency. See Remark 3. (Integer > 0 or blank)
BVALUE Damping property value (force per unit velocity). See Remark 3. (Real > 0.0 or blank)
BTABID Identification number of a TABLEDi entry that defines the damping property value
(force per unit velocity) as a function of frequency. See Remark 3. (Integer > 0 or blank)
GEVALUE Damping coefficient value. See Remarks 4., 5. and 6. (Real > 0.0 or blank)
GETABID Identification number of a TABLEDi entry that defines the damping coefficient value
as a function of frequency. See Remarks 4., 5. and 6. (Integer > 0 or blank)
Main Index
1860 FRFFLEX
FRF Component Flexible Connection Specification for FRF Based Assembly (FBA)
Remarks:
1. If neither of the FRF components COMPID1/COMPNAM1 and COMPID2/COMPNAM2 is
part of the FBA process, then this entry is ignored. However, if one of them is part of the FBA process
but not the other, the program terminates the job with a user fatal message.
2. POINTi must be among the connection points of the corresponding FRF component
COMPIDi/COMPNAMi. If not, the program terminates the job with a user fatal message.
3. The KVALUE/KTABID and BVALUE/BTABID fields may not both be blank.
4. The continuation entry is not needed if GEVALUE/GETABID is not to be defined.
5. GEVALUE/GETABID may not be specified unless KVALUE/KTABID is specified.
6. To obtain the damping coefficient, multiply the critical damping ratio C C 0 by 2.0.
7. It is important to note that this entry by itself does not define a connection between the specified
points. It merely defines properties for flexible connections between two points whose connection is
established either explicitly via an FRFCONN entry or is implied by automatic connection.
8. The flexible connection properties for component C of connection points POINT1 and POINT2
may be defined on more than one FRFFLEX entry.
9. In the absence of FRFFLEX data, the program assumes rigid connections between the corresponding
components.
10. A grid point component may not appear on both an FRFFLEX entry and an FRFRELS entry. If it
does, the program identifies such usage and terminates the job with a user fatal message.
Main Index
FRFRELS 1861
FRF Component Grid Point Release for FRF Based Assembly (FBA)
FRFRELS FRF Component Grid Point Release for FRF Based Assembly (FBA)
Defines the degrees-of-freedom of FRF component connection grid points that are not to be connected in
an FRF Based Assembly (FBA) process.
Format:
1 2 3 4 5 6 7 8 9 10
FRFRELS SID C COMPID1/ GRIDPNT1 COMPID2/ GRIDPNT2 COMPID3/ GRIDPNT3
COMPNAM1 COMPNAM2 COMPNAM3
Examples:
FRFRELS 100 45 10 15 BODY 20 FRAME 30
FRFRELS 20 1 WING 25 NACELLE 35
Describer Meaning
SID Identification number of the FRFRELS entry. (Integer > 0)
C Component number(s). See Remark 1. (Any unique combination of the integers 1
through 6 with no embedded blanks.)
COMPIDi Identification number of an FRF component whose FRFs have been generated in a
previous Nastran execution. See Remark 2. (Integer > 0)
COMPNAMi Name of an FRF component whose FRFs have been generated in a previous Nastran
execution. See Remark 2. (Up to 8 characters; no blank allowed)
GRIDPNTi Grid point identification number. See Remarks 3. and 4. (Integer > 0)
Remarks:
1. The grid point component(s) specified by C will not be connected in the FBA process.
2. If FRF component COMPIDi/COMPNAMi is not part of the FBA process, then the release data for
that FRF component is ignored.
3. GRIDPNTi must be among the connection points of the corresponding FRF component
COMPIDi/COMPNAMi. If not, the program terminates the job with a user fatal message.
4. If GRIDPNTi is not connected to any other grid point in the FBA process, the program ignores the
FRFRELS data for this point and issues a warning message indicating this to the user.
5. If the connection points of an FRF component in the FBA process consist of coincident grid points,
the program identifies such points via a user information message. All such coincident grid points
must be referenced on FRFCONN or FRFRELS entries in order to ensure proper connections in the
FBA process. In the absence of such specifications for coincident connection grid points, the
program terminates the job with a user fatal error.
Main Index
1862 FRFSPC1
FRF Component Single-Point Constraint for FRF Based Assembly (FBA)
FRFSPC1 FRF Component Single-Point Constraint for FRF Based Assembly (FBA)
Defines single-point constraints for FRF component connection points in an FRF Based Assembly (FBA)
process.
Format:
1 2 3 4 5 6 7 8 9 10
FRFSPC1 SID C COMPID1/ POINT1 COMPID2/ POINT2 COMPID3/ POINT3
COMPNAM1 COMPNAM2 COMPNAM3
Examples:
FRFSPC1 100 4 10 12 ENGINE 23 FRAME 31
FRFSPC1 20 1 STRUT 25 NACELLE 35
Describer Meaning
SID Identification number of the single-point constraint set. See Remark 1. (Integer > 0)
C Component number(s). (Any unique combination of the integers 1 through 6 with no
embedded blanks for grid points; integer 0 or blank for scalar points.)
COMPIDi Identification number of an FRF component whose FRFs have been generated in a
previous Nastran execution. See Remark 2. (Integer > 0)
COMPNAMi Name of an FRF component whose FRFs have been generated in a previous Nastran
execution. See Remark 2. (Up to 8 characters; no blank allowed)
POINTi Grid or scalar point identification number. See Remarks 3. and 4. (Integer > 0)
Remarks:
1. Single-point constraint sets must be selected with the Case Control command SPC = SID.
2. If FRF component COMPIDi/COMPNAMi is not part of the FBA process, then the single-point
constraint data for that FRF component is ignored.
3. POINTi must be among the connection points of the corresponding FRF component
COMPIDi/COMPNAMi. If not, the program terminates the job with a user fatal message.
4. If POINTi is not connected to any other point in the FBA process, the program ignores the FRFSPC1
data for this point and issues a warning message indicating this to the user.
5. Unlike in non-FBA jobs, wherein a degree-of-freedom that has SPCs specified for it yields exact zero
results, a degree-of-freedom that has an FRFSPC1 specified for it in an FBA job will, in general, not
give exact zero results, but will give results that are nearly zero or very close to zero, usually around
1.0E-12 or so.
Main Index
FRFXIT 1863
Unit Load Degree-of-Freedom Specification for Frequency Response Function (FRF) Computations
FRFXIT Unit Load Degree-of-Freedom Specification for Frequency Response Function
(FRF) Computations
Specifies a single degree-of-freedom where unit loads are to be applied for Frequency Response Function
(FRF) generation.
Format:
1 2 3 4 5 6 7 8 9 10
FRFXIT PNTID C LABEL
Example:
FRFXIT 10 3 UNIT LOAD AT LEFT CORNER
Describer Meaning
PNTID Grid or scalar point identification number. (Integer > 0)
C A single component number. (Integer 0 or blank for a scalar point; any integer between
1 and 6 for a grid point.)
LABEL A string comprising no more than 48 characters (fields 4 through 9) that will be used
in the label portion of the FRF output to identify this unit load specification. See
Remarks 1. and 2.
Remarks:
1. The small field format must be employed for this entry. If the free field or large field format is
employed, the results are unpredictable and in many cases may lead to fatal errors and subsequent
termination of the job.
2. The LABEL data must have a non-blank entry in field 4.
3. The FRFXIT1 Bulk Data entry and the DLOAD Case Control request provide alternate means of
unit load specification for FRF generation.
4. Redundant unit load specifications are ignored.
5. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1864 FRFXIT1
Unit Load Degrees-of-Freedom Specification for Frequency Response Function (FRF) Computations
FRFXIT1 Unit Load Degrees-of-Freedom Specification for Frequency Response
Function (FRF) Computations
Specifies degrees-of-freedom where unit loads are to be applied for Frequency Response Function (FRF)
generation.
Format:
1 2 3 4 5 6 7 8 9 10
FRFXIT1 C PNTID1 PNTID2 PNTID3 PNTID4 PNTID5 PNTID6 PNTID7
Example:
FRFXIT1 123 10 20 30 40
Alternate Format and Example:
1 2 3 4 5 6 7 8 9 10
FRFXIT1 C PNTID1 THRU PNTID2
FRFXIT1 123 5 THRU 15
Describer Meaning
C Component numbers. (Any unique combination of integers 1 through 6 with no
embedded blanks for grid points; integer 0 or blank for scalar points.)
PNTIDi Grid or scalar point identification numbers. See Remark 1. (Integer > 0)
Remarks:
1. Points in the THRU range need not all exist.
2. The FRFXIT Bulk Data entry and the DLOAD Case Control request provide alternate means of unit
load specification for FRF generation.
3. Redundant unit load specifications are ignored.
4. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
FSICTRL 1865
FSICTRL
Defines the analysis type for OpenFSI fluid structure analysis simulations in SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
FSICTRL SERV_ID TYPE FREQ ANALYSIS
Examples:
FSICTRL scafsi EXPLICIT 1
Describer Meaning
SERV_ID OpenFSI SCA service name associated with the wetted Character None
surface loads (see WETLOAD). The OpenFSI SCA service is
defined using the CONNECT SERVICE file management
section statement.
TYPE Type of solution strategy coupling between the external code Character EXPLICIT
and SOL 700. TYPE can be either EXPLICIT or
IMPLICIT.
FREQ External force and displacement update frequency per time Integer > 0 1
step, for the exchange with the external code using the
IMPLICIT solution strategy TYPE.
ANALYSIS OpenFSI service type, it is either DV or U. The DV Character DV
indicates the service implements OpenFSI interface, the U
means the service implements OpenFSI_Ex interface.
Remarks:
1. This entry is used for nonlinear SOL 400 analysis.
2. In the FMS Section:
CONNECT SERVICE SERV_ID ' ExternalCodeVendor.OpenFSI '
3. The SERV_ID string must be 8 characters or less.
Main Index
1866 FSLIST
Free Surface List
FSLIST Free Surface List
Defines the fluid points (RINGFL entry) that lie on a free surface boundary.
Format:
1 2 3 4 5 6 7 8 9 10
FSLIST RHO IDF1 IDF2 IDF3 IDF4 IDF5 IDF6 IDF7
IDF8 -etc.-
Examples:
FSLIST 1.0-4 AXIS 432 325 416 203 256 175
Describer Meaning
RHO Mass density at the surface. (Real > 0.0 or blank; the default is taken from DRHO on
the AXIF entry.)
IDF1 Identification number of RINGFL entry. (Integer > 0 or Character = “AXIS” or
“LAXIS”) See Remark 5.
IDF2-IDFi Identification number of additional RINGFL entries. (Unique Integers > 0)
Remarks:
1. This entry is allowed only if an AXIF entry is also present.
2. The order of the points must be sequential with the fluid on the right with respect to the direction of
travel.
3. The word “AXIS” defines an intersection with the polar axis of the fluid coordinate system.
4. If the fluid density varies along the boundary, there must be one FSLIST entry for each interval
between fluid points.
5. If the polar axis of the fluid coordinate system is to occur at the first point use AXIS. If the polar axis
of the fluid coordinate system is to occur at the last point use LAXIS. See Remark 2.
Main Index
FTGDEF 1867
Fatigue Element Definitions
FTGDEF Fatigue Element Definitions
Defines elements and their associated fatigue properties to be considered for fatigue analysis for time domain
SOLutions 101, 103, 112 and frequency domain SOLutions 108 and 111.
Format (SOL 101/103/112):
11
1 2 3 4 5 6 7 8 9 10
FTGDEF ID TOPSTR PFTGID TOPDMG NENTS maxENTS NHS HSGATE
"ELSET" ELSID1 PFTGID1 ELSID2 PFTGID2 ELSID3 PFTGID3
ELSID4 PFTGID4 ... ... ... ...
-etc.-
"SPOTW" ELSID1 PFTGID1 ELSID2 PFTGID2 ELSID3 PFTGID3
ELSID4 PFTGID4 ... ... ... ...
-etc.-
"SEAMW" ELSID1 PFTGID1 NDSID1 WELD1 TYPE1
ELSID2 PFTGID2 NDSID2 WELD2 TYPE2
-etc.-
"XELSET" XELSID1 XELSID2 XELSID3 XELSID4 XELSID5 XELSID6 XELSID7
XELSID8 ... ... ... ... ... ...
-etc.-
Format (SOL 108/111):
1 2 3 4 5 6 7 8 9 10
FTGDEF ID TOPRMS
"ELSET" ELSID1 ELSID2 ELSID3
ELSID4 ... ...
-etc.-
"XELSET" XELSID1 XELSID2 XELSID3 XELSID4 XELSID5 XELSID6 XELSID7
XELSID8 ... ... ... ... ... ...
-etc.-
Examples:
FTGDEF 22 100.0 3
FTGDEF 22
ELSET 14 3 15 4
Main Index
1868 FTGDEF
Fatigue Element Definitions
FTGDEF 22
SPOTW 44 1 45 2 46
FTGDEF 22
SEAMW 44 99 31 FILLET TOE
45 99 LASER ROOT
Describer Meaning
ID Unique identification number called out by the FATIGUE case control.
(Integer > 0).
TOPSTR SOL 101, 103, 112: Top stress percentage. Retains and reports only the percentage of
entities with the highest simple stress range. Cannot be used with SOL 200 or for
fatigue analysis of spot and seam welds; leave blank. (-100.0 Real 100.0; Default =
blank - 100% will be used). See Remark 8.
TOPRMS SOL 108, 111: Top RMS (root mean square) stress percentage. Only entities with RMS
stress levels in this top percentage are retained and report results. (0.0 < Real 100.0;
Default = blank - 100% will be used)
PFTGID SOL 101, 103, 112 only. ID of a PFTG entry for associating fatigue properties to all
elements of the model. Ignored if ELSET flag is present and should be left blank in this
case. (Optional, Integer > 0). See Remark 2.
TOPDMG SOL 101, 103, 112 only. Top damage percentage. Retains and reports only the
percentage of entities with the highest damage. (0.0 < Real 100.0; Default = blank).
Cannot be used with SOL 200 or for fatigue analysis of spot and seam welds; leave
blank. See Remark 8.
NENTS SOL 101, 103, 112 only. Specifies the number of actual entities to output in order to
limit or further reduce output file sizes based on most damage or maximum stress/strain
range. A positive value indicates the criterion for entity filtering is based on the most
damaged entities. A negative number indicates the filtering criteria is based on
maximum stress/strain range. (Integer 0; Default = blank). Not valid for SOL 200;
leave blank. See Remark 10.
maxENTS SOL 101, 103, 112 only. This is used only if STROUT=4 is specified in the FATIGUE
case control. If the number of entities requested is greater than maxENTS, the job stops
to avoid performance issues. Setting this to a large number can severely affect
performance. (Integer > 0; Default = 100). See Remark 11.
NHS SOL 101, 103, 112 only. Specifies the number of hot spots to identify in the model.
(Integer > 0; Default = blank). This setting overrides TOPSTR and/or TOPDMG. See
Remark 8.
HSGATE SOL 101, 103, 112 only. Number of element layers to keep around each hot spot
defined by NHS. Zero (0) indicates that only the hot spot elements are retained.
Otherwise HSGATE layers of connected elements around each hot spot element are
retained. (Integer > 0; Default = 0).
Main Index
FTGDEF 1869
Fatigue Element Definitions
Describer Meaning
ELSET Flag indicating that a list of element set and property pairs will follow, defining the
elements and their associated properties for consideration in the fatigue analysis.
(Optional, Character = ELSET) See Remark 9.
ELSIDi ID of a SET1, SET3, or SET4 entry listing entities of the model (elements) to be
included in the fatigue analysis. (Integer > 0). See Remark 3.
PFTGIDi ID of a PFTG entry, which indicates the fatigue property associated to the preceding
entities defined by ELSIDi. (Optional, Integer > 0). See Remark 2.
SPOTW SOL 101, 103, 112 only. Flag indicating that a list of element set and property pairs
will follow, defining the elements and their associated properties for fatigue analysis of
spot welds. See Remark 5. and 6.
ELSIDi Same as ELSIDi under ELSET above. See Remark 3.
PFTGIDi Same as PFTGIDi under ELSET above.
SEAMW SOL 101, 103, 112 only. Flag indicating that a list of element set and property pairs
will follow, defining the elements and their associated properties for fatigue analysis of
seam welds. See Remark 5.
ELSIDi Same as ELSIDi under ELSET above. These are to elements that make up the seam
weld toe, root, or throat. See Remark 3.
PFTGIDi Same as PFTGIDi under ELSET above.
NDSIDi ID of a SET1 or SET3 entry listing grids of the elements defined by ELSIDi to be
retained in the analysis. These grids define the seam line of the seam weld. If left blank,
all nodes of the elements are retained. Nodes defined that are not part of ELSIDi are
ignored. (Optional, Integer >0).
WELDi Seam weld definition. One of the following: FILLET, OVERLAP, LASER, EDGE, or
GENERIC, which define either a fillet, overlap, laser overlap, laser edge overlap or
generic seam weld, respectively. (Character; Default=GENERIC). See Remark 7.
TYPEi The type location on the seam weld that this set of elements represent. One of the
following: TOE, ROOT, or THROAT. (Character; Default = TOE for all but WELDi
= LASER where Default = ROOT). See Remark 7.
XELSET Flag indicating that sets of elements to be excluded from the fatigue analysis will follow.
(Optional, Character). See Remark 4.
XELSIDi ID of a SET1 or SET3 entry listing elements of the model to be excluded from the
fatigue analysis. (Integer>0). See Remark 3.
Main Index
1870 FTGDEF
Fatigue Element Definitions
Remarks:
1. FTGDEF bulk data entries are ignored if not selected by a FATIGUE case control. If no FTGDEF
is present for a given fatigue analysis (or only the FTGDEF with no ELSET line), all elements of the
model that have fatigue material properties defined are used with default properties except for fatigue
analysis of spot and seam welds. If a mix of standard SN/N and seam/spot weld analyses is requested,
then an ELSET line is required, otherwise the standard SN/N analysis is ignored. See Remark 5.
below.
2. If no PFTGID or PTFGIDi is specified, default properties are assigned to the entities.
3. If a SET3 is specified, field 3 of the SET3 entry must be set to "ELEM". The SET4 entry must be
specified to select elements by property ID. The following elements referenced by PSHELL,
PSHEAR, and PSOLID properties are supported for standard S-N and -N fatigue analysis:
CQUAD4, CQUADR, CQUAD8, CSHEAR, CTRIA3,CTRIAR, CTRIA6, CHEXA, CPENTA,
CPYRAM and CTETRA. The following elements referenced by PBAR, PBEAM, PSOLID, and
PWELD properties are supported for fatigue analysis of spot welds: CBAR, CBEAM, CHEXA,
CWELD. Only elements referenced by PSHELL properties are available for fatigue analysis of seam
welds, excluding TRIA3 as no corner stresses are available from this element.
4. If only the XELSET flag is present, then the entire model is included in the fatigue analysis less the
excluded entities.
5. For fatigue analysis of spot or seam welds, the FTGDEF card is required with the corresponding keyword
and line defining the elements of interest. If standard SN/N analysis is also requested, then an
ELSET line is required, otherwise the standard SN/N analysis is ignored.
6. Elements used to represent spot welds are typically very stiff bar or beam (CBAR/CBEAM) elements,
weld (CWELD) elements, or individual solid (CHEXA) elements. These elements connect the two
metal sheets defined by shell elements (CSHELL). Bars and beams must connect directly to the grids
of the shells, whereas welds and fasteners only need to pierce the shell elements. If individual solid
elements are used, face G1-G2-G3-G4 must have its grids connected to shell elements that define the
top sheet (sheet 1) via RBE3 rigid elements. And face G5-G6-G7-G8 must have corresponding RBE3
elements connecting the bottom sheet (sheet 2). Some CWELD options auto-generate grids on the
top and bottom metal sheets (when only GS grid is defined on CWELD entry with no GA/GB grids);
the fatigue results are associated to these generated grids.
7. The normals of the throat elements should point outward toward the welder, except for laser overlap,
in which case the normals just need to be consistently the same direction. The elements defining the
toe and root of the weld must have the top of the shell (Z2 layer) be the side where the crack is
expected to develop. For full descriptions of the throat, root, and toe elements for the various seam
welds, please see the MSC Nastran Embedded Fatigue User’s Guide, which show proper modeling
techniques. The WELDi and TYPEi entries are used for labeling purposes only and have no effect on
internal calculations.
8. Use of TOPSTR/TOPDMG, or NHS/HSGATE allows the user to significantly speed up the analysis
times of very large models and more quickly determine the critical damage locations and reduce
output. The preferred method is to use NHS/HSGATE as opposed to TOPSTR and/or TOPDMG.
If NHS is defined, it overrides any TOPSTR and/or TOPDMG settings, as they are mutually
exclusive.
Main Index
FTGDEF 1871
Fatigue Element Definitions
• NHS/HSGATE: This method determines high damaged areas called hot spots. The algorithm is
such that the hot spots detected are distinct from one another. In other words, if two adjacent
elements show the highest damage, and NHS=2, the two adjacent element only count as one hot
spot and another hot spot away from the first one is detected. In order to show nice
postprocessing plots, use HSGATE to retain a certain number of element layers around each hot
spot element. If HSGATE=0, only a single element for each hot spot is retained, which means
that not all the highest damaged elements are likely reported.
• If TOPSTR is used alone (TOPDMG is left unspecified), and is a positive percentage, then a two
(2) pass analysis is performed where the first (1st) pass determines the approximate percentage of
entities to retain with the highest simple stress range. The second (2nd) pass computes damage
on only the remaining elements. The simple range test is done using this equation:
Max k – Min k SCALE k vonMises k
assessed = ------------------------------------------------------------------------------------------------
LDM k
-
k
where Maxk and Mink are the maximum and minimum values from each channel of loading
history (load case k). SCALE and LDM are the scale factor and divisor as defined on FTGLOAD
entries for each load case k, otherwise unity is used.
The calculation is similar for strains, except that the output is in strain units, and the calculation
of vonMises strain requires a value of the Poisson ratio. For the purposes of this simple ranking
procedure, the Poisson ratio is assumed to be 0.3. When the analysis involves a duty cycle (loading
sequence), the resulting assessed stress is the largest value from each of the events in the duty cycle.
If a negative percentage is given, then the retained elements are determined based on the actual
stress range after combination and superposition using that specified on the FTGPARM entry.
As an example, if TOPSTR=10%, and the highest stress range is determined to be 1000MPa,
then any entity with stress range higher than 900MPa is retained (10% of 1000 is 100; 1000-
100=900). This can have the effect of retaining many less entities that the positive percentage
method, but has the drawback of being extremely sensitive to high stress gradients.
• If TOPDMG is used alone (TOPSTR=100% or left unspecified), the percentage of entities
returned are simply based on the highest damage. This does not necessarily reduce computation
time, but does significantly reduce result recovery time as less entities are retained.
• If TOPSTR and TOPDMG are both specified, then a 2-pass analysis is performed where the first
(1st) pass eliminates all but the highest stressed entities and the second (2nd) pass returns only
the percentage of damaged entities based on those retained in the 1st pass.
• If none of TOPSTR, TOPDMG, or NHS are specified (all are blank or default), then a complete
analysis is done on all requested elements. This is the default scenario.
9. Element sets must be the same for all FATIGUE case control IDs that request surface resolved stresses
through the FTGPARM entry (SRESOLVE field = YES). Otherwise a fatal condition is flagged and the
analysis stops.
Main Index
1872 FTGDEF
Fatigue Element Definitions
10. This NENTS parameter can be used by itself or in conjunctions with TOPSTR, TOPDMG, or
NHS. Only entities that pass this filter are reported in the f06 file and/or output to the OUTPUT2
and/or HDF5 files. If NENTS is used with the SRESOLVE option on the FTGPARM entry, then the
number of entities printed may be more as the SRESOLVE option saves the number of grids and each
element associated with those grids.
11. If FATIGUE(STROUT=4) case control is used it is highly recommended that output be limited.
Temporary CSV files are created for each entity and F06 output can be enormous if not filtered using
the ELSET entries. The analysis fails if maxENTS is less than the number of elements requested using
ELSET entries when STROUT=4 is specified. Increase maxENTS if necessary after assessing output
needs.
Main Index
FTGEVNT 1873
Fatigue Loading Events
FTGEVNT Fatigue Loading Events
Groups simultaneously applied loads into loading events for pseudo-static fatigue analysis using SOL 101 or
modal analysis using SOL 103 or random vibration fatigue using SOL 108 or SOL 111 by referencing
FTGLOAD entries.
Format (SOL 101, 103, 108, 111):
1 2 3 4 5 6 7 8 9 10
FTGEVNT ID FLOAD1 FLOAD2 FLOAD3 FLOAD4 FLOAD5 FLOAD6 FLOAD7
FLOAD8 ... ... ... ... ... ...
-etc-
“NAME” EVNTNAM
Example:
FTGEVNT 22 4 11
NAME rough_road
Describer Meaning
ID Unique ID. See Remark 1.
FLOADi ID of a FTGLOAD entry (Integer > 0, no default). See Remark 5.
NAME Flag indicating that a name is to be associated with this load event. See Remark
2.
EVNTAM Event name associated with this event (Character). Can span fields 3 through
9, however for practical purposes, the name is truncated in f06 output. No
spaces are allowed. See Remark 3. and 4.
Remarks:
1. Each FTGEVNT ID must be unique relative to all other FTGEVNT and FTGSEQ IDs.
2. Event names are passed to the f06 print file and displayed as the name of the event as opposed to the
event ID. If no name is given, the event is referred to by its ID.
3. EVNTNAM cannot have numbers at the start of any field. For example, using 8 character formatted
fields, the first character of fields 3-9 cannot be numeric (columns 1, 9, 17, etc. of the EVNTNAM
field). These would be acceptable:
“Flights” or “F_l_i_g_h_t_s’.
But these would not be acceptable:
“1_Flights” or “F_l_i_g_2ts”
because the “1” and the “2” are in columns 1 and 9 of the EVNTNAM field.
Main Index
1874 FTGEVNT
Fatigue Loading Events
4. EVNTNAM cannot handle spaces within its field as one might expect. If you wish to uses spaces,
make sure that once a space is used the next character does not start until the start of the next field.
For example, using 8 character formatted fields, the following would be acceptable:
“My_flights” or “My Flights”.
But this would not be acceptable:
“My Flights”
and would end up just being displayed as “Myts” because once a space is encountered within the 8
character field, the code interprets that as no more character data until it processes the next 8 character
field. It is best not to use spaces in EVNTNAM.
5. For random vibration fatigue (SOL 108 and 111),
• Only one FTGLOAD of TYPE=PSD can be referenced
• Only one FTGLOAD of TYPE=STATIC can be referenced
• A FTGEVNT referencing a FTGLOAD of TYPE=STATIC by itself is not allowed
• A FTGEVNT referencing a FTGLOAD of TYPE=SINE or NARROW by itself (or themselves)
is allowed for pure deterministic and/or sine sweeps
• Only single load PSD random input allows mixed deterministic, sine sweep, and static offsets on
random loading. Only a static offset (FTGLOAD of TYPE=STATIC) can be mixed with multi-
load PSD random input.
• FTGSEQ entry referencing FTGEVNT entries cannot mix events containing single load and
multi-load PSDs.
• All multi-load PSD events must all have the same number of channels (input loads).
• When only FTGLOAD entries of TYPE=SINE or NARROW are referenced (i.e., only
deterministic loading with no random loading input), it is recommended that the ATYPE field
of the FTGPARM entry be set to SINE.
Main Index
FTGLOAD 1875
Fatigue Cyclic Loading Variation
FTGLOAD Fatigue Cyclic Loading Variation
Defines cyclic loading variation for pseudo-static fatigue analysis using SOL 101 or modal analysis using
SOL 103 or random PSD, deterministic, sine sweep and/or static offset loading for SOL 108 and SOL 111.
Format (SOL 101 and 103):
1 2 3 4 5 6 7 8 9 10
FTGLOAD ID TID LCID LDM SCALE/ OFFSET/ TYPE CHNL
MAX MIN
"UNITS" EQUIV EQNAME
Format (SOL 108 and 111):
1 2 3 4 5 6 7 8 9 10
FTGLOAD ID TID LCID SCALE OFFSET TYPE
"DETLOAD" F1 G1/H1 B1 F2 G2/H2 B2
F3 G3/H3 B3 ... ... ...
-etc.-
“SWEEP” F1 G1/H1 Fn Gn/Hn
SWTYPE SWNUM SWRATE NSWEEP FRFUNIT LDUNIT
Examples:
FTGLOAD 55 4 2 1.0 1.0 0.0
FTGLOAD 23 4 5 1.0 1.0 0.0 DB
UNITS 5.5 Flights
Main Index
1876 FTGLOAD
Fatigue Cyclic Loading Variation
Describer Meaning
ID Unique ID which is referenced by a FTGEVNT entry or directly by a FATIGUE case
control in the case of SOL 101 only for a single load (Integer > 0). See Remark 1.
TID SOL 101, 103: Table ID of a TABLFTG (or TABLED1) entry that defines the
time variation of the loading or the ID of a UDNAME entry for external definition
of the loading time variation (Integer > 0). See Remarks 2. through 6. Ignored if
TYPE=CONST or STATIC.
SOL 108, 111: leave blank unless:
TYPE=STATIC: UDNAME ID referencing an external OP2 file containing
stress results for static loading offsets. Leave blank (and set LCID = 0 if a
constant offset defined solely by the OFFSET field is desired.
TYPE = PSD with TIM2PSD: UDNAME ID referencing an external RPC or
CSV file when time history to PSD conversion is requested. A TIM2PSD entry
must be present in this case, otherwise TID is ignored.
LCID SOL 101: Subcase ID of a linear static solution SUBCASE (Integer > 0, no
default).
SOL 103: Mode number for SOL 103 (Integer > 0, no default).
SOL 108, 111:
TYPE = PSD with no TIM2PSD: SID of RANDPS entry(ies). TID should be
left blank in this case.
TYPE = PSD with TIM2PSD: -1 for fully correlated multi-input loading, -2
for uncorrelated multi-input loading.
TYPE = STATIC: SUBCASE ID of a static SUBCASE (freq=0.0). A TID must
also be defined in this case to point to an external OP2 file. Set to zero (0) if a
constant offset solely defined by the OFFSET field is desired. TID should be
left blank in this case.
TYPE=SINE or NARROW: SUBCASE ID of transfer function (TF) used for
deterministic or sweep loading. TID should be left blank in this case.
LDM SOL 101, 103 only. Largest magnitude of the applied load (in the same units used to
define the load time variation in field TID) used to normalize the load (Real,
default=1.0). This effectively scales the stress to simulate a stress state due to a unit load.
See Remark 7.
SCALE/ SOL 101, 103: Scale factor applied to the load time history (Real, default=1.0). See
MAX Remark 7. Or the 1st peak level of a constant amplitude signal if TYPE=CONST (Real,
default=1.0).
SOL 108, 111: Acts as an additional scale factor on the input PSD. This applies only to
TYPE=PSD (Real, default=1.0).
Main Index
FTGLOAD 1877
Fatigue Cyclic Loading Variation
Describer Meaning
OFFSET/ SOL 101, 103: Offset applied to the load time history (Real, default=0.0). See Remark
MIN 7. Or the 2nd peak level of a constant amplitude signal if TYPE=CONST (Real, default
= -1.0). MAX can be < or > than MIN for TYPE=CONST.
SOL 108, 111: Offset of resultant stress PSD in stress units. This has the effect of adding
a mean stress effect to the random load response. This only applies to TYPE=STATIC
and if TID is blank, this is only a constant offset. With TID a variable offset plus this
constant offset is applied (Real, default = 1.0).
TYPE Flag indicating the type of load being defined. Values can be: blank, "DB", "DAC",
"RPC", "CONST", “PSD”, “SINE”, “NARROW” or "STATIC". Default is blank. See
Remarks 2. through 6.
CHNL SOL 101 and 103 only. Channel of referenced RPC file (TYPE=RPC). (Integer >0,
Default is blank). See Remark 12.
"UNITS" SOL 101 and 103 only. Flag indicating that a fatigue equivalent unit name is defined
for this loading. See Remarks 9. and 10.
EQUIV Number of equivalent units (Real>0.0, default=1.0). See Remarks 9. and 10.
EQNAME Equivalent name of this loading history. EQNAME can span across fields 4 through 9.
If not defined it will be called Repeats (Character). No spaces are allowed. See Remarks
9. and 10.
"DETLOAD" SOL 108 and 111 only. Flag indicating that deterministic load input is to follow for
TYPE=SINE or NARROW.
Fi Frequency of sine wave for TYPE=SINE or center frequency of narrow band frequency
block for TYPE=NARROW. (Real>0.0; no Default).
Gi Height of sine wave (Gi) in units of peak amplitude (FE stress units) for TYPE=SINE.
Hi Height of narrow band PSD block (Hi) in units of (stress)2/Hz for TYPE=NARROW.
(Real>=0.0; no Default).
Bi Width of narrow band frequency block. Only supplied for TYPE=NARROW.
(Real>=0.0; no Default).
"SWEEP" SOL 108 and 111 only. Flag indicating that sine sweep load input is to follow for
TYPE=SINE (not supported for NARROW).
F1/Fn F1/Fn Frequency of 1st and last sine waves for TYPE=SINE. (Real>0.0; no Default).
G1/H1 Height of 1st (G1) and last (Gn) sine waves in units of peak amplitude (FE stress units)
Gn/Hn for TYPE=SINE. (Real>=0.0; no Default).
SWTYPE The sweep type: Decibel (DB), Octave (OCT), or Linear (HZ). (Character;
Default = HZ)
SWNUM Number of sine/narrow bands to use (Integer>0 where N=SWNUM+1; Default = 50)
SWRATE Sweep rate per second in HZ (default), DB or OCT. (Real>0.0; No Default)
NSWEEP Number of sweep passes (Integer>0; No Default).
Main Index
1878 FTGLOAD
Fatigue Cyclic Loading Variation
Describer Meaning
FRFUNIT Units of loading used to create FRF - can be acceleration (A), velocity (V), displacement
(D), or force (F). Used for TYPE=SINE only. (Character; Default = A)
LDUNIT Units of loading used to define sweep - can be acceleration (A), velocity (V),
displacement (D), or force (F). Used for TYPE=SINE only. (Character; Default = A)
Remarks:
1. If a FATIGUE case control command invokes an ID that is present on both an FTGSEQ entry and
a FTGLOAD entry, the FTGSEQ request will be honored and the FTGLOAD entry will be ignored
unless it is referenced on a FTGEVNT entry.
2. For SOL 101 and 103, if the TYPE field is blank then TID references a TABLFTG or TABLED1
entry. For SOL 108 or 111, TYPE must be supplied.
3. For SOL 101 and 103, if TYPE=DB, DAC or RPC, then TID references a UDNAME ID. A
UDNAME entry must be supplied in this case to specify the file and path of the externally defined
load time variation. This file is expected to be in standard DAC file format or channel data in the
form of a RPC file. TYPE=DB is the same as TYPE=DAC. You cannot mix TYPE=RPC designations
with any other TYPEs within the same fatigue analysis (FATIGUE=FID). If RPC is used, all
FTGLOAD entries must use TYPE=RPC. The same RPC file must be referenced via UDNAME for
all FTGLOADs of the same event (FTGEVNT). For SOL 108 and 111, if TYPE=STATIC or if
TYPE=PSD with TIM2PSD entry active, the UDNAME references an external OP2 file or
RPC/CSV channel data file, respectively.
4. For SOL 101 and 103, if TYPE is STATIC, the TID field should be left blank as it will be ignored.
STATIC indicates that the stress state from the specified LCID is to act as a static offset with no load
time variation when performing the linear superposition, which will give every element a different
offset defined by the stress state at each element of the specified subcase, as opposed to simply
specifying the OFFSET field, which gives every element the same offset. If the "STATIC" flag is
specified, there must be at least two FTGLOAD entries defined and called out by a FTGEVNT entry,
one of which must be time varying (see Remark 7.). For SOL 108 and 111, if TYPE is STATIC, the
TID field must be supplied.
5. For SOL 101 and 103, if TYPE is CONST, the TID, LDM, and CHNL fields are ignored. The
MAX and MIN fields are used to define the maximum and minimum values of a constant amplitude
cycle. TYPE=CONST cannot be mixed with any other TYPE values for a given fatigue analysis
(FATIGUE=FID). All loading must be of TYPE=CONST. This is sometimes referred to as block
loading.
6. For modal analysis using SOL 103, the referenced load variation defines the modal participation
factors for the referenced mode.
7. For SOL 101 and 103, the LDM, SCALE, and OFFSET are used together in the following manner
to scale/modify the stress state in order to determine the resulting stress time variation:
ij,l
ij t = P t ------------- SCALE + OFFSET
LDM
Main Index
FTGLOAD 1879
Fatigue Cyclic Loading Variation
8. where ij t is the resulting stress tensor at time t, ij l is the stress tensor from the subcase or
mode defined by the LCID field, and P(t) is the y value of the load-time history at time t as defined
by the TID field. For multiple loads, the principle of linear superposition is used to combine all loads
for a single event. For SOL 108 and 111, LDM and SCALE act as a divisor and multiplier,
respectively, to the defined loading. OFFSET is only used for TYPE=STATIC and acts as an
additional constant offset over all entities.
9. If the "UNITS" flag is absent, the default fatigue equivalent unit is 1.0 Repeats of the stress time
history. If this FTGLOAD is referenced by a FTGEVNT, then the equivalent units on this entry are
ignored and those on the FTGSEQ entry take precedent. Only if a FTGLOAD is directly referenced
by a FATIGUE case control are the fatigue equivalent units used as defined on the FTGLOAD entry.
10. Example of using equivalent units: If one repeat of the defined time history is equivalent to 5 times
around a test track, the equivalent unit name, EQNAME, might be "laps," and the equivalent unit,
EQUIV, would be 5.0. Fatigue life will be reported in these units if defined, otherwise they are
reported as Repeats of the loading. Life output is reported in both Repeats and the fatigue equivalent
units, if defined.
11. All FTGLOAD entries referenced by a FTGEVNT should reference different SUBCASEs for SOL
101 (or modes for SOL 103) and must have time variations consisting of the same number of points.
12. CHNL is only used for TYPE=RPC for SOL 101 and 103. If supplied, the specified channel of the
referenced RPC file is used. If it is left blank, the next available channel sequentially from the last one
referenced will be used. For example, if there are three FTGLOAD entries for a specific event and
CHNL is blank for all three, the 1st one will use channel 1, the 2nd one will use channel 2 and the
3rd will used channel 3. If in this example the 1st specifies CHNL=11 and the others are blank, then
the channels used will be 11, 12, and 13. If the 1st is left blank and the 2nd references CHNL=12,
then the channels used will be 1, 12, and 13.
Main Index
1880 FTGPARM
Fatigue Parameters
FTGPARM Fatigue Parameters
Defines parameters for a fatigue analysis in time domain SOLs 101, 103, and 112 and in frequency domain
SOLs 108 and 111.
Format (SOLs 101, 103, 112):
1 2 3 4 5 6 7 8 9 10
FTGPARM ID TYPE FACTOR NTHRD LOGLVL LAYER
"STRESS" COMB CORR PLAST LOC INTERP RECOVER SRESOLVE
or
“STRAIN”
NANGLE
“RAINFLOW” RTYPE
"CERTNTY" SURV
"FOS" OPTION LIFE BACKACC MAXFAC MINFAC
“SPOTW” COMB CORR NANGLE SWLOC MIDDLE TORSION
“SEAMW” COMB CORR THICK LOCSM RESENT
“MULTI” MMTHD NONLWR NONUPR BIAXLWR BIAXMID BIAXUPR ZERO
GATE
“NAVG” MTHD OUTPUT NORMAL
Format (SOLs 108, 111):
1 2 3 4 5 6 7 8 9 10
FTGPARM ID TYPE LOGLVL LAYER
"STRESS" COMB CORR PLAST LOC RECOVER
"FOS" LIFE
“VIBFTG” ATYPE MAXSTR CLIPLVL MAXPEAK STRBINS MAXFREQ NCALC
Examples:
FTGPARM 22 EN
FTGPARM 22 SN
STRESS SGVON NONE NODA CUBIC
FTGPARM 22 SN
SEAMW FKM 0
FTGPARM 22 SN
SPOTW STNDRD SIMPLE 18 3 0 0
Main Index
FTGPARM 1881
Fatigue Parameters
Describer Meaning
ID Unique ID of the FTGPARM entry called out by a FATIGUE case control
(Integer > 0). See Remark 1.
TYPE SOL 101, 103, 112: Type of fatigue analysis: "SN" or "EN" (Character,
Default=SN).
SOL 108, 111: Type of fatigue analysis: "SN" or "EN" (Character,
Default=SN). This is used only when there is a conflict with the defined
material properties, i.e., both S-N and -N properties exist for the same
material MID. Otherwise it is ignored and the material properties define
the type of fatigue analysis to be performed..
FACTOR SOL 101, 103, 112 only. Global scale factor to be applied to combined
resultant stress output (Real>0.0, Default=1.0).
NTHRD SOL 101, 103, 112 only. Number of threads to use for parallel processing
for this fatigue analysis (Integer 0; Default = Blank). Blank denotes that
the number of threads used is based on SMP setting and the existence of
an SMP license. Zero (0) is used as a flag to tell the code to use all available
threads. Otherwise the number of threads designated is used if available.
An SMP license is only necessary to take advantage of multiple treads if left
blank.
LOGLVL SOL 101, 103, 112: Level of messaging sent to the log file (Integer 0,
Default = 0; 0=None, 1=Error, 2=Info, 3=Low, 4=Medium, 5=High).
Note that setting LOGLVL >0 can result in a significant performance
penalty and should be used for debugging purposes only and limited to the
entities of interest. LOGLVL=5 produces an HDF5 file that shows all
parameter settings. This file can be significantly large.
SOL 108, 111: Level of output to generate (Integer 0, Default = 0;
0=Standard, 1=Output all PSD responses, 2=Additionally output all
Rainflow data). Note that LOGLVL >0 can result in a significant
performance penalty and should be used for debugging purposes only and
limited to the entities of interest only. See Remark 15.
LAYER For shell elements, the output results layer to print to the f06 file. Values
can be 0=Worst, 1=Top(Z2), 2=Bottom(Z1). (Integer, Default = 0). This
is for printed output only. The analysis produces results for both layers,
which are always available through the MASTER/DBALL, Output2, or
other files for graphical postprocessors. See the FATIGUE case control
entry.
"STRESS" or Flag indicating that stress is used in the fatigue calculation. See Remark 2.
"STRAIN" SOL 101, 103, 112 only. Flag indicating that strain is used in the fatigue
calculation. Not valid for TYPE = SN. See Remark 2.
Main Index
1882 FTGPARM
Fatigue Parameters
Describer Meaning
COMB Stress/strain combination to use in the fatigue analysis. Acceptable values
are listed in Table 9-17 after the Remarks below (Character;
Defaul t= ABSMAXPR).
CORR Mean stress correction to use in the fatigue analysis. Acceptable values are
listed in Table 9-18 and Table 9-19 after the Remarks below (Character;
Default=None or MMPDS if MMPDS fatigue material model is specified
on the MATFTG entry).
PLAST SOL 101, 103, 112: Plasticity correction for TYPE = EN. Value can
currently only be "NEUBER" for Neuber method. (Character;
Default=NEUBER). See Remark 3.
SOL 108, 111: Only NEUBER correction is available.
LOC SOL 101, 103, 112: Location to report fatigue lives. Valid values are
"NODA”, “NODE”, or “ELEM” based on nodal averaged, element nodal,
or element centroid stresses or strains, respectively. (Character; Default =
NODA). See the RECOVER field and Remark 4. Also see the “NAVG”
field and parameters.
SOL 108, 111: Location to report fatigue lives. Valid values are “NODE”,
“NODA”, or “ELEM” based on element nodal, nodal averaged, or
element center stresses, respectively. (Character; Default = NODA). See
the RECOVER field and Remark 4.
INTERP SOL 101, 103, 112 only. Interpolation limit for multi-curve mean stress
correction method (Integer0; 0=Use Max Curve, 1=Extrapolate; Default
= 0).
RECOVER Stress recovery method to determine stresses/strains for the fatigue
calculation. Valid values are “SGAGE”, “CORNER”, “BILIN”, “CUBIC”
or "CENTER" (Character; Default = CORNER if LOC=NODA or
NODE; Default = CENTER if LOC=ELEM and any other setting is
ignored). These are the same values used for the STRESS (or STRAIN)
case control output request. See LOC field and Remark 4.
SRESOLVE SOL 101, 103, 112 only. Request for surface resolved, 2D stress state.
Used only for 3D solid elements. (Character YES or NO; Default = NO).
See Remark 5.
Main Index
FTGPARM 1883
Fatigue Parameters
Describer Meaning
NANGLE The number of calculation angles for 2D critical plane analysis
(COMB=CRITICAL) (1≤Integer≤360; Default = 36, i.e. every 10
degrees). Practical values are 360, 180, 120, 90, 72, 60, 45, 40, 36, 30, 24,
18, 15, 12, 10, 9, 8, 6, 5, 4 for every 1, 2, 3, 4, 5, 6, 8, 9, 10, 12, 15, 20,
24, 30, 36, 40, 45, 60, 72, 90 degrees, respectively. The more angles
computed, the more compute intensive the analysis will be. In actuality,
only half the angles are computed since the principals are the same 180
degrees opposite any computed angle.
“RAINFLOW” SOL 101, 103, 112 only. Flag indicating that parameters that follow
define rainflow cycle counting parameters for rainflow data reduction. See
Remark 6.
RTYPE Method of rainflow data reduction (Time History Compression). Value
can only be "LOAD" for load time history data reduction on each load
time history (Character; no default). Remark 6.
"CERTNTY" SOL 101, 103, 112 only. Flag indicating that the parameter that follows
defines the certainty of survival in fatigue analysis.
SURV Certainty of survival based on the scatter in the S-N or e-N curves. (0.1 ≤
Real ≤ 99.9; Default = 50). See Remark 7.
"FOS" SOL 101, 103, 112: Flag indicating that parameters that follow are used
in a factor of safety analysis. The presence of this flag triggers a factor of
safety analysis. See Remark 8. and 13. Not applicable to Spot Weld fatigue
analysis.
SOL 108, 111: Flag indicating that the total signal time duration desired
is to be specified for use in calculating margin of safety. Only the LIFE field
is required in this case and defaults to 1.0. A margin of safety is always
calculated.
OPTION Supported option is LIFE, requesting a life-based factor of safety analysis
or NONE. (Character; default = LIFE).
LIFE SOL 101, 103, 112: The targeted design life given in user defined life units
(such as laps, miles, etc.) as defined by “UNITS” line on FTGSEQ or
FTGLOAD entry, or Repeats of the cyclic loading if no “UNITS” line
exists (Real>0, no default).
SOL 108, 111: Total time duration required for margin of safety
calculation in time units specified by TUNIT field on FTGSEQ entry.
BACKACC SOL 101, 103, 112 only. The back calculation accuracy used to control
back calculation iterations that determine the scale factor on the applied
stress level to achieve the target design life. Defined as a percentage error
on the target design life. (0.01 Real 100.0, Default = 1.0).
Main Index
1884 FTGPARM
Fatigue Parameters
Describer Meaning
MAXFAC SOL 101, 103, 112 only. The maximum safety factor to calculate and
report. When this threshold is exceeded, the analysis will go on to the next
element and report the maximum for the exceeded element (2.0 Real
5.e6, Default = 5.0).
MINFAC SOL 101, 103, 112 only. The minimum safety factor to calculate and
report. If the result is below this threshold, the analysis will report
MINFAC as the safety factor for this element and go on to process the next
element. (0.0Real0.5, Default = 0.2).
"SPOTW" SOL 101, 103, 112 only. Flag indicating that parameters for fatigue
analysis of spot welds are to follow. See Remark 9.
COMB Stress combination to use in the fatigue analysis. Acceptable values are
listed in Table 9-17 after the Remarks below (Character;
Default=STNDRD, which is basically a critical plane analysis).
CORR Mean stress correction to use in the fatigue analysis of spot welds. Only
NONE, FKM, or SIMPLE are valid for fatigue analysis of spot welds. See
Table 9-18 and Table 9-19 below. (Character; Default = NONE).
NANGLE The number of calculation angles in 360 degrees around the spot weld.
(10Integer360; Default = 18, i.e., every 20 degrees)
SWLOC Location on the spot welds to report fatigue life. Zero (0) reports worst
case angle and location (top/bottom sheet or nugget); one (1) reports worst
case angle for each location; two (2) reports worst case location for each
angle; three (3) reports all locations and angles. (Integer 0, 1, 2, or 3,
Default=0).
MIDDLE Whether to process middle sheets if there are more than two sheets in the
weld. (Integer 0 or 1, Default = 1- process middle sheets). See Remark 11.
TORSION Whether to calculate torsion in the spot weld. (Integer 0 or 1, Default = 0
-do not calculate torsion). See Remark 12.
"SEAMW" SOL 101, 103, 112 only. Flag indicating that parameters for fatigue
analysis of seam welds are to follow. See Remark 9.
COMB Stress/strain combination to use in the fatigue analysis of seam welds. Only
ABSMAXPR and CRITICAL are supported. See Table 9-17 below.
(Character; Default = ABSMAXPR).
CORR Mean stress correction to use in the fatigue analysis of seam welds. Only
NONE or FKM are valid for fatigue analysis of seam welds. See Table 9-18
and Table 9-19 below. (Character; Default=NONE).
THICK Thickness correction to be applied. (Integer 0 or 1; Default =0 - no
correction)
Main Index
FTGPARM 1885
Fatigue Parameters
Describer Meaning
LOCSM Location on seam weld to report life. Valid values are "NODE”,
“SGAGE”, “CORNER”, “BILIN”, or “CUBIC” (Character; Default =
NODE). If “STRESS” line is also include, LOCSM must be the same as
LOC. LOC=ELEM is not valid for fatigue analysis of seam welds and
cannot be mixed with LOC = NODE. See Remark 4.
RESENT Result entity type used in the fatigue analysis of seam welds; only STRESS
is currently supported. (Character; Default = STRESS).
"MULTI" SOL 101, 103, 112 only. Flag indicating that parameters for
biaxial/multiaxial assessment are to follow. See Remark 10. and 13.
MMTHD Can be set to the following:
NONE = No multiaxial assessment is done.
SIMPLE = Calculates simple biaxiality ratios only.
STANDard =Standard method of assessment, which merely
returns the results of the assessment.
AUTO = Performs the standard method, but then may recalculate
fatigue damage depending on the results of the assessment.
Currently valid for S-N analysis only and only results of individual
events are meaningful.
"NAVG" SOL 101, 103, 112 only. Flag indicating that parameters for nodal (grid
point) stress (or strain) averaging are to follow. The LOC field must be set
to NODA, otherwise this line is ignored. These parameters are the same as
those specified in the SURFACE and VOLUME case control for
requesting grid point stresses/strains and the user is referred to the
OUTPUT(POST) section for more details. All defaults are used if this line
is omitted. See Remark 14.
MTHD Method to calculate average grid point stresses/strains:
TOPO = Topological method (default)
GEOM = Geometric method.
OUTPUT Coordinate system in which to translate stresses/strains before averaging:
-1 : Specifies the element coordinate system for output
0 : Specifies the basic coordinate system for output (default)
CID : Specifies the coordinate system defined on a CORDij bulk
data entry for output
The X-axis of this system is used to define the X stress direction. For shell
elements the X-axis of the specified coordinate system is projected onto the
surface or, that is, the resulting averaged stresses are a projection onto the
surface.
Main Index
1886 FTGPARM
Fatigue Parameters
Describer Meaning
NORMAL For shell elements defining a surface, this specifies the method to define the
surface normal. For solid elements defining a volume, this specifies the
method to define the stress Z-axis. Indirectly this also sets the reference
direction for positive fiber and shear stress output, but has no effect when
OUTPUT=-1. Can be set to R (default), X1, X2, or X3.
M Specifies the reverse of the direction given by R, X1, X2, or X3 and must
be entered as MR, MX1, MX2, or MX3 with no space between the M and
the following letter. R Specifies the radius vector from the origin of
reference coordinate system to the grid point.
The Y stress direction is the cross product of the Z and X stress directions
defined by the NORMAL and the X-axis of the OUTPUT coordinate
system.
“VIBFTG” SOL 108, 111 only. Flag indicating that vibration fatigue parameters
follow. The line is optional and defaults are used if not present.
ATYPE Analysis method to use to generate the PDF of rainflow ranges: DIRLIK,
NARROW, STEIN, SINES. (Character; default = DIRLIK)
MAXSTR Maximum stress to use as a function of the number of RMS stress levels to
determine maximum stress in the rainflow cycle count. (Real>0.0;
Default=10.0).
CLIPLVL Value of stress where all stresses are "clipped" (kept at that level) when
doing fatigue life calculation. Real>0.0; (Default CLIPLVL=MAXSTR).
CLIPLVL=6 means +/- 3*RMS amplitudes or 6*RMS in terms of range.
MAXPEAK Used to calculate an estimation of maximum and minimum stress (number
of RMS levels) in the random response. It is not used in any way to
calculate damage or life. This is also used when the maximum elastic-
plastic peak strain is calculated. Where a mean load is included the peak
stress is calculated as the mean_stress + MAXPEAK*RMS and the
minimum stress is calculated as the mean_stress - MAXPEAK*RMS. This
is similar to the time domain approach where the maximum and minimum
stress are retained from the rainflow cycle count. (Real>0;
Default=CLIPLVL/2 or, if CLIPLVL not defined, MAXSTR/2).
STRBINS Number of bins to generate in rainflow cycle count. Default = 1280 for
ATYPE=SINES otherwise 32. Not recommended to use anything over
5000.
Main Index
FTGPARM 1887
Fatigue Parameters
Describer Meaning
MAXFREQ Percentage of frequency content retained as a function of the first spectral
moment m0 of the PSD defining the maximum frequency used to
integrate the spectral moments for m1, m2, and m4. 0≤Real≤100.0;
Default=99.9). 100% is not a recommended setting as it can cause
numerical instability related to the calculation of the 4th spectral moment.
NCALC Alternative options for the way "N" (life to failure) is calculated for a given
stress bin. Valid values are MID, UPR, or AVG for middle, upper or
average. (Character; Default=AVG). See Table 9-20.
Remarks:
1. FTGPARM bulk data is ignored if not selected by a FATIGUE case control entry. If a FTGPARM
entry is not defined, default properties are used for the requested fatigue analysis.
2. SOL 101, 103, 112: For total life or stress-life (TYPE=SN), only STRESS results can be used. For
crack initiation or strain-life (TYPE=EN), the fatigue analyzer may use either STRESS or STRAIN
results from the finite element analysis. This selection should make no difference to the final results
of a crack initiation calculation, as strains will always be calculated. The exception is when shell results
are used. In this case, STRESS should be selected because only 2D results are available and the
absence of the out-of-plane strains will cause incorrect calculation of combined parameters. It is an
error to have both STRESS and STRAIN lines. If both are missing, then STRESS will be assumed
with its default values.
3. SOL 101, 103, 112: PLAST can only be set to NEUBER. Please note that NEUBER can be used
universally for uniaxial stress states. PLAST is only valid for TYPE=EN.
4. If LOC=ELEM (element center), fatigue lives are calculated based on stresses/strains at element
centroids (not recommended for anything but shell or 2D solid elements (plane stress/strain and
axisymmetric) and the RECOVER field is ignored or automatically set to CENTER.
If LOC=NODE, the fatigue lives are calculated from the stresses/strains at the element nodes,
resulting in multiple damage values per node. Note that for LOC=NODE, the RECOVER field can
be set to SGAGE, BILIN, CUBIC, or CORNER to control which stresses are used in the fatigue
analysis for element nodal stresses and correspond to the same options as on the STRESS case
control.
If LOC is set to NODA, the same RECOVER options as LOC=NODE apply, however:
SOL 101, 103, 112: With LOC=NODA, fatigue lives are based on stresses/strains from nodal
averaged (grid point) stresses, resulting in a single damage value at each node as opposed to using
LOC=NODE where the fatigue lives are calculated from the stresses/strains at the element nodes,
resulting in multiple damage values per node. The grid point stresses are generated using Nastran’s
GPSTRESS output request internally (it is not required to include the GPSTRESS case control
unless you wish to view the grid point stress also). See the NAVG line settings also on how to
control grid point stress calculations.
Main Index
1888 FTGPARM
Fatigue Parameters
SOL 108, 111: With LOC=NODA, after the nodal transfer function (TF) stresses for each element
contribution are converted to the requested stress combination (e.g. COMB=SGVON), the stresses
are summed and averaged at each node. This is done at every frequency to give a single TF of stress
at each node. Thus a single damage and fatigue life per node is reported as opposed to slightly
different values when LOC=NODE. Please note that the coordinate system in which the elements
are defined should be consistent (the same). Otherwise the nodal averaging will not be done using
consistent coordinate systems. Thus, for solid element, setting CORDM on the PSOLID entry to
the Basic coordinate system or a specified CID is required and setting CID=-1 or -2 (element
systems) is not recommended. For shell elements, MCID should be set on the respective element
entry.
This parameter cannot be changed on a RESTART since it would require a different set of
stress/strain data, which is not allowed on a RESTART for a pure fatigue analysis.
LOC=NODE generally gives more conservative answers than LOC=NODA since no averaging of
the stresses/strains is done from the contributions of the surrounding elements.
5. SOL 101, 103, 112: SRESOLVE is applicable for all three values of LOC, i.e.: LOC = ELEM,
NODE or NODA. SRESOLVE is an option to evaluate surface stresses instead of volume stresses.
When surface resolved stresses are requested from 3D solid elements, a thin layer of 2D shell elements
is internally created encompassing the volume of the elements defined on the FTGDEF entry from
which the 2D stress state is then determined. This parameter is necessary if a multiaxial assessment of
a model made of 3D elements is necessary, otherwise 3D elements are ignored during a multiaxial
assessment. Fatigue life and multiaxial statistics are only reported for these newly defined 2D elements
(or reduced set of nodes) on the surface of the volume (free surface). Interior nodes are not included
in the fatigue calculation. The internal element IDs generated by this option can be controlled by
using MSC Nastran SYSTEM cell 183 (Default is set to 200000000).
Element sets must be the same for all FATIGUE case control IDs that request surface resolved
stresses. Otherwise a fatal condition is flagged and the analysis stops.
6. This RAINFLOW flag is used only to speed up the analysis by performing peak-valley-extraction. For
each event the input time history peaks and valleys are retained as well as corresponding points from
time histories of other events participating in the loading sequence. All other loading points are
eliminated, thus reducing the input time history data processing during the rainflow counting
procedure. RTYPE must be set to LOAD and is currently the only valid option.
7. Certainty of survival is based on scatter in the S-N or -N curves. It is used to modify the curves
according to the standard error parameters ( SE n ) defined in the MATFTG material entry. A higher
reliability level requires a larger certainty of survival.
8. SOL 101, 103, 112: This FOS option will calculate a type of safety factor for over design analysis to
be performed. This analysis is in addition to the normal fatigue life/damage output and must be
requested by the presence of this FOS flag and its parameters. This analysis method can be very useful
for those components which predict infinite life, providing a measure of the risk of fatigue failure.
The results of this analysis are factors by which the stress would have to be scaled to attain the specified
Main Index
FTGPARM 1889
Fatigue Parameters
design life. A value of one suggests that the specified life will be exactly attained whereas a factor less
than one means the desired life will not be attained. Factors greater than one are, therefore, most
desirable. FOS results are only reported for the sum of all events when multiple events are defined.
Resulting fatigue life results reported are not affected by the presence of the FOS line.
SOL 108, 111: This FOS option is actually a margin of safety (MOS) calculation, which requires
only the desired or required duration of entire loading sequence in time units. By default this is set
to 1.0 and the time units are those defined by the TUNIT field on the FTGSEQ entry.
9. For fatigue analysis of spot and seam welds, besides the “SPOTW” and “SEAMW” lines themselves,
“CERTNTY”, and “FOS” are also applicable. “MULTI” is applicable to seam weld, but not spot
welds. All others are ignored. TYPE field is ignored as an SN analysis is forced for fatigue of spot and
seam welds.
10. Biaxial/Multiaxial assessment can be requested for all but fatigue analysis of spot welds and is ignored
by SOL 200 optimization runs. These assessments require a 2D state of stress. For this reason only
shell elements are supported with this feature. See the SRESOLVE field if 3D elements are involved.
11. The Rupp method for spot weld life prediction has not been validated for the prediction of fatigue
damage occurring at the middle sheets for spot welds joining more than two sheets. It should also be
noted that such failures are relatively rare, difficult to reproduce in the laboratory, and difficult to
detect in practice. Scrutinize middle sheet results carefully as they may give a false positive failure
prediction.
12. Setting the TORSION option enables fatigue calculations to be made based on the shear stress
around the periphery of the spot weld in each sheet due to the torsional load on the spot weld. Please
note the following:
a. This option requires that suitable S-N curves be defined for the torsion case, which may mean a
separate run for torsion vs for a non-torsion run.
b. Do not use this option unless your modeling strategy can generate realistic torsional loads in the
spot welds. For example, this is not true of the simple CBAR modeling approach.
c. The mean stress correction is applied a little differently, because the sign of a mean shear stress
cannot influence the fatigue damage. For this reason, the ABSOLUTE value (i.e., the magnitude)
of the mean stress is used when applying any mean stress correction for the torsion case.
d. The calculation is a completely separate operation—there is no combination of the torsional
stresses with the other stresses on the spot weld.
e. This option has had little validation, and no suitable S-N curves are provided with the software.
However, it has been successfully used in practice, using S-N curves deduced from practical
experience with car body structures, and has proved a useful tool for predicting premature failure
in the small number of spot welds that may experience significant torsional loads.
f. The results of the torsional fatigue calculation are identified in the results by being associated with
an angle of -1
13. Factor of Safety (FOS) analysis is only compatible with the MMTHD=SIMPLE if doing a multi-
axial/biaxial (MULTI) assessment in the same run. A fatal error is issued if also used in conjunction
with SPOTW (fatigue analysis of spot welds).
Main Index
1890 FTGPARM
Fatigue Parameters
14. When LOC=NODA for requesting nodal average stresses, the grid point stresses generator is used to
determine the nodal averaging. A limited set of controls is provided on the NAVG line to control how
the averaging method. Internally, SURFACE and/or VOLUME definitions are created for the grid
point stress request, just as if the GPSTRESS case control, with its associated OUTPUT(POST)
commands, were given. However, only one SURFACE and/or VOLUME is determined based on the
elements defined on the FTGDEF entry for requesting fatigue analysis. The user should be aware of
possible stress discontinuities that can result from this.
15. By default the response PSD at the most critical location is output using LOGLVL=0 via a
<jobname>PSD.csv file. If LOGLVL=1, response PSDs for all requested locations are output to
that same file. Also a <jobname>RCC.csv file is produced with limited data showing the
summation of damages from the rainflow cycle count. If LOGLVL=2, both files are created and in
the latter, addition the stress and damage BIN data for each event is included. Be aware that this can
create a lot of data, resulting in huge output files, and can severely degrade performance. Please use
this option with care and limit the output to only the critical elements of interest.
Main Index
FTGPARM 1891
Fatigue Parameters
Table 9-17 Allowable Values for the COMB Field
Stress/Strain SOL 101, 103, 112* SOL 108, 111 Valid
Combination Valid for TYPE for TYPE Meaning
ABSMAXPR SN (+SeamWeld) SN Absolute Maximum Principal (default)†
EN EN
SGVON SN SN Signed von Mises Stress (recommended
EN EN for SOL 108, 111 but not default)
SGMAXSHR SN Signed Maximum Shear
EN
CRITICAL SN (+Seam Weld), Critical Plane Analysis - every 10 degrees
EN by default unless NANGLE is specified
otherwise for standard SN/EN analysis
only- Not valid for 3D solid or CSHEAR
elements - element must have an in-plane
stress state.
STNDRD SN This is basically a critical plane analysis
(Spot Weld only) with calculations being done at
NANGLEs around the circumference of
the spot weld.
COMPX SN Individual stress components
COMPY EN
COMPZ
COMPXY
COMPYZ
COMPZX
* In time domain, six multiaxial components of the stress tensor are resolved into one uniaxial, com-
bined value for fatigue calculations at each entity per time step since damage models are based on
uniaxial theories. For S-N analysis, the signed von Mises (SGVON) will be smaller than the Abso-
lute Maximum Principal (ABSMAXPR) when there is positive biaxiality and hence this selection
would be less conservative. (Note also that some BS weld classes require shear stress to be used.) The
signed parameters use the sign of the absolute maximum principal value for conservative fatigue life
estimates. It is not recommended to use non-signed values, thus they are not supported.
† In frequency domain, this is a Maximum Principal calculation using accurate phase scanning.
Main Index
1892 FTGPARM
Fatigue Parameters
Table 9-18 Allowable Values for the CORR Field
Mean Stress SOL 101, 103, 112 SOL 108, 111
Correction Valid for TYPE Valid for TYPE Meaning
NONE SN (+Spot/Seam Weld) SN No mean stress correction (default)
EN EN
GOODMAN SN SN Goodman mean stress correction
EN
GERBER SN SN Gerber mean stress correction
EN
GDMANT SN SN Tension only Goodman mean stress
EN correction
GRBERT SN SN Tension only Gerber mean stress
EN correction
FKM SN (+Spot/Seam Weld) FKM mean stress correction method.
Uses M1, M2, M3, M4 slopes as defined
in MATFTG entry. See remarks in
MATFTG entry.
SIMPLE SN (Spot Weld only) Modified FKM mean stress correction
method where M1=M2=M3=M4=-MSS
as defined in the MATFTG entry.
INTERP SN Interpolation method used with multiple
SN curves only. TYPE field of MATFTG
entry must be set to MEAN, RRATIO,
or LIFE. Requires that there be multiple
curves defined, one at R=-1 for
TYPE=RRATIO, or zero (0) mean stress
for TYPE=MEAN.
SWT EN SN Smith-Watson-Topper mean stress
EN correction
MORROW EN EN Morrow mean stress correction
WALKER EN Walker mean stress correction
MMPDS SN* SN Walker mean stress correction built into
EN the MMPDS-01 material curves
*If MMPDS S-N material model is specified and referenced on a MATFTG, then the MMPDS
mean stress correction is automatically applied regardless of the value of the CORR field.
Main Index
FTGPARM 1893
Fatigue Parameters
Table 9-19 Allowable S-N vs. Mean Stress Correction Methods for SOLs 101, 103, 112
S-N Method
Mean Stress
Correction Standard Multi Mean Curve Multi R-Ratio Curve Haigh
NONE YES YES* YES† NO
GOODMAN YES YES* YES† NO
GERBER YES YES* YES† NO
GDMANT YES YES* YES† NO
GRBERT YES YES* YES† NO
FKM YES YES* YES† NO
SIMPLE‡ YES NO NO NO
INTERP NO YES YES YES
MMPDS MMPDS** NO NO NO
* Allowed but a curve at zero mean stress must be present.
†Allowed but a curve at R = -1 must be present.
‡Spot Welds only.
**MMPDS mean stress correction is only applicable when using MMPDS S-N material model and
automatically applied regardless of the mean stress correction (CORR) setting.
Table 9-20 Alternative NCALC options to calculate “N” (cycles to failure)
NCALC option Meaning
AVG Calculation of “N” is done by adding up all the values of N within the BIN
and then dividing through by the number of N values used. In this context the
average value of N is calculated over the BIN.
MID “N” is extracted at the mid (stress) point of the BIN.
UPPER “N” is extracted at the upper (stress) point of the BIN.
Main Index
1894 FTGSEQ
Fatigue Load Sequence
FTGSEQ Fatigue Load Sequence
Defines the loading sequence for pseudo-static fatigue analysis using SOL 101 or modal transient fatigue
analysis using SOL 103 or SOL 112 or vibration fatigue using SOL 108 or SOL 111.
Format (SOL 101, 103, 112):
1 2 3 4 5 6 7 8 9 10
FTGSEQ ID EVNTOUT METHOD
FID1 N1 FID2 N2 FID3 N3 FID4 N4
FID5 N5 ... ... ... ... ... ...
-etc.-
"UNITS" EQUIV EQNAME
Format (SOL 108, 111):
1 2 3 4 5 6 7 8 9 10
FTGSEQ ID EVNTOUT TUNIT LDM
FID1 N1 FID2 N2 FID3 N3 FID4 N4
FID5 N5 ... ... ... ... ... ...
-etc.-
"UNITS" EQUIV EQNAME
Examples:
FTGSEQ 1
6 15
Describer Meaning
ID Unique ID with respect to all other FTGSEQ and FTGEVNT entries called out by a
FATIGUE case control. (Integer>0) See Remark 1.
EVNTOUT Flag for requesting fatigue output for each event individually. (Integer; 0=no or 1=yes;
Default = 0). See Remark 7. For SOL 108 and 111, this also controls the written output
request for spectral statistics (m0, m1, m2, m4, etc.).
METHOD SOL 101, 103, 112 only. Event processing method. 0=independent, 1=Combined Full, 2=
Combined Fast (Integer; Default = 0). This entry is only honored from the controlling
FTGSEQ entry when called out by the FATIGUE case control. Otherwise it is ignored. See
Remark 2. Currently only METHOD=0 is supported.
TUNIT SOL 108, 111 only. Time units of Ni values. SECS, MINS, HRS, DAYS, WKS, MTHS,
YRS for seconds, minutes, hours, days, weeks, months, or years, respectively (Character;
Default=SECS).
Main Index
FTGSEQ 1895
Fatigue Load Sequence
Describer Meaning
LDM SOL 108, 111 only. FE load magnitude used to create transfer function. Used to normalize
the transfer function stresses (Real, Default=1.0).
FIDi SOLs 101, 103: ID of a FTGEVNT or another FTGSEQ entry for pseudo-static
fatigue analysis using SOL 101 or a modal analysis using SOL 103 (Integer > 0).
See Remark 3. and 4.
SOL 112: A subcase ID that represents the loading event or another FTGSEQ
entry for modal transient fatigue analysis using SOL 112. (Integer > 0). See
Remark 3. and 4.
SOL 108, 111: ID of a FTGEVNT entry for random vibration fatigue using
SOLs 108 or 111. Nested FTQSEQs are not allowed.
Ni SOLs 101, 103, 112: Number of repeats of this loading sequence or event
(Real>0.0, Default=1.0). Ignored if only one event is defined. For METHOD
equal 1 and 2, Ni must be a whole number, i.e., 1.0, 2.0, 3.0, etc. In other words,
fractions of events are not allowed. Fractional events are also not allowed for any
METHOD if the corresponding FID references a FTGSEQ entry. See Remark 3.
and 4.
SOL 108, 111: Duration of each event in TUNIT units. This value is not used
for random loading only. These values are also not needed and overwritten if
SWRATE/NSWEEP are provided on a FTGLOAD entry of TYPE= SINE (sine
sweep). (Real>0.0; Default=1.0).
"UNITS" Flag indicating that a fatigue equivalent unit name is applied to this loading. See Remark
5. and 6.
EQUIV Number of equivalent units. (Real>0.0; Default=1.0 ). See Remark 5. and 6.
EQNAME Equivalent name of this loading event. EQNAME can span across fields 4 through 9. If
not defined it will be called Repeats (Character). No spaces are allowed. See Remark 5. and
6.
Remarks:
1. FTGSEQ bulk data are called out by FATIGUE case control.
2. Processing of events can be done by determining the damage due to each event independently
(default) and then summing the damage due to all events. Or the events can be concatenated and
damage determined after rainflow cycle counting over all events. The advantage of the independent
method over the combined methods is computational expense versus accuracy. The combined
method will close all cycles, whereas the individual method may miss a large damaging cycle if the
cycle begins in one event and ends or closes in a subsequent event. The combined fast method
performs a rainflow count data reduction to speed up the analysis and determine the most critical
locations first and then redoes a full analysis on the critical locations. The concatenated methods are
currently not supported in this version.
Main Index
1896 FTGSEQ
Fatigue Load Sequence
3. Once a FTGSEQ bulk data entry is referenced in an FIDi field, it can't be referenced again in any
other FTGSEQ entries (within its own associations - the same fatigue analysis) to avoid infinite
loops. And if it is referenced by the FATIGUE case control, it cannot appear in any FIDi field of the
FTGSEQ bulk data.
4. Different FTGEVNTs can be set up and the user can construct each sequence by specifying how
many times to repeat each event in a sequence. One sequence could then be referenced in another
sequence to tell the new sequence how many times to repeat that sequence. As an example, assume
there are three events an automobile is subjected to: cobble stones, pot holes, speed bumps. One
sequence might be five (5) "cobble stones," six (6) "potholes" and three (3) "speed bumps." This
sequence may be called "torture track." Also define two more events called "cornering left" and
"cornering right." A load sequence of ten (10) "cornering left" and ten (10) "cornering right" might
be called "country road." Now with a nested FTGSEQ you can put these together any way you
want. So one fatigue analysis might use a sequence of only "country road," another of only "torture
track" and another of a combined six (6) "torture tracks," five (5) "country roads," followed by one
(1) more "torture track" and one (1) more "country road" This would result in 3 fatigue analyses as
shown in Table 9-21 below.
5. If the "UNITS" flag is absent, the default fatigue equivalent unit is 1.0 Repeats of the resulting stress
time history sequence. Equivalent units specified on FTGLOAD entries are ignored when FTGSEQ
entries are used
6. Example of using equivalent units: If one repeat (or total duration) of the sequence is equivalent to
five (5) times around a test track, the equivalent unit name, EQNAM, might be "laps," and the
equivalent unit, EQUIV, would be five (5). Fatigue life will be reported in these units if defined,
otherwise they are reported as repeats of the loading sequence. Life output is reported in both Repeats
and the fatigue equivalent units, if defined.
7. For SOL 200 only EVNTOUT=0 is supported. Also some additional output file formats are not
supported if EVNTOUT>0. See the FATIGUE case control entry forSTROUT=4 limitations. If a
factor of safety (FOS line present on FTGPARM entry), safety factors are only reported for the sum of
all events.
8. SOL 108, 111: For vibration fatigue a FTGSEQ cannot reference both an event with single input
random loading and multiple input random loading.
Table 9-21 Example of nested FTGSEQ entries
SET 1=22,33,44
FATIGUE=1
BEGIN BULK
$
FTGSEQ,22 $<-- 1 country road only
,2
FTGSEQ,33 $<-- 1 torture track only
,3
$combined
FTGSEQ,44 $<-- 6 torture track, 5 country road, + 1 of each
,3,6.0,2,5.0,3,1.0,2,1.0
$country road:
FTGSEQ,2
,8,10.0,9,10.0 $<-- 10 cornering left + 10 cornering right
$torture track:
Main Index
FTGSEQ 1897
Fatigue Load Sequence
FTGSEQ 3
,5,5.0,6,6.0,7,3.0 $<-- 5 cobble stones, 6 potholes, 3 speed bumps
$
FTGEVNT,5... $cobble stones
FTGEVNT,6... $potholes
FTGEVNT,7... $speed bumps
FTGEVNT,8... $cornering right
FTGEVNT,9... $cornering left
Main Index
1898 GBAG
Gas-Bag Pressure Definition
GBAG Gas-Bag Pressure Definition
Defines the pressure within an enclosed volume. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
GBAG GID BSID TRIGGER TRIGGERV PORID INFID HTRID INTID
CPGAS GPGASV RGAS PENV REVERSE CHECK PINIT
TINIT TENV
Examples:
GBAG 101 37 11 12
CONSTANT 1000. 297.0 101325. ON ON
293.0
Describer Meaning
GID Unique gas-bag number. I>0 Required
BSID Identification number of a BSURF, BCBOX, BCPROP, I>0 Required
BCMATL, or BCSEG entry defining the surface of the gas-
bag.
TRIGGER The time-dependent parameters are offset in time. Character TIME
TIME The offset is defined at TRIGGERV.
TRIGGERV The value of the offset in time. Real Required
PORID Number of a set of LEAKAGE entries, that defines the Integer > 0 No porosity
porosity (permeability) and holes for the gas-bag surface
and/or subsurfaces.
INFID Number of a set of ABINFL entries, that defines the one or Integer > 0 No inflators
more inflators on subsurface(s) of the GBAG surface.
HTRID Number of a set of HEATLOS entries, that defines the heat I>0 No heat
transfer definitions for the gas-bag surface and/or transfer
subsurfaces.
INTID ID of an INITGAS entry specifying the initial gas I>0 No initial gas
composition for this GBAG. composition
Main Index
GBAG 1899
Gas-Bag Pressure Definition
Describer Meaning
CPGAS The variation of the specific heat constant at constant Character CONSTANT
pressure.
CONSTANT The specific heat is constant and specified in
CPGASV.
CPGASV The specific heat of the gas. Real Required
RGAS Gas constant of the inflowing gas. Real Required
PENV Environmental pressure surrounding the gas bag. Real Required
REVERSE Normal auto-reverse switch. C ON
ON The normals of the surface are automatically reversed
if necessary so that they point in the same direction and
provide a positive volume.
OFF The normals are not automatically reversed.
CHECK Normal checking switch. C ON
ON The normals of the surface are checked to see if they all
point in the same direction and provide a positive volume.
OFF The normals are not checked.
If REVERSE is set to ON, CHECK is automatically set to
ON.
PINIT Initial pressure inside the gas bag. Real PENV
TINIT Initial temperature inside the gas bag. Real Required.
See Remark 4.
TENV Environmental Temperature. Real > 0 TINIT
Remarks:
1. The BSURF entry referenced by the BSID field must form a closed volume.
2. The pressure in the gas bag is applied to all the faces of the outer boundary.
3. TINIT is the temperature of the gas inside the volume at time = 0. At time = 0, the mass of the gas
inside the gas bag is calculated as
P init V
m = ---------------
RT init
where, P init the initial pressure, V the volume, R the gas constant, and T init the initial gas
temperature.
Main Index
1900 GBAG
Gas-Bag Pressure Definition
4. The flow through exhaust openings, leakage areas and user-specified outflow rate is accumulated. The
volumetric porosity contributes to the outflow of gas as
p
m· out = Q = ----------- Q
RT
where
Q = volumetric flow rate
r = density inside the bag
p = pressure inside the bag
R = gas constant
T = temperature inside the bag
m· out = mass outflow rate
The value of Q can be specified as a constant, as a function of the pressure difference, or as a function
of time. Negative values for the volumetric flow rate are not allowed, since this would mean inflow of
outside air.
5. A mixture of BSURF, BCBOX, BCPROP, BCMATL or BCSEG with the same BSID is allowed.
However multiple BSID of the same type is not allowed. When using this option, special care must
be taken to assure the same element is not part of multiple BSID definitions.
Main Index
GBAGCOU 1901
General Coupling to Gas-Bag Switch
GBAGCOU General Coupling to Gas-Bag Switch
Defines a switch from full gas dynamics to uniform pressure formulation. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
GBAGCOU ID CID GID TSTART PERCENT
Examples:
GBAGCOU 1 100 101 0.0 5
Describer Meaning
ID Unique number of a GBAGCOU entry. I>0 Required
CID Number of a COUPLE entry. I>0 Required
GID Number of a GBAG entry. I>0 0.0
TSTART Time after which the coupling algorithm checks if a switch Real > 0 0.0
to the uniform pressure method is valid. It is valid when the
following is true:
Pmax + Paverage Paverage – Pmin PERCENT
Max ---------------------------------------------- --------------------------------------------- --------------------------
Paverage Paverage 100
where
Pmax = maximum Eulerian pressure exerted on the
SURFACE
Pmin = minimum Eulerian pressure exerted on the
SURFACE
Paverage = average Eulerian pressure exerted on the
SURFACE
PERCENT Value used in validity check as defined previously. R > 0. 0.0
Remarks:
1. The BSID referenced by the COUPLE entry CID and by the GBAG entry GID must be the same.
2. All Eulerian and general coupling calculations are deactivated after transition from gas dynamics to
uniform pressure.
Main Index
1902 GENEL
General Element
GENEL General Element
Defines a general element.
Format:
1 2 3 4 5 6 7 8 9 10
GENEL EID UI1 CI1 UI2 CI2 UI3 CI3
UI4 CI4 UI5 CI5 -etc.-
UIm -- The last item in the UI list will appear in one of fields 2, 4, 6, or 8.
“UD” UD1 CD1 UD2 CD2 -etc.-
UDn -- The last item in the UD list will appear in one of fields 2, 4, 6, or 8.
“K” or “Z” KZ11 KZ21 KZ31 -etc.- KZ22 KZ32
-etc.- KZ33 KZ43 -etc.-
KZmm -- The last item in the K or Z matrix will appear in one of fields 2 through 9.
“S” S11 S12 -etc.- S21 -etc.-
Smn -- The last item in the S matrix will appear in one of fields 2 through 9.
Example:
GENEL 629 1 1 13 4 42 0
24 2
UD 6 2 33 0
Z 1.0 2.0 3.0 4.0 5.0 6.0 7.0
8.0 9.0 10.0
S 1.5 2.5 3.5 4.5 5.5 6.5 7.5
8.5
Describer Meaning
EID Unique element identification number. (Integer > 0)
Uli, Cli Identification numbers of degrees-of-freedom in the UI or UD list, in sequence
UDj, CDj corresponding to the [K], [Z], and [S] matrices. UIi and UDi are grid point numbers,
and CIi and CDj are the component numbers. If a scalar point is given, the
component number is zero. (Integer > 0)
KZij Values of the [K] or [Z] matrix ordered by columns from the diagonal, according to the
UI list. (Real)
Main Index
GENEL 1903
General Element
Describer Meaning
Sij Values of the [S] matrix ordered by rows according to the UD list. (Real)
“UD”, “K”, Character strings that indicate the start of data belonging to the UD list or the [K], [Z],
“Z”, and or [S] matrices.
“S”
Remarks:
1. The stiffness approach:
fi K – KS u i
= T T
fd – S K S KS u d
The flexibility approach:
ui Z S fi
= T
fd –S O ud
where
T
u i = u i1 u i2 u im
T
u d = u d1 u d2 u dn
KZ =
KZ11
KZ21 KZ22
T
K or Z = KZ31 KZ32 and KZ = KZ
KZ m1 KZ mm
S11 S 1n
S21
S = S31
S m1 S mn
Main Index
1904 GENEL
General Element
The required input is the u i list and the lower triangular portion of [K] or [Z]. Additional input
may include the u d list and [S]. If [S] is input, u d must also be input. If u d is input but
[S] is omitted, [S] is internally calculated. In this case, u d must contain six and only six degrees-
of-freedom.
The forms shown above for both the stiffness and flexibility approaches assume that the element is a
free body with rigid body motions that are defined by u i = S u d . See General Element
Capability (GENEL) (Ch. 3) in the MSC Nastran Reference Guide for further discussion.
2. When the stiffness matrix K is input, the number of significant digits should be the same for all terms.
3. Double-field format may be used for input of K or Z.
4. The DMIG entry or the INPUTT4 module offer alternative methods for inputting large matrices.
5. The general element entry in the example above defines the following:
T
u i = 1 – 1 13 – 4 42 24 – 2
T
u d = 6 – 2 33
where i-j means the j-th component of grid point i. Points 42 and 33 are scalar points.
1.0 2.0 3.0 4.0 1.5 2.5
Z = 2.0 5.0 6.0 7.0 S = 3.5 4.5
3.0 6.0 8.0 9.0 5.5 6.5
4.0 7.0 9.0 10.0 7.5 8.5
Main Index
GENUDS 1905
User Data for Notify User Defined Service or Subroutine
GENUDS User Data for Notify User Defined Service or Subroutine
The GENUDS defines integer, real and character type data that will be passed to the notify method in
runtime info interface. The notify method will be called at start of load case, start of increment, end of
increment and end of load case.
Format:
1 2 3 4 5 6 7 8 9 10
GENUD SRV_ID
S
“INT” IDATA1 IDATA2 IDATA3 IDATA4 IDATA5 IDATA6 IDATA7
IDATA8 IDATA9 ... IDATAn
“REAL” RDATA1 RDATA2 RDATA3 RDATA4 RDATA5 RDATA6 RDATA7
RDATA8 RDATA9 ... RDATAn
“CHAR” CDATA1 CDATA2 ... CDATAn
Example:
GENUDS MY_SRV
INT 1 2 100
Describer Meaning
SRV_ID The service identifier used in the CONNECT SERVICE statement. (Character, no
default)
“INT” Keyword indicating that the following data is integer. (Character)
IDATAi User supplied integer data. (Integer, no default)
“REAL” Keyword indicating the following data is real. (Character)
RDATAi User supplied real data. (Real, no default)
“CHAR” Keyword indicating the following data is character. (Character)
CDATAi User supplied character data. (Character, no default)
Remarks:
1. The SRV_ID is the service identifier of SCA service in the CONNECT SERVICE statement. The
SCA service should have implemented the RuntimeInfo interface.
2. A CDATAi entry cannot be the character “INT”, “REAL” or “CHAR”.
Main Index
1906 GMBNDC
Geometric Boundary - Curve
GMBNDC Geometric Boundary - Curve
Defines a geometric boundary consisting of element edges along a curve interface. The boundary may consist
of edges of shell, beam, or solid elements.
Format:
1 2 3 4 5 6 7 8 9 10
GMBNDC BID GRIDI GRIDF
ENTITY ID1 ID2 ID3 ID4 ID5 ID6 ID7
ID8 -etc.-
Examples:
GMBNDC 1 101 106
GRID 102 103 104 105
Describer Meaning
BID Boundary identification number to be referenced by a CINTC entry. (Integer > 0)
GRIDI Initial grid identification number for boundary. (Integer > 0)
GRIDF Final grid identification number for boundary. (Integer > 0)
ENTITY Entity type for defining boundary. GRID (Character)
IDi Entity identification numbers for boundary of subdomain. Values in the list must be
unique. (Integer > 0)
Remarks:
1. All boundary identification numbers must be unique.
2. GRIDI and GRIDF define the end points of the boundary.
3. For each boundary, GRID is required.
4. For the GRID entity type, the entities should be listed in order from the GRIDI to the GRIDF. The
GRIDI and GRIDF need not be repeated in the IDi list.
5. Multiple continuation entries may be specified for additional entity identification numbers, IDi.
6. Interface elements may generate high or negative matrix/factor diagonal ratios. If there are no other
modelling errors, these messages may be ignored and PARAM,BAILOUT,-1 may be used to continue
the run.
Main Index
GMOVR3 1907
RBE3 SOL400 Rigid = Lagrange perturbation coincident grid override.
GMOVR3 RBE3 SOL400 Rigid = Lagrange perturbation coincident grid override.
Allows override values to the MDLPRM, GMOVR3 entry.
Format:
1 2 3 4 5 6 7 8 9 10
GMOVR3 ELEM1 X1 Y1 Z1 GMOVR3T1
ELEM2 X2 Y2 Z2 GMOVR3T2
-etc.- -etc.- -etc.- -etc.- -etc.-
Example:
GMOVR3 36955001 0.1
Describer Meaning
ELEMi RBE3 element ID. (Integer>0)
Xi Perturbation value of X coordinate (Real; default = 0.01)
Yi Perturbation value of Y coordinate (Real; default = 0.01)
Zi Perturbation value of Z coordinate (Real; default = 0.01)
GMOVR3Ti Adjustment to MDLPRM, GMOVR3T value. Zero Tolerance = GMOVR3T +
GMOVR3T ≥ 0.0. (Real; Default=0.0)
Remarks:
1. This entry is only active if MDLPRM,GMOVR3,3 or MDLPRM,GMOVR3,4 is present on the
MDLPRM Bulk Data entry.
2. This entry only affects RBE3 elements meeting the following criterion:
a. Let xq, yq, zq be the coordinates of the REFGRID and xk, yk, zk the coordinates of one of the
connected Gi,j nodes.
b. If |xk - xq|, |yk -yq|, and |zk - zq| are all less than or equal to GMOVR3T + GMOVR3T) for ALL
connected Gi,j nodes, the grids are considered coincident.
Any entry not meeting the above requirements will be ignored.
Main Index
1908 GRAV
Acceleration or Gravity Load
GRAV Acceleration or Gravity Load
Defines acceleration vectors for gravity or other acceleration loading.
Format:
1 2 3 4 5 6 7 8 9 10
GRAV SID CID A N1 N2 N3 MB
Example:
GRAV 1 3 32.2 0.0 0.0 -1.0
Describer Meaning
SID Set identification number. (Integer > 0)
CID Coordinate system identification number. (Integer > 0; Default = 0)
A Acceleration vector scale factor. (Real)
Ni Acceleration vector components measured in coordinate system CID. (Real; at least one
Ni 0.0)
MB Indicates whether the CID coordinate system is defined in the main Bulk Data Section
(MB = -1) or the partitioned superelement Bulk Data Section (MB = 0). Coordinate
systems referenced in the main Bulk Data Section are considered stationary with respect
to the assembly basic coordinate system. See Remark 10. (Integer; Default = 0)
Remarks:
1. The acceleration vector is defined by a = AN , where N is the vector defined by (N1, N2, N3).
The magnitude of a is equal to A times the magnitude of N . The static loads generated by this entry
are in the direction of a .
2. A CID of zero references the basic coordinate system.
3. Acceleration or gravity loads may be combined with “simple loads” (e.g., FORCE, MOMENT) only
by specification on a LOAD entry. That is, the SID on a GRAV entry may not be the same as that
on a simple load entry.
4. In the static solution sequences, SID must be selected by the LOAD Case Control command.
In the dynamic solution sequences, if there is a LOADSET Case Control command, then SID must
be referenced in the LID field of a selected LSEQ entry. If there is no LOADSET Case Control
command, then SID must be referenced in the EXCITEID field of an RLOADi or TLOADi entry.
5. At most nine GRAV entries can be selected in a given run either by Case Control or the LOAD Bulk
Data entry. Multiples or reflections of a given acceleration or gravity load can be economically
accomplished by use of the LOAD Bulk Data entry.
Main Index
GRAV 1909
Acceleration or Gravity Load
6. In cyclic symmetry solution sequences, the T3 axis of the coordinate system referenced in field 3 must
be parallel to the axis of symmetry. In dihedral cyclic symmetry (where STYPE = “DIH” on the
CYSYM entry), the T1 axis must, in addition, be parallel to Side 1 of segment 1R of the model.
7. For image superelements, the coordinate system must be rotated if the image is rotated relative to its
primary superelement.
8. Acceleration or gravity loads do not include effects due to mass on scalar points.
9. The RFORCE entry may be used to specify rotational accelerations.
10. The coordinate systems in the main Bulk Data Section are defined relative to the assembly basic
coordinate system which is fixed. This feature is useful when a superelement defined by a partitioned
Bulk Data Section is rotated or mirrored and the gravity load is more conveniently defined in terms
of coordinates which are fixed.
11. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1910 GRDSET
GRID Entry Defaults
GRDSET GRID Entry Defaults
Defines default options for fields 3, 7, 8, and 9 of all GRID entries.
Format:
1 2 3 4 5 6 7 8 9 10
GRDSET CP CD PS SEID
Example:
GRDSET 16 32 3456
Describer Meaning
CP Identification number of coordinate system in which the location of the grid points are
defined. (Integer > 0 or blank)
CD Identification number of coordinate system in which the displacements, degrees-of-
freedom, constraints, and solution vectors of the grid point are defined.
(Integer > -1 or blank)
PS Permanent single-point constraints on the grid point. (Any combination of Integers 1
through 6 with no embedded blanks, or blank.)
SEID Superelement identification number. (Integer > 0 or blank)
Remarks:
1. The contents of fields 3, 7, 8, or 9 of this entry are assumed for the corresponding fields of any GRID
entry whose field 3, 7, 8, and 9 are blank. If any of these fields on the GRID entry are blank, the
default option defined by this entry occurs for that field. If no permanent single-point constraints are
desired, one of the coordinate systems is basic, or the grid is assigned to the residual structure then the
default may be overridden on the GRID entry by making one of fields 3, 7, 8, or 9 zero (rather than
blank). Only one GRDSET entry may appear in the Bulk Data Section.
2. The primary purpose of this entry is to minimize the burden of preparing data for problems with a
large amount of repetition (e.g., two-dimensional pinned-joint problems).
3. At least one of the fields CP, CD, PS, or SEID must be specified.
Main Index
GRID 1911
Grid Point
GRID Grid Point
Defines the location of a geometric grid point, the directions of its displacement, and its permanent
single-point constraints.
Format:
1 2 3 4 5 6 7 8 9 10
GRID ID CP X1 X2 X3 CD PS SEID
Example:
GRID 2 3 1.0 -2.0 3.0 316
Free Field Large Format Example:
GRID*, 2, , 1.0, -2.0,
*, 3.0, , 136
Translates to:
1 2 3 4 5 6 7 8 9 10
GRID* 2 1.0 -2.0 +
*+ 3.0 136
The comma immediately following the -2.0 is required if NASTRAN IFPSTAR=NO is used. The comma
is always recommended even if NASTRAN IFPSTAR=YES (Default) is used.
Describer Meaning
ID Grid point identification number. (0 < Integer < 100,000,000, see Remark 6.)
CP Identification number of coordinate system in which the location of the grid point is
defined. (Integer > 0 or blank*)
X1, X2, X3 Location of the grid point in coordinate system CP. (Real; Default = 0.0)
CD Identification number of coordinate system in which the displacements, degrees-of-
freedom, constraints, and solution vectors are defined at the grid point.
(Integer > -1 or blank, see Remark 3.)*
PS Permanent single-point constraints associated with the grid point. (Any of the Integers
1 through 6 with no embedded blanks, or blank*.)
SEID Superelement identification number. (Integer > 0; Default = 0)
*See the GRDSET entry for default options for the CP, CD, PS, and SEID fields.
Main Index
1912 GRID
Grid Point
Remarks:
1. All grid point identification numbers must be unique with respect to all other structural, scalar, fluid
and extra (EPOINT) points.
2. The meaning of X1, X2, and X3 depends on the type of coordinate system CP as follows (see the
CORDij entry descriptions):
Type X1 X2 X3
Rectangular X Y Z
Cylindrical R (degrees) Z
Spherical R (degrees) (degrees)
See Grid Point and Coordinate System Definition in the MSC Nastran Reference Guide, for a definition of
coordinate system terminology.
3. The collection of all CD coordinate systems defined on all GRID entries is called the global
coordinate system. All degrees-of-freedom, constraints, and solution vectors are expressed in the
global coordinate system. It is recommended that points on the z-axis not have their displacement
directions defined with cylindrical or spherical coordinates. (See further remarks on the CORD1S,
CORD2S, CORD1C, and CORD2C.)
4. The SEID field can be overridden by use of the SESET entry.
5. If CD = -1, then this defines a fluid grid point in coupled fluid-structural analysis. This type of point
may only connect the CAABSF, CHACBR, CHACAB, CHEXA, CPENTA, CPYRAM, and
CTETRA elements to define fluid elements.
6. A zero (or blank if the GRDSET entry is not specified) in the CP and CD fields refers to the basic
coordinate system.
Main Index
GRIDA 1913
Associative GRID for PAA
GRIDA Associative GRID for PAA
Defines an associative GRID point to be used in the COMBINE step of PAA.
Format:
1 2 3 4 5 6 7 8 9 10
GRIDA GID ORIG_GID
PARTNAME
Example:
GRIDA 1 1000
Left_outboard_wing_tank
Describer Meaning
GID GRID ID to be used in the current run. (Integer > 0)
ORIG_GID GRID ID in Part being referenced. (Integer > 0)
PATNAMEi Name of Part ORIG_GID is in. (Character, C64, no internal blank spaces)
Remarks:
1. GRIDA entries are used only in the COMBINE step of PAA processing. They are used to allow the
other entries in the current bulk data to reference GRID points or SPOINTs in Parts that are being
combined to create the Assembly.
2. ORIG_GID must exist in the referenced Part. If the Part has been reduced, it must be a boundary
GRID for that Part (in the A-set of that Part).
3. The GRIDA id may be treated the same as if it were defined using a GRID or SPOINT entry in the
current run. The program will handle the connection to the referenced GRID/SPOINT in the Part.
4. Only dof which are in the Part A-set will be available for connection. If a GRIDA references a GRID
in a Part, which has fewer than 6 dof in the Part A-set (dof available in the Part matrices), although
the GRIDA will have 6 dof, only the dof which exist in the Part matrices will be connected to the
Part.
Main Index
1914 GRIDB
Axisymmetric Grid Point
GRIDB Axisymmetric Grid Point
Defines the location of a geometric grid point on a fluid point (RINGFL entry) for an axisymmetric fluid
model and/or axisymmetric structure. Also defines the boundary of the fluid.
Format:
1 2 3 4 5 6 7 8 9 10
GRIDB ID PHI CD PS IDF
Example:
GRIDB 30 30.0 3 345 20
Describer Meaning
ID Grid point identification number. (0 < Integer < 1000000)
PHI Azimuthal position of the fluid in degrees. (Real)
CD Identification number of the coordinate system in which the displacements are defined
at the grid point. (Integer > 0 or blank)
PS Permanent single-point constraints associated with grid point. (Any combination of
the Integers 1 through 6 with no embedded blanks, or blank.)
IDF Identification number of a RINGFL entry. (Integer > 0)
Remarks:
1. GRIDB is allowed only if an AXIF entry is also present. The AXIF entry must define a fluid
coordinate system.
2. All GRIDB identification numbers must be unique with respect to other scalar, structural, fluid and
extra (EPOINT) points.
3. The referenced RINGFL entry must be present and be included in a boundary list (BDYLIST entry).
4. If no harmonic numbers on the AXIF entry are specified, no fluid elements are necessary.
5. The collection of all CD coordinate systems defined on all GRID and GRIDB entries is called the
global coordinate system.
6. Fields 3, 4, and 6 are ignored, which facilitates the conversion of GRID entries to GRIDB entries.
Note that the fields are the same except for fields 1 and 9 when a cylindrical coordinate system is used.
Main Index
GRIDF 1915
Fluid Point
GRIDF Fluid Point
Defines a scalar degree-of-freedom for harmonic analysis of a fluid.
Format:
1 2 3 4 5 6 7 8 9 10
GRIDF ID R Z
Example:
GRIDF 23 2.5 -7.3
Describer Meaning
ID Identification number of axisymmetric fluid point. (0 < Integer < 1000000)
R Radial location of point in basic coordinate system. (Real > 0.0)
Z Axial location of point in basic coordinate system. (Real)
Remarks:
1. This entry is allowed only if an AXSLOT entry is also present.
2. ID must be unique with respect to all other scalar, structural, fluid and extra (EPOINT) points.
3. Grid points on slot boundaries are defined on GRIDS entries. Do not also define them on GRIDF
entries.
4. For plotting purposes, the R location corresponds to the basic X coordinate. The Z location
corresponds to the basic Y coordinate. Pressures will be plotted as displacements in the basic Z
direction.
5. Load and constraint conditions are applied as if GRIDF were a scalar point. Positive loads
correspond to inward flow. A single-point constraint causes zero pressure at the point.
Main Index
1916 GRIDS
Slot Surface Point
GRIDS Slot Surface Point
Defines a scalar degree-of-freedom with a two-dimensional location. Used in defining pressure in slotted
acoustic cavities.
Format:
1 2 3 4 5 6 7 8 9 10
GRIDS ID R Z W IDF
Example:
GRIDS 25 2.5 -7.3 0.5
Describer Meaning
ID Identification number of the slot point. (Integer > 0)
R Radial location of point in basic coordinate system. (Real 0.0)
Z Axial location of point in basic coordinate system. (Real)
W Slot width or thickness at the GRIDS point. (Real > 0.0 or blank)
IDF Identification number to define a GRIDF point. (Integer > 0 or blank)
Remarks:
1. This entry is allowed only if an AXSLOT entry is also present.
2. ID (and IDF if present) must be unique with respect to all other scalar, structural, fluid and extra
(EPOINT) points.
3. If W is blank, the default value on the AXSLOT entry will be used.
4. The IDF number is referenced on the CAXIFi entry for central cavity fluid elements next to the
interface. The IDF number is entered only if the grid point is on an interface. In this case, the IDF
should also be defined on a GRIDF entry.
5. If IDF is nonzero, then R must be greater than zero.
6. For plotting purposes, the R location corresponds to the basic X coordinate. The Z location
corresponds to the basic Y coordinate. The slot width, W, corresponds to the basic Z coordinate. The
pressure will be plotted in the basic Z direction.
7. Load and constraint conditions are applied as if the GRIDS is a scalar point. Positive loads
correspond to inward flow. A single-point constraint causes zero pressure at the point.
Main Index
GUST 1917
Aerodynamic Gust Load Description
GUST Aerodynamic Gust Load Description
Defines a stationary vertical gust for use in aeroelastic response analysis.
Format:
1 2 3 4 5 6 7 8 9 10
GUST SID DLOAD WG X0 V
Example:
GUST 133 61 1.0 0. 1.+4
Describer Meaning
SID Gust set identification number. (Integer > 0)
DLOAD Set identification number of a TLOADi or RLOADi entry that defines the time or
frequency dependence. (Integer > 0)
WG Scale factor (gust velocity/forward velocity) for gust velocity. (Real0.0)
X0 Streamwise location in the aerodynamic coordinate system of the gust reference point.
(Real)
V Velocity of vehicle. See Remark 5. (Real > 0.0)
Remarks:
1. The GUST entry must be selected with the Case Control command GUST = SID.
2. The gust angle is in the +z direction of the aerodynamic coordinate system. The value is
X – X0
WG T t – ----------------
V
where T is the tabular function.
3. In random analysis, a unit gust velocity (WG = 1/velocity) is suggested. The actual rms value is
entered on the TABRNDG entry.
4. X0 and V may not change between subcases under one execution.
5. V must be equal to VELOCITY on the AERO Bulk Data entry.
Main Index
1918 H5OUT
HDF5 Output Parameters for Dedicated and Appended HDF5
H5OUT HDF5 Output Parameters for Dedicated and Appended HDF5
HDF5 parameter control for Dedicated and Appended HDF5 files (for Modules only).
Format:
1 2 3 4 5 6 7 8 9 10
H5OUT MDID
PARAM1 VAL1 PARAM2 VAL2 -etc.- -etc.-
Example:
H5OUT 1
INPUT NO
H5OUT 80
ROTDOF NO
Describer Meaning
MDID MSC Nastran Module ID. (Integer ≥ 0)
PARAM(i) Name of a parameter. Allowable names are given in the HDF5OUT entry, see Table 9-22.
(Character)
VAL(i) Value of the parameter. See HDF5OUT entry, see Table 9-22 (Real or Integer).
Remarks:
1. This entry is to specify HDF5 default overrides to individual MSC Nastran Modules.
2. This entry must be in the Main Bulk Data (i.e., MODULE 0).
3. This entry overrides, for individual Modules, the HDF5OUT bulk data parameter specifications.
4. If HDF5 output is desired, The HDF5OUT Bulk Data entry is required.
5. The HDF5OUT bulk data parameters PRCISION, CMPRMTHD, and LEVEL are ignored on this
entry.
Main Index
HADACRI 1919
Mesh Adaptivity Criterion and Corresponding Parameters - SOL 101 & 400 (Linear)
HADACRI Mesh Adaptivity Criterion and Corresponding Parameters - SOL 101 & 400 (Linear)
Specifies Mesh refinement criterion for adaptive mesh refinement and corresponding parameters.
Format:
1 2 3 4 5 6 7 8 9 10
HADACRI CRITID TYPE F1 F2 F3 F4 F5 F6
Example:
HADACRI 1 1 0.9
Describer Meaning
CRITID Identification number referenced by the CRITID field in the HADAPTL Bulk Data entry.
(Integer > 0; no Default)
TYPE Type of Mesh refinement adaptivity criteria. See Remark 2. (Integer > 1 and < 4; Default = 1)
F1 to F8 Criteria specific parameters. See Remark 2. (Real; no Default)
Remarks:
1. The mesh refinement criteria currently available (and selected in the TYPE field) are:
TYPE Name of Mesh Refinement Criterion
1 Error indicator based
2 Element within a spatial spherical region
3 Elements within a spatial cubic region
4 Elements in contact criteria
Main Index
1920 HADACRI
Mesh Adaptivity Criterion and Corresponding Parameters - SOL 101 & 400 (Linear)
2. The following table describes the different refinement criteria and corresponding parameters:
Main Index
HADACRI 1921
Mesh Adaptivity Criterion and Corresponding Parameters - SOL 101 & 400 (Linear)
TYPE Description
1 In this case a scalar error indicator E e is computed for all elements ‘e’ in the finite element
mesh. Then, an element ‘e’ will be refined if
2 2
Ee F1 E
where F 1 is a weight factor 0 F 1 1 specified in the F1 field and E is the quadratic
mean of the error indicator defined as
N
2 1 2
E = ---- Ee
N
e=1
with N the total number of elements in the element set where element ‘e’ belongs. For this
criteria the fields F2 to F6 are ignored.
The elemental error indicator E e is computed using the grid point stresses following the
procedure utilized by the ELSDCON Case Control command and described in Mesh Stress
Discontinuities at Grid Points in the MSC Nastran Reference Guide. This procedure can be
summarized as follows:
Let
Na
e e
aij = W a aij
e=1
be the weighted average over all elements ‘e’ concurrent to a given node ‘a’ of each
e e
component ‘ij’ of the grid point stresses aij where W is a weighting factor assigned
to element ‘e’ and N a is the number of elements connected to the given node ‘a’.
An estimate of the error in a particular component of stress ‘ij’ at a grid point ‘a’ is
then be computed as
N
2 e 2
E aij = Wa aij – aij
f=1
Averaging the latter over the different stress components, ‘ij’, over the different shell
fibers (for shell elements) and over the different grid points ‘a’ connected by a given
element ‘e’ we obtain the elemental, scalar error indicator E e .
Main Index
1922 HADACRI
Mesh Adaptivity Criterion and Corresponding Parameters - SOL 101 & 400 (Linear)
TYPE Description
2 In this case the user specifies a spherical region in space with center given by (F1,F2,F3) and
radius given by F4. Then, all elements with at least one node with basic coordinates (X,Y,Z)
with the spherical region (i.e., such that X Y Z – F1,F2,F3 F4 ) will be refined. For
this criteria the fields F5 and F6 are ignored.
3 In this case the user specifies a hexahedral region in space, aligned with the basic coordinates
system, with corners given by (F1,F2,F3) and (F4,F5,F6). Then, all elements with at least one
node with basic coordinates (X,Y,Z) within the specified hexahedral region (i.e., such that
F1 X F4 , F2 Y F5 , F3 Z F6 ) will be refined.
4 In this case all elements with at least one node involved in contact either as touching or touched
nodes in deformable contact bodies are refined. For this criteria the fields F1 to F6 are ignored.
3. Each criteria must have a unique ID (specified by the CRITID field and referenced by the CRITID
field of the Bulk Data entry, HADAPTL).
4. The user might need to adjust the VARPHI parameter to ensure proper singular geometric feature
detection (such as sharp edges or corners) (See the Parameter, VARPHI).
Main Index
HADAPTL 1923
Local Adaptive Mesh Refinement Control Parameters - SOL 101 & 400 (Linear)
HADAPTL Local Adaptive Mesh Refinement Control Parameters - SOL 101 & 400 (Linear)
Specifies Local Adaptive Mesh Refinement control parameters.
Format:
1 2 3 4 5 6 7 8 9 10
HADAPTL ID REPEAT CRITID WHEREME WHEREID SNAPMETH
T
MAXLEVEL
Example:
HADAPTL 1 10 1 PROP 5
Describer Meaning
ID Identification number referenced by the Case Control HADAPT command. (Integer > 0;
no Default)
REPEAT Maximum number of analysis performed before the adaptive mesh refinement process is
stopped. See Remark 3. (Integer > 0; Default = 6)
CRITID Identification number of a mesh refinement criterion to be selected with the HADACRI
Bulk Data entry. See Remarks 1. and 2. and the HADACRI Bulk Data entry. (Integer >
0; no Default)
WHEREMET Method to specify the mesh refinement region subjected to the refinement criterion
referenced by the field CRITID. It can take the values: “ALL” or “SUPER” or “PROP”.
See Remark 4. (Character; Default = ALL)
WHEREID ID of the mesh refinement region subjected to the refinement criterion referenced by the
field CRITID. Must be specified if WHEREMET is “SUPER” or “PROP”. If
WHEREMET=ALL, this field will be ignored. See Remark 4. (Integer > 0; Default = 0)
SNAPMETH Method to project, snap or relax new grid pints created on mid-edge or mid-faces on the
mesh boundary during the refinement process onto the analysis domain boundary:
0 No projection; New grids are placed in the mid-side of edges.
1 New grid points are projected onto a smooth approximation of the analysis
domain boundary interpolated from the initial mesh boundary.
(Integer > 0; Default = 0)
MAXLEVEL Maximum refinement level allowed for each individual element in the mesh. No elements
in the mesh will be refined to a level bigger then MAXLEVEL. (Integer > 0; Default =
REPEAT)
Main Index
1924 HADAPTL
Local Adaptive Mesh Refinement Control Parameters - SOL 101 & 400 (Linear)
Remarks:
1. The adaptive mesh refinement occurs when a particular refinement criterion is satisfied. Data for the
refinement criterion is specified by the Bulk Data entry HADACRI referenced by the CRITID field.
2. Multiple mesh refinement criteria can be selected in different subsets of the model. To this end, the
user needs to define multiple HADAPTL entries with the same ID. Each entry might specify a
different criteria (referenced in the CRITID field and defined on the corresponding HADACRI Bulk
Data entry) on different subsets of the mesh (defined in the WHEREMET and WHEREID fields).
3. When multiple HADAPTL entries with the same ID are specified, NASTRAN will chose for the
REPEAT, SNAPMETH, and MAXLEVEL field the maximum among all multiple instances.
4. The fields WHEREMET and WHEREID refer respectively to the Method to specify the mesh
refinement region (subjected to the refinement criterion referenced by the field CRITID and defined
with the Bulk Data entry, HADACRI) and its corresponding ID. For example, WHEREMET=SUPER,
WHEREID=3 means that local adaptive mesh refinement (with the criteria referenced by the
CRITID field) should be effected only in superelement 3. Likewise, WHEREMET=PROP,
WHEREID=5 (see the previous Example) means that local adaptive mesh refinement (with the
criteria referenced by the CRITID field) should be effected only in those element with Property ID
equal to 5. Finally, WHEREMET=ALL imply mesh refinement in all elements.
5. In partitioned superelements, the HADAPT entry must be specified in the main bulk data section.
Entries specified in the Bulk Data Section corresponding to individual parts (sections beginning with
BEGIN SUPER) will be ignored.
6. When using regular superelements, the Bulk Data Section must begin with BEGIN SUPER as
opposed to BEGIN BULK, in order for the refinement to be appropriately propagated across
superelement boundaries. If BEGIN BULK is used, grid points on the superelement boundaries will
be duplicated and not shared by the joining superelements.
7. The user should avoid the use of MPC sets 90000000 to 99999999 which are reserved for hanging
nodes constraints generated during the adaptive mesh refinement process.
8. The user might need to adjust the VARPHI parameter to ensure proper singular geometric feature
detection (such as sharp edges or corners) (See the Parameter, VARPHI).
9. When SNAPMETH=0, all mid-edge nodes belonging to straight edges are placed on the mid-side of
its edge. By contrast, when SNAPMETH=1, mid-edge nodes belonging to the boundary of the mesh
are projected to a smooth approximation of the analysis domain boundary interpolated from the mesh
boundary.
10. Mid-face nodes belonging to bilinear quadrilateral faces are placed at the baricenter of its face.
Main Index
HDF5DA 1925
List of Modules for Dedicated and Appended HDF5 Output
HDF5DA List of Modules for Dedicated and Appended HDF5 Output
This entry is referenced by the HDF5DA case control. It is used to specify the dedicated HDF5 file name,
via the UDNAME entry, for individual BEGIN MODULE.
Format:
1 2 3 4 5 6 7 8 9 10
HDF5DA ID CONFIG
MDID0 UDID0 MDID1 UDID1 MDID2 UDID2 MDID3 UDID3
MDID4 UDID4 MDID5 UDID5 -etc.-
Example:
HDF5DA 17 1
0 100 2 200
Describer Meaning
ID ID associated with the Case Control HDF5DA command. (Integer > 0)
CONFIG ID of a UDNAME entry to assign a name for assembly configuration. The number of
characters should not exceed 64 on the referenced UDNAME. (Integer ≥ 0). Default=0 for
no configuration name.
MDIDi MODULE ID for a dedicated HDF5 file. Residual structure is considered MODULE 0. See
Remark 2. (Integer ≥ 0)
UDIDi ID of a UDNAME entry to specify the dedicated HDF5 file name for module MDIDi.
(Integer > 0).
Remarks:
1. This entry must be present for any dedicated HDF5 module file and be referenced by HDF5DA case
control.
2. Every module (primary and secondary, including MODULE 0) must have a pair of (MDID, UDID)
listed in this entry.
3. Unique UDID is not required for each UDIDi field. (i.e., Two or more module outputs can be
directed to same H5 file).
4. This entry must be in the main bulk data section. It may not occur in a BEGIN MODULE.
5. 'MDLPRM, HDF5, value' and any of its variants are forbidden
Main Index
1926 HDF5OUT
HDF5 output parameters
HDF5OUT HDF5 output parameters
HDF5 output parameters.
Format:
1 2 3 4 5 6 7 8 9 10
HDF5OUT PARAM1 VAL1 PARAM2 VAL2 ... ... PARAMi VALi
Example:
HDF5OUT PRCISION 32 CMPRMTHD LZ4 LEVEL 4
HDF5OUT 3 PRCISION 64
Describer Meaning
Param(i) Name of a parameter. Allowable names are given in Table 9-22. (Character)
Value(i) Value of the parameter. See Table 9-22. (Real or Integer)
Table 9-22 HDF5OUT Parameters
Name Description Type and Value
PRCISION Precision of hdf5 file. Integer, 32 (default) or 64.
32 Single precision. All integers are 32 bits. Most real numbers are 32
bits, however a real number can be 64 bits if its type attribute in
DataType_<version>.xml is “double”.
64 Double precision. All integers and real numbers are in 64 bit.
CMPRMTHD Compress method. Characters, “NONE”, “BLOSCLZ”, “LZ4” (default) or
“GZIP”.
NONE No compression
BLOSCLZ Blosclz method
LZ4 LZ4 method
GZIP Gzip method, this is the only method MSC Nastran had been
supported from 2016.1 to 2022.1
LEVEL Compress level, 0 < level ≤ 9(integer), no default. For Gzip method, level is fixed to
3 internally
Main Index
HDF5OUT 1927
HDF5 output parameters
Table 9-22 HDF5OUT Parameters (continued)
Name Description Type and Value
INPUT Option to write input datasets and characters.
YES Write out input datasets, characters (default)
NO Do not write out
ROTDOF Option to write rotational components for vector type datasets, characters. “YES”
(default) or “NO”. This can reduce file size when “NO” is specified
MTX Option to write matrix data. “YES” or “NO” (default)
YES Write matrix data
NO (default) Do not write matrix data.
MDL Option to write out input datasets into a separate file. Integer, -1, 0(default), 1 or 2.
2 Write model input data only
1 Write model input data into a separate file
0 Do not write model input data into a separate file (Default)
-1 Use PARAM OP2GM34 setting for GEOM3 and GEOM4 output
GM12 Option to write GEOM1 and GEOM2 data blocks in the .h5 file, integer, 1
(default) or 0.
1 (default) Write GEOM1 and GEOM2 data blocks into .h5
0 Do not write GEOM1 and GEOM2 data blocks into .h5
GM34 Option to write GEOM3 and GEOM4 data blocks in hdf5 file, integer, -1(default),
1 or 0.
-1 Use PARAM OP2GM34 setting
1 Write GEOM3 and GEOM4 data blocks into hdf5
0 Do not write GEOM3 and GEOM4 data blocks into hdf5
INFO Option to write job run information in NH5RDB. Characters.
YES Write the run information in NH5RDB. (Default)
NO Do not write the information in NH5RDB
XHH Option to write BHH and MHH matrices. Characters.
YES Write BHH and MHH matrices
NO Do not write BHH and MHH matrices. (Default)
Main Index
1928 HDF5OUT
HDF5 output parameters
Table 9-22 HDF5OUT Parameters (continued)
Name Description Type and Value
SGENL Set compression factor for NLOUT non-strain output datasets.
0 to 10 Scale factor with scaleoffset lossy compression (Default=3)
-1 Don't use scaleoffset lossy compression
SSTRN Set compression factor for NLOUT strains output datasets.
0 to 10 Scale factor with scaleoffset lossy compression (Default=3)
-1 Don't use scaleoffset lossy compression
Remarks
1. The .h5 binary database file will be generated when HDF5OUT is specified in bulk data section.
2. When PRCISION is 32, all integers and most real numbers will be written in 32 bit. Some real
numbers are written in 64 bit when they are declared as type="64" in schema_<version>.xml.
When PRCISION is 64, all integers and real numbers are in 64 bit.
3. To help third party software packages to distinguish hdf5 file precision, an HDF5 attribute with
name "PRECISION" is attached to hdf5 file object. It is a 32 bit integer with value of 32 or 64 based
on PRCISION parameter in HDF5OUT entry.
4. When HDF5OUT is specified, all hdf5 related parameters, such as HDF5, H5INFO, H5MDL,
H5GM34, H5XHH, H5MTX, H5NORDOF, H5SGENL and H5SSTRN in MDLPRM entry are
ignored. Those parameters will be deprecated in the future.
5. It is required to set below environment variable to view or use hdf5 utilities for an hdf5 file
compressed by LZ4 or BloscLZ filter.
HDF5_PLUGIN_PATH=<msc_nastran_version>/<arch>/lib/hdf5plugin/plugins
For example, in Windows, if MSC Nastran 2022.3 is installed to location “C:\Program
Files\MSC.Software\MSC_Nastran\2022.3”, the variable should be:
HDF5_PLUGIN_PATH="C:\Program
Files\MSC.Software\MSC_Nastran\2022.3\msc20223\win64i8\lib\hdf5plugin\
plugins"
6. This entry is not allowed in a MODULE but some of its parameters for specific MODULES may be
overridden via the H5OUT bulk data entry.
Main Index
HEATLOS 1929
Heat Loss Through Convection or Radiation of the Airbag Surface - SOL 700
HEATLOS Heat Loss Through Convection or Radiation of the Airbag Surface - SOL 700
Defines the heat-transfer model to be used with GBAG or COUPLE. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
HEATLOS HID HTRID SUBID HTRTYPE HTRTYPID COEFF COEFFV
Example:
HEATLOS 101 83 HTRCONV 2 TABLE 14
Describer Meaning
HID Unique number of a HEATLOS entry. (Integer > 0; Required)
HTRID Number of a set of HEATLOS entries HTRID must be referenced from a GBAG or
COUPLE entry. (Integer > 0; Required)
SUBID (Integer > 0, 0)
>0 Number of a BSURF, BCBOX, BCPROP, BCMATL or BCSEG, which
must be a part of the surface as defined on the GBAG or COUPLE
entries.
=0 HEATLOS definitions are used for the entire surface as defined on the
GBAG or COUPLE entries.
HTRTYPE Defines the type of heat transfer. (Character; Required)
HTRCONV The HTRCONV logic is used to model heat transfer through
convectionion in an air bag. The area of convection through which the
energy is transported is equal to the area of the subsurface multiplied by
COEFFV. A value of COEFFV = 1.0 will expose the complete subsurface
area, while a value of COEFFV = 0.0 will result in no heat transfer
through the subsurface.
HTRRAD The HTRRAD logic is used to model heat transfer through radiation in
an air bag. The area of convection through which the energy is
transported is equal to the area of the subsurface multiplied by COEFFV.
A value of COEFFV = 1.0 will expose the complete subsurface area,
while a value of COEFFV = 0.0 will result in no heat transfer through
the subsurface.
HTRTYPID Heat transfer ID. References existing HTRTYPE entry. (Integer > 0; Required)
COEFF Method of defining the area coefficient. (Character, CONSTANT)
CONSTANT The area coefficient is constant and specified on COEFFV.
Main Index
1930 HEATLOS
Heat Loss Through Convection or Radiation of the Airbag Surface - SOL 700
Describer Meaning
TABLE The area coefficient varies with time. COEFFV is the number of a
TABLED1 entry giving the variation with time.
COEFFV The area coefficient or the number of a TABLED1 entry depending on the COEFF entry.
(0.0 < R < 1.0 or 1 > 0, 1.0)
Remarks
1. A combination of multiple HEATLOS with different HTRTYPEs is allowed.
2. It allows for setting up the exact same model for either a uniform pressure model (GBAG to
HEATLOS) or an Eulerian model (COUPLE to HEATLOS). It is then possible to set up the model
using the switch from full gas dynamics to uniform pressure (GBAGCOU).
3. For the same BSURF multiple, different types of heat transfer may be defined.
4. A more detailed description can be found in Porosity in Air Bag for more details.
Main Index
HGSUPPR 1931
Hourglass Suppression Method - SOL700
HGSUPPR Hourglass Suppression Method - SOL700
Defines the hourglass suppression method and the corresponding hourglass damping coefficients. Used in
SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
HGSUPPR HID PROP PID HGTYPE HGCMEM HGCWRP HGCTWS HGCSOL
+ RBRCOR VALUE
Example:
HGSUPPR 1 SHELL 100 FBV 0.1 0.1 0.1
+ YES 10000
Describer Meaning
HID Hourglass suppression definition number. (Integer > 0; Required.)
PROP Property type. (Character; See Remark 1.)
PID Property number. (Integer > 0; See Remark 1.)
HGTYPE Hourglass suppression method: (Character; See Remark 2.)
FBV For shells only (default for shells)
FBS For shells and solids (default for solids)
Dyna For solids only
HGCMEM Membrane damping coefficient. (0.0 ≤ Real ≤ 0.15; default=0.1)
HGCWRP Warping damping coefficient. (0.0 ≤ Real ≤ 0.15; default=0.1)
HGCTWS Twisting damping coefficient. (0.0 ≤ Real ≤ 0.15; default=0.1)
HGCSOL Solid damping coefficient. (0.0 ≤ Real ≤ 0.15; default=0.1)
RBRCOR Rigid body rotation correction: (Character; default=NO)
NO No rigid-body rotation correction is applied to hourglass resisting
forces.
YES Rigid-body rotation correction is applied to hourglass resisting
forces.
VALUE Number of steps. (Integer > 0; See Remark 3.)
Main Index
1932 HGSUPPR
Hourglass Suppression Method - SOL700
Remarks:
1. The property type definition and the property number are required. Since property numbers are
unique within a certain class of element types, the property type and the property number uniquely
define to what elements the hourglass suppression method and coefficients apply. The following
property types are valid entries:
BAR For bar elements
BEAM For beam elements
BELT For belt elements
COMP For composite shell elements
DAMP For damper elements
ELAS For spring elements
EULER For Eulerian elements
ROD For rod elements
SHELL For shell elements
SOLID For solid Lagrangian elements
It must be noted however, that only shell CQUAD4 and Lagrangian CHEXA and CPENTA
elements can suffer from undesired hourglass modes. All HGSUPPR entries referring to other types
of elements are ignored.
2. There are three types of hourglass suppression methods available in Nastran. These are standard
DYNA viscous (DYNA) hourglass damping, the Flanagan-Belytschko Stiffness (FBS) hourglass
damping, and the Flanagan-Belytschko Viscous (FBV) hourglass damping.
Lagrangian solid elements can address DYNA and FBS suppression; shell elements can address
DYNA and FBV suppression. The default for the Lagrangian solid elements is FBS. The default for
the shell elements is FBV.
3. The rigid-body rotation correction on the hourglass forces is only necessary in cases where shell
elements undergo a large rigid-body rotation. If the RBRCOR field is set to YES, and the VALUE
field is left blank, the correction is applied during each time step. If the VALUE field is set to a
number, the rotation correction is applied only when the rigid-body rotation would result in a
rotation of the element over 90° in less than VALUE time steps. Usually, if the rigid-body rotation
correction is necessary; 10000 is a good value. This option saves some CPU time.
The RBRCOR option applies to the Key-Hoff shell formulation only; for all other element types and
formulations, the option is ignored.
4. The membrane, warping and twisting coefficients apply to shell elements only; for all other element
types, the data is ignored. The solid damping coefficient applies to solid Lagrangian elements only;
for all other element types, the data is ignored.
Main Index
HTRCONV 1933
Air Bag Convection
HTRCONV Air Bag Convection
Defines the heat transfer through convection for a COUPLE and/or GBAG surface.
Convection is heat transfer from the air bag to the environment through the air bag surface. Used in SOL 700
only.
Format:
1 2 3 4 5 6 7 8 9 10
HTRCONV HTRID HTRCFC HTRCFT TENV
Example:
HTRCONV 8 14 293.0
Describer Meaning
HTRID Unique number of a HTRCONV entry. Referenced from HEATLOS. (Integer > 0;
Required)
HTRCFC Constant heat transfer convection coefficient. See Remark 3. (Real > 0)
HTRCFT The heat transfer convection coefficient is a tabular function of time. The number
given here is the number of a TABLED1 entry. See Remark 3. (Integer > 0)
TENV Environmental temperature. (Real > 0; Required)
Remarks:
1. The HTRCONV entry can be referenced from a HEATLOS entry.
2. When used with Euler, the entry can only be used with the single material hydrodynamic Euler solver
using an EOSGAM (ideal gas) equation of state. Two of the four gas constants ( , R, c and/or c p )
have to be defined on the EOSGAM entry.
3. Either HTRCF-C or HTRCF-T must be specified.
4. Energy will only transfer out of the air bag if the temperature inside the air bag is higher than the
environmental temperature.
Main Index
1934 HTRRAD
Air Bag Radiation
HTRRAD Air Bag Radiation
Defines the heat transfer through radiation for a COUPLE and/or GBAG surface.
Radiation is heat transfer from the air bag to the environment through the air bag surface. Used in SOL 700
only.
Format:
1 2 3 4 5 6 7 8 9 10
HTRRAD HTRID GASBMI-C GASEMI-T TENV SBOLTZ
Example:
HTRRAD 2 0.15 293.0 5.676E-8
Describer Meaning
HTRID Unique number of a HTRRAD entry. Referenced from HEATLOS. (Integer > 0;
Required)
GASEMI-C Constant gas emissivity. See Remark 3. (Real > 0)
GASEMI-T The gas emissivity is a tabular function of time. The number given here is the number
of a TABLED1 entry. See Remark 3. (Integer > 0)
TENV Environmental temperature. (Real > 0; Required)
SBOLTZ Stephan-Boltzman constant. (Real > 0; Required)
Remarks:
1. The HTRRAD entry can be referenced from a HEATLOS entry.
2. When used with Euler, the entry can only be used with the single material hydrodynamic Euler solver
using an EOSGAM (ideal gas) equation of state. Two of the four gasconstants ( , R, c and/or c p )
have to be defined on the EOSGAM entry.
3. Either GASEMI-C or GASEMI-T must be specified.
4. Energy will only transfer out of the air bag if the temperature inside the air bag is higher than the
environmental temperature.
Main Index
HYBDAMP 1935
Hybrid Modal Damping for Direct Dynamic Solutions
HYBDAMP Hybrid Modal Damping for Direct Dynamic Solutions
Specifies hybrid damping parameters.
Format:
1 2 3 4 5 6 7 8 9 10
HYBDAMP ID METHOD SDAMP KDAMP PRTEIG
Example:
HYBDAMP 101 2000 2001 NO YES
Describer Meaning
ID Identification number of HYBDAMP entry (Integer > 0; Required)
METHOD Identification number of METHOD entry for modes calculation. (Integer > 0;
Required)
SDAMP Identification number of TABDMP1 entry for modal damping specification. (Integer
> 0; Required)
KDAMP Selects modal “structural” damping. See Remark 1. (Character: “Yes” or “NO”; Default
= “NO”)
PRTEIG Print eigenvalue summary from hybrid damping calculation (Character: “Yes” or
“NO”; Default = “NO”)
Remarks:
1. For KDAMP = “YES”, the viscous modal damping is entered into the complex stiffness matrix as
structural damping.
2. Hybrid damping is generated using modal damping specified by the user on TABDMP entries.
T
b 1 1
b 2 T
2
BH = M 1 2 n M
b n T
n
For KDAMP = “YES”
Main Index
1936 HYBDAMP
Hybrid Modal Damping for Direct Dynamic Solutions
T
g 1 1
g 2 T
2
KH = M 1 2 n M
g n T
n
where
i = modes of the structure
M = structural mass matrix
b i = modal damping values, b i = g i i m i
g i = twice the critical damping ratio determined from user specified TABDMP entry
i = natural frequency of mode i
mi = generalized mass of mode i
3. Hybrid damping is based on a modal solution and the mass matrix. Even if user requested all the
modes and specified a flat value of G the result is still dependent on the Rank of the Mass matrix. Also
note that Hybrid damping does not include residual vectors to compensate for high frequency
contribution and other possible massless degrees of freedom effects in the Rank of the mass matrix.
PARAM, COUPMASS, 1 may improve the mass rank.
4. HYBDAMP is referenced by the DAMPING and ROTHYBD Bulk Data entries.
5. When hybrid damping is used during FRF component generation, it is recommended to set the
KDAMP field to YES on the HYBDAMP entry. See remarks under SDAMPING Case Control
description for further details.
6. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
HYDROC 1937
Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements using fluid cavities.
HYDROC Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid
Elements using fluid cavities.
Defines a hydrostatic pressure load on a face of a CHEXA, CPENTA, CPYRAM, CTETRA, CTRIA3,
CTRIA6, CTRIAR, CQUAD4, CQUAD8, or CQUADR element using fluid cavity data. The HYDROC
entry is NOT supported in SOL101 because SOL 101 does not support the Fluid Structure Interface.
Format:
1 2 3 4 5 6 7 8 9 10
HYDROC SID PSOLID PNOM G PCH PLD4 OVRD
CID/GRD HGHTB HABOV
Example:
HYDROC 66 33 42. 980. 1
99 0. 10.
Describer Meaning
SID Load set identification number. (Integer > 0)
PSOLID PSOLID ID of the cavity. Fluid density will be obtained from the associated MAT10
entry. (Integer > 0); HYDROC requires ACMODL,DIFF (the default value).
PNOM Nominal or atmosphere pressure. If G=0.0, PNOM only is applied. (Real; default =
0.0)
G Acceleration (e.g. of gravity) in the direction from HABOV toward the origin defined
by the CID/GRD field. (Real; Default = 1.0)
PCH 0 - default (no punch);
1 - Punch Set of structural grids.
2 - Punch Set of structural elements.
3 - Punch both structural grids and structural elements. (Integer ≥0)
PLD4 0 - default (no punch);
1 - Punch the resulting PLOAD4 entries. (Integer ≥ 0)
OVRD 0-default. If PARAM, INREL, is present and G not equal to 1.0, then a fatal error
message will be issued.
1 - Allow non unit value of G.
CID/GRD Coordinate ID of a reference coordinate system to measure the coordinate z-direction.
If Integer ≥ 0; a coordinate system ID is used. If Integer < 0; a GRID ID is used with
the z-direction of the GRID, CD field. Note: A spherical coordinate system will result
in a fatal error. See Remark 1.; (Integer - default 0 -basic).
Main Index
1938 HYDROC
Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements using fluid cavities.
Describer Meaning
HGHTB The z-distance to the lowest fluid point measured from reference origin. See Remark 1..
(Real; Default = 0.0)
HABOV The height of the fluid above the lowest point measured in the z-direction from
reference origin. See Remark 1. (Real; Default = 0.0)
Remarks:
1. On the HYDROC entry, HGHTB along with the z-coordinate direction, are used to determine the
location of the “bottom” of the fluid body in the case where the fluid cavity is full and there is no free
surface.
In the case where a free fluid surface has been modeled in the cavity, CID/GID and HGHTB are for
reference only. The lowest fluid level is determined as the lowest wetted grid in the FSI coupling
measure in the direction defined by CID/GID. From the FSI coupling, free surface formed by
examining wetted grids may not be perpendicular to the z-direction of CID/GID. Hence, HABOV
will be considered as average free surface and hydrostatic pressure will be computed with respect to
HABOV. However, a fatal message will occur if the average free surface specified by HABOV is
significantly above the free surface of wetted grids. Also note that some wetted grids/elements may
not get loaded if HABOV is too low.
Main Index
HYDROC 1939
Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements using fluid cavities.
2. The HYDROC entry will internally be converted to an equivalent set of PLOAD4 entries with the
same load SID
3. Each fluid cavity should have a unique PSOLID entry as HYDROC uses the PSOLID to identify
the cavity.
4. The PNOM is applied only from fluid surface to bottom of fluid.
5. HYDROC interaction with the Fluid Structure Interface (FSI) algorithm is shown in the two figures
below. The top figure shows a column of fluid over some structural elements. The column of fluid is
30 units high, however, only its bottom surface is in contact with structural elements. Therefore, the
FSI will only see a fluid that is 10 units high. A HYDROC entry for this model, with a HABOV =
50 units would fail to compute any hydrostatic loading, because 50 units is well outside the tolerance
of the FSI interface, which is at 30 units.
The second figure shows the same fluid column, but a layer of shell elements has been laid on top of
the fluid column.
Main Index
1940 HYDROC
Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements using fluid cavities.
In this case, the FSI sees a column of fluid 50 units high. Thus a HABOV = 50 units will generate
PLOAD4 entries using a height of 30 units for the fluid. For this model, any HABOV with values
(30 units ≤ HABOV ≤ 50 units) will yield valid PLOAD4 entries on the fluid structure interface of
the structural solid elements with the height used depending on the value of HABOV.
6. The figures below show additional HYDROC PNOM rules associated with the FSI interface. Also
note how fluid cavities are defined by PSOLID ID.
Staggered grid for flooding simulation.
Main Index
HYDROS 1941
Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements using element or grid sets
HYDROS Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements
using element or grid sets
Defines a hydrostatic pressure load on a face of a CHEXA, CPENTA, CPYRAM, CTETRA, CTRIA3,
CTRIA6, CTRIAR, CQUAD4, CQUAD8, or CQUADR element using element set data.
Format:
1 2 3 4 5 6 7 8 9 10
HYDROS SID PNOM RHO G SETE SETG PLD4 OVRD
CID/GRD HGHTB HABOV CNTL
Example:
HYDROS 77 55. 0.08 17. 300 1
200 97. 83
Describer Meaning
SID Load set identification number. (Integer > 0)
PNOM Nominal or atmosphere pressure. If G=0.0, PNOM only is applied. (Real; Default =
0.0)
RHO Mass density. (Real > 0.0)
G Acceleration (e.g. of gravity) in the direction from HABOV toward the origin defined
by the CID/GRD field. (Real; Default = 1.0)
SETE The ID of a SET3 entry using (DES= ELEM) or SET1 to identify the element IDs of
structure elements at fluid-structure interface used for hydrostatic loading. (Integer ≥0)
SETG The ID of a SET3 entry using (DES= GRID) or SET1 to identify the element grid IDs
of structure elements at fluid-structure interface used for hydrostatic loading.
(Integer ≥0)
PLD4 0 - default (no punch);
1 - Punch the resulting PLOAD4 entries. (Integer ≥ 0)
OVRD 0-default. If PARAM, INREL, is present and G not equal to 1.0, then a fatal error
message will be issued.
1 - Allow non unit value of G.
CID/GRD Coordinate ID of a reference coordinate system to measure the coordinate z-direction.
If Integer ≥ 0; a coordinate system is used. If Integer < 0; a GRID ID is used with the
z-direction of the GRID, CD field. Note: A spherical coordinate system will result in a
fatal. See Remark 1.; (Integer - default 0 -basic).
Note: A spherical coordinate system will result in a fatal error.
HGHTB The z-distance to the lowest fluid point measured from reference origin.
(Real; Default = 0.0)
Main Index
1942 HYDROS
Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements using element or grid sets
Describer Meaning
HABOV The height of the fluid above the lowest point measured in the z-direction from
reference origin. (Real; Default = 0.0)
CNTL SET3 ID of control grids to get pressure application direction. (Integer ≥0, see Remark
2.).
Remarks:
1. The HYDROS entry will internally be converted to an equivalent set of PLOAD4 entries with the
same load SID.
Main Index
HYDROS 1943
Hydrostatic Pressure Loading on Surface and Faces of Shell or Solid Elements using element or grid sets
2. The pressure direction can be defined with or without CNTL entry in HYDROS card for closed and
open geometries.
• For closed geometry like sphere, cylinder, cube, etc., SET3 id should have only one grid defined
inside the geometry. Use of inside grid, will result in internal pressure to be applied. If the external
pressure needs to be applied, then change the sign of Pnom and Gravity in the HYDROS card.
(P = Pnom+.g.h)
• For open geometry, the direction of the pressure is based on the relation between the direction of
control point grid to the element and the element normal. Refer 1(a) and 1(b) for direction of
pressure for a open geometry.
• Without control point defined in the HYDROS card the pressure direction is aligned with the
element normal direction. If the element normal is outward, then the pressure direction is
outward and vice versa.
Figure 1 (a) Figure 1 (b)
Main Index
1944 HYDSTAT
Hydrostatic Preset of Density in Euler Elements
HYDSTAT Hydrostatic Preset of Density in Euler Elements
Initializes the Euler element densities in accordance to a hydrostatic pressure profile. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
HYDSTAT HID MID GID CID XCG YCG ZCG PATM
Example:
HYDSTAT 101 4 0.0 0.0 0.0 100000.
Describer Meaning
HID Identification number of the HYDSTAT entry referenced from the COUPLE entry.
(Integer > 0; Required)
MID Material MATDEUL id to which the hydrodynamic pressure profile will be applied.
(Integer > 0; Required)
GID Number of a grid point at the free surface. See Remark 4. (Integer > 0)
CID Local coordinate system. See Remark 4. (Integer > 0)
XCG,YCG, Coordinates of a point at the free surface. See Remark 4. (Real)
ZCG
PATM Pressure at free surface. (Real; Required)
Remarks:
1. It is assumed that each Euler domain contains at most two Eulerian materials and includes the GRAV
entry. One material has to be a fluid using EOSPOL the other a gas or void. This EOSPOL material
is given by the MID entry. The interface between gas and fluid is the free surface and is assumed to
be normal to the gravity vector as specified on the GRAV entry. For example if the gravity vector
points in the z-direction then the interface between the gas and the fluid has to be horizontal.
2. The hydrostatic preset changes the density of the fluid like material in order to conform to the
hydrostatic preset. It overrules the material densities as specified on the TICEL and TICVAL entries.
Densities of the gas like material are not changed.
3. The free surface has to match with material fractions as defined in the initialization of Euler elements
by the TICEL and TICEUL entries. The hydrostatic preset only changes densities, it does not change
material fractions.
4. There are two options to enter the location of the free surface. The first option is to enter a grid point
number. In that case the fields CID and XCG-ZCG have to be left blank. The GRIDPOINT entry
already has the option of using a local coordinate system. When coordinates are used then the field
GID has to be left blank.
Main Index
HYDSTAT 1945
Hydrostatic Preset of Density in Euler Elements
5. If there is no structural grid point indicating the free surface then a new grid point can be defined
that will only be used for determining the free surface level. If the Gravity vector points in the z-
direction, only the z-coordinate of the grid point will be used. The x and y ordinate can be chosen
arbitrarily. Similar remarks hold when the gravity vector is in one of the other coordinate directions.
The same holds when using coordinates instead of a grid point.
6. PATM should be equal to the pressure in the air.
7. When coupling surfaces are present then the HYDSTAT ID needs to be referenced by at least one
coupling surface. For each coupling surface a different HYDSTAT entry can be defined. Several
COUPLE entries can refer to the same HYDSTAT ID. If no HYDSTAT ID is specified on a
COUPLE entry then Euler elements associated to this coupling surface will not be initialized with a
hydrostatic preset.
Main Index
1946 IMPCASE
Defines a collection of imperfection cases
IMPCASE Defines a collection of imperfection cases
Defines a collection of imperfection cases by listing of identification numbers of IMPGEOM entries. Used
in SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
IMPCASE ID IMPFID1 IMPFID2 ... IMPFIDi
Example:
IMPCASE 5 1 2
Describer Meaning
ID Identification number (integer > 0, required)
IPMFIDi Identification number of imperfection case (integer >0, required)
Remarks:
1. When the ID is referenced by case control IMPERFECT command, the list of IMPGEOM entries
are used to apply geometric imperfections.
2. “THRU” can be used to specify IMPFIDi.
Main Index
IMPGEOM 1947
Defines Geometric Imperfection
IMPGEOM Defines Geometric Imperfection
Defines geometric imperfection by selecting subcases, steps, mode numbers or increments from imperfection
input files. Used in SOL 400.
Format:
1 2 3 4 5 6 7 8 9 10
IMPGEOM IMPFID SETID SCALE UNIT MODID
SUBCASE1 STEP1 MODEINC1 SETID1 SCALE1 UNIT1 MODID1
SUBCASE2 STEP2 MODEINC2 SETID2 SCALE2 UNIT2 MODIDi
etc.
Example:
IMPGEOM 1
1 3 1 0.011 34
1 3 2 0.002 34
Describer Meaning
IPMFID Identification number of imperfection case (integer >0, required)
SETID Default of SETIDi (integer ≥ 0, default=0)
SCALE Default of SCALEi (real, default=0.0)
UNIT Default of UNITi (integer ≥ 0, default=0)
MODID Default of MODIDi (integer≥ -1,default=-1), see remark 11.
SUBCASEi Identification number of a subcase (integer ≥ 0, default=0)
STEPi Identification number of a step (integer ≥ 0, default=0)
MODEINCi Mode number if the selected step by SUBCASEi and STEPi or subcase by SUBCASEi is
a result of buckling analysis or modal analysis, increment number if the selected result is
from a static analysis. (integer ≥ 0, default=0)
SETIDi Identification number of a SET1 or SET3 bulk entry (integer ≥ 0, default = 0). When it
is defined, only the grid points with the id listed in SET1 or SET3 have geometric
imperfection effect. If a SET3 is used, it must be GRID type.
SCALEi Scale factor (real, default = 0.0)
UNITi Imperfection file unit number specified by ASSIGN HDF5IN, INPUTT2 or IMPFIN
FMS command.
MODIDi Module ID (integer ≥ -1,default=-1), see remark 11.
Main Index
1948 IMPGEOM
Defines Geometric Imperfection
Remarks:
1. All IMPGEOM identification numbers must be unique. An IMPGEOM entry is referenced by
IMPERFECT case control directly or by an IMPCASE bulk entry.
2. Geometric imperfection effect is applied to grid points as coordinates variation, the variation is
superposed by eigenvectors of multiple modes or displacement of increments defined in multiple
continuation lines.
3. An imperfection input file can be an MSC Nastran HDF5 result file, a Nastran op2 file or a text based
file called IMPF. To use it, an ASSIGN HDF5IN, INPUTT2 or IMPFIN FMS command is
required.
4. The imperfection input file of HDF5 or op2 can be a result file of SOL 101, 103, 105 or a SOL 400
with ANALYSIS type of BUCK, MODES, STATIC, NLSTATIC or NLTRAN, and must contain
eigenvectors or displacement results.
5. IMPF file format is described in remark 12. It can be DISP format or GEOM format. If an IMPF file
is used in an IMPGEOM entry, only one continuation line of IMPGEOM is allowed, and
SUBCASEi, STEPi and MODEINCi are ignored. If format is GEOM, SCALE and SCALEi are
ignored too.
6. SUBCASEi must be specified if the imperfection input file is an op2 or hdf5 file.
7. STEPi is ignored when the imperfection input file is a result of SOL 101, 103 or 105. It must be
specified for a SOL 400 result file.
8. MODEINCi is ignored when the file is a result of SOL 101 or a linear static step of SOL 400. It is
required for other cases if the imperfection file is an hdf5 or op2 file.
9. UNITi must be specified if UNIT is 0 or not specified.
10. Geometric imperfection is applied to residual structure for superelement models. In the case of part
superelement, it is advised to adjust boundary grid point searching tolerance due to geometry
changing. This can be done by adding or modifying SEBULK or SECONCT entries.
11. MODID and MODIDi are only used when modules are present. -1 means the whole model, 0 or a
positive number is a module identification number.
12. Format of IMPF file
The IMPF file is a csv-like file, delimiters of a line can be spaces, a comma or a tab space. A line
starting with a “$” or “#” is a comment line. If the first line is a comment line and contains string
“GEOM” or “GRID”, then it is a GEOM file, i.e., the grid coordinates provided here will replace the
grid coordinates in the FE model; otherwise it is a DISP file, i.e., the displacements provided in the
file will be superimposed to the coordinates of the corresponding grids.
For each line, the first column is grid point id, followed by x,y and z. For DISP format, x,y and z are
coordinate variations from the original coordinates, and coordinate system is MSC Nastran global
system, this means that x,y,z are in the coordinate system indicated by CD field of GRID entries in
the original input file. For GEOM format, x,y and z are “imperfect” coordinates of the grid points,
coordinate system is MSC Nastran input system, this means the values of x,y,z respect CP field of the
GRID entries in the original input file.
Main Index
IMPGEOM 1949
Defines Geometric Imperfection
When modules are present, BEGIN MODULE=modid and ENDMODULE can be used to specify
module id for a section of grids.
Below is a DISP format of IMPF file.
disp_1.impf
--------------------------------------------------------------------------------
18 , 0.000000000000E+00 , 0.000000000000E+00 , 0.000000000000E+00
19 , 0.000000000000E+00 , 0.000000000000E+00 , 0.000000000000E+00
20 , 1.882586315422E-04 , -1.382379038267E-03 , -5.111620104649E-05
21 , 3.080245224512E-04 , -1.360710847814E-03 , -5.111620104647E-05
22 , 4.254461607540E-04 , -1.328686826189E-03 , -5.111620104646E-05
23 , 5.396298968822E-04 , -1.286550695534E-03 , -5.111620104647E-05
24 , 6.497067236577E-04 , -1.234623137246E-03 , -5.111620104650E-05
25 , 7.548388899626E-04 , -1.173299351397E-03 , -5.111620104657E-05
26 8.542262765314E-04 -1.103046049026E-03 -5.111620104668E-05
27 , 9.471124853400E-04 , -1.024397900185E-03 -5.111620104681E-05
28 1.032790596252E-03 -9.379534647748E-04 -5.111620104691E-05
29 , 1.110608547111E-03 , -8.443706371464E-04 , -5.111620104698E-05
30 , 1.179974096322E-03 , -7.443616391243E-04 , -5.111620104702E-05
31 , 1.240359330172E-03 , -6.386875995705E-04 , -5.111620104705E-05
Below is a GEOM format of IMPF file.
geom_example.impf
--------------------------------------------------------------------------------
# GEOM
1, 0.000000000000E+00, 0.000000000000E+00, 0.000000000000E+00
2, 1.000000014901E-01, 4.367130542590E-24, 1.464331138939E-08
3, 2.000000029802E-01, 7.552163438029E-24, 3.787209513278E-08
4, 2.999999821186E-01, 8.873575793200E-24, 5.096678857312E-08
5, 3.999999463558E-01, 0.000000000000E+00, 0.000000000000E+00
6, 4.999999701977E-01, 0.000000000000E+00, 0.000000000000E+00
7, 5.999999642372E-01, 0.000000000000E+00, 0.000000000000E+00
8, 6.999999880791E-01, 0.000000000000E+00, 0.000000000000E+00
9, 7.999998927116E-01, 0.000000000000E+00, 0.000000000000E+00
10, 8.999999165535E-01, 0.000000000000E+00, 0.000000000000E+00
11, 9.999999403954E-01, 0.000000000000E+00, 0.000000000000E+00
12, 1.099999904633E+00, 0.000000000000E+00, 0.000000000000E+00
13, 1.199999928474E+00, 0.000000000000E+00, 0.000000000000E+00
14, 1.299999952316E+00, 0.000000000000E+00, 0.000000000000E+00
Impf file with modules, mod_example.impf
-----------------------------------------------------------------------
----
Main Index
1950 IMPGEOM
Defines Geometric Imperfection
# below lines are in module 0
1, 0.01, 0.0, 0.0
2, -0.001, -1.e-3, 0.0
……
# below are for module 10
begin module=10
1, -1.0000000E-2, 0.0000000E+00, 0.0000000E+00
2, -7.0000000E-02, 0.0000000E+00, 0.0000000E+00
3, -1.3900000E-01, 0.0000000E+00, 0.0000000E+00
……
endmodule
# below are for module 20
BEGIN MODULE 20
1, -1.0000000-3, 0.0000000E+00, 0.0000000E+00
2, -7.10E-02, 0.0000000E+00, 0.0000000E+00
3, -1.3900000E-01, 0.0000000E+00, 0.0000000E+00
ENDMODULE
……
Main Index
INCLUDE 1951
Insert External File
INCLUDE Insert External File
Inserts an external file into the input file. The INCLUDE statement may appear anywhere within the input
data file.
Format:
INCLUDE’filename’
Describer:
filename Physical filename of the external file to be inserted. The user must supply the name
according to installation or machine requirements. It is recommended that the
filename be enclosed by single right-hand quotation marks.
Example:
The following INCLUDE statement is used to obtain the Bulk Data from another file called
MYBULK.DATA:
SOL 101
CEND
TITLE = STATIC ANALYSIS
LOAD = 100
BEGIN BULK
INCLUDE ’MYBULK.DATA’
ENDDATA
Remarks:
1. INCLUDE statements may be nested; that is, INCLUDE statements may appear inside the external
file. The nested depth level must not be greater than 10.
2. The total length of any line in an INCLUDE statement must not exceed 72 characters. Long file
names may be split across multiple lines. For example the file:
/dir123/dir456/dir789/filename.dat
may be included with the following input:
INCLUDE ‘/dir123
/dir456
/dir789/filename.dat’
3. See the for more examples.
Main Index
1952 INFLCG
Airbag Cold Gas Inflator Model
INFLCG Airbag Cold Gas Inflator Model
Defines the cold gas-inflator characteristics of a COUPLE and/or GBAG subsurface. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
INFLCG INFLID TANKVOL INITPRES INITTEMP INITMAS C R
GASNAM
CP
Example:
INFLCG 11 0.875 131325 293 1.37 1.4 286
Describer Meaning
INFLID Unique number of an INFLCG entry. Referenced from ABINFL. (Integer > 0;
Required)
TANKVOL Tank Volume. (Real > 0; Required)
INITPRES Initial tank pressure. (Real > 0; Required)
INITTEMP Initial tank temperature. (Real > 0; Required)
INITMAS Initial gas mass of inflator. (Real > 0; Required)
, GASNAM Ratio of specific heat constants if real. Name of an INFLGAS entry if character. See
Remarks 4. and 5. (Real > 0 or 1)
C Specific heat at constant volume. See Remark 6. (Real > 0)
R Gas constant. See Remark 6. (Real > 0)
CP Specific heat at constant pressure. See Remark 6. (Real > 0)
Remarks:
1. The INFLCG entry can be referenced from an ABINFL entry.
2. When used in an Euler coupled analysis, the entry can only be used with the single material
hydrodynamic Euler solver using an EOSGAM (ideal gas) equation of state.
3. Either INITPRESS or INITMASS has to be specified, but not both. The relation between
INITMASS and INITPRESS is given by
INITMAS
INITPRES = R ---------------------------- INITTEMP
TANKVOL
Main Index
INFLCG 1953
Airbag Cold Gas Inflator Model
4. The cold gas inflator is a reservoir filled with high pressure gas. It is assumed that the volume stays
constant at TANKVOL. The mass inside the inflator will steadily decrease due to flow into the Euler
domain or to a GBAG. Due to inertia it can happen that the pressure of the inflator becomes less that
the outside pressure. In that case some inflow into the inflator occurs. Transport between inflator and
the Euler domain or GBAG is based on the constancy of total temperature. This is equivalent to the
pressure method.
5. If this field contains a real entry real or is left blank, the inflator gas constants are given on the
INFLTR entry itself. Otherwise, the entry will be read as the name of an INFLGAS entry. In this
case, the remaining entries must be left blank.
6. Specify only two of the four gas constants. They are related as:
cp
= ----- R = cp – c
c
Main Index
1954 INFLFRC
Hybrid Inflator Gas Fraction Definition
INFLFRC Hybrid Inflator Gas Fraction Definition
Defines the gas fractions as a function of time for hybrid inflators. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
INFLFRC FRACID TYPE
“TIME” TIME1 FRAC1 FRAC2 FRAC3 etc.
“TIME” TIME2 FRAC1 FRAC2 FRAC3 etc.
Example:
INFLFRC 12
TIME 14.0E-3 11.342 13.391 9.626 57.019 7.31 1.312
0.0 0.1 0.2
TIME 14.1E-3 43.332 6.2817 4.5155 26.747 3.4291 0.4898
15.077 0.0 0.4
Describer Meaning
FRACID Unique number of an INFLFRC entry.(Integer > 0, required.)
TYPE Specifies whether mass fractions or molar fractions will be given (Character,
default=MASS.)
MASS The fractions on INFLFRC are mass fractions.
MOLAR The fractions on INFLFRC are molar fractions. See Remark 5.
TIMEID Defines a new line of data (Character, required.)
TIME Specifies that data for a new time increment will be given. See Remark 3.
TIMEi Time for which the gas fractions are given. (Real0.0, required.)
FRACi Fraction of gas i at the specified time..See Remark 7. (Real0.0, required.)
Remarks:
1. The INFLFRC entry is referenced with FRACID from an AIRBAG entry with the option
“INFLATOR” or from INFLHB.
2. Fraction values of the inflowing gas will be linearly interpolated between the specified time
increments.
3. Use as many continuation lines as necessary to completely define the gas fractions. The data for a time
step are preceded by a TIME keyword. Missing entries will be set to 0.0.
Main Index
INFLFRC 1955
Hybrid Inflator Gas Fraction Definition
4. The order of the gases for which the fractions are specified is identical to the order in which the gases
are specified on the AIRBAG entry with the option “INFLATOR”.
5. At least one line of gas fractions must be given.
6. If molar fractions (TYPE=MOLAR) are to be used, the universal gas constant must be specified
through PARAM, UGASC.
7. At least one of the fractions for each time step must have a value greater than 0.0.
8. Fractions for each timestep should add up to 1.0. If this is not the case, they will be scaled so that
they do.
Main Index
1956 INFLGAS
Inflator Gas Definition
INFLGAS Inflator Gas Definition
Defines a thermically ideal gas to be used with a standard or hybrid inflator. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
INFLGAS GASNAM TYPE VALUE CPGAS V1 V2 V3 V4
Example:
INFLGAS 101 RSPEC 189. CONSTAN 846.
T
Describer Meaning
GASNAM Unique number of an INFLGAS entry. (Integer; Required)
TYPE Specific gas constant or molar weight specified. (Character; RSPEC)
RSPEC Specific gas constant
MOLWT Molar weight, see Remark 2.
VALUE Value of the variable TYPE. (Real > 0; Required)
CPGAS The variation of the specific heat constant at constant pressure. (Character;
CONSTANT)
CONSTANT The specific heat is constant and specified in V1.
TABLE The specific heat constant is temperature-dependent. V1 is the number
of a TABLED1 entry giving the variation of the specific heat with the
temperature.
POLY The specific heat constant is temperature-dependent. V1 through V4
are the coefficients of a polynomial expression, see Remark 3.
V1 The specific heat constant, the number of a TABLED1 entry or the first polynomial
coefficient, depending on the value of CPGAS. (Real or Integer > 0; Required)
V2, V3, V4 Coefficients of polynomial expression when CPGAS equals POLY. (Real; 0.0)
Remarks:
1. INFLGAS can be referenced by an INFLTR, INFLHB or INITGAS entry.
2. When the molar weight is given, the universal gas constant R uni must be specified using PARAM,
UGASC, so that:
R spec = R uni MOLWT
3. A polynomial expression for c p is given by:
Main Index
INFLGAS 1957
Inflator Gas Definition
2 V4
c p t = V1 + V2 T + V3 T + -------
2
T
4. The specific heat constant at constant volume c is calculated from the specific heat constant at
constant pressure c p , the universal gas constant and the molecular weight according to:
c = c p T – R spec
5. The ratio of specific heats is given as:
= cp c
Main Index
1958 INFLHB
Hybrid Inflator Model
INFLHB Hybrid Inflator Model
Defines the hybrid-inflator characteristics of a COUPLE and/or GBAG subsurface. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
INFLHB INFLHID MASFLRT TBMPT TEMPC FRAC
GASNAM1 GASNAM2 GASNAM3 -etc.-
Example:
INFLHB 9 15 650. 12
22 25 3
Describer Meaning
INFLID Unique number of an INFLHB entry. (Integer > 0; Required)
MASFLRT Table number of a TABLED1 entry specifying the massflow-rate as a function of time.
(Integer > 0; Required)
TEMPT Table number of a TABLED1 entry specifying the static temperature of the inflowing
gas as a function of time. See Remark 3. (Integer > 0)
TEMPC Constant value of the temperature of the inflowing gas. See Remark 3. (Real > 0.0)
FRAC Number of an INFLFRC entry specifying the fractions of the inflowing gas as a
function of time. (Integer > 0; Required)
GASNAMi ID of an INFLGAS entry. See Remark 4. (Integer)
Remarks:
1. The INFLHB entry can be referenced from a ABINFL entry.
2. When used in an Euler coupled analysis, the entry can only be used with the single material
hydrodynamic Euler solver using an EOSGAM (ideal gas) equation of state.
3. Either TEMPC or TEMPT must be specified. The INFLHB entry uses the specified temperature as
the static temperature of the inflowing gas. In literature the static temperature is also known as total-
, rest-, or stagnation temperature and refers to the temperature of the gas when brought to rest from
its moving condition as opposed to the dynamic temperature that refers to the temperature of the
moving gas.
4. At least one inflator gas must be specified using an INFLGAS entry. There is no limit to the number
of inflator gases per INFLHB.
Main Index
INFLTNK 1959
Airbag Tanktest Inflator Model
INFLTNK Airbag Tanktest Inflator Model
Defines the Tanktest-inflator characteristics of a COUPLE and/or GBAG subsurface. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
INFLTNK INFLID METHOD TPTABLE TANKVOL INFLMAS INITPRES ENDTPRES INITTEMP
ENDTEMP c R cp IPTABLE INFLPRES INFLTEMP
INFLAREA SFTP SFIP
Example:
INFLTNK 111 AVTEMP 10 0.12 0.01 0.0
1.4 286.
See
Describer Meaning
INFLID Unique number of an INFLTNK entry. (Integer > 0; Required)
METHOD Method of calculating the mass-flowrate: (Character; Required)
AVTEMP Average Temperature Method
INFPRES Inflator Pressure Method
TPTABLE Table number of a TABLED1 entry specifying the tank pressure as a function of time.
(Integer > 0; Required)
TANKVOL Tank Volume. (Real > 0; Required)
INFLMAS Total gas mass generated by inflator. (Real > 0; Required)
INITPRES Initial tank pressure. See Remark 3. (Real > 0; Required)
ENDPRES End tank pressure. See Remarks 4. and 5. (Real > 0; Required)
INITTEMP Initial tank temperature. See Remark 5. (Real > 0; Required)
ENDTEMP End tank temperature. See Remark 5. (Real > 0; Required)
Ratio of specific heat constants. See Remark 7. (Real > 0)
c Specific heat at constant volume. See Remark 7. (Real > 0)
R Gas Constant. See Remark 7. (Real > 0; Required)
cp Specific heat at constant pressure. See Remark 7. (Real > 0)
IPTABLE Table number of a TABLED1 entry specifying the inflator pressure as a function of time.
See Remark 5. (Integer > 0; Required)
INFLPRES Initial inflator pressure. See Remarks 5. and 6. (Real > 0; Required)
Main Index
1960 INFLTNK
Airbag Tanktest Inflator Model
Describer Meaning
INFLTEMP Temperature of inflowing gas: See Remark 5. (Real > 0 or Character; ATM)
ATM Use average temperature of AVTEMP method.
Real value User specified temperature.
INFLAREA Total area of inflator holes. See Remark 5. (Real > 0; Required)
SFTP Scale factor for tank pressure. See Remark 5. (Real > 0; 1.0)
SFIP Scale factor for inflator pressure. See Remark 5. (Real > 0, 1.)
Remarks:
1. The INFLTNK entry can be referenced from an ABINFL entry.
2. When used in an Euler coupled analysis, the entry can only be used with the single material
hydrodynamic Euler solver using an EOSGAM (ideal gas) equation of state.
3. The initial tank pressure entry (INITPRES) is interpreted as an absolute pressure and used to define
reference pressure at t=0 in the tank. The different between INITPRES and the pressure value at t=0
from the table will be added to the entire pressure curve of TPTABLE.
4. The end tank pressure entry (ENDPRES) is interpreted as an absolute pressure at t=tend of tank
pressure table (TPTABLE). This value is used for calculation of total generated mass in the tank.
5. This field must be specified only when Inflator Pressure Method (INFPRES) is defined in the
METHOD field.
6. The initial inflator pressure entry (INFLPRES) is interpreted as an absolute pressure and used to
define reference pressure at t=0 in the inflator. The different between INFLPRES and the pressure
value at t=0 from the table will be added to the entire pressure curve of IPTABLE.
7. Specify only two of the four gas constants. They are related as:
cp
= ----- R = cp – c
c
Main Index
INFLTR 1961
Airbag Inflator Model
INFLTR Airbag Inflator Model
Defines the inflator characteristics of a COUPLE and/or GBAG subsurface. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
INFLTR INFLID MASFLRT TEMPT TEMPC c R cp
GASNAME
MID
Example:
INFLTR 5 100 907.0 1.5 283.0
0 0 0
Describer Meaning
INFLID Unique number of an INFLTR entry. (Integer > 0; Required)
MASFLRT Table number of a TABLED1 entry specifying the massflow-rate as a function of time.
(Integer > 0; Required)
TEMPT Table number of a TABLED1 entry specifying the static temperature of the inflowing
gas as a function of time. See Remark 3. (Integer > 0)
TEMPC Constant value of the static temperature of the inflowing gas. See Remark 3. (Real > 0)
, GASNAM Ratio of specific heat constants if real. Name of an INFLGAS entry if character. See
Remarks 4. and 5. (Real > 0 or Character)
c Specific heat at constant volume. See Remark 5. (Real > 0)
R Gas constant. See Remark 5. (Real > 0)
Specific heat at constant pressure. See Remark 5. (Real > 0)
MID Material MATDEUL ID of the Inflator material. See Remark 2. Only used for
MMHYDRO solver. (Integer > 0)
Remarks:
1. The INFLTR entry can be referenced from an ABINFL entry.
2. When used in combination with the single material hydrodynamic Euler solver an EOSGAM (ideal
gas) equation of state is required. In that case the material number MID can be left blank. When
using the Multi-material solver the Material number MID has to point to one of the Eulerian
materials and the equation of state of that material has to be of type EOSGAM. The Multi-material
solver does not allow the use of gas fractions.
Main Index
1962 INFLTR
Airbag Inflator Model
3. Either TEMP-C or TEMP-T must be specified. The INFLTR entry uses the specified temperature
as the static temperature of the inflowing gas. In literature the static temperature is also known as
total-, rest-, or stagnation temperature and refers to the temperature of the gas when brought to rest
from its moving condition, as opposed to the dynamic temperature which refers to the temperature
of the moving gas.
4. If this field contains a real entry real or is left blank, the inflator gas constants are given on the
INFLTR entry itself, see Remark 5. Otherwise, the entry will be read as the name of an INFLGAS
entry. In this case, the remaining entries must be left blank.
5. Specify only two of the four gas constants. They are related as:
cp
= ----- R = cp – c
c
Main Index
INITGAS 1963
Gasbag or Coupling Surface Inital Gas Fraction Definition
INITGAS Gasbag or Coupling Surface Inital Gas Fraction Definition
Specifies the initial gas composition inside a gasbag or Euler coupling surface. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
INITGAS INTID GASNAM1 FRAC1 GASNAM2 FRAC2 -etc.
Example:
INITGAS 4 14 0.4 32 0.11
Describer Meaning
INTID Unique number of an INITGAS entry. (Integer > 0; Required)
GASNAMi ID of an INFLGAS entry. See Remark 3. (Integer > 0)
FRACi Mass fraction of gas i. See Remark 4. (Real > 0.0)
Remarks:
1. The INITGAS entry can be used to specify the initial gas composition for a gasbag or for an Eulerian
coupling surface. The INTID must be referenced either from a GBAG cad or a COUPLE entry.
2. Use as many continuation lines as necessary to completely define the gas fractions.
3. At least one INFLGAS reference must be given.
4. Fractions should add up to 1.0. If this is not the case, they will be scaled so that they do.
Main Index
1964 IPSTRAIN
Initial Equivalent Plastic Strain Values in SOL 400
IPSTRAIN Initial Equivalent Plastic Strain Values in SOL 400
Defines initial equivalent plastic strain values. This is the initial plastic strain option used in SOL 400 only.
(NOTE: This entry is SINGLE FIELD ONLY! Double field will fatal)
Format:
1 2 3 4 5 6 7 8 9 10
IPSTRAIN EID1 EID2 INT1 INTN LAY1 LAYN STRAIN
Example:
IPSTRAIN 2001 2020 1 4 1 5 0.025
Describer Meaning
EID1 First Element ID to which these strains apply. (Integer > 0)
EID2 Last Element ID to which these strains apply. (Integer; Default = EID1)
INT1 First Integration point for which the strain applies. (Integer > 0; Default = 1)
INTN Last Integration point for which the strain applies. (Integer > 0; Default = 4)
LAY1 First element layer for which the strain applies. (Integer > 0; no Default. Enter zero or
leave blank if the model does not contain beams or shells.)
LAYN Last element layer for which the strain applies. (Integer > 0; no Default. Enter zero or
leave blank if the model does not contain beams or shells.)
STRAIN Equivalent plastic strain value at start of analysis. (Real; Default is 0.0)
Remarks:
1. This entry only applies to SOL 400 advanced nonlinear elements (selected with PSHLN1, PSLDN1,
etc.) and is ignored for other solutions.
2. This entry is normally used for metal forming and represents the amount of plastic deformation that
the model was previously subjected to. It is used in work (strain) hardening models.
Main Index
ISTRESS 1965
Initial Stress Values in SOL 400
ISTRESS Initial Stress Values in SOL 400
Defines initial stress values. This is used in SOL 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
ISTRESS EID1 EID2 INT1 INTN LAY1 LAYN STRESS1 STRESS2
STRESS3 STRESS4 STRESS5 STRESS6 STRESS7
“COORD” CID
Example:
ISTRESS 2001 2020 1 4 1 5 45000. -2000.
0.0 4500. 0.0 2350.
Describer Meaning
EID1 First Element ID to which these stresses apply. (Integer > 0)
EID2 Last Element ID to which these stresses apply. (Integer; Default = EID1)
INT1 First Integration point for which the stress applies. (Integer > 0; Default = 1)
INTN Last Integration point for which the stress applies. (Integer > 0; Default = 4)
LAY1 First element layer for which the stress applies. (Integer > 0; no Default. Enter zero or
leave blank if the model does not contain beams or shells.)
LAYN Last element layer for which the stress applies. (Integer > 0; no Default. Enter zero or
leave blank if the model does not contain beams or shells.)
STRESS(i) Up to 7 stress components may be entered. (Real; Default = 0.0)
"COORD" Indicate that this line defines coordinate system in which STRESS(i) are evaluated
CID = -1: element coordinate; = 0: basic coordinate (Integer≥ -1 ≤ 0; default=-1 for
CQUAD4 and TRIA3 only)
Remarks:
1. This entry only applies when using SOL 400 and is ignored for other solutions.
2. Initial stresses must be self-equilibrating and may not produce material nonlinearity.
3. Stress components are as follows:
Definitions:
s - normal type stress
t - shear type stress
x,y,z in basic coordinate system
1,2,3 in element local system
Main Index
1966 ISTRESS
Initial Stress Values in SOL 400
3D solid elements (for example type 7)
1 - sxx
2 - syy
3 - szz
4 - txy
5 - tyz
6 - tzx
7 - hydrostatic pressure (Herrmann elements only, otherwise 7 should be blank)
Thick shells (for example type 75)
1 - s11
2 - s22
3 - t12
4 - t23
5 - t31
Thin shells (for example type 72)
1 - s11
2 - s22
3 - t12
Beams (for example type 14 or 98)
1 - s - axial
2 - t - twist
4. STRESS(i) by default are in element coordinate (CID=-1); if CID=0, STRESS(i) will be transformed
from basic to element coordinate, for CQUAD4 and CTRIA3 only.
Main Index
ITER 1967
Iterative Solver Options
ITER Iterative Solver Options
Defines options for the iterative solver in SOLs 101, 106, 108, 111, 153, 200 and 400.
Format:
1 2 3 4 5 6 7 8 9 10
ITER SID
OPTION1VALUE1 OPTION2VALUE2 -etc.-
Example:
ITER 100
ITSEPS=1.0E0-7, MSGFLG=YES, PRECOND=BICWELL, IPAD=3
Describer Meaning
SID Set identification number. (Integer > 0).
PRECOND Preconditioner option. (Character; Default = “BIC” for real analysis, “BICCMPLX” for
complex analysis) See Remarks 3. and 4.
J Jacobi
JS Jacobi with diagonal scaling.
C Incomplete Cholesky.
CS Incomplete Cholesky with diagonal scaling.
RIC Reduced incomplete Cholesky.
RICS Reduced incomplete Cholesky with diagonal scaling.
BIC Block incomplete Cholesky for real problems.
BICCMPLX Block incomplete Cholesky for complex problems.
CASI Element-based third party iterative solver.
USER User given preconditioning. For direct frequency response (SOL 108): a
decomposition will be done for 1st frequency and the factor will be used
for all subsequent frequencies as a preconditioner with the iterative
solver. Other solutions require a DMAP alter. Please refer to the MSC
Nastran Numerical Methods User’s Guide description of the SOLVIT
module.
CONV Convergence criterion. (Character; Default = “AREX”)
AR r b where r is the residual vector of current iteration and b is the
initial load vector; internal criterion.
GE Alternative convergence criterion using geometric progression and the
differences between two consecutive solution updates; internal criterion.
Main Index
1968 ITER
Iterative Solver Options
Describer Meaning
AREX Same criterion as AR but with the additional consideration of the
external convergence criterion. See Remark 2. (Default).
GEEX Same criterion as GE but with the additional consideration of the
external convergence criterion. See Remark 2.
MSGFLG Message flag. (Character; Default = “NO”)
YES Messages will be printed for each iteration.
NO Only minimal messages will be printed from the iterative solver
(Default).
ITSEPS User-given convergence parameter epsilon. (Real > 0.0)
Default= 1.E-4 for PRECOND = "CASI"
Default= 1.E-8 for PRECOND = "CASI" with contact in the model
Default= 1.E-6 for all other PRECOND options
ITSMAX Maximum number of iterations. (Integer > 0; Default = N/4 where N is the number of
rows in the matrix)
IPAD Padding value for RIC, RICS, BIC, and BICCMPLX preconditioning. (Integer > 0)
Default = 0 for PRECOND = “RIC” or “RICS”
Default = 2 for PRECOND = “BIC” for purely three-dimensional models and three
for two-dimensional and mixed element models. IPAD may be reset
automatically by the program to the best value.
Default = 5 for PRECOND = “BICCMPLX”.
IEXT Extraction level in reduced incomplete Cholesky preconditioning. Block structuring
method in block incomplete Cholesky preconditioning. (Integer = 0 thought 7;
Default = 0)
0 Uses USET/SIL tables (Default).
1-7 The default value of 0 is recommended for all problems. The values 1 -
7 use a heuristic algorithm with a maximum block size equal to IEXT.
Although setting IEXT to a value other than 0 could lead to slightly
improved performance or reduced disk space use, it should be considered
exploratory without the expectation of a benefit.
PREFONLY Specifies early termination of the iterative solver. (Integer = 0 or -1; Default = 0)
0 Runs to completion (Default).
-1 Terminates after preface giving resource estimates.
Remarks:
1. The optional ITER Bulk Data entry is selected by the SMETHOD Case Control command and is
only required to override the defaults specified above.
Main Index
ITER 1969
Iterative Solver Options
2. The external epsilon is computed as follows:
r x
= -------------
b x
where r is the final residual vector, x is the final solution vector and b is the initial load vector (r, x)
indicates the inner product of r and x and (b, x) indicates the inner product of b and x.
3. See the MSC Nastran Numerical Methods User’s Guide for more information on these options.
4. The element-based iterative solver is primarily intended for the solution of very large solid element
structural analysis problems. The following restrictions apply:
• SOLs 101, 200 and 400 only.
• SOL 101 convergence parameter epsilon of 1.E-4 may be too large for some models and a
decrease to 1.E-8 may be necessary.
• Solver selection criteria and parameters cannot vary across subcases.
• No GENEL elements allowed
• x2GG/x2PP direct input matrix selection is allowed; however, the matrix size is limited to 100
grid points and must be symmetric.
• No ASET/OMIT reduction allowed
• Inertia relief is supported in SOL 101 for PARAM,INREL,-1. A SUPORT entry is required.
PARAM,INREL,-2 and -4 are not supported.
• No transfer functions allowed
• No RFORCE or PLOADX follower forces allowed
• Follower force stiffness must be symmetricized
• No heat transfer allowed
• DMP is not supported with the CASI solver.
Only BAR, BEAM, BUSH, ROD, CONMi, CONROD, DAMPi, ELASi, HEXA, MASSi,
PENTA, QUAD4, QUAD8, QUADR, SEAM, SHEAR, TRIA3, TRIA6, TRIAR, TETRA, VISC
and WELD elements are allowed.
5. GPGPU devices are not supported for iterative methods.
6. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
1970 LBSH3DG
Tables used by an NLBSH3D to find force as function of displacement, velocity and rotor speed
LBSH3DG Tables used by an NLBSH3D to find force as function of displacement, velocity and rotor speed
Defines the force tables of NLBSH3D nonlinear loads as function of relative displacement or velocity and
current rotor speed.
Format:
FORM = ASYM (Asymmetric matrix representation)
1 2 3 4 5 6 7 8 9 10
LBSH3DG LID FORM MIN_FREQ MAX_FREQ
P11 P12 P13 P14 P15 P16
P21 P22 P23 P24 P25 P26
P31 P32 P33 P34 P35 P36
P41 P42 P43 P44 P45 P46
P51 P52 P53 P54 P55 P56
P61 P62 P63 P64 P65 P66
FORM = DIAG (Only Diagonal terms representation)
1 2 3 4 5 6 7 8 9 10
LBSH3DG LID FORM MIN_FREQ MAX_FREQ
P11 P22 P33 P44 P55 P66
FORM = SYM (Symmetric matrix representation)
1 2 3 4 5 6 7 8 9 10
LBSH3DG LID FORM MIN_FREQ MAX_FREQ
P11
P21 P22
P31 P32 P33
P41 P42 P43 P44
P51 P52 P53 P54 P55
P61 P62 P63 P64 P65 P66
Describer Meaning
LID Load identification group number for a NLBSH3D. (Integer > 0; Required)
FORM Type of Input Curves. (Character; Default SYM)
SYM Symmetric, only lower triangular terms needed
DIAG Only diagonal terms are needed
Main Index
LBSH3DG 1971
Tables used by an NLBSH3D to find force as function of displacement, velocity and rotor speed
Describer Meaning
ASYM Asymmetric, all terms are needed
MIN_FREQ Minimum valid rotor speed for all the table lookups provided. (Real). See remark 4.
MAX_FREQ Max valid rotor speed for all the table lookups provided. (Real > 0.0 Required). Refer
remark 4.
Pij TABLED5 Id that provides TABLED1 ids as a function of rotor speed in cycles per unit
time. The TABLED1 will have force as a function of relative displacement and/or velocity.
Remarks:
1. Values for the nonlinear forces will be determined using interpolation based on rotor speed and
relative deflection/velocity of grid pair. If the rotor speed is beyond the range specified by
MIN_FREQ and MAX_FREQ, a FATAL message will be produced. (Extrapolation will NOT be
used beyond this range).
2. At selected rotor speeds (Xi), force vs displacement (for LID-1) or force vs velocity (for LID-2) tables
(TIDi) are defined on TABLED1 entries.
3. For an arbitrary rotor speed n, linear interpolation is used to determine the force fxn to be applied for
the displacement/velocity. The illustration shows a graphic representation of interpolation for force
vs displacement between tables defined for rotor speeds X1 and X2.
4. For SYNC analysis, rotor speed is obtained from NLFREQ / NLFREQ1 bulk data card. For ASYNC
analysis, rotor speed is obtained from RGYRO bulk data card.
5. All the tables (TABLED5 Pij) should provide lookup tables (TABLED1) for the range of rotor speeds
between Min_FREQ and Max_Freq.
Main Index
1972 LEAKAGE
Mass Loss Through Holes or Permeability of the GBAG or COUPLE Surface
LEAKAGE Mass Loss Through Holes or Permeability of the GBAG or COUPLE Surface
Defines the porosity model to be used with GBAG or COUPLE. Used in SOL 700 only.
Format:
1 2 3 4 5 6 7 8 9 10
LEAKAGE LID PORID SUBID PORTYPE PORTYPID COEFF COEFFV
Example:
LEAKAGE 7 100 365 PERMEAB 63 0.99
Describer Meaning
LID Unique number of a LEAKAGE entry. (Integer > 0; Required)
PORID Number of a set of LEAKAGE entries PORID must be referenced from a GBAG or
COUPLE entry. (Integer > 0; Required)
SUBID >0 Number of a BSURF, BCBOX, BCPROP, BCMATL or BCSEG,
which must be a part of the surface, as defined on the GBAG or
COUPLE entry.
=0 LEAKAGE definitions are used for the entire surface as defined on the
GBAG or COUPLE entry.
PORTYPE Defines the type of porosity. (Character; Required)
PORFLOW The PORFLOW logic is used to model a constant flow boundary in
the coupling surface. The flow boundary acts on the open area of the
coupling surface. The open area is equal to the area of the (sub) surface
multiplied by COEFFV. A hole can be modeled when COEFFV is set
to 1.0. A closed area results for COEFFV = 0.0. The characteristics of
the flow are defined on a PORFLOW entry, with ID as defined on the
PORTYPID.
PORFLWT The PORFLWT logic is used to model a time dependent flow
boundary in the coupling surface. The flow boundary acts on the open
area of the coupling surface. The open area is equal to the area of the
(sub) surface multiplied by COEFFV. A hole can be modeled when
COEFFV is set to 1.0. A closed area results for COEFFV = 0.0. The
characteristics of the flow are defined on a PORFLWT entry, with ID
as defined on the PORTYPID.
Main Index
LEAKAGE 1973
Mass Loss Through Holes or Permeability of the GBAG or COUPLE Surface
Describer Meaning
PORHOLE The PORHOLE logic can be used to model small holes in an air bag.
A BSURF defines the hole. The open area of the hole is equal to the
area of the (sub) surface multiplied by COEFFV. A value of COEFFV
= 1.0 will open up the complete area of the hole, while a value of
COEFFV = 0.0 will result in a closed hole. The characteristics for the
flow are defined on a PORHOLE entry, with ID as defined on the
PORTYPID.
PERMEAB The PERMEAB logic is used to model permeable air-bag material. The
permeable area can be defined for a BSURF or for the entire coupling
surface. The velocity of the gas flow through the (sub) surface is
defined as a linear or tabular function of the pressure difference
between the gas inside the air bag and the environmental pressure. The
function is specified on a PERMEAB entry, with ID as defined on the
PORYPID. The area actually used for outflow is the subsurface area
multiplied by the value of COEFFV
PORFGBG The PORFGBG logic can be used to model gas flow through a hole in
the coupling surface connected to a GBAG. A BSURF defines the hole.
The open area of the hole is equal to the area of the surface multiplied
by COEFFV. A value of COEFFV = 1.0 will open up the complete area
of the hole, while a value of COEFFV = 0.0 will result in a closed hole.
The characteristics for the flow are defined on a PORFGBG entry,
with ID as defined on the PORTYPID.
PERMGBG The PERMGBG logic is used to model gas flow through a permeable
area in the coupling surface connected to a GBAG. The permeable area
can be defined for a BSURF or for the entire coupling surface. The
velocity of the gas flow through the (sub) surface is defined as a linear
or tabular function of the pressure difference. This function is specified
on a PERMGBG entry, with ID as defined on the PORYPID. The area
actually used for outflow is the subsurface area multiplied by the value
of COEFFV.
PORFCPL The PORFCPL logic can be used to model gas flow through a hole in
the coupling surface connected to another coupling surface. A BSURF
defines the hole. The open area of the hole is equal to the area of the
(sub) surface multiplied by COEFFV. A value of COEFFV = 1.0 will
open up the complete area of the hole, while a value of COEFFV = 0.0
will result in a closed hole. The characteristics for the flow are defined
on a PORFCPL entry, with ID as defined on the PORTYPID.
PORHYDS Prescribes a hydrostatic pressure profile.
PORTYPID Porosity ID. References existing PORTYPE entry. (Integer > 0; Required)
COEFF Method of defining the porosity coefficient. (Character; CONSTANT)
Main Index
1974 LEAKAGE
Mass Loss Through Holes or Permeability of the GBAG or COUPLE Surface
Describer Meaning
CONSTANT The porosity coefficient is constant and specified on COEFFV.
TABLE The porosity coefficient varies with time. COEFV is the number of a
TABLED1 entry giving the variation with time.
COEFFV The porosity coefficient or the number of a TABLED1 entry depending on the COEFF
entry. (0.0 < Real < 1.0 or Integer < 0, 1.0)
Remarks:
1. The combination of multiple LEAKAGEs with different PORTYPEs is allowed.
2. It allows for setting up the exact same model for either a uniform pressure model (GBAG to
LEAKAGE) or an Eulerian model (COUPLE to LEAKAGE). It is then possible to set up the model
using the switch from full gas dynamics to uniform pressure (GBAGCOU).
The options PORFGBG and PERMGBG can be used to model air bags with multiple compartments.
Main Index
LOAD 1975
Static Load Combination (Superposition)
LOAD Static Load Combination (Superposition)
Defines a static load as a linear combination of load sets defined via FORCE, MOMENT, FORCE1,
MOMENT1, FORCE2, MOMENT2, DAREA (if these entries have been converted), PLOAD, PLOAD1,
PLOAD2, PLOADB3, PLOAD4, PLOADX1, SLOAD, RFORCE, and GRAV, ACCEL and ACCEL1
entries. In addition, all the thermal loads are also supported in the NASTRAN thermal analysis (SOL 153
and SOL 400 with analysis=hstat) such as QBDY1, QBDY2, QBDY3, QVECT, QVOL, SLOAD, QHBDY
Bulk Data entries.
Format:
1 2 3 4 5 6 7 8 9 10
LOAD SID S S1 L1 S2 L2 S3 L3
S4 L4 -etc.-
Example:
LOAD 101 -0.5 1.0 3 6.2 4
Describer Meaning
SID Load set identification number. (Integer > 0)
S Overall scale factor. (Real)
Si Scale factor on Li. (Real)
Li Load set identification numbers defined on entry types listed above. (Integer > 0)
Remarks:
1. The load vector P is defined by
P = S Si P Li
i
2. Load set IDs (Li) must be unique.
3. This entry must be used if acceleration loads (GRAV entry) are to be used with any of the other types.
4. In the static solution sequences, SID must be selected by the LOAD Case Control command. In
dynamic solution sequences the EXCITEID of a RLOADi or TLOADi may refer to a LOAD entry.
5. A LOAD may be referenced by another LOAD entry. Nested LOAD references are permitted. A
LOAD entry may not reference itself.
6. Note that the LOAD entry scaling for RFORCE uses the square root of the absolute S × Si in rotor
dynamics. Thus it is recommended that the LOAD entry not be used with RFORCE in rotor
dynamics with a value other than S=1.0 and Si=1.0 value. See Remark 21. of the RFORCE entry.
Main Index
1976 LOAD
Static Load Combination (Superposition)
7. LOAD Bulk Data entry will not combine an SPCD load entry. In the static solution sequences, the
set ID of the SPCD entry (SID) is selected by the LOAD Case Control command. In dynamic
analysis refer to Remark 2. of the SPCD entry.
8. If Modules are present then this entry may only be specified in the main Bulk Data section.
Main Index
LOADCLID 1977
Define Solution Load Combinations Using Part Load ID
LOADCLID Define Solution Load Combinations Using Part Load ID
Define a loading combination in PAA using the Load ID from SUBCASEs of the Parts.
Format:
1 2 3 4 5 6 7 8 9 10
LOADCLID LID S
S1 LID1
PARTNAME1
S2 LID2
PARTNAME2
Etc.
Example:
LOADCLID 202 1.00
1.00 101
first_part_name
1.0 301
second_part_name
Describer Meaning
LID Load set ID. Selected by the LOAD Case Control command. (Integer > 0)
S Overall scale factor. (Similar to LOAD Bulk Data entry) (Real 0)
Si Scale factor applied to Load ID loads. (Real 0)
LIDi Load ID specified during GENERATE by LOAD or CLOAD Case Control
directive. (Integer > 0)
PARTNAMEi Name of Part. (64 -Characters maximum)
Remarks:
1. LOADCLID entries are used only in the COMBINE and SOLVE steps of PAA processing.
2. The LOADCLID allows a loading combination to be created using the Load id (LIDi) from case
control. In each PAA run, each SUBCASE may have a LIDi provided. These are used by the
LOADCLID to define a loading combination.
3. As with other loading entries, all loads with the same LID are combined. Therefore, care must be
exercised when using loading combinations.
Main Index
1978 LOADCNAM
Define Solution Load Combination by Load Name
LOADCNAM Define Solution Load Combination by Load Name
Used only in PAA to define a loading combination using the LOADNAMEs used in Case Control for Parts.
Format:
1 2 3 4 5 6 7 8 9 10
LOADCNAM LID S
S1
LOADNAME1
PARTNAME1
S2
LOADNAME2
PARTNAME2
Etc.
Example:
LOADCNAM 101 1.00
2.5
gravity_x
outboard_right_side_engine_nacelle
1.1
gravity_x_on_another_part
second_part_name
Describer Meaning
LID Load set ID. Selected by the LOAD Case Control command. (Integer > 0)
S Overall scale factor. (Similar to LOAD Bulk Data entry) (Real ≠ 0)
Si Scale factor applied to LOADNAME loads. (Real ≠ 0)
LOADNAMEi Name of Load for that Part. (64 -Characters maximum)
PARTNAMEi Name of Part. (64 -Characters maximum)
Remarks:
1. LOADCNAM entries are used only in the COMBINE and SOLVE steps of PAA processing.
2. The LOADCNAM allows a loading combination to be created using the LOADNAME from case
control. In each PAA run, each SUBCASE may have a LOADNAME provided. These
LOADNAMEs are used by the LOADCNAM to define a loading combination.
3. All loads with the same LID are combined. Therefore, care must be exercised when using loading
combinations.
Main Index
LOADCSUB 1979
Define Solution Load Combinations Using Subcase Number
LOADCSUB Define Solution Load Combinations Using Subcase Number
Used only in PAA to define a loading combination using the LOADNAMEs used in Case Control for Parts.
Format:
1 2 3 4 5 6 7 8 9 10
LOADCSUB LID S
S1 SUB1
PARTNAME1
S2 SUB2
PARTNAME2
Etc.
Example:
LOADCSUB 1001 1.0
1.0 1
part_we_are_using_subcase_1_from
1.0 3
part_we_are_using_subcase_3_from
Describer Meaning
LID Load set ID. Selected by the LOAD Case Control command. (Integer > 0)
S Overall scale factor. (Similar to LOAD Bulk Data entry) (Real ≠ 0)
Si Scale factor applied to Load ID loads. (Real ≠ 0)
SUBi Subcase Number specified during GENERATE or COMBINE run. (Integer > 0)
PARTNAMEi Name of Part. (Character, C64)
Remarks:
1. LOADCSUB entries are used only in the COMBINE and SOLVE steps of PAA processing.
2. The LOADCSUB allows a loading combination to be created using the SUBCASE ids from case
control. In each PAA run, each SUBCASE has an id. These ids are used by the LOADCSUB to define
a loading combination.
3. All loads with the same LID are combined. Therefore, care must be exercised when using loading
combinations.
Main Index
1980 LOADCYH
Harmonic Load Input for Cyclic Symmetry
LOADCYH Harmonic Load Input for Cyclic Symmetry
Defines the harmonic coefficients of a static or dynamic load for use in cyclic symmetry analysis.
Format:
1 2 3 4 5 6 7 8 9 10
LOADCYH SID S HID HTYPE S1 L1 S2 L2
Example:
LOADCYH 10 1.0 7 C 0.5 15
Describer Meaning
SID Load set identification number. (Integer > 0)
S Scale Factor. (Real)
HID Harmonic. See Remark 6. (Integer or blank)
HTYPE Harmonic type. (Character: “C”, “S”, “CSTAR” “SSTAR”, “GRAV”, “RFORCE”, or
blank).
Si Scale factor on Li. (Real)
Li Load set identification number. See Remark 10. (Integer > 0)
Remarks:
1. The LOADCYH entry is selected with the Case Control command LOAD = SID.
2. If HTYPE is blank, the load will be applied to all applicable types in the problem.
3. If HTYPE is “GRAV” or “RFORCE”, GRAV or RFORCE entry loading will be used. Harmonic
loads for appropriate available harmonics will be generated automatically in these cases.
4. L1 and L2 may reference LOAD entries. However, the LOAD entry in such a case must not reference
load sets defined via RFORCE and/or GRAV entries.
5. If L1 refers to a set ID defined by an SPCD entry, the same ID must not reference any nonzero
loading specified by the other Bulk Data loading entries given via FORCE, MOMENT, FORCE1,
MOMENT1, FORCE2, DAREA (if these entries have been converted), MOMENT2, PLOAD,
PLOAD1, PLOAD2, PLOAD4, PLOADX, and SLOAD or converted DAREA entries. In other
words, an enforced deformation loading via the SPCD entry is specified by a load set ID L1 or L2
and a zero magnitude loading via a load (such as FORCE) with the same ID.
6. If HTYPE is “GRAV” or “RFORCE”, the entry in HID will be ignored and therefore may be blank.
S2 and L2 must be blank for this case.
7. Load set IDs L1 or L2 may not be referenced by load set ID L1 or L2 of LOADCYN entries.
8. If HTYPE = “C”, “S”, “CSTAR”, or “SSTAR”, the load on component (HTYPE) of harmonic
(HID) is L = S S1 L1 + S2 L2 .
Main Index
LOADCYH 1981
Harmonic Load Input for Cyclic Symmetry
9. S must be nonzero. In addition, either S1 or S2 must be nonzero.
10. L1 and L2 may reference any of the static or dynamic loading entries including GRAV and
RFORCE.
Main Index
1982 LOADCYN
Physical Load Input for Cyclic Symmetry
LOADCYN Physical Load Input for Cyclic Symmetry
Defines a physical static or dynamic load for use in cyclic symmetry analysis.
Format:
1 2 3 4 5 6 7 8 9 10
LOADCYN SID S SEGID SEGTYPE S1 L1 S2 L2
Example:
LOADCYN 10 1.0 1 R 0.5 17
Describer Meaning
SID Load set identification number. (Integer > 0)
S Scale Factor. (Real)
SEGID Segment identification number. (Integer)
SEGTYPE Segment type. (Character: “R”, “L”, or blank)
Si Scale Factors. (Real)
Li Load set ID numbers. See Remark 8. (Integer > 0)
Remarks:
1. The LOADCYN entry is selected by the LOAD Case Control command.
2. If SEGTYPE is blank, both R and L segments will be used in DIH-type symmetry.
3. L1 and L2 may reference LOAD entries. However, the LOAD entry in such a case must not reference
load sets defined via RFORCE and/or GRAV entries.
4. If L1 refers to a set ID defined by SPCD loading entry, the same ID must not reference any nonzero
loading specified by the other Bulk Data loading entries given via FORCE, MOMENT, FORCE1,
MOMENT1, FORCE2, DAREA (if these entries have been converted), MOMENT2, PLOAD,
PLOAD1, PLOAD2, PLOAD4, PLOADX1, and SLOAD entries. In other words, an enforced
deformation loading via the SPCD entry is specified by a load set ID L1 or L2 and a zero magnitude
loading via a load (such as FORCE) with the same ID.
5. Load set IDs L1 or L2 may not be referenced by load set ID L1 or L2 of LOADCYH entries.
6. The load on the segment (or half-segment) is L = S S1 L1 + S2 L2 .
7. S must be nonzero. In addition, either S1 or S2 must be nonzero.
8. L1 and L2 may reference any of the static or dynamic loading entries except GRAV and RFORCE.
9. For cyclic buckling loads may only be applied to the first segment and only zero harmonic loads may
be applied so the LOADCYH entry should be used.
Main Index
LOADCYT 1983
Table Load Input for Cyclic Symmetry
LOADCYT Table Load Input for Cyclic Symmetry
Specifies loads as a function of azimuth angle by references to tables that define scale factors of loads versus
azimuth angles. This entry is used only when STYPE = “AXI” on the CYSYM entry.
Format:
1 2 3 4 5 6 7 8 9 10
LOADCYT SID TABLEID1 LOADSET1 METHOD1 TABLEID2 LOADSET2 METHOD2
Example:
LOADCYT 10 19 27 21 26 1
Describer Meaning
SID Load set identification number. (Integer > 0)
TABLEIDi Table ID for table load input for load set Li. See Remark 3. (Integer > 0)
LOADSETi Load set Li. (Integer > 0)
METHODi Method of interpolation. See Remark 5. (Integer: 0 or 1; Default = 0)
0 Interpolate the load with the Fourier coefficients specified in the table up to
the specified number of harmonics. (Default)
1 Interpolate the magnitude of the load at corresponding grid points in all
segments.
Remarks:
1. The LOADCYT entry is selected by the LOAD Case Control command.
2. The load set ID given in fields 4 or 7 of this entry may refer to FORCE, MOMENT, PLOAD,
PLOAD2, PLOAD4, SPCD, TEMP, or TEMPP1 Bulk Data entries.
3. Either TABLED1 or TABLED2 type tabular data of azimuth angle (Xi) versus scale factors (Yi) may
be used. The azimuth angle values must be in degrees.
4. The scale factors given in the tables referenced by TABLEDi entries will be applied only to the
magnitudes of the loads defined by LOADSET IDs given in fields 4 or 7.
5. For grid point loading entries, (like FORCE, MOMENT, SPCD, and TEMP Bulk Data entries)
METHODi = 1 option should be used. For element loading entries (like PLOAD, PLOAD2,
PLOAD4, and TEMPP1 Bulk Data entries) either METHODi = 0 or METHODi = 1 option can
be used. In particular, if harmonic output of element stresses under temperature loading via
TEMPP1 Bulk Data entry, METHODi = 0 option should be used to specify TEMPP1 load set.
Main Index
1984 LSEQ
Static Load Set Definition
LSEQ Static Load Set Definition
Defines a sequence of static load sets.
Format:
1 2 3 4 5 6 7 8 9 10
LSEQ SID EXCITEID LID TID
Example:
LSEQ 100 200 1000 1001
Describer Meaning
SID Set identification of the set of LSEQ entries. See Remark 5. (Integer > 0)
EXCITEID The EXCITEID set identification assigned to this static load vector. See Remark 5.
(Integer > 0)
LID Load set identification number of a set of static load entries such as those referenced by
the LOAD Case Control command. (Integer > 0 or blank)
TID Temperature set identification of a set of thermal load entries such as those referenced
by the TEMP(LOAD) Case Control command. (Integer > 0 or blank)
Remarks:
1. LSEQ will not be used unless selected in the Case Control Section with the LOADSET command.
2. The number of static load vectors created for each superelement depends upon the type of analysis.
In static analysis, the number of vectors created is equal to the number of unique EXCITEIDs on all
LSEQ entries in the Bulk Data; in dynamic analysis, the number of vectors created is equal to the
number of unique EXCITEIDs on all RLOAD1, RLOAD2, TLOAD1, TLOAD2 and ACSRCE
entries in the Bulk Data.
3. EXCITEID may be referenced by CLOAD, RLOAD1, RLOAD2, TLOAD1, and TLOAD2 entries
in order to apply the static load in nonlinear, static and dynamic analysis.
4. Element data recovery for thermal loads is not currently implemented in dynamics.
5. The SID-EXCITEID number pair must be unique with respect to similar pairs on all other LSEQ
entries in the Bulk Data.
6. In a nonsuperelement analysis, LID and TID cannot both be blank. In superelement analysis, they
may both be blank as long as static loads are prescribed in the upstream superelements.
7. It is no longer necessary to employ LOADSET/LSEQ data to specify static loading data for use in
dynamic analysis. In the absence of LSEQ Bulk Data entries, all static loads whose load set IDs match
the EXCITEIDs on all RLOAD1, RLOAD2, TLOAD1, TLOAD2 and ACSRCE entries in the Bulk
Data are automatically processed.
Main Index
MASSSET 1985
Mass Combination Definition
Entries M - O
CREE
MASSSET Mass Combination Definition
The MASSSET bulk data entry defines a linear combination of mass cases to form the subcase-dependent
mass which is selected by associated MASSSET case control. The subcase mass is defined as follows by the
MASSSET bulk:
M ID = S0 Si M i
i
Where, i refers to the MASSID qualifier: i = 0 is the base mass case, i > 0 are the incremental mass cases.
ID’s of mass combinations defined by MASSSET bulk data entry and mass increments defined by MASSID
bulk data sections should be unique.
Format:
1 2 3 4 5 6 7 8 9 10
MASSSET ID S0 S1 ID1 S2 ID2 S3 ID3
S4 ID4
Example:
MASSSET 11 1.0 1.0 0 1.0 101
Describer Meaning
ID Set identification number referenced by MASSSET case control. (Integer > 0;
Required)
S0 The overall scale factor for the linear combination (Real >= 0.0; Default = 0.0)
Si The scale factor for the ith mass increment (Real >= 0.0; Default = 0.0)
IDi The MASSID for the ith mass increment (Integer > 0; No Default)
Main Index
1986 MATBV
Material Bulk Viscosity - SOL700
MATBV Material Bulk Viscosity - SOL700
Defines the bulk viscosity for materials. Used in SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
MATBV MID BULKTYP BULKQ BULKL CSCALE DMPFAC IIMMREL
Example:
MATBV 7 1.2
Describer Meaning
MID Material identification. See Remark 1. (Integer > 0, Required.)
BULKTYP Bulk viscosity type. (Character: default=DYNA)
DYNA Standard DYNA3D model.
DYTRAN Enhanced DYNA model.
BULKL Linear bulk-viscosity coefficient. (Real ≥ 0.0; default=1.0)
BULKQ Quadratic bulk-viscosity coefficient. (Real ≥ 0.0; default=0.0)
CSCALE When this material model is used with MEMB shell elements (See PSHELL1), the
compressive stresses in the principal directions will be scaled with this factor.
CSCALE=0.0 results in a tension only material. See Remark 2. (Real ≥ 0.0;
default=1.0)
DMPFAC When this material model is used with MEMB shell elements, damping is applied
to the stresses. DMPFAC = 0.05 results in 5% damping applied to membrane
stresses. See Remark 2. (Real ≥ 0.0; default=0.0)
IIMMREL Relaxation factor used with the Initial Metric Method. This option is only used
when this material model is used with MEMB shell elements and the IMM
method is activated. See Remark 3. (0.0 < Real < 1.0; default=1.0e-3)
Remarks:
1. The material number must refer to a basic material definition such as
MAT1/MAT2/MAT8/MATORT/MATHE.
2. For air bag modeling the following values of CSCALE and DMPFAC are suggested:
CSCALE = 0.1
DMPFAC= 0.05 to 0.20
3. The Initial Metric Method relaxation factor is used to slow down the expansion of the membrane
elements during the calculation. The default is sufficient in most simulations.
Main Index
MAT1 1987
Isotropic Material Property Definition
MAT1 Isotropic Material Property Definition
Defines the material properties for linear isotropic materials.
Format:
1 2 3 4 5 6 7 8 9 10
MAT1 MID E G NU RHO A TREF GE
ST SC SS MCSID
Example:
MAT1 17 3.+7 0.33 4.28 6.5-6 5.37+2 0.23
20.+4 15.+4 12.+4 1003
Describer Meaning
MID Material identification number. (Integer > 0)
E Young’s modulus. (Real > 0.0 or blank)
G Shear modulus. (Real > 0.0 or blank)
NU Poisson’s ratio. (-1.0 < Real < 0.5 or blank)
RHO Mass density. See Remark 5. (Real)
A Thermal expansion coefficient. (Real)
TREF Reference temperature for the calculation of thermal loads, or a
temperature-dependent thermal expansion coefficient. See Remarks 9. and 10.
(Real; Default = 0.0 if A is specified.)
GE Structural element damping coefficient. See Remarks 8., 9., and 4. (Real)
ST, SC, SS Stress limits for tension, compression, and shear are optionally supplied, used only
to compute margins of safety in certain elements; and have no effect on the
computational procedures. (Real > 0.0 or blank). See Remark 13.
MCSID Material coordinate system identification number. Used only for PARAM,CURV
processing. See Parameters. (Integer > 0 or blank)
Remarks:
1. The material identification number must be unique for all MAT1, MAT2, MAT3, MAT8, MAT9,
MATDIGI, MATG, MATHE, MATHP, MATNLE, MATORT, MATPE1, MATSMA,
MATUSR, MCOHE, MIXTURE, and MATD* entries.
2. The following rules apply when E, G, or NU are blank:
• E and G may not both be blank.
• If NU and E, or NU and G, are both blank, then both are set to 0.0.
Main Index
1988 MAT1
Isotropic Material Property Definition
• If only one E, G, or NU is blank, then it will be computed from the equation:
E = 2 1 + NU G . If this is not desired, then the MAT2 entry is recommended. If E, G,
or NU are made temperature dependent by the MATT1 entry, then the equation is applied to the
initial values only. Caution: Inconsistent E and G can result in NU >.5 which for three
dimensional elasticity results in negative stress for positive strain. This can cause large max ratios.
3. If values are specified for all of the properties E, G, and NU, then it is recommended that the
following relationship be satisfied:
E
1 – --------------------------------------- 0.01
2 1 + NU G
If this relationship is not desired, then the MAT2 entry is recommended.
It should also be noted that some of the properties are not applied in the stiffness formulation of
certain elements as indicated in Table 18. Therefore, it is recommended that only the applicable
properties be specified for a given element.
Table 18 Material Property Usage Versus Element Types
Element Entry E NU G
CROD Extension and Not Used Torsion Transverse
CBEAM Bending Shear
CBAR
CQUADi Membrane, including In-plane Shear, and Transverse Shear
CTRIAi Bending
CCONEAX
CSHEAR Not Used Shear
CRAC2D All Terms Not Used
CHEXA All Terms Not Used
CPENTA
CTETRA
CRAC3D
CTRIAX6 Radial, Axial, All Coupled Ratios Shear
Circumferential
4. MAT1 materials may be made temperature-dependent by use of the MATT1 entry. In SOL 106,
linear and nonlinear elastic material properties in the residual structure will be updated as prescribed
under the TEMPERATURE Case Control command.
5. The mass density RHO will be used to compute mass for all structural elements automatically.
6. Weight density may be used in field 6 if the value 1/g is entered on the PARAM,WTMASS entry,
where g is the acceleration of gravity (see Parameters).
7. MCSID must be nonzero if PARAM,CURV is specified to calculate stresses or strains at grid points
on plate and shell elements only.
Main Index
MAT1 1989
Isotropic Material Property Definition
8. To obtain the damping coefficient GE, multiply the critical damping ratio C/C0, by 2.0.
9. TREF and GE are ignored if the MAT1 entry is referenced by a PCOMP/PCOMPG entry.
10. TREF is used in two different ways (See Remarks 6. and 7. of TEMPERATURE Case Control entry
for details.):
• Except for SOL106 and SOL400 nonlinear analysis, TREF is used as the reference temperature
for the calculation of thermal loads. TEMPERATURE(INITIAL) may be used for this purpose,
in which case, TREF is ignored.
• In SOL106 and SOL400 nonlinear analysis, TREF is used only for the calculation of a
temperature-dependent thermal expansion coefficient. The reference temperature for the
calculation of thermal loads is obtained from the TEMPERATURE(INITIAL) set selection.
L-
----- = 1 + T
L0
A(T)
A T0
T
TREF T0 T
Figure 9-92 Use of TREF in Calculation of Thermal Loads
T = A T T – TREF – A T 0 T 0 – TREF
where T is requested by the TEMPERATURE(LOAD) command and T 0 is requested by the
TEMPERATURE(INITIAL) command.
Main Index
1990 MAT1
Isotropic Material Property Definition
Notes: A is a secant quantity.
TREF is obtained from the same source as the other material properties; e.g.,
ASTM, etc.
If A(T) constant, then T = A T – T 0
If PARAM,W4 is not specified, GE is ignored in transient analysis. See
Parameters.
11. In nonlinear static analysis (SOL 106) the QUAD4 and TRIA3 thermal loads are computed using
the secant (default) method. To use the more accurate integral method, specify
‘PARAM,EPSILONT,INTEGRAL’ in bulk data. See Parameters.
12. Negative values for ST, SC, and SS lead to no margins of safety being computed.
13. ST, SC, and SS are not used in SOL 400 with advanced elements. Use MATF instead.
Main Index
MAT1A 1991
Additional Material Properties for MAT1- SOL700
MAT1A Additional Material Properties for MAT1- SOL700
Specifies additional the material properties of MAT1 for solid elements. Use SOL700 only.
Format:
1 2 3 4 5 6 7 8 9 10
MAT1A MID EID
Example:
MAT1A 101 201
Describer Meaning
MID Identification number of MAT1. (Integer > 0; required.)
EID EOSxxx ID. (Integer > 0; required.)
Remarks:
1. MAT1A always required for solid elements when MATEP is used. However, when RYIELD option
of MATEP is set to VMISES, ORTHOCR or SOIL, MATEOS is not required.
Main Index
1992 MAT1F
Isotropic Material Frequency Dependence
MAT1F Isotropic Material Frequency Dependence
Specifies frequency-dependent material properties on MAT1 entry fields via TABLEDi entries.
Format:
1 2 3 4 5 6 7 8 9 10
MAT1F MID E G NU GE
Example:
MAT1F 33 15 22 16
Describer Meaning
MID Material property identification number that matches the identification number on
MAT1 entry. (Integer > 0)
E Identification number of a TABLEDi entry for the Young’s modulus. (Integer > 0 or
blank)
G Identification number of a TABLEDi entry for the shear modulus. (Integer > 0 or blank)
NU Identification number of a TABLEDi entry for the Poisson’s ratio. (Integer > 0 or blank)
GE Identification number of a TABLEDi entry for the structural damping coefficient.
(Integer > 0 or blank)
Remarks:
1. Fields 3, 4, etc., of this entry correspond, field-by-field, to fields 3, 4, etc., of the MAT1 entry
referenced in field 2. The value in a particular field of the MAT1 entry is replaced by the table
referenced in the corresponding field of this entry. Blank or zero entries mean that there is no
frequency dependence of the fields on the MAT1 entry.
2. The user is reminded that on the MAT1 entry, if any one of the entries E, G, or, NU is left blank,
they are connected by the relationship G=E/(2(1+NU)). Therefore, this entry requires that if any E,
G, or NU is
You might also like
- MSC Nastran 2023.1 Linear Static Analysis User Guide100% (1)MSC Nastran 2023.1 Linear Static Analysis User Guide727 pages
- Nastran 2013.1.1 Quick Reference GuideNo ratings yetNastran 2013.1.1 Quick Reference Guide3,774 pages
- MSC Nastran 2019 Quick Reference GuideNo ratings yetMSC Nastran 2019 Quick Reference Guide3,334 pages
- MSC - Nastran 2005 r3: Quick Reference GuideNo ratings yetMSC - Nastran 2005 r3: Quick Reference Guide2,192 pages
- MSC Nastran 2021.3: Quick Reference GuideNo ratings yetMSC Nastran 2021.3: Quick Reference Guide3,392 pages
- MSC Nastran 2022.1 Linear Static Analysis User GuideNo ratings yetMSC Nastran 2022.1 Linear Static Analysis User Guide716 pages
- Patran 2021 Interface To MSC NASTRAN Preference Guide Volume 1 Structural AnalysisNo ratings yetPatran 2021 Interface To MSC NASTRAN Preference Guide Volume 1 Structural Analysis636 pages
- MSC Nastran 2021.3 Linear Static Analysis User GuideNo ratings yetMSC Nastran 2021.3 Linear Static Analysis User Guide715 pages
- 6 MSC Nastran 2020 Linear Static Analysis User GuideNo ratings yet6 MSC Nastran 2020 Linear Static Analysis User Guide709 pages
- Docu87490 - Data Domain DD3300 Field Replacement and Upgrade Guide PDF0% (2)Docu87490 - Data Domain DD3300 Field Replacement and Upgrade Guide PDF204 pages
- Patran 2008 r1 PCL Reference Manual Volume 1: Function DescriptionsNo ratings yetPatran 2008 r1 PCL Reference Manual Volume 1: Function Descriptions2,210 pages
- MD/MSC Nastran 2010 Quick Reference Guide100% (1)MD/MSC Nastran 2010 Quick Reference Guide3,422 pages
- MSC - Access User's Manual Version 2005.1No ratings yetMSC - Access User's Manual Version 2005.1222 pages
- MSC Nastran 2012 Installation and Operations GuideNo ratings yetMSC Nastran 2012 Installation and Operations Guide404 pages
- MSC Nastran 2022.1 SOL 400 Getting Started GuideNo ratings yetMSC Nastran 2022.1 SOL 400 Getting Started Guide215 pages
- MD Nastran R3 Installation and Operations GuideNo ratings yetMD Nastran R3 Installation and Operations Guide416 pages
- DSM-00058-01 AMIGOS Graphics Operating System Reference Manual 199004No ratings yetDSM-00058-01 AMIGOS Graphics Operating System Reference Manual 199004205 pages
- Patran 2023.2 Reference Manual Part 4 Functional AssignmentsNo ratings yetPatran 2023.2 Reference Manual Part 4 Functional Assignments284 pages
- MD & MSC Nastran 2010 Installation and Operations GuideNo ratings yetMD & MSC Nastran 2010 Installation and Operations Guide418 pages
- Perhitungan Tugas Besar Geometri Jalan Raya (Andre Gunawan 1622201019)No ratings yetPerhitungan Tugas Besar Geometri Jalan Raya (Andre Gunawan 1622201019)77 pages
- Nastran 2018 Linear Static Analysis Guide PDFNo ratings yetNastran 2018 Linear Static Analysis Guide PDF759 pages
- Patran 2008 r1 Installation and Operations GuideNo ratings yetPatran 2008 r1 Installation and Operations Guide148 pages
- Exploring Social Psychology 8th Edition Myers Full DownloadNo ratings yetExploring Social Psychology 8th Edition Myers Full Download405 pages
- Annexure 9.13 - Spillway Pier, Breast Wall, Training Wall Solid Stresses100% (1)Annexure 9.13 - Spillway Pier, Breast Wall, Training Wall Solid Stresses6 pages
- Summons in A Civil Action - National Attorney Collection Services Inc KansasNo ratings yetSummons in A Civil Action - National Attorney Collection Services Inc Kansas3 pages
- Restauración de Poblaciones de Plantas AmenazadasNo ratings yetRestauración de Poblaciones de Plantas Amenazadas2 pages
- What Is Painting? Definition & Description - Eden GalleryNo ratings yetWhat Is Painting? Definition & Description - Eden Gallery3 pages
- Autodesk 3ds Max 2023: A Comprehensive Guide, 23rd EditionFrom EverandAutodesk 3ds Max 2023: A Comprehensive Guide, 23rd EditionNo ratings yet
- Engine, Turbine & Power Transmission Equipment World Summary: Market Values & Financials by CountryFrom EverandEngine, Turbine & Power Transmission Equipment World Summary: Market Values & Financials by CountryNo ratings yet
