MSC Nastran Quick Reference Guide

MSC Nastran 2014.1

Quick Reference Guide

June 30, 2015

Main Index
 Corporate Europe, Middle East, Africa
MSC Software Corporation MSC Software GmbH
4675 MacArthur Court, Suite 900 Am Moosfeld 13
Newport Beach, CA 92660 81829 Munich, Germany
Telephone: (714) 540-8900 Telephone: (49) 89 431 98 70
Toll Free Number: 1 855 672 7638 Email: [email protected]
Email: [email protected]

Japan Asia-Pacific
MSC Software Japan Ltd. MSC Software (S) Pte. Ltd.
Shinjuku First West 8F 100 Beach Road
23-7 Nishi Shinjuku #16-05 Shaw Tower
1-Chome, Shinjuku-Ku Singapore 189702
Tokyo 160-0023, JAPAN Telephone: 65-6272-0082
Telephone: (81) (3)-6911-1200 Email: [email protected]
Email: [email protected]

Worldwide Web
www.mscsoftware.com

Disclaimer
MSC Software Corporation reserves the right to make changes in specifications and other information contained
in this document without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only,
and are not intended to be exhaustive or to apply to any particular engineering problem or design. MSC Software
Corporation assumes no liability or responsibility to any person or company for direct or indirect damages resulting
from the use of any information contained herein.
User Documentation: Copyright  2015 MSC Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or
distribution of this document, in whole or in part, without the prior written consent of MSC Software Corporation is
prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from MSC
Software suppliers. Additional terms and conditions and/or notices may apply for certain third party software. Such
additional third party software terms and conditions and/or notices may be set forth in documentation and/or at
http://www.mscsoftware.com/thirdpartysoftware (or successor website designated by MSC from time to time).
PCGLSS 8.0, Copyright © 1992-2014, Computational Applications and System Integration Inc. All rights reserved.
PCGLSS 8.0 is licensed from Computational Applications and System Integration Inc. METIS is copyrighted by
the regents of the University of Minnesota. A copy of the METIS product documentation is included with this
installation. Please see “A Fast and High Quality Multilevel Scheme for Partitioning Irregular Graphs”. George
Karypis and Vipin Kumar. SIAM Journal on Scientific Computing, Vol. 20, No. 1, pp. 359-392, 1999. MPICH2 is
developed by Argonne National Laboratory. Copyright + 2002 University of Chicago.
MSC, Dytran, Marc, MSC Nastran, Patran, the MSC Software corporate logo, OpenFSI, e-Xstream, Digimat, and
Simulating Reality are trademarks or registered trademarks of the MSC Software Corporation in the United States
and/or other countries.
NASTRAN is a registered trademark of NASA. LS-DYNA is a trademark or registered trademark of Livermore
Software Technology Corporation. FLEXlm and FlexNet Publisher are trademarks or registered trademarks of
Flexera Software. All other trademarks are the property of their respective owners.

Revision 0. June 30, 2015

NA:V2014.1:Z:Z:Z:DC-QRG

Main Index
 C O N T E N T S
MSC Nastran Quick Reference Guide
Table of Contents

Table of Contents
Preface  List of Nastran Books, xx
 Technical Support, xxi
 Training and Internet Resources, xxii

1
nastran Command and  The nastran Command, 2
NASTRAN Statement
 The NASTRAN Statement, 13
- NASTRAN, 14 - UPDTTIM (128), 18
- BUFFSIZE (1), 15 - SMPYAD67 (129), 18
- F06 (2), 15 - MAXDBSET, 18
- NLINES (9), 15 - AUTOASGN (133), 18
- MAXLINES (14), 15 - TSTAMP (135), 18
- METIME (20), 15 - QUADINT (141), 18
- APP (21), 15 - SCR300 (142), 19
- MACHTYPE (22), 15 - LOCBULK (143), 19
- DIAGA (25), 15 - (144), 19
- CONFIG (28), 15 - BFGS (145), 19
- MESH (31), 15 - FBSMEM (146), 19
- ADUMi (46 - 54), 15 - UWM (147), 19
- HEAT (56), 15 - DBVERCHK (148), 20
- DIAGB (61), 15 - SCR300DEL (150), 20
- PUNCH (64), 15 - (151), 20
- MPYAD (66), 16 - DBLAMKD (155), 20
- SOLVE (69), 16 - (166), 20
- DELFF (77), 16 - LDQRKD (170), 21
- DBSET, 16 - OLDQ4K (173), 21
- DMAP (82), 16 - Q4TAPER (189), 21
- F04 (86), 16 - Q4SKEW (190), 21
- RADMTX (87), 16 - TETRAAR (191), 21
- RADLST (88), 17 - SCRSAVE (196), 21
- NEWHESS (108), 17 - MINFRONT (198), 22
- (109), 17 - NSEGADD (200), 22
- BUFFPOOL (114), 17 - CORDM (204), 22
- (119), 17 - (205), 22
- ATTDEL (124), 17 - DCMPSEQ (206), 22
- NOKEEP (125), 17 - USPARSE (209), 23
- SPARSE (126), 18 - PUNCHTYPE (210), 23

Main Index
 - CHEXAINT (212), 23 - KRYLOV5 (391), 28
- DISTORT (213), 23 - BARMASS (398), 28
- T3SKEW (218), 23 - DPBLKTOL (402), 28
- (219), 23 - OP2NEW (403), 28
- (220), 23 - DEF_DENS (408), 29
- (221), 23 - DEF_TECO (410), 29
- (253 - 262), 24 - DEF_TEIJ (411), 29
- MAXSET (263), 24 - DEF_DAMP (412), 29
- QUARTICDLM (270), 24 - OPTCOD (413), 29
- (273), 24 - , 29
- DBCFACT (274), 24 - (414), 29
- (275), 24 - OLDTLDMTH (428), 29
- SPLINE_METRICS (281), 24 - NONLRGAP (431), 29
- MINDEF (303), 24 - ESLNRO (443), 29
- MPERTURB (304), 24 - (444), 30
- (309), 25 - IFPSTAR, 30
- OLDRBE3 (310), 25 - MNLQ4C (445), 30
- TBCMAG (311), 25 - (446), 30
- INDEX (316), 25 - PARSLAVE(449), 31
- XMSG (319), 25 - (451), 31
- OLDDAREA (320), 25 - IFPBUFF(624), 31
- RSEQCONT (357), 25 - NONUPIV (653), 32
- QLHOUL (359), 26 - GPU_MIN_FRONT (655), 32
- PRTPCOMP (361), 26 - GPU_MIN_RANK (656), 32
- STRICTUAI (363), 26 - (662), 32
- STPFLG (366), 26 - SEGLOG(664), 33
- QRMETH (370), 26 - CNTBKCMP(666), 33
- , 26 - LMFBKCMP(676), 33
- PARAMCHK (372), 27 - FFOBKCMP(677), 33
- TZEROMAX (373), 27 - (679), 33
- NOLIN (386), 27 - (680), 34
- KRYLOV1 (387), 27 - (681), 34
- KRYLOV2 (388), 27 - (682), 34
- KRYLOV3 (389), 27 - RDBOTH(695), 34
- KRYLOV4 (390), 28 - S2SDEF(701), 34

2
File Management  Key to Descriptions, 36
Statements
 The File Management Section (FMS), 37
 File Management Statement Summary, 37
 File Management Statement Descriptions, 38
 File Management Statements, 42
- $, 42 - DBFIX, 71
- ACQUIRE, 43 - DBLOAD, 72
- ASSIGN, 44 - DBLOCATE, 75
- CONNECT, 52 - DBSETDEL, 78
- DBCLEAN, 56 - DBUNLOAD, 79
- DBDICT, 57 - DBUPDATE, 81
- DBDIR, 70 - DEFINE, 82

Main Index
 - ENDJOB, 85 - MEMLIST, 93
- EXPAND, 86 - PROJ, 94
- INCLUDE, 88 - RESTART, 95
- INIT, 89

3
Executive Control  Key to Descriptions, 98
Statements  Executive Control Section, 99
 Executive Control Statement Summary, 99
 Executive Control Statement Descriptions, 100
- $, 101 - ID, 127
- ALTER, 102 - INCLUDE, 128
- APP, 105 - LINK, 129
- CEND, 106 - MALTER, 131
- COMPILE, 107 - MODEL_CHECK, 135
- COMPILER, 111 - SOL, 138
- DIAG, 112 - SOL 600,ID, 141
- DOMAINSOLVER, 116 - SOL 700,ID, 161
- ECHO, 122 - SPARSESOLVER, 174
- ENDALTER, 123 - TIME, 178
- GEOMCHECK, 124

4
Case Control  Key to Descriptions, 180
Commands
 The Case Control Section, 181
 Case Control Command Descriptions, 181
 Case Control Command Summary, 183
 Subcase Definition, 183
 Data Selection, 184
 Output Selection, 189
 Superelement Control, 193
 Miscellaneous, 194
 Case Control Commands, 195
- $, 195 - ADAPT (Case), 227
- $S700, 196 - AECONFIG (Case), 228
- A2GG (Case), 207 - AERCONFIG (Case), 229
- ACCELERATION (Case), 208 - AEROF (Case), 230
- ACFPMRESULT (Case), 211 - AESYMXY (Case), 231
- ACPOWER (Case), 213 - AESYMXZ (Case), 232
- ACTIVAT (Case), 214 - AEUXREF (Case), 233
- ACTRIM (Case), 215 - ANALYSIS (Case), 234
- ADACT (Case), 216 - APRESSURE (Case), 243
- ADAMSMNF* (Case), 217 - AUTOSPC (Case), 244

Main Index
 - AUXCASE (Case), 247 - FLUX (Case), 338
- AUXMODEL (Case), 248 - FMETHOD (Case), 339
- AXISYMMETRIC (Case), 249 - FORCE (Case), 340
- B2GG (Case), 250 - FREQUENCY (Case), 343
- B2PP (Case), 251 - FRF (Case), 344
- BC (Case), 252 - GPFORCE (Case), 359
- BCHANGE (Case), 253 - GPKE (Case), 361
- BCONTACT (Case), 254 - GPRSORT (Case), 362
- BCONTACT (Case), 257 - GPSDCON (Case), 363
- BCMOVE (Case), 260 - GPSTRAIN (Case), 364
- BEGIN BULK (Case), 261 - GPSTRESS (Case), 365
- BOUTPUT (Case), 263 - GROUNDCHECK (Case), 366
- BSQUEAL (Case), 264 - GUST (Case), 367
- CAMPBELL (Case), 265 - GVECTOR (Case), 368
- CLOAD (Case), 266 - HADAPT (Case), 369
- CMETHOD (Case), 267 - HARMONICS (Case), 370
- CMSENRGY (Case), 268 - HDOT (Case), 371
- CSSCHD (Case), 271 - HISTOGRAM (Case), 372
- DATAREC (Case), 272 - HOUTPUT (Case), 374
- DBSAVE (Case), 273 - HTFLOW (Case), 375
- DEACTEL (Case), 275 - IC (Case), 376
- DEFORM (Case), 276 - ICF (Case), 378
- DESGLB (Case), 277 - INCLUDE (Case), 380
- DESMOD (Case), 278 - INTENSITY (Case), 381
- DESOBJ (Case), 279 - IRLOAD (Case), 382
- DESSUB (Case), 280 - K2GG (Case), 383
- DESVAR (Case), 281 - K2PP (Case), 384
- DISPLACEMENT (Case), 282 - K42GG (Case), 385
- DIVERG (Case), 287 - LABEL (Case), 386
- DLOAD (Case), 288 - LINE (Case), 387
- DRSPAN (Case), 289 - LOAD (Case), 388
- DSAPRT (Case), 290 - LOADNAME (Case), 389
- DSYM (Case), 292 - LOADSET (Case), 390
- ECHO (Case), 293 - M2GG (Case), 392
- EDE (Case), 295 - M2PP (Case), 393
- EKE (Case), 297 - MASTER (Case), 394
- ELSDCON (Case), 299 - MAXLINES (Case), 396
- ELSENS (Case), 300 - MAXMIN (Case), 397
- ELSUM (Case), 302 - MAXMIN (Case), 399
- ENDSTEP (Case), 304 - MAXMIN(DEF) (Case), 401
- ENDTIME (Case), 305 - MCFRACTION (Case), 404
- ENTHALPY (Case), 306 - MCHSTAT (Case), 407
- EQUILIBRIUM (Case), 307 - MEFFMASS (Case), 408
- ERP (Case), 308 - METHOD (Case), 410
- ESE (Case), 311 - MFLUID (Case), 411
- EXPORTLD (Case), 314 - MODALKE (Case), 412
- EXTSEOUT (Case), 316 - MODALSE (Case), 416
- FATIGUE (Case), 327 - MODES (Case), 420
- FBODYLD (Case), 330 - MODESELECT (Case), 421
- FLSFSEL (Case), 331 - MODTRAK (Case), 427
- FLSPOUT (Case), 333 - MONITOR (Case), 428
- FLSTCNT (Case), 336 - MPC (Case), 430

Main Index
 - MPCFORCES (Case), 431 - SEMGENERATE (Case), 504
- MPRES (Case), 434 - SEMREDUCE (Case), 505
- NLHARM (Case), 435 - SERESP (Case), 506
- NLIC (Case), 436 - SET (Case), 507
- NLLOAD (Case), 438 - SETP (Case), 509
- NLOPRM (Case), 439 - SETS DEFINITION (Case), 510
- NLPARM (Case), 442 - SKIP (Case), 511
- NLRESTART (Case), 443 - SMETHOD (Case), 512
- NLSTEP (Case), 445 - SPC (Case), 513
- NLSTRESS (Case), 446 - SPCFORCES (Case), 514
- NONLINEAR (Case), 447 - SPLINOUT (Case), 517
- NOUTPUT (Case), 448 - STATSUB (Case), 518
- NSM (Case), 449 - STEP (Case), 519
- OFREQUENCY (Case), 450 - STOCHASTICS (Case), 520
- OLOAD (Case), 452 - STRAIN (Case), 521
- OMODES (Case), 455 - STRESS (Case), 524
- OTIME (Case), 457 - STRFIELD (Case), 527
- OUTPUT (Case), 459 - SUBCASE (Case), 528
- OUTRCV (Case), 460 - SUBCOM (Case), 529
- P2G (Case), 461 - SUBSEQ (Case), 531
- PACCELERATION (Case), 462 - SUBSEQ1 (Case), 532
- PAGE (Case), 463 - SUBSTEP (Case), 533
- PARAM (Case), 464 - SUBTITLE (Case), 535
- PARTN (Case), 465 - SUPER (Case), 536
- PFGRID (Case), 466 - SUPORT1 (Case), 538
- PFMODE (Case), 468 - SVECTOR (Case), 539
- PFPANEL (Case), 472 - SVELOCITY (Case), 540
- PLOTID (Case), 475 - SYM (Case), 541
- POST (Case), 476 - SYMCOM (Case), 542
- PRESSURE (Case), 480 - SYMSEQ (Case), 543
- RANDOM (Case), 481 - TEMPERATURE (Case), 544
- RCROSS (Case), 482 - TERMIN (Case), 548
- REPCASE (Case), 484 - TFL (Case), 549
- RESVEC (Case), 485 - THERMAL (Case), 550
- RGYRO (Case), 487 - TITLE (Case), 551
- RIGID (Case), 488 - TRIM (Case), 552
- RSDAMP (Case), 490 - TRIMF (Case), 553
- SACCELERATION (Case), 491 - TRIMGRP (Case), 555
- SDAMPING (Case), 492 - TSTEP (Case), 556
- SDISPLACEMENT (Case), 493 - TSTEPNL (Case), 557
- SEALL (Case), 494 - TSTRU (Case), 558
- SEDAMP (Case), 495 - UNGLUE (Case), 559
- SEDR (Case), 496 - VCCT (Case), 560
- SEDV (Case), 497 - VECTOR (Case), 561
- SEEXCLUDE (Case), 498 - VELOCITY (Case), 562
- SEFINAL (Case), 500 - VUGRID (Case), 565
- SEKREDUCE (Case), 501 - WEIGHTCHECK (Case), 566
- SELGENERATE (Case), 502 - WETSENS (Case), 567
- SELREDUCE (Case), 503
 Case Control Applicability Tables, 569
 OUTPUT(PLOT) Commands, 586

Main Index
 - AXES, 588 - PERSPECTIVE, 603
- CAMERA, 590 - PLOT, 604
- CONTOUR, 591 - PLOTTER, 612
- CSCALE, 593 - PROJECTION, 613
- DISTORTION, 594 - PTITLE, 614
- FIND, 595 - SCALE, 615
- MAXIMUM DEFORM, 597 - SEPLOT, 616
- OCULAR SEPARATION, 598 - SET, 617
- ORIGIN, 599 - SEUPPLOT, 620
- ORTHOGRAPHIC, etc., 600 - STEREOSCOPIC, 621
- PAPER SIZE, 601 - VANTAGE POINT, 622
- PEN, 602 - VIEW, 623
 X-Y PLOT Commands, 625
 X-Y Output Command Summary, 626
- ALLEDGE TICS, 629 - XTITLE, 663
- BALL EDGE TICS, 630 - XYPAPLOT, 664
- BLEFT TICS, 631 - XYPEAK, 665
- BRIGHT TICS, 632 - XYPLOT, 666
- CAMERA, 633 - XYPRINT, 672
- CLEAR, 634 - XYPUNCH, 673
- CSCALE, 635 - XVALUE PRINT SKIP, 674
- CURVELINESYMBOL, 636 - YAXIS, 675
- DENSITY, 637 - YBDIVISIONS, 676
- LEFT TICS, 638 - YBINTERCEPT, 677
- LONG, 639 - YBGRID LINES, 678
- LOWER TICS, 640 - YBLOG, 679
- PENSIZE, 641 - YBMAX, 680
- PLOTTER, 642 - YBMIN, 681
- RIGHT TICS, 643 - YBTITLE, 682
- SEPLOT, 644 - YBVALUE PRINT SKIP, 683
- SEUPPLOT, 645 - YDIVISIONS, 684
- TALL EDGE TICS, 646 - YINTERCEPT, 685
- TCURVE, 647 - YGRID LINES, 686
- TLEFT TICS, 648 - YLOG, 687
- TRIGHT TICS, 649 - YMAX, 688
- UPPER TICS, 650 - YMIN, 689
- XAXIS, 651 - YPAPER, 690
- XBAXIS, 652 - YTAXIS, 691
- XBGRID LINES, 653 - YTDIVISIONS, 692
- XDIVISIONS, 654 - YTGRID LINES, 693
- XGRID LINES, 655 - YTINTERCEPT, 694
- XINTERCEPT, 656 - YTITLE, 695
- XLOG, 657 - YTLOG, 696
- XMAX, 658 - YTMAX, 697
- XMIN, 659 - YTMIN, 698
- XPAPER, 660 - YTTITLE, 699
- XTAXIS, 661 - YTVALUE PRINT SKIP, 700
- XTGRID LINES, 662 - YVALUE PRINT SKIP, 701
 OUTPUT(POST) Commands, 702
- SURFACE, 702
- VOLUME, 705

Main Index
 5
Parameters  Parameter Descriptions, 708
- ACEXTMTD, 708 - CDIF, 721
- ACEXTSET, 708 - CDITER, 721
- ACOUT, 708 - CDPCH, 721
- ACOWEAK, 709 - CDPRT, 722
- ACSYM, 709 - CFDIAGP, 722
- ADJMETH, 709 - CFRANDEL, 722
- ADMPOST, 709 - CHECKOUT, 722
- ADPCON, 710 - CK1, CK2, 723
- ADSTAT, 710 - CK3, 724
- AERODOF, 710 - CLOSE, 724
- AESDISC, 710 - CM1, CM2, 724
- AESMAXIT, 711 - COMPMATT, 724
- AESMETH, 711 - CONFAC, 725
- AESRNDM, 711 - COPOR, 725
- AESTOL, 711 - COSUBCYC, 725
- ALPHA1, ALPHA2, 711 - COSUBMAX, 726
- ALPHA1FL, ALPHA2FL, 712 - COUPMASS, 726
- ALTRED, 713 - CP1, CP2, 726
- ALTSHAPE, 713 - CQC, 727
- ARBMASP, 714 - CURV, 727
- ARBMFEM, 714 - CURVPLOT, 729
- ARBMPS, 714 - CWDIAGP, 730
- ARBMSS, 714 - CWLDIGNR, 730
- ARBMSTYP, 714 - CWRANDEL, 731
- ARF, 715 - DAMAGET, 731
- ARS, 715 - DBALL, 731
- ASCOUP, 715 - DBCCONV, 732
- ASING, 715 - DBCDIAG, 732
- AUNITS, 715 - DBCOVWRT, 732
- AUTOADJ, 715 - DBDICT, 732
- AUTOGOUT, 716 - DBDN, 733
- AUTOMSET, 717 - DBDRPRJ, 733
- AUTOQSET, 717 - DBDRVER, 733
- AUTOSPC, 718 - DBEXT, 733
- AUTOSPCR, 718 - DBRCV, 733
- AUTOSPRT, 718 - DBUP, 733
- BAILOUT, 718 - DDRMM, 733
- BEAMBEA, 719 - DELCLUMP, 734
- BEIGRED, 719 - DESPCH, 734
- BIGER, BIGER1, BIGER2, 719 - DESPCH1, 735
- BLADEDEL, 719 - DFREQ, 735
- BLADESET, 719 - DIROUT, 736
- BLDRSTRT, 720 - DOPT, 736
- BLDTHETA, 720 - DPEPS, 736
- BUCKLE, 720 - DPHFLG, 736
- CASIEMA, 720 - DSNOKD, 737
- CASPIV, 720 - DSO, 737
- CB1, CB2, 721 - DSZERO, 737

Main Index
 - DV3PASS, 738 - DYSHELLFORM, 752
- DYBEAMIP, 738 - DYSHGE, 752
- DYBLDTIM, 738 - DYSHNIP, 753
- DYBULKL, 738 - DYSHTHICK*, 753
- DYBULKQ1, 738 - DYSIGFLG, 753
- DYCMPFLG, 738 - DYSTATIC, 753
- DYCONECDT*, 739 - DYSTRFLG, 754
- DYCONENMASS*, 739 - DYSTSSZ, 754
- DYCONIGNORE*, 739 - DYTERMNDTMIN*, 754
- DYCONPENOPT*, 740 - DYTERMNENDMAS, 755
- DYCONRWPNAL*, 740 - DYTSTEPDT2MS*, 755
- DYCONSKIPRWG*, 740 - DYTSTEPERODE, 755
- DYCONSLSFAC*, 740 - ENFMETH, 755
- DYCONTHKCHG*, 741 - ENFMOTN, 756
- DYCOWPRD, 741 - EPPRT, 757
- DYCOWPRP, 741 - EPSILONT, 757
- DYDCOMP, 741 - EPZERO, 758
- DYDEFAUL, 741 - ERPC, 758
- DYDTOUT, DT, 742 - ERPREFDB, 758
- DYDYLOAD, 743 - ERPRHO, 758
- DYELAS1C, ITABLE, 744 - ERPRLF, 758
- DYELAS1F, IFOLLOW, 744 - ERROR, 758
- DYELAS1R, ICID, 744 - ESLFSAV, 759
- DYELPLET, RETAN, 744 - ESLMOVE, 759
- DYELPLFL, FAIL, 745 - ESLLCOMP, 759
- DYELPLSY, RSIGY, 745 - ESLMPC1, 760
- DYENDTIM, 745 - ESLOPTEX, 760
- DYENERGYHGEN, 745 - ESLPRT, 760
- DYENGFLG, 746 - ESLPRT1, 760
- DYHRGIHQ, 746 - ESLRCF,user_rc_file, 761
- DYHRGQH, 746 - ESLTOPCV, 761
- DYIEVERP, 746 - ESLUNT2, 761
- DYINISTEP*, 747 - ESLUNT1, 762
- DYLDKND, 747 - EST, 762
- DYMATS1, 747 - EULBND, 762
- DYMAXINT, 747 - EULBULKL, 763
- DYMAXSTEP*, 748 - EULBULKQ, 763
- DYMINSTEP*, 748 - EULBULKT, 764
- DYNAMES, 748 - EULSTRES, 764
- DYNEIPH, 748 - EUSUBCYC, 765
- DYNEIPS, 749 - EXTDR , 765
- DYNINT, 749 - EXTDROUT , 765
- DYNINTSL, 749 - EXTDRUNT, 766
- DYNRBE23, 749 - EXTOUT, 766
- DYNREAL, 749 - EXTRCV, 769
- DYN3THDT, 750 - EXTUNIT, 769
- DYNSPCF, 750 - FACTOR, 769
- DYPBM71, 750 - FASTFR, 769
- DYPRMSPC, 751 - FBATOLR, 770
- DYRBE3, 751 - FBLEND, 770
- DYRBE3TY, 751 - FIXEDB, 771
- DYRLTFLG, 751 - FKSYMFAC, 771

Main Index
 - FLEXINCR, 772 - MARCAUTO, 789
- FLUIDMP, 772 - MARCAXEL, 789
- FLUIDNE, 773 - MARCBEAM, 790
- FLUIDSE, 773 - MARCBODY, 790
- FMULTI, 773 - MARCBUSH, 790
- FOLLOWK, 773 - MARCCBAR, 791
- FRQDEPO, 774 - MARCCENT, 791
- FULLSEDR, 774 - MARCCON2, 791
- FZERO, 774 - MARCCON3, 792
- G, GFL, 774 - MARCCPY, 792
- GEOMU, 774 - MARCDEF, 793
- GPECT, 775 - MARCDILT, 794
- GRADMESH, 775 - MARCDIS2, 794
- GRDPNT, 775 - MARCDIS3, 794
- GUSTAERO, 776 - MARCDIS4, 794
- GYROAVG, 776 - MARCDMIG,N, 794
- HEATCMD, 777 - MARCDUPE, 795
- HEATSTAT, 777 - MARCDYND, 795
- HFREQ, HFREQFL, 777 - MARCEKND, 796
- HTOCITS, 778 - MARCEXIT, 796
- HTOCPRT, 778 - MARCFEAT,N, 796
- HTOCTOL, 778 - MARCFILi, 796
- HTSYM, 778 - MARCFRIC, 797
- ICOPT, 778 - MARCGAPD, D, 798
- IFP, 779 - MARCGAPN, ID, 798
- INREL, 779 - MARCGAPP, 798
- INRLM, 779 - MARCGAUS, 798
- IRES, 780 - MARCGLUE, 799
- ITAPE, 780 - MARCGRAV, 799
- IUNIT, 780 - MARCHOST, 799
- JWLDET, 780 - MARCIAMN, 799
- KDAMP, KDAMPFL, 780 - MARCINTC, 800
- KDIAG, 781 - MARCINTF, 800
- K6ROT, 781 - MARCITER, 800
- LANGLE, 782 - MARCL001, 801
- LDSUM, 782 - MARCLOWE, 802
- LFREQ, LFREQFL, 782 - MARCLUMP, 802
- LGDISP, 783 - MARCMAT2, 803
- LMFACT, 783 - MARCMAT3, 803
- LMODES, LMODESFL, 784 - MARCMATT, 804
- LOADU, 784 - MARCMEM, Value, 804
- LOOPID, 784 - MARCMID3, 804
- LSTRN, 785 - MARCMNF, 804
- MACH, 785 - MARCMPCC, 805
- MARALPHA, 785 - MARCMPII, 805
- MARAUTOC, 786 - MARCND99, 806
- MARBATCH, 786 - MARCNOER, 806
- MARBK105, 787 - MARCOFFT, 806
- MARBK106, 787 - MARCONTF, 807
- MARC4401, 787 - MARCOOCC, 807
- MARC7601, 788 - MARCOPT, 808
- MARCASUM, 788 - MARCOSET, 808

Main Index
 - MARCOTIM, 808 - MARCWDIS, 828
- MARCOUTR, 809 - MARCWELD, 829
- MARCPARR, 809 - MARELSTO, 829
- MARCPENT, 810 - MARGPFEL, 829
- MARCPINN, 810 - MARGPFOR, 830
- MARCPLAS, n, 810 - MARFACEA, 830
- MARCPOS, 811 - MARFACEB, 830
- MARCPOST, 811 - MARFATAL, 830
- MARCPR99, 812 - MARHEATM, 831
- MARCPRN, 812 - MARHTPRT, 831
- MARCPRNG, 813 - MARIBOOC, 831
- MARCPRNR, 813 - MARIPROJ, 831
- MARCPROG, 813 - MARLDCMB, 832
- MARCRACC, 813 - MARLDRMV, 832
- MARCRBAL, 814 - MARMPCHK, 833
- MARCRBAR, 814 - MARMPCID, 833
- MARCRBE2, 815 - MARMPICH, 834
- MARCRBE3, 815 - MARMTLCK, 834
- MARCREVR, 816 - MARNOCID, 834
- MARCREVRX, 816 - MARNOSET, Name, 835
- MARCRIGD, 816 - MAROFSET, 835
- MARCSAME, 817 - MARPLANE, 835
- MARCSCLR, 818 - MARPROCS, 836
- MARCSETS, 818 - MARRBAR2, 836
- MARCSETT, 819 - MARROUTT, 836
- MARCSINC, 819 - MARSHRII, 837
- MARCSIZ3, Value, 819 - MARTET10, 837
- MARCSIZ4, Value, 819 - MARTETIN, 838
- MARCSIZ5, Value, 819 - MARUPDAT, 838
- MARCSIZ6, Value, 820 - MARVFCUT, 839
- MARCSLHT, 820 - MAUTOSPC, 839
- MARCSOLV, 820 - MAXIREVV, 840
- MARCSPCC, 821 - MAXLP, 840
- MARCSTIFF, Time, 821 - MAXRATIO, 840
- MARCSTOP, 822 - MBENDCAP, 841
- MARCSUMY, 822 - MCNLPARM, 841
- MARCT16, 822 - MCON2D3D, 841
- MARCT19, 823 - MCORDUPD, 842
- MARCTABL, 823 - MCSSHLCK, 842
- MARCTEDF, 824 - MCSSHORR, 842
- MARCTEDN, 824 - MDAREAMD, 843
- MARCTEMP, 824 - MDEFSEPP, 843
- MARCTETT, 825 - MDK4OPT, 844
- MARCTIEC, 825 - MDOPT14, 844
- MARCTOL, 825 - MDOTM, 845
- MARCTOTD, 826 - MDOTMFAC, 845
- MARCTOTL, 826 - MDUMLOAD, 845
- MARCTOTT, 826 - MECHFIL, 845
- MARCTUBE, 827 - MECHFIX, 845
- MARCTVL, Value, 827 - MECHPRT, 846
- MARCUSUB, chr, 828 - MESH, 846
- MARCVERS, 828 - METHCMRS, 846

Main Index
 - MEXTRNOD, 846 - MRBEAMB, 864
- MEXTSEE,N, 847 - MRBEPARM, IJK, 864
- MFASTCMP, 847 - MRBDYCVT, 864
- MFEA5701, 847 - MRBIGMEM, 865
- MFORCOR1, 848 - MRBUKMTH, 865
- MFORDUPE, 848 - MRC2DADD, 866
- MFSKIPPP, 848 - MRCKBODY, 866
- MGAPINIT, 849 - MRCKLOAD, 866
- MGLUETOL, 849 - MRCONADD, 867
- MHEATSHL, 849 - MRCONRES, 867
- MHEATUNT, 850 - MRCONTAB, 867
- MHEMIPIX, 850 - MRCONUSE, 868
- MHOUBOLT, 850 - MRCONVER, 868
- MHRED, 851 - MRCOORDS, 869
- MICRO , 851 - MRCQUAD4, 869
- MINCLDSB, 851 - MRCTRIA3, 869
- MINIGOA, 852 - MRCWANGL, 870
- MINRECCC, N, 852 - MRDELTTT, 870
- MINSOUTT, 852 - MRDISCMB, 871
- MINVASHF, 852 - MRDUPMAT, 871
- MINVCITR, 853 - MRDYNOLD, 872
- MINVCSHF, 853 - MREIGMTH, 872
- MINVCTOL, 853 - MREL1103, 872
- MINVFMAX, 853 - MRELRB, 872
- MINVNMOD, 853 - MRELSPCD, 873
- MLDALLOW, 853 - MRENUELE, 873
- MLSTRAIN, 854 - MRENUGRD, 874
- MLSTRAN2, 855 - MRENUMBR, 875
- MMAT2ANI, 855 - MRESTALL, 875
- MMBOLTUS, 855 - MRESULTS, 875
- MMEMDETT, 856 - MREVPLST, 876
- MMFIL, 856 - MRFINITE, 876
- MNASTLDS, 856 - MRFOLLOW, 876
- MODACC, 858 - MRFOLLO2, 876
- MODEL, 858 - MRFOLOW1, 876
- MOFFCORE, 858 - MRFOLOW3, 877
- MOP2TITL, 858 - MRFOLOW4, 877
- MOUTRCOR, 859 - MRGAPUSE, 878
- MP1SET, 859 - MRHERRMN, 878
- MPCX, 859 - MRHYPMID, 878
- MPERMPRT, 860 - MRITTYPE,, 879
- MPTUNIT, 860 - MRMAT8A3, Value, 879
- MQUATERN, 860 - MRMAT8E3, Value, 879
- MRADUNIT, 860 - MRMAT8N1, Value, 879
- MRAFFLOR, N, 861 - MRMAT8N3, Value, 879
- MRAFFLOT, N, 861 - MRMAXISZ, 879
- MRAFFLOW, Name, 862 - MRMAXNUM, 880
- MRALIAS ID (MALIAS02, MALIA - MRMEMSUM, 880
S03, etc.), 862 - MRMTXKGG, Name, 880
- MRALLOCG, 863 - MRMTXNAM, Name, 880
- MRALLOCS, 863 - MRNOCOMP, 881
- MRBE3SNG, 863 - MRNOCOR, 881

Main Index
 - MRNOECHO, 881 - MSPLINC0, 903
- MRORINTS, 882 - MSTFBEAM, 903
- MROUTLAY, 883 - MSTRFREE, 903
- MRPARALL, 883 - MSTTDYNE, 904
- MRPBUSHT, 884 - MTABIGNR, 904
- MRPIDCHK, 885 - MTABLD1M, 905
- MRPELAST, 885 - MTABLD1T, 905
- MRPLOAD4, 885 - MTDYMAT9, 905
- MRPLOD4R, 886 - MTEMPCHK, 906
- MRPLSUPD, 886 - MTEMPDWN, 906
- MRPOISCK, 887 - MTET4HYP, 907
- MRPREFER, 887 - MTLD1SID, 907
- MRPRSFAC, 887 - MUALLUDS, 908
- MRPSHCMP, 888 - MULRFORC, 908
- MRPSHELL, 889 - MUMPSOLV, 908
- MRRBE3TR, 889 - MUSBKEEP, 909
- MRRCFILE, RCF, 890 - MVERMOON, 909
- MRRELNOD, 890 - MWINQUOT, 909
- MRRSTOP2, 890 - MWLDGSGA, 910
- MRSCMOD, 891 - MXICODE0, 910
- MRSETNA1, N, 891 - MXLAGM1, 910
- MRSETNA2, M, 891 - NASPRT, 910
- MRSETNAM, N, 892 - NDAMP, NDAMPM, 910
- MRSPAWN2, CMD, 892 - NEWMARK, 912
- MRSPLINE, 892 - NHPLUS, 912
- MRSPRING, 893 - NINTPTS, 912
- MRSPRVER, 893 - NLAYERS, 912
- MRSTEADY, 893 - NLHTLS, 913
- MRT16STP, N, 894 - NLHTOL, 913
- MRTABLIM, 894 - NLHTWK, 913
- MRTABLS1, 894 - NLMAX, 913
- MRTABLS2, 895 - NLMIN, 913
- MRTABPRC, 896 - NLPACK, 914
- MRTFINAL, 896 - NLTOL, 914
- MRTHREAD, 896 - NMLOOP, 914
- MRTIMING, 897 - NOCOMPS, 915
- MRTSHEAR, 897 - NODCMP, 915
- MRUSDATA, 897 - NOELOF, 915
- MRVFIMPL, 897 - NOELOP, 915
- MRV09V11, 898 - NOGPF, 915
- MSIZOVRD, 898 - NOMSGSTR, 916
- MSOLMEM, MBYTE, 899 - NONCUP, 916
- MSPCCCHK, 899 - NQSET, 916
- MSPCKEEP, 900 - NUMOUT, NUMOUT1, NUMOUT2
- MSPEEDCB, 900 , 916
- MSPEEDCW, 900 - OELMSET , 916
- MSPEEDOU, 901 - OG, 917
- MSPEEDP4, 901 - OGEOM, 917
- MSPEEDPS, 901 - OGRDOPT, 917
- MSPEEDSE, 902 - OGRDSET, 917
- MSPEEDS2, 902 - OLDSEQ, 917
- MSPEEDSH, 902 - OMACHPR, 919

Main Index
 - OMAXR, 920 - RHOCP, 936
- OMID, 920 - RKSCHEME , 936
- OMSGLVL, 920 - RMSINT, 937
- OPCHSET, 920 - ROHYDRO , 937
- OPGEOM, 920 - ROMULTI , 938
- OPGTKG, 920 - ROSTR , 939
- OPPHIB, 921 - ROTSEKE, 939
- OPPHIPA, 921 - RSPECTRA, 940
- OPTEXIT, 921 - RSPRINT, 940
- OPTION, 922 - RSTTEMP, 940
- OSETELE, 922 - S1, S1G, S1M, 940
- OSETGRD, 922 - S1AG,S1AM, 942
- OSWELM, 922 - SBOLTZ, 942
- OSWPPT, 923 - SCALEMAS, 943
- OUGCORD, 923 - SCRSPEC, 943
- OUNIT1, 923 - SDRPOPT, 944
- OUNIT2, 923 - SEMAP,
- OUTOPT, 923 SEMAPOPT, SEMAPPRT, 944
- PACINFID, 923 - SENSUOO, 945
- PANELMP, 924 - SEP1XOVR, 946
- PATPLUS, 924 - SEQOUT, 946
- PATVER, 924 - SERST, 946
- PCOMPRM, 924 - SESDAMP, 947
- PDRMSG, 924 - SESEF, 947
- PEDGEP, 924 - SHIFT1, 947
- PEMMAPC, 925 - SHLDAMP, 947
- PEMNPART, 925 - SIGMA, 948
- PENFN, 926 - SKINOUT, 948
- PERCENT, 926 - SKPAMP, 948
- PH2OUT, 926 - SLOOPID, 948
- PKRSP, 926 - SMALLQ, 949
- PLTMSG, 927 - SNORM, 949
- POST, 927 - SNORMPRT, 950
- POSTEXT, 933 - SOFTEXIT, 950
- POSTADF, 933 - SOLADJC, 950
- POSTU, 934 - SOLID, 951
- PREFDB, 934 - SPARSEDM, 951
- PRGPST, 934 - SPARSEDR, 951
- PRINT, 934 - SPARSEPH, 952
- PROUT, 934 - SPDRRAT, 952
- PRPA , 934 - SPCGEN, 952
- PRPJ, 934 - SPDMRAT, 952
- PRPHIVZ, 935 - SQSETID, 952
- PRTMAXIM, 935 - SRCOMPS, 953
- PRTRESLT, 935 - SRTELTYP, 953
- PSENPCH, 935 - SRTOPT, 953
- PVALINIT, 935 - START, 953
- Q, 936 - STEPFCT, 953
- RADMOD, 936 - STEPFCTL, 953
- RBSETPRT, 936 - STIME, 953
- RESLTOPT, 936 - STRUCTMP, 954
- RESVEC, 936 - SUBCASID, 954

Main Index
 - SUBID, 954 - USETSTRi, 960
- SUPAERO, 955 - VARPHI, 960
- SUPDOF, 955 - VELCUT , 961
- SUPER, 955 - VMOPT, 961
- TABID, 955 - VREF, 962
- TABS, 955 - VUELJUMP, VUGJUMP, 962
- TESTNEG, 956 - VUBEAM,
- TFSYMFAC, 956 VUHEXA, VUPENTA, VUQUAD
- TINY, 956 4, VUTETRA, VUTRIA3, 962
- TOLRSC, 957 - WRBEAMB, 963
- TOPOCONV, 957 - WTMAS600, 963
- TRMBIM, 957 - WTMASS, 963
- TSTATIC, 957 - W3, W4, W3FL, W4FL, 964
- UGASC, 958 - WR3, WR4, WRH, 964
- UNSYMF, 958 - XFLAG, 964
- UNSYMKB, 958 - XYUNIT, n, 965
- UPDTBSH, 958 - ZROCMAS, 965
- USETPRT, 958 - ZROVEC, 965
- USETSEL, 960
 Parameter Applicability Tables, 967

6
Item Codes  Item Code Description, 1004
 Element Stress (or Strain) Item Codes, 1005
- CAXIF2 (47), 1006 - CHEXAFD (207), 1016
- CAXlF3 (48), 1006 - CIFHEX (65), 1016
- CAXIF4 (49), 1006 - CIFPENT (66), 1016
- CAXISYM (241), 1007 - CIFQDX (73), 1017
- CBAR (34), 1007 - CIFQUAD (63), 1017
- CBAR (100), 1008 - CONROD (10), 1017
- CBAR (238), 1009 - CONROD (92), 1017
- CBEAM (2), 1009 - CPENTA (68), 1017
- CBEAM (94), 1009 - CPENTA (91), 1018
- CBEAM (239), 1010 - CPENTAFD (204), 1019
- CBEAM3 (184), 1010 - CPENTAFD (209), 1019
- CBEND (69), 1011 - CQUAD4 (33), 1020
- CBUSH (102), 1011 - CQUAD4 (90), 1020
- CBUSH1D (40), 1012 - CQUAD42 (95), 1021
- CCONEAX (35), 1013 - CQUAD4 (144), 1021
- CDUM3, 1013 - CQUAD8 (64), 1022
- CDUM9 (55-61), 1013 - CQUAD82 (96), 1023
- CELAS1 (11), 1013 - CQUADFD (201), 1023
- CELAS2 (12), 1013 - CQUADFD (208), 1023
- CELAS3 (13), 1013 - CQUADR (82), 1023
- CGAP (86), 1014 - CQUADR (172), 1023
- CHEXA (67), 1014 - CQUADR (232), 1023
- CHEXA (93), 1015 - CQUADX(18), 1024
- CHEXAFD (202), 1015 - CQUADXFD (214), 1024

Main Index
 - CQUADXFD (215), 1025 - CTRIAX6 (53), 1029
- CROD (1), 1025 - CTRIAXFD (212), 1030
- CROD (89), 1025 - CTRIAXFD (213), 1030
- CSHEAR (4), 1025 - CTUBE (3), 1030
- CSLOT3 (50), 1025 - CTUBE (87), 1030
- CSLOT4 (51), 1025 - VUHEXA (145), 1031
- CTETRA (39), 1026 - VUPENTA (146), 1031
- CTETRA (85), 1027 - VUTETRA (147), 1031
- CTETRAFD (205), 1027 - VUHEXA (145), 1032
- CTETRAFD (210), 1027 - VUPENTA (146), 1032
- CTRIA3 (74), 1028 - VUTETRA (147), 1032
- CTRIA32 (97), 1028 - VUQUAD (189)
- CTRIA3 (88), 1028 VUTRIA (190), 1033
- CTRIA6 (75), 1028 - VUQUAD (189)
- CTRIA62 (98), 1028 VUTRIA (190), 1034
- CTRIAFD (206), 1028 - VUQUAD (189)
- CTRIAFD (211), 1029 VUTRIA (190), 1035
- CTRlAR (70), 1029 - VUQUAD (189)
- CTRIAR (173), 1029 VUTRIA (190), 1036
- CTRIAR (233), 1029 - VUQUAD (189)
- , 1029 VUTRIA (190), 1037
- CTRIAX(17), 1029 - VUBEAM (191), 1038
 Element Force Item Codes, 1040
- CBAR (34), 1040 - CQUAD8 (64), 1047
- CBAR (100), 1040 - CQUAD82 (96), 1048
- CBEAM (2), 1041 - CQUADR (82), 1048
- CBEAM3 (184), 1042 - CQUADR (235), 1048
- CBEND (69), 1042 - CROD (1), 1049
- CBUSH (102), 1043 - CSHEAR (4), 1049
- CCONEAX - CTRIA3 (74), 1050
(35), 1043 - CTRIA32 (97), 1050
- CDAMP1 (20), 1043 - CTRlA6 (75), 1050
- CDAMP2 (21), 1043 - CTRlA62 (98), 1050
- CDAMP3 (22), 1044 - CTRIAR (70), 1051
- CDAMP4 (23), 1044 - CTRIAR (236), 1051
- CDUM3 thru CDUM9 (55 - 61), 1044 - CTUBE (3), 1051
- CELAS1 (11), 1044 - CVlSC (24), 1051
- CELAS2 (12), 1044 - CWELDP (118), 1051
- CELAS3 (13), 1044 - CWELDC (117), 1051
- CELAS4 (14), 1044 - CWELD (200), 1051
- CGAP (38), 1044 - VUQUAD (189)
- CONROD (10), 1045 VUTRIA (190), 1051
- CQUAD4 (33), 1045 - VUQUAD (189)
- CQUAD4 (95), 1045 VUTRIA (190), 1053
- CQUAD4 (144), 1046 - VUBEAM (191), 1054
 Fluid Virtual Mass Pressure Item Codes, 1055
 2D Slideline and 3D Surface Contact Item Codes, 1056
- CSLIFID (116), 1056 - 203, 1057
- 203, 1057
 Element Strain Energy Item Codes, 1059

Main Index
  Fatigue Item Codes, 1060
 Equivalent Radiated Power (ERP) Item Codes, 1067

7
Degree-of-Freedom  Degree-of-Freedom Set Definitions, 1070
Sets
 Degree-of-Freedom Set Bulk Data Entries, 1074

8
Bulk Data Entries  Key to Descriptions, 1076
 The Bulk Data Section, 1077
 Bulk Data Entry Descriptions, 1078
 Format of Bulk Data Entries, 1079
 Continuations, 1085
 Bulk Data Entry Summary, 1088
 Constraints and Partitioning, 1088
 Elements, 1091
 Geometry, 1101
 Loads, 1105
 Materials, 1109
 Miscellaneous, 1111
 Nastran Implicit Nonlinear (SOL 600), 1116
 Explicit Nonlinear (SOL 700), 1119
 Solution Control, 1136
 Bulk Data Entries, 1141
- $, 1141 - AEFORCE, 1175
- /, 1142 - AEGRID, 1176
- ABINFL, 1146 - AELINK, 1177
- ACC, 1148 - AELIST, 1178
- ACCEL, 1149 - AELISTC, 1179
- ACCEL1, 1151 - AEPARM, 1180
- ACCMETR, 1152 - AEPRESS, 1181
- ACLOAD, 1154 - AEQUAD4, 1182
- ACMODL, 1155 - AERO, 1183
- ACPEMCP, 1161 - AEROS, 1184
- ACSRCE, 1163 - AESCALE, 1185
- ACTIVAT, 1165 - AESTAT, 1186
- ACTRIM, 1166 - AESURF, 1188
- ADAPT, 1167 - AESURFS, 1190
- ADUMi, 1170 - AETRIA3, 1191
- AECOMP, 1171 - AIRBAG, 1192
- AECOMPL, 1172 - ALIASM, 1199
- AEDW, 1173 - ASET, 1201
- AEFACT, 1174 - ASET1, 1202

Main Index
 - AXIC, 1203 - BNDFIX, 1407
- AXIF, 1205 - BNDFIX1, 1408
- AXSLOT, 1207 - BNDFREE, 1410
- BAROR, 1208 - BNDFRE1, 1411
- BARRIER, 1210 - BNDGRID, 1413
- BCBDPRP, 1212 - BOLT, 1414
- BCBMRAD, 1218 - BOUTPUT, 1417
- BCBODY, 1220 - BRKSQL, 1419
- BCBODY, 1232 - BSET, 1422
- BCBODY1, 1247 - BSET1, 1423
- BCBOX, 1249 - BSQUEAL, 1425
- BCBZIER, 1251 - BSURF, 1432
- BCGM700, 1253 - BWIDTH, 1434
- BCGRID, 1258 - CAABSF, 1436
- BCHANGE, 1259 - CACINF3, 1438
- BCHANGE, 1261 - CACINF4, 1439
- BCMATL, 1263 - CAERO1, 1440
- BCMOVE, 1264 - CAERO2, 1442
- BCMOVE, 1265 - CAERO3, 1444
- BCNURB2, 1267 - CAERO4, 1446
- BCNURBS, 1269 - CAERO5, 1448
- BCONECT, 1271 - CAMPBLL, 1452
- BCONP, 1273 - CAXIFi, 1453
- BCONPRG, 1275 - CAXISYM, 1454
- BCONPRG-700, 1280 - CBAR, 1455
- BCONPRP, 1295 - CBARAO, 1460
- BCONPRP-700, 1299 - CBEAM, 1462
- BCONUDS, 1308 - CBEAM3, 1467
- BCONUDS, 1311 - CBELT, 1470
- BCPARA, 1313 - CBEND, 1471
- BCPARA, 1318 - CBUSH, 1474
- BCPATCH, 1325 - CBUSH1D, 1478
- BCPROP, 1326 - CBUSH2D, 1479
- BCPROP, 1328 - CBUTT, 1480
- BCPROP1, 1329 - CCONEAX, 1483
- BCRIGID, 1331 - CCRSFIL, 1484
- BCRGSRF, 1333 - CDAMP1, 1487
- BCSEG, 1334 - CDAMP1D, 1488
- BCTABLE, 1335 - CDAMP2, 1490
- BCTABLE - Glued Option, 1367 - CDAMP2D, 1491
- BCTABLE, 1372 - CDAMP3, 1493
- BCTABL1, 1380 - CDAMP4, 1494
- BCTRIM, 1382 - CDAMP5, 1495
- BDYLIST, 1384 - CDUMi, 1496
- BDYOR, 1385 - CELAS1, 1497
- BEADVAR, 1386 - CELAS1D, 1498
- BEAMOR, 1390 - CELAS2, 1500
- BFRlC, 1392 - CELAS2D, 1501
- BIAS, 1393 - CELAS3, 1503
- BJOIN, 1396 - CELAS4, 1504
- BLDOUT, 1399 - CFAST, 1505
- BLSEG, 1405 - CFILLET, 1508

Main Index
 - CFLUIDi, 1511 - CQUADR, 1615
- CGAP, 1513 - CQUADX, 1618
- CHACAB, 1515 - CRAC2D, 1620
- CHACBR, 1517 - CRAC3D, 1622
- CHBDYE, 1519 - CREEP, 1626
- CHBDYG, 1522 - CROD, 1631
- CHBDYP, 1526 - CROSSEC, 1633
- CHEXA, 1530 - CSEAM, 1636
- CIFHEX, 1533 - CSET, 1645
- CIFPENT, 1535 - CSET1, 1646
- CIFQDX, 1537 - CSHEAR, 1648
- CIFQUAD, 1539 - CSLOT3, 1651
- CINTC, 1541 - CSLOT4, 1652
- CLOAD, 1542 - CSPOT, 1653
- CMARKB2, 1543 - CSPH, 1657
- CMARKN1, 1544 - CSPR, 1658
- CMASS1, 1545 - CSSCHD, 1660
- CMASS2, 1547 - CSSHL, 1662
- CMASS3, 1548 - CSSHLH, 1664
- CMASS4, 1549 - CSSHLM, 1665
- CMREBAI, 1550 - CSSHLP, 1666
- CMREBAR, 1552 - CSUPER, 1667
- CNTRUDS, 1554 - CSUPEXT, 1669
- COHESIV, 1555 - CTETRA, 1670
- COMBWLD, 1557 - CTQUAD, 1673
- CONM1, 1560 - CTRIA3, 1675
- CONM2, 1561 - CTRIA6, 1679
- CONROD, 1563 - CTRIAR, 1683
- CONSPOT, 1565 - CTRIAX, 1686
- CONTRLT, 1566 - CTRIAX6, 1688
- CONV, 1570 - CTTRIA, 1692
- CONV3, 1572 - CTUBE, 1694
- CONVM, 1573 - CVISC, 1695
- CORD1C, 1576 - CWELD, 1696
- CORD1R, 1578 - CYAX, 1706
- CORD1RX, 1580 - CYJOIN, 1707
- CORD1S, 1581 - CYLINDR, 1709
- CORD2C, 1583 - CYSUP, 1710
- CORD2R, 1585 - CYSYM, 1712
- CORD2RX, 1587 - D2R0000, 1713
- CORD2S, 1588 - D2RAUTO, 1714
- CORD3G, 1590 - D2RINER, 1717
- CORD3R, 1592 - DAMPGBL, 1718
- CORD3RX, 1593 - DAMPING, 1719
- COUOPT, 1594 - DAMPMAS, 1722
- COUP1FL, 1596 - DAMPSTF, 1724
- COUPINT, 1597 - DAREA, 1726
- COUPLE, 1598 - DBEXSSS, 1727
- CPENTA, 1602 - DBREG, 1728
- CQUAD, 1605 - DCONADD, 1730
- CQUAD4, 1607 - DCONSTR, 1731
- CQUAD8, 1611 - DDVAL, 1733

Main Index
 - DEACTEL, 1735 - DYPARAM,ELDLTH, 1857
- DEACTEL, 1736 - DYPARAM,EULERCB, 1858
- DEFORM, 1737 - DYPARAM,EULERPR, 1859
- DEFUSET, 1738 - DYPARAM,EULTRAN, 1861
- DELAY, 1739 - DYPARAM,EUSUBMAX, 1863
- DEQATN, 1740 - DYPARAM,FASTCOUP, 1865
- DESVAR, 1745 - DYPARAM,HYDROBOD, 1867
- DETSPH, 1746 - DYPARAM,JWLDET, 1868
- DIVERG, 1747 - DYPARAM,LIMITER, 1869
- DLINK, 1748 - DYPARAM,LSDYNA,ACCURACY
- DLOAD, 1749 , 1870
- DMI, 1750 - DYPARAM,LSDYNA,BINARY, 18
- DMIAX, 1754 72
- DMIG, 1756 - DYPARAM,LSDYNA,CONTACT, 1
- DMIG,UACCEL, 1759 874
- DMIGOUT, 1761 - DYPARAM,LSDYNA,DBEXTENT,
- DMIGROT, 1765 1880
- DMIJ, 1767 - DYPARAM,LSDYNA,ENERGY, 18
- DMIJI, 1770 84
- DMIK, 1773 - DYPARAM,LSDYNA,HOURGLAS,
- DOPTPRM, 1776 1885
- DPHASE, 1784 - DYPARAM,LSDYNA,IMPLICIT, 1
- DRESP1, 1785 887
- DRESP2, 1797 - DYPARAM,LSDYNA,OUTPUT, 18
- DRESP3, 1803 92
- DSCREEN, 1807 - DYPARAM,LSDYNA,RELAX, 189
- DTABLE, 1809 4
- DTABLE2, 1810 - DYPARAM,LSDYNA,SHELL, 1895
- DTI, 1811 - DYPARAM,LSDYNA,SOLID, 1900
- DTI,ESTDATA, 1813 - DYPARAM,LSDYNA,THERMAL,
- DTI,INDTA, 1817 1901
- DTI,SETREE, 1820 - DYPARAM,LSDYNA,TIMESTEP,
- DTI,SPECSEL, 1822 1903
- DTI,SPSEL, 1823 - DYPARAM,SPHERSYM, 1907
- DTI,UNITS, 1825 - DYPARAM,SPREMAP, 1908
- DVBSHAP, 1827 - DYPARAM,VELMAX, 1909
- DVCREL1, 1828 - DYRELAX, 1910
- DVCREL2, 1830 - DYRIGSW, 1912
- DVGRID, 1832 - DYTERMT, 1913
- DVLREL1, 1834 - DYTIMHS, 1915
- DVMREL1, 1836 - ECHOOFF, 1923
- DVMREL2, 1838 - ECHOON, 1924
- DVPREL1, 1840 - EIGB, 1925
- DVPREL2, 1842 - EIGC, 1927
- DVSHAP, 1844 - EIGP, 1933
- DVPSURF, 1845 - EIGR, 1934
- DYCHANG, 1846 - EIGRL, 1938
- DYDELEM, 1851 - ELEMUDS, 1942
- DYFSISW, 1852 - ELEMUDS, 1944
- DYPARAM,AXIALSYM, 1853 - ELIST, 1946
- DYPARAM,AXREMAP, 1855 - ENDDATA, 1947
- DYPARAM,COHESION, 1856 - ENDDYNA, 1948

Main Index
 - ENTUDS, 1949 - FRFSPC1, 2046
- EOSGAM, 1951 - FRFXIT, 2047
- EOSGRUN, 1953 - FRFXIT1, 2048
- EOSIG, 1955 - FSICTRL, 2049
- EOSJWL, 1961 - FSLIST, 2050
- EOSMG, 1963 - FTGDEF, 2051
- EOSPOL, 1965 - FTGEVNT, 2055
- EOSTAB, 1967 - FTGLOAD, 2057
- EOSTABC, 1969 - FTGPARM, 2060
- EOSTAIT, 1971 - FTGSEQ , 2071
- EOSUDS, 1973 - GBAG, 2075
- EPOINT, 1975 - GBAGCOU, 2078
- ERPPNL, 1976 - GENEL, 2079
- EULFOR, 1977 - GENUDS, 2082
- EULFOR1, 1978 - GMBC, 2083
- EULFREG, 1979 - GMBNDC, 2091
- EXPLSV, 1981 - GMBNDS, 2093
- EXTRN, 1984 - GMCONV, 2095
- FAILJC, 1985 - GMCORD, 2098
- FAILMPS, 1987 - GMCURV, 2100
- FAILUDS, 1988 - GMINTC, 2107
- FBADLAY, 1990 - GMINTS, 2109
- FBALOAD, 1991 - GMLOAD, 2111
- FBAPHAS, 1992 - GMNURB, 2114
- FBODYLD, 1993 - GMQVOL, 2117
- FBODYSB, 1994 - GMSPC, 2118
- FEEDGE, 1995 - GMSURF, 2119
- FEFACE, 1998 - GRAV, 2125
- FFCONTR, 2000 - GRDSET, 2127
- FLFACT, 2002 - GRIA, 2128
- FLOW, 2004 - GRID, 2129
- FLOWDEF, 2006 - GRIDA, 2131
- FLOWSPH, 2008 - GRIDB, 2132
- FLOWT, 2010 - GRIDF, 2133
- FLOWUDS, 2013 - GRIDS, 2134
- FLSYM, 2016 - GUST, 2135
- FLUTTER, 2017 - HADACRI, 2136
- FORCE, 2020 - HADAPTL, 2139
- FORCE1, 2022 - HEATLOS, 2141
- FORCE2, 2023 - HGSUPPR, 2143
- FORCEAX, 2024 - HTRCONV, 2147
- FREEPT, 2025 - HTRRAD, 2148
- FREQ, 2026 - HYBDAMP, 2149
- FREQ1, 2027 - HYDSTAT, 2151
- FREQ2, 2028 - INCLUDE, 2153
- FREQ3, 2029 - INFLCG, 2154
- FREQ4, 2032 - INFLFRC, 2156
- FREQ5, 2035 - INFLGAS, 2158
- FRFCOMP, 2037 - INFLHB, 2160
- FRFCONN, 2040 - INFLTNK, 2161
- FRFFLEX, 2042 - INFLTR, 2163
- FRFRELS, 2044 - INITGAS, 2165

Main Index
 - IPSTRAIN, 2166 - MATD020, 2285
- IPSTRN, 2167 - MATD20M, 2288
- ISTRESS, 2168 - MATD021, 2289
- ISTRNSH, 2170 - MATD022, 2293
- ISTRNSO, 2171 - MATD024, 2296
- ISTRSBE, 2172 - MATD025, 2300
- ISTRSSH, 2173 - MATD026, 2306
- ISTRSSO, 2175 - MATD027, 2312
- ISTRSSS, 2177 - MATD028, 2315
- ISTRSTS, 2179 - MATD029, 2316
- ITER, 2181 - MATD030, 2321
- LEAKAGE, 2185 - MATD031, 2324
- LOAD, 2188 - MATD032, 2327
- LOADCLID, 2189 - MATD034, 2329
- LOADCNAM, 2190 - MATD036, 2333
- LOADCSUB, 2192 - MATD037, 2339
- LOADCYH, 2193 - MATD039, 2342
- LOADCYN, 2195 - MATD040, 2344
- LOADCYT, 2197 - MATD053, 2347
- LOADOF, 2198 - MATD054, 2349
- LOADT, 2199 - MATD057, 2357
- LORENZI, 2201 - MATD058, 2361
- LSEQ, 2205 - MATD059, 2366
- MACREEP, 2207 - MATD062, 2370
- MARCIN, 2209 - MATD063, 2372
- MARCOUT, 2211 - MATD064, 2374
- MARPRN, 2219 - MATD066, 2376
- MAT1, 2221 - MATD067, 2378
- MAT2, 2225 - MATD068, 2381
- MAT3, 2227 - MATD069, 2385
- MAT4, 2229 - MATD070, 2389
- MAT5, 2231 - MATD071, 2391
- MAT8, 2232 - MATD072, 2393
- MAT9, 2235 - MATD72R, 2395
- MAT10, 2237 - MATD073, 2398
- MATD001, 2239 - MATD074, 2401
- MATD2AN, 2241 - MATD076, 2403
- MATD2OR, 2245 - MATD077, 2406
- MATD003, 2248 - MATD77H, 2407
- MATD004, 2250 - MATD77O, 2411
- MATD005, 2252 - MATD078, 2415
- MATD006, 2255 - MATD080, 2419
- MATD007, 2256 - MATD081, 2421
- MATD009, 2257 - MATD083, 2427
- MATD010, 2259 - MATD084, 2432
- MATD012, 2262 - MATD087, 2435
- MATD013, 2263 - MATD089, 2439
- MATD014, 2265 - MATD091, 2441
- MATD015, 2268 - MATD092, 2444
- MATD016, 2273 - MATD093, 2447
- MATD018, 2280 - MATD094, 2448
- MATD019, 2282 - MATD095, 2450

Main Index
 - MATD096, 2451 - MATDS03, 2635
- MATD097, 2454 - MATDS04, 2636
- MATD098, 2455 - MATDS05, 2637
- MATD099, 2457 - MATDS06, 2638
- MATD100, 2459 - MATDS07, 2640
- MATD106, 2460 - MATDS08, 2641
- MATD107, 2463 - MATDS13, 2642
- MATD110, 2469 - MATDS14, 2643
- MATD111, 2472 - MATDS15, 2644
- MATD112, 2475 - MATDT01, 2648
- MATD114, 2477 - MATDT02, 2649
- MATD116, 2479 - MATDT03, 2651
- MATD119, 2481 - MATDT04, 2652
- MATD120, 2486 - MATDT05, 2654
- MATD12J, 2491 - MATDT06, 2656
- MATD12R, 2497 - MATDSW1 - MATDSW5, 2657
- MATD121, 2501 - MATEP, 2666
- MATD123, 2503 - MATEP, 2675
- MATD124, 2505 - MATF, 2690
- MATD126, 2508 - MATF, 2700
- MATD127, 2516 - MATF1, 2710
- MATD128, 2519 - MATFTG , 2711
- MATD129, 2523 - MATG, 2721
- MATD130, 2526 - MATHE, 2724
- MATD143, 2529 - MATHED, 2732
- MATD145, 2535 - MATHP, 2735
- MATD147, 2540 - MATM, 2738
- MATD155, 2542 - MATNLE, 2743
- MATD156, 2544 - MATORT , 2748
- MATD158, 2547 - MATPE1, 2751
- MATD159, 2553 - MATRIG, 2753
- MATD163, 2563 - MATS1, 2756
- MATD164, 2565 - MATS3, 2761
- MATD170, 2567 - MATS8, 2763
- MATD173, 2570 - MATSMA, 2765
- MATD176, 2574 - MATSORT, 2769
- MATD181, 2579 - MATT1, 2771
- MATD184, 2581 - MATT2, 2773
- MATD185, 2582 - MATT3, 2775
- MATD186, 2585 - MATT4, 2777
- MATD190, 2589 - MATT5, 2778
- MATD193, 2594 - MATT8, 2779
- MATD196, 2596 - MATT9, 2781
- MATD224, 2599 - MATTEP, 2782
- MATD266, 2602 - MATTEP, 2784
- MATDB01, 2608 - MATTF, 2786
- MATDERO, 2610 - MATTG, 2789
- MATDEUL, 2622 - MATTHE, 2791
- MATDIGI, 2624 - MATTORT, 2794
- MATDMG, 2626 - MATTM, 2795
- MATDS01, 2633 - MATTUSR, 2798
- MATDS02, 2634 - MATTVE, 2799

Main Index
 - MATUDS, 2802 - MT16SPL, 2911
- MATUDS, 2808 - MTABRV, 2914
- MATUSR, 2811 - MTCREEP, 2916
- MATVE, 2814 - MTHERM, 2918
- MATVP, 2818 - NLADAPT, 2919
- MAUXCMD, 2822 - NLAUTO, 2921
- MBOLT, 2823 - NLCYSYM, 2926
- MBOLTUS, 2825 - NLDAMP, 2930
- MCHSTAT, 2827 - NLFREQ, 2931
- MCOHE, 2829 - NLFREQ1, 2932
- MDELAM, 2831 - NLHARM, 2933
- MDLPRM, 2833 - NLHEATC, 2934
- MDMIAUX, 2840 - NLMOPTS, 2936
- MDMIOUT, 2841 - NLOUT, 2950
- MESH, 2843 - NLOUTUD, 2953
- MESUPER, 2850 - NLPARM, 2954
- METADATA, 2853 - NLPCI, 2962
- MFLUID, 2854 - NLRGAP, 2964
- MGRSPR, 2857 - NLRSFD, 2967
- MINSTAT, 2858 - NLSTEP, 2970
- MISLAND, 2860 - NLSTRAT, 2984
- MIXTURE, 2861 - NOLIN1, 2994
- MKAERO1, 2863 - NOLIN2, 2996
- MKAERO2, 2864 - NOLIN3, 2998
- MLAYOUT, 2865 - NOLIN4, 3000
- MNF600, 2866 - NSM, 3002
- MODTRAK, 2868 - NSM1, 3003
- MOMAX, 2869 - NSMADD, 3005
- MOMENT, 2870 - NSML, 3006
- MOMENT1, 2871 - NSML1, 3007
- MOMENT2, 2872 - NTHICK, 3009
- MONCNCM, 2873 - OMIT, 3010
- MONDSP1, 2874 - OMIT1, 3011
- MONGRP, 2876 - OMITAX, 3012
- MONPNT1, 2877 - OUTPUT, 3013
- MONPNT2, 2879 - OUTRCV, 3016
- MONPNT3, 2881 - PAABSF, 3019
- MONSUM, 2883 - PAABSF, 3019
- MONSUM1, 2886 - PACABS, 3021
- MONSUMT, 2889 - PACBAR, 3022
- MPC, 2891 - PACINF, 3023
- MPCADD, 2893 - PAERO1, 3025
- MPCAX, 2894 - PAERO2, 3026
- MPCD, 2896 - PAERO3, 3028
- MPCREEP, 2897 - PAERO4, 3030
- MPCY, 2899 - PAERO5, 3032
- MPHEAT, 2901 - PANEL, 3036
- MPROCS, 2902 - PARAM, 3037
- MREVERS, 2904 - PARAMARC, 3039
- MRSSCON, 2906 - PAXISYM, 3042
- MSTACK, 2908 - PAXSYMH, 3044
- MT16SEL, 2909 - PBAR, 3046

Main Index
 - PBARL, 3048 - PLOAD, 3206
- PBARN1, 3054 - PLOAD1, 3208
- PBCOMP, 3058 - PLOAD2, 3211
- PBDISCR, 3063 - PLOAD4, 3213
- PBEAM, 3066 - PLOADB3, 3216
- PBEAM3, 3071 - PLOADX1, 3218
- PBEAM71, 3074 - PLOTEL, 3221
- PBEAM71, 3079 - PLPLANE, 3222
- PBEAM71, 3085 - PLSOLID, 3224
- PBEAMD, 3087 - PMARKER, 3225
- PBEAML, 3088 - PMASS, 3226
- PBELTD, 3096 - PMINC, 3227
- PBEMN1, 3097 - PMREBAI, 3229
- PBEND, 3101 - PMREBAR, 3233
- PBMARB6, 3109 - POINT, 3237
- PBMNUM6, 3112 - POINTAX, 3238
- PBMSECT, 3116 - PORFCPL, 3239
- PBRSECT, 3121 - PORFGBG, 3241
- PBSPOT, 3124 - PORFLOW, 3243
- PBUSH, 3126 - PORFLWT, 3245
- PBUSH1D, 3129 - PORHOLE, 3248
- PBUSH2D, 3134 - PORHYDS, 3250
- PBUSHT, 3136 - PORUDS, 3252
- PCOHE, 3142 - PRAC2D, 3253
- PCOMP, 3143 - PRAC3D, 3254
- PCOMPA, 3148 - PRESAX, 3255
- PCOMPF, 3150 - PRESPT, 3256
- PCOMPG, 3152 - PRESTRS, 3257
- PCOMPLS, 3156 - PRIMx, 3258
- PCONEAX, 3161 - PRJCON, 3265
- PCONV, 3163 - PROD, 3267
- PCONVM, 3166 - PRODN1, 3268
- PCONV1, 3168 - PSEAM, 3270
- PDAMP, 3170 - PSET, 3272
- PDAMP5, 3171 - PSHEAR, 3274
- PDAMPT, 3172 - PSHEARN, 3276
- PDUMi, 3173 - PSHELL, 3278
- PELAS, 3174 - PSHELL1, 3283
- PELAS1, 3175 - PSHELLD, 3285
- PELAST, 3176 - PSHLN1, 3293
- PERMEAB, 3178 - PSHLN2, 3298
- PERMGBG, 3180 - PSLDN1, 3303
- PEULER, 3182 - PSOLID, 3307
- PEULER1, 3184 - PSOLIDD, 3313
- PFAST, 3185 - PSPH, 3317
- PFTG , 3189 - PSPRMAT, 3319
- PGAP, 3193 - PSSHL, 3321
- PHBDY, 3196 - PTSHELL, 3322
- PINTC, 3198 - PTUBE, 3324
- PINTS, 3199 - PVAL, 3326
- PLBLAST, 3200 - PVISC, 3328
- PLCOMP, 3202 - PWELD, 3329

Main Index
 - QBDY1, 3332 - ROTORSE, 3448
- QBDY2, 3333 - RROD, 3450
- QBDY3, 3334 - RSPINR, 3452
- QBDY4, 3335 - RSPINT, 3456
- QHBDY, 3336 - RSPLINE, 3459
- QSET, 3338 - RSSCON, 3461
- QSET1, 3339 - RTRPLT, 3464
- QVECT, 3340 - RTRPLT1, 3466
- QVOL, 3343 - RVDOF, 3468
- RADBC, 3345 - RVDOF1, 3469
- RADBC2, 3346 - SANGLE, 3470
- RADBND, 3347 - SBPRET, 3471
- RADC, 3348 - SBRETR, 3475
- RADCAV, 3350 - SBSENSR, 3479
- RADCOL, 3353 - SBSLPR, 3481
- RADCT, 3354 - SEBNDRY, 3483
- RADLST, 3355 - SEBSET, 3484
- RADM, 3357 - SEBSET1, 3485
- RADMT, 3359 - SEBULK, 3487
- RADMTX, 3360 - SECONCT, 3490
- RADSET, 3361 - SECSET, 3492
- RANDPS, 3362 - SECSET1, 3493
- RANDT1, 3364 - SECTAX, 3495
- RBAR, 3365 - SEDLINK, 3496
- RBAR1, 3367 - SEDRSP2, 3498
- RBAX3D, 3369 - SEDRSP3, 3501
- RBE1, 3371 - SEELT, 3504
- RBE2, 3373 - SEEXCLD, 3505
- RBE2A, 3375 - SELABEL, 3506
- RBE2D, 3376 - SELOC, 3507
- RBE2F, 3381 - SEMPLN, 3509
- RBE2GS, 3383 - SENQSET, 3510
- RBE3, 3386 - SEQGP, 3511
- RBE3D, 3389 - SEQROUT, 3512
- RBE3U, 3392 - SEQSEP, 3513
- RBJOINT, 3393 - SEQSET, 3515
- RBJSTIF, 3404 - SEQSET1, 3517
- RCONN, 3415 - SESET, 3519
- RCPARM, 3417 - SESUP, 3520
- RCROSS, 3420 - SET1, 3521
- RELEASE, 3422 - SET2, 3522
- RESTART, 3424 - SET3, 3524
- RESTART, 3427 - SET4 , 3526
- RFORCE, 3430 - SETREE, 3527
- RGYRO, 3434 - SEUSET, 3529
- RINGAX, 3436 - SEUSET1, 3530
- RINGFL, 3438 - SHREL, 3531
- RJOINT, 3439 - SHRPOL, 3532
- RLOAD1, 3440 - SHRUDS, 3533
- RLOAD2, 3442 - SLBDY, 3534
- ROTORAX, 3444 - SLOAD, 3535
- ROTORG, 3446 - SLOADN1, 3536

Main Index
 - SNORM, 3537 - TABLEM3, 3637
- SPBLND1, 3539 - TABLEM4, 3639
- SPBLND2, 3541 - TABLES1, 3640
- SPC, 3542 - TABLEST, 3642
- SPC1, 3544 - TABLFTG, 3643
- SPCADD, 3546 - TABRND1, 3644
- SPCAX, 3547 - TABRNDG, 3646
- SPCD, 3548 - TABSCTL, 3647
- SPCD2, 3550 - TEMP, 3649
- SPCNR, 3554 - TEMPAX, 3651
- SPCOFF, 3556 - TEMPB3, 3652
- SPCOFF1, 3557 - TEMPBC, 3654
- SPCR, 3558 - TEMPD, 3657
- SPHDEF, 3560 - TEMPF, 3659
- SPHERE, 3563 - TEMPN1, 3660
- SPHSYM, 3564 - TEMPP1, 3662
- SPLINE1, 3565 - TEMPP3, 3665
- SPLINE2, 3567 - TEMPRB, 3666
- SPLINE3, 3569 - TERMIN, 3669
- SPLINE4, 3571 - TF, 3671
- SPLINE5, 3573 - THPAD, 3672
- SPLINE6, 3575 - TIC, 3678
- SPLINE7, 3578 - TICD, 3679
- SPLINEX, 3580 - TICEL, 3680
- SPLINRB, 3582 - TICEUDS, 3682
- SPOINT, 3583 - TICEUL1, 3683
- SPRBCK, 3584 - TICREG, 3684
- SPRELAX, 3588 - TICVAL, 3686
- SPWRS, 3589 - TIC3, 3688
- STOCHAS, 3591 - TIMNAT, 3690
- SUPAX, 3593 - TIMNVH, 3691
- SUPORT, 3594 - TIMSML, 3697
- SUPORT1, 3595 - TIRE1, 3698
- SUPORT6, 3597 - TLOAD1, 3699
- SURFINI, 3599 - TLOAD2, 3702
- SWLDPRM, 3601 - TMPSET, 3706
- TABD1MD, 3608 - TODYNA, 3708
- TABDMP1, 3610 - TOMVAR, 3709
- TABISTR, 3613 - TOPVAR, 3711
- TABL3D, 3614 - TRIM, 3714
- TABLE3D, 3619 - TRIM2, 3715
- TABLED1, 3620 - TRMCPL, 3717
- TABLED2, 3623 - TSTEP, 3719
- TABLED3, 3625 - TSTEPNL, 3720
- TABLED4, 3627 - TTEMP, 3727
- TABLED5, 3628 - UDNAME , 3729
- TABLEHT, 3629 - UDSESV, 3730
- TABLEDR, 3630 - UNBALNC, 3732
- TABLEH1, 3631 - UNGLUE, 3734
- TABLEL1, 3632 - UNGLUE, 3735
- TABLEM1, 3633 - USET, 3737
- TABLEM2, 3635 - USET1, 3738

Main Index
 - USRSUB6, 3740 - WETSURF, 3770
- UXVEC, 3741 - YLDHY, 3771
- VCCT, 3742 - YLDJC, 3772
- VCCT, 3744 - YLDMC, 3774
- VIEW, 3747 - YLDMSS, 3775
- VIEW3D, 3749 - YLDPOL, 3777
- VIEWEX, 3751 - YLDRPL, 3778
- WALL, 3756 - YLDSG, 3779
- WALLGEO, 3761 - YLDTM, 3780
- WEAR, 3764 - YLDUDS, 3782
- WETELME, 3766 - YLDVM, 3784
- WETELMG, 3767 - YLDZA, 3787
- WETLOAD, 3768

A
Configuring the  Specifying Parameters, 2
Runtime Environment  Command Initialization and Runtime Configuration Files, 2
 Environment Variables, 6
 User-Defined Keywords, 8
 General Keywords, 8
 PARAM Keywords, 9
 Value Descriptors, 10
 Examples:, 12
 Resolving Duplicate Parameter Specifications, 13
 Customizing Command Initialization and Runtime Configuration Files, 16
 Examples, 18
 Symbolic Substitution, 22
 Introduction, 22
 Simple Examples, 22
 Detailed Specifications, 25
 Examples, 34

Main Index
Main Index
 Preface MSC Nastran Quick Reference Guide

Preface


List of Nastran Books
 Technical Support

Training and Internet Resources

Main Index
 xx MSC Nastran Quick Reference Guide
List of Nastran Books

List of Nastran Books

Below is a list of some of the Nastran documents. You may find any of these documents from MSC
Software at http://simcompanion.mscsoftware.com/infocenter/index?page=home.

Installation and Release Guides

• Installation and Operations Guide
• Release Guide
Guides
Reference Books
• Quick Reference Guide
• DMAP Programmer’s Guide
• Reference Manual

User’s Guides
• Getting Started
• Linear Static Analysis
• Dynamic Analysis
• Embedded Fatigue
• MSC Nastran Demonstration Problems
• Thermal Analysis
• Superelements
• Design Sensitivity and Optimization
• Implicit Nonlinear (SOL 600)
• Explicit Nonlinear (SOL 700)
• Aeroelastic Analysis
• User Defined Services
• Nastran Embedded Fatigue User’s Guide
• Non Linear User's Guide (SOL 400)

Main Index
 Preface xxi
Technical Support

Technical Support
For technical support phone numbers and contact information, please visit:
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx
Support Center (http://simcompanion.mscsoftware.com)

The SimCompanion link above gives you access to the wealth of resources for MSC Software products.
Here you will find product and support contact information, product documentations, knowledge base
articles, product error list, knowledge base articles and SimAcademy Webinars. It is a searchable
database which allows you to find articles relevant to your inquiry. Valid MSC customer entitlement and
login is required to access the database and documents. It is a single sign-on that gives you access to
product documentation for complete list of products from MSC Software, allows you to manage your
support cases, and participate in our discussion forums.

Main Index
 xxii MSC Nastran Quick Reference Guide
Training and Internet Resources

Training and Internet Resources

MSC Software (www.mscsoftware.com)

MSC Software corporate site with information on the latest events, products and services for the
CAD/CAE/CAM marketplace.
http://simcompanion.mscsoftware.com

The SimCompanion link above gives you access to the wealth of resources for MSC Software products.
Here you will find product and support contact information, product documentations, knowledge base
articles, product error list, knowledge base articles and SimAcademy Webinars. It is a searchable
database which allows you to find articles relevant to your inquiry. Valid MSC customer entitlement and
login is required to access the database and documents. It is a single sign-on that gives you access to
product documentation for complete list of products from MSC Software, allows you to manage your
support cases, and participate in our discussion forums.
http://www.mscsoftware.com/msc-training

The MSC-Training link above will point you to schedule and description of MSC Seminars. Following
courses are recommended for beginning Nastran users.
NAS101A - Linear Static and Normal Modes Analysis using MSC Nastran

This course serves as an introduction to finite element analysis. It includes discussion of basic features
available in MSC Nastran for solving structural engineering problems. In this course, all finite element
models will be created and edited using a text editor, not a graphical pre-processor. Proper data structure
of the MSC Nastran input file is covered. At the conclusion of seminar, the student will be familiar with
fundamental usage of MSC Nastran.
NAS101B - Advanced Linear Analysis using MSC Nastran

This course is a continuation of NAS101A - Linear Static and Normal Modes Analysis using MSC
Nastran. In this class, you will learn: Theory of buckling analysis and how to perform a buckling analysis
About rigid elements - MPC, RBAR,RBE2, and RBE3 Modeling with interface element CINTC and
connectors Lamination theory and composite materials MSC Nastran composite theory Failure theories
Linear contact and permanent glued contact Different model checks Modeling tips and tricks
NAS120 - Linear Static Analysis using MSC Nastran and Patran

This seminar introduces basic finite element analysis techniques for linear static, normal modes, and
buckling analysis of structures using MSC Nastran and Patran. MSC Nastran data structure, the element
library, modeling practices, model validation, and guidelines for efficient solutions are discussed and
illustrated with examples and workshops. Patran will be an integral part of the examples and workshops
and will be used to generate and verify illustrative MSC Nastran models, manage analysis submission
requests, and visualize results. This seminar provides the foundation required for intermediate and
advanced MSC Nastran applications.

Main Index
 nastran Command and NASTRAN Statement MSC Nastran Quick Reference Guide

1 nastran Command and

NASTRAN Statement


The nastran Command

The NASTRAN Statement

Main Index
 2 MSC Nastran Quick Reference Guide
The nastran Command

The nastran Command

MSC Nastran is executed with a command called nastran. (Your system manager may assign a different
name to the command.) The nastran command permits the specification of keywords used to request
options affecting MSC Nastran job execution. The format of the nastran command is:
nastran input_data_file [keyword1 = value1 keyword2 = value2 ...]
where input_data_file is the name of the file containing the input data and keywordi = valuei is one or
more optional keyword assignment argument(s). Input data names must follow the Universal Naming
Convention ( Ampersand characters are invalid ). For example, to run a job using the data file
example1.dat, enter the following command:
nastran example1
Keyword assignments can be specified as command line arguments and/or included in RC files.
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 .nast2014rc on Linux and nast2014.ref 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 20121.ref) (see Using Filenames and Logical Symbols (p. 67) in the MSC Nastran 2016
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 (p. 45) in the MSC Nastran 2016 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.

after after = time Default: None

(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: nastran example after=10:00
The job is held until 10:00 AM.

Main Index
 nastran Command and NASTRAN Statement 3
The nastran Command

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: nastran 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: nastran example batch=no

Result: The job is run in the foreground.
bpool bpool=value Default: 25% of memory requested
Used to control the amount of memory for IO buffering.
Buffer pooling is achieved by dedicating a portion of MEM to buffer pool activity
("BPOOL"). An exception to this process occurs when running SOL 101 or SOL 400.
In these cases, "mem=max" invokes the estimate program, which determines the
BPOOL size. The amount of memory can be specified in either GINO blocks, in GB,
or as a percentage of the physical memory.
The use of bufferpool reduces the amount of I/O to physical devices, but too large a
bufferpool results in insufficient memory to obtain an efficient computational
sollution.
buffsize buffsize=value Default: 8193 words
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.

Main Index
 4 MSC Nastran Quick Reference Guide
The nastran Command

dbs dbs=pathname Default= . {Current directory}

Creates database files (see Using the NASTRAN Statement (p. 101) in the MSC
Nastran 2016 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: msc2014 nastran 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: msc2014 nastran 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: msc2014 nastran 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: msc2014 nastran 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: msc2014 nastran 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: msc2014 nastran example dmp=4
host=a:b:c:d dbs=/aa:/bb:/cc:/dd
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.

Main Index
 nastran Command and NASTRAN Statement 5
The nastran Command

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 direct solution of the linear system of equations will be performed in parallel
for all solution sequences
• 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 dmparallel > 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 the element 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.

gpuid gpuid=id,id or gpuid=id:id Default: none

id: the ID of a licensed GPU device to be used in the analysis. Multiple IDs
may be assigned to MSC Nastran distributed memory processor (DMP) runs.
Separate a list of IDs with a comma or a colon. Each DMP process will be
assigned a GPU ID in round robin fashion.

GPGPU processing is available for direct solution methods only; iterative

methods are not supported.
gpu_min_front gpu_min_front=value Default: 16
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.

Main Index
 6 MSC Nastran Quick Reference Guide
The nastran Command

gpu_min_rank gpu_min_rank=value Default: 1024

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.

memory memory=memory_size Default=max

Specifies the amount of open core 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 4 or 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: nastran example memory=5gb
Result: The job is run using an open core memory size of 5 gigabytes.
Example: nastran 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 (Ch. C) in the MSC Nastran
Installation and Operations Guide.
memorymax memorymax=maximum user Default: 0.5 x the amount of physical memory on
memory your 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 between 0.8xphysical to 0.85xphysical.
mode mode=i4 or i8 Default: i8
Determines whether large memory address space can be used on 64-bit machines.
i8 is recommended for all large problems.

Main Index
 nastran Command and NASTRAN Statement 7
The nastran Command

mode=i8 is not applicable on Win32 machines.

mode=i8 should not be used for global or multi-model optimization.

news news={yes|no|auto} Default=yes

Displays the news file (install_dir/msc2014/nast/news.txt on LINUX and
install_dir\msc2014\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: nastran example news=yes
Result: The news file is displayed in the .f06 file after the title page block.
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: nastran 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: msc2014 nastran 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
 8 MSC Nastran Quick Reference Guide
The nastran Command

Apparently, the user ran the job four times, but deleted some of the files; e.g.
v2401.f04.3
v2401.f06.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: msc2014 nastran example
or: msc2014 nastran 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: msc2014 nastran 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: msc2014 nastran 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: msc2014 nastran 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
 nastran Command and NASTRAN Statement 9
The nastran Command

rcf rcf=pathname Default=no

Specifies the name of the local RC file. If this keyword is not specified,
the .nast2014rc file on LINUX and nast2014.rcf on Windows located in the input
data file’s directory is used.
Example: $ nastran 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 ./.nast2014rc on LINUX,
and .\nast2014.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
(p. 445) in the MSC Nastran Reference Manual 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.
Example: nastran 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 (p. 74) in the MSC Nastran 2016
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: nastran example sdir=/scratch
Result: Scratch files are created in the directory /scratch.

Main Index
 10 MSC Nastran Quick Reference Guide
The nastran Command

smp smp=number Default: No use of parallization on shared memory

tasks
The smp keyword specifies the number of processors used to efficiently obtain a
solution to the simulation. The processors used will be on a single machine. If DMP
is used, then SMP processors will be used on each DMP process (on each host if
multiple hosts are used).
smp parallization is available for mathematical kernals.
smp parallization may be used for solution of linear equations in SOL 400; the
SPARSESOLVER Executive Control Statement is also required.
smp parallization may be used for solution of linear equations in SOL 101 if contact
is used without permanent glue; the SPARSESOLVER Executive Control Statement
is also required.
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.
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'

Main Index
 nastran Command and NASTRAN Statement 11
The nastran Command

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 (p. 100) in the MSC Nastran 2016
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.

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.
Example:

If user routine is written in Fortran: nastran example uds=mysource.F

If user routine is written in C++: nastran example uds=mysource.cpp

Main Index
 12 MSC Nastran Quick Reference Guide
The nastran Command

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: nastran 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: nastran example uds=mysource.F
udssave=/scratch/mydir

xmonast xmonast={yes|no|kill} Default: No

Indicates if XMONAST is to be run to monitor the MSC Nastran job. If
“xmonast=yes” is specified, XMONAST will be automatically started; you must
manually exit XMONAST when the MSC Nastran job has completed. If
“xmonast=kill” is specified, XMONAST will start and will automatically exit when
the MSC Nastran job has completed.
Example: nastran example xmon=kill
This example runs the XMONITOR utility while the MSC Nastran job is running.
Once the job completes, the XMONITOR program is automatically terminated.

( * xmonast will be removed in future versions )

Main Index
 nastran Command and NASTRAN Statement 13
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 MSC Nastran
2016 Installation and Operations Guide .

Main Index
 14 NASTRAN
Executive System Parameter Modification

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 1-1.
SYSTEM Specifies the system cell number.
expression See DEFINE statement for description.
i System cell number from Table 1-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 Quick
Reference 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 (p. 30) 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) = 4097
or
NASTRAN BUFFSIZE = 4097

Main Index
 BUFFSIZE (1) 15
Executive System Parameter Modification

or, if a prior DEFINE statement had defined a keyword MY_SYSBUF to the value 4097, then the
following code could be used:
NASTRAN SYSTEM(1)=MY_SYSBUF
or
NASTRAN BUFFSIZE=MY_SYSBUF
The following statement is used to request execution of MSGMESH:
NASTRAN MESH
2. Table 1-1 gives a summary of the recommended system cells. System Cells
.

Table 1-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.
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 600 or
SOL 700.
NLINES (9) Specifies the number of lines printed per page of output. LINE
(Case), 387.
MAXLINES (14) MAXLINES (Case), 396

METIME (20) Minimum time for execution summary table message. Output
Description (p. 320) in the MSC Nastran Reference Manual.
APP (21) Approach Flag. See the APP, 105 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, 112.
CONFIG (28) Machine subtype
MESH (31) Requests execution of MSGMESH.
ADUMi (46 - 54) Dummy element flag, i=1 through 9.
HEAT (56) APP, 105

0 Structural analysis (Default).

1 Heat transfer
DIAGB (61) Alternate method to set diagnostics 33 through 64. DIAG, 112.
PUNCH (64) Specifies FORTRAN unit number for PUNCH file (.f07).
(Default=7)

Main Index
 16 MPYAD (66)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
MPYAD (66) Selects/deselects multiplication methods. MPYAD (p. 1201) in the
MSC Nastran DMAP Programmer’s Guide.
SOLVE (69) Controls matrix decomposition for MSCLDL and MSCLU. Same
as DECOMP (p. 733) in the MSC Nastran DMAP Programmer’s
Guide and the Option Selection (p. 69) in the MSC.Nastran
Numerical Methods User’s Guide.
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 (p. 712) in the
MSC Nastran DMAP Programmer’s Guide.
DMAP (82) Allows NOGO to operate. See Processing of User Errors (p. 40) in
the DMAP Programmer’s Guide.
F04 (86) Specifies FORTRAN unit number for Execution Summary Table
(.f04). Output Description (p. 320) in the MSC Nastran Reference
Manual (Integer > 0; a value of 0 sends the results to the log file;
Default = 4).
RADMTX (87) Type of radiation exchange coefficients, RADMTX, 3360.
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.

Main Index
 RADLST (88) 17
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
2 Direct input of a unsymmetric SCRIPT-AF matrix on
RADMTX and RADLST entries is allowed. Due to the
symmetry, 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, 3355.
NEWHESS (108) Request complex eigenvalue method. See the EIGC, 1927 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 (p. 45) in
the MSC Nastran 2016 Installation and Operations Guide.
(119) Controls the type of bufferpool method to be used:
4 Use Version 2012.2 bufferpool method. Default = 4.
Not 4 Use Version 2012.1 bufferpool method.
ATTDEL (124) Controls the automatic assignment of the delivery database.
Database Concepts (p. 445) in the MSC Nastran Reference
Manual. See also Creating and Attaching Alternate Delivery
Databases (p. 173) in the MSC Nastran 2014 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
1 Enable NOKEEP

Main Index
 18 SPARSE (126)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
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, 81 FMS statement.
0 Do not update.
>0 Time, in minutes, between database directory updates.
SMPYAD67 (129) Select pre-Version 67 method in the SMPYAD module. SMPYAD
(p. 1473) 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 (p. 445) in the MSC Nastran
Reference Manual.
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

Main Index
 SCR300 (142) 19
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
SCR300 (142) Requests creation of SCR300 partition on SCRATCH DBset.
INIT, 89 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.
(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 MSC Nastran Nonlinear
Handbook.
0 Update Δu R and Δu p at every iteration with 2 (Default).
1 Update Δu R only with 2.
2 Update Δu R only with 2*.

FBSMEM (146) Reserves part of Nastran open core memory for faster solution in
the Lanczos method of eigenvalue extraction. Default = 0. When
FBSMEM is less than or equal to 0, available memory is used to
store the factor matrix for use during forward-backward
substitution (FBS) operations (aka “factor caching”). System
Information Message 4199 is printed in the F04 file when the
factor matrix is cached.
Set FBSMEM=1 to disable Lanczos factor caching.
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.

Main Index
 20 DBVERCHK (148)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
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, 89 FMS statement
(Default = 100).
(151) Requests spill or no spill of the SCR300 partition of SCRATCH
DBset. INIT, 89 FMS statement (Default = 0).
DBLAMKD (155) Differential stiffness formulation for CBEAM and CTETRA
elements.
0 Current formulation (Default)
1 Pre-Version 67 formulation
(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. When using Intel
MKL Pardiso, output matrix to a file in Matrix Market
format.
32 Turn off internal matrix scaling in the READ module.
Turn off matrix scaling in Intel MKL Pardiso.
64 Turn off internal matrix balancing in the READ module.

Main Index
 LDQRKD (170) 21
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
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.
131072 Use Intel MKL Pardiso factorization method. Only
valid for NLSOLV module, and KMETH=FNT/PFNT.
See http://software.intel.com/en-us/node/470282. In- or
Out-of-core solution method will be used, based on the
amount of memory provided to Nastran.
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
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).
SCRSAVE (196) Lanczos high performance option: Controls reuse of scratch files
in segment logic.
0 Do not reuse (Default)
1 Reuse

Main Index
 22 MINFRONT (198)
Executive System Parameter Modification

Table 1-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.

Main Index
 USPARSE (209) 23
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
2048 Selects METIS reordering in Intel MKL Pardiso sparse
solver.
4096 Selects OpenMP (SMP) METIS reordering in Intel
MKL Pardiso sparse solver.
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.
PUNCHTYPE (210) Used to control punch formula.
0 “Old” punch, default in MSC Nastran 2001 and earlier
versions.
1 “New” punch, default in MSC Nastran 2004 and uses
the NDDL.
2 Same as 1 except the line numbers are eliminated.
CHEXAINT (212) Specifies CHEXA element’s integration rule for p-adaptive
analysis and p=2x2x2 (only).
0 Reduced (Default)
1 Full
DISTORT (213) Element distortion fatal termination override. Applies to all
p-elements and the TETRA h-elements.
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).

Main Index
 24 (253 - 262)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
(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, 1938. The default is 7 for most
machines but it is machine dependent.
QUARTICDLM A value of 1 selects the new quartic formulation of the doublet
(270) lattic kernel (N5KQ), while 0 selects the original quadratic form
(Default = 0).
(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 Print additional spline quality information
(281)
=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

Main Index
 (309) 25
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
<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, 3654 for more
information. The default stiffness is 1.0E10.
INDEX (316) Indexes and/or saves a minimum set of data blocks to the database
needed to for postprocessing in Patran or the toolkit. 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.)
XMSG (319) If set to 1, gives extended error messages (Default = 0).
OLDDAREA (320) Do not convert DAREA Bulk Data entries for grid and scalar
points to equivalent FORCE/MOMENT/SLOAD Bulk Data
entries (equivalent to SYSTEM(320) = -1).
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

Main Index
 26 QLHOUL (359)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
Setting this system cell to 1 causes all continuation fields to be
ignored and treated as blank. If set to 1, the continuation entries
must immediately follow the parent.
System cell (357) only works when IFPSTAR=NO, it is fixed to 1
when IFPSTAR=YES
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)
1 Selects the old formulation for CQUADR/CTRIAR.

Main Index
 PARAMCHK (372) 27
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
2 Converts CQUADR/CTRIAR into QUAD4/CTRIA3
using the alternate CQUAD4/CTRIA3 formulation.
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
1 Issue User Fatal Message for the initialized parameter
(Default = 0)
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.

Main Index
 28 KRYLOV4 (390)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
-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.
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)

Main Index
 DEF_DENS (408) 29
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
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).
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.
> Lumped Mass matrix will contain translational
components only for CBAR and CBEAM elements.
OLDTLDMTH (428) If nonzero, requests the pre-version 2005 r3 method for computing
thermal expansion in CHEXA, CPENTA, and CTETRA elements.
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

Main Index
 30 (444)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
(444) 0 Selects the pre Nastran 2010 release of IFP for bulk data
processing.
1 Selects the MSC Nastran 2010 release Common Data
Model for data processing. (Default)
On command line SYS444=0 or 1
Or
IFPSTAR YES Select the Nastran Common Data Model for data
processing. (Default)
NO Select the MSC Nastran IFP for bulk data processing.
On command line IFPSTAR=YES or NO.
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
 PARSLAVE(449) 31
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
PARSLAVE(449) Bitwise control of DMP operations in SOL 400 nonlinear analysis.
Bit Value Description
1 0 Slave processes execute the entire analysis.
This value is recommended for distributed
execution. (Default)
1 Slave 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).
The default value if Bit 1 is determined 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.
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
 32 NONUPIV (653)
Executive System Parameter Modification

Table 1-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, 2833,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_FRONT The criteria for GPGPU execution during matrix factorization are
(655) 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 1024.
GPU_MIN_RANK If the rank of the frontal matrix is smaller than value, the rank
(656) 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 16.
(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
 SEGLOG(664) 33
Executive System Parameter Modification

Table 1-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.
0 Use the existing/old logic (Default) 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 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.
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
1 Use old algorithm (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).
(679) Controls checking for validity of sparse matrix passed to Intel
MKL Pardiso. Column indices must be in increasing order within
rows.
0 Disable matrix checking (Default)
1 Enable matrix checking

Main Index
 34 (680)
Executive System Parameter Modification

Table 1-1 System Cell Summary (continued)

System Cell
Name (Number) Function and Reference
(680) Controls the maximum number of iterative refinement steps used
in solution phase with Intel MKL Pardiso.
i=0 Two steps (Default)
i>0 Use a maximum of i steps
i<0 Use a maximum of abs(i) steps, and extended precision
and complex data types for residual computation
(681) Controls the use of (non-)symmetric weighted matching in Intel
MKL Pardiso. When enabled, large entries near the diagonal can
be permuted, leading to a more robust pivoting strategy, at the cost
of higher memory requirements.
0 Disable weighted matching
1 Enable weighted matching (Default)
(682) Controls the use of partial pivoting for indefinite problems in Intel
MKL Pardiso. Enabling Bunch-Kaufman 2x2 pivoting is
recommended for highly indefinite problems where, when
combined with sufficient iterative refinement, it leads to a more
robust partial-pivoting scheme.
0 Use 1x1 diagonal pivoting
1 Use 1x1 and 2x2 Bunch-Kaufman pivoting (Default)
RDBOTH(695) Parameter to select Rayleigh damping approach for rotordynamics
(compatibility withV2005) implementation, Integer
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
S2SDEF(701) Parameter to control backward compatibility of Seg-to-Seg
contact default values.
0 Original Seg-to-Seg contact default values Original
Seg-to-Seg contact default values
1 New Seg-to-Seg contact default values (Default)

Main Index
 File Management Statements MSC Nastran Quick Reference Guide

2 File Management Statements

 Key to Descriptions

The File Management Section (FMS)

Main Index
 36 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
thingsasasthethe
statement’s
statement’srelationship
relationshiptotoother
otherstatements,
statements,
restrictions
restrictionsand
andrecommendations
recommendationson onitsitsuse,
use,
and
andfurther
furtherdetails
detailsregarding
regardingthe
thedescribers.
describers.

Main Index
 File Management Statements 37
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 (p. 445) in the MSC
Nastran Reference Manual. 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.
DBDIR
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.

Main Index
 38 MSC Nastran Quick Reference Guide
The File Management Section (FMS)

INIT Creates a temporary or permanent DBset.

NASTRAN Specifies values for system cells.
PROJ Defines the current or default project identifier.

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:

Main Index
 File Management Statements 39
The File Management Section (FMS)

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
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.

Main Index
 40 MSC Nastran Quick Reference Guide
The File Management Section (FMS)

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.
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.

Main Index
 File Management Statements 41
The File Management Section (FMS)

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[;...])
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 (p. 8) in the 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
 42 $
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 43
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
 44 ASSIGN
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 = ]   [ RECL = 1 ] [ SIZE = s ]
 UNFORMATTED 
 AIX64 
 
 LITTLEENDIAN (or LTLEND) 
 
 LITTLEENDIAN64 (or LITT64) 
 LTLEND64 (or LTLE64) 
 
 <ostype> 

TEMP
[DEFER ] [ DELETE] [SYS = ‘sys-spec’]
DELZERO

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:

Main Index
 ASSIGN 45
Assigns Physical File

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 LITTLEENDIAN 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 LITTLEENDIAN
...
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.
DELETE Requests that the file associated with logical-key/UNIT, if it exists before
the start of the run, be deleted.
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,
LITTLEENDIAN, LTLEND, LITTLEENDIAN64, LTLEND64, <ostype>)
format. See Remark 10., 11., 12., 13. and 18.

Main Index
 46 ASSIGN
Assigns Physical File

Describer Meaning
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.

Remarks:
1. The ASSIGN statement and its applications are discussed further in the Database Concepts
(p. 445) in the MSC Nastran Reference Manual.
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 2-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 2-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. Also, unit numbers 1 through 10, 14, 16, 18, 19 and 21
should not be assigned. PUNCH and PLOT may be used, but are not recommended.
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.

Main Index
 ASSIGN 47
Assigns Physical File

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 it is necessary to execute the INPUTT4 and OUTPUT4 modules on the same unit, then specify
ASSIGN OUTPUT4 only. The same is recommended for the INPUTT2 and OUTPUT2 modules.
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.
• FORMAT=NEUTRAL is selected on the DBUNLOAD and DBLOAD FMS statements that
process the unit. See the Database Concepts (p. 445) in the MSC Nastran Reference Manual.
• 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 using FORM=LITTLEENDIAN,
FORM=LTLEND, FORM=LITTLEENDIAN64, FORM=LTLEND64 or FORM=<ostype>. The
keywords with a "64" appended are for use on long-word systems (mode=i8) or
FORM=<ostype>. The FORM= specifications are used when the generated output file is to be
processed on a platform other than current platform. The format appropriate for the platform on
which the file is to be processed (the target platform) must be specified. The FORM=<ostype>
specification can by used as a convenience, allowing the desired output format to be specified
using the target platform OS name or vendor (if there can be no ambiguity) instead of its actual
binary file format. <ostype> can be one of the following:
• Machines LINUX and WINDOWS are equivalent to LITTLEENDIAN.

Main Index
 48 ASSIGN
Assigns Physical File

See the MSC Nastran Installation and Operations Guide for further information on binary file
formats.
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. That is, a binary file in BIGENDIAN format
cannot be processed on a LITTLEENDIAN platform and vice versa. This is also true on long-
word systems where for example a BIGENDIAN64 cannot be processed as a BIGENDIAN.
13. For the DBUNLOAD FMS statement and OUTPUT2 module, if FORM is other than
UNFORMATTED (or equivalent, e.g., LITTLEENDIAN 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 MSC Nastran Installation and Operations Guide 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.
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 SirnXpert may fail to process the results.

Main Index
 ASSIGN 49
Assigns Physical File

Table 2-1 FORTRAN Files and Their Default Attributes

Logical
Key Physical Unit Description/
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
AESO out.AESO 23 FORMATTED NEW YES YES SEQ. Optimization
DBC out.xdb 40 UNFORMATTED NEW YES YES DIRECT Database Converter
Unit
DBUNLOAD REQ 50 UNFORMATTED* NEW YES NO SEQ. DBUNLOAD FMS
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

Main Index
 50 ASSIGN
Assigns Physical File

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.
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.

Main Index
 ASSIGN 51
Assigns Physical File

++ 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.

Main Index
 52 CONNECT
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 geometric entities. These entities should belong to the same evaluator-class
(a set of routines that process them), and should reside on the same database. The GMCURV and
GMSURF Bulk Data entries relate to the GEOMEVAL type.
2. 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.
3. A group of external spline entities. The SPLINEX Bulk Data entry relates to the SPLINEX type.
4. 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.

Main Index
 CONNECT 53
User Defined Service and Group Evaluator Data

Old Group Examples:

CONNECT GEOMEVAL FENDER, CATIA, ‘ ‘/u/kiz/adp’, ‘Version=6 as of
1/31/93’
In this case, the user is requesting that all calculations on GMCURV and GMSURF Bulk Data
entries that are grouped as FENDER use the CATIA database/evaluator. For each GMCURV and
GMSURF entry where the group parameter is set to FENDER, appropriate evaluator routines will
be called to initialize and perform computations on the curve or surface.
CONNECT GEOMEVAL HOOD, MSCRPC
In this case, the user is requesting that all calculations on GMCURV and GMSURF Bulk Data
entries that are grouped as HOOD use the Nastran RPC database/evaluator. There is no need for
additional routines to be supplied by the user since the MSCRPC and MSCEQN evaluator
libraries are included in the standard Nastran delivery.
CONNECT GEOMEVAL DOOR, MSCEQN
In this case, the user is requesting that all calculations on GMCURV and GMSURF Bulk Data
entries that are grouped as DOOR use the Nastran EQUATION database/evaluator. There is no
need for additional routines to be supplied by the user since the MSCRPC and MSCEQN
evaluator libraries are included in the Nastran standard delivery.
CONNECT BEAMEVAL HOIST, NEWBEAMS
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

Main Index
 54 CONNECT
User Defined Service and Group Evaluator Data

Describer Meaning
(Old Group Format)
group Group name referenced by the GROUP field on DRESP3, GMCURV,
GMSURF, 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.

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 geometric data defined by GMCURV and GMSURF entries, or
beam cross section data defined by PBARL and PBEAML entries.

Main Index
 CONNECT 55
User Defined Service and Group Evaluator Data

2. Two reserved group names, MSCGRP0 and MSCGRP1, have been predefined for geometric
entities. These names may be used in the GMCURV and GMSURF entries without being defined
explicitly by means of a CONNECT FMS statement. 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
 56 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,
94.)

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 57
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
 58 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, . . .),

 A , … ,
SORT  colname = 
 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 59
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
 60 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 2-2 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 LOCAL DATABLOCKS 6.
a 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) ,

Main Index
 DBDICT 61
Prints Database Directory Tables

LABEL(’NDDL 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 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 2-1 DBDICT DATABLK Example

Table 2-3 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.

Table 2-3 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.

Main Index
 62 DBDICT
Prints Database Directory Tables

Table 2-3 DBDICT DATABLK Colnames (continued)

Default Default
colname col-width col-label Description
EQUIVD 4 EQ Equivalenced flag.
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 63
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 2-2 DBDICT PARAM Example

Table 2-4 gives the allowable colnames along with a description that may be specified in the
FORMAT, SELECT, and SORT describers.

Table 2-4 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
 64 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 2-3 DBDICT QUALIFIERS Example

QUALALL selects all qualifiers to be printed. The qualifiers will be printed in alphabetic order.
QUALSET selects the only the qualifiers SEID, PEID, SPC, MPC, LOAD, and METH to be
printed.
Table 2-5 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.

Table 2-5 DBDICT QUALIFIERS Colnames

Default Default
colname col-width col-label Description
KEY 5 KEY Key number.
qual-name See Note. qualifier name Qualifier name.

Main Index
 DBDICT 65
Prints Database Directory Tables

Table 2-5 DBDICT QUALIFIERS Colnames

Default Default
colname col-width col-label Description
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 2-4 DBDICT QUALCURR Example

Table 2-6 gives the allowable colnames and a description that may be specified in the SELECT
describers.

Table 2-6 DBDICT QUALCURR Colnames

Default Default
colname col-width col-label Description
qual-name See Note. qualifier name Qualifier name.

Main Index
 66 DBDICT
Prints Database Directory Tables

Table 2-6 DBDICT QUALCURR Colnames

Default Default
colname col-width col-label Description
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 2-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 2-7 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.

Table 2-7 DBDICT DATABLK(LOCAL) Colnames

Default Default
colname col-width col-label Description
NAME 8 NAME Parameter name.
SUBDMAP 8 SUBDMAP SubDMAP name.

Main Index
 DBDICT 67
Prints Database Directory Tables

Table 2-7 DBDICT DATABLK(LOCAL) Colnames

Default Default
colname col-width col-label Description
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
ALTSHAPE SESTATIC 0
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 2-6 DBDICT PARAM(LOCAL) Example

Table 2-8 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.

Main Index
 68 DBDICT
Prints Database Directory Tables

Table 2-8 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 2-7 DBDICT PROJVERS Example

Table 2-9 gives the allowable colnames and a description that may be specified in the FORMAT,
SELECT, and SORT describers.

Table 2-9 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.
VERS 10 VERSION Version number.
DELFLG 7 DELETED Flag indicating whether this project/version has
been deleted by the RESTART NOKEEP or
DBCLEAN statements.

Main Index
 DBDICT 69
Prints Database Directory Tables

Table 2-9 DBDICT PROJVERS Colnames

Default Default
colname col-width col-label Description
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,
SEID,PEID) ,
SORT(NAME,SIZE=D) WHERE( SEID=10 OR PEID=10)

Main Index
 70 DBDIR
Prints Database Directory Tables

DBDIR Prints Database Directory Tables

Obsolete. See the DBDICT statement.

Main Index
 DBFIX 71
Database Directory Error Detection

DBFIX Database Directory Error Detection

Detects and optionally corrects errors in the database directory.

 LIST   CORRECT 
Format: DBFIX   
 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
 72 DBLOAD
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
 DBLOAD 73
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.
BINARY BlNARY 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 (p. 445)
in the MSC Nastran Reference Manual.
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
 74 DBLOAD
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 (p. 445) in the MSC Nastran Reference Manual.

Main Index
 DBLOCATE 75
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
 76 DBLOCATE
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
 DBLOCATE 77
Attaches Secondary Databases

Remarks:
1. The DBLOCATE statement and its applications are discussed further in the Database Concepts
(p. 445) in the MSC Nastran Reference Manual.
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
 78 DBSETDEL
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
(p. 445) in the MSC Nastran Reference Manual.
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
 DBUNLOAD 79
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
 80 DBUNLOAD
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,
REWIND then 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
(p. 445) in the MSC Nastran Reference Manual.
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
 DBUPDATE 81
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 (p. 320) in the
MSC Nastran Reference Manual. 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
 82 DEFINE
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
 DEFINE 83
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 NASTRAN, 14 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,9 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 MSC
Nastran 2016 Installation and Operations Guide .
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=4097 LOCATION=SYSTEM(1)
2. Set the sparse matrix selection to forward-backward substitution only:
DEFINE SPARSE=16 LOCATION=SYSTEM(126)

Main Index
 84 DEFINE
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=4097
NASTRAN BUFFSIZE=2048

Valid usage:

DEFINE BUFFSIZE=4097 LOCATION=SYSTEM(1)

NASTRAN BUFFSIZE=2048

Main Index
 ENDJOB 85
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 or DBDIR statement, or after database initialization.

Main Index
 86 EXPAND
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
 EXPAND 87
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 (p. 445) in the MSC Nastran
Reference Manual.

Main Index
 88 INCLUDE
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 MSC Nastran 2016 Installation and Operations Guide for more examples.

Main Index
 INIT 89
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
 90 INIT
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 Kolobytes (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 MSC Nastran 2016 Installation and
Operations Guide 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 nastran Command (p. 6) in the MSC Nastran
Reference Manual. The default is RAM or RAM=30000. NORAM or
RAM=0 specifies that no real memory is to be allocated.

Main Index
 INIT 91
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 nastran Command and NASTRAN Statement, 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. 7) in the
MSC Nastran Reference Manual. The default m is machine dependent and
may be found in the MSC Nastran 2016 Installation and Operations Guide .
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. See the MSC Nastran 2016 Installation and Operations Guide.
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 (p. 445) in
the MSC Nastran Reference Manual.
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
(p. 445) in the MSC Nastran Reference Manual.
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 (p. 445) in the MSC Nastran
Reference Manual.
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
 92 INIT
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 BUFFSlZEbmax statement (see
The NASTRAN Statement (Optional) (p. 7) in the MSC Nastran Reference Manual). 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 MSC Nastran
2016 Installation and Operations Guide 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
 MEMLIST 93
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
 94 PROJ
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, DBDIR, 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, DBDIR, 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.
5. Project-ID is saved with only the first 40 characters specified.

Main Index
 RESTART 95
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.

Remarks:
1. There may only be one RESTART statement in the File Management Section.

Main Index
 96 RESTART
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 4, and 101 through
200 and SOL 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 in one version typically cannot be directly restarted into a different version.
Restrictions are typically documented in the current release guide; however, a DBLOCATE type
restart might work.
7. Restarts do not work with ACMS and DMP.
8. If you are using IFPSTAR (default) than either the IFPDAT file created by the inital run must be
in your current working directory or you must ASSIGN it using a statement similar to:
ASSIGN IFPDB=run1.IFPDAT
9. For SOL 400 one must also use NLRESTART (Case) .

Main Index
 Executive Control Statements MSC Nastran Quick Reference GuideMSC Nastran Quick Reference
Guide

3 Executive Control Statements


Key to Descriptions 98
 Executive Control Statement Descriptions 100

Main Index
 98 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
 Executive Control Statements 99
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 600,ID Creates Marc input and optionally executes Marc from SOL 600
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
 100 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
 $ 101
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
 102 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 103
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 used in conjunction with the COMPILE Executive Control
statement. Note: ALTER statements cannot be used in conjunction with an MALTER statement,
and therefore should never immediately follow this 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)’ $

Main Index
 104 ALTER
Inserts and/or Deletes DMAP Statements

7. The ALTER statement must not exceed 72 characters (no continuations are allowed).
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
or . line. 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 105
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 nastran
Command and NASTRAN Statement, 1.

Main Index
 106 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 107
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
 108 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 .

Main Index
 COMPILE 109
Compiles DMAP Statements

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:
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.

Main Index
 110 COMPILE
Compiles DMAP Statements

• 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
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 MSC Nastran 2016 Installation and Operations
Guide .

Main Index
 COMPILER 111
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
NODECK written 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
NOSORT in 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
 112 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 (p. 320) in the MSC Nastran Reference
Manual.
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 (p. 320) in the MSC Nastran Reference Manual.
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 (p. 320) in the
MSC Nastran Reference Manual.
k=7 Prints eigenvalue extraction diagnostics for the complex determinate method.

Main Index
 DIAG 113
Requests Diagnostic Output

k=8 Prints matrix trailers as the matrices are generated in the execution summary table.
See the Output Description (p. 320) in the MSC Nastran Reference Manual.
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 Uses alternate nonlinear loading 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
(p. 320) in the MSC Nastran Reference Manual.
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 DBDIR 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
 114 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, 3719 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=36 Prints extensive tables generated by the GP0 module in p-version analysis.
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, 707.
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=40 Print constraint override/average information for edges and faces in p-adaptive
analysis
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 TSTEPNL 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.

Main Index
 DIAG 115
Requests Diagnostic Output

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.
k=53 MESSAGE module output will also be printed in the execution summary table.
See the Output Description (p. 320) in the MSC Nastran Reference Manual.
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 (p. 320) in the MSC Nastran
Reference Manual.
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.
k=64 Requests upward compatibility DMAP conversion from Version 65 only. Ignored
in Version 70.5 and later systems.

Main Index
 116 DOMAINSOLVER
Domain Decomposition Solution Method

DOMAINSOLVER Domain Decomposition Solution Method

Selects domain decomposition solution methods.

Format:
STAT
MODES  DOF
FREQ  GRID ,NUMDOM = int,
DOMAINSOLVER  PARTOPT =
ACMS  FREQ

DSA ELEM
NLSOLV

YES SUPER
UPFACT = real ,PRINT = , NCLUST = int, CLUSTSZ = int, COMPMETH = GRID ,
NO
NONE
BEND
MSTSLV MSCMLV 
RUNOPT= , PARTMETH= , TIPSIZE=int 
MULTIMST METISG 
METISO

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)
The keywords function as follows:

STAT Linear statics.

MODES Normal modes.
FREQ Frequency response.
ACMS Automated component modal synthesis.
DSA Design sensitivity analysis. (See Remark 2.)
NLSOLV Nonlinear analysis

The descriptions of the parameters are as follows:

PARTOPT Partitioning option. Selects which domain is to be decomposed.

Main Index
 DOMAINSOLVER 117
Domain Decomposition Solution Method

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 3-1 for further
descriptions.
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 Default = dmp; if NUMDOM has any other value, it will automatically be set to
(STAT) dmp (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
(MODES) to 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.
NUMDOM Default = dmp; if NUMDOM has any other value, it will automatically be set to
(FREQ) dmp (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).
PRINT Controls intermediate print of upstream and data recovery processing in .f06 and
(ACMS) .f04 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
(MODES) Lanczos. 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.

Main Index
 118 DOMAINSOLVER
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.
NONE Specifies that no compression should be done.
RUNOPT Specifies the DMP run option. The following are valid options for RUNOPT:
MSTSLV Specifies "master-slave" DMP execution mode. Only the Master
DMP process executes the full Nastran solution. This is optimal for
single-host DMP execution.
MULTIMST Specifies "multiple-master" 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/below)
METISO Specifies the METIS partitioning method based on the desired tip
size (see TIPSIZE below). Available for ACMS only.

Note: NUMDOM (see above/below) will be ignored for

PARTMETH=METISO.
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

Table 3-1 Analysis Types and Partitioning Methods

Partitioning Methods Available
Solution DMP
Sequence Method GRID DOF FREQ DOF+FREQ ELEM
101 STAT * *
MODES * * *
103
ACMS * *

Main Index
 DOMAINSOLVER 119
Domain Decomposition Solution Method

Table 3-1 Analysis Types and Partitioning Methods (continued)

Partitioning Methods Available
Solution DMP
Sequence Method GRID DOF FREQ DOF+FREQ ELEM
108 FREQ *
MODES *
110
ACMS *
MODES * *
111 ACMS * * * *
FREQ *
MODES *
112
ACMS *
MODES * * *
ACMS * * *
200
FREQ *
DSA
400 STAT *
NLSOLV *

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 3-2 will
result based on solution sequence.

Table 3-2 DOMAINSOLVER Defaults with “dmp=” on command line

Default DOMAINSOLVER Options
Solution Sequence DMP Method Partitioning Option
101 STAT DOF
103 MODES DOF
108 FREQ FREQ
110 MODES FREQ
MODES FREQ
111
FREQ FREQ
112 MODES FREQ
MODES DOF
200
FREQ FREQ

Main Index
 120 DOMAINSOLVER
Domain Decomposition Solution Method

Table 3-2 DOMAINSOLVER Defaults with “dmp=” on command line

Default DOMAINSOLVER Options
Solution Sequence DMP Method Partitioning Option
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)
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

Main Index
 DOMAINSOLVER 121
Domain Decomposition Solution Method

4. In SOL 400, the DOMAINSOLVER NLSOLV (RUNOPT=MULTIMST) 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.

Main Index
 122 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 123
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
 124 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 ], [ 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

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.
NONE None of the optional element geometry tests will be performed.

Main Index
 GEOMCHECK 125
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, 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.
BEAM_OFF Real > 0.0 0.15 CBEAM element offset length ratio.
BAR_OFF Real > 0.0 0.15 CBAR element offset length ratio.

Main Index
 126 GEOMCHECK
Specifies Geometry Check Options

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.
• 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.
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.

Main Index
 ID 127
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
 128 INCLUDE
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 MSC Nastran 2016 Installation and Operations Guide for more examples.

Main Index
 LINK 129
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
 130 LINK
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, 89 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
 MALTER 131
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
 132 MALTER
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
 MALTER 133
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
or< > example, “[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
or . the 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 3-3.
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
 134 MALTER
Inserts and/or Deletes DMAP Statements in Solution Sequences

Table 3-3 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
 MODEL_CHECK 135
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
 136 MODEL_CHECK
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
 MODEL_CHECK 137
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
 138 SOL
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
 SOL 139
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 3-4 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
 140 SOL
Executes a Solution Sequence

Table 3-4 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
600 SESTATIC ( See MSC Nastran API into MSC MARC nonlinear
SOL 600,ID, 141)
700 NLTRAN ( See Nonlinear Explicit Transient Analysis
SOL 700,ID, 161)

Main Index
 SOL 600,ID 141
Executes Marc from Inside Nastran

SOL 600,ID Executes Marc from Inside Nastran

Creates Marc input and optionally executes Marc from inside SOL 600.

Format:
SOL 600, ID PATH= COPYR= NOERROR MARCEXE=SOLVE NOEXIT
OUTR=op2,xdb,pch,f06,eig,dmap,beam, sdrc,pst,cdb=(0, 1, 2, or 3) STOP= CONTINUE=
S67OPT= MSGMESH= SCRATCH= TSOLVE= SMEAR PREMGLUE MRENUELE=
MRENUGRD= MRENUMBR= SYSabc= S6NEWS=

Examples:
SOL 600,106 STOP=1
SOL 600,106 OUTR=OP2,F06
SOL 600,106 PATH=/progs/marc2003/tools OUTR=op2,f06
SOL 600,129 PATH=1 STOP=1
SOL 600,129 PATH=1 OUTR=OP2,CDB=0
SOL 600,106 PATH=1 CONTINUE=1
SOL 600,106 PATH=1 MARCEXE=SOLVE OUTR=OP2
SOL 600,153 PATH=1 STOP=1 TSOLVE=M
SOL 600,106 OUTR=OP2,F06 SMEAR
SOL 600,106 OUTR=OP2 PERMGLUE
SOL 600,106 PATH=1 STOP=1 MRENUELE=2
SOL 600,106 PATH=1 STOP=1 MRENUGRDD=2
SOL 600,106 PATH=1 STOP=1 MRENUMBR=2
SOL 600,106 STOP=1 SYS001=8193 SYS9=6000
SOL 600,106 STOP=1 S6NEWS=YES
SOL 600,ID is an Executive Control statement similar to SOL. The difference between SOL and
SOL 600,ID is that the computations (element matrix formulations, matrix decomposition, etc.) will be
performed by Marc rather than by Nastran. Inputs and outputs as much as possible will be the same as
(or similar to) the familiar Nastran inputs and outputs, however standard Marc inputs and outputs are also
available. SOL 600 is primarily intended for nonlinear static and dynamic analysis of 3D structures that
have already been manufactured and assembled. Although it has capabilities for 2D structures and for
certain manufacturing processes, those capabilities should only be used for “simple” cases. For more
complex 2D and manufacturing analyses either a standalone version of Marc or SOL 400 is
recommended.
The SOL 600,ID statement should normally be used only for nonlinear analysis, but it may also be used
for certain classes of linear static or dynamic analyses. The recommended form of this command is
shown with the options provided above. If entered with “SOL 600,ID” only, it acts just like SOL except
a Marc input data file “jid.marc.dat” will be generated (“jid” is the name of the Nastran input file without
the extension.) For example, if the Nastran input file is named abcd.dat, (or abcd.bdf) then “jid”=abcd.
The required ID represents many valid solution sequence integer or names shown in Table 3-4 for the
SOL statement. Examples are 106, 129, NLSTATIC, NLTRAN. The following solutions are not
available: 107, 108, 110, 111, 112, 114, 115, 116, 118, 144, 145, 146, 190, 200, and 400 (and their

Main Index
 142 SOL 600,ID
Executes Marc from Inside Nastran

equivalent names). Solutions specified in Table 3-4 of the SOL statement may be used. If the model has
contact, ID must be 106, 129, 153, 159 or their equivalent names unless PERMGLUE is used.
Although SOL 600 supports 2D analyses (axisymmetric and plane strain), the support is not complete. It
is strongly recommended that 2D analyses use some other solution sequence.
Most items on the SOL 600,ID after ID itself may be specified in environmental variables. This may be
done any way environmental variables can be set. They may be set by the Nastran user at run time or by
the system administrator when Nastran is installed. Any values specified on the SOL statement override
those in the environment. Environmental variables are fully described in the MSC Nastran 2016
Installation and Operations Guide. 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 Nastran. Any string or value listed on the SOL 600,ID statement is also valid as an environmental
variable. If the environmental variables are placed in the system-wide rc file, they may be used by a
company for all Nastran users and even hide the fact that Marc is being spawned if so desired.
The following environmental variables are available:

Environmental Variable Item on SOL Statement

NASM_PATH PATH
NASM_COPYR COPYR
NASM_OUTR OUTR
NASM_STOP STOP
NASM_NOERROR NOERROR
NASM_STRFILE Path and name of marcfilt.txt file (see below)

PATH
PATH is an optional item which determines the location of the version of Marc to be executed. If PATH
is omitted, the version of Marc included with Nastran will be used if it can be located. In this case, the
run script for Marc (run_marc or run_marc.bat) will be expected to be in a directory under /MSC_BASE.
MSC_BASE is an environmental variable set when Nastran first starts execution that defines the base
installation directory for Nastran. If for some reason MSC_BASE cannot be determined, the commands
to spawn Marc will fail and the user must re-run Nastran with one of the PATH options set or the
NASM_PATH environmental option set to the desired location of Marc’s tools directory. If streaming
input is used, PATH should not be entered.

PATH=1
If PATH=1 is specified, Nastran will determine the proper command to execute the companion program.
To aid Nastran in determining the program’s location, a file named marcrun.pth must be available in the
same directory where the Nastran input file resides. The marcrun.pth file must contain one line providing
the location (complete path) of the run_marc script. A typical example of the line in the file marcrun.pth
would be

Main Index
 SOL 600,ID 143
Executes Marc from Inside Nastran

/mycomputer/marc200x/tools
To this path is appended the string “/run_marc -jid name.marc -v no” and possibly other items to form
the complete string used to execute Marc. This complete string looks like the string shown in the
following PATH=3 example. Note that on Windows systems, substitute a back slash for the forward
slashes shown. Do not terminate the line with a forward slash or back slash.

PATH=2
If PATH=2 is specified, it is expected that the directory with the run_marc script is on the PATH. If
PATH=2 is specified, Marc will be executed from inside Nastran using the command:
run_marc -jid jid.marc.dat -v no

PATH=3
When PATH=3 is specified, the complete command to execute Marc must be contained in a file named
marc.pth (lowercase). This file should typically contain one line of the form:
/mycomputer/marc200x/tools/run_marc -jid name.marc -v no

COPYR
COPYR is an optional item. If COPYR is specified, Marc output files will be copied to Nastran output
files and/or deleted according to the options shown in the following table:

Copy Marc Output Files to Nastran Delete Marc Input &

COPYR Option Output Files Output Files
0 (default) No No
1 or -1 (see below) Yes Yes
2 or -2 (see below) Yes No
3 No Yes

If COPYR is 1 or 2, Marc’s out and log files will be copied exactly as produced by Marc.
If COPYR is -1 or -2 the actions as shown above for +1 or +2 will occur, and Marc-type text will be
converted to Nastran-type text (or any other desired text) using an ASCII file named marcfilt.txt. This
file must be located in the same directory where the Nastran input resides or in the same directory where
the Marc executable resides. The marcfilt.txt file can contain as many lines as desired like the one shown
below:
"Marc string 1" "Replacement String 1"
"Marc string 2" "Replacement String 2"
That is, each line contains two strings. Each string starts and ends with a double quote sign ("). The Marc
string must match the exact content and case as found in the Marc .out or .log files. The replacement
string may be any string desired and can be the same length, shorter or longer than the Marc string. The

Main Index
 144 SOL 600,ID
Executes Marc from Inside Nastran

two strings must be separated by at least one space, but more spaces are acceptable. Line lengths for
marcfilt.txt, as well as Marc’s .out and .log files are limited to 200 characters for the text replacement
option.
The following Marc files are potentially affected by the COPYR option:

Marc Output File Nastran Output Copied to COPYR

name.marc.out name.f06 1, 2, -1, -2
name.marc.log name.log 1, 2, -1, -2
name.marc.t16 Not copied, will remain if produced
name.op2, fort.11 or ftn11 Not copied, will remain if produced

MARCEXE=SOLVE
MARCEXE=SOLVE is an optional item. If MARCEXE is entered, an existing input file named
jid.marc.dat is assumed to exist in the directory where the run was submitted. Nastran will execute Marc
using the existing jid.marc.dat file. A new Marc file will not be created. Other options available when
MARCEXE is used are PATH and OUTR. Options not available with MARCEXE are COPYR, STOP,
NOEXIT, NOERROR and CONTINUE. Beware that the original jid.marc.dat will be renamed to
jid.marc.dat.1 automatically by Nastran just like an existing jid.f06 is renamed to jid.f06.1

NOERROR
NOERROR is an optional item. If NOERROR is specified, errors due to features that are available in
Nastran but not available in Marc, and/or features not yet supported by the translator will be ignored (see
Restrictions and Limitations). If NOERROR is entered and STOP=2 (or 3) is not specified, Marc will be
executed even though the complete Nastran model may not have been completely translated. We
recommend that NOERROR only be used by experienced analysts and then only with extreme caution.

MSGMESH
MSGMESH is an optional item and should be omitted unless the Bulk Data contains some entries in the
MSGMESH format. If there are any MSGMESH entries present, set MSGMESH=Nhigh, where Nhigh
is an integer equal to the largest node, element, material or property in the model (after MSGMESH
entries have been expanded). Optionally this item can be set as an environmental variable
S600_M001=Nhigh. If MSGMESH entries are present and neither S600_M001 nor MSGMESH on the
SOL 600 statement are set, the job will terminate with an appropriate message.

NOEXIT
NOEXIT is an optional item. If entered, the DMAP generated “on the fly” to process the OUTR options
will not contain EXIT and Nastran will proceed. This means in most cases, the Nastran solution as well
as the Marc solution will occur. If .f06 is specified as one of the OUTR options, this could cause
confusing output as both the Marc and Nastran results will be in the .f06 file. Confusion could also result

Main Index
 SOL 600,ID 145
Executes Marc from Inside Nastran

from both outputs being in .op2, .xdb and/or .pch files. Therefore, this option should only be used with
great care.
Listing of the DMAP generated on the fly for SOL 600 can be suppressed by placing ECHOOFF just
after the SOL 600 entry.

Restrictions:
• OUTR options may not be used with restart jobs.
• OUTR options are not available for SOL 600 2D analysis such as axisymmetric or plane strain.
• OUTR options are not available for SOL 600 heat transfer.
• Spaces in the list of OUTR items are not allowed.

OUTR
OUTR is an optional item. If OUTR is specified, Marc output results will be converted to various types
of Nastran formats. The OUT option on the Nastran command should not be used with any OUTR
options. The type of output to be produced depends on the OUTR options entered as well as any DMAP
entered in the executive control. If OUTR is omitted, no Marc output will be brought back into Nastran,
but standard Marc .out, .t16 and/or .t19 as well as an op2 file will be available depending on the options
selected with PARAM,MARCT16, PARAM,MARCT19 and other options. OUTR options may not be
used with restart jobs.
The following options are available:

Option 1 -- Specify a String of Desired Output Types (Preferred Method)

OUTR=OP2,F11,F06,PCH,XDB,T16,T19,PST
Use any or all of the above to request the following options except that both OP2 and XDB should not
be entered:

OP2 Create output2 file named jid.op2 consisting of input model and output results
datablocks. This option requires PARAM,POST,-1 or PARAM,POST,-2 in the Bulk
Data.
F11 Create output file fort.11 or ftn11 (depending on the computer system) consisting of
output results datablocks only.
F06 Put Marc output results (displacements, stresses, strains) in Nastran’s jid.f06 file using
OFP. The resulting output will look just like any standard Nastran run.
PCH Create punch file named jid.pch with Marc’s output in standard Nastran punch format.
XDB Create .xdb database file named jid.xdb with input model and output results. This option
requires PARAM,POST,0 in the Bulk Data. XDB is not available with the eig option and
if entered will switch to the OP2 option.

Main Index
 146 SOL 600,ID
Executes Marc from Inside Nastran

eig The eig option must be specified if .op2, .xdb, .pch, or .f06 options are specified and
Marc performs natural frequency or buckling eigenvalue analysis. The reason it must be
provided on the SOL entry is to enable Nastran to create DMAP on the fly which include
the LAMA data block. If the eig option is omitted, eigenvectors will be present in the
Nastran output but no eigenvalues will be available. The beam and eig options are
mutually exclusive (you cannot specify both).
BEAM The BEAM option must be specified if .op2, .xdb, .pch, or .f06 options are specified and
you want to place internal loads in any of these files.The BEAM option is not available
for Windows systems.
SDRC An SDRC op2 file will be produced. PARAM,POST,-2 is also necessary in the Bulk
Data for this option. Note: The datablocks might be in a different order than for other
solution sequences.
T16 Marc’s results will be saved during the Marc execution on a binary (or unformatted) file
named jid.marc.t16 (this happens by default and does not need to be specified on the
SOL 600 line).
T19 Marc’s results will be saved during the Marc execution on an ASCII file named
jid.marc.t19. The t19 file will normally be saved if param,maract19,1 is entered.
PST Nastran will be run to output a previous Marc run’s results contained on t16 file in the
desired forms (OP2,F11,F06,PCH and/or XDB). The appropriate OUTR T16 options
must be selected in addition to PST (specify one or more of OP2,F11,F06,PCH and/or
XDB.) Nastran will not be run past IFP and is used only to perform the desired output
results conversions. A previous Marc t16 file must be copied to the new jid.marc.t16.1
(you may not process XDB and OP2 in the same run.)
DMAP The user will enter his own DMAP to create whatever type of output that is desired, such
as .op2, .xdb, .pch, or .f06. For all other options, DMAP as needed is generated internally
by Nastran.

Main Index
 SOL 600,ID 147
Executes Marc from Inside Nastran

cdb 3D Contact will be output in one of the datablocks described below:

0 Store output in OESNLBR and OESNLXR (OESNLXR will be empty like

SOL 106)
1 Store output in OESNLBR
2 Store output in OESNLBD
3 Store output in OESNLXD
Note: 1. SOL 106 outputs both OESNLBR and OESNLXR but OESNLXR is empty.
2. SOL 129 only outputs the OESNLXD datablock and it is empty.
3. Case Control BOUTPUT is also required to obtain this type of output.
4. The default is 0 if contact is present in the model and OUTR=op2 (or .xdb, punch
and/or .f06).
5. This option is specified like the example shown:
OUTR=OP2,F06,CDB=0
6. The datablocks have the same names and type of information whether executing
SOL 600,106 or SOL 600,129.

Option 2 -- Specify an Integer to Select Certain Options (Not Recommended)

OUTR=1 or 2 and an op2 file named fort.11 or ftn11 will be produced and DMAP as shown below is
required to bring the Marc output results back into the Nastran database.
COMPILE NLSTATIC
ALTER ‘SUPER1’ $
INPUTT2 /OUGV1,OES1,OSTR1,TOL,/-1/11 $
OFP OUGV1,OES1,OSTR1//0/1 $
EXIT $
The 1 at the end of the OFP statement produces output in the .f06 file. If a punch file is also needed,
change the 1 to a 5. If an XDB file is also needed, add the following lines just after the OFP line:
DBC TOL,CASECC,,,,,,,,,,,,,,,,,,//
'OL'/'CASECC'///////////////////
-1/DBCPATH/S,N,CP/''TRAN''//GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT $
DBC OUGV1,OES1,,,,,,,,,,,,,,,,,,//
'OUG'/'OES'///////////////////
-1/DBCPATH/S,N,CP/''TRAN''//GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT $
DBC OSTR1,,,,,,,,,,,,,,,,,,,//
'OES'////////////////////
-1/DBCPATH/S,N,CP/''TRAN''//GEOMU/LOADU/POSTU/
DBCDIAG/DBCCONV/DBCOVWRT $
OUTR can be set to one of the following values to automatically produce the output in Nastran form
without entering any DMAP. In fact, no DMAP should be entered for the options greater than 2 shown:

Main Index
 148 SOL 600,ID
Executes Marc from Inside Nastran

Table 3-5 Integer Options Available Using SOL 600 OUTR Option --
Nastran Output Results Produced When Marc Exits
fort.11 or
OP2 with
OUTR ftn11 Output .f06 .pch Marc File
Input .xdb
(IO) Datablocks (Print) (Punch) Used
Datablocks
Only
1 N Y N N N .t19
2 N Y N N N .t16
16 Y Y N N Y .t16
166 Y Y Y N Y .t16
266 Y Y N Y Y .t16
366 Y Y Y Y Y .t16
19 Y Y N N Y .t19
199 Y Y Y N Y .t19
299 Y Y N Y Y .t19
399 Y Y Y Y Y .t19

If OUTR = –1, -2, –16, -166, -266, -366, -19, -199, -299 or –399 only the output conversion process
takes place. An Marc input file is not produced, Marc is not spawned from Nastran, but .op2, .xdb, .pch
and/or .f06 results can be produced. For such cases, the Case Control and Bulk Data files can be dummies
(for example, they can contain several nodes and one element) or a full file could be used. These options
are handy if Marc is run by modifying the Marc input file (jid.marc.dat) with an editor or for someone
who creates Marc input and runs Marc outside the Nastran environment, but wants output in one of the
Nastran formats (see Remark 6.)

STOP
STOP is an optional item. STOP is used to prevent execution of Marc or exit Nastran after IFP, if so
desired. DO NOT ENTER any of the STOP options if any of the OUTR options are entered as the DMAP
generated automatically by Nastran will put an EXIT in the proper place. The various options are as
follows:

STOP=0
If STOP=0 Nastran will not be stopped after Marc exits. Nastran will attempt to obtain its own solution
to the problem if possible. Use of this option can lead to confusion because results from both Marc and
Nastran will be available. If the Marc results are placed in the .f06 file and if the Nastran results are also
available in the .f06 file, it will be difficult to tell which results came from Nastran and which results
came from Marc. This also applies to .op2 files and .xdb files. It is suggested the STOP=0 option be used
by extremely experienced SOL 600 users and even then with great care.

Main Index
 SOL 600,ID 149
Executes Marc from Inside Nastran

STOP=1
If STOP=1 Nastran will be gracefully stopped after IFP. This option is used to prevent Nastran from
performing its own solution (normally used when the solution is performed by the Marc). STOP=1
should be normally used if OUTR is not specified. STOP=1 is the default if no STOP, CONTINUE or
OUTR options are entered.

STOP=2
For STOP=2 Marc will not be executed. This option is used if you wish to examine the Marc input file
and make changes prior to running Marc. However, if STOP=2 is entered, the OUTR options will not be
available.

STOP=3
STOP=3 is a combination of STOP=1 and STOP=2. Nastran is stopped after IFP and Marc is not
executed. This would be the normal STOP option if you want to examine a Marc input file, then execute
Marc manually. The STOP=2 option is normally used if you want to obtain comparative results between
standard Nastran solutions and Marc solutions (in which case, all input options must be fully supported
by both programs). If STOP=3 is entered, the OUTR options will not be available.

CONTINUE=
CONTINUE= specifies an option as to how Nastran will continue its analysis after Marc finishes. For
this to happen, do not enter any STOP or OUTR options. It is not usually possible to perform more than
one of these operations if necessary.

0 Nastran will continue the current solution sequence as normal. For example if
SOL 600,106 is entered, SOL 106 will continue as normal after Marc finishes. Of
course, no 3D contact or materials not supported by SOL 106 may be used.
1 Nastran will switch to SOL 107 to compute complex eigenvalues. Marc will
generate DMIG matrices for friction stiffness (and possibly damping) on a file
specified by pram,marcfil1,name and time specified by param,marcstif,time. This
is accomplished by making a complete copy of the original Nastran input file and
spawning off a new job with the SOL entry changed and an include entry for the
DMIG file. The user must put CMETHOD and CEIG in the original Nastran input
file.
2 (Option not presently available.) Nastran will switch to SOL 107 to compute
complex eigenvalues. Marc will generate OUTPUT4 matrices for friction stiffness
(and possibly damping) on a file specified by pram,marcfil2,name and time
specified by param,marcstif,time. This is accomplished by making a complete copy
of the original Nastran input file and spawning off a new job with the SOL entry
changed and an include entry for the DMIG file.

The original Nastran file should include CMETHOD=id in the Case Control
command and a matching EIGC entry in the Bulk Data.

Main Index
 150 SOL 600,ID
Executes Marc from Inside Nastran

In addition, the DMIG entries specified by MDMIOUT will be included in a

separate Nastran execution spawned from the original execution. Case Control and
Bulk Data will be added to the original input to properly handle these matrices in
the spawned Nastran execution.
6 Same as option 1 except SOL 110 is run. For this option, the original Nastran input
file must contain METHOD=ID1 and CMETHOD=ID2 in the Case Control as well
as matching EIGRL (or EIGR) and EIGC entries in the Bulk Data.
7 Same as option 1 except SOL 103 is run for real eigenvalues/eigenvectors. The
database can be saved to restart into SOL 110 if desired. This should be done on the
command line or in a rc file with scratch=no. For this situation, the original Nastran
input file must include METHOD=id in the Case Control command and a matching
EIGRL or EIGR entry in the Bulk Data. (CMETHOD and EIGC can also be
included.) The actual restart from SOL 103 to 110 must be performed manually at
the present time.
101+ Continue options 101 to 400 are used to convert Marc’s initial contact tying
constraints to MPC’s and then continue in SOL 101 to 112 as a standard Nastran
execution. For example, if CONTINUE=101, a SOL 101 run with all the geometry
load cases, etc. from the original run would be conducted with the addition of the
initial contact MPC determined from Marc. The continue=101+ options are
frequency used to model dissimilar meshes as well as glued contact which does not
change throughout the analysis. This option can be used for any standard Nastran
sequence where the initial contact condition does not change. In order for initial
contact to work, the surfaces must be initially touching. If they are separated by a
gap, the MPC’s will be zero until the gap closes and thus the initial MPC’s are zero.
This option automatically sets BCPARA INITCON=1.

S67OPT=NO
If S67OPT=NO is entered the following action will be taken for SOL 600 or SOL 700: TA1MCK and
EMGPRO will not be disabled (when these routines are disabled, materials used only by SOL 600 or SOL
700 such as MATG, MATF, MATHP, etc. may be in the model and the t16op2 conversion will take place,
otherwise the job will fail with a FATAL ERROR). Also, Case Control FATAL error termination will
occur at the same place as other Nastran Solution Sequences. If S67OPT=YES or S67OPT is omitted
entirely, TA1MCK and EMGPRO will be disabled and Case Control FATAL ERRORS will cause job
termination immediately. S67OPT=YES is the default.

SCRATCH=
Determines what will happen when a SOL 600 job is initiated with SOL 600 database files (*.3dc, *.prp)
present in the run directory (this usually means another job is running and conflicts can occur.) The
default is SCRATCH=WAIT01. Options are as follows:

Main Index
 SOL 600,ID 151
Executes Marc from Inside Nastran

SCRATCH=DELETE Attempt to delete all *.3dc and *.prp files, continue with present job.
If the attempt to delete them fails, the job will terminate with an
appropriate message.
SCRATCH=ABORT If any *.3dc or *.prp files are found, abort the present job with an
appropriate message.
SCRATCH=WAIT If any *.3dc or *.prp files are found, wait until they disappear, then
begin current run. This option will wait an “indefinite” amount of
time.
SCRATCH=WAITxx If any *.3dc or *.prp files are found, wait for xx minutes or until they
disappear, then begin current job. If they do not disappear within xx
minutes, abort the current job with an appropriate message. Examples,
to wait up to 1 minute, enter SCRATCH=WAIT01, to wait up to 15
minutes, enter SCRATCH=WAIT15. Note: xx can range from 01 to
99.

SCRATCH= Remarks:
1. For the WAIT options, if no *.3dc or *.prp files are found, the job will start immediately.
2. No spaces are allowed.

TSOLVE
Determines which “solver” (Nastran or Marc) is used to solve a heat transfer analysis. The default is
Nastran.

TSOLVE=M Marc is used as the thermal solver.

TSOLVE=MS Marc is used as the thermal solver followed by a structural analysis using the
temperatures from the end of thermal analysis.
TSOLVE=N Nastran is used as the thermal solver (default).

TSOLVE Remarks:
1. If the default is used and thermal contact is present, SOL 600 spawns Marc to calculate initial
thermal contact variables which are then read by Nastran, turned into Nastran CELAS and other
variables. A second Nastran run is spawned for the primary Nastran run to complete the heat
transfer calculations.
2. If OUT or OUTDIR are used with thermal contact in SOL 600 they must both reference the same
directory.
3. This option should be entered for heat transfer analysis only.

Main Index
 152 SOL 600,ID
Executes Marc from Inside Nastran

SMEAR
The term SMEAR, as used by SOL 600, is different then that used on the PCOMP Bulk Data entry. For
SOL 600, SMEAR is the same as LAM=BLANK on the PCOMP entry. Other LAM options are not
available using SOL 600, however complete integration and fast integration methods are available, see
the PCOMPF Bulk Data entry.
If the string SMEAR is entered on the SOL 600,ID command line, composite shell entries using PCOMP
will use the smeared approach. If SMEAR is not entered, the through-the-thickness integration approach
will be used. The smeared approach is identical to other Nastran solution sequences where PCOMP
entries are converted to PSHEL and MAT2 entries. The through-the-thickness integration approach is
more accurate for post-buckling and nonlinear analyses but takes more computer time. OP2.f06 and
punch outputs are available and are controlled by the OUTR options OUTR=xxx where xxx is .op2, .f06
and/or .pch. If any OUTR options are specified, .op2 must be included. In addition, standard Case Control
requests are required.

SMEAR Option Restrictions

1. The SMEAR option may only be used if all composite materials in the model are made of shell
elements (if there are any composite solid elements, this option may not be used.)
2. Case Control requests for DISP(options)=ALL, the STRESS(options)=ALL must be entered.
STRAIN(options)=ALL is optional. (options) consist of any combination of (print,plot,punch)
3. The SMEAR output options may not be controlled using sets.
4. It is suggested that the Marc t16 file be limited to only those output “items” absolutely necessary
as composite output can be large and take significant computer time.
5. If OUT or OUTDIR are used with this option, they must reference the same directory.

PERMGLUE
Specify PERMGLUE if permanent glued contact is to be used. Permanent glued contact is glued contact
where the glued condition is determined using initial contact. This glued condition will remain
throughout the analysis. The MPC’s produced by the PERMGLUE option are identical to those formed
in SOL 101 or SOL 103 when the permanent glue option is specified. When this option is used, set
BCONTACT=ALLGLUP. For SOL 600, the PERMGLUE option is the only way contact can be used
with SOL600,101 or SOL 600,103 or other “linear” analyses.

MRENUELE
Determines if SOL 600 elements will be renumbered or not. (Default = 0)

0 No renumbering will occur (suggested for models with largest element number less than
approximately 20000)

Main Index
 SOL 600,ID 153
Executes Marc from Inside Nastran

1 All elements will be renumbered and the new numbers will be used in the Marc analysis. An
equivalence list will be output on file elenum.txt
2 All elements will be renumbered internally during translation, however the original element
numbers will be used in the Marc input file and Marc analysis.

Remarks concerning MRENUELE:

1. MRENUELE must be set on the SOL 600 entry if the maximum element number is greater than
9,999,999.
2. The “=” and an integer of “0” “1” or “2” must follow “MRENUELE” with no spaces when
MRENUELE is entered on the SOL 600 entry.
3. If the maximum element is 9,999,999 or smaller MRENUELE may be set as a parameter in the
bulk data or placed in a rc file.
4. MRENUELE should not be set on the SOL 600 and as a parameter.
5. For MRENUELE=1 an equivalence list of original and re-numbered element numbers is output
on file elenum.txt

MRENUGRD
Determines if SOL 600 grid ID’s will be renumbered or not. (Default = 0)

0 No renumbering will occur (suggested for models with largest grid ID less than approximately
20000)
1 All grid ID’s will be renumbered and the new numbers will be used in the Marc analysis. An
equivalence list will be output on file grdid.txt
2 All grid ID’s will be renumbered internally during translation, however the original element
numbers will be used in the Marc input file and Marc analysis.

Remarks concerning MREUGRD:

1. MRENUGRD must be set on the SOL 600 entry if the maximum element number is greater than
9,999,999.
2. The “=” and an integer of “0” “1” or “2” must follow “MRENUELE” with no spaces when
MRENUGRD is entered on the SOL 600 entry.
3. If the maximum grid ID is 9,999,999 or smaller MRENUGRD may be set as a parameter in the
bulk data or placed in a rc file.
4. MRENUGRD should not be set on the SOL 600 and as a parameter.
5. For MRENUGRD=1 an equivalence list of original and re-numbered grid id’s is output on file
gridnum.txt

Main Index
 154 SOL 600,ID
Executes Marc from Inside Nastran

MRENUMBR
Determines both grid and element ID’s for SOL 600 will be renumbered or not. (Default = 0)

0 No renumbering will occur (suggested for models with largest grid ID less than
approximately 20000)
1 All grid and element ID’s will be renumbered and the new numbers will be used in the Marc
analysis. An equivalence list will be output on file grdid.txt
2 All grid and element ID’s will be renumbered internally during translation, however the
original element numbers will be used in the Marc input file and Marc analysis.

Remark concerning MREUMBR: All remarks for MRENUELE and MRENUGRD apply.

S6news
S6news can be set to YES or NO. If set to YES, a list of new features currently considered to be in beta
tests are output complete with the Case Control and/or Bulk Data descriptions anticipated once these
features are released.

SYSabc
Allows Nastran system cells to be set on the SOL 600 Executive Control statement if desired. Abc must
be an integer ranging from1 to 500 and be a valid system number. INTT must be an integer with 1-8
digits. More than one SYSabc=INTT statement may be made if so desired, however abc may not be
repeated. Note that the limit on the integer following the equal sign is 8 digits.

Running SOL 600 in Steps -- Modification of the SOL 600 Statement Using
Environmental Variables:
It is possible to run the main portions of SOL 600 in single steps without changing the Nastran input file.
This is accomplished using one of the two environmental variables discussed below. A user can set these
variables in a script that runs Nastran, from the command line or for Windows using the control panel.
Note that on Linux systems, the name of the environmental variable must be in upper case. The string to
which it is set can be in upper or lower case and will be converted to upper case.

To Run SOL 600 in Three Steps Without Changing the SOL 600 Statement in the Input
File:
First, make sure that your SOL 600 input file has a SOL 600 statement that contains all of the features
you would want if all steps were done in a single run. For example, if you wish to make an op2 file and
place the results in the .f06 file, a typical SOL 600 statement would be as follows:
SOL 600,NLSTATIC PATH=1 OUTR=OP2,F06
or
SOL 600,NLSTATIC OUTR=OP2,F06

Main Index
 SOL 600,ID 155
Executes Marc from Inside Nastran

(if the default path to Marc is to be used).

It is important to have the OUTR options specified at the end of the SOL 600 statement. The following
environmental variable can be set as shown to run the three steps (a LINUX shell example is shown):
1. export MARC_RUN=“stop”
This will tell Nastran to run the internal Nastran-to-Marc translator only. The first SOL 600
statement shown would be changed internally just for this run above to the following:
SOL 600,NLSTATIC PATH=1 OUTR=OP2,F06 STOP=3
This change will be shown in the .f06 file.
2. export MARC_RUN=“solv”
This will tell Nastran to run Marc from inside Nastran. The first SOL 600 statement shown
would be changed internally just for this run above to the following:
SOL 600,NLSTATIC PATH=1 OUTR=OP2,F06 MARCEXE=SOLVE
For this run, it is assumed that a file named jid.marc.dat resides in the input file directory created
from a previous translator-only run. The Nastran script will automatically rename jid.marc.dat
to jid.marc.dat.1, but the Nastran executive processing will name it back to jid.marc.dat
3. export MARC_RUN=“pst” This will tell Nastran to run the t16 to op2 translator inside Nastran.
The first SOL 600 statement shown would be changed internally just for this run above to the
following:
SOL 600,NLSTATIC PATH=1 OUTR=OP2,F06,PST
For this run, it is assumed that a file named jid.marc.t16 as well as the original Nastran input file jid.dat
resides in the input file. The “t16” file should have been created from a previous Marc execution using
the same computer system (cross-platform support is not available for this step). The Nastran script will
automatically rename jid.marc.t16 to jid.marc.t16.1, and the Nastran t16op2 conversion routines will
look for files with names jid.marc.t16, jid.marc.t16.1, jid.marc.t16.2 up to jid.marc.t16.5 in that order. If
no such files are found, the t16op2 job will exit with a message.

Method to Completely Modify the SOL 600 Statement:

For maximum versatility without having to modify the Nastran input file, the SOL 600 statement can be
modified completely using the environmental variable SOL600_CMD. Assuming that the original
SOL 600 statement in jid.dat contains the string:
SOL 600,NLSTATIC OUTR=OP2,F06
and the environmental variable is set as follows:
export SOL600_CMD=“SOL 600,NLSTATIC PATH=1 MARCEXE=SOLVE”
the new SOL command line internal to Nastran will be
SOL 600,NLSTATIC PATH=1 MARCEXE=SOLVE
and Nastran will stop after creating the Marc input file. This would be the same as if the following SOL
600 statement was entered:

Main Index
 156 SOL 600,ID
Executes Marc from Inside Nastran

SOL 600,NLSTATIC PATH=1 STOP=3

Any valid SOL 600 statement can be issued using the SOL600_CMD environmental variable without
changing the original Nastran input file at all.

Remarks:
1. Only one SOL 600,ID job may be run in a directory at any given time. However, if a previous
run was made and output files such as name.marc.t16 were produced, they will be renamed
name.marc.t16.1, etc. following the Nastran re-naming convention.
2. If OUTR is specified, STOP must not be specified.
3. The COPYR option can be used to delete all files directly created by Marc if the output desired
are Nastran files only.
4. When OUTR is specified, the Marc files such as jid.marc.out, jid.marc.t16 will be renamed to
jid.marc.out.1 and jid.marc.t16.1 at the start of the run. This renaming is accounted for when
opening the files
5. To generate .xdb files, PARAM,POST,0 must be included in the Bulk Data Section. To generate
OP2 files with geometry, PARAM,POST,-1 (for Patran and Femap) or PARAM,POST,-2 (for
SDRC) should be included in the Bulk Data.
6. Although SOL 600,ID supports linear analysis (ID=101, 103, 105), not all features are available.
For example, Case Control commands, STATSUB, SUBCOM, SUBSEQ, SYMCOM,
AUXMODEL, AXISYMMETRIC, CLOAD, DEFORM, HARMONICS, MFLUID, NSM, and
REPCASE are not available. For nonlinear analyses (ID=106, 129) Case Control commands,
NNLOAD and NONLINEAR are not available.
7. To output displacements in the jid.marc.out file, do the following:
In the Case Control, set DISP(PRINT)=ALL or DISP(PRINT,PLOT)=ALL
In the Bulk Data, include the following two parameters:
PARAM,MARCPRNR,1
PARAM,MARCND99,-1

8. All SOL 600 character variable parameters, such as MRAFFLOW, must be left justified in the
starting in field 3.
9. If generation options such as EGRID, GRIDG, CGEN, etc., are used, the MSGMESH option or
the environmental variable, S600_M001 must be set with a value equal to the largest grid ID or
element ID (whichever is larger). This is needed for initial SOL 600 memory sizing, which
happens before these generation entries are converted to standard Nastran GRID, CQUAD4, etc.
entries. SOL 600 can not read the generation features. This environmental variable needs to be
included in the script or batch file that runs SOL 600 jobs (for Windows, it can be set in the
environment).
10. Fixed load stepping (or time stepping) is controlled primarily by PARAM,MARCITER and
PARAM,MARCAUTO rather than NLPARM or NLAUTO.
11. 2D and 3D contact and elements may not be mixed in the same model.

Main Index
 SOL 600,ID 157
Executes Marc from Inside Nastran

12. For the OUTR options, the only stress tensor available is Cauchy stress (E341). If some other
stress tensor is selected using MARCOUT, and E341 is not selected, no stresses will be available
in the .op2, .xdb, .pch, or .f06 files.
13. For multi-layer composites, stresses in the preferred direction (E391), also known as the layer
direction, are usually necessary. The default Cauchy stresses (E341) will be automatically
charged to E391 for composites.
14. SOL 600 supports a new field on RFORCE (2nd line 4th field) to allow different portions of the
structure to have different rotation accelerations.
15. 2D Plain stress is available and this type of analysis is achieved by setting MID=-1 on all PSHELL
entries and adding the following parameters to the bulk data.
PARAM,MRALIAS,011003
PARAM,MALIAS02,006003

SOL 600 will use the alias commands to convert plain strain elements that normally are
introduced with MID2=-1 into the input into plain stress. Although MALIAS02 specifies that
Marc element 3 be used for CTRIAi, the new Marc element 201 plain stress triangle will be used
instead of a degenerate element 6 plain stress quad. By default, the CTRIAi node numbers will
not be reversed, however if the user wants to reverse them enter PARAM,MREVPLST,1 in the
bulk data. Any contact entered into the file needs to specify 2D on all BCBODY entries. 2D plain
stress analysis for SOL 600 is available through Patran which will generate the above alias
parameters automatically.

Restrictions and Limitations of SOL 600

Certain features are available in Nastran that are not available in Marc, and vice versa, the following
restrictions/limitations are imposed on Nastran. Those restrictions indicated by (*) will be removed as
soon as possible. Items with (**) will issue a FATAL error (for the Nastran-to-Marc translator internal to
Nastran) and Marc will not be “spawned” from Nastran unless NOERROR is entered on the SOL 600
statement.
• External superelements are supported. Other types of superelements are not currently supported.
• Scalar points are not supported.
• PBCOMP is not supported.
• CCONEAX is not supported.
• CBARAO is not supported.
• Output set definitions that contain grid or element numbers greater than the largest grid or
element in the model will produce errors in Marc.
• Output set definitions may include the word BY as in output plot set definitions for use by Marc
only. Nastran must be stopped using STOP=1 or one of the OUTR options since BY is a FATAL
ERROR to Nastran.
• Nastran’s CREEP entry must be changed to the MATVP entry.
• For orthotropic materials using MATORT, all shear moduli must be entered.
• SPOINTs are mapped to GRIDs with x, y, z coordinates at (0., 0., 0.)

Main Index
 158 SOL 600,ID
Executes Marc from Inside Nastran

• SLOAD and other scalar features are not supported.

• CELAS3 and CELAS4 are not supported.
• CLOAD is not supported.
• Fracture Mechanics is available.
• Aerodynamics is not supported.
• Bulk data entries with + or * in column 73 must have an actual continuation card for most
entries. Nastran does not require this, but the internal Marc translator does. (*).
• Slideline contact is not supported (BLSEG, BWIDTH, BFRIC, BCONP, and BOUTPUT, if
entered will cause FATAL ERRORS in Nastran).
• p-elements are not supported.
• Offsets are available for CBAR, CBEAM, CQUAD4 and CTRIA3 in all types of structural
analysis (linear or nonlinear). The offsets must be specified in the global coordinate system
(displacement output coordinate system) unless PARAM,MAROFSET is 1 (2 or 3, see
description in Parameter Descriptions, 708). Offsets are available for CQUAD8 and CTRIA6 but
only if all 8 or 6 grids are defined for these elements, respectively. If PARAM,MAROFSET,1 (2
or3) is included in the bulk data, the offsets will be incorporated using a new Marc feature that
does not need extra grids or elements.
• For SOL 600, it is required that a Case Control LOAD or DLOAD entry be made for each
subcase. If there are no subcases, one LOAD or DLOAD entry must be made.
• For SOL 600, it is required that all enforced displacements (other than motion of rigid contact
surfaces applied using fields on the BCBODY entry) be applied using SPCD rather than SPC.
The ID’s of the SPCD must correlate with the Case Control LOAD or DLOAD entries.
• MPCs must be the same for all load cases.
• MAT10 is not presently supported.
• The following Solution Sequences are not presently supported: 107, 108, 110, 111, 114-116, 118,
144-146, 190, 200, 400 and 700 and will cause Severe Warnings (FATAL ERRORS) in the
internal translator.
• DOMAINSOLVER is not supported. If this Executive Control statement is entered, and Nastran
Implicit Nonlinear is requested by the SOL 600, ID statement, the DOMAINSOLVER request
will be commented out internally by Nastran.
• IDs Grids, elements, properties, materials, etc. are limited to 9,999,999 unless one of the
MRENUxxx items is specified in which case the limit is 10 digits.
• CGAP does not completely map to Marc’s gap element. The user should change all Nastran gaps
to contact before running SOL 600. If the gaps are not changed to contact, some options will fail
to translate as indicated by warning messages. Certain simple gaps translate as expected and will
produce nearly the same results as standard Nastran solution sequences, but the user is
responsible for ensuring that any model with gaps gives the behavior he expects when using
SOL 600.
• Nastran MATS1 Mohr-Coulomb is mapped to Marc’s Linear Mohr Coulomb option.

Main Index
 SOL 600,ID 159
Executes Marc from Inside Nastran

• Nastran MATS1 Drucker-Prager is mapped to Marc’s Parabolic Mohr Coulomb option.

• Solid element composite output is not presently available using the OUTR options, It must be
postprocessed directly using the t16 file - Patran is recommended.
• If layered output for Composite Structures is desired, the following bulk data parameters or bulk
data entry, MARCOUT with LAYCODE of 1 or 2 should be included in the Bulk Data. If output
for all layers is desired, set LAYCODE to zero and enter the following parameters:
param,mroutlay,N
param,marcslht,N
where N is the maximum number of layers in any composite PCOMP description. The preferred
option is MARCOUT with LAYCODE=1.
• The rotational acceleration portion of RFORCE (RACC) is not supported and if entered will
generate a Severe Warning and Marc will not be spawned.
• The following Case Control option for displacement/velocity/acceleration/spcforce/ mpcforce
are not supported and will be ignored if entered:
• SORT2, REAL, IMAG, PHASE, PSDF, ATOC, CRMS, RALL, RPRINT, RPUNCH,
NORPRINT, CID, TM, RM
• Elements with mid-side nodes must have all mid-side nodes. For example CTETRA must either
have 4 or 10 nodes.
• For PC systems, if SOL 600 is run from a command prompt (DOS box), if any old DOS
programs are used prior to running SOL 600 the path where the job is being run is usually
adjusted such that any names longer than 8 characters will be shortened (for example brake-
squeal becomes BRAKE-~3). The continue options including brake squeal jobs will not work
when this happens. Open a new command prompt and run SOL 600 before any old DOS
programs are run in that window.
• The CID field on the RFORCE entry is not completely supported. If entered with a positive
integer, the job will abort with a Severe Warning unless PARAM,MARCRCID is entered.
PARAM,MARCRCID,1 may be used to ignore this field in which case R1,R2,R3 define the
direction cosines of the rotation vector (see Marc Volume C, ROTATION A description) and the
magnitude is given by A*sqrt(R1**2+R2**2+R3**2) [see RFORCE description for definitions
of CID, A, R1, R2, R3 as well as Remark 16].
• Filenames entered on SOL 600 Bulk Data entries must be entered in small field fixed format,
must be left-justified in the first applicable field and must be entered in lower case unless
otherwise noted.
• For any jobs using the CONTINUE option or brake squeal, the jid must be entirely in lower case
for Linux systems.
• Ixy of PBAR/PBEAM is ignored, if entered, for SOL 600.
• PARAM,MRDISCMB=1 must be used for models with multiple subcases with the same
pressure loadings in each subcase. The program will automatically attempt to reset the default
(mrdiscmb=0 to mrdiscmb=1 in such circumstances, however, it is recommended that the user
does this himself.

Main Index
 160 SOL 600,ID
Executes Marc from Inside Nastran

• Some Bulk Data input entries are not checked as completely for SOL 600 as they are for other
solution sequences, particularly those that apply only to SOL 600. In addition, certain checks for
all types of entries, even those that can be used in other solution sequences may be made after
Marc is spawned or the error messages not output until after Marc is spawned. For those cases,
the error message, if any, will not be visible until Marc has finished and may not even be output
unless one or more of the OUTR options is selected. Users should take special care that the
SOL 600 input is free from errors and that no duplicates occur prior to running SOL 600. One
way to do this which is highly recommended is to run a preliminary SOL 101 job with as much
of the same input file as possible.
• For SOL 600, it is required that all enforced displacements (other than motion of rigid contact
surfaces described by fields in BCBODY entries) be applied using SPCD rather than SPC. The
ID’s of the SPCD must correlate with the Case Control LOAD or DLOAD entries.
• If an .op2, .xdb, .f06, and/or punch file is requested using the OUTR option, static analyses must
have “times” ranging from 0.0-1.0 for the first subcase, 1.0-2.0 for the second subcase, etc. If
NLAUTO is used to change these times, the job will fail with an appropriate message. This
means that if NLAUTO is used TFINAL (field 4) must always be 1.0.
• Concentrated masses are not considered in gravity loading for linear or nonlinear static analyses.
• Non-structural mass is ignored by SOL 600.

Main Index
 SOL 700,ID 161
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)= MEM(or MEM700)= DBL(or DBL700)= FSIDMP=
HPMPI= INTELMPI= EID= YES BLADEOUT

Examples:
SOL 700,129 PATH=3 NP=4
SOL 700,129 NP=2 MEM=500 DBL=YES
SOL 700,129 MEM=250
(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. This client-server approach is
similar to SOL 600, using Marc.
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.

Executive Control Parameters:

The required ID may be one of several valid solution sequence integers or names shown in Table 3-4 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 MSC
Nastran 2016 Installation and Operations Guide . A keywords file is available to describe the format of

Main Index
 162 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)

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-lsdyna 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-lsdyna jid=name.dytr.dat O=name.dytr,d3hsp G=name.dytr.d3plot D=name.dytr.d3dump
F=name.dytr.d3thdt A=name.dytr.runrsf B=name.dytr.d3drfl
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-lsdyna i=enf2e.dytr.dat O=enf2e.dytr.d3hsp G=enf2e.dytr.d3plot D=enf2e.dytr.d3dump
F=enf2e.dytr.d3thdt A=enf2e.dytr.runrsf B=enf2e.dytr.d3drfl

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 script or batch files is run_dytran (or run_dytran.bat). 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.

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-lsdyna for Linux and dytran-lsdyna.exe for windows
will be appended. If exe= is used, it must be the second line in the sol700.pth file.

Main Index
 SOL 700,ID 163
Executes MSC Nastran Explicit Nonlinear (SOL 700)

nproc Number of processors.

(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-lsdyna executable resides must also be shared for parallel execution.
bat Run in background or foreground (Default).
memory Amount of memory. Example: memory=200m (200 mega words/ 800 megabytes). If
mem(or MEM700)= is placed directly on the command line (not in sol700,pth) the value
entered may not have “m” or any other letter(s) at the end. “m” will automatically be
appended.
wdir Working directory. For parallel execution, this directory must be shared with read/write
privileges. Default is directory where MSC Nastran input resides.
copy Yes or no. Input and output files are copied from wdir to the input directory. Default is yes.
machine Machines and number of processors to use in the form:
machine1#2+marchin2#4 (use 2 processors on machine 1 and 4 processors on machine 2)
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
hpmpi To activate the HP MPI set hpmpi equal to yes. Default is no. If HPMPI=YES is placed
directly on the command line (not in sol700.pth) HP MPI will be activated too.
intelmpi To activate the INTEL MPI set intelmpi equal to yes. Default is no. This option is only
available on Windows 64. If INTELMPI=YES is placed directly on the command line (not
in sol700.pth) INTEL MPI will be activated too.
scale scale factor for binary file (d3plot, binout, etc) sizes. (default=70) The default size is around
1GB. Example: scale=70

A Windows example of the file sol700.pth for the PATH=3 case follows.
e:\sol700\dytran-lsdyna\run_Dytran
nproc=4
memory=20m
wdir=f:\temp
machine=cp01#2+cp02#2
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.)
e:\sol700\dytran-lsdyna\run_dytran jid=abcd.dytr nproc=4 memory=20m
widr=f:\temp delete=yes marchine=pc01#2+pc02#2

Main Index
 164 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Available PATH=3 options for Linux systems follows:

copy Yes or no. Input and output files are copied from wdir to the input directory. Default is
yes.
dbl Specifying dbl=yes indicates to run the double precision version (R8I8). This is
required for prestress and thermal calculations and is recommended for Time Domain
NVH problems. Default is no.
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.
eid ARCid,NCYCLE,MESHID: ARCid is the filename of archive result file of a previous
Euler calculation. NCYCLE is the cycle number in the ARC file which will be used for
the follow-up simulation. MESHID is the mesh ID of the Euler mesh that is initialized.
If EID= is placed directly on the command line (not in sol700,pth) it will work as the
same as eid in sol700.pth. If only one cycle is stored in the ARCid file, NCYCLE may
remain blank. eid can be repeated up to 10 times on the command line. If more than one
eid is used, MESHID is required to indicate which ARCid is initializing which Euler
mesh. If only one eid is used, MESHID may remain blank.
Examples:
eid=BLAST_EULER_539.ARC
or
eid=LEFT_EULER_80.ARC,,1
eid=RIGHT_EULER_80.ARC,,2
exe The full path to the executable for dytran-lsdyna 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.
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).
hpmpi To activate the HP MPI set hpmpi equal to yes. Default is no. This option is only
available on Linux IA32, Linux Itanium2 and Linux X8664. If HPMPI=YES is placed
directly on the command line (not in sol700.pth) HP MPI will be activated too.
memory Amount of memory; example: memory=200m (200 mega words/800 megabytes). If
MEM(or MEM700)= is placed directly on the command line (not in sol700,pth) the
value entered may not have "m" or any other letter(s) at the end. "m" will automatically
be appended.
mpipath The MPI install directory if you wish to used a non-default MPI directory.
mpirun The MPI run command you want to use. If entered, it overrides the default MPI run
command on your machine as well as the command in mpipath.

Main Index
 SOL 700,ID 165
Executes MSC Nastran Explicit Nonlinear (SOL 700)

nproc Number of processors. (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.
wdir Working directory. Default is directory where MSC Nastran input resides.
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.
scale scale factor for binary file (d3plot, binout, etc) sizes. (default=70) The default size is
around 1GB. Example: scale=70

A Linux example of the file sol700.pth for the PATH=3 case is as follows:
/APP/sol700/run_dytran
memory=800m
nproc=8
For the above example, MSC Nastran will create the a command similar to the following to spawn
dytranlsdyna assuming your input file is named abcd.dat
/APP/sol700/run_dytran \
jid=abcd.dytr.dat memory=800m nproc=8
If PATH is not specified, the default search path will be used to locate the dytran-lsdyna executable. This
version will be located in a subdirectory named dyna/machine below the MSC Nastran base directory
(MSC_BASE). Not all PATH3 options are available using this default path option.

STOP
STOP is an optional item. STOP is used to prevent execution of dytran-lsdyna 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-lsdyna 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-lsdyna 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

Main Index
 166 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)

properly installed on all computers involved and a hostfile designating which computers are to be used
for each domain 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.

DBL=Double Precision
If DBL(or DBL700)=YES is specified, the double precision version will be used instead of the standard
simple precision version. The double precision version is slower but is needed for long runs and in certain
other applications, such as time domain or prestress calculations.

BLADEOUT
Enter the string BLADEOUT if it is desired that the forces produced by the broken blade, rubbing forces
due to the non-broken blades, etc. be saved on the Nastran MASTER database (see the BLDOUT Bulk
Data entry). When this string is entered, DMAP is generated on the fly to create and save this datablock.
To output the blade forces saved in the database from the SOL 700 portion of a bladeout run using
TABPT, enter BLADEPRT instead of BLADEOUT on the SOL 700 entry.

Item Case Control Commands Available in SOL 700

$ Y
ACCELERATION Y
BCONTACT Y
BEGIN BULK Y (Other BEGIN forms are not allowed)
DISPLACEMENT Y
DLOAD Y
ECHO Y
ELFORCE see FORCE Y
ENDTIME Y (new)
ENDSTEP
FORCE & ELFORCE Y (automatically produced in d3plot files no user control)
GROUNDCHECK Y (MSC Nastran .f06 only)
IC Y
INCLUDE Y
LABEL Y (MSC Nastran .f06 only)
LINE Y (MSC Nastran .f06 only)
LOAD Y (for dynamic pseudo-statics only)
LOADSET Y
MAXLINES Y (MSC Nastran .f06 only)

Main Index
 SOL 700,ID 167
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Item Case Control Commands Available in SOL 700

MPC Y
NLPARM Y (Psuedo static analysis only)
NLSTRESS Y (Changed to STRESS)
PAGE Y (In MSC Nastran only)
PARAM Y (Only applicable params are used)
PRESSURE Y
SET Y
SET – OUTPUT(PLOT) N
SKIP Y (Required if multiple subcases are present)
SPC Y
STRAIN Y
STRESS Y
SUBCASE Y (See note)
Note: Only one subcase can be selected for a particular SOL 700 analysis. Many subcases may
be entered in the input file, but the one to be used must be selected using the SKIP ON
and SKIP OFF Case Control commands. If the SKIP ON/OFF commands are not found
or are in the wrong place, the first subcase encountered will be used and the others
ignored.
SUBTITLE Y
TITLE Y
TSTEP Y (Same as TSTEPNL)
TSTEPNL Y
VELOCITY Y
WEIGHTCHECK Y (In MSC Nastran only)

The following summarizes the Bulk Data entries for SOL 700:

Item Bulk Data Entries Available in SOL 700 Fatal Error

AXIC N Y
AXIF N Y
AXSLOT N Y
BAROR Y
BCBODY Y
BCHANGE N Y

Main Index
 168 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Item Bulk Data Entries Available in SOL 700 Fatal Error

BSURF Y
BCBOX Y
BCGRID
BCPROP Y
BCMATL Y
BCONP N
BCSEG Y
BCTABLE Y
CBAR Y
CBEAM Y
CBEND N Y
CBUSH N Y
CCONEAX N Y
CDAMP1D Y (New)
CDAMP2D Y (New)
CELAS1D Y (New)
CELAS2D Y (New)
CFLUID N Y
CGAP N Y
CHACAB N Y
CHEXA Y (8 Nodes only)
CONM2 Y
CONROD Y
CORD1C Y
CORD1R Y
CORD1S Y
CORD2C Y
CORD2R Y
CORD2S Y
CORD3G N Y
CPENTA Y (5 Nodes only)
CQUAD4 Y
CQUAD8 Y (4 Nodes only)

Main Index
 SOL 700,ID 169
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Item Bulk Data Entries Available in SOL 700 Fatal Error

CQUADR Y
CQUADX N Y
CREEP N Y
CROD Y
CSHEAR N Y
CTETRA Y (4 Audio Nodes only)
CTRIA3 Y
CTRIA6 Y (3 Nodes only)
CTRIA3R Y
CTRIAX N Y
CTRIAX6 N Y
CTUBE Y
CVISC Y
CWELD N Y
CSPOT Y
CFILLET Y
CBUTT Y
CCRSFIL Y
COMBWLD Y
DAMPGBL Y (New for Dynamic Relaxation)
DAREA Y
DEFORM N Y
DELAY N Y
DMI N Y
DMIAX N Y
DMIG N Y
DPHASE N Y
DTI N Y
ECHOOFF Y
ECHOON Y
ENDDATA Y
EOSPOL Y
FORCE Y

Main Index
 170 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Item Bulk Data Entries Available in SOL 700 Fatal Error

FORCE1 N Y
FORCE2 Y
FORCEAX N Y
GENEL N Y
GRAV Y
GRDSET Y
GRID Y
INCLUDE Y
IPSTRN N Y
ISTRESS N Y
LOAD Y
LSEQ Y
MAT1 Y
MAT2 Y
MAT3 Y
MAT8 Y
MATDxxx Y
MATD20M Y (New Rigid Material Merge)
MATEP N Y
MATHE N Y
MATHED N Y
MATF N Y
MATHP Y
MATS1 Y
MATVE N Y
MATORT N Y
MATVP N Y
MATG N Y
MFLUID N Y
MOMAX N Y
MPC Y
MPCAX N Y
NLPARM Y (For pseudo statics)

Main Index
 SOL 700,ID 171
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Item Bulk Data Entries Available in SOL 700 Fatal Error

NLRGAP N Y
NOLINi N Y
NTHICK N Y
PANEL N Y
PBAR Y Y
PBARL Y
PBCOMP N Y
PBEAM Y
PBEAML Y
PBEND N Y
PBUSH N Y
PCOMP Y
PDAMP Y
PDAMP5 N Y
PELAS Y
PELAST N Y
PGAP N Y
PHBDY N Y
PINTC N Y
PINTS N Y
PLOAD Y
PLOAD1 N Y
PLOAD2 Y
PLOAD4 Y (Continuation supported)
PLOADX1 N Y
PLPLANE Y
PLSOLID Y
PMASS N Y
PRESPT N Y
PROD Y
PSHEAR N
PSHELL Y
PSOLID Y

Main Index
 172 SOL 700,ID
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Item Bulk Data Entries Available in SOL 700 Fatal Error

PTUBE Y
PVISC Y
RBAR Y
RBE1 N Y
RBE2 Y
RBE3 Y (Changed to RBE3D)
RESTART Y
RFORCE (CID, METHOD, continuation line not supported)
RLOADi N Y
RROD N Y
RSPLINE N Y
RTRPLT N Y
SLOAD N Y
SPC Y
SPC1 Y
SPCADD Y
SPCAX N Y
SPCD Y
SUPAX N Y
TABLED1 Y
TABLED2 Y
TABLED3 Y
TABLES1 Y
TEMP N Y
TEMPD N Y
TIC Y
TICD Y (New with increment options)
TIC3 Y (New Dytran type entry)
TLOAD1 Y
TLOAD2 N
TSTEP Y (Changed to TSTEPNL)
TSTEPNL Y
WALL Y (New rigid wall entry)

Main Index
 SOL 700,ID 173
Executes MSC Nastran Explicit Nonlinear (SOL 700)

Notes and Restrictions:

The following Case Control stress/strain/load options are not supported and will be ignored if entered:
• SORT2, REAL, IMAG, PHASE, MAXS, SHEAR, STRCUR, FIBER, CENTER, CORNER,
BILIN, SGAGE, CUBIC, PSDF, ATOC, CRMS, RALL, RPRINT, RPUNCH, NORPRINT
The following Case Control displacement/velocity/acceleration/spcforce/mpcforce options are not
supported and will be ignored if entered:
• SORT2, REAL, IMAG, PHASE, PSDF, ATOC, CRMS, RALL, RPRINT, RPUNCH,
NORPRINT, CID, TM, RM
The ANALYSIS= Case Control command is not supported, and if entered, will cause the job to terminate
with an appropriate message.

Main Index
 174 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 

 GRID  
  
SORT =  VALUE   )
  
 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:
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

Main Index
 SPARSESOLVER 175
Sparse Solver Options

• 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, and NONE. The default automatically selects among METIS,
MMD and BEND
fmeth Factorization method to be used (MSCLDL).
The choices for factorization method are: MSCLDL, MSCLU, UMFLU,
NUMFLU and PRDLDL. The default factorization method for symmetic
matrices is MSCLDL. For unsymmetric matrices, the default is MSCLU.
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.
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).

Main Index
 176 SPARSESOLVER
Sparse Solver Options

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

CEAD Yes Yes No Yes No
DCMP Yes Yes No No No
DECOMP Yes Yes Yes Yes No
FRRD1 Yes Yes Yes No No
MDSTAT Yes Yes No No No
NLSOLV Yes Yes No No Yes
READ Yes No No No No
SOLVE Yes Yes Yes Yes No
TRD1 Yes Yes Yes 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).
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 choices for ordering method are: AMF, BEND, MD, METIS, MMD, PRDMD, PRDMETIS,
PRDSMPMS, and NONE. The default automatically selects among METIS, MMD and BEND.
8. The UMFLU factorization method ignores COMPMETH and ORDMETH since it contains its
own compression/reordering method.
9. 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.
10. 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.
11. 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.

Main Index
 SPARSESOLVER 177
Sparse Solver Options

12. 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, m CHARTR=5 produces different outputs compared to CHARTR=15, CHART.
13. 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.
14. 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.
15. Notes on PRDLDL:
a. ORDMETH must be one of PRDMD, PRDMETIS, or PRDSMPMS.
b. COMPMETH option is ignored.
c. The maximum number of threads used is given by DMP*PARALLEL, and PARDISO solver
will choose a number of threads, up to this maximum, most suitable to the problem size.
d. The LMT2MPC elimination will be ignored.
e. If there is not sufficient memory for an in-core solve, an out-of-core solve will be attempted.
f. Only the FNT/PFNT methods for nonlinear iteration (KMETHOD field of NLPARM
parameter) are supported.
g. Only SOL 400 with ANALYSIS = NLSTATICS and SOL 101 with general linear contact
(excluding permanent glue contact) is supported for 2014 release.
h. DOMAINSOLVER (RUNOPT=MULTIMST) is not supported with the Intel MKL Pardiso
solver. If used, MSTSLV will be used instead.
i. When using SOL 400, if the problem fails to converge with PRDLDL, then setting
SYSTEM(682)=0 to turn off Bunch-Kaufman pivoting and setting SYSTEM(680)=4 to
increase number of iterative refinement steps to 4 may recover convergence.
16. For CEAD the default solver for unsymmetric matrices is UMFPACK while for Hermitian
matrices the default is MSCLU.

Main Index
 178 TIME
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
 Case Control Commands MSC Nastran Quick Reference GuideMSC Nastran Quick Reference Guide

4 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
 180 Key to Descriptions
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 describersare
default describers are 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
 The Case Control Section 181
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 (p. 459) in the MSC Nastran Reference Manual).
• Defines the subcase structure for the analysis.

Table 4-7 through Table 4-12 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.

Main Index
 182 The Case Control Section
The Case Control Section

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 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.

Main Index
 Case Control Command Summary 183
Case Control Command Summary

Case Control Command Summary

This section contains a summary of all Case Control commands under the following headings:

Subcase Definition
1. Output Request Delimiters

ENDCARDS Reactivates processing of Bulk Data entries (MSGMESH).

OUTPUT (Case) Delimits the various types of commands for the structure
plotter, curve plotter, grid point stress, and MSGSTRESS.
OUTPUT(PLOT) Beginning of structure plotter output request.
OUTPUT(POST)
or Indicates beginning of grid point stress output requests
SETS DEFINITION and/or p-element data recovery set definition.

OUTPUT(XYOUT)
or Indicates beginning of curve plotter output request.
OUTPUT(XYPLOT)

OUTPUT(CARDS) Suppresses processing of Bulk Data entries (MSGMESH).

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.
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.

Main Index
 184 Case Control Command Summary
Case Control Command Summary

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.
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.

Main Index
 Case Control Command Summary 185
Case Control Command Summary

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.
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.

Main Index
 186 Case Control Command Summary
Case Control Command Summary

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.
NLHARM (Case) Selects the parameters used for nonlinear harmonic response analysis.
NLOPRM (Case) Controls MSC Nastran nonlinear output, debug printout and debug
POST.
NLPARM (Case) Selects the parameters used for nonlinear static analysis.
SMETHOD (Case) Selects iterative solver override parameters in nonlinear static analysis.

Main Index
 Case Control Command Summary 187
Case Control Command Summary

STEP (Case) Defines and identifies a nonlinear analysis for SOL 400.
TSTEPNL (Case) Transient time step set selection for nonlinear analysis.

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.
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 entries for the current subcase that are to be
used in a DRESP2 or DRESP3 response that spans subcase.

Main Index
 188 Case Control Command Summary
Case Control Command Summary

DSAPRT (Case) Specifies design sensitivity output parameters.

MODTRAK (Case) Selects mode tracking options in design optimization (SOL 200).

11. .p-Element and p-Adaptivity Analysis

ADAPT (Case) Specifies whether or not the subcase is to participate in the p-adaptivity
process.
ADAPT (Case) Specifies p-adaptivity control parameters.
DATAREC (Case) Requests form and type of output for p-version elements.
OUTRCV (Case) Selects the output options for p-elements defined on an OUTRCV Bulk
Data entry.
SET (Case) Defines a set of element identification numbers only for the SURFACE
and VOLUME commands (grid point stress) or the OUTRCV Bulk
Data entry (p-element data recovery). This form of the SET command
must and can only be specified after the SETS DEFINITION or
OUTPUT(POST) command delimiter.
SETS DEFINITION Delimits the various type of commands under grid point stress and/or
(Case) p-version element set definitions. This command is synonymous with
OUTPUT(POST).
VUGRID (Case) Requests output of view grid and view element entries used in
p-version element data recovery.

12. Adaptive Meshing

HADAPT (Case) Specifies Mesh adaptivity control parameters.

13. 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.

Main Index
 Case Control Command Summary 189
Case Control Command Summary

INTENSITY (Case) Requests output of acoustic intensity on wetted surface.

TRIMGRP (Case) Selection of Trim Component(s)

14. 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.

15. Contact

BCHANGE (Case) Selects the change of the definition contact bodies in contact
analysis.
BCMOVE (Case) Contact body movement selection in contact analysis.
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.

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.

Main Index
 190 Case Control Command Summary
Case Control Command Summary

PLOTID Defines a character string that will appear on the first frame of any plotter
(Case) 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.
SUBTITLE Defines a subtitle that will appear on the second heading line of each page
(Case) of 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.

3. Physical Set Output Requests

ACCELERATION (Case) Requests the form and type of acceleration vector output.
BOUTPUT (Case) Requests line or 3D (SOL 600) contact output.
CMSENRGY (Case) Requests the output of component (superelement) modal strain,
kinetic, and damping energies.

Main Index
 Case Control Command Summary 191
Case Control Command Summary

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
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 for printing only.
GPSTRESS (Case) Requests grid point stresses for printing only.
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).
HISTOGRAM (Case) Requests resultant stress/strain time history and/or rainflow
cycle histogram output from entities of a FATIGUE output
request.
MCFRACTION (Case) Requests modal contribution fractions output.
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.

Main Index
 192 Case Control Command Summary
Case Control Command Summary

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.
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.
SVECTOR (Case) Requests the form and type of solution set eigenvector output.
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.
SACCELERATION Requests the form and type of solution set acceleration output.
(Case)
SDISPLACEMENT Requests the form and type of solution set displacement output.
(Case)

Main Index
 Case Control Command Summary 193
Case Control Command Summary

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

EXTSEOUT (Case) Specifies the data to be saved for an external superelement, and the
medium on which the data is to be saved.
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.
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
(Case) loads 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.

Main Index
 194 Case Control Command Summary
Case Control Command Summary

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.
SUPER (Case) Assigns a subcase(s) to a superelement or set of superelements.

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.
POST (Case) Controls selection of data to be output for postprocessing.
RIGID (Case) Selects type of rigid element formulations to be used.

Main Index
 Case Control Commands 195
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-lsdyna. 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-lsdyna 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
 196 $S700
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. This option controls ARC output files which include Eulerian element results.

Format:
$S700 TYPE(logical_file) = ARCHIVE
$S700 ELEMENTS(logical_file) = setid
$S700 SET setid = idi
$S700 ELOUT(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

Field Contents
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 Element identification numbers at which the output is requested. “THRU” and “BY”;
for the “THRU” and “BY” options, respectively. See Remark 6. (Integer > 0 or
characters; Required)
Var Variable name to be output. See Remark 7. (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 4. and
5. (Real > 0.0 or characters; Required)

Main Index
 $S700 197
Direct Case Control Command for SOL 700

Field Contents
stepi Steps at which output is required. “THRU” and “BY”; for the “THRU” and “BY”
options, respectively. See Remarks 4. and 5. (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. SOL 700 supports only ARCHIVE file type, ELEMENTS output and ELOUT variables.
3. 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.
4. Either STEPS or TIMES must be specified. STEPS and TIMES can not be used for the same
logical_file.
5. A list of times or steps should be in ascending order.
6. For choosing element ids, additional options are available.
ALLEULHYDRO: output for all entities associated with hydrodynamic Eulerian elements.
ALLEULSTRENGTH: output for all entities associated with Eulerian elements with shear
strength.
ALLMULTIEULHYDRO: output for all entities associated with hydrodynamic Eulerian
multimaterial elements.
ALLMULTIEULSTREN: output for all entities associated with Eulerian multimaterial elements
with shear strength.
7. Result variables depending on the Euler element types are described below.

Table 4-1 Eulerian Solid Elements - Hydrodynamic

Output Variables Description
XVEL x-velocity
YVEL y-velocity
ZVEL z-velocity
VOLUME Element volume
MASS Mass of material 1
DENSITY Density of material 1
SIE Specific internal energy of material 1
PRESSURE Pressure

Main Index
 198 $S700
Direct Case Control Command for SOL 700

Table 4-1 Eulerian Solid Elements - Hydrodynamic

Output Variables Description
Q Artificial viscosity
ENERGY Total energy (kinetic + internal) of material 1
DIV Divergence
VOID Void fraction
FMAT Material fraction of material 1
FMATPLT Material fraction of material times the volume uncovered fraction
SSPD Speed of sound
FBURN Burn fraction
TDET Detonation time
BFTIME Burn time
XMOM x-momentum
YMOM y-momentum
ZMOM z-momentum
FVUNC Volume uncovered fraction
QDIS Characteristic element length
FVUOLD Old volume uncovered fraction
MFLR Total mass-flow rate (sum of MFLR-POR, MFLR-PER and MFLR-INF)
MFL Total mass-flow (sum of MFLR-POR, MFLR-PER and MFLR-INF)
MFLR-POR Mass-flow rate by PERMEAB (flow between the Euler element and GBAGs
through holes) or PORHOLE (flow between the Euler element and the
environment through holes)
MFL-POR Mass-flow by PORFGBG (flow between the Euler element and GBAGs through
holes) or PORHOLE (flow between the Euler element and the environment
through holes)
MFLR-PER Mass-flow rate by PERMGBG (flow between the Euler element and GBAGs
through permeable surfaces) or PERMEAB (flow between the Euler element and
the environment through permeable surfaces)
MFL-PER Massflow by PERMEAB (flow between the Euler element and GBAGs through
permeable surfaces) or PERMEAB (flow between the Euler element and the
environment through permeable surfaces)
MFLR-INF Massflow rate by inflators (inflow by INFLTR)
MFL-INF Massflow by inflators (inflow by INFLTR)
DQDT Total heat transfer rate (sum of DQDT-CNV and DQDT-RAD)
DQ Total heat transfer (sum of DQ-CNV and DQ-RAD)

Main Index
 $S700 199
Direct Case Control Command for SOL 700

Table 4-1 Eulerian Solid Elements - Hydrodynamic

Output Variables Description
DQDT-CNV Heat transfer rate by HTRCONV (transfer from the Euler element to the
environment through surfaces)
DQ-CNV Heat transfer by HTRCONV (transfer from the Euler element to the environment
through surfaces)
DQDT-RAD Heat transfer rate by HTRRAD (transfer from the Euler element to environment
through surfaces)
DQ-RAD Heat transfer by HTRRAD (transfer from the Euler element to the environment
through surfaces)

Table 4-2 Eulerian Solid Elements - Viscous Hydrodynamic

Output Variables Description
XVEL x-velocity
YVEL y-velocity
ZVEL z-velocity
VOLUME Element volume
MASS Mass of material 1
DENSITY Density of material 1
SIE Specific internal energy of material 1
PRESSURE Pressure
Q Artificial viscosity
ENERGY Total energy (kinetic + internal) of material 1
DIV Divergence
VOID Void fraction
FMAT Material fraction of material 1
SSPD Speed of sound
FBURN Burn fraction
TDET Detonation time
BFTIME Burn time
XMOM x-momentum
YMOM y-momentum
ZMOM z-momentum
FVUNC Volume uncovered fraction

Main Index
 200 $S700
Direct Case Control Command for SOL 700

Table 4-2 Eulerian Solid Elements - Viscous Hydrodynamic

Output Variables Description
QDIS Characteristic element length
SXX xx-deviatoric stress
SYY yy-deviatoric stress
SZZ zz-deviatoric stress
TXX xx-stress
TYY yy-stress
TZZ zz-stress
TXY xy-stress
TYZ yz-stress
TZX zx-stress
EFFSTS Effective stress
DUDX x-velocity gradient in x-direction
DUDY x-velocity gradient in y-direction
DUDZ x-velocity gradient in z-direction
DVDX y-velocity gradient in x-direction
DVDY y-velocity gradient in y-direction
DVDZ y-velocity gradient in z-direction
DWDX z-velocity gradient in x-direction
DWDY z-velocity gradient in y-direction
DWDZ z-velocity gradient in z-direction
FVUOLD Old volume uncovered fraction
MFLR Total mass-flow rate (sum of MFLR-POR, MFLR-PER and MFLR-INF)
MFL Total mass-flow (sum of MFLR-POR, MFLR-PER and MFLR-INF)
MFLR-POR Mass-flow rate by PERMEAB (flow between the Euler element and GBAGs
through holes) or PORHOLE (flow between the Euler element and the
environment through holes)
MFL-POR Mass-flow by PORFGBG (flow between the Euler element and GBAGs through
holes) or PORHOLE (flow between the Euler element and the environment
through holes)
MFLR-PER Mass-flow rate by PERMGBG (flow between the Euler element and GBAGs
through permeable surfaces) or PERMEAB (flow between the Euler element and
the environment through permeable surfaces)

Main Index
 $S700 201
Direct Case Control Command for SOL 700

Table 4-2 Eulerian Solid Elements - Viscous Hydrodynamic

Output Variables Description
MFL-PER Massflow by PERMEAB (flow between the Euler element and GBAGs through
permeable surfaces) or PERMEAB (flow between the Euler element and the
environment through permeable surfaces)
MFLR-INF Massflow rate by inflators (inflow by INFLTR)
MFL-INF Massflow by inflators (inflow by INFLTR)
DQDT Total heat transfer rate (sum of DQDT-CNV and DQDT-RAD)
DQ Total heat transfer (sum of DQ-CNV and DQ-RAD)
DQDT-CNV Heat transfer rate by HTRCONV (transfer from the Euler element to the
environment through surfaces)
DQ-CNV Heat transfer by HTRCONV (transfer from the Euler element to the environment
through surfaces)
DQDT-RAD Heat transfer rate by HTRRAD (transfer from the Euler element to environment
through surfaces)
DQ-RAD Heat transfer by HTRRAD (transfer from the Euler element to the environment
through surfaces)

Table 4-3 Eulerian Solid Elements - with Shear Strength

Output Variables Description
XVEL x-velocity
YVEL y-velocity
ZVEL z-velocity
TXX xx-stress
TYY yy-stress
TZZ zz-stress
TXY xy-stress
TYZ yz-stress
TZX zx-stress
EFFSTS Effective stress
PRESSURE Pressure
SXX xx-deviatoric stress
SYY yy-deviatoric stress
SZZ zz-deviatoric stress
SXY xy-deviatoric stress

Main Index
 202 $S700
Direct Case Control Command for SOL 700

Table 4-3 Eulerian Solid Elements - with Shear Strength

Output Variables Description
SYZ yz-deviatoric stress
SZX zx-deviatoric stress
SINWX x-stress rotation angle
SINWY y-stress rotation angle
SINWZ z-stress rotation angle
EFFPLS Effective plastic strain
EPSXXD xx-strain rate
EPSYYD yy-strain rate
EPSZZD zz-strain rate
EPSXYD xy-strain rate
EPSYZD yz-strain rate
EPSZXD zx-strain rate
VOLUME Element volume
MASS Mass of material 1
DENSITY Density of material 1
SIE Specific internal energy
EDIS Distortional energy
ENERGY Total energy (kinetic + internal)
Q Artificial viscosity
DIV Divergence
VOID Void fraction
FMAT Material fraction
FMATPLT Material fraction of material times the volume uncovered fraction
SSPD Speed of sound
FBURN Burn fraction
TDET Detonation time
BFTIME Burn time
XMOM x-momentum
YMOM y-momentum
ZMOM z-momentum
FVUNC Volume uncovered fraction
QDIS Characteristic element length

Main Index
 $S700 203
Direct Case Control Command for SOL 700

Table 4-3 Eulerian Solid Elements - with Shear Strength

Output Variables Description
FVUOLD Old volume uncovered fraction
VOLPLS Volumetric plastic strain; used for snow model
SOFTE Softening; used for snow model

Table 4-4 Eulerian Solid Elements - Multimaterial Hydrodynamic

Output Variables Description
XVEL x-velocity
YVEL y-velocity
ZVEL z-velocity
VOLUME Element volume
MASS Mass of material 1
DENSITY Density of material 1
SIE Specific internal energy of material 1
PRESSURE Pressure
Q Artificial viscosity
ENERGY Total energy (kinetic + internal) of material 1
DIV Divergence
VOID Void fraction
FMAT Material fraction of material 1
FMATPLT Material fraction of material times the volume uncovered fraction
SSPD Speed of sound
FBURN Burn fraction
TDET Detonation time
BFTIME Burn time
XMOM x-momentum
YMOM y-momentum
ZMOM z-momentum
FVUNC Volume uncovered fraction
QDIS Characteristic element length
FVUOLD Old volume uncovered fraction
MASST Total mass of element

Main Index
 204 $S700
Direct Case Control Command for SOL 700

Table 4-4 Eulerian Solid Elements - Multimaterial Hydrodynamic

Output Variables Description
HMAT Internal material number with the largest volume fraction
VOLPLS Volumetric plastic strain; used for snow model
SOFTE Softening; used for snow model
DAMAGE Damage; used for FAILJC

Table 4-5 Eulerian Solid Elements - Multimaterial with Shear Strength

Output Variables Description
XVEL x-velocity
YVEL y-velocity
ZVEL z-velocity
VOLUME Element volume
MASS Mass of material 1
DENSITY Density of material 1
SIE Specific internal energy of material 1
PRESSURE Pressure
Q Artificial viscosity
ENERGY Total energy (kinetic + internal) of material 1
DIV Divergence
VOID Void fraction
FMAT Material fraction of material 1
FMATPLT Material fraction of material times the volume uncovered fraction
EPSXXD xx-strain rate
EPSYYD yy-strain rate
EPSZZD zz-strain rate
EPSXYD xy-strain rate
EPSYZD yz-strain rate
EPSZXD zx-strain rate
SINWX x-stress rotation angle
SINWY y-stress rotation angle
SINWZ z-stress rotation angle
SXX xx-deviatoric stress

Main Index
 $S700 205
Direct Case Control Command for SOL 700

Table 4-5 Eulerian Solid Elements - Multimaterial with Shear Strength

Output Variables Description
SYY yy-deviatoric stress
SZZ zz-deviatoric stress
SXY xy-deviatoric stress
SYZ yz-deviatoric stress
SZX zx-deviatoric stress
TXX xx-stress
TYY yy-stress
TZZ zz-stress
TXY xy-stress
TYZ yz-stress
TZX zx-stress
EFFPLS Effective plastic strain
EFFSTS Effective stress
EDIS Distortional energy
VOLOLD Old volume
HMAT Internal material number with the largest volume fraction
VOLPLS Volumetric plastic strain; used for snow model
SOFTE Softening; used for snow model
DAMAGE Damage; used for FAILJC

Table 4-6 Eulerian Solid Elements - IG Explosive Materials (EOSIG) Only

Output Variables Description
SIE-E Specific internal energy per unit of mass of un-reacted explosive part
SIE-P Specific internal energy per unit of mass of reaction products part
IGBURN Burn fraction
FMAT-P Volume fraction of reaction product
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

Main Index
 206 $S700
Direct Case Control Command for SOL 700

All variables starting with MFL (MassFLow) have the following sign conventions:

MFLxx > 0 means inflow of mass in the Euler element.

MFLxx < 0 means outflow of mass from the Euler element.

All variables starting with DQ have following sign conventions:

DQxx > 0 means inflow of heat in the Euler element.

DQxx < 0 means outflow of heat from the Euler element.

The different materials in an element are in pressure equilibrium, but they have their own density, specific
internal energy, and material volume fraction. The variables stored in element data storage relate to the
material in the element that is stored as the first one internally. Multi-material editing can be performed
for a material with material user number xx using the following variables:
MASSxx: Mass of material xx.
DENSITYxx: Density of material xx.
SIExx: Specific internal energy of material xx.
ENERGYxx: Total energy of material xx.
DIVxx: Divergence of material xx.
FMATxx: Volume fraction of material xx.

Note: Leading zeros in material user numbers are not accepted as correct input.

Main Index
 A2GG (Case) 207
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. It must appear above any subcase structure.

Main Index
 208 ACCELERATION (Case)
Acceleration Output Request

ACCELERATION (Case) Acceleration Output Request

Requests form and type of acceleration vector output.

Format:
SORT1 PRINT, PUNCH REAL or IMAG PSDF, ATOC ,CRMS
ACCELERATION ( , , , ,
SORT2 PLOT PHASE or RALL

RPRINT
, RPUNCH ,CID ,
NORPRINT

 ALL 
   
[TRMC =  ALL  =  n 
 setid   
 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(TRMC=100)=101

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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Computes, but does not print or punch, acceleration output.
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.

Main Index
 ACCELERATION (Case) 209
Acceleration Output Request

Describer Meaning
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.
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.
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.
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 Accelerations at no points will be output.
TRMC Selects a set of trim components for output. The default is NONE. See
Remark 10..

TRMC=ALL: Output the solution results from all trim components

involved in the analysis by Case Control command, TRIMGRP.

setid is the identification of a trim component set, defined by a previously

appearing SET command. (Integer>0).

Remarks:
1. Both PRINT and PUNCH may be requested.
2. 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.
3. See Remark 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2.
4. ACCELERATION=NONE allows overriding an overall output request.
5. The PLOT option is used when curve plots are desired in the magnitude/phase representation and
no printer request is present for magnitude/phase representation.

Main Index
 210 ACCELERATION (Case)
Acceleration Output Request

6. Acceleration results are output in the global coordinate system (see field CD on the GRID Bulk
Data entry).
7. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.
8. 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.
9. The selected trim components must be specified by TRIMGRP for the analysis. Since the same
grid point identifications can be shared by several trim components as well as the structure/cavity,
unintentional output could happen.
10. TRMC subcommand should be used to identify the IDs of trim component for which data
recovery operation is requested. The interface grid IDs of trim components that data recovery is
desired should be included in the set n of the request.

Main Index
 ACFPMRESULT (Case) 211
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 only.

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.
PRINT The printer will be the output medium (Default).
PUNCH The punch file will be the output medium.
PLOT Results are generated but not output.
The PLOT option is used if results are requested for postprocessing but no
printer output is desired.
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.
ALL Radiated power will be processed for the wetted surface and all panels.
PHASE Requests polar format (magnitude and phase) of complex output. Phase
output is in degrees.
POWER Requests output of power through field point mesh (Default = YES).
ALL Results of all field point meshes will be processed.
n Set identification of a previously defined set of field point mesh identifiers.
Results will be processed for the field point meshes in this set only.
NONE Field point mesh results will not be processed. ACFPMRESULT = NONE
overrides an overall request.

Main Index
 212 ACFPMRESULT (Case)
Acoustic Field Point Mesh Results Output Request

Remark:
1. Both PRINT and PUNCH may be requested.
2. 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.

Main Index
 ACPOWER (Case) 213
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 only.

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).
PRINT The printer will be the output medium (Default).
PUNCH The punch file will be the output medium.
PLOT Results are generated but not output.
The PLOT option is used if results are requested for postprocessing but no printer
output is desired.
CSV Results will be written to a .CSV file. See Remark 2.
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. Both PRINT and PUNCH may be requested.
2. If output to an .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

Main Index
 214 ACTIVAT (Case)
Elements to be Reactivated in SOL 600

ACTIVAT (Case) Elements to be Reactivated in SOL 600

Indicates which Bulk Data ACTIVAT entry is used to control the elements to be activated in this subcase.
This entry may only be used in SOL 600.

Format:
ACTIVAT=N

Example:
ACTIVAT=3

Describer Meaning
N ID of a matching Bulk Data ACTIVAT entry specifying the elements to be
reactivated for this subcase.

Remarks:
1. Different sets of elements can be reactivated during different subcases using this Case Control
command.
2. The elements specified in the matching ACTIVAT Bulk Data entry must currently be in a
deactivated state.

Main Index
 ACTRIM (Case) 215
ACTRAN Trimmed Material Matrices for SOL 108/111

ACTRIM (Case) ACTRAN Trimmed Material Matrices for SOL 108/111

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
 216 ADACT (Case)
p-Adaptivity Subcase Selection

ADACT (Case) p-Adaptivity Subcase Selection

Specifies whether or not the subcase is to participate in the p-adaptivity process.

Format:
 ALL 
 
ADACT =  n 
 
 NONE 

Examples:
ADACT=NONE
ADACT=10

Describer Meaning
ALL All subcases will participate in the error analysis.
n The first n modes in a normal modes analysis will participate in the error analysis
(Integer > 0).
NONE The current subcase will not participate in the error analysis.

Remarks:
1. ADACT is processed only when an adaptive analysis is requested. An ADAPT Case Control
command must be present in order to have an p-adaptive analysis.
2. In a static analysis, ADACT=n is equivalent to ADACT=ALL, and ALL means that the results
of all subcases will be included in the error analysis. When ADACT=NONE in any subcase, the
results of that subcase are excluded from the error analysis and adaptivity.
3. In an eigenvalue analysis, ALL means that the results of all the modes will be included in the error
analysis.
4. Only one ADACT command may be specified per subcase.

Main Index
 ADAMSMNF* (Case) 217
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   NONE   MNF 
     
MINVAR =  FULL  , PSETID =  setid plotel  , EXPORT =  DB 
     
 NONE   ALL   BOTH 
 RIGID 
 

Example(s):
ADAMSMNF FLEXBODY = YES

Note: *Nastran/ADAMS modal stress recovery (MSR) interface is also available. See Remark
19. CAUTION: Do not use mode=i8 (64 bit integer, 64 bit float) option when submitting
the Nastran job if the ADAMSMNF EXPORT option specifies DB or BOTH and your
intent is to use the DB in ADAMS. ADAMS does not currently support i8 DB files. If you
use mode=i8, you must use the MNF in ADAMS.

NASTRAN/ADAMS MNF can be used with SOL 400 as described in Remark 21.

Describer Meaning
FLEXBODY Requests that the Nastran/ADAMS interface be executed.
NO Executes standard Nastran.
YES Executes Nastran/ADAMS interface.

Main Index
 218 ADAMSMNF* (Case)
Control for Nastran/ADAMS Interface

Describer Meaning
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.
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 (4-1), (4-2), (4-6), and (4-7) will be calculated.
PARTIAL All mass invariants except (4-5) and (4-9) will be calculated.
NONE No mass invariants are computed.

Main Index
 ADAMSMNF* (Case) 219
Control for Nastran/ADAMS Interface

Describer Meaning
RIGID No modal information is output to the .mnf file. Only units, grid point
coordinates, element connectivity, interface nodes, and invariant (4-1), (4-2),
and (4-7) data are shared in the .mnf file.
EXPORT Controls modal output to MNF file, Nastran database or both.
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.

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.
3. The nine mass invariants are defined by Eqs. (4-1) through (4-9):
N
1
I
1×1
=  mp (4-1)
p =1

N
2
I
3×1
=  mp sp (4-2)
p =1

N
3
Ij
=  m p Φ p j = 1, …, M (4-3)
3×M p =1

N
4
I *

3×M
=  m p s̃ pΦ + I p Φ p
p
(4-4)
p = 1

N
5
Ij
=  m p φ̃ pj Φ p j = 1, …, M (4-5)
3×M p =1

Main Index
 220 ADAMSMNF* (Case)
Control for Nastran/ADAMS Interface

N
6
I T *T *

M×M
=  mp Φp Φp + Φp Ip Φp (4-6)
p =1

N
7
I T

3×3
=  m p s̃ p s̃ p + I p (4-7)
p= 1

N
8
Ij
=  m p s̃ p φ̃ pj j = 1, …, M (4-8)
3×3 p =1

N
9
Ijk
=  m p φ̃ pj φ̃ pk j, k = 1 , … , M (4-9)
3×3 p=1

where s p = [ xyz ] T are the coordinates of grid point p in the basic coordinate system;

0 –z y
s̃ p = z 0 –x
–y x 0

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. Since p-elements use a coupled mass formulation, they should not be used.
5. If the CONM1 is used, M21, M31, and M32 entries should be left blank.
6. If PARAM,GRDPNT,value specified, mass invariants 1I , 2I , and 7I 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
 ADAMSMNF* (Case) 221
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. The OUTSTRS or
OUTSTRN entries are required for importing ADAMS results into MSC Fatigue. See the
Nastran/ADAMS/durability documentation for more information.

Main Index
 222 ADAMSMNF* (Case)
Control for Nastran/ADAMS Interface

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.
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 is intended for users who plan to import ADAMS results into MSC
Fatigue. This 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 for input into MSC Fatigue.
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.

Main Index
 ADAMSMNF* (Case) 223
Control for Nastran/ADAMS Interface

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:
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.

Main Index
 224 ADAMSMNF* (Case)
Control for Nastran/ADAMS Interface

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.
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 or, for a Nastran/ADAMS
interface run, by PARAM,SESDAMP,FRB (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 = ye Modal damping for each superelement SDAMP  TABDMP1
s using the fixed boundary CMS modes. SDAMP in superelement subcase.
sesdamp = frb Modal damping for each superelement SDAMP  TABDMP1
using the free boundary 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.

Main Index
 ADAMSMNF* (Case) 225
Control for Nastran/ADAMS Interface

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 results, the ADAMS results, when brought back into Nastran
SOL 111 or SOL 112, must be restarted from the original Nastran database that produced the
original .mnf which was the basis of the ADAMS run.
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

Main Index
 226 ADAMSMNF* (Case)
Control for Nastran/ADAMS Interface

METHOD = 210
$ 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.

Main Index
 ADAPT (Case) 227
p-Adaptivity Control Selection

ADAPT (Case) p-Adaptivity Control Selection

Specifies p-adaptivity control parameters.

Format:
ADAPT=n

Example:
ADAPT=12

Describer Meaning
n Set identification for either an ADAPT or PSET Bulk Data entry (Integer > 0).

Remarks:
1. ADAPT is required only when an analysis with p-elements is requested.
2. A multiple p-level analysis with error analysis is performed whenever the ADAPT command
references an ADAPT Bulk Data entry.
3. A single p-level analysis without error analysis is performed whenever the ADAPT command
references a PSET Bulk Data entry.
4. Only one ADAPT may appear in the Case Control Section, and should appear above all
SUBCASE commands.
5. The subcases that will not participate in the error analysis/p-adaptivity must contain the
ADACT=NONE command.

Main Index
 228 AECONFIG (Case)
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
 AERCONFIG (Case) 229
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
 230 AEROF (Case)
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
 AESYMXY (Case) 231
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
 232 AESYMXZ (Case)
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
 AEUXREF (Case) 233
Defines the Reference Aerodynamic Extra Point (Controller) Vector

AEUXREF Defines the Reference Aerodynamic Extra Point (Controller) Vector

(Case)

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
 234 ANALYSIS (Case)
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.

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, 159 and 600 only)
STRUCTURE Structural Analysis (SOLs 153 & 159 only, default for these two
SOLs)
HSTAT Steady State Heat Transfer (SOL 400)
HTRAN Transient Heat Transfer (SOL 400)
NLSTATICS Nonlinear Static Analysis (SOL 400 and 700). See Remark 5.
NLTRAN Nonlinear Transient Analysis (SOL 400 and 700). See Remark 3.
HOT2COLD Hot-to-cold Analysis (SOL 106 only). See Remark 4.

Main Index
 ANALYSIS (Case) 235
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

Describer Meaning
RCNS RC Network Thermal Solver Steady State
RCNT RC Network Thermal Solver Transient

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
• SOL 600,153 and SOL 600,159 require ANALYSIS=HEAT. For other SOL 600,ID
executive control entries, ANALYSIS= is not used and should not be entered.
• 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 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)).

Main Index
 236 ANALYSIS (Case)
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

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.
• 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 not allowed.
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

Main Index
 ANALYSIS (Case) 237
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

• 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
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=MODES, DFREQ, MFREQ, MTRAN, DCEIG, and MCEIG entries.
An example is:
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
SPC = 2
DISPLACEMENT = ALL
STEP 3
LABEL=Linear Perturbation, MFREQ
ANALYSIS = MFREQ
NLIC STEP 1 LOADFAC 1.0

Main Index
 238 ANALYSIS (Case)
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

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. These are standard
SUBCASE type of analysis.
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
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

Main Index
 ANALYSIS (Case) 239
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

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
TSTEPNL = 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
TSTEPNL= 1
SPC = 2
TEMP (LOAD, HSUBC=3) = 3
DISPLACEMENT(SORT1,REAL)=ALL
NLSTRESS = ALL
STRESS = ALL
STEP 2
TSTEPNL= 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
TSTEPNL= 3
SPC = 2
TEMP (LOAD, HSUBC=10, HTIME=ALL) = 5
DISPLACEMENT(SORT1,REAL)=ALL
NLSTRESS = ALL
stress = all

Main Index
 240 ANALYSIS (Case)
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

BEGIN BULK
g. 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
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.
An example is:
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

Main Index
 ANALYSIS (Case) 241
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

SUBCASE 5
$ NORMAL MODES AT THE NEW LOADING
ANALYSIS= MODES
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.
5. . MSC Nastran SOL 700 analysis allows for three thermal analysis types:
a. Structural temperature loading (Control Solution: SOLN=0): ANALYSIS = NLTRAN
b. Thermal temperature loading (Control Solution: SOLN=1): ANALYSIS = HTRAN
c. Combination structural and thermal (Control Solution SOLN=2):
STEP=1
SUBSTEP=10
ANALYSIS=HTRAN

Main Index
 242 ANALYSIS (Case)
Analysis Discipline SUBCASE/STEP/SUBSTEP Assignment

SUBSTEP=20
ANALYSIS=NLTRAN
This thermal analysis is only available in the double precision version of SOL 700(DPL=YES)

Main Index
 APRESSURE (Case) 243
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
 244 AUTOSPC (Case)
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 ], [ EPSSING = r2 ],
 NOPRINT PUNCH

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 residual structure and superelements. See
Remarks 6. and 7.

For SOL 101, applies AUTOSPC to linear analysis with contact. See Remark
8.
PRINT Enables the printout of a summary table of singularities (Default).
NOPRINT Disables the printout of a summary table of singularities.
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).
EPSSING=r2 Identifies the potential singularities with stiffness ratios less than r2. See
Remark 2. (Default=1.E-8).
SPC Applies single-point constraints on degrees of freedom identified as singular.
(Default)
MPC Applies multipoint constraints on degrees of freedom identified as singular.

Main Index
 AUTOSPC (Case) 245
Constrains Stiffness Singularities via m-sets or s-sets

Describer Meaning
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 (p. 353) in the MSC
Nastran Reference Manual 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. The default equals YES for all solutions except nonlinear SOLs 106, 129, and 153. For these
SOLs this command is ignored for the residual structure. The AUTOSPC operation provides the
correct action for upstream superelements. Parameter PARAM,AUTOSPCR, not the AUTOSPC
command, is used for the o-set (omitted set) in the residual structure in SOLs 106 and 153.
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.
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

Main Index
 246 AUTOSPC (Case)
Constrains Stiffness Singularities via m-sets or s-sets

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 101 with contact, user can turn on AUTOSPC by using RESIDUAL option. i.e., when
AUTOSPC(RESIDUAL)=YES, AUTOSPC will be turned on for linear analysis with contact.
9. This entry is not supported by SOL 600. Please enter PARAM,AUTOSPC in the bulk data.

Main Index
 AUXCASE (Case) 247
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
 248 AUXMODEL (Case)
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
 AXISYMMETRIC (Case) 249
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 (p. 117) in the MSC Nastran Reference Manual for a discussion of the
conical shell problem.
4. See the Additional Topics (Ch. A) in the for a discussion of the hydroelastic formulation.
5. The sine boundary condition will constrain components 1, 3, and 5 at every ring for the zero
harmonic.
6. The cosine boundary condition will constrain components 2, 4, and 6 at every ring for the zero
harmonic.
7. SPC and MPC Case Control commands may also be used to specify additional constraints. See
Case Control Commands, pg. 179.

Main Index
 250 B2GG (Case)
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
name Name of [ B 2gg ] 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, pg. 707.
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
 B2PP (Case) 251
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
name Name of [ B 2pp ] 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 (p. 353) in the MSC Nastran Reference Manual.
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
 252 BC (Case)
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
 BCHANGE (Case) 253
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
 254 BCONTACT (Case)
Selects 3D Contact Surfaces

BCONTACT (Case) Selects 3D Contact Surfaces

This entry is used to initiate and control which bodies come into contact in SOLs 101, 400, and 700.
For SOL 101 and SOL 400, the form BCONTACT = n or = ALLBODY is required with default
BCONTACT = NONE. In SOL 101, standard subcase rules apply. In SOL 400, standard step rules apply;
thus, BCONTACT may be specified within each subcase or step to define which bodies may make
contact during that particular subcase or step. In SOL 101 and SOL 400, the presence in the Bulk Data
Section of the contact entries listed below with ID=0 will automatically invoke initial preload contact
conditions, such that the contact bodies will just touch each other before the nonlinear simulation begins.
The permanent glued contact capability available in SOLs 101, 103, 105, 107, 108, 109, 110, 111, 112,
and 400 for small deformation and rotation is initiated by the presence of BCONTACT=n (n > 0) above
the subcase level referring to a BCTABLE,n, BCTABL1,n or BCONECT,n with a valid positive value in
the IGLUE field. See Remark 3.
SOL 700 allows only one BCONTACT Case Control command and only one subcase.

Format:
 n 
   
BCONTACT=  ALLBODY  or  ALLELE 
   
 NONE 

SOL 700 only

Examples:
BCONTACT = 5
BCONTACT=ALLBODY

Describer Meaning
n Identification number of a BCTABLE, BCTABL1, BCONECT, BCHANGE, and/or
BCMOVE Bulk Data entry. If the model has beams, this option or BCPROP or
MCMATL must be used.
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 and
SOL 700, 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.
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.)

Main Index
 BCONTACT (Case) 255
Selects 3D Contact Surfaces

Describer Meaning
ALLELE All elements in the model can potentially contact with each other. When this option
is specified, no 3D contact input is required in the bulk data and, if entered, will be
ignored. Warning-this option may take excessive computer time. This option can only
be used if it applies to all subcases. All elements in the model must be the same kind
(either shell or solid). This option may not be used if there are beams, bars or rods in
the model. (SOL 700 only)

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, and 112.
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.
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. For SOL700, if the form BCONTACT=ALLBODY, SOL700 will fatal
if no BCBODY entries are found.
4. If all slave'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 will be
used for all SLAVE entries in all subcases and all steps unless BCPARA,0,NLGLUE,1 is
specified. If IGLUE < exists, permanent glued contact for large deformation and large rotation is
activated. For further discussions of NLGLUE, see Remark 3. of BCONTACT. (Integer; Default
= 0)
5. The ALLELE option requires that the model be made up of either all shells or all solids.
The use of BCONTACT and the entries it references, BCTABLE or BCTABL1, BCONECT, BCONPRG,
BCONPRP define the interaction of the bodies in the loadcase or step. From a user's perspective one can
define contact as:
General Contact - two bodies may come into contact and separate at any point in the simulation and the
bodies may slide alone 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, SOL 600 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.

Main Index
 256 BCONTACT (Case)
Selects 3D Contact Surfaces

Bodied that are in glued contact may lose contact if the separation (force or stress based) separation
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 value a
negative value of IGLUE for each contact pair. It is similar to Glued Contact, there are two conditions.
1. The contact status will be checked at the beginning of the step, and those nodes or segments that
are in contact will remain in glued contact for the entire step. The constraints will change due to
large rotations. Furthermore if a large tensile force or stress developed over the interface in the
current loadcase, no separation would occur for these regions which are initially in contact. .
Performing an Unglue of Breaking glue would also not be 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 wanted 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 will 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 due 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 will be 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 will never separate. Permanent glue should not be
used in models that experience large rotations. It is applicable to SOL 101, 103, 105, 107, 108, 109, 110,
111, 112, SOL 200 and SOL 400 . Permanent Glued contact is activated if the BCTABLE or BCTABL1
that is referenced in the first Loadcase (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, enter bulk data BCPARA,0,NLGLUE,1 to deactivate the Permanent Glue in a
subsequent step .
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.
In SOL 400 one can have a 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.

Main Index
 BCONTACT (Case) 257
Selects 3D Contact Surfaces in SOL 600

BCONTACT (Case) Selects 3D Contact Surfaces in SOL 600

This entry is used to initiate and control 3D contact in SOL 600.

Standard subcase rules apply and BCONTACT may be specified within each subcase to define which
bodies may make contact during that particular subcase. A BCONTACT = 0 above the subcase level is
used in SOL 600 to invoke an option such that the contact surfaces will just touch each other before the
nonlinear simulation begins. It is highly recommended that if contact is specified for any subcase in
SOL 600, and if there are any rigid contact surfaces, BCONTACT = 0 and a matching BCTABLE with
ID = 0 be included.

Format:
 ALL 
 
 ALLELE 
 
 ALLELE2 
 
 ALLGLUE 
 n   ALLGLU2 
   
BCONTACT=  ALLBODY  or  ALLGLUM 
   
 NONE   ALLGLM4 
 ALLGLUP 
 
 BCBOX 
 
 BCPROP 
 
 BCMATL 

Examples:
BCONTACT = 5
BCONTACT=ALLBODY

Describer Meaning
n Identification number of a BCTABLE, BCHANGE, and/or BCMOVE Bulk
Data entry. If the model has beams, this option or BCPROP or MCMATL must
be used.
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.
NONE All contact definitions (BCTABLE, BCBODY) are ignored. BCONTACT =
NONE may be used for any subcase desired and/or for increment zero - some
subcases can have contact and others no contact.
ALL All elements in the model can potentially contact with each other (Default).
When this option is specified, no 3D contact input is required in the bulk data
and, if entered, will be ignored. Warning–this option may take excessive
computer time. This option can only be used if it applies to all subcases.

Main Index
 258 BCONTACT (Case)
Selects 3D Contact Surfaces in SOL 600

Describer Meaning
ALLELE Same as ALL. All elements in the model must be the same kind (either shell or
solid). This option may not be used if there are beams, bars or rods in the model.
ALLELE2 Same as ALLELE except shell and solid elements may both be in the model in
which case separate bodies for each are formed. (This option requires that both
shells and solids be in the model.) All beams, bars and rods in the model will be
ignored with respect to contact.
ALLGLUE Same as ALLELE or ALLELE2 except glued contact will be used for all bodies.
The glued contact can vary from increment to increment, however when grids
come into contact they cannot separate. BCBODY and BCTABLE entries are
created automatically. BCBODY slave entries have IGLUE=I (see BCTABLE
entry).
ALLGLU2 Same as ALLELE or ALLELE2 except glued contact will be used for all bodies.
The glued contact can very from increment to increment, however when grids
come into contact they cannot separate. BCBODY and BCTABLE entries are
created automatically. BCBODY slave entries have IGLUE=2 (see BCTABLE
entry).
ALLGLUM Same as ALLELE or ALLELE2 except glued contact with moment carrying
glue will be used for all bodies. BCBODY and BCTABLE entries are created
automatically. BCBODY slave entries have IGLUE=3 (see BCTABLE entry).
ALLGLM4 Same as ALLELE or ALLELE2 except glued contact with moment carrying
glue will be used for all bodies. BCBODY and BCTABLE entries are created
automatically. BCBODY slave entries have IGLUE=4 (see BCTABLE entry).
ALLGLUP Same as ALLELE or ALLELE2 except “permanent glue” is used. This option
determines which grids are initially in contact and uses this contact situation in
a glued condition for the remainder of the analysis. To use this option, specify
PERMGLUE on the SOL 600 Executive Control statement. (SOL 600 only)
Note for SOL 600, the PERMGLUE option is the only way contact can be used
with SOL 600,101 or SOL 600,103 or other “linear” analyses.
BCBOX All elements defined within a box-like region as defined by the Bulk Data entry
BCBOX can potentially contact each other. See Remark 2.
BCPROP All elements defined by the Bulk Data entry BCPROP can potentially contact
each other. See Remark 2.
BCMATL All elements defined by the Bulk Data entry BCMATL can potentially contact
each other. See Remark 2.

Main Index
 BCONTACT (Case) 259
Selects 3D Contact Surfaces in SOL 600

Remarks:
1. Normally, only one form of this entry may be used in any given analysis. Analysis restarts must
use the same form as the original run. An exception is that if BCONTACT = NONE is entered for
any subcase, BCONTACT=N may also be specified for different subcases.
BCONTACT=ALLxxx cannot be mixed with BCONTACT=NONE or BCONTACT=N in the
same input file.
2. Bulk Data entries BCBOX, BCPROP, and BCMATL may be used with BCONTACT = n,
wherein case IDs specified on the BCBODY entry and on the BCBOX, BCPROP, and/or
BCMATL entries must match.
3. For options ALLELE, ALLELE2, ALLGLUE, ALLGLU2, ALLGLUM, and ALLGLM2, no
BCBODY or BCTABLE entries should be included in the model. Nastran will automatically
create BCBODY and/or BCTABLE entries as necessary for these options.
4. The ALLELE option requires that the model be made up of either all shells or all solids.
5. The ALLELE2 option requires that the model have both shells and solids.
6. The ALLGLUE, ALLGLU2, ALLGLUM and ALLGLM4 options can be used with models with
shells only, solids only for a combination of shells and solids.
7. The ALLGLUP option can either be used with BCBODY/BCTABLE entries or without them. If
there are not BCBODY/BCTABLE entries, SOL 600 will create them. If they exist, all SLAVE
lines on all BCTABLE entries must specify IGLUE=1.
8. The ALLG* options are not available for edge contact. Edge contact may only be run using
BCONTACT=N and the corresponding BCTABLE having a FBSH line with COPS1 and/or
COPM1 properly specified.

Main Index
 260 BCMOVE (Case)
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
 BEGIN BULK (Case) 261
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
BEGIN [ BULK ] AUXMODEL = auxmind
SUPER = seid
TRMC = trimid
UDS

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).
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
trimid Trim component identification number (Integer>0; Required).
UDS Indicates the beginning of user defined subroutine section.

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.

Main Index
 262 BEGIN BULK (Case)
Case Control and Bulk Data Delimiter

3. Partitioned Bulk Data Sections defined by BEGIN SUPER are used to define only one
superelement each. Bulk Data commands which define 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.
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, or 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.

Main Index
 BOUTPUT (Case) 263
Line Contact or 3D Contact Output Requests

BOUTPUT (Case) Line Contact or 3D Contact Output Requests

Selects contact regions for output.

Format:
 ALL 
 
BOUTPUT ( SORT1 , PRINT, PUNCH ) =  n 
SORT2 PLOT  
 NONE 

Examples:
BOUTPUT=ALL
BOUTPUT=5

Describer Meaning
SORT1 Output is presented as a tabular listing of slave 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 slave node.
PRINT The print file is the output media.
PUNCH The punch file is the output media.
PLOT Output histories for slave nodes are generated by not printed.
ALL Histories of all the slave 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 slave 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 slave 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 slave nodes in that contact region are output.
NONE Result histories for slave nodes are not calculated or output.

Remarks:
1. BOUTPUT is processed in SOLs 101, 106, 129, 153, 159, 400, and 600 only.
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.

Main Index
 264 BSQUEAL (Case)
Brake Squeal Analysis Data Selection

BSQUEAL (Case) Brake Squeal Analysis Data Selection

Selects data for brake squeal analysis in SOL 400.

Format:
BSQUEAL= n

Example:
BSQUEAL=10

Describer Meaning
n Set identification number of a BSQUEAL Bulk Data entry (Integer > 0).

Remark:
This command is used only in SOL 400 for brake squeal analysis with 3D Contact.
This command is not available with segment-to-segment contact.

Main Index
 CAMPBELL (Case) 265
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. 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
 266 CLOAD (Case)
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), pg. 536) 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
 CMETHOD (Case) 267
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, pg. 958, to perform complex eigenvalue analysis in
SOL 106.

Main Index
 268 CMSENRGY (Case)
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 
   NONE   NONE 
RESPONSE =  MODAL  , CMSE =   , CMKE =   ,
   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
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates modal fractions for the requested set, but no printer output.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output.
PHASE Requests polar format (magnitude and phase) of complex output.
ESORT Keyword selecting one of the output sorting options: MODE, ASCEND, or
RATIO.
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.

Main Index
 CMSENRGY (Case) 269
Component Modal Synthesis Energy Output Request

Describer Meaning
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. Both PRINT and PUNCH may be requested.
3. ESORT, FILTER, and TOPN describers apply only to QSET results output. TOTAL results
output is always in increasing order of superelement ID number.
4. 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.
5. 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.

Main Index
 270 CMSENRGY (Case)
Component Modal Synthesis Energy Output Request

6. 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.
7. 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
 CSSCHD (Case) 271
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
 272 DATAREC (Case)
Data Recovery Output for p-Version Elements

DATAREC (Case) Data Recovery Output for p-Version Elements

Requests form and type of output for p-version elements.

Format:

DATAREC ( SORT1 ) = n
SORT2

Example:
DATAREC=12

Describer Meaning
SORT1 Output will be presented as a tabular listing of grid point results per loadcase.
SORT2 Output will be presented as a tabular listing of loadcase per grid point.
n SID of OUTPUT Bulk Data entry to be used. Only displacements, stresses,
and strains of p-version elements with identification numbers that appear on
the OUTPUT Bulk Data entry with SID=n will be output (Integer > 0).

Remarks:
1. DATAREC is processed only when an adaptive analysis is requested.
2. Only one command per subcase is allowed.
3. This information is used only for output control and does not affect the analysis.
4. Displacements, stresses, and strains will be calculated and printed only for p-version elements on
OUTPUT Bulk Data entries. Those elements listed that are not p-version elements will be
ignored.
5. The coordinates of the view points (points at which the displacements are calculated and printed)
can be printed by using the VUGRID command.

Main Index
 DBSAVE (Case) 273
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)
Default saving datablocks of advanced nonlinear elements at the end of each
loadcase
-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

Main Index
 274 DBSAVE (Case)
Saving Control Parameter of Datablocks for Advanced Nonlinear Elements

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
 DEACTEL (Case) 275
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 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
 276 DEFORM (Case)
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
 DESGLB (Case) 277
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.

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, or FATIGUE). The
DESGLB command must be used when applying constraints to FRMASS, WMPID or 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
 278 DESMOD (Case)
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 toolkit application.

Format:
DESMOD=name

Examples:
DESMOD=FLUTTER

Describer Meaning
Name User-specified name to designate the model. (Character)

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, the toolkit manager 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.

Main Index
 DESOBJ (Case) 279
Design Objective

DESOBJ (Case) Design Objective

Selects the DRESP1 or DRESP2 entry to be used as the design objective.

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 or DRESP2 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.

Main Index
 280 DESSUB (Case)
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.

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 and FATIGUE response using the DESSSUB
command. Use the DESGLB command instead.

Main Index
 DESVAR (Case) 281
Design Variable Selection

DESVAR (Case) Design Variable Selection

Selects a set of DESVAR entries for the design set to be used.

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
 282 DISPLACEMENT (Case)
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:

DISPLACEMENT ( SORT1 , PRINT, PUNCH , REAL or IMAG PSDF, ATOC, CRMS ,

SORT2 PLOT PHASE RALL
RPRINT TM = f RM = f
, RPUNCH , CID, -------------------------------------------------------- , --------------------------------------------------------- ,
NORPRINT T1 = f, T2 = f, T3 = f R1 = f , R2 = f, R3 = f
 ALL 
    
[CONNECTOR = ALL , [TRMC=  ALL   =  n 
m  setid    
 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 (TRMC=100) = 101

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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, displacement data.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of
either REAL or IMAG yields the same output.

Main Index
 DISPLACEMENT (Case) 283
Displacement Output Request

Describer Meaning
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 8.
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 8.
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 8.
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 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 Requests printing of output coordinate system ID in printed output file, (.f06).
TM Translational magnitude filter. See Remark 10.
T1, T2, T3 Translational component filters. See Remark 10.
RM Rotational magnitude filters. See Remark 10.
R1, R2, R3 Rotational component filters. See Remark 10.
F Filter value (Real > 0.0). See Remark 10.
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 the right side of the DISP command is defined as NONE, then no points
will be output even if the user has defined the keyword CONN=ALL or
CONN=m.

Main Index
 284 DISPLACEMENT (Case)
Displacement Output Request

Describer Meaning
If the right side of the DISP command is defined as 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, then to avoid having to define a previously appearing m SET
command with all connectors listed, the user may define 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.
TRMC Selects a set of trim components for output. The default is NONE. See
Remark 13..

TRMC=ALL: Output the solution results from all trim components involved
in the analysis by Case Control command, TRIMGRP.

setid is the identification of a trim component set, defined by a previously

appearing SET command. (Integer>0).

Remarks:
1. Both PRINT and PUNCH may be requested.
2. 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
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!
3. VECTOR and PRESSURE are alternate forms and are equivalent to DISPLACEMENT. In
complex analysis, the pressure is ALWAYS magnitude-phase.
4. DISPLACEMENT=NONE overrides an overall output request.
5. The PLOT option is used when curve plots are desired in the magnitude/phase representation and
no printer output request is present for magnitude/phase representation.

Main Index
 DISPLACEMENT (Case) 285
Displacement Output Request

6. The units of translation are the same as the units of length of the model. Rotations are in units of
radians.
7. Displacement results are output in the global coordinate system (see field CD on the GRID Bulk
Data entry).
8. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.
9. 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.
10. 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
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

Main Index
 286 DISPLACEMENT (Case)
Displacement Output Request

C4 = (C1 + C2)/2
C5 = (C1 - C2)/2
Then,
TM (or RM) = C4 + SQRT (C5**2 + C3**2)
11. 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.
12. The selected trim components must be specified by TRIMGRP for the analysis. Since the same
grid point identifications can be shared by several trim components as well as the structure/cavity,
unintentional output could happen.
13. TRMC subcommand should be used to identify the IDs of trim component for which data
recovery operation is requested. The interface grid IDs of trim components that data recovery is
desired should be included in the set n of the request.

Main Index
 DIVERG (Case) 287
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
 288 DLOAD (Case)
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
 DRSPAN (Case) 289
Response Spanning Set Selection

DRSPAN (Case) Response Spanning Set Selection

Selects a set of DRESP1 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 responses that span
subcases if these DRESP1 responses have been identified using a DRSPAN Case Control
command that references a SET request that identifies the DRESP1 Bulk Data entries.
2. Each DRESP1 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. DRESP2, or DRESP3 that SPANS subcases, cannot reference another DRESP2 and/or DRESP3.
5. DRSPAN must appear in every subcase in the file if the synthetic response is to span the subcases.
The synthetic response via DRESP2 or DRESP3 must reference all DRESP1 IDs defined in SETs
of DRSPAN. In DEQATN, all DRESP1 IDs should show up in the list of variables. For those
DRESP1 IDs that are not needed, it can be dropped from the definition of equation(s).
6. To check the value of spanned response, set parameter P2 of DOPTPRM to a value equal to or
larger then 8, see DOPTPRM for details. Note that verification requires performing hand
calculation based on user-provided DEQATN for the spanned response.

Main Index
 290 DSAPRT (Case)
Design Sensitivity Output Parameters

DSAPRT (Case) Design Sensitivity Output Parameters

Specifies design sensitivity output parameters.

Format:

FORMATTED ALL
NOEXPORT , START = i, BY = j, END = k
DSAPRT UNFORMATTED , = 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
 DSAPRT (Case) 291
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
 292 DSYM (Case)
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
AS, AA to 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
 ECHO (Case) 293
Bulk Data Echo Request

ECHO (Case) Bulk Data Echo Request

Controls echo (i.e., printout) of the Bulk Data.

Format:
 
 SORT ( [ EXCEPT ]cdni,... )  SORT  
 
ECHO =  UNSORT , PUNCH  BOTH  , FILE 
 
 BOTH  NEWBULK 
 
 NONE 

Examples:
ECHO=NOSORT
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
 294 ECHO (Case)
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, ECHOOF 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
 EDE (Case) 295
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.

Format:
AVERAGE  ALL 
PRINT, PUNCH  
EDE ( AMPLITUDE [ THRESH = p ] ) =  n 
PLOT  
PEAK  NONE 

Examples:
EDE=ALL
EDE(PUNCH, THRESH=.0001)=19

Describer Meaning
PRINT Write energy values to the print file.(Default).
PUNCH Write energy values to the punch file.
PLOT Do not write energy values to either the punch file or the print file.
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).
ALL Energy 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 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.

Main Index
 296 EDE (Case)
Element Energy Loss Per Cycle Output Request

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.
{ u r }= displacement (real part).
{ u i }= displacement (imaginary part).
[ B e ]= 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.

Main Index
 EKE (Case) 297
Element Kinetic Energy Output Request

EKE (Case) Element Kinetic Energy Output Request

Requests the output of the kinetic energy in selected elements.

Format:
AVERAGE  ALL 
PRINT, PUNCH  
EKE ( AMPLITUDE [ THRESH = p ]) =  n 
PLOT  
PEAK  NONE 

Examples:
EKE=ALL
EKE(PUNCH, THRESH=.0001)=19

Describer Meaning
PRINT Writes energy values to the print file (Default).
PUNCH Writes energy values to the punch file.
PLOT Do not write energy values to either the punch file or the print file.
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).
ALL Kinetic energy 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 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

Main Index
 298 EKE (Case)
Element Kinetic Energy Output Request

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.
{ vr } = velocity (real part).
{ vi } = velocity (imaginary part).
[ Me ] = 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.

Main Index
 ELSDCON (Case) 299
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
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.
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
 300 ELSENS (Case)
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:
ELSENS ( [ PRINT , PUNCH / PLOT] , [ REAL or IMAG / PHASE ] , [ THRESH = p ] ,
RESPONSE = r ,[ SOLUTION = { ALL / setf }] , [ MASS , STIFF
, DYNAMIC , SQMASS ,
SQSTIFF , SQDYNA] ) = { ALL / 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
PRINT Writes sensitivities to the print file (Default).
PUNCH Writes sensitivities to the punch file.
PLOT Do not write sensitivities to either the print file or punch file.
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.
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.

Main Index
 ELSENS (Case) 301
Element Sensitivity Output for SOL 108/111

Remarks:
1. Set r for RESPONSE has no default.
2. The equations various options of ELSENS

ELSENS(MASS) = [Asetf]t[Melem][Ar]

ELSENS(STIFF) = [Usetf]t[Kelem][Ur]

ELSEND(DYNAMIC) = [Asetf]t[Melem][Ar] + [Usetf]t[Kelem][Ur]

ELSENS(SQMASS) = [Asetf]t[Melem][Ar] + [Asetf]*t[Melem]* [Ar]*

ELSENS(SQSTIF) = [Usetf]t[Kelem][Ur] + [Usetf]*t[Kelem]* [Ur]*

ELSEND(DYNAMIC) = [Asetf]t[Melem][Ar] + [Usetf]t[Kelem][Ur] +

[Asetf]*t[Melem]* [Ar]* + [Usetf]*t[Kelem]* [Ur]*

where [Usetf] is the displacement of SOLUTION

[Asetf] is the acceleration of SOLUTION
[Ur] is the displacement of RESPONSE
[Ar] is the acceleration of RESPONSE
[Kelem] is element stiffness matrix
[Melem] is element mass matrix
superscript * means complex conjugate of the term.

Main Index
 302 ELSUM (Case)
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.
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,

Main Index
 ELSUM (Case) 303
Element Summary Output Request

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.

Main Index
 304 ENDSTEP (Case)
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
 ENDTIME (Case) 305
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
 306 ENTHALPY (Case)
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 
 
ENTHALPY ( SORT1 , PRINT, PUNCH ) =  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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, enthalpies.
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
 EQUILIBRIUM (Case) 307
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
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, equilibrium force balance data block.
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.
2. Results are always output in the basic coordinate system.
3. The EQUILIBRIUM Case Control command is applicable to static analysis only, and does not
produce output if any superelements are present.

Main Index
 308 ERP (Case)
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  
ERP  , SOLUTION =  setf  ,
 SORT1 PLOT  
  sett 

 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

Describer Meaning
SORT1 Output is presented as a tabular listing of ERP panels for each frequency.
SORT2 Output is presented as a tabular listing of frequency for each ERP panel.
PRINT Output is written to the .f06 file
PUNCH Output is written to the .pch file
PLOT Results are computed and placed on the ERP table but not output.
SOLUTION Keyword to select frequencies 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.

Main Index
 ERP (Case) 309
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 total ERP. 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 total ERP exceeds the filter value.
ERPRHO Fluid density for Equivalent Radiated Power (ERP) analysis. This item is actually an
MSC Nastran parameter.
ERPC Phase speed of the fluid for Equivalent Radiated Power (ERP) analysis. This item is
actually an Nastran parameter.
ERPRLF Radiation loss factor. In frequency the scale factor C = ERPRLF * (½ERPRHO *
ERPC). In transient the scale factor C = ERPRLF * (ERPRHO * ERPC).
RHOCP Scale factor used in dB computation. This item is actually an MSC Nastran parameter.
ERPREFDB Scale factor used in dB computation. This item is actually an MSC Nastran parameter.
ERP
The dB calculation is ERPdB = 10 log  RHOCP ⋅ -----------------------------
- .

ERPREFDB

CSV Results will be written to a .csv file.

unit Unit of the .csv file as used on the required ASSIGN statement.
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.
2. Output is generated in SORT2 by default. Unlike other Case Control requesting SORT2 format,
the ERP command does not force all other output into SORT2 format.
3. FILTER has no effect on PUNCHed, CSV or OP2 output.
4. In addition to individual panel output a summary named ALLPANEL is produced. If there are
multiple subcases, the panel name is formed from the serial subcase number (1-nsubc) and the
characters ‘ALLP’ as in ALLP0002 unless the ERP command request output for ALL panels
across the Subcases. In this case, the summary panel name ALLPANEL is retained.
5. Selectable frequencies are dependent on the presence of an OFREQ Case Control command.
6. ERPRHO, ERPC, ERPRLF, RHOCP, and ERPREFDB are actually PARAM,name,value entries.
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.

Main Index
 310 ERP (Case)
Equivalent Radiated Power Panel Participation Factor Output Request

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

Main Index
 ESE (Case) 311
Element Strain Energy Output Request

ESE (Case) Element Strain Energy Output Request

Requests the output of the strain energy in selected elements.

Format:
AVERAGE
PRINT, PUNCH  
ESE ( AMPLITUDE [ THRESH = p ] ) =  ALL 
PLOT  n 
PEAK

Examples:
ESE=ALL
ESE (PUNCH, THRESH=.0001)=19

Describer Meaning
PRINT Writes energies to the print file (Default).
PUNCH Writes energies to the punch file.
PLOT Do not write energies to either the punch file or the print file.
AVERAGE Requests average energy in frequency response analysis only.
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).
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.
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

Main Index
 312 ESE (Case)
Element Strain Energy Output Request

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:
E peak = E o + E a

where:

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.
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τ (4-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. (4-10). If we assume a linear variation of
temperatures from subcase to subcase, then the strain energy in Eq. (4-10) for the special case of
linear material and geometry becomes

Main Index
 ESE (Case) 313
Element Strain Energy Output Request

E = 1 1 T
T
--- u K e u – --- u P et (4-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 (4-12)
2

where P et is the element load vector for temperature differences and element deformation.
In Eq. (4-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. (4-11), set the parameter XFLAG to 2; the default value for XFLAG is 0, which uses Eq.
(4-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. The advanced elements are not supported in ESE.

Main Index
 314 EXPORTLD (Case)
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:

Example Results
EXPORTLD LOADID=subcase ID, LOADNAME=’ ‘ -
default value applied.
EXPORTLD(LOADID=12) LOADID=12, LOADNAME=’ ‘

Main Index
 EXPORTLD (Case) 315
Saves a Load Vector on the Database for Subsequent Reuse

Example Results
EXPORTLD(LOADID=1,LOADNAME= LOADID=1, LOADNAME=’FORCE12’
FORCE12)
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
 316 EXTSEOUT (Case)
External Superelement Creation Specification

EXTSEOUT (Case) External Superelement Creation Specification

Format:


EXTSEOUT  STIFFNESS MASS DAMPING K4DAMP LOADS FSCOUP



 MAN 
 
ASMBULK =  MANQ  EXTBULK EXTID = seid
 
 AUTO 

 
 MATDB (or MATRIXDB) 
 DMIGDB 
  
DMIGSFIX =  cccccc   DMIGOP2 = unitop 2 
 EXTID   
 DMIGPCH 
 MATOP4 (or MATRIXOP4) = unitop 4 
 

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)
(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.
LOADS Store the boundary static loads matrix. See Remark 1.
FSCOUP Store the boundary fluid-structure coupling matrix. See Remark 1.

Main Index
 EXTSEOUT (Case) 317
External Superelement Creation Specification

Describer Meaning
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., 4., 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.
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.

Main Index
 318 EXTSEOUT (Case)
External Superelement Creation Specification

Describer Meaning
MATDB Store the boundary matrices and other information on the database. See
(or MATRIXDB) Example 1 in Remark 18.
(Default)
DMIGDB Similar to MATDB (or MATRIXDB) except that the boundary matrices
are stored as DMIG Bulk Data entries on the database. See Example 1 in
Remark 18.
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). 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.

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.

Main Index
 EXTSEOUT (Case) 319
External Superelement Creation Specification

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
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.
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

Main Index
 320 EXTSEOUT (Case)
External Superelement Creation Specification

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)
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.

Main Index
 EXTSEOUT (Case) 321
External Superelement Creation Specification

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).
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.
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.
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.

Main Index
 322 EXTSEOUT (Case)
External Superelement Creation Specification

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, and element stresses 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.
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.
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.

Main Index
 EXTSEOUT (Case) 323
External Superelement Creation Specification

Example 1. MATDB / MATRIXDB or DMIGDB Option

• External SE Creation Jobs
• Case Control Requirement for the MATDB / MATRIXDB option
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
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.
• Assembly Job
• File Management Section (FMS) Requirement
ASSIGN dbname10=’extse10.MASTER’
ASSIGN dbname20=’extse20.MASTER’
ASSIGN dbname30=’extse30.MASTER’
DBLOCATE DATABLK=(EXTDB) CONVERT(SEID=10)
LOGICAL=dbname10
DBLOCATE DATABLK=(EXTDB) CONVERT(SEID=20)
LOGICAL=dbname20
DBLOCATE DATABLK=(EXTDB) 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.)
• 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
 324 EXTSEOUT (Case)
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 since there is no need for the
databases to be saved at the end of the jobs.
• 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
• 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
 EXTSEOUT (Case) 325
External Superelement Creation Specification

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,
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)
• 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
 326 EXTSEOUT (Case)
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 since there is no need for the
databases to be saved at the end of the jobs.
• 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
• 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
 FATIGUE (Case) 327
Fatigue Output Request

FATIGUE (Case) Fatigue Output Request

Requests one or more fatigue analyses for use in pseudo-static (SOL 101), modal (SOL 103) and modal
transient (SOL 112) runs.

Format:

 
FATIGUE ( SORT1 , PRINT, PUNCH , FORMAT = [ CODE ], BULK ) =  n 
SORT2 PLOT SET  

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 block 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 block is always in SORT1
format.
PRINT The printer will be the output medium (default)
PUNCH The PUNCH file will be the output medium.
PLOT Results will be generated but no printer output.
FORMAT Request that fatigue be output in specific file formats.
CODE Codes for specific file format output. See Remark 7.
BULK Specifies that the n refers directly to bulk data IDs of FTGSEQ/ FTGLOAD,
FTGPARM and FTGDEF entries of the same ID (default)
SET Specifies that the n refers to a previously appearing set ID.
n ID of a SET case control entry (SET option) or ID of FTGSEQ/FTGLOAD,
FTGPARM, FTGDEF bulk data entries of the same ID (BULK option)

Remarks:
1. Both PRINT and PUNCH may be requested.

Main Index
 328 FATIGUE (Case)
Fatigue Output Request

2. A single FATIGUE case control is required to perform one or more 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.
3. 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.
4. For a single fatigue analysis, BULK=n points to a FTGDEF, a FTGPARM, and a FTGSEQ (or
FTGLOAD) entry, each with ID=n.
5. 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.
6. 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.
7. 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 will be generated with _top or _bottom designations in the name. If you wish to have
only a single file with the results of the worst layer only, add 10,000 to the CODE. Using the
above example would give 10192.
• Some output is not available for duty cycle jobs if EVNTOUT>0 on the FTGSEQ bulk data
entry. Check messages if the f06 file if the requested output files are not being generated.

File Format CODE

No additional output 0
FER (Design Life Output File) 4
HYP (HyperMesh Results File) 8
UNV (Universal File) 32
CSV File (Comma Separated - Excel File) 64
FEF (Patran Results File) 128
Worst Case Output - worst case (layer) output will be created for any 256
of the HYP,UNV,CSV, and FEF files, other wise all layer data is
written to multiple files.

8. 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.

Main Index
 FATIGUE (Case) 329
Fatigue Output Request

9. 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

*User units are fatigue equivalent units as defined on the FTGSEQ or FTGLOAD en-
try and other output is available depending on the settings of the FTGPARM entry.
Please see those entries for more detail.
†Depending on FTGPARM flag used.

Main Index
 330 FBODYLD (Case)
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
 FLSFSEL (Case) 331
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.
FLUIDSE Defines a specified superelement to be used for fluids only.
seidf Defines a fluid only superelement.

Main Index
 332 FLSFSEL (Case)
Control for Fluid-Structure Frequency Selection

Remarks:
1. This entry represents a collection of PARAM,name,value entries. See Parameters, pg. 707 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 (Ch. 5) 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
 FLSPOUT (Case) 333
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
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.

Main Index
 334 FLSPOUT (Case)
Control for Fluid-Structure Mode Participation Output

Describer Meaning
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.
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.

Main Index
 FLSPOUT (Case) 335
Control for Fluid-Structure Mode Participation Output

Describer Meaning
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, pg. 707 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 (Ch. 5) 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, pg. 1075).

Main Index
 336 FLSTCNT (Case)
Miscellaneous Fluid-Structure Control Parameters

FLSTCNT (Case) Miscellaneous Fluid-Structure Control Parameters

Control for fluid-structure symmetry and force requests.

Format:
 YES   PEAK 
FLSTCNT ACSYM =  -----------  , ACOUT =  --------------- 
 NO   RMS 

 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 Requests peak value output to be used with the FORCE request.
RMS 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.
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.

Main Index
 FLSTCNT (Case) 337
Miscellaneous Fluid-Structure Control Parameters

Remarks:
1. This entry represents a collection of PARAM,name,value entries. See Parameters, pg. 707 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.

Main Index
 338 FLUX (Case)
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
PRINT The printer will be the output medium.
PUNCH The punch file .pch will be the output medium.
PLOT The output will be sent to the plot file.
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
 FMETHOD (Case) 339
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
 340 FORCE (Case)
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.
PLOT Generates force output for requested set, but no printed output.
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.
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.
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.

Main Index
 FORCE (Case) 341
Element Force Output or Particle Velocity Request

Describer Meaning
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.
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.
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 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2.
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.

Main Index
 342 FORCE (Case)
Element Force Output or Particle Velocity Request

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.
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.
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.

Main Index
 FREQUENCY (Case) 343
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
where DFREQ is a user parameter with a default of 10 – 5 . 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.

Main Index
 344 FRF (Case)
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 

 
 COMP 
 UNIT   
   ALL   STD 
 UNITALL   ASSEMBLY   
[ CONNPTS = setid ] XITOUT =   ASMOUT =   LOADLBL =  ALT 
 USER   CONNINFO   
 USERTOTL     ALTX 
   n 
 
 cname 

 DB  
  
 OP2 = unit  


 ALL  
  
ICFGEN=  n  
  
 compname  
  ICFDB 
 n   =  
ICFUSE=     ICFOP2={icfunit } 
 compname  


 n  
ICFAUTO=   
  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)

Main Index
 FRF (Case) 345
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification

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.
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
 346 FRF (Case)
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
 FRF (Case) 347
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.
DB Store the FRF matrices and other information on the database. See
(Default) Examples 2 and 4 in Remark 13.

Main Index
 348 FRF (Case)
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification

Describer Meaning
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 specified by SET ID

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 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
 FRF (Case) 349
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 in the FBA process only for
that single FRF component whose ID is given by |n|.
ICFAUTO = compname only for that 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.

Main Index
 350 FRF (Case)
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification

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.
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.

Main Index
 FRF (Case) 351
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification

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.
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.

Main Index
 352 FRF (Case)
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
• 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.
• 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’

Main Index
 FRF (Case) 353
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 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
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’

Main Index
 354 FRF (Case)
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.
• 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’
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
 FRF (Case) 355
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
 356 FRF (Case)
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’

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

Main Index
 FRF (Case) 357
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
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
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).

Main Index
 358 FRF (Case)
Frequency Response Function (FRF) Generation and/or FRF Based Assembly (FBA) Specification

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.

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
 GPFORCE (Case) 359
Grid Point Force Output Request

GPFORCE (Case) Grid Point Force Output Request

Requests grid point force balance at selected grid points.

Format:
PRINT, PUNCH  
GPFORCE =  ALL 
PLOT  n 

Examples:
GPFORCE=ALL
GPFORCE=17

Describer Meaning
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
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
CROD
CBEAM
CSHEAR
CONROD
CTRIA3
CQUAD4
CTUBE

Main Index
 360 GPFORCE (Case)
Grid Point Force Output Request

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, 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:

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

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 108 or 111.
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. SOL 129 does not support GPFORCE. 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 advanced elements are not supported in GPFORCE.

Main Index
 GPKE (Case) 361
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

where Φ mass
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.
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
 362 GPRSORT (Case)
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
 GPSDCON (Case) 363
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
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
 364 GPSTRAIN (Case)
Grid Point Strain Output Request for Printing Only

GPSTRAIN (Case) Grid Point Strain Output Request for Printing Only

Requests grid point strains for printing only.

Format:
 ALL 
 
GPSTRAIN PRINT, PUNCH =  n 
PLOT  
 NONE 

Examples:
GPSTRAIN=ALL
GPSTRAIN=19

Describer Meaning
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 2 under DISPLACEMENT (Case), pg. 282 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.
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
 GPSTRESS (Case) 365
Grid Point Stress Output Request for Printing Only

GPSTRESS (Case) Grid Point Stress Output Request for Printing Only

Requests grid point stresses for printing only.

Format:
 ALL 
 
GPSTRESS PRINT, PUNCH =  n 
PLOT  
 NONE 

Examples:
GPSTRESS=ALL
GPSTRESS=19

Describer Meaning
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 2 under DISPLACEMENT (Case), pg. 282 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 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
 366 GROUNDCHECK (Case)
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 =  YES 
 NO 
GRID = gid, THRESH = e,DATAREC = YES , ( RTHRESH = r ))
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.
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.

Main Index
 GUST (Case) 367
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
 368 GVECTOR (Case)
G-Set Eigenvector Output Request in SOLs 200 and 400

GVECTOR (Case) G-Set Eigenvector Output Request in SOLs 200 and 400

Requests the form and type of g-set eigenvector output in SOLs 200 and 400.

Format:
 ALL 
 
GVECTOR [ ( PRINT, PUNCH ) ] =  n 
 
 NONE 

Examples:
GVECTOR=ALL
GVECTOR(PUNCH)=NONE

Describer Meaning
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
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. Both PRINT and PUNCH may be requested.
2. GVECTOR=NONE overrides an overall output request.
3. Output will be presented as a tabular listing of grid points for each eigenvector.
4. GVECTOR is intended to specified in subcases with ANALYSIS=MFREQ, MTRAN, MCEIG,
FLUTTER, and SAERO.

Main Index
 HADAPT (Case) 369
Mesh Adaptivity Activation and Control

HADAPT (Case) Mesh Adaptivity Activation and Control

Specifies Mesh adaptivity control parameters in SOLs 101 and 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.
HADPAT cannot be used in Linear Contact Analyses.
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, pg. 2136 and HADAPTL, pg. 2139). 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 not be used with quadratic elements with deleted mid-side nodes,
i.e., CHEXA element with 9 to 19 nodes or CTETRA element with 5 to 9 nodes. Remeshing of
these elements produces inaccurate results. Note that using a subset of these elements for any
analysis is not recommended.
5. The implementation of h-adaptivity uses dynamic memory from open core that cannot be
estimated at the beginning at a job run. A user needs to make sure sufficient memory is assigned
or use the MEMORY=MAX command line option.

Main Index
 370 HARMONICS (Case)
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
 HDOT (Case) 371
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 
 
HDOT ( SORT1 , PRINT, PUNCH ) =  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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, rate of change of enthalpy.
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
 372 HISTOGRAM (Case)
Fatigue Histogram/Time History Output Request

HISTOGRAM (Case) Fatigue Histogram/Time History Output Request

Requests resultant stress/strain time history and/or rainflow cycle histogram output from entities defined
by a FATIGUE case control output request.

Format:

BOTH  ALL 
 
HISTOGRAM ( HIST , FORMAT = [CODE] ) =  n 
 
TIME  NONE 

Examples:
SET 99 = 100,101
HISTOGRAM(TIME,FORMAT=ASCII)= 99

Describer Meaning
BOTH Both time histories and histograms are output (Default).
HIST Only histograms are output.
TIME Only time histories are output.
FORMAT Specifies the output file format of the time history and/or histogram files. Valid values
of CODE are ASCII or BINARY. (Default: FORMAT=ASCII).
ALL Time histories and/or histograms of all entities associated with a FATIGUE case
control output request are output. See Remarks below.
n Time histories and/or histograms of only entities defined in a SET of ID n are output.
The entities must also be part of a FATIGUE case control output request.
NONE No histogram or time history output is processed.

Remarks:
1. If no FATIGUE case control is defined, this output request is ignored.
2. This output request has the potential to create many thousands of files if the ALL option is used.
A separate file for each time history and/or histogram for each entity is created. It is recommended
to specify a SET to limit the output.
3. If FORMAT=BINARY, file formats are DAC for time histories and S3M for histograms.
If FORMAT=ASCII, both time histories and histograms are output in CSV format.
4. File names produced by this option are cryptic and increment by the number of time histories or
histograms being processed. You must open each file to check for which element, node, and layer
it is associated with.

Main Index
 HISTOGRAM (Case) 373
Fatigue Histogram/Time History Output Request

5. This option is not supported for duty cycle analysis and will be ignored with no output generated.
Specifically this occurs when the FTGSEQ bulk data entry references more than one FTGEVNT
or more than one repeat of a single FTGEVNT entry.

Main Index
 374 HOUTPUT (Case)
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
 HTFLOW (Case) 375
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
 376 IC (Case)
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, 400 and 600).

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, 129, and
600) or TEMP and TEMPD entries for heat transfer analysis (SOLs 159 and 600).
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 (SOLs 159 and
600).
3. IC(MODAL) may be specified only in modal transient analysis (SOL 112).
4. IC(STATSUB) and IC(STATSUB,DIFFK) may not both be specified in the same 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
 IC (Case) 377
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

Main Index
 378 ICF (Case)
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   
ICF  , PRINT, PUNCH , REAL or IMAG  =  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 2. through 5.
SORT2 Output will be presented as a tabular listing of frequency for each grid point. See
Remarks 2., 4. and 6.
PRINT The printer will be the output medium. See Remark 1.
PUNCH The punch file will be the output medium. See Remark 1.
PLOT Generates, but does not print, ICFs.
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 2. through 6.
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 2. through 7.
NONE ICFs for no points will be output.

Remarks:
1. Both PRINT and PUNCH may be requested.
2. See Remark 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2. In
the SORT1 format, only nonzero values will be output.

Main Index
 ICF (Case) 379
Inter-Component Forces (ICF) Output Request

3. 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.
4. 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.
5. 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.
6. In SORT2 format, ICF output is honored for all requested connection and non-connection points
of FRF components even if their ICFs are null.
7. ICF output request is ignored for undefined points.

Main Index
 380 INCLUDE (Case)
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 MSC Nastran 2016 Installation and Operations Guide for more examples.

Main Index
 INTENSITY (Case) 381
Acoustic Intensity Output Request

INTENSITY (Case) Acoustic Intensity Output Request

Requests output of acoustic intensity on wetted surface. SOLs 108 and 111 only.

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.
PRINT The printer will be the output medium (Default).
PUNCH The punch file will be the output medium.
PLOT Results are generated but not output.
ALL Intensities will be computed for all grid points of the wetted surface.
n Set identification of a previously defined set of grid points. Intensities will be
computed for the grid points in this set only.
NONE Acoustic intensities will not be processed.

Remarks:
1. Both PRINT and PUNCH may be requested.
2. INTENSITY = NONE overrides an overall request.
3. The PLOT option is used if results are requested for postprocessing but no printer output is
desired.
4. This Case Control command can be used in SOL 108 and SOL 111 only.

Main Index
 382 IRLOAD (Case)
Nonlinear Inertia Relief Selection (SOL 400 only)

IRLOAD (Case) Nonlinear Inertia Relief Selection (SOL 400 only)

Selects nonlinear inertia relief set for SOL 400

 
Format: IRLOAD=  QLINEAR 
 NONE 

Example:
IRLOAD=QLINEAR

Field Contents
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
 K2GG (Case) 383
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
name Name of a [ K 2gg ] 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, pg.
707.
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
 384 K2PP (Case)
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
name Name of a [ K 2pp ] 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 (p. 353) in the MSC Nastran Reference Manual.
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
 K42GG (Case) 385
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
name Name of a [ K4 2gg ] 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
 386 LABEL (Case)
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
 LINE (Case) 387
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 nastran
Command and NASTRAN Statement, pg. 1.

Main Index
 388 LOAD (Case)
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
 LOADNAME (Case) 389
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
 390 LOADSET (Case)
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
 LOADSET (Case) 391
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
 392 M2GG (Case)
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
name Name of a [ M 2gg ] 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
 M2PP (Case) 393
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
name Name of a [ M 2pp ] 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 (p. 353) in the MSC Nastran Reference Manual.
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
 394 MASTER (Case)
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
 MASTER (Case) 395
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
 396 MAXLINES (Case)
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 does not override any system parameters such as those on job control language
commands.
3. MAXLINES may also be specified on the NASTRAN statement with SYSTEM(14). See the
nastran Command and NASTRAN Statement, pg. 1.
4. 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
 MAXMIN (Case) 397
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 = lisst = 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.

Main Index
 398 MAXMIN (Case)
MAXMIN Survey Output Request (old form)

Describer Meaning
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).

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
 MAXMIN (Case) 399
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  CENTER  ALL 

  PRINT, PUNCH VONMISES  
MAXMIN(  ELEM , ), , CUBIC , STRCUR =  n 
  NOPRINT MAXS or SHEAR SGAGE FIBER  
 BOTH   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.
CORNER or Output CQUAD4 element stress/strains at the center and grid points using
BILIN strain gage approach with bilinear extrapolation.

Main Index
 400 MAXMIN (Case)
Requests Output of Maximums and Minimums in Data Recovery (new form)

Describer Meaning
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
 MAXMIN(DEF) (Case) 401
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   CENTER 
   / ALL 
MAXMIN ( DEF )  STRAIN  { eltype1 [ , eltype2,... ] }  comp1 [ , comp2... ]  ,
   GROUP 
 FORCE   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

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

Main Index
 402 MAXMIN(DEF) (Case)
Defines Parameters for Monitoring Maximums and Minimums (new form)

Describer Meaning
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.
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, pg. 1003 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.
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.

Main Index
 MAXMIN(DEF) (Case) 403
Defines Parameters for Monitoring Maximums and Minimums (new form)

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 CQUAD4C and CTRIAC for corner stresses of CQUAD4 and CTRIA3 elements.
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
 404 MCFRACTION (Case)
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 
NULL =
12  =  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.
PRINT The printer will be the output medium.
PUNCH The punch file (.pch) will be the output medium.
PLOT Generate modal fractions for the requested set, but no printer output.
REAL or IMAG Requests rectangular format (real and imaginary) of complex output.
PHASE Requests polar format (magnitude and phase) of complex output.
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.

Main Index
 MCFRACTION (Case) 405
Modal Contribution Fractions Output Request

Describer Meaning
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.

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. Both PRINT and PUNCH may be requested.
3. Printed output includes results for all of the data items described in the itemlist table.
4. Punched output includes results for only the data items selected by the ITEMS keyword.

Main Index
 406 MCFRACTION (Case)
Modal Contribution Fractions Output Request

5. 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.
6. 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.
7. 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.
8. If the magnitude of the total response at a selected grid pint component is less than 1.0 × 10 –ipowr ,
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 1.0 × 10 – 12 .
9. 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.
10. 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
 MCHSTAT (Case) 407
Change State in SOL 600

MCHSTAT (Case) Change State in SOL 600

Indicates which MCHSTAT Bulk Data entry option will be used to control the state variables
(temperatures)used in this subcase for a thermal stress simulation in SOL 600.

Format:
MCHSTAT=N

Example:
MCHSTAT=10

Describer Meaning
N ID of a matching Bulk Data MSCHSTAT entry specifying temperatures or other
state variable values to be used from a previous analysis for this subcase.

Remark:
1. This entry may only be used in SOL 600.

Main Index
 408 MEFFMASS (Case)
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:
a. Modal effective mass matrix [ ε T ] [ m ] [ ε ]
where:

ε = Modal participation factors: [ m 1 ] [ φ T ] [ M aa ] [ D ar ] .

m = Generalized mass matrix.
φ = Eigenvectors.

Main Index
 MEFFMASS (Case) 409
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.

b. A-set rigid body mass matrix: [ D Ta r ] [ M a a ] [ 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 ε .
3. The MEFFM describer outputs the modal effective mass table ε 2 , 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
 410 METHOD (Case)
Real Eigenvalue Extraction Method Selection

METHOD (Case) Real Eigenvalue Extraction Method Selection

Selects the real eigenvalue extraction parameters.

Format:
BOTH
METHOD STRUCTURE = n
FLUID

Examples:
METHOD=33
METHOD(FLUID)=34

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
or FLUID fluid portion of the model.
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. See Additional
Topics (p. 515) in the .
• If METHOD(STRUCTURE) or METHOD(FLUID) is also specified, then they will override
the METHOD(BOTH) 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
(p. 390) in the MSC Nastran Reference Manual) 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.

Main Index
 MFLUID (Case) 411
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 Additional Topics (p. 515) in the .
2. Use parameter PARAM,VMOPT controls how the virtual mass is processed.

Main Index
 412 MODALKE (Case)
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  
 DESCENT 

   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).
MODES Compute energies for all modes or the set of mode numbers defined in SET n
(Default = ALL).
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.

Main Index
 MODALKE (Case) 413
Modal Kinetic Energy Request

Describer Meaning
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.

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.

Main Index
 414 MODALKE (Case)
Modal Kinetic Energy Request

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.

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.

Main Index
 MODALKE (Case) 415
Modal Kinetic Energy Request

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,
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.

[Fractional Kinetic Energy] = [Normalized Kinetic Energy]/[diagonal [ { 1.0 } T [Normalized
Kinetic Energy]]], term-by-term division.

Main Index
 416 MODALSE (Case)
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  
 DESCENT 

   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).
MODES Compute energies for all modes or the set of mode numbers defined in SET n
(Default = ALL).
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.

Main Index
 MODALSE (Case) 417
Modal Strain Energy Request

Describer Meaning
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.

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.

Main Index
 418 MODALSE (Case)
Modal Strain Energy Request

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.

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.

Main Index
 MODALSE (Case) 419
Modal Strain Energy Request

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:
1 T
[ Actual SE ] = --- { u h } [ M 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] = [Normalized Strain Energy]/[diagonal [ { 1.0 } T [Normalized
Strain Energy]]], term-by-term division.

Main Index
 420 MODES (Case)
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 =
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
 MODESELECT (Case) 421
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
MODESELECT  [ T1FR [ = t1fr ] ] [ T2FR [ = t2fr ] ] [ T3FR [ = t3fr ] ]
 FLUID
[ R1FR [ = r1fr ] ] [ R2FR [ = r2fr ] ] [ R3FR [ = r3fr ] ]
SUM
[ ALLFR [ = allfr ] ] [ UNCONSET = m ] ANYMIN
ALLMIN

See Remark 14. for examples illustrating the use of the preceding formats.

Main Index
 422 MODESELECT (Case)
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).

Main Index
 MODESELECT (Case) 423
Computed Mode Selection

Describer Meaning
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.
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.

Main Index
 424 MODESELECT (Case)
Computed Mode Selection

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.
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

Main Index
 MODESELECT (Case) 425
Computed Mode Selection

$ EXCLUDE STRUCTURE MODE 5 FROM THE ANALYSIS

MODESELECT = -5 $ (SET 5 NOT DEFINED)

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.

Main Index
 426 MODESELECT (Case)
Computed Mode Selection

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.
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 AND
will be selected.
Modes 20 and 30 will be selected regardless of their MEFFMFRA values.

Main Index
 MODTRAK (Case) 427
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).

Main Index
 428 MONITOR (Case)
Print Selection for Monitor Data

MONITOR (Case) Print Selection for Monitor Data

Specifies options in the printing of monitor data.

Format:
 ALL 
MONITOR [ REAL or IMAG, PHASE, NODSP1, NOPNT1, NOPNT2, NOPNT3 ] =  
 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 and 146.
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. MONITOR
commands in subcases subsequent to the first one are ignored.
4. MONPNT1 is not applicable in SOL 103.
5. Results for dynamic solutions (SOLs 108, 109, 111, 112, and 146) will be in SORT2 format. All
other solutions will be in SORT1 format.

Main Index
 MONITOR (Case) 429
Print Selection for Monitor Data

Output Format:
The output formats for complex energy in frequency response analysis follow.

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
 430 MPC (Case)
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
 MPCFORCES (Case) 431
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,IPSDF, 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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, multipoint constraint forces.
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.
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.
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.

Main Index
 432 MPCFORCES (Case)
Multipoint Forces of Constraint Output Request

Describer Meaning
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.
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.
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 3.
and 6.
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. Both PRINT and PUNCH may be requested.
2. See Remark 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2. In
the SORT1 format, only nonzero values will be output.
3. In a statics problem, a request for SORT2 causes loads at all points (zero and nonzero) to be
output.
4. MPCFORCES=NONE overrides an overall output request.
5. 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.
6. MPCFORCE results are output in the global coordinate system (see field CD on the GRID Bulk
Data entry).
7. MPCFORCE results are not available in SOL 129.
8. In inertia relief analysis, the MPCFORCE output includes both the effects of applied and inertial
loads.
9. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.

Main Index
 MPCFORCES (Case) 433
Multipoint Forces of Constraint Output Request

10. 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
 434 MPRES (Case)
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 
 
MPRES ( PRINT, PUNCH , REAL or IMAG ) =  n 
PLOT PHASE  
 NONE 

Examples:
MPRES=5
MPRES(IMAG)=ALL

Describer Meaning
PRINT The printer will be the output medium. (Default)
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print or punch, data.
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
 NLHARM (Case) 435
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
 436 NLIC (Case)
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.

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. For
perturbation analysis, NLIC can only be pointed to the loadstep in the same subcase.

Main Index
 NLIC (Case) 437
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 APPROACH=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
 438 NLLOAD (Case)
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
 NLOPRM (Case) 439
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.

Format:
NLOPRM = [ OUTCTRL = { STD,SOLUTION,INTERM } ]
 NONE 
 
  N3DBAS  
NLDBG =   
 NLBASIC,NRDBG,ADVDBG,  N3DMED  
  
  N3DADV  
NONE
 
 LTIME   NONE 
   
DBGPOST =  LSTEP  , MPCPCH =  BEGN,OTIME,STEP 
   
 LSUBC   TBEGN,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
INTERM Intermediate nonlinear solution output in OP2 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)

Main Index
 440 NLOPRM (Case)
Nonlinear Regular and Debug Output Control Parameters - SOL 400

Describer Meaning
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.
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. 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.
No No output (default)
Yes Select output

Main Index
 NLOPRM (Case) 441
Nonlinear Regular and Debug Output Control Parameters - SOL 400

Describer Meaning
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. For OUTCTRL = INTERM, the intermediate ouptut is is only available in OP2 file. .
3. For NLDBG, all nonlinear information is printed out in only F06 file.
4. For DBGPOST, all nonlinear information is printed out in the MASTER/DBALL.
5. For MPCPCH, it is a punch output that MPC and MPCY requests cannot be mixed.
6. In MPCPCH punch output, it is restricted that SID=1 for a general contact and SID=2 for the
glued contact.
7. 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.

Main Index
 442 NLPARM (Case)
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. For SOL 600, the only fields used are ID, NINC, DT (creep only), EPSU, EPSP, and EPSW. Use
PARAM,MARCOTIM instead of INTOUT. For other fields, advanced convergence controls are
available using the NLAUTO, NLSTRAT, and PARAM,MARCDEF Bulk Data entries.

Main Index
 NLRESTART (Case) 443
Nonlinear Restart Request

NLRESTART (Case) Nonlinear Restart Request

Request a RESTART execution at a specified point for SOL 400.

Format:

NLRESTART SUBCASE i , STEP j , LOADFAC f

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 = 0.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 0 ).

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.
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
TSTEPNL). 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).

Main Index
 444 NLRESTART (Case)
Nonlinear Restart Request

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. Nonlinear Restart is not supported in SOL 400 if advanced elements are used.

Main Index
 NLSTEP (Case) 445
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 TSTEPNL or both.
2. If a NLSTEP is present anywhere in a SUBCASE, then any NLPARM or TSTEPNL 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.)

Main Index
 446 NLSTRESS (Case)
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 
 
NLSTRESS ( SORT1 , PRINT, PUNCH , [ NLOUT = m ] ) =  n 
SORT2 PLOT  
 See Remark 4 

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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates nonlinear element stresses for requested set, but no printer output.
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)

Remarks:
1. Both PRINT and PUNCH may be requested.
2. ALL should not be used in a transient problem due to potentially excessive output.
3. See Remark 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2.
4. If there is a stress request, the default output set is that of the STRESS request.

Main Index
 NONLINEAR (Case) 447
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, 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
 448 NOUTPUT (Case)
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
 NSM (Case) 449
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
 450 OFREQUENCY (Case)
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.

Main Index
 OFREQUENCY (Case) 451
Output Frequency Set

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:
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
 452 OLOAD (Case)
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.
PRINT The printer will be the output medium. (Default)
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.
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.
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.
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.

Main Index
 OLOAD (Case) 453
Applied Load Output Request

Describer Meaning
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.
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 2. and 8.
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. Both PRINT and PUNCH may be requested.
2. See Remark 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2. In
the SORT1 format, only nonzero values will be output.
3. In a statics problem, a request for SORT2 causes loads at all requested points (zero and nonzero)
to be output.
4. OLOAD=NONE overrides an overall output request.
5. 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.
6. 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.
7. Loads generated by the SPCD Bulk Data entry do not appear in OLOAD output.
8. 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.
9. OLOAD results are output in the global coordinate system (see field CD on the GRID Bulk Data
entry).

Main Index
 454 OLOAD (Case)
Applied Load Output Request

10. In static inertia relief analysis, the OLOAD output includes both the inertia loads and applied
loads.
11. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.
12. 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.
13. OLOAD output is not available in SOL 600.

Main Index
 OMODES (Case) 455
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, 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
 456 OMODES (Case)
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.

Main Index
 OTIME (Case) 457
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
SET10 = . . .
DISP = ALL
SUBCASE 3
OTIME = 20
SET 20 = . . .
STRESS = ALL

Main Index
 458 OTIME (Case)
Output Time Set

5. The OTIME command is not effective in nonlinear transient analysis (SOL 129). However, the
OTIME command can be used in the nonlinear transient thermal analysis (SOL 159) to limit the
output to specified output times.
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
 OUTPUT (Case) 459
Case Control Delimiter

OUTPUT (Case) Case Control Delimiter

Delimits the various types of commands for the structure plotter, curve plotter, grid point stress, and
MSGSTRESS.

Format:
 
 PLOT 
 POST 
 
OUTPUT (  XYOUT  )
 
 XYPLOT 
 CARDS 
 

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, pg. 586.
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, pg. 586.
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, pg. 625.
CARDS The OUTPUT(CARDS) packet is used by the MSGSTRESS program. See the
MSGMESH Analyst’s Guide for details. These commands have no format rules.
This package must terminate with the command ENDCARDS (starting in
column 1).

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.

Main Index
 460 OUTRCV (Case)
P-element Output Option Selection

OUTRCV (Case) P-element Output Option Selection

Selects the output options for the p-elements defined on an OUTRCV Bulk Data entry.

Format:
OUTRCV=n

Examples:
OUTRCV=10
OUTR=25

Describer Meaning
n Set identification number of a OUTRCV Bulk Data entry (Integer > 0).

Remark:
1. The OUTRCV command is optional. By default, p-element output uses the defaults specified for
CID and VIEW as described in the OUTRCV Bulk Data entry description.

Main Index
 P2G (Case) 461
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
name Name of a [ P 2g ] 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, pg. 707.
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
 462 PACCELERATION (Case)
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:
PACCELERATION [ ( [ PRINT, PUNCH / PLOT ] , [ REAL or IMAG / PHASE ] ,
[ SOLUTION = { ALL / 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
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT The particle acceleration output will be generated but does not print.
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.

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
 PAGE (Case) 463
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
 464 PARAM (Case)
Parameter Specification

PARAM (Case) Parameter Specification

Specifies values for parameters. Parameters are described in Parameters, pg. 707.

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, pg. 1075.
2. The parameter values that may be defined in the Case Control Section are described in
Parameters, pg. 707. 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
 PARTN (Case) 465
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
 466 PFGRID (Case)
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 
   
SOLUTION =  setf  ) =  setdof 
   NONE 
 NONE 

Example:
SET 10 = 11217
SET 20 = 25., 30., 35.
PFGRID(PHASE, SOLUTION=20) = 10

Describer Meaning
PRINT Output will be written to the .f06 file (Default).
PUNCH Output will be written to the .pch file.
PLOT Results are computed but not output.
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 to be processed; the default is all
structural grid points.
setg Identifier of a set containing the identifiers of the structural grid points to be
processed.
SOLUTION Keyword selecting a set of excitation frequencies for which the participation
factors will be processed; default is all excitation frequencies.
setf Identifier of a set of excitation frequencies.
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, and PFGRID Case Control commands must reference the
same set of fluid degrees of freedom.
2. Acoustic grid participation factors are available in a coupled frequency response analysis
(SOL 108 and SOL 111).

Main Index
 PFGRID (Case) 467
Acoustic Grid Participation Factor Output Request

3. Both PRINT and PUNCH may be requested.

4. 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
 468 PFMODE (Case)
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 
   
PANELMP =  setp  , SOLUTION =  setf  , [ FILTER = fratio ],
   
 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

Describer Meaning
STRUCTURE Requests output of MPFs for the response of structural degrees of freedom.
See Remark 9. (Default).
FLUID Requests output of MPFs for the response of acoustic grid points (one degree
of freedom per point). See Remark 10.
PRINT Output will be written to the .f06 file. See Remarks 5. and 6. (Default).
PUNCH Output will be written to the .pch file. See Remarks 5. and 7.
PLOT Results are computed but not output.
PRTMSG Request generation of diagnostic messages for badly-defined output sets
during PF computations. These badly defined sets generally produce no
output. See Remark 16..

Main Index
 PFMODE (Case) 469
Modal Participation Factor (MPF) Output Request

Describer Meaning
SORT Keyword selecting the sort type. Default is sorting by increasing natural mode
number. See Remark 8.
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 8.
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:

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 8.
MODERESP Magnitude and phase relative to total response of modal
participation factors. See Remark 8.

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 10.
mf Number of lowest fluid modes for which MPFs will be computed. See
Remark 10.
STRUCTMP Keyword to select output of structural MPFs. See Remarks 9. and 10.
ms Number of lowest structural modes for which MPFs will be computed. See
Remarks 9. and 10.

Main Index
 470 PFMODE (Case)
Modal Participation Factor (MPF) Output Request

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. See Remark 11.
setf Identifier of a set of excitation frequencies. See Remark 11.
FILTER Keyword specifying the value of a filter to be applied to the printed output.
See Remark 12.
fratio Filter value (Default is 0.001). See Remark 12.
NULL Keyword specifying the power of ten used to detect a null response. See
Remark 13.
ipower Power of ten used to detect a null response (Default is 12). See Remark 13.
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.

Remarks:
1. All PFMODE(FLUID), PFPANEL, and PFGRID Case Control commands must reference the
same set of acoustic grid points.
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 a coupled modal frequency response analysis (SOL 111) only.
5. Both PRINT and PUNCH may be requested.
6. Printed output includes results for ALL the data items described in the Item List Table.
7. Punched output includes results for only the data items selected by the ITEMS keyword.
8. 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.
9. 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.
10. 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.

Main Index
 PFMODE (Case) 471
Modal Participation Factor (MPF) Output Request

11. 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.
12. The filter is applied to the real part of the normalized projected participation factors. Only
participation factors that pass the filter are output.
13. 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.
14. Acoustic panel MPFs are normalized using the panel response instead of the total response.
15. If present, output of acoustic structural MPFs includes the load participation factor. The load
participation factor has a mode number of 0 and a resonance frequency of 0.
16. 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
 472 PFPANEL (Case)
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
PFPANEL ( ----------------------------------- PRINT, PUNCH [ PRTMSG ] , REAL or IMAG , PANEL =  ALL 
STRUCTURE  
PLOT PHASE  setp 
,
 ALL 
[ SORT = sorttype ], [ KEY = sortitem ], ITEMS =   ,
 ( itemlist ) 

 ALL 
 
SOLUTION =  setf  , [ FILTER = fratio ], [ NULL = ipower ] )
 
 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

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.
PRINT Output will be written to the .f06 file (Default).
PUNCH Output will be written to the .pch file.
PLOT Results are computed but not output.
PRTMSG Request generation of diagnostic messages for badly-defined output sets
during PF computations. These badly defined sets generally produce no
output. See Remark 13..
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.

Main Index
 PFPANEL (Case) 473
Acoustic Panel Participation Factor Output Request

Describer Meaning
setp Identifier of a set of panels.
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:

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.
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 Selects a set of excitation frequencies for which the participation factors
will be processed; default is all excitation frequencies.
setf Identifier of a set of excitation frequencies.

Main Index
 474 PFPANEL (Case)
Acoustic Panel Participation Factor Output Request

FILTER Keyword specifying the value of a filter to be applied to the printed output.
fratio Filter value (Default is 0.001), see Remark 8.
NULL Keyword specifying the power of ten used to detect a null response, see
Remark 9.
ipower Power of ten used to detect a null response (Default is 12), see Remark 9.
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, and PFGRID Case Control commands must reference the
same set of fluid degrees of freedom.
2. Acoustic panel participation factors are available in a coupled frequency response analysis
(SOL 108 and SOL 111).
3. Both PRINT and PUNCH may be requested.
4. Printed output includes results for all the data items described in the itemlist table.
5. Punched output includes results for only the data items selected by the ITEMS keyword.
6. 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.
7. 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.
8. The filter is applied to the real part of the normalized projected participation factors. Only
participation factors that pass the filter are output.
9. 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.
10. If present, output includes the load participation factor. The panel name of the load participation
factors is –LOAD-.
11. The FLUID option selects panel PF calculation for acoustic grid points (one degree of freedom
per point) and setdof should be identification numbers.
12. The STRUCTURE option selects panel PF calculation for structure grid points and setdof should
be identification numbers and component codes.
13. 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
 PLOTID (Case) 475
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
 476 POST (Case)
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:
  furn  [ ppname ] [ oplist ]
POST  TOFILE   
 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).
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, pg. 707. 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.

ppname Product PARAM,POST,Value

PATRAN MSC Patran V3 -1
SDRC SDRC IDEA-S -2
NF MSC/LMS NF -4

Main Index
 POST (Case) 477
Postprocessor Data Specifications

ppname Product PARAM,POST,Value

FEMTOOLS DDS/FemTools -5
UNIGRAHICS EDS/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, pg. 707.
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, pg. 707 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
Element strains [NO]STRAIN STRAIN
Grid point stresses [NO]GPSTRESS GPSTRESS
Grid point strains [NO]GPSTRAIN GPSTRAIN
Applied loads [NO]LOAD OLOAD

Main Index
 478 POST (Case)
Postprocessor Data Specifications

Output Item oplist Keyword Case Command

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, pg. 707 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, pg. 707 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
 POST (Case) 479
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 (".").

Main Index
 480 PRESSURE (Case)
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), pg. 282.

Main Index
 RANDOM (Case) 481
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. P-elements are not supported in random analysis.
5. 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
 482 RCROSS (Case)
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), pg. 481 Case Control command description.

Main Index
 RCROSS (Case) 483
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
 484 REPCASE (Case)
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, 600, and 700.

Main Index
 RESVEC (Case) 485
Controls Residual Vectors

RESVEC (Case) Controls Residual Vectors

Specifies options for and calculation of residual vectors.

Format:
 
APPLOD ADJLOD DYNRSP 
RESVEC  INRLOD , , RVDOF , DAMPLOD ,

=
 NOINRL NOAPPL NOADJLOD NORVDO NODAMP NODYNRSP 

SYSTEM/NOSYSTEM
 
 COMPONENT/NOCOMPONENT 
 
 BOTH or YES 
 NO 

Examples:
RESVEC=SYSTEM
RESVEC(NOINRL)=COMPONENT
RESVEC=NO

Describer Meaning
INRLOD/ Controls calculation of residual vectors based on inertia relief (Default =
NOINRL INRLOD).
APPLOD/ Controls calculation of residual vectors based on applied loads (Default =
NOAPPL APPLOD).
ADJLOD/ NOADJLOD Controls calculation of residual vectors based on adjoint load vectors
(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
NODYNRSP dynamically 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
 486 RESVEC (Case)
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.

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.

Main Index
 RGYRO (Case) 487
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.

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
 488 RIGID (Case)
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, pg. 1070.

Main Index
 RIGID (Case) 489
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 and/or CFAST 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.
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. In SOL 400, if either or both of the Case Control
Commands EXTSEOUT and PARAM, EXTOUT are present, the Case Control Command
RIGID, must be set to LINEAR.

Main Index
 490 RSDAMP (Case)
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
 SACCELERATION (Case) 491
Solution Set Acceleration Output Request

SACCELERATION (Case) Solution Set Acceleration Output Request

Requests the form and type of solution set acceleration output.

Format:
 ALL 
 
SACCELERATION ( SORT1 , PRINT, PUNCH, REAL or IMAG ) =  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
2 under the DISPLACEMENT (Case), pg. 282 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
 492 SDAMPING (Case)
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:

SDAMPING ( STRUCTURE ) = n
FLUID

Example:
SDAMPING=77

Describer Meaning
STRUCTURE Modal damping is requested for the structural or fluid portion of the model.
or FLUID
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), SDAMPING must reference a TABLEDi
entry which defines viscoelastic (frequency-dependent) material properties. See Viscoelastic
Materials in Frequency Response Analysis (p. 908) in the MSC Nastran Reference Manual.
3. SDAMPING may be requested for superelements as long as PARAM,SESDAMP,YES is
specified.

Main Index
 SDISPLACEMENT (Case) 493
Solution Set Displacement Output Request

SDISPLACEMENT (Case) Solution Set Displacement Output Request

Requests the form and type of solution set displacement output.

Format:
 ALL 
 
SDISPLACEMENT ( SORT1 , PRINT, PUNCH, REAL or IMAG ) =  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
2 under the DISPLACEMENT (Case), pg. 282 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
 494 SEALL (Case)
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 (p. 408) in the MSC Nastran
Reference Manual.
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), pg.
496 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
 SEDAMP (Case) 495
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
 496 SEDR (Case)
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 (p. 408) in the MSC Nastran
Reference Manual.
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).

Main Index
 SEDV (Case) 497
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
 498 SEEXCLUDE (Case)
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

Main Index
 SEEXCLUDE (Case) 499
Superelement Matrix and Load Assembly Exclusion

then the user must specify the following commands in the Case Control Section:
SEKR = 30
PARAM,SERST,MANUAL

Main Index
 500 SEFINAL (Case)
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
 SEKREDUCE (Case) 501
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 (p. 408) in the MSC Nastran
Reference Manual.
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
 502 SELGENERATE (Case)
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 (p. 408) in the MSC Nastran
Reference Manual.
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
 SELREDUCE (Case) 503
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 (p. 408) in the MSC Nastran
Reference Manual.
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
 504 SEMGENERATE (Case)
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 (p. 408) in the MSC Nastran
Reference Manual.
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
 SEMREDUCE (Case) 505
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 (p. 408) in the MSC Nastran
Reference Manual.
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
 506 SERESP (Case)
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 Manual .
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
 SET (Case) 507
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.

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 = ALL

SET n = { i 1 ⁄ c 1 [ ,i 2 ⁄ c 2, i 3 ⁄ c 3, i 4 ⁄ c 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 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, or R3.
l 1, l 2 etc. Identification names of literals used for matrix or group selection.
i 1, i 2 etc. Identification numbers. If no such identification number exists, the request is
ignored (Integer > 0).

Main Index
 508 SET (Case)
Set Definition, General Form

Describer Meaning
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 Case Control command.
5. SET commands using literals apply only to direct matrix input such as K2PP etc. or FLSPOUT
panel grouping.

Main Index
 SETP (Case) 509
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).
SET identification numbers. If no such identification number exists, the request
is ignored (Integer > 0).
EXCEPT Set identification numbers following EXCEPT will be deleted from output list as
long as they are in the range of the set defined by the immediately preceding
THRU. An EXCEPT list may not include a THRU list or ALL.

Remarks:
1. A SETP command may be more than one physical command. A comma at the end of a physical
command signifies a continuation command. Commas may not end a set. THRU may not be used
for continuation—place a number after the THRU.
2. Set identification numbers following EXCEPT,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
 510 SETS DEFINITION (Case)
Case Control Processing Delimiter

SETS DEFINITION (Case) Case Control Processing Delimiter

Delimites the various type of commands under grid point stress and/or p-version element set definitions.
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
 SKIP (Case) 511
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
 512 SMETHOD (Case)
Iterative Solver Method Selection

SMETHOD (Case) Iterative Solver Method Selection

Selects iterative solver method and parameters.

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 and does not handle p-elements. See the ITER Bulk Data entry for a list of restrictions.
3. The element-based iterative solver can be used with SMP by setting smp=number on the
command line. Please refer to smp, pg. 10 of this manual for correct usage.
4. For SOL 600, the iterative solver is activated using the MARCSOLV PARAM.
5. GPGPU devices are not supported for iterative methods.

Main Index
 SPC (Case) 513
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
 514 SPCFORCES (Case)
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:

SPFORCES ( 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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, single point forces of constraint.
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.
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.

Main Index
 SPCFORCES (Case) 515
Single Point Forces of Constraint Output Request

Describer Meaning
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.
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.
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.
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 2.
and 5.
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. Both PRINT and PUNCH may be requested.
2. See Remark 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2. In
the SORT1 format, only nonzero values will be output.
3. In a statics problem, a request for SORT2 causes loads at all points (zero and nonzero) to be
output.
4. SPCFORCES=NONE overrides an overall output request.
5. 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.
6. SPCFORCES results are output in the global coordinate system (see field CD on the GRID Bulk
Data entry).
7. In SOLs 129 and 159, SPCFORCES results do not include the effects of mass and damping
elements.

Main Index
 516 SPCFORCES (Case)
Single Point Forces of Constraint Output Request

8. 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.
9. In inertia relief analysis, the SPCFORCES output is interpreted differently for SOLs 1, 101, and
200:
a. In SOL 1, the SPCFORCE output reflects the effects due to the applied loads only, and not the
inertial loads.
b. In SOLs 101 and 200, the SPCFORCE output includes both the effects due to inertial loads
and applied loads.
10. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.
11. 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.

Main Index
 SPLINOUT (Case) 517
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
 518 STATSUB (Case)
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 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 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 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 and SOL 400 support linear buckling analysis only, but do not support post-buckling
(nonlinear buckling analysis)

Main Index
 STEP (Case) 519
Step Delimiter

STEP (Case) Step Delimiter

Delimits and identifies a nonlinear analysis step for 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
 520 STOCHASTICS (Case)
Randomization of Model Parameters

STOCHASTICS (Case) Randomization of Model Parameters

Request randomization of all or selected subsets of model parameters.

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
 STRAIN (Case) 521
Element Strain Output Request

STRAIN (Case) Element Strain Output Request

Requests the form and type of strain output.

Format:

STRAIN ( SORT1 , PRINT, PUNCH REAL or IMAG , VONMISES , STRCUR ,

SORT2 PLOT PHASE MAXS or SHEAR FIBER

CENTER  ALL 
CORNER or BILIN , PSDF, ATOC, CRMS RPRINT  
, RPUNCH ) =  n 
SGAGE or RALL NORPRINT  
CUBIC  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

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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates strain for the requested set, but no printer output.
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.
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.

Main Index
 522 STRAIN (Case)
Element Strain Output Request

Describer Meaning
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.
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.
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
BILIN gage approach with bilinear extrapolation.
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.

Main Index
 STRAIN (Case) 523
Element Strain Output Request

3. Both PRINT and PUNCH may be requested.

4. STRAIN=NONE overrides an overall output request.
5. The PLOT option is used when strains are requested for postprocessing, but no printer output is
desired.
6. Definitions of stress, strain, curvature, and output locations are given in the Structural Elements
(p. 39) in the MSC Nastran Reference Manual.
7. 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.
8. The VONMISES, MAXS, and SHEAR options are ignored in the complex eigenvalue and
frequency response solution sequences.
9. 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), pg. 340 Case Control command for further
discussion.
10. See Remark 2 under the DISPLACEMENT (Case), pg. 282 Case Control command for a
discussion of SORT1 and SORT2.
11. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.

Main Index
 524 STRESS (Case)
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:

STRESS ( SORT1 , PRINT, PUNCH , REAL or IMAG , VONMISES ,

SORT2 PLOT PHASE MAXS or SHEAR

CENTER  ALL 
CUBIC RPRINT  
, PSDF, ATOC, CRMS , RPUNCH ) =  n 
SGAGE or RALL NORPRINT  
 NONE 
CORNER or BILIN

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

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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates stresses for requested set, but no printer output.
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.
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.

Main Index
 STRESS (Case) 525
Element Stress Output Request

Describer Meaning
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.
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.
VONMISES Requests von Mises stresses.
MAXS or Requests maximum shear in the plane for shell elements and octahedral
SHEAR stress for solid elements.
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. Both PRINT and PUNCH may be requested.
2. ALL should not be used in a transient problem due to excessive output.
3. See Remark 2 under the DISPLACEMENT (Case), pg. 282 Case Control command description for
a discussion of SORT1 and SORT2.
4. ELSTRESS is an alternate form and is equivalent to STRESS.
5. STRESS=NONE overrides an overall output request.
6. The PLOT option is used when contour plots of stresses are requested, but no printer output of
stresses is desired. However, in versions prior to MSC Nastran 2014, in nonlinear analysis, the
nonlinear stresses will still be printed unless NLSTRESS(PLOT) is specified.

Main Index
 526 STRESS (Case)
Element Stress Output Request

7. The VONMISES option is ignored for ply stresses.

8. The VONMISES, MAXS, and SHEAR options are ignored in the complex eigenvalue and
frequency response solution sequences.
9. 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), pg. 340 Case Control command for further
discussion.
10. For composite ply output, the grid point option for CQUAD4 elements will be reset to the default
option (CENTER).
11. MAXS for shell elements is not an equivalent stress.
12. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.

Main Index
 STRFIELD (Case) 527
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
 528 SUBCASE (Case)
Subcase Delimiter

SUBCASE (Case) Subcase Delimiter

Delimits and identifies a subcase.

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
 SUBCOM (Case) 529
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

Main Index
 530 SUBCOM (Case)
Combination Subcase Delimiter

SUBCOM 1010
LABEL=COMBINE SUBCASES 1001 AND 1002
SUBSEQ=1.,1.
7. For static aeroelasticity, only the displacement/element responses are combined. Trim, stability
derivative and monitor point results are not combined.

Main Index
 SUBSEQ (Case) 531
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
 532 SUBSEQ1 (Case)
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
 SUBSTEP (Case) 533
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

Main Index
 534 SUBSTEP (Case)
SUBSTEP Delimiter

NLSTEP=84
SubSTEP 1
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
 SUBTITLE (Case) 535
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
 536 SUPER (Case)
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
 SUPER (Case) 537
Superelement Subcase Assignment

7. If the ALL option is used, it must be used for all loading conditions.

Main Index
 538 SUPORT1 (Case)
Fictitious Support Set Selection

SUPORT1 (Case) Fictitious Support Set Selection

Selects the fictitious support set (SUPORT1 or SUPORT6 entries 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 or SUPORT6
Bulk Data entries (Integer > 0).

Remarks:
1. SUPORT1 or SUPORT6 Bulk Data entries will not be used unless selected in the Case Control
Section by the SUPORT1 command.
2. SUPORT entries will be applied in all subcases.
3. For SOL 600, Case Control command SUPORT1 must reference a SUPORT6 Bulk Data entry
with ID = N.

Main Index
 SVECTOR (Case) 539
Solution Set Eigenvector Output Request

SVECTOR (Case) Solution Set Eigenvector Output Request

Requests the form and type of solution set eigenvector output.

Format:
 ALL 
 
SVECTOR [ ( PRINT, PUNCH ) ] =  n 
 
 NONE 

Examples:
SVECTOR=ALL
SVECTOR(PUNCH)=NONE

Describer Meaning
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
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. Both PRINT and PUNCH may be requested.
2. SVECTOR=NONE overrides an overall output request.
3. Output will be presented as a tabular listing of grid points for each eigenvector.

Main Index
 540 SVELOCITY (Case)
Solution Set Velocity Output Request

SVELOCITY (Case) Solution Set Velocity Output Request

Requests the form and type of solution set velocity output.

Format:
 ALL 
 
SVELOCITY ( SORT1 , PRINT, PUNCH, REAL or IMAG ) =  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. Both PRINT and PUNCH may be requested.
2. Velocity output is only available for transient and frequency response problems.
3. The defaults for SORT1 and SORT2 depend on the type of analysis, and is discussed in Remark
2 under the DISPLACEMENT (Case), pg. 282 Case Control command. If SORT1 is selected for
any of the commands SACC, SDIS, and SVEL, then the remaining commands will also be
SORT1.
4. SVELOCITY=NONE overrides an overall output request.

Main Index
 SYM (Case) 541
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
 542 SYMCOM (Case)
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
 SYMSEQ (Case) 543
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
 544 TEMPERATURE (Case)
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 = n
 LOAD  ALL
 
 BOTH 

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 14.
BOTH Both MATERIAL and LOAD will use the same temperature set.
n Set identification number of TEMP, TEMPD, TEMPP1,TEMPB3, TEMPRB,
TEMPF, 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 14.
i Identification number of a SUBCASE executed in the selected thermal job.
(Integer > 0, Default = 0 is the first SUBCASE) See Remark 14.
HSTEP Specifies a STEP executed in the selected thermal job. See Remark 14.
j Identification number of a STEP executed in the selected thermal job.
(Integer > 0, Default = 0 is the first STEP) See Remark 14.
HTIME Specifies the time of a time step executed in the selected nonlinear transient
thermal job. See Remark 14.

Main Index
 TEMPERATURE (Case) 545
Temperature Set Selection

Describer Meaning
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 14.
ALL Selects all time steps executed in the selected nonlinear transient thermal job. See
Remark 14.

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 ( To ) ⋅ ( T – To )

where A ( T o ) is the thermal expansion coefficient defined on the MATi Bulk Data entries, T is the
load temperature defined with TEMPERATURE(LOAD), and T o 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.
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 ( T o ) ⋅ ( T o – TREF )

Main Index
 546 TEMPERATURE (Case)
Temperature Set Selection

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 T o 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.
For SOL 600, TREF and TEMP(INIT) must be consistent (the same values) or unexpected results
may occur.
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.
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. This reference temperature is only used for determining the material properties, unless
TEMP(INIT) is not defined, in which case it also defines TEMP(INIT) for the calculation of
thermal strains.
13. For SOL 600, in a thermal stress analysis where the temperatures were produced in a previous
SOL 600 simulation, the use of MCHSTAT is preferred.

Main Index
 TEMPERATURE (Case) 547
Temperature Set Selection

14. 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

Main Index
 548 TERMIN (Case)
Conditions to Terminate in SOL 600

TERMIN (Case) Conditions to Terminate in SOL 600

Selects a TERMIN Bulk Data entry which specifies criteria such that a SOL 600 analysis can be
terminated, for example, if the displacement at a certain grid exceeds a specified value.

Format:
TERMIN=N

Example:
TERMIN=5

Describer Meaning
N ID of a matching TERMIN Bulk Data entry specifying the termination conditions
for a particular analysis.

Remarks:
1. This entry may only be used within subcases (it may not be placed above the first subcase entry).
If there are no subcase entries, it may be placed anywhere in the Case Control Section.
2. Most SOL 600 analyses do not require TERMIN entries.
3. If some subcases have TERMIN entries and others do not, only those that do will check for
termination conditions.
4. TERMIN criteria may be different for different subcases.

Main Index
 TFL (Case) 549
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 Dynamics Users Guide.
4. It is recommended that PARAM,AUTOSPC,NO be specified when using transfer functions. See
Constraint and Mechanism Problem Identification in SubDMAP SEKR (p. 353) in the MSC
Nastran Reference Manual.
5. The transfer functions are additive if multiple TF values are referenced on the TFL command.

Main Index
 550 THERMAL (Case)
Temperature Output Request

THERMAL (Case) Temperature Output Request

Requests the form and type of temperature output.

Format:
 ALL 
 
THERMAL ( SORT1 , PRINT, PUNCH ) =  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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Compute temperatures but do not print.
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).
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
 TITLE (Case) 551
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
 552 TRIM (Case)
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
 TRIMF (Case) 553
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.

Main Index
 554 TRIMF (Case)
Trim Load Output Specification

Describer Meaning
ALL Loads for all points will be output
n Set identification of a previously appearing SET command. Only loads on points
with identification numbers that appear on this SET command will be output
(Integer > 0)

Remark:
1. By default, the loads are written to the punch file (Fortran unit 7). If the user specifies an alternate
Fortran unit number on the TRIMF entry, by default the loads will be written to a file name that
is machine specific (i.e. ‘fort.53’ on many 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 eight loads sets are available: Rigid Inertial, Rigid Applied, Rigid Air, Rigid Sum and four
more with the sum of the rigid and elastic increment. This table indicates how the describers
invoke each of these sets:

INERTIAL APPLIED AIR SUM

RIGID O O O O
ELASTIC O 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.

Main Index
 TRIMGRP (Case) 555
Selection of Trim Component(s)

TRIMGRP (Case) Selection of Trim Component(s)

Selects a set of trim components for analysis.

Format:

sid
TRIMGRP = ALL
NONE

Example:
TRIMGRP=101

Describer Meaning
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. Trim component with Poro-elastic material(PEM) is supported only on Linux64, Window32 and
Window64 platforms. Attempt to run PEM job on platforms other than supported platforms will
fail with fatal message.
3. PEM capability is available in SOL 111 and SOL 200 with analysis=mfreq.
4. SUBCASEs without TRIMGRP will have the equivalent effect of TRIMGRP=none even with the
presence of 'BEGIN TRMC' in the deck.
5. To run PEM job with multiple processors, additional information is available in 'Running PEM
jobs' section of Using the Advanced Functions in MSC Nastran (p. 170) in the MSC Nastran 2016
Installation and Operations Guide.

Main Index
 556 TSTEP (Case)
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 TSTEPNL Bulk Data entry (Integer >
0).

Remarks:
1. A TSTEP entry must be selected to execute a linear transient analysis (SOLs 109 or 112) and
TSTEPNL for a nonlinear transient analysis (SOLs 129 and 159).
2. A TSTEPNL 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 TSTEP or TSTEPNL, but not
both at the same time.

Main Index
 TSTEPNL (Case) 557
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), pg. 556.

Main Index
 558 TSTRU (Case)
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, TEMPF, 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. P-elements should also have the
same geometry description. P-order between runs can be different.
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 following parameter should be placed in the nonlinear heat run. This will place UG heat
transfer on the database.

Main Index
 UNGLUE (Case) 559
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
 560 VCCT (Case)
Virtual Crack Closure Technique for SOLs 400/600 Analysis

VCCT (Case) Virtual Crack Closure Technique for SOLs 400/600 Analysis

Selects grid sets to be used for virtual crack closure analysis in SOL 600 and 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 SOLs 400/600.
2. Different sets of cracks can be selected for different subcases using this option.
3. For SOL 600, N=0 may be entered above any subcases; then, the Bulk Data entry VCCT with
ID=0 will be used in the Marc model definition section. The fracture mechanics calculations will
be performed for all subcases. Otherwise, if N > 0, the matching Bulk Data entry VCCT will be
used in Marc’s history definition section for the applicable subcase, and all subsequent subcases,
until a new VCCT is activated.

Main Index
 VECTOR (Case) 561
Displacement Output Request

VECTOR (Case) Displacement Output Request

Requests the form and type of displacement vector output.

See the description of the DISPLACEMENT (Case), pg. 282.

Main Index
 562 VELOCITY (Case)
Velocity Output Request

VELOCITY (Case) Velocity Output Request

Requests the form and type of velocity vector output.

Format:

SORT1 PRINT, PUNCH REAL or IMAG PSDF,ATOC,CRMS

VELOCITY ( , , , ,
SORT2 PLOT PHASE or RALL
RPRINT
, RPUNCH ,[CID ,
NORPRINT

 ALL 
    
TRMC =  ALL   =  n 
 setid    
 NONE 

Examples:
VELOCITY=5
VELOCITY(SORT2,PHASE,PUNCH)=ALL
VELOCITY(SORT2, PRINT, PSDF, CRMS, RPUNCH)=20
VELOCITY(PRINT, RALL, NORPRINT)=ALL
VELOCITY(TRMC=100)=10

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.
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generates, but does not print, velocities.
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.
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.

Main Index
 VELOCITY (Case) 563
Velocity Output Request

Describer Meaning
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.
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.
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).
TRMC Selects a set of trim components for output. The default is NONE. See
Remark 10.

TRMC=ALL: Output the solution results from all trim components involved
in the analysis by Case Control command, TRIMGRP.

setid is the identification of a trim component set, defined by a previously

appearing SET command. (Integer>0).

Remarks:
1. Both PRINT and PUNCH may be requested.
2. Velocity output is only available for transient and frequency response problems.
3. See Remark 2 under DISPLACEMENT (Case), pg. 282 for a discussion of SORT1 and SORT2.
4. VELOCITY=NONE overrides an overall output request.
5. The PLOT option is used when curve plots are desired in the magnitude/phase representation, and
no printer request is present for magnitude/phase representation.
6. Velocity results are output in the global coordinate system (see field CD on the GRID Bulk Data
entry).
7. The option of PSDF, ATOC, CRMS, and RALL, or any combination of them, can be selected for
random analysis.

Main Index
 564 VELOCITY (Case)
Velocity Output Request

8. 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.
9. The selected trim components must be specified by TRIMGRP for the analysis. Since the same
grid point identifications can be shared by several trim components as well as the structure/cavity,
unintentional output could happen.
10. TRMC subcommand should be used to identify the IDs of trim component for which data
recovery operation is requested. The interface grid IDs of trim components that data recovery is
desired should be included in the set n of the request.

Main Index
 VUGRID (Case) 565
View Geometry Output for p-Version Analysis

VUGRID (Case) View Geometry Output for p-Version Analysis

Requests output of view grid and view element entries used in p-version element data recovery.

Format:
 
VUGRID ( PRINT, PUNCH ) =  ALL 
PLOT  n 

Example:
VUGRID(PRINT)=n

Describer Meaning
ALL All view element and grid entries will be output.
n Set identification of a previously appearing SET command. Only those
p-version elements with identification numbers that appear on this SET
command will be output (Integer > 0).
PRINT The printer will be the output medium.
PUNCH The punch file will be the output medium.
PLOT Generate entries, but do not print or punch.

Remarks:
1. VUGRID is processed only when an analysis with p-version elements is requested.
2. Only one VUGRID command per analysis is allowed.
3. The VUGRID command is used only for output control, and does not in anyway affect the
p-version analysis.
4. See parameters VUHEXA, VUTETRA, and VUPENTA in Parameters, pg. 707, for renaming
element entries.
5. See parameters VUELJUMP and VUGJUMP in Parameters, pg. 707, for numbering of view grid
and view element entries.

Main Index
 566 WEIGHTCHECK (Case)
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 t the g-set.

Format:

( PRINT PUNCH, SET = (  G, N, N + AUTOSPC, F, A,V  )

 
NOPRINT  ALL   
WEIGHTCHECK =  YES 
YES , WEIGHT )  NO 
GRID = gid, CGI =
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) (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.
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.

Main Index
 WETSENS (Case) 567
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:
WETSENS ( [ PRINT , PUNCH / PLOT] , [ REAL or IMAG / PHASE ] , [ THRESH = p ] ,
RESPONSE = r ,[ SOLUTION = { ALL / setf }] , [WETTED , SQWETT]) = { ALL / 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
PRINT Writes sensitivities to the print file (Default).
PUNCH Writes sensitivities to the punch file.
PLOT Do not write sensitivities to either the print file or punch file.
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.
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

Main Index
 568 WETSENS (Case)
Sensitivity Wetted Grids for SOL 108/111

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.

Main Index
 Case Control Applicability Tables 569
Case Control Applicability Tables

Case Control Applicability Tables

The following tables describe the applicability of Case Control commands to Solution Sequences:

Table 4-7 and SOLs (101 through 200) -- Subcase Definition, Superelement Control, and
Table 4-8 Auxiliary Model Control
Table 4-9 and SOLs (101 through 200) -- Data Selection
Table 4-10
Table 4-11 and SOLs (101 through 200) -- Output Selection
Table 4-12

Main Index
 570 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-7 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
CAMPBLL 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
STOCHASTICS X X
SUBCASE X X X X X X X X X X
SUBCOM X

Main Index
 Case Control Applicability Tables 571
Case Control Applicability Tables

Table 4-7 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
SUBSEQ X
SUPER X X X X X X X X X X
SYM X
SYMCOM X
SYMSEQ X

Main Index
 572 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-8 Case Control Commands in SOLs 114 Through 400 -- Subcase Definition, Superelement
Control, and Auxiliary Model Control
Solution Number
Command Name 114 115 116 118 129 144 145 146 153 159 200 400
ADACT
ANALYSIS X X
AUXCAS X
AUXMODEL X
BEGIN BULK X X X X X X X X X X X
MASTER 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
OUTPUT(PLOT) 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
SETS DEFINITION
OUTPUT(XYPLOT) 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
SEDR X X X X X X X X X X X
SEDV 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
SEKR X X X X X X X X X X X
SELG X X X X X X X X X
SELR X X X X X X X X X
SEMR X X X X X X X X X X X
SEMR X X X X X X X X X
SERE X
STOCHASTICS X X
SUBCASE 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
SYM X

Main Index
 Case Control Applicability Tables 573
Case Control Applicability Tables

Table 4-8 Case Control Commands in SOLs 114 Through 400 -- Subcase Definition, Superelement
Control, and Auxiliary Model Control
Solution Number
Command Name 114 115 116 118 129 144 145 146 153 159 200 400
SYMCOM X
SYMSEQ X

Main Index
 574 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-9 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
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

Main Index
 Case Control Applicability Tables 575
Case Control Applicability Tables

Table 4-9 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
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
 576 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-9 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
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.

Main Index
 Case Control Applicability Tables 577
Case Control Applicability Tables

Table 4-10 Case Control Commands in SOLs 114 Through 400 -- Data Selection
Solution Number
Command Name 114 115 116 118 129 144 145 146 153 159 200 400
ADAPT
AUTOSPC X X X X X X X X X
AXISYMME X
B2GG X X X X X X X X X X X
B2PP X X X X X X
BC
CLOAD X
CMETHOD X
DEFORM X X X X
DESGLB X
DESMOD X
DESOBJ X
DESSUB X
DESVAR X
DLOAD 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
K2PP X X X X X X
LOAD X X X X X X X X
LOADSET X X X X X X X X X
M2GG X 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 X X
MFLUID X X X X X X X X
MODTRAK

Main Index
 578 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-10 Case Control Commands in SOLs 114 Through 400 -- Data Selection (continued)
Solution Number
Command Name 114 115 116 118 129 144 145 146 153 159 200 400
MPC X X X X X X X X X X 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
SDAMPING X X X
SMETHOD
SPC 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)

Main Index
 Case Control Applicability Tables 579
Case Control Applicability Tables

Table 4-10 Case Control Commands in SOLs 114 Through 400 -- Data Selection (continued)
Solution Number
Command Name 114 115 116 118 129 144 145 146 153 159 200 400
TEMPER(LOAD) X X X X X
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

Main Index
 580 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-11 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
GPFORCE 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

Main Index
 Case Control Applicability Tables 581
Case Control Applicability Tables

Table 4-11 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
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 X
MAXMIN (DEF) 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
OUTRCV X X X 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
SACCELER X X X X

Main Index
 582 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-11 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
SDISPLAC X X X X X X X
SET X X X X X X X X X X
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
VUGRID X X X X X X
*For modal part of solution.
+
Forces limited to stiffness contributions.

Main Index
 Case Control Applicability Tables 583
Case Control Applicability Tables

Table 4-12 Case Control Commands in SOLs 114 Through 400 --Output Selection
Solution Number
Command Name 114 115 116 118 129 144 145 146 153 159 200 400
ACCELERA 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
DSAPRT X
ECHO X X X X X X X X X X X
EDE X X X
EKE 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
FLUX X X X X
FORCE X X X X X X X X X X X
GPFORCE 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
GROUNDCHECK X X X X X X X X X
HARMONY X X X X X
HDOT X
HOUTPUT X X X X
INTENSITY

Main Index
 584 Case Control Applicability Tables
Case Control Applicability Tables

Table 4-12 Case Control Commands in SOLs 114 Through 400 --Output Selection (continued)
Solution Number
Command Name 114 115 116 118 129 144 145 146 153 159 200 400
LABEL X X X X X X X X X X X
LINE X X X X X X X X X X X
MAXLINES X X X X X X X X X X X
MAXMIN
MPCFORCE X X X X X X X X
MPRES X X X X X X
NLLOAD X
NLOPRM X
NLSTEP X
NOUTPUT X X X X
OFREQUEN X X X
OLOAD X X X X X X X X X
OTIME X X X X X X X X X
OUTRCV
PAGE X X X X X X X X X X X
PARTN 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
SACCELER X X X X
SDISPLAC X X X X X X X
SET 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
STRAIN X X X X X X X X X X X
STRESS 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

Main Index
 Case Control Applicability Tables 585
Case Control Applicability Tables

Table 4-12 Case Control Commands in SOLs 114 Through 400 --Output Selection (continued)
Solution Number
Command Name 114 115 116 118 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
TEMPERATURE
THERMAL X X X X
TITLE 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
VELOCITY X X X X
VOLUME X X X X
VUGRID

Main Index
 586 MSC Nastran Quick Reference Guide
OUTPUT(PLOT) Commands

OUTPUT(PLOT) Commands MSC Nastran Quick Reference Guide

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.

Main Index
 OUTPUT(PLOT) Commands 587
OUTPUT(PLOT) Commands

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.
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
 588 AXES
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
 AXES 589
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, 604 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
 590 CAMERA
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
 CONTOUR 591
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).

Main Index
 592 CONTOUR
Contour Plot Options

Describers Meaning
LIST a, b, ... List of stresses, displacements or temperatures which define the contours
(Real).
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
 CSCALE 593
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
 594 DISTORTION
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
 FIND 595
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.

Main Index
 596 FIND
Automatic Calculation of Scale, Origin, and Vantage Point

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.
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
 MAXIMUM DEFORM 597
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
 598 OCULAR SEPARATION
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
 ORIGIN 599
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, 595 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
 600 ORTHOGRAPHIC, etc.
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
 PAPER SIZE 601
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
 602 PEN
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, 604 command.
3. The PEN command is optional and is not appropriate for microfilm plotters.

Main Index
 PERSPECTIVE 603
Selects Perspective Projection

PERSPECTIVE Selects Perspective Projection

See the description of the ORTHOGRAPHIC, etc., 600.

Main Index
 604 PLOT
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”).
DEFORMATIO Plot displacements or temperatures in the Z
N direction (Default).
VELOCITY Plot velocities.

Main Index
 PLOT 605
Undeformed or Deformed Plot Request

Describers Meaning
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
DEFORMATION d Remark 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
 606 PLOT
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
 PLOT 607
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
 608 PLOT
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 (p. 792) in the MSC
Nastran Reference Manual). 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
 PLOT 609
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
 610 PLOT
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
 PLOT 611
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
 612 PLOTTER
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
 PROJECTION 613
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 (p. 459) in the
MSC Nastran Reference Manual.

Main Index
 614 PTITLE
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, 179 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
 SCALE 615
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 = .007
p = --------
-
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
(p. 171) in the MSC Nastran 2014 Installation and Operations Guide.

Main Index
 616 SEPLOT
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
 SET 617
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:

ELEMENTS EXCEPT  type1 type2 … typej 

SET n = ALL   ,
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
 618 SET
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
 SET 619
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
 620 SEUPPLOT
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
 STEREOSCOPIC 621
Selects Stereoscopic Projection

STEREOSCOPIC Selects Stereoscopic Projection

See the description of the ORTHOGRAPHIC, etc., 600.

Main Index
 622 VANTAGE POINT
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 (p. 459) in the MSC Nastran
Reference Manual.

Main Index
 VIEW 623
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
 624 VIEW
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
 X-Y PLOT Commands 625
X-Y PLOT Commands

X-Y PLOT Commands MSC Nastran Quick Reference Guide

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.

Main Index
 626 X-Y PLOT Commands
X-Y PLOT Commands

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.
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.

Main Index
 X-Y PLOT Commands 627
X-Y PLOT Commands

Commands Applied to Whole Frame Curves Only

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.
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 all 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.

Main Index
 628 X-Y PLOT Commands
X-Y PLOT Commands

Commands Applied to Lower Half Frame Curves Only

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.
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
 ALLEDGE TICS 629
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
 630 BALL EDGE TICS
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, 629.

Main Index
 BLEFT TICS 631
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, 629.
3. See related command BRIGHT TICS, 632.

Main Index
 632 BRIGHT TICS
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, 629.

Main Index
 CAMERA 633
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
 634 CLEAR
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
 CSCALE 635
Character Scale Factor

CSCALE Character Scale Factor

Defines scale factor for characters in the plot frame. See the command CSCALE, 593 in the
OUTPUT(PLOT) Section.

Main Index
 636 CURVELINESYMBOL
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
 DENSITY 637
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
 638 LEFT TICS
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, 629.
3. See related command RIGHT TICS, 643.

Main Index
 LONG 639
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
 640 LOWER TICS
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, 629.

Main Index
 PENSIZE 641
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
 642 PLOTTER
X-Y Plot File Format

PLOTTER X-Y Plot File Format

See the command PLOTTER, 612 in the OUTPUT(PLOT) Section.

Main Index
 RIGHT TICS 643
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, 629.
3. See related command LEFT TICS, 638.

Main Index
 644 SEPLOT
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
 SEUPPLOT 645
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
 646 TALL EDGE TICS
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, 629.

Main Index
 TCURVE 647
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
 648 TLEFT TICS
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, 629.
3. See related command TRIGHT TICS, 649.

Main Index
 TRIGHT TICS 649
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, 629.
3. See related command TLEFT TICS, 648.

Main Index
 650 UPPER TICS
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, 629.
3. See related command LOWER TICS, 640.

Main Index
 XAXIS 651
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, 675.

Main Index
 652 XBAXIS
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
 XBGRID LINES 653
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, 678.

Main Index
 654 XDIVISIONS
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
 XGRID LINES 655
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, 686.

Main Index
 656 XINTERCEPT
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
 XLOG 657
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
 658 XMAX
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, 659, YMIN, 689, and YMAX, 688.

Main Index
 XMIN 659
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, 658, YMIN, 689, and YMAX, 688.

Main Index
 660 XPAPER
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, 690.

Main Index
 XTAXIS 661
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
 662 XTGRID LINES
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, 693

Main Index
 XTITLE 663
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
 664 XYPAPLOT
Generate X-Y Plots for a Printer

XYPAPLOT Generate X-Y Plots for a Printer

Generates X-Y plots for a printer.

See XYPLOT, 666 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
 XYPEAK 665
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, 666 for format, describers, and additional remarks.

Main Index
 666 XYPLOT
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)

Main Index
 XYPLOT 667
Generate X-Y Plots for a Plotter

BEGIN BULK
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
 668 XYPLOT
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.

Main Index
 XYPLOT 669
Generate X-Y Plots for a Plotter

Describers Meaning
STEMP Temperature in the solution set.
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
 670 XYPLOT
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 6-1 and Table 6-6 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.

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.
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

Main Index
 XYPLOT 671
Generate X-Y Plots for a Plotter

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.

Main Index
 672 XYPRINT
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, 666 for format, describers, and additional remarks.

Main Index
 XYPUNCH 673
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, 666 for format, describers, and additional remarks.

Main Index
 674 XVALUE PRINT SKIP
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
 YAXIS 675
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
 676 YBDIVISIONS
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
 YBINTERCEPT 677
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
 678 YBGRID LINES
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, 653

Main Index
 YBLOG 679
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, 657.

Main Index
 680 YBMAX
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, 681.

Main Index
 YBMIN 681
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, 680.

Main Index
 682 YBTITLE
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
 YBVALUE PRINT SKIP 683
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
 684 YDIVISIONS
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
 YINTERCEPT 685
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
 686 YGRID LINES
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, 655

Main Index
 YLOG 687
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, 657.

Main Index
 688 YMAX
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, 689.

Main Index
 YMIN 689
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, 688.

Main Index
 690 YPAPER
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, 660.

Main Index
 YTAXIS 691
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
 692 YTDIVISIONS
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
 YTGRID LINES 693
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, 662

Main Index
 694 YTINTERCEPT
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
 YTITLE 695
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
 696 YTLOG
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, 657.

Main Index
 YTMAX 697
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, 698.

Main Index
 698 YTMIN
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, 697.

Main Index
 YTTITLE 699
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
 700 YTVALUE PRINT SKIP
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
 YVALUE PRINT SKIP 701
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
 702 OUTPUT(POST) Commands
OUTPUT(POST) Commands

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 } ], BRANCH  MESSAGE  BREAK

  ,
GEOMETRIC  NOMESSAGE  NOBREAK

Example:
SURFACE 10 SET 9 NORMAL X3

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.
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.

Main Index
 SURFACE 703
Surface Definition

Describer Meaning
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
GEOMETRIC default 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
NOBREAK discontinuities.
MESSAGE A warning message will (or will not) be issued when multiple element
NOMESSAGE intersections are encountered.

Remarks:
1. SURFACE commands must be specified after OUTPUT(POST).
2. The surface 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 commands. The seid 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.

Main Index
 704 SURFACE
Surface Definition

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
 VOLUME 705
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
 706 VOLUME
Volume Definition

• The BASIC output system is used.

Main Index
 Parameters MSC Nastran Quick Reference GuideMSC Nastran Quick Reference Guide

5 Parameters


Parameter Descriptions 708
 Parameter Applicability Tables 967

Main Index
 708 Parameter Descriptions
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, 1075. The PARAM Case
Control command is described in the PARAM (Case), 464. PARAMs may also be used in .rc and .ini files
as described in Specifying Parameters, 2. 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.

ACOUT
Default = PEAK
ACOUT specifies the type of output to be used with the FORCE Case Control command in coupled
fluid-structural analysis (see Additional Topics (p. 515) in the . 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

See also the Case Control command FLSTCNT (Case), 336.

Main Index
 ACOWEAK 709
Parameter Descriptions

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.

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 (p. 369) in the MSC Nastran Reference Manual. See also the Case Control command
FLSTCNT (Case), 336.

If the iterative solver is selected (see the Case Control command, SMETHOD (Case), 512) then the
external work diagnostic will be different between ACSYM=YES and ACSYM=NO.

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.

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), 217
footnote and Remark 19. for more details on restrictions and required file assignments.

Main Index
 710 ADPCON
Parameter Descriptions

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 slave 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.

ADSTAT
Character; Default = YES
In transient analysis (SOLs 109 and 112 only), if there is a preload (see Case Control command
STATSUB (Case), 518) and ADSTAT=YES, the static displacements, SPC forces, and MPC forces will
be included in the transient output. There is a limitation that OLOAD is not included. Another limitation
is that element stress and force recover will neglect thermal strains and, hence will be wrong if there is a
TEMP(LOAD) request. For any other value of ADSTAT the preload effects will not be included in the
output, hence the output will be the perturbation displacements, SPC forces and MPC forces.

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, 711) which are not linearly independent.

Main Index
 AESMAXIT 711
Parameter Descriptions

AESMAXIT
Default = 15
Maximum number of iterations for the ITER method (see Case Control command, AESMETH, 711).

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
Number of random vectors to use as generalized functions in the RITZ method (see Case Control
command, AESMETH, 711).

AESTOL
Default = 1.E-10
Convergence criteria for the iterative solver.

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.
[ 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

Main Index
 712 ALPHA1FL, ALPHA2FL
Parameter Descriptions

  ω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 ω ω
ξ l = -------------------
2 
----- – ----- ξ i –  -----i – -----l ξ j
 ω ω 
ωj – ωi ωl ωj
2
l i

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 ]

Main Index
 ALTRED 713
Parameter Descriptions

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 
  ωj ωi  

and the damping ratio for any other ξ l mode becomes

ω i ω j  ω j ω l ω ω
ξ l = -------------------
2 
----- – ----- ξ i – -----i – -----l ξ
 ω ω  j
ωj – ωi ωl ωj
2
l i

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, 359, Static
and Dynamic Load Generation, 362, and Data Recovery Operations in SubDMAP SEDISP (p. 373) in the
MSC Nastran Reference Manual.

ALTSHAPE
Default = 0
ALTSHAPE selects the set of displacement shape functions to be used in p-version analysis.
PARAM,ALTSHAPE,0 selects the MacNeal set. PARAM,ALTSHAPE,1 selects the Full Product Space
set. For ALTSHAPE=1, IN=1 and ISOP=1 must be specified on the PSOLID entry.

Main Index
 714 ARBMASP
Parameter Descriptions

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’.

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’.

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.

Main Index
 ARF 715
Parameter Descriptions

ARF
Default = 0.95
See FLUIDMP, 772.

ARS
Default = 0.95
See FLUIDMP, 772.

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), 336 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, 378 and Real Eigenvalue Analysis in SubDMAPs SEMR3 and MODERS (p. 390) in the MSC
Nastran Reference Manual.

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.

Main Index
 716 AUTOGOUT
Parameter Descriptions

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.
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
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

Main Index
 AUTOMSET 717
Parameter Descriptions

AUTOMSET
Character, Default = NO
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. For PARAM,
AUTOMSET,YES, dependent degrees-of-freedom of the model, the M-set are automatically determined
by employing a rectangular decomposition of the RMG matrix.
For solutions other then SOL 600, the rectangular decomposition is performed via UMFPACK, which is
used by permission. Copyright (c) 2002 by Timothy A. Davis. All rights reserved. Availability:
http://www.cise.ufl.edu/research/sparse/umfpack.

Notes: • When used in SOL 600, AUTOMSET=Yes maps to Marc’s new parameter,
AUTOMSET. By default or if PARAM,AUTOMSET,NO is entered, Marc’s
AUTOMSET will be omitted. See Volume C of Marc for further details.
• PARAM,AUTOMSET,YES is not supported for SOL 109/112/200/400.
• 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.
5. This feature is not supported with:
a. PARAM,AUTOMSET,YES is not supported for SOL 109/112/200/400.
b. Design optimization (SOL 200)
c. Aerodynamic analyses (SOLs 144, 145, 146)
d. Cyclic symmetry analyses (SOLs 114, 115, 116, 118)
e. 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.

Main Index
 718 AUTOSPC
Parameter Descriptions

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), 244. It is
ignored in all nonlinear analysis in SOL 400 that only support the AUTOSPC Case Control command.
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 153 only)
In nonlinear static analysis only, AUTOSPCR specifies the action to take when singularities exist in
linear stiffness matrix of the residual structure after multipoint constraints are processed.
AUTOSPCR=YES means that singularities will be constrained and AUTOSPCR=NO means they will
not be constrained. 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.0E-4.

BAILOUT
Default = 0
See MAXRATIO, 840.

Main Index
 BEAMBEA 719
Parameter Descriptions

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 = NO (if DOMAINSOLVER ACMS is not specified)
Default = YES (if DOMAINSOLVER ACMS is specified)
PARAM,BEIGRED,YES requests a more efficient method be to reduce the viscous damping matrices
coming from upstream superelements. The CPU and disk space savings may be significant if there are a
small number of viscous damping elements in tip superelements within a multilevel superelement tree.

BIGER, BIGER1, BIGER2

Default = 0.0
See S1.

BLADEDEL
Integer, Default = 0, SOL 700 only.
Option to whether SOL 700 blade out scratch files such as ncforc are deleted or not at the end of the run.

0 Delete the blade out scratch files.

1 Do not delete the files.

BLADESET
Integer, Default = 1. SOL 700 only.
Parameter to set the ID of the UNBALNC entry for SOL 700 blade out computations. This value is placed
in field 2 if the UNBALNC entry generated by SOL 700 and the UNBALNC entry is placed on a file
named unbalnc.txt.

Main Index
 720 BLDRSTRT
Parameter Descriptions

BLDRSTRT
Integer, Default = 0, SOL 700 only.
Option to restart SOL 700 blade out analysis after the BINOUT to NCFORCE conversion so that
regeneration of the BINOUT, D2PLOT and NCFORCE files is not required.

0 Do not restart the run.

777 Restart the run just after the BINOUT to NCFORCE file conversion.

BLDTHETA
Real, Default = 0.0, SOL 700 only.
Parameter to set the value of “THETA” on the UNBALNC entry for SOL 700 blade out computations.

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. (Not supported for SOL 600.)
BUCKLE=2 requests buckling in a SOL 106 cold start run. (Must be in Bulk Data for SOL 600.)

CASIEMA
Default = NO, SOL 400 CASI Solver only
When the CASI element-based iterative solver is specified (see the Case Control command SMETHOD
(Case), 512) 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.
This parameter only applies to SOL 400 usage of the CASI solver.

CASPIV
Default = 1.0e-10

Main Index
 CB1, CB2 721
Parameter Descriptions

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 ]

where [ B 2jj ] is selected via the Case Control command B2GG and [ B xjj ] 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.
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.

CDPCH
Default = NO

Main Index
 722 CDPRT
Parameter Descriptions

See CDITER, 721.

CDPRT
Default = YES
See CDITER, 721.

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 (p. 345) in the MSC Nastran Reference Manual. 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

The SIL numbers correspond to degrees-of-freedom, i.e., one SIL number for scalar point and six
SIL numbers for a grid point.

Main Index
 CK1, CK2 723
Parameter Descriptions

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.

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 ]

where [ K 2jj ] is selected via the Case Control command K2GG and [ K zjj ] 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.

Main Index
 724 CK3
Parameter Descriptions

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 ]

where [ K yjj ] comes from the GENEL Bulk Data entries and [ K xjj ] is derived using PARAMs CK1 and
CK2. CK3 is effective only if GENEL entries are defined. Related parameters include CK1 and CK2.

CLOSE
Default = (1.0)
A value of 1.05 will set natural frequencies within 5% of each other as close. See SCRSPEC.

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 ]

where [ M 2jj ] is selected via the Case Control command M2GG and [ M xjj ] 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.

Main Index
 CONFAC 725
Parameter Descriptions

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).

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, 1667). Specification of this parameter is
recommended instead of DIAG 37 (DIAG 37 ignores User Fatal Messages 4277 and 4278).

COPOR
Default = NO, SOL 700 only
Format: PARAM,COPOR,option
Activates contact based porosity.

YES Leakage of air through holes or permeability of the air bag fabric can be blocked, in case
the element is in contact with either itself or other objects. (Character)
NO Blockage of surfaces is not considered.

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.

Main Index
 726 COSUBMAX
Parameter Descriptions

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.
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 . This option
applies to both structural and nonstructural mass for the following elements:
CBAR, CBEAM, CONROD, CQUAD4, CHEXA, CPENTA, 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.

P-elements are always generated with coupled mass and are not affected by COUPMASS.

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 }

Main Index
 CQC 727
Parameter Descriptions

where { P 2j } is selected via the Case Control command P2G, and { P xj } 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, 943.

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.)
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.

Main Index
 728 CURV
Parameter Descriptions

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 ⋅ im ≥ .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.
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.

Main Index
 CURVPLOT 729
Parameter Descriptions

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:
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,

Main Index
 730 CWDIAGP
Parameter Descriptions

.
.
.
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 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.

CWLDIGNR
Integer, Default = 0, SOL 700 only

Main Index
 CWRANDEL 731
Parameter Descriptions

Option to completely ignore CWELD entries.

0 Process (or fatal out CWELD entries if not supported yet) action depends on version.
1 Skip all CWELD entries.

Note: The following entries will also be ignored if CWLDIGNR=1

CSHEAR
CGAP
PBEND
CBUSH
PBUSH
PGAP

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.

DAMAGET
Default = 0.0, SOL 700 only
Time interval to check ply damage in advanced composite progressive failure material model (MATM),
if this value is set to zero, damage will be checked for every time step.

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.
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 (p. 380) in the MSC Nastran Reference Manual) of
superelement analysis is being performed. PARAM,DBALL specifies the default value for parameters
DBDN, DBUP, and DBRCV.

Main Index
 732 DBCCONV
Parameter Descriptions

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 2. 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
 DBDN 733
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 and the user PARAMeter
EXTOUT.

DBRCV
Default = value of PARAM,DBUP.
See DBALL.

DBUP
Default = value of PARAM,DBALL.
See DBALL.

DDRMM
Default = 0

Main Index
 734 DELCLUMP
Parameter Descriptions

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.

DELCLUMP
Default = 0.5, SOL 700 only

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

Main Index
 DESPCH1 735
Parameter Descriptions

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.
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 all (topology designed and non-designed) element density values to the topology
element density history file jobname, des.
<0 Write topological designed element density values to the topology 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

Main Index
 736 DIROUT
Parameter Descriptions

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, 943.

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.

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.

Main Index
 DSNOKD 737
Parameter Descriptions

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 > 0 is specified in SOL 105, under the original Design Sensitivity Analysis (DSA),
the differential stiffness sensitivity calculation is performed under the assumption that all the
displacements are enforced; i.e., the change in the stiffness matrix due to the changes in the displacements
are not computed. Therefore, PARAM,DSNOKD,0.0 is recommended in SOL 105. 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.
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.

Main Index
 738 DV3PASS
Parameter Descriptions

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.

DYBEAMIP
Integer, Default = 0, SOL 700 d3plot output only.
Number of beam integration points for output. This option does not apply to beams that use a resultant
formulation

DYBLDTIM
Real, no Default, SOL 700 only.
The value entered for DYBLDTIM is the number of seconds over which a static load is built up. This
parameter is only used in conjunction with PARAM,DYSTATIC,2.

DYBULKL
Real > 0.0, Default set internally, SOL 700 only.
Value of the linear coefficient in the bulk viscosity equation. For structural elements only.

DYBULKQ1
Real > 0.0, Default set internally, SOL 700 only.
Quadratic bulk viscosity coefficient. For structural elements only.

DYCMPFLG
Integer, Default = 0, SOL 700 d3plot output only.
Orthotropic and anisotropic material stress and strain output in local material coordinate system for
solids, shells and thick shells.

0 Global
1 Local

Main Index
 DYCONECDT* 739
Parameter Descriptions

DYCONECDT*
Integer > 0, Default = 0, SOL 700 only.
Time step size override for eroding contact:

0 Contact time size may control Dt.

1 Contact is not considered in Dt determination
*Large field parameter only.

DYCONENMASS*
Integer > 0, Default = 0, SOL 700 only.
Treatment of the mass of eroded grids in contact. This option effects the adaptive contact algorithm
(ADAPT=YES on the BCBODY option). Generally, the removal of eroded grids makes the calculation
more stable; however, in problems where erosion is important the reduction of mass will lead to incorrect
results.

0 Eroding grids are removed from the calculation.

1 Eroding grids of solid elements are retained and continue to be active in contact.
2 The eroding grids of solid and shell elements are retained and continue to be
active in contact
*Large field parameter only.

DYCONIGNORE*
Integer > 0, Default = 0, SOL 700 only.
Ignore initial penetrations during contact. ‘Initial’ in this context refers to the first time step that a
penetration is encountered. This option can also be specified for each contact pair individually by using
IGNORE on the BCTABLE entry. The value defined here will be the default. Only active for contact
pairs with AUTO=YES.

0 Move nodes to eliminate initial penetrations in the model definition.

1 Allow initial penetrations to exist by tracking the initial penetrations.
2 Allow initial penetrations to exist by tracking the initial penetrations. However, penetration
warning messages are printed with the original coordinates and the recommended
coordinates of each slave node given.
*Large field parameter only.

Main Index
 740 DYCONPENOPT*
Parameter Descriptions

DYCONPENOPT*
Integer > 0, Default = 1, SOL 700 only.
Penalty stiffness value option. This only applies to contacts with SOFT=0 on the BCBODY entry.

0 The default is set to 1.

1 Minimum of master segment and slave node.
2 Use master segment stiffness.
3 Use slave node value.
4 Use slave node value, area or mass weighted.
5 Same as 4, but inversely proportional to the shell thickness. This may require special scaling
and is not generally recommended.
Options 4 and 5 are recommended for metal forming calculations.
*Large field parameter only.

DYCONRWPNAL*
Real > 0.0, Default = 0.0, SOL 700 only.
Scale factor for rigid wall penalties for treating rigid bodies interacting with fixed rigid walls.

0.0 Rigid bodies interacting with rigid walls are not considered.
> 0.0 Rigid bodies interact with fixed rigid walls. A value of 1.0 is recommended. Seven variables
are stored for each slave node. This can increase memory requirements significantly if all
nodes are slaved to the rigid walls.
*Large field parameter only.

DYCONSKIPRWG*
Integer > 0, Default = 0, SOL 700 only.
Flag not to display stationary rigid wall.

0 Generate three extra nodes and one shell element to visualize a stationary rigid wall
1 Do not generate nodes and shell element
*Large field parameter only.

DYCONSLSFAC*
Real > 0.0, Default = 0.1, SOL 700 only.

Main Index
 DYCONTHKCHG* 741
Parameter Descriptions

Default scale factor for contact forces.

*Large field parameter only.

DYCONTHKCHG*
Integer > 0, Default = 0, SOL 700 only.
Shell thickness changes considered in single surface contact.

0 No consideration (Default)
1 Shell thickness changes are included.
*Large field parameter only.

DYCOWPRD
Real, no Default, SOL 700 only.
If this parameter is entered, the real value is the value of D in the Cowper Symonds strain rate equation
(see MSC Dytran Reference Manual Remark 7 for YLDVM).

DYCOWPRP
Real, no Default, SOL 700 only.
If this parameter is entered, the real value is the value of P in the Cowper Symonds strain rate equation
(see the MSC Dytran Reference Manual Remark 7 for YLDVM).

DYDCOMP
Integer, Default = 1, SOL 700 d3plot output only.
Data compression to eliminate rigid body data:

1 Off (Default), no rigid body data compression,

2 On, rigid body data compression active,
3 Off, no rigid body data compression, but nodal velocities and accelerations are eliminated
from the database.
4 On, rigid body data compression active and nodal velocities and accelerations are
eliminated from the database

DYDEFAUL
Character, SOL 700 only.

Main Index
 742 DYDTOUT, DT
Parameter Descriptions

Controls the default setting of the simulation. Allowed entries are DYNA and DYTRAN. This parameter
must be present in the Case Control Section. When present in the Bulk Data Section, it will be ignored.
1. The following defaults are set for the parameters shown below depending on whether
“DYTRAN” or “DYNA” is specified. If this parameter is not entered, the defaults in the following
“DYTRAN” column are used:
2. When "DYTRAN" is specified, I12 of BELY element formulation of PBEAM71 will not be
considered. However when "DYNA" is specified, it will be considered and the torsional behavior
will be added for unsymmetrical cross section such as Z cross section, etc.

Input DYTRAN DYNA

DYPARAM,LSDYNA,ENERGY,HGEN 1 1
DYPARAM,LSDYNA,ENERGY,SLNTEN 1 1
DYPARAM,LSDYNA,ENERGY,RYLEN 1 1
DYPARAM,LSDYNA,OUTPUT,IKEDIT 100 100
DYPARAM,LSDYNA,OUTPUT,IFLUSH 5000 5000
DYPARAM,LSDYNA,SHELL,WRPANG 20. 20.
DYPARAM,LSDYNA,SHELL,ESORT 0 0
DYPARAM,LSDYNA,SHELL,IRNXX -1 -1
DYPARAM,LSDYNA,SHELL,THEORY 10 2
DYPARAM,LSDYNA,SHELL,MITER 1 1
DYPARAM,LSDYNA,SHELL,BWC 2 2
SOFT option in BCTABLE 1 0
PARAM,DYBULKQ 1.0 1.5
PARAM,DYBULKL 1.0E-10 0.06

Note: In the 2012 release there is a defect and the DYBULKL value is set to 0.06, to correct this
also include PARAM,DYBULKL, 1.3-10 which will reset it to a small value.

DYDTOUT, DT
Real, no Default, SOL 700 only.
This parameter is used to determine the increment for d3plot outputs. It is used in conjunction with
DISP=ALL, VELOCITY=ALL, ACCELERATION=ALL, STRESS=ALL, etc. For example, if
DISP=ALL is entered and PARAM,DYDTOUT,DT is entered, the following Dytran Case Control will
be generated:
TYPE(D3PLOT) = D3PLOT
TIMES(D3PLOT) = 0,THRU,END,BY,DT

Main Index
 DYDYLOAD 743
Parameter Descriptions

DYDYLOAD
Integer, Default = 1, SOL 700 only.
Determines if MSC Nastran dynamic loads are passed directly to Dytran or translated by the internal
translator in MSC Nastran.

0 Dynamic loads are translated by the internal translator in MSC Nastran using the same
methods employed for version up to and included 2005 r2.
1 Dynamic loads are passed directly to Dytran. For this option to work properly, if loads other
than what is listed below are used, the job may fail or obtain the wrong results. This option
requires version 2005 r3 or greater of MSC Nastran and Dytran.
Case Control

DLOAD
LOADSET
LOAD (dynamic relaxation only)
Bulk Data

LSEQ
DLOAD
DELAY
LOAD (dynamic relaxation only)
DAREA
TLOAD1
TABLED1, TABLED2, TABLED3
FORCE
FORCE2
MOMENT
MOMENT2
GRAV
PLOAD
PLOAD4
RFORCE (CID, METHOD, RACC, MB fields are not available)
SPCD
Note: This parameter may be placed in rc files.

Main Index
 744 DYELAS1C, ITABLE
Parameter Descriptions

DYELAS1C, ITABLE
Integer, no Default, SOL 700 only.

ITABLE If this parameter is entered, and ITABLE is positive, all CELAS1 entries will be
converted to CELAS1D. ITABLE will be used directly to specify TABLED1
associated with each of these CELAS1 springs.
If ITABLE is negative, all CELAS1 entries will be converted to CELAS1D. New
TABLED1 entries will be created for each PELAS with an ID the same as PELAS
entry. The Y (force) values of the new TABLED1 entries are calculated by multiplying
the spring stiffness of each original PELAS times the Y values of corresponding points
n the TABLES1 curve with ID of ITABLE (which should be considered to by a “unit
value” curve). The unit curve is limited to 20 points.

TABLED1 with an ID of ITABLE must exist if this parameter is entered.

DYELAS1F, IFOLLOW
Integer, no Default, SOL 700 only.

IFOLLOW This parameter is only active if PARAM,DYELAS1C is also entered. IFOLLOW

should be set to 1 if the spring is a follower spring. If the spring is not a follower
spring, set IFOLLOW=0 or leave the parameter out.

DYELAS1R, ICID
Integer, no Default, SOL 700 only.

ICID This parameter is only active if PARAM,DYELAS1C is also entered. ICID is the
reference coordinate system the spring degrees-of-freedom are defined in. If the
system is the basic coordinate system, leave this parameter out or set ICID=0.

DYELPLET, RETAN
Real, no Default, SOL 700 only.

RETAN This parameter is only active if PARAM,DYELPLSY is also entered. In addition,

RETAN=ETAN/E (the ratio of tangent modulus to Young’s modulus, E) to be used
for all MAT1 conversions. Retan must be greater than zero.

Main Index
 DYELPLFL, FAIL 745
Parameter Descriptions

DYELPLFL, FAIL
Integer, no Default, SOL 700 only.

FAIL This parameter is only active if PARAM,DYELPLSY is also entered. FAIL is the
plastic failure strain which must be > 0.0

DYELPLSY, RSIGY
Real, no Default, SOL 700 only.

RSIGY If this parameter is entered, all elastic MAT1 materials will be converted to elastic-
plastic MATD024 materials. In addition, RSIGY=SIGY/E (the ratio of yield stress to
Young’s modulus, E) to be used for all MAT1 conversions. RSIGY must be greater
than zero.

DYENDTIM
Integer, Default = 1, SOL 700 only.

-1 MSC Nastran TSTEP and TSTEPNL entries will be translated directly to

Dytran. This option requires that fields 7 and beyond as well as the
continuation entries be eliminated.
0 or 1 or if parameter is MSC Nastran TSTEP and TSTEPNL entries will be translated to the Dytran
omitted Case Control ENDTIME command with the ENDTIME where the
ENDTIME value is calculated using the number of time steps times the
delta time from the TSTEP or TSTEPNL entry (only the first such
specification will be translated)

DYENERGYHGEN
Integer > 0, Default = 1, SOL 700 only.
Hourglass energy calculation option. This option requires significant additional storage and increases
cost by ten percent.

1 Hourglass energy is not computed (Default).

2 Hourglass energy is computed and included in the energy balance.
The hourglass energies are reported in the ASCII output files GLSTAT and MATSUM.
*Large field parameter only.

Main Index
 746 DYENGFLG
Parameter Descriptions

DYENGFLG
Integer, Default = 1, SOL 700 d3plot output only.
Flag for including shell internal energy density and thickness in the Dytran database:

1 Include (Default)
2 Exclude

DYHRGIHQ
Integer > 0, Default = 1, SOL 700 only.
Default hourglass viscosity type

1 Standard Dytran (Default)

2 Flanagan-Belytschko integration
3 Flanagan-Belytschko with exact volume integration
4 Stiffness form of type 2 (Flanagan-Belytschko)
5 Stiffness form of type 3 (Flanagan-Belytschko)
6 Belytschko-Bindeman assumed strain co-rotational stiffness form for solid elements only.

DYHRGQH
Real > 0.0, SOL 700 only.
Default hourglass coefficient, QH. Values of QH that exceed .15 may cause instabilities.

DYIEVERP
Integer, Default = 0, SOL 700 d3plot output only.
Every plot state for “d3plot” database is written to a separate file. This option will limit the database to
1000 states:

0 More than one state can be on each plotfile.

1 One state only on each plotfile.

Main Index
 DYINISTEP* 747
Parameter Descriptions

DYINISTEP*
Real > 0, SOL 700 only.
Specifies the initial time step. If not given, the value will be calculated automatically, unless
PARAM,DYENDTIM=-1, in which case the initial time step is equal to DT as specified on a TSTEP or
TSTEPNL entry. This parameter may be entered in the Bulk Data or RC file. If entered in an RC file, it
must be truncated to 8 characters, param,dyinste,value.
*Large field parameter only.

DYLDKND
Integer, Default = 0, SOL 700 only.
Stress-strains curves for the entire input file are defined as follows:

0 Engineering stress-strain
1 True stress and strain
2 True stress and plastic strain
3 Plastic modulus and true stress

DYMATS1
Integer, Default = 1, SOL 700 only.
If DYMATS1=0, MSC Nastran MATS1 entries will be translated directly to Dytran. If DYMATS1=1,
MSC Nastran MATS1entries will be translated to the Dytran Bulk Data entry YLDVM. The matching
TABLES1 entry if present will be converted to TABLED1 as required by DYTRAN.

Note: PARAM,DYLDKND determines the type of stress-strain curve entered. If desired, the
values D and P in the Cowper Symonds strain-rate equation can be entered with
PARAM,DYCOWPRD,D and PARAM,DYCOWPRP,P respectively.

If DYMATS1=-1, all MATS1 and TABLES1 entries will be skipped.

DYMAXINT
Integer, Default = 0, SOL 700 d3plot output only.
Number of shell integration points written to the binary database. If the default value of 3 is used then
results are output for the outermost (top) and innermost (bottom) integration points together with results
for the neutral axis. If MAXINT is set to 3 and the element has 1 integration point then all three results

Main Index
 748 DYMAXSTEP*
Parameter Descriptions

will be the same. If a value other than 3 is used then results for the first MAXINT integration points in
the element will be output.

Note: If the element has an even number of integration points and MAXINT is not set to 3 then
you will not get mid-surface result.

DYMAXSTEP*
Real > 0.0, Default = 1.e20, SOL 700 only.
Defines the maximum allowable time step. If the stable time step calculated is greater than MAXSTEP,
the time step is set to MAXSTEP.
*Large field parameter only.

DYMINSTEP*
Real > 0.0, SOL 700 only.
Defines the minimum time step that causes the analysis to terminate. 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, a lot of computer resources may be
wasted. This option allows you to specify a minimum time step that causes the analysis to terminate. This
parameter may be entered in the Bulk Data or an RC file. If entered in an RC file, it must be truncated to
8 characters, param,dyminstre,value. If this parameter is entered, PARM,DYINISTEP must also be
entered.
*Large field parameter only.

DYNAMES
Integer, Default = 0, SOL 700 only.

0 Dytran output names will be of the form jid.dytr.d3plot, jid.dytr.d3hsp etc.

1 Dytran output names will be of the form d3plot, d3hsp, etc.

DYNEIPH
Integer, Default = 0, SOL 700 d3plot output only.
Number of additional integration point history variables written to the binary database for solid elements.
The integration point data is written in the same order that it is stored in memory-each material model
has its own history variables that are stored. For user defined materials it is important to store the history
data that is needed for plotting before the data which is not of interest.

Main Index
 DYNEIPS 749
Parameter Descriptions

DYNEIPS
Integer, Default = 0, SOL 700 d3plot output only.
Number of additional integration point history variables written to the binary database for both shell and
thick shell elements for each integration point, see also PARAM,DYNEIPH.

DYNINT
Integer, Default = 3000000, SOL 700 only.
Defines the size of the integer memory in words.
It may still be possible that your analysis data does not fit in the requested memory. In that case, the
definition in the input file must be altered again. For an estimate of the size that the analysis
approximately needs, check at the memory summary at the end of the <jobname>.dytr.OUT file. Please
note the memory size mentioned are only an indication, as the summary is written when the analysis
stopped. If the analysis completed successfully, the core memory size is accurate. This core memory will
only be used for input files that activate the fluid structure interaction (PEULER or PEULER1) and
uniform pressure airbags (GBAG). For structure only models, this core memory is not used.

DYNINTSL
Integer, Default = 1, SOL 700 d3plot output only.
Number of solid element integration points written to the Dytran database. The default value is 1. For
solids with multiple integration points NINTSLD may be set to 8. Currently, no other values for
NINTSLD are allowed. For solids with multiple integration points, an average value is output if
NINTSLD is set to 1.

DYNRBE23
Integer, Default = 1, SOL 700 only.
Dytran sometimes experiences numerical errors when RBE2 or RBE3 are used with less than 6 degrees
of freedom. This parameter allows the user to determine whether to use the degrees of freedom specified
in the model or to use all six degrees of freedom for all RBE2 and RBE3 elements.

0 Use the degrees of freedom found in the model without change (the user needs to check that
Dytran successfully completed all specified time steps when using this option).
1 Change all RBE2 and RBE3 to use all 6 degrees of freedom even if fewer are specified.

DYNREAL
Integer, Default = 2500000, SOL 700 only
Defines the size of the float memory in words.

Main Index
 750 DYN3THDT
Parameter Descriptions

It may still be possible that your analysis data does not fit in the requested memory. In that case, the
definition in the input file must be altered again. For an estimate of the size that the analysis
approximately needs, check at the memory summary at the end of the <jobname>.dytr.OUT file. Please
note the memory size mentioned are only an indication, as the summary is written when the analysis
stopped. If the analysis completed successfully, the core memory size is accurate. This core memory will
only be used for input files that activate the fluid structure interaction (PEULER or PEULER1) and
uniform pressure airbag (GBAG). For structure only models, this core memory is not used.

DYN3THDT
Integer, Default = 1, SOL 700 d3plot output only.
Material energy write option for D3THDT database

1 Off, energy is NOT written to D3THDT database,

2 On (Default), energy is written to D3THDT database

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.

DYPBM71
Integer, Default = 0, SOL 700 only.
Determines whether PBEAM71 header will remain as is or be changed to PBEAM1 in the jid.dytr.dat
dytran input file.

0 Header PBEAM71 will be changed to PBEAM1.

1 Header PBEAM71 remains as is.

Main Index
 DYPRMSPC 751
Parameter Descriptions

DYPRMSPC
Integer, Default = 1, SOL 700 only.
Determines if permanent constraints (field 8 of GRID entry) is translated to SPC.

0 Permanent constraints are not translated to SCP.

1 Permanent constraints are translated to SCP.

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.

DYRBE3
Integer, Default = 0, SOL 700 only.

-1 RBE3 will be translated to a new Dytran RBE3D entry.

0 RBE3 will be translated as is to Dytran .

DYRBE3TY
Integer, Default = 1, SOL 700 only.
Determines if RBE3 is mapped to MPC to Dytran’s RBE3D.

0 RBE3 is mapped to Dytran’s RBE3 entry.

1 RBE3 is mapped to MPC’s.

Note: When DYRBE3TY=1, DYNREB23 will be set to zero.

DYRLTFLG
Integer, Default = 1, SOL 700 d3plot output only.
Flag for including stress resultants in the shell Dytran database:

1 Include (Default)
2 Exclude

Main Index
 752 DYSHELLFORM
Parameter Descriptions

DYSHELLFORM
Integer, Default = 10, SOL 700 only.
Sets the default for the shell formulation.

1 Hughes-Liu
2 Belytschko-Tsay (similar to Dytran’s BLT)
3 BCIZ triangular shell
4 C0 triangular shell
5 Belytschko-Tsay membrane
6 S/R Hughes-Liu
7 S/R co-rotational Hughes-Liu
8 Belytschko-Leviathan shell
9 Fully integrated Belytschko-Tsay membrane
10 Belytscho-Wong-Chiang (similar to Dytran’s KEYHOFF)
11 Fast (co-rotational) Hughes-Liu
16 Fully integrated shell element (very fast)
17 Fully integrated DKT, triangular shell element
18 Fully integrated linear DK quadrilateral/triangular shell
20 Fully integrated linear assumed strain C0 shell
21 Fully integrated linear assumed C0 shell (5 DOF)
22 Linear shear panel element (3 DOF per node)
*Large field parameter only.

DYSHGE
Integer, Default = 1, SOL 700 d3plot output only.
Output shell hourglass energy density:

1 Off (Default), no hourglass energy written

2 On

Main Index
 DYSHNIP 753
Parameter Descriptions

DYSHNIP
Integer, Default = 3, SOL 700 only.
Specifies the number of integration points for SOL 700 shell elements (see DYSHELLFORM* to specify
the type of shell to be used in the analysis).

DYSHTHICK*
Character, Default = YES, SOL 700 only.
Specifies whether or not the thickness of the shell changes with membrane straining.

YES Shell thickness is modified according to the membrane strain.

NO Shell thickness is constant.
*Large field parameter only.

DYSIGFLG
Integer, Default = 1, SOL 700 d3plot output only.
Flag for including stress tensor in the shell Dytran database:

1 Include (Default)
2 Exclude

DYSTATIC
Integer, Default = 0, SOL 700 only.

0, and if SOL 700, 106 is Static analysis will be simulated using dynamic relaxation. This option
entered requires the use of Bulk Data entry DAMPGBL. The use of dynamic
relaxation frequently adds significant damping to the model which in some
cases can change the static response compared to the use of small damping.
(Default)

Main Index
 754 DYSTRFLG
Parameter Descriptions

1, and if SOL 700, 106 is Static analysis will be simulated using a slow buildup of the loading. It is
entered not necessary to add excess damping with this approach, but run times may
be longer than if dynamic relaxation is used. PARAM,DYENDTIME is
required for DYSTATIC=1 unless the default end time of 1.00 is
acceptable.
2, and if SOL 700, 106 is Static analysis will be simulated using a slow buildup of the loading linearly
entered increasing from zero to full value over a period of time defined by
PARAM,DYBLDTIM. The load will be held at full value between the time
defined by PARAM,DYBLDTIM and the time defined by the time defined
by PARAM,DYENDTIME and/or Case Control command, ENDTIME.
For this option, damping greater than what the structure actually has is
frequently employed, but not as much damping as for the dynamic
relaxation option (DYSTATIC=0).

DYSTRFLG
Integer, Default = 0, SOL 700 d3plot output only.
Set to 1 to dump strain tensors for solid, shell and thick shell elements for plotting by LS-PREPOST and
ASCII file ELOUT. For shell and thick shell elements two tensors are written, one at the innermost and
one at the outermost integration point. For solid elements a single strain tensor is written.

DYSTSSZ
Integer, Default = 1, SOL 700 d3plot output only.
Output shell element time step, mass, or added mass:

1 Off (Default)
2 Output time step size
3 Output mass, added mass, or time step size

DYTERMNDTMIN*
Real, Default = 0.0, SOL 700 only.
Reduction (or scale) factor for initial time step size to determine minimum time step, TSMIN.
TSMIN=DTSTART*DTMIN where DTSTART is the initial step size. When TSMIN is reached, the
solver terminates with a restart dump.
*Large field parameter only.

Main Index
 DYTERMNENDMAS 755
Parameter Descriptions

DYTERMNENDMAS
Real > 0.0, Default = 1.e20, SOL 700 only.
Percent change in the total mass for termination of calculation. This option is relevant if and only if mass
scaling is used to limit the minimum time step size. See DYSTEPDT2MS*.
*Large field parameter only.

DYTSTEPDT2MS*
Real, Default = 0.0, SOL 700 only.
Time step size for mass scaled solutions, DT2MS.
Positive values are for quasi-static analyses or time history analyses where the inertial effects are
insignificant. If negative, fact*|DT2MS| is the minimum time step size permitted and mass scaling is
done if and only if it is necessary to meet the Courant time step size criterion. The value of fact is
specified on PARAM,STEPFCTL*. This mass scaling option can be used in transient analyses if the mass
increases remain insignificant. See PARAM,DYTERMNENDMAS*.
*Large field parameter only.

DYTSTEPERODE
Integer > 0, SOL 700 only.
Flag determining the behavior when TSMIN is reached (see PARAM,DYTERMNDTMIN).

0 The calculation will terminate

1 The element(s) with this time step will be eliminated
*Large field parameter only.

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 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

Main Index
 756 ENFMOTN
Parameter Descriptions

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

Main Index
 EPPRT 757
Parameter Descriptions

enforced 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
 758 EPZERO
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

Main Index
 ESLFSAV 759
Parameter Descriptions

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
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 cycle, X 1k – 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.

Main Index
 760 ESLMPC1
Parameter Descriptions

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 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

Main Index
 ESLRCF,user_rc_file 761
Parameter Descriptions

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.

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

Main Index
 762 ESLUNT1
Parameter Descriptions

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.

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.

Main Index
 EULBULKL 763
Parameter Descriptions

EULBULKL
Default = 0.0, SOL 700 only
Defines the default value of the linear bulk viscosity coefficient for Eulerian materials.

Format:
PARAM,EULBULKL,VALUE

Example:
PARAM,EULBULKL,0.1

VALUE Value of the linear coefficient in the bulk viscosity equation. (Real > 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
MATDEUL material entries.
3. When BULKL is specified on a material definition entry, the default value is overridden for that
specific material.

EULBULKQ
Default = 1.0, SOL 700 only
Defines the default value of the quadratic bulk viscosity coefficient for Eulerian materials.

Format:
PARAM,EULBULKQ,VALUE

Example:
PARAM,EULBULKQ,0.1

VALUE Value of the quadratic coefficient in the bulk viscosity equation. (Real > 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 BULKQ is blank on the
MATDEUL material entries.

Main Index
 764 EULBULKT
Parameter Descriptions

3. When BULKQ is specified on a material definition entry, the default value is overridden for that
specific material.

EULBULKT
Default = DYNA, SOL 700 only
Defines the default type of bulk viscosity for Eulerian materials.

Format:
PARAM,EULBULKT,option

DYNA Standard DYNA3D model. (Character)

DYTRAN Enhanced DYNA model.

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 BULKTYP is blank on the
MATDEUL material entries.
3. When BULKTYP is specified on a material definition entry, the default value is overridden for
that specific material.

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.

Main Index
 EUSUBCYC 765
Parameter Descriptions

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.
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.

EXTDR
EXTDR Default = NO. See EXTOUT.

EXTDROUT
EXTDROUT Default = NO.

Main Index
 766 EXTDRUNT
Parameter Descriptions

EXTDRUNT
EXTDRUNT Default = 31. See EXTOUT.

EXTOUT
When inputting the matrices for a reduced external superelement (SEBULK, CSUPER), there are four
options that can be selected using the parameter EXTOUT. EXTOUT must be placed in the Case Control
Section above any subcase or in the main Bulk Data Section. The options for Step 1 (see the table at the
end of this discussion) are as follows:
If EXTOUT is set to MATRIXDB, the reduced structural matrices and loading are stored on the database.
If EXTOUT is set to DMIGDB, the reduced structural matrices and loading are stored on the database in
a format which allows automatic connection to the analysis model if the identification numbers of the
reduction grid points and scalar points are the same as the grid points and scalar points used in the
analysis model.
If EXTOUT is set to DMIGOP2, the reduced structural matrices and loading are written in OUTPUT2
format to a tape unit specified by the parameter EXTUNIT (Default is 31). The storage format is the
same as the DMIGDB option and allows automatic connection to the analysis model if the identification
numbers of the reduction grid points and scalar points are the same as the grid points and scalar points
used in the analysis model. The output unit can be assigned to a specific file by using an ASSIGN
command in the File Management Section.
If EXTOUT is set to DMIGPCH, the reduced structural matrices and loading are output on the punch file
(.pch) in DMIG format.
The procedure for accessing the external superelement information depends on the option used to output
the external superelement in Step 1. The methods are as follows:
1. If EXTOUT was MATRIXDB or DMIGDB in Step 1, use the following commands in the File
Management Section:
ASSIGN SEXXX=’step1.MASTER’
DBLOCATE DATABLK=(EXTDB)CONVERT(SEID=xxx),
LOGICAL=SEXXX
where:
step1.MASTER is the database from the Step 1.
xxx is the superelement identification number given to the partitioned Bulk Data Section for the
external superelement.
2. If EXTOUT was DMIGOP2 in Step 1, then use the following commands in the File Management
Section:
ASSIGN INPUTT2=’step1_output2_file’,UNIT=extunit
where:
step1_output2_file is the OUTPUT2 file from Step 1.

Main Index
 EXTOUT 767
Parameter Descriptions

extunit is the unit number specified by the parameter EXTUNIT (Default=30).

3. If EXTOUT was DMIGPCH in Step 1, then include the punch file from step one in the partitioned
Bulk Data Section. In addition, add the following Case Control commands in the subcase for the
external superelement:
K2GG=KAAX
P2G=PAX
The SEBULK entry defining the superelement as an external superelement and the EXTRN entry
in the partitioned Bulk Data Section should not be specified.
If data recovery is desired for the external component in SOLs 101, 103, and 107 through 112, there are
three methods to transmit the displacements of the reduced model to the external full model. The method
is selected by the parameter EXTDROUT in the partitioned Bulk Data Section. The options are as
follows:
1. EXTDROUT set to MATRIXDB. 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.
2. EXTDROUT set to DMIGDB. 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. This option can only be used if EXTOUT was set to DMIGDB or DMIGOP2.
3. EXTDROUT set to DMIGOP2. The same as EXTDROUT set to DMIGDB except that the
displacements of the reduced model are written in OUTPUT2 format to a tape unit specified by
parameter EXTDRUNT (Default=31). The output unit can be assigned to a specific file by using
an ASSIGN command in the File Management Section. This option can only be used if EXTOUT
was set to DMIGDB or DMIGOP2.
Data recovery for the external component is limited to SOLs 101 and 103 and 107 through 112. Data
recovery is accomplished using a restart procedure from the data base created in step one and setting
parameter EXTDR to YES. 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 input methods are
as follows:
1. If EXTDROUT was MATRIXDB or DMIGDB in Step 2, then add the following commands in
the File Management Section:
ASSIGN SEXX=’step1.MASTER’
RESTART LOGICAL=SEXX
ASSIGN SEYYY=’step2.MASTER’
DBLOCATE DATABLK=(EXTDB) WHERE(SEID=yyy),
LOGICAL=SEYYY
where:
step1.MASTER is the database from the Step 1.
step2.MASTER is the database from the Step 2.

Main Index
 768 EXTOUT
Parameter Descriptions

yyy is the superelement identification number given to the partitioned Bulk Data Section for the
external superelement in Step 2.
2. If EXTDROUT was DMIGOP2 in Step 2, then add the following commands in the File
Management Section:
ASSIGN INPUTT2=’step2_output2_file’,UNIT=extdrunt
where:
step2_output2_file is the OUTPUT2 file from Step 2.
extdrunt is the unit number specified by the parameter EXTDRUNT (Default=31).
For SOL 101, the 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.
For SOL 103 and 107 through 112, the Case Control structure must match the analysis model subcase
structure in the number of eigenvalue extractions, FREQ/DLOAD or TSTEP/DLOAD subcases.

Step 1 - Create Step 2 - Step 3 -

External SE Perform Analysis Data Recovery for External SE
PARAM,EXTOUT, a. ASSIGN SEXX=’step1.MASTER’ a. ASSIGN SEXX=’step1.MASTER’
MATRIXDB DBLOCATE DATABLK=(EXTDB), RESTART LOGICAL=SEXX
CONVERT (SEID=xxx), ASSIGN SEYYY=’step2.MASTER’
LOGICAL=SEXX DBLOCATE DATABLK=(EXTDB),
WHERE(SEID=YYY),
b. PARAM,EXTDROUT,MATRIXDB LOGICAL=SEYYY

b. PARAM,EXTDR,YES
PARAM,EXTOUT, a. ASSIGN SEXX=’step1.MASTER’ a. ASSIGN SEXX=’step1.MASTER’
DMIGDB DBLOCATE DATABLK=(EXTDB), RESTART LOGICAL=SEXX
CONVERT (SEID=xxx), ASSIGN SEYYY=’step2.MASTER’
LOGICAL=SEXX DBLOCATE DATABLK=(EXTDB)
WHERE(SEID=YYY)
b. PARAM,EXTDROUT,MATRIXDB or LOGICAL=SEYYY
PARAM,EXTDROUT,DMIGDB or
ASSIGN INPUTT2= ’step2_output_file’,
PARAM,EXTDROUT,DMIGOP2 UNIT=Extdrunt

b. PARAM,EXTDR,YES

Main Index
 EXTRCV 769
Parameter Descriptions

Step 1 - Create Step 2 - Step 3 -

External SE Perform Analysis Data Recovery for External SE
PARAM,EXTOUT, a. ASSIGN INPUTT2=’step1_output2_file’, a. ASSIGN SEXX=’step1.MASTER’
DMIGOP2 Unit = extunit RESTART LOGICAL=SEXX
ASSIGN SEYY=’step2.MASTER’
b. PARAM,EXTDROUT,MATRIXDB or DBLOCATE DATABLK=(EXTDB),
PARAM,EXTDROUT,DMIGDB or WHERE(SEID=YYY),
LOGICAL=SEYYY
PARAM,EXTDROUT,DMIGOP2
ASSIGN INPUTT2=’step2_output_file’,
UNIT=Exdrunt

b. PARAM,EXTDR,YES
PARAM,EXTOUT, Include the .PCH file in partitioned Bulk
DMIGPCH Data Section and for external SE subcase

a. K2GG=KAAX
PG=PAX

EXTRCV
Default = 0
EXTRCV > 0 indicates that data recovery is to be performed on an external superelement. In this type
of run, the database for the external superelement must be attached as the primary database (Database
Concepts (p. 445) in the MSC Nastran Reference Manual), and the database that contains the solution
vectors, superelement map, and external/internal grid point equivalence table for its downstream
superelement must be attached via the DBLOCATE statements. The value of EXTRCV must also be
specified in the CONVERT clause of the DBLOCATE statement for the EMAP data block.
The following example shows the DBLOCATE statements for external superelement data recovery in
SOL 101.

EXTUNIT
Default = 31. See EXTOUT.

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.

Main Index
 770 FBATOLR
Parameter Descriptions

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.

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.

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.

Main Index
 FIXEDB 771
Parameter Descriptions

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).

FIXEDB
Default = 0
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 o a ] 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 o a ] 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 o a ] .

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.

Main Index
 772 FLEXINCR
Parameter Descriptions

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:

K fs = 1
T
--- ( K f + K f )
2

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), 333.

Main Index
 FLUIDNE 773
Parameter Descriptions

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.

FLUIDSE
Default = 0
PARAM,FLUIDSE,seidf specifies a special superelement reserved for fluid elements. Frequency
dependent fluid elements must still be in the residual. The newer 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 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 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

Main Index
 774 FRQDEPO
Parameter Descriptions

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.

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.

FZERO
Default = 1.0E-4
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 (p. 369) in the MSC Nastran Reference Manual.

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.

Main Index
 GPECT 775
Parameter Descriptions

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.

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.

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

Main Index
 776 GUSTAERO
Parameter Descriptions

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.
• 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, PARAM,WR3 and PARAM,WR4 must be specified to include rotor damping.

Main Index
 HEATCMD 777
Parameter Descriptions

HEATCMD
Character*16, Default=nastran
Name of a command to run SOL 600 thermal contact runs. Nastran first sets up an Marc run to determine
the thermal contact conditions which are output in a file named jid.nthcnt. Next, Nastran converts these
to standard Nastran thermal elements, and finally spawns a second Nastran job from the primary Nastran
job. The command to run the second Nastran job is provided using this parameter. For example, if
nast2005t1 is desired, enter CMD=nast2005t1. If the command “Nastran” is desired, either leave the
parameter out or enter “nastran”. The MSC Nastran run to be spawned will have the form:
CMD jid.nast.dat rcf=RCF
Where file RCF depends on PARAM,MARHEATM.

Remarks:
1. See PARAM,MRSPAWN2 for structural analysis.
2. CMD will be converted to lower case regardless of the case entered.

HEATSTAT
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
TEMP(LOAD) = Heat Transfer Subcase ID
If this default is not acceptable, then in heat transfer subcase add the Case Control word TSTRU=SID
and in structures subcase here
TEMP(LOAD) = SID
See the Case Control command, TSTRU (Case), 558. PARAM,NESET is no longer used. HEATSTAT
not supported for p-elements.

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

Main Index
 778 HTOCITS
Parameter Descriptions

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
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

Main Index
 IFP 779
Parameter Descriptions

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 or -2 requests that inertia relief or enforced acceleration be performed.
Enforced accelerations, if desired, are input on the DMIG,UACCEL Bulk Data entry. (See Section 7.2
of the MSC Nastran Reference Manual for the theoretical basis.)
Inertia Relief is not currently supported with external superelements.

-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.
-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.

INRLM
Replaced by the INRLOD keyword on the RESVEC Case Control command.

Main Index
 780 IRES
Parameter Descriptions

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.)

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
(p. 408) in the MSC Nastran Reference Manual.

Main Index
 KDIAG 781
Parameter Descriptions

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
143). 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.

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

1 2 ∂u ∂u
–6
Π p = 10 K6ROT --- G  ( Θ z – Ω z ) tdA with Ω z = 1---  --------y – --------x
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 5-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 5-1 In plane displacements u x, u y and normal rotation Θ z

Main Index
 782 LANGLE
Parameter Descriptions

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 information is to be stored on a CSV (comma separated values) file in a SOL 144 (static
aeroelasticity) task. The unit the CSV file is stored to is specified by param XYUNIT. LDSUM has the
following options:

0 (Default) – Do not create a CSV file for static aeroelasticity

1 Create a CSV file that contains for each static aeroelastic subcase:
• Subcase ID
• 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, MONDPS1, MONPNT2,
MONPNT3) results.
3 Same as 2 plus the output of RIGID AIR, ELASTIC RESTRAINED, and INERTIAL,
RIGID APPLIED and ELASTIC APPLIED components for the structural MONPNT1
results.
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

Main Index
 LGDISP 783
Parameter Descriptions

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, 600 and SOL 400 (see Table 3-1, under “Geometric Nonlinear” in the
MSC Nastran Reference Manual) 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).
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

Main Index
 784 LMODES, LMODESFL
Parameter Descriptions

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 linear contact.
For SOL 400 and SOL 101 linear 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.

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

Main Index
 LSTRN 785
Parameter Descriptions

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.

MARALPHA
Default = 10, SOL 600 only.
Determines what type of coefficient of thermal expansion (CTE) is entered in the Nastran input file when
CTE varies with temperature. For most Nastran solution sequences, such as SOL 106 and SOL 400, if
CTE’s vary with temperature, secant values need to be entered. This parameter specifics whether secant
or actual values are entered at each temperature on curves using the TABLEM1 entry. In addition, it
offers methods to convert the secant CTE’s instantaneous values required by Marc. Please read MAT1
Remark 10 and MATHE Remark 8 for further details.

-1 CTE’s (vs temperature) are entered in the Nastran input as instantaneous values – no
conversion is required (Warning if this option is used, the CTE’s should only be used in
SOL 600 and will produce incorrect results if used in SOL 106 or SOL 400).
0 CTE’s (vs temperature) are secant values (as required by SOL 106, 129 and 400). They
will be converted to instantaneous values using the formula immediately below for use in
the Marc portion of SOL 600.

Ai – Ai – 1
α i = A i +  ------------------------ ( T i – T ref )
 Ti – Ti – 1

1 CTE’s (vs temperature) are secant values and are converted to instantaneous values using
the formula immediately below for use in the Marc portion of SOL 600.

A i ( T i – T ref ) – A i – 1 ( T i – 1 – T ref )
α i = -----------------------------------------------------------------------------------
-
Ti – Ti – 1

Main Index
 786 MARAUTOC
Parameter Descriptions

2 CTE’s (vs temperature) are secant values and are converted to instantaneous values using
the average of the values computed by options 0 and 1.
N Same as option 1 except N intermediate points are placed between each original CTE vs
temperature value to increase accuracy. N must be 3 or greater. Testing has shown that
for CTE’s that change appreciably over the temperature range, N should be 10 or larger.
The total number of points must not exceed 8000.

Remarks:
1. α is the actual (instantaneous) CTE
2. T is temperature T ref is specified on MAT1 and other MAT entries.
3. At T ( 1 )α 1 = A 1
4. The above equations are applied at mid temperatures. The first temperature is retained. Starting
with the second temperature T iN = 0.5 ⋅ ( T i + T i – 1 ) original. Since the new final temperature will
be smaller than the original the user should ensure that the final average temperature is large
enough to cover the applied temperature range of the analysis.
5. If the CTE’s entered in the Nastran input file are secant values, it is recommended that
MARALPHA=N with N set to a value of 20 or larger but less than 8000 divided by the number
of points in the largest CTE vs temperature TABLEM1 entry.
6. Only option -1 was available prior to MD Nastran 2010 and MSC Nastran 2009.

MARAUTOC
Default = 0, SOL 600 only.
Determines whether NLAUTO entries for SOL 600,129 will override the default or not.

0 Do not override the default. (Default)

1 NLAUTO initial time step and final time will override the defaults.

Remark:
The default for the initial time step is to use the DT value from the TSTEPNL entry or the first non-zero
time value on the TABLED1 entry divided by 100.0 whichever is smaller. The default for the final time
is NDT*DT from the TSTEPNL entry or the last time point from the TABLED1 entry whichever is
smaller.

MARBATCH
Default = 0, SOL 600 only.
Specifies whether Marc will be spawned from Nastran in the “batch” mode or not.

Main Index
 MARBK105 787
Parameter Descriptions

0 Marc will be spawned using batch=no. (Default)

1 Marc will be spawned using batch=yes.

Note: PARAM,MARBATCH,0 requires PARAM,MARCTEMP,1 (which is the default). This

combination of parameters will place the Marc log file in the Nastran log file.

MARBK105
Default = 1, SOL 600 only.
This parameter controls whether linear buckling or nonlinear buckling eigenvalues are calculated for
SOL 600,105.

-1 Nonlinear eigenvalues are found. In other words, all loads are placed after Marc’s END
OPTION and default values are used for CONTROL and AUTOSTEP. This option
simulates what happens with SOL 106 or SOL 400.
1 Linear eigenvalues are found. In other words, all loads are placed before Marc’s END
OPTION, a linear analysis is used to obtain the differential stiffness and eigenvalues are
then calculated. This option simulates what happens with SOL 105. (Default)

MARBK106
Default = 1, SOL 600 only.
Controls whether linear buckling or nonlinear buckling eigenvalues are calculated for SOL 600,106.

-1 Nonlinear eigenvalues are found. In other words, all loads are placed after Marc’s END
OPTION and default values are used for CONTROL and AUTO STEP. This option
stimulates what happens with SOL 106 or SOL 400.
1 Linear eigenvalues are found. In other words, all loads are placed before Marc’s END
OPTION, a linear analysis is used to obtain the differential stiffness and eigenvalues are then
calculated. This option simulates what happens with SOL 106.

MARC4401
Default = 0, SOL 600 only.
Determines whether recycling due to body to body contact occurs.

Main Index
 788 MARC7601
Parameter Descriptions

0 Recycling due to body to body contact can occur

1 Recycling due to body to body contact is prevented - will add feature,4401 to the Marc input

MARC7601
Default = 0, SOL 600 only.
Determines whether large deformation RBE3 element will be used.

0 Use small deformation RBE3

1 Use large deformation RBE3

Remarks:
1. MARC7601=0 sets FEATURE,7601 in Marc.
2. MARC7601=1 will not set FEATURE,7601.

MARCASUM
Default is -1 for nonlinear analysis and 1 for linear analysis. SOL 600 only.

Marc’s assumed strain formulation is used for plane stress, plane strain and solid elements (Marc types
3, 11 and 7). The assumed strain formulation improves the bending behavior of these elements and uses
an enriched set of interpolation functions. Assumed strain should be off for analyses with a significant
amount of plasticity. In determining the type of analysis (linear or nonlinear) for defaults of this
parameter, the SOL 600,ID Executive statement is used. If ID is 106 or 129, the analysis is considered
to be nonlinear and the default is -1. If ID is any other value, the analysis is considered to be linear and
the default is 1. For nonlinear analyses without plasticity, this parameter should be turned on for models
with solid elements.
-1 Assumed strain is not used.
1 Assumed strain is used.

Main Index
 MARCAUTO 789
Parameter Descriptions

MARCAUTO
Default = leave out parameter, SOL 600 only.
Determines which Marc’s increment option is used.

1 NLPARM entries will be translated to Marc’s AUTO STEP option. If contact is present, the
number of steps (NINC) is less than 100, it will be reset to 100. Marc will adaptively reduce
the number of steps if possible, however, this option forces the first step to be 1% of the total
time. If the first step is too large, experience has shown that convergence problems may
result. To start with a different initial time step, see options 999 or -999.
-1 NLPARM entries will be translated to Marc’s AUTO INCREMENT option. If contact is
present, the number of steps is automatically set to 100. It has been found that certain
difficult contact problems which fail using the AUTO STEP option run successfully using
AUTO INCREMENT. This option is not available if the only “loading” is rigid contact or
velocity control.
-2 NLPARM entries will be translated to Marc’s AUTO LOAD option with no adjustment in
the number of steps. Use of the option is not recommended. This option is not available if
the only “loading” is rigid contact or velocity control.
999 Marc’s AUTO STEP option will be used with no adjustment in the number of steps whether
or not contact is present. This option is not available if the only “loading” is rigid contact or
velocity control.
-999 Marc’s AUTO INCREMENT option will be used with no adjustment in the number of steps
whether or not contact is present. This option is not available if the only “loading” is rigid
contact or velocity control.

See PARAM,MARCITER for a similar option. Do not use both MARCAUTO and MARCITER
parameters.

MARCAXEL
Default = 0, SOL 600 only.
Allows a combination of axisymmetric and plane stress elements for 2D analyses. This analysis
technique is sometimes used for approximate turbine disk/blade analysis.

0 The combination, if present in the input data will cause a Severe Warning and Marc will not
be spawned.
1 Combination is allowed and all CQUAD4, CQUAD8, CQUADR, CTRIA3, CTRIA6,
CTRIAR elements will be considered to be plane stress and mate with CTRIAX6 elements.

Main Index
 790 MARCBEAM
Parameter Descriptions

MARCBEAM
Default = -1, SOL 600 only.

-1 All CBEAM elements which reference PBEAML will be mapped to Marc element type 14 for
all cross if any CBEAM elements in the model reference MATS1 or MATEP entries. Full
plasticity is available for all such cross section shapes with this option. CBEAM cross sections
specified using PBEAM (where only A, I, J are available) will be mapped to Marc element 98
and remain elastic even though they might reference MATS1 or MATEP.
0 CBEAM will be mapped to Marc element type 14 for all cross sections specified with
PBEAML. Full plasticity is available for all such cross section shapes with this option.
CBEAM cross sections specified using PBEAM will be mapped to Marc element 98 and
remain elastic even though they might reference MATS1 or MATEP.
1 All CBEAM elements will be mapped to Marc element type 98 and remain elastic regardless
of whether the cross section is specified using PBEAM or PBEAML or whether they reference
MATS1 or MATEP.

Remark:
If PBMARB6 or PBMNUM6 beam properties are used, MACRBEAM must be set to zero which
automatically activates the new forms of Marc element 98 that can include plasticity.

MARCBODY
Default=0, SOL 600 only.
Control the logic when the specified value of NBODIES entry on BCPARA bulk data card does not
match the actual number of contact bodies in the model.

0 Analysis continuing with number of bodies actually in the model

1 Analysis continuing with number of bodies specified on NBODIES entry on BCPARA bulk
data card. (This may produce exit 13 in Marc)

MARCBUSH
Default = -1.0 if parameter is not entered, no “small” stiffness will replace zero stiffness terms, SOL 600
only.
Determines whether “small” stiffness values will be used instead of zero for the stiffness values in various
directions of CBUSHi elements.

Main Index
 MARCCBAR 791
Parameter Descriptions

-1.0 No “small” stiffness terms will replace zero stiffness values in any direction.
0.0 Stiffness values of 0.01*Kmax will be added for any direction that is zero Marc input
(apples to both translational and rotational directions)
Value The value entered will be used to calculate stiffness=Value*Kmax to replace any zero
stiffness values (applies to both translational and rotational directions)

MARCCBAR
Default = 0, SOL 600 only.
Specifies whether CBAR will be replaced by CBEAM for SOL 600.

0 CBAR is not replaced by CBEAM.

1 CBAR is replaced by CBEAM (PBAR is replaced by PBEAM, PBARL is replaced by
PBEAML).

Note: Use of this parameter is not usually required but might be beneficial in combination with
PARAM,MSPEEDSE,1 to speed up translation of models with a large number of CBAR
elements particularly when a there are large number of PBAR entries or PBARL entries.

MARCCENT
Default = 0, SOL 600 only.
Controls where the element output is generated.

0 Element output from Marc will be generated for each integration point.
1 Element output from Marc will be generated at the center of each element only. This
option saves disk space and computer time, but may not catch the maximum stresses or
strains. Because the residual load calculation is not accurate, this should not be used in
a nonlinear analysis.

MARCCON2
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered is the second value on Marc’s CONTACT second
entry representing the maximum number of entities to be created for any contact surface.

Main Index
 792 MARCCON3
Parameter Descriptions

MARCCON3
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered is the third value on Marc’s CONTACT second entry
representing the maximum number of nodes that lie on the periphery of any deformable
contact surface.

MARCCPY
If MARCCPY is specified, Marc files will be copied to Nastran output files and/or deleted according to
the option (0, 1, or 2) shown below.

MARCCPY Copy Marc Output Files to Delete Marc Input &

Option Nastran Output Files Output Files
0 (Default) No No
1 Yes Yes
2 Yes No
3 No Yes

If MARCCPY is 1 or 2, the out and log files will be copied as produced by Marc. If MARCCPY is -1 or
-2 the actions as shown above for +1 or +2 will occur, and Marc-type test will be converted to Nastran-
type text using and ASCII file named marcfilt.txt which must be located in the same directory where the
Nastran input resides or in the same directory where the Nastran executable resides.
The following Marc files are potentially affected by the MARCCPY option:

Marc Output File Nastran Output Copied to MARCCPY

name.marc.out name.f06 1, 2, -1, -2
name.marc.log name.log 1, 2, -1, -2
name.marc.t16 not copied, will remain if produced
name.op2, fort.11, or ftn11 not copied, will remain if produced

Main Index
 MARCDEF 793
Parameter Descriptions

MARCDEF
Default = 2, SOL 600 only.

0 SOL 600 default options for Marc will be set to values determined to be best for Nastran-
type problems (for MARCDEF=0, Marc’s SHELL SECT parameter will be set to 11 if the
value of MARCDEF is zero.
1 Default values will be set to current Marc standard (Mentat) values.
2 Default values will be set to “improved” Marc default values agreed on by the Marc and
Nastran development groups.

Default values affect the following Marc input data entries and fields:

MARCDEF Value MARC Implicit Entry Type Field Value

0 control 2 10
0 Auto Step 5 0.01*max time
0 Auto Step 8 10
0 Auto Step 10 1
1 control 2 3
1 Auto Step 5 1.0E-5*max time
1 Auto Step 8 5
1 Auto Step 10 0
2 control 2 10
2 Auto Step 5 1.0E-3*max time
2 Auto Step 8 5
2 Auto Step 10 1

Note: For MARCDEF=0, the first three values were found to provide better convergence and the
last (auto step 10) allows snap-through solution to converge correctly without having to use
arc-length methods. This parameter can be set in the system-wide rc file as well as the
user’s rc file or the local rc file (same directory as the Nastran input data to provide the
selected set of defaults for all runs if so desired. If the parameter is entered in the Nastran
input data file, it will override any parameters set in any of the rc files.

Main Index
 794 MARCDILT
Parameter Descriptions

MARCDILT
Default = 0, SOL 600 only.
If omitted, SOL 600 determines the value.

0 Constant dilatation is not used.

1 Constant dilatation formulation is used for solids, axisymmetric, and plane strain elements
(advance nonlinear element types 7, 10, 11, 19 and 20) if the model includes any of these
element types. For elastic-plastic and creep analysis this formulation is usually too stiff when
constant dilatation is not used. MARCDILT=1 and MARCASUM=1 should not both be
used.

MARCDIS2
Default = Program determines value, SOL 600 only.

Value If entered, this integer value entered here is the second value on Marc’s DIST LOADS
(“parameter” Section 2 of Marc’s Volume C Program Input) entry representing the
maximum number of different lists of distributed loads.

MARCDIS3
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered here is the third value on Marc’s DIST LOADS
(“parameter” Section 2 of Marc’s Volume C Program Input) entry representing the
maximum number of elements in any particular distributed loads list.

MARCDIS4
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered here is the fourth value on Marc’s DIST LOADS
(“parameter” Section 2 of Marc’s Volume C Program Input) entry representing the
maximum number of nodes with point loads applied.

MARCDMIG,N
Default = 0, SOL 600 only.
If matrices or loads are entered using K2GG, M2GG, B2GG, K2PP, M2PP, B2PP, P2G in the Nastran Case
Control Section, they will be translated to Marc as follows depending on the value of N:

Main Index
 MARCDUPE 795
Parameter Descriptions

N=0 All DMIG’s in the Nastran file (and include files) will be placed in the Marc input file
whether used or not.
N>0 All DMIG’s in the Nastran file (and include files) will be placed on a new file named
dmigxxxx.dmi where xxxx is the value of N. This new file will be “included” in Marc
using a Marc include statement. For example, if N=100 the file name will be
dmig100.dmi if N=25765 the file is dmig25765.dmi. N must not exceed a value of
999999.

Note: This parameter is ignored for External Superelements (if the MESUPER Bulk Data entry
is present).

MARCDUPE
SOL 600 only.
Controls whether SOL 600 will check for duplicate entries for most every type of bulk data entry.
SOL 600 does not allow duplicate entries, but the portion of IFP that runs prior to spawning Marc does
not usually check for duplicate entries.

1 Duplicate entries will be checked and exact duplicates are found, the job will fatal out.
2 In addition to option 1, entries will be checked and if duplicate ID’s (field 2 for most entries
or field 3 for loads) are found, the job will fatal out.
-1 Duplicate entries and ID’s will not be checked (this is desirable for certain models)

MARCDYND
Integer, Default = 0
Determines whether dynamic loads with “advanced table input” will be used in SOL 600.

0 Do not use advanced table input for dynamic loads

1 Use advanced table input for dynamic loads

If MARCDYND=1, PARAM,MARCTOTD,1 and PARAM,MARCTOTT,1 must also be set.

Main Index
 796 MARCEKND
Parameter Descriptions

MARCEKND
Default = 0, SOL 600 only.

ID Selects the type of strain results to be placed in a Nastran op2 file (if a request for an op2
file is made). ID can take the following values:

MARCEKND=0, Total strains will be processed

MARCEKND=1, Plastic strains will be processed
MARCEKND=2, Elastic strains will be processed
For creep analyses, creep strain is output if a request for strain output is made.

MARCEXIT
Default = 0, SOL 600 only.

0 If one of the COPYR options on the SOL 600 statement is specified, Nastran will process
these options and then a DMAP exit will occur.
1 The COPYR options will be processes and Nastran will not exit.

MARCFEAT,N
SOL 600 only.
If entered will add FEATURE,N to the Marc input file in the Parameters Section.

N Feature to be added, for example PARAM,MARCFEAT,5102 will generate a heat

transfer thermal contact file jid.marc.nthcnt

Only one PARAM,MARCFEAT may be entered.

MARCFILi
No Default, SOL 600 only.

Name Name a file name limited to 8 characters (16 characters if param* is used) used in
conjunction with one of the CONTINUE options on the SOL 600 statement. For
example, if CONTINUE=1 on the SOL 600 statement and
PARAM,MARCFIL1,DMIG44 is entered, friction stiffness and possibly damping)
matrices are created in DMIG format by Marc and placed on file DMIG44. The various
CONTINUE options use the following MARCFILi entries:

Main Index
 MARCFRIC 797
Parameter Descriptions

Continue Option MARCFILi SOL Executed K2GG/K2PP

1. MARCFIL1 107 K2GG
2. MARCFIL2 107 K2GG
3. MARCFIL3 111 K2PP
4. MARCFIL1 112 K2PP
5. MARCFIL1 * *
6. MARCFIL1 110 K2GG
7. MARCFIL1 103 K2GG

Remarks:
1. For most continue options other than brake squeal models, the Marc portion of SOL 600 will
produce files with very long names such as jid.marc.conmpc_0007 These file names are too long
for a Nastran parameter field even if PARAM* is used. The solution is to specify a short name
such as
PARAM,MARCFIL1,ABCD.TXT
Inside ABCD.TXT place an include line for the actual file desired, such as
INCLUDE ‘myjob.marc.conmpc_0007’
Where myjob would be replaced by the actual JID of the primary Nastran run without the bdf or
dat extension.
2. If INITCON=4 on the BCPARA entry is specified contact MPC’s for each increment will be out
on a file named jid.marc.conmpc_incr (if the increment is 7 it would be jid.marc.conmpc_0007).
3. If the DMIGOUT Bulk Data entry is used, DMIG’s will be produced in the form
jid.marc_cglsti_incr. See the description of DMIGOUT for further details.
4. For most cases, the difference between jid.marc.conmpc_last and jid.marc.conmpc.0001 is not
large enough to affect the subsequent analysis significantly. To be sure that the last
jid.marc.conmpc_xxxx is used specify the following
param,marcfil1,lastt
Nastran will search for all jid.marc.conmpc_* files and choose the one with the largest _xxxx.
If no jid.marc.conmpc_* files exist, the job will terminate with an fatal error message.

MARCFRIC
Default = 0.0, SOL 600 only.
When the Case Control command, BCONTACT = ALL is specified, no other 3D contact data is required
in the input file, except that the Coulomb coefficient of friction may be entered using the value of this
parameter. Do not enter this entry if contact surfaces are specified in the Bulk Data.

Main Index
 798 MARCGAPD, D
Parameter Descriptions

MARCGAPD, D
Default is U0 of the PGAP, 3193 entry, SOL 600 only.

D Depending on the value of PARAM,MARCGAPP, enter the gap closure distance for fixed
direction gaps or the minimum distance between end points for the true distance gap. If d >
0, the two end points are never closer than a distance d apart. If d < 0, the two end points
are never farther apart than d .

MARCGAPN, ID
No Default, SOL 600 only.

ID ID of gap element for which the immediately following PARAM,MARCGAPP and

PARAM,MARCGAPD apply. Unlike most other parameters, several sequences of
parameters MARCGAPN, MARCGAPP and MARCGAPD may be entered to specify
values for all gap elements. If no MARCGFAPN is entered, the values entered for
MARCGAPP and MARCGAPD will be used for all gaps in the model.

MARCGAPP
Default = 0, SOL 600 only.

0 Nastran gap elements will be translated to Marc fixed gap elements.

1 Nastran gap elements will be translated to Marc True Distance gaps.

MARCGAUS
Default if parameter is not entered = 1, SOL 600 only.

1 SOL 600 output stresses and strains will be at the Gauss points for solid elements and
extrapolated to the corner points for plates/shells elements. Strains are handled the same way
as stresses.
2 SOL 600output stresses and strains will be at the center and at the grid points for solid
elements (the maximum stress from any Gauss point is determined and compatible stresses
for that Gauss point are placed at the center and at each of the grid points). Shell/plate stresses
are at the center (top and bottom surfaces). The maximum Gauss point stress at each surface
is found and a compatible set of stresses at that Gauss point are placed in the center of the
surface. Strains are handled the same way as stresses.
3 Solid stresses/and strains are the same as option 1 and shell/plate stresses and strains are the
same as option 2.

Main Index
 MARCGLUE 799
Parameter Descriptions

If this parameter is entered with values of zero or less or values greater than 3, it will be reset to 1.

MARCGLUE
Default = 0 if parameter is not entered, SOL 600 only.
If MARCGLUE is set to 1, all contact surfaces will be glued whether or not IGLUE=1 is specified on the
BCTABLE entry or not.

0 IGLUE on BCTABLE entries specifies whether or not glued contact is used

1 IGLUE on BCTABLE entries will be ignored and glued contact will be used for all contact
surfaces.

Remark:
For this parameter to function BCTABLE entries must be entered (do not set BCONTACT=ALL).

MARCGRAV
Integer, Default = 0
Determines whether PARAM,MNASTLDS,777 will automatically be set if multiple GRAV entries are
present in any subcase. This is determined in a simplified fashion by comparing the number of GRAV
entries to the number of subcases to save computer time.

0 Set PARAM,MNASTLDS,777 for multiple GRAV entries.

1 Do not set PARAM,MNASTLDS,777 regardless of the number of GRAV and SUBCASE
entries.

MARCHOST
No Default, SOL 600 only.
Determines the name of a hostfile to be used with SOL 600 parallel runs. If this parameter is missing, no
host file is used and the parallel run will run on one machine. That machine may have several processors
and as many processors as specified on the PARAMARC Bulk Data entry will be used. If
PARAM,MARCHOST,Name is specified, the hostfile must be generated by the user in a format
acceptable to Marc (see the Marc and Marc Mentat Installation and Operations Guide). Each line of the
hostfile normally lists how many processors are used on each machine. If PARAM*,MARCHOST is
entered, the name is limited to 16 characters (all lower case).

MARCIAMN
Default = 1, SOL 600 only.

Main Index
 800 MARCINTC
Parameter Descriptions

0 Nastran is directed to spawn Marc (as specified by the SOL 600 Executive Control
statement or PARAM,MARCRUN), using a full version of Marc. Standard Marc licensing
is required.
1 A special version of Marc is spawned by Nastran. This version of Marc may have certain
features that are not available in the full version. Marc will be spawned from Nastran with
the additional command line switch - iam nanl. The licensing for both Nastran and Marc
reflect this situation. This option applies only to Marc version 2003 or later. If
PARAM,MARCVERS points to a Marc version earlier than 2003, MARCIAMN will be
set to zero and a full version of Marc is required.

The parameter may be set in the system-wide rc, the user rc file or as an environmental variable using
NASM_IAMN=0 or 1 (similar to the way values on the SOL 600 statement are set).

MARCINTC
Default = 2.
Option to ignore or fatal SOL 600 if any CINTC Bulk Data entries are found This option will also ignore
or issue a warning for GMBNDC entries.

0 Fatal job if any CINTC entries are found (also issue warning messages if any GMBNDC
entries are found).
1 Ignore all CINTC and GMBNDC entries in SOL 600.
2 Generate the MPC’s for CINTC/GMBNDC and combine them with standard MCP entries (if
they exist), then use them in the SOL 600 analysis (SOL 600 only).

Remark:
MARCINTC=2 spawns a secondary SOL 100 Nastran job to generate MPC’s for the CINTC’s. Licenses
from the primary job are released, then reclaimed after the secondary job terminates. The secondary job
stops prior to decomp and uses the standard SOL 101 licenses.

MARCINTF
Default = 1.0D-6.
Threshold value below which MPC coefficients generated by CINTC/GMBNDC are not considered.
This parameter is ignored unless PARAM,MARCINTC,2 has been entered.

MARCITER
Default = 0, SOL 600 only.

Main Index
 MARCL001 801
Parameter Descriptions

Used to control fixed time stepping in SOL 600.

0 Fixed time steps or auto time steps will be controlled by PARAM,MARCAUTO.

N Allows fixed time steps to be used without needing to set the maximum and minimum
times to nearly the same value (using Marc’s AUTO STEP option). This parameter
triggers true fixed time stepping with the other advantages AUTO STEP has over
methods such as AUTO LOAD. For example, it uses better numerical damping. If this
parameter is entered with a positive integer (N), a value of 2 is placed in the AUTO
STEP field 9 and N is placed in field 7.
-1 This option is similar to PARAM,MARCITER,N (fixed time stepping will be used)
except that the time comes from the NLPARAM or TSTEPNL entry. This option is not
available if the only “loading” is rigid contact or velocity control. See
PARAM,MARCAUTO for a similar option. Do not use both MARCAUTO and
MARCITER parameters.

MARCL001
Default = -1, SOL 600 only.

Determines whether Marc’s POINT LOAD (without tables) 2nd datablock, 3rd field will be honored or
not. If this value is set to 1 multiple loads at the same dof in the same subcase will usually be summed
(however, see item d.).

-1 The 2nd datablock 3rd field will be set to 1 (see Remark)

1 The 2nd datablock 3rd field will not be set to 1. If it is necessary to sum the loads, this
must be accomplished in one of several ways:
a. Summed in the GUI or other method of data input
b. By setting PARAM,MNASTLDS,1
b. By setting PARAM,MARCTOTT,1
d. For certain simple multiple force/moment cases, SOL 600 can sum them and
PARAM,MNASTLDS,1 must be specified to prevent loads from being specified
multiple times. However, it may be difficult to determine whether the loads are
complex or not, so the use of either option c or b is recommended.

Remarks:
1. For releases prior to MD Nastran 2010 and MSC Nastran 2009, this field was set to 1 to
automatically sum any forces or moments that might have been entered more than once by the
GUI (see PARAM,MNASTLDS for a discussion of ways this can happen). This field, when set
to one, allows loads entered more than once at the same grid ID in the same subcase to be summed.

Main Index
 802 MARCLOWE
Parameter Descriptions

However, experience shows that this field does not work in certain circumstances, particularly
when “total loads” using PARAM,MARCTOTL are requested. PARAM,NASTLDS has been
added beginning with MD Nastran 2010 and MSC Nastran 2009 to handle the cases where the 2nd
datablock 3rd field does not work as expected.
2. To maintain backward compatibility with previous runs, set the following parameters:
PARAM,MARCL001,1
PARAM,MNASTLDS,0
PARAM,MARCTOTL,0
PARAM,MARCTOTT,0
3. If PARAM,MARCTOTL,1 is entered, PARAM,MARCL001,1 will be set unless
PARAM,MARCL001,-1 is entered.
4. This parameter may be set in RC files.

MARCLOWE
Default = 0, SOL 600 only.
Used in conjunction with superelement matrices created by Marc.

0 Standard modulus values for all materials will be used.

1 All modulus of elasticity values will be changed to 1.0E-9 for the second Nastran run
(when Nastran spawns another Nastran run using the SOL 600 continue option. This
option is sometimes necessary for cases where Marc creates a superelement or
substructure stiffness matrix but does not create a mass matrix. In this case, the second
Nastran run will create the mass matrix using standard elements, density and other
concentrated and distributed masses but the stiffness created by Nastran will be very low.
Essentially the entire stiffness of the model will come from the stiffness matrices created
by Marc.

MARCLUMP
Default = 0, SOL 600 only.

0 Consistent mass will be used for SOL 600 transient dynamics or eigenvalue problems with
rotational masses (if applicable). (Default)
1 Lumped mass will be used for SOL 600 transient dynamics or eigenvalue problems with
rotational masses (if applicable).
2 Consistent mass will be used for SOL 600 transient dynamics or eigenvalue problems
without rotational masses.
3 Lumped mass will be used for SOL 600 transient dynamics or eigenvalue problems
without rotational masses.

Main Index
 MARCMAT2 803
Parameter Descriptions

Remark:
This parameter is only used with dynamic analysis.

MARCMAT2
Default = -1.0, SOL 600 only.
Used if g33 = 0.0 on MAT2 entries. Marc will diverge if g33 = 0.0 for MAT2 entries. If the value entered
is positive, the value is a multiplier of g11 and g22 to calculate g33 as follows:
g33 = marcmat2*(g11 + g22)

MARCMAT3
Default = 1, SOL 600 only.
Used if Nastran has generated MAT2 from PCOMP and the MID of MAT2 is 30000001 is greater
corresponding to MID3 for PSHELL.
If the value entered is 0, this entry is ignored regardless of the MAT2 MID value.
If the value entered is 1 the MAT2 entry will be mapped to Marc’s ANISOTROPIC entry such that all
Cij are zero except the following:
C55=g11
C56=g12
C66=g22
If the value entered is 2 the MAT2 entry will be mapped to Marc’s ANISOTROPIC entry such that all
Cij are zero except the following:
C44=g11
C45=g12
C55=g22
C66=g22
If the value entered is 11 the MAT2 entry will be mapped to Marc’s ANISOTROPIC entry such that all
Cij are zero except the following:
C55=g11
C56=g12
C66=g22
If the value entered is 12 the MAT2 entry will be mapped to Marc’s ANISOTROPIC entry such that all
Cij are zero except the following:
C44=g11
C45=g12
C55=g22
C66=g22

Note: This entry is ignored unless the MAT2 MID is greater than 30000000.

Main Index
 804 MARCMATT
Parameter Descriptions

MARCMATT
Default = -1 if parameter is not entered, SOL 600 only.
Determines if Marc input file will be created with materials using the table-driven formats or not.
)

-1 Table-driven formats for materials will not be used. (Default)

1 Table-driven formats for materials will be used

Remark:
This parameter can be set in RC files.

MARCMEM, Value
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered here is the second field on Marc’s SIZING entry
(MAXALL) and is the main memory specification for memory in Marc. This value is
entered in MW (the program multiplies it by 1,000,000). For example, if a value of 350
is entered, the number of 350000000 will be placed in the second field of the SIZING
entry.

MARCMID3
Default = 0, SOL 600 only.
Controls whether MID3 will be set to the same value as MID2 when the Marc PSHELL option is used
(designated by PARAM,MRPSHELL,1 or when the SMEAR option is used on the SOL 600 Executive
Control statement.)

0 MID3 will not be changed (if zero or blank, it will remain zero or blank). (Default)
1 MID3 will be set to MID2. This improves the singularity ratio in some problems without
appreciably changing the results particularly when orthotropic material properties are used. It
is not necessary if PARAM,MMAT2ANI,11 or a similar option is used to specify anisotropic
material properties.

MARCMNF
Default = 0, SOL 600 only.
Controls creation of an Adams MNF file by Marc for eigenvalue analysis when Marc is spawned from
SOL 600.

Main Index
 MARCMPCC 805
Parameter Descriptions

0 MNF file will not be created. (Default)

1 MNF file will be created (for Marc 2003, the MNF file is located in the .t19 file, so
PARAM,MARCT19,1 must also be specified).

Note: It is not necessary to use this parameter if the MDMIOUT Bulk Data entry is used to
request an MSC.Adams MNF file.

MARCMPCC
Default = 0, SOL 600 only.
Determines whether SOL 600 converts MPCs to stiff beams or not.

0 MPC’s are not converted to stiff beams. (Default)

1 MPC’s are converted to stiff beams.

Note: PARAM,MARCMPCC,1 should not be used if RBE’s are converted to MPC’s using
PARAM,MARCRBE2 or PARAM,MARCRBE3.

MARCMPII
Integer, Default = 2 for DDM parallel executions, SOL 600 only.
Determines whether the MPI service on PC systems will remain running after the job finishes.

-1 The MPI service will remain running after SOL 600 finishes
1 The Intel MPI service, ismpd.exe will be uninstalled before SOL 600 terminates.
2 The Intel MPI service, ismpd.exe will be started before each Marc execution and terminated
at the end of each Marc execution from within the Nastran portion of SOL 600.
771 MSMPI rather than Intel MPI is requested (starting and/or stopping of the ismpd.exe Intel
MPI service is ignored)

Remarks:
1. If SOL 600 terminates abnormally the service may remain running regardless of the value of this
parameter.
2. This option is currently available only for Intel MPI running on PC systems. It applies to both 32-
bit and 64-bit versions.

Main Index
 806 MARCND99
Parameter Descriptions

3. Leaving the MPI service running will speed up the execution of multiple jobs.
4. This parameter may be entered in RC files.
5. Although ismpd.exe is started by the Marc script, it sometimes fails to start properly unless started
outside the script. The user can either do this in his own script or set MARCMPII=2 to have
Nastran do it. Either of these options improves reliability of the Intel MPI starting.

MARCND99
Default-see below. SOL 600 only.
Determines whether a set in the Marc input file to output all nodal quantities will be generated or not. If
MARCND99=1, all Case Control nodal output requests must have the PLOT qualifier or the job may fail.

-1 A set named ND999999 will be generated to output all nodes for at least one type of nodal
output. This is the default of all Case Control nodal requests do not have (plot).
1 The set will not be generated. If all nodal Case Control requests have (plot) such as
DISP(PLOT)=ALL, ACCEL(PLOT)=ALL, etc. the default is 1 even if the parameter is not
entered.

MARCNOER
Default = 0, SOL 600 only.
Determines action to take when unsupported features are encountered.

0 The internal Marc translator will stop and generate FATAL ERRORs if unsupported features
in Marc or in the internal translator are encountered.
1 If unsupported features are encountered, they are ignored, no FATAL ERROR messages are
issued and if requested, Marc will be executed.

MARCOFFT
Default = -1, SOL 600 only.
Controls whether Nodal Temperatures are specified at the original or offset grid point or both grid points
for beams and shells with offsets or connected by RBE2’s (see note 2) when PARAM,MAROFSET is set
to 0,2,3. For the default MAROFSET=1 where Marc handles the offsets and RBE2’s are not added, this
parameter is not applicable and will be reset to -1 internally. Applies only if MAROFSET=0.

0 Temperatures are applied both at the original grid point and at the offset grid point.
1 Temperatures are applied at the original grid point only.

Main Index
 MARCONTF 807
Parameter Descriptions

2 Temperatures are applied at the offset grid point only.

-1 Temperature loading is not altered in any way from the Nastran input.

Note: 1. Processing time can increase significantly if beam or shell offsets are present and
param,marcoftt is zero or greater unless PARAM,MOFFCORE,1 is used.
2. If nodes are connected by RBE2’s and a temperature is applied at an independent
node, the temperature will be applied at the independent node and the first
dependent node of the rbe2 if MARCOFFT=0.
3. If MAROFSET is 0, 2 or 3 and a node has applied temperature and is also a part of
a standard RBE2 with many grids, the job may abort or the results can be wrong.

MARCONTF
No Default, SOL 600 only.

Name Name of a file name limited to 8 characters (16 characters if param* is used) used in
conjunction with one of the CONTINUE options on the SOL 600 statement. If entered
this file will be used as the input file for the second Nastran execution (after Marc has
finished). If specified, this file will be used instead of automatically creating a file named
jid.nast.dat from the original jid.dat input. This option allows more versatility in
achieving exactly what is desired in the Nastran continuation run input at the expense of
additional input data preparation.

MARCOOCC
Default = 0, SOL 600 only.

0 Standard Marc memory management will be used. If the memory is sufficient the
decomposition will be in core. If the memory requirements are too large, an out of core
solution will take place.
1 An out of core solution will be forced if solvers 0, 2, 4 or 8 are used. This option triggers
Marc parameter, OOC (without any other characters).
2 An out of core solution will be forced if solver 0, 2, 4 or 8 are used - available starting
with Marc 2005 r2. This option generates Marc parameter OOC,0,1.
3 Same as option2 except Marc parameter version,4902 will be added. This option triggers
Marc parameter OOC,0,1 plus version,4902.

Main Index
 808 MARCOPT
Parameter Descriptions

MARCOPT
Default = 9, SOL 600 only.
Determines which bandwidth optimizer is to be used.

0 Marc does not optimize the bandwidth.

2 Cuthill-McKee bandwidth optimization is used
5 External user-supplied bandwidth optimization is used
9 Sloan bandwidth optimization is used. (Default)
10 Minimum degree bandwidth optimization is used (only available with the sparse solver)
11 Metis nested dissection algorithm (only available with multifrontal direct sparse solver)
-9999 Set MARCOPT to -9999 if the OPTIMIZE entry is not wanted in the Marc file for
example with use by the iterative solver.

MARCOSET
Default = 0, SOL 600 only.
Determines whether SOL 600 set names will be standard sets or “open sets” for nodes and elements. The
standard Marc sets are:
DEFINE, ELEMENT, SET, PR00001
DEFINE, NODE, SET, ND001
The Marc open sets (OSET) are:
DEFINE, ELEMENT, OSET, PR00001
DEFINE, NODE, OSET, ND001

-1 Standard sets are defined.

0 Standard sets are defined for small models and open sets are defined for large models.
1 Open sets are defined.

Note: For Parallel (DDM) analyses, it is sometimes necessary to set MARCOSET=1.

MARCOTIM
Default = 0, (SOL 600 only and is mapped to Marc’s POST 2nd line 9th field.
Determines if Marc is to be processed at selective or at all output times.

Main Index
 MARCOUTR 809
Parameter Descriptions

0 or 1 Marc output data will be processed by Nastran at all converged output times. This option
is similar to INTOUT=YES on the NLPARM entry.
2 Marc output data will be processed by Marc only at times near 1.0, 2.0, 3.0, etc. For this
option, no additional output times will be available in the Marc .t16 and/or .t19 output
files. This option is similar to INTOUT=NO on the NLPARM entry.
N Marc output data will be processed by Marc every Nth increment for the .t16 and/or .t19
output files. (N > 2)

MARCOUTR
Default = 1 if Marc single file parallel input is used, Default = 0 if Marc multiple file inputs are used, see
Note, SOL 600 only.
Determines how Marc t16 file results will be handled for SOL 600 parallel processing.

0 Multiple t16 files, one for each domain will be produced.

1 A single t16 file will be produced by Marc. This option requires Marc 2005 or later versions
and the parallel run made using the “single file” input (PARAMARC KIND=0). (Default)

Note: Whether single file or multiple Marc inputs are used for parallel processing is determined
by the PARAMARC Bulk Data entry.

MARCPARR
Default = 0, SOL 600 only.
Controls options for splitting an Marc file into parts for DDM.

0 All Marc files will be created during this run. (Default)

1 Nastran will be stopped after the single-processor file has been created and before DDM
files are created. If desired, all files may be copied to a backup directory for use with
MARCPARR=2.
2 The parallel files will be created starting with the single processor file created using the
MARCPARR=1 option.
3 Same as MARCPARR=2 except the debug option MARCBUG=1 is turned on.

Main Index
 810 MARCPENT
Parameter Descriptions

MARCPENT
Default = 0, SOL 600 only.
Option to specify if CPENTA is mapped to Marc brick element with degenerate nodes or actual penta
elements (see Remarks).

0 Map CPENTA to Marc brick elements with degenerate nodes. (Default)

1 Marc CPENTA to actual Marc penta elements.

Remarks:
1. Option zero is the default to maintain backwards compatibility.
2. The t16 to op2 version is not available for option 1. That means no op2, xdb, f06 or punch file is
available for option 1. Postprocessing must occur using the t16 or t19 file if option 1 is used.
3. Speed options such as invoked using param,mspeedse are available using option 1 only.

MARCPINN
Default = 0, SOL 600 only.

0 Pin flags will be included by created new nodes and appropriate MPC’s by the translator in
Nastran. (Default)
1 Pin flags will be ignored and the translator will continue.
2 A severe warning will be issued and Marc will not run.
3 The new Marc PIN CODE option will be used. feature,6901 will also be used so that extra
nodes are not introduced.

Remark:
This parameter can be set in RC files.

MARCPLAS, n
Default = 3 if there is plasticity in the model. SOL 600 only.
This parameter effects the value of Marc’s PLASTICITY parameter. The value of n can range from 0 to
6 (0 is the same as 3).

1 Additive decomposition using the mean normal method; small strain formulation
2 Additive decomposition using the radial return method; small strain formulation.

Main Index
 MARCPOS 811
Parameter Descriptions

3 Additive decomposition using the mean normal method; large strain formulation using the
updated Lagrange procedure.
4 Additive decomposition using the radial return method; large strain formulation during the
updated Lagrange procedure.
5 Multiplicative decomposition (FeFp) using the radial return method and the three field
variational principle; large strain formulation using the updated Lagrange procedure.
6 Advance nonlinear elements type 3 and 26 (plane stress), 18 and 30 (membrane) using
multiplicative decomposition with the radial return method; large strain formulation using
the updated Lagrange procedure.
-1 Ensures that the Marc PLASTICITY parameter will not be used.

MARCPOS
SOL 600 only.
Determines whether to terminate Marc if a non-positive definite matrix is attempted.

0 The run will terminate if a non-positive definite matrix decomposition is encountered.

1 Non-positive definite matrices will be solved.

MARCPOST
Default, SOL 600 only.
Determines the format for the .t16 and .t19 files.

-1 The .t16 and .t19 files will be created using the Marc default for the version of Marc that
is executed.
0 Same as MARCPOST=9.
1 The .t16 and .t19 files will be created using Marc K2 formats.
3 The .t16 and .t19 files will be created using Marc K3 formats.
4 The .t16 and .t19 files will be created using Marc K4 formats.
5 The .t16 and .t19 files will be created using Marc K5 formats.
6 The .t16 and .t19 files will be created using Marc K6 formats.
7 The .t16 and .t19 files will be created using Marc K7 formats.
8 The .t16 and .t19 files will be created using Marc K8 formats.
9 The .t16 and .t19 files will be created using Marc 2000 formats.
10 The .t16 and .t19 files will be created using Marc 2001 formats.
11 The .t16 and .t19 files will be created using Marc 2003 formats.

Main Index
 812 MARCPR99
Parameter Descriptions

12 The .t16 and .t19 files will be created using Marc 2005 formats.
13 The .t16 and .t19 files will be created using Marc 2005 r3 formats.

Note: It is suggested that a small test case be executed and tested with your postprocessor to
determine what version is necessary for your postprocessor.

MARCPR99
Default-see below. SOL 600 only.
Determines whether a set in the Marc input file to output all elemental quantities will be generated or not.
If MARCPR99=1, all Case Control element output requests must have the PLOT qualifier or the job may
fail.

-1 A set named PR999999 will be generated to output all elements for at least one type of
element output. This is the default if all elemental Case Control requests do not have (plot).
1 The set will not be generated. If all elemental Case Control requests have (plot) such as
STRESS(PLOT)=ALL, STRAIN(PLOT)=ALL, etc. The default is 1 even if the parameter is
not entered.

MARCPRN
SOL 600 only.
Controls the amount of contact information printed.

0 Detailed contact information is not printed.

1 Detailed contact information is printed (this is equivalent to Marc parameter PRINT,2,8).
2 Somewhat less detailed contact information is printed (this is equivalent to Marc parameter
PRINT,2). Print constraint matrices associated with MPC’s, RBAR, RBE2, RBE3 and the
formable to deformable contact.
5 Marc print option. PRINT,5 will be used. Prints messages when changes in contact status
occur.
25 Marc print options. PRINT,2,5 will be used.
258 Marc print options. PRINT,2,5,8 will be used. In addition to 2 and 5, also prints the
displacement and reaction forces in the local coordinate system associated with formable to
rigid contact.

For other print options, use the MARCIN Bulk Data entry.

Main Index
 MARCPRNG 813
Parameter Descriptions

MARCPRNG
Default = 0, SOL 600 only.
Determines whether geometry is printed in the Marc .out file.

0 Most geometry printing is suppressed.

1 All geometry is printed.

MARCPRNR
Default = 0, SOL 600 only.
Determines whether nodal stress and strain output is printed in the Marc .out file.

0 Nodal, stress and strain printing is suppressed.

1 Nodal, stress and strain printing will occur if Case Control options request it specifically or
by default.

MARCPROG
No Default, SOL 600 only.

prg “prg” is the name of a program to be executed instead of Marc. The program may be any
program desired and must already be fully compiled on the computer system being run. prg
is limited to 8 characters, however 16 characters can be used if PARAM* is entered. “prg”
must be a compiled program, not a script or batch file. The name of the program must be in
lower case (if not, it will be converted to lower case).

MARCRACC
Default = 0, SOL 600 only.
SOL 600 does not normally support RACC on the RFORCE entry. The default is to fatal a job when
RACC is zero or blank. This parameter may be used to set it to zero or to obtain approximate results.

0 If MARCRACC is zero and RACC is nonzero, the job will terminate with an appropriate
message (Default).

Main Index
 814 MARCRBAL
Parameter Descriptions

1 If MARCRACC is one and RACC is nonzero, RACC will be set to zero internally and the
job will continue.
2 If MARCRACC is two and RACC is nonzero, the following will occur:
for brake squeal, coriolis loading and values (C1, C2, C3) will be placed in Marc ROTATION
A 3rd datablock fields 4-6 as follows:
RR=SQRT(R1**2+R2**2+R3**2)
C1=RACC*R1/RR
C2=RACC*R3/RR
C3=RACC*R3/RR

Where RACC, R1, R2, R3 are described on the RFORCE entry.

For standard structural analysis if MARCRACC=2, the value of A in RFORCE field 5 will be altered
using the following equation:
Anew=sqrt(A**2+RACC)
Marc’s ROTATION A entry will be the same as if RACC=0.0 was entered unless A is zero, in which case
the third line will have all zero entries. Results should be considered as an approximation.

Remarks:
1. See PARAM,MARCRCID for related SOL 600 RFORCE uses.
2. MARCRACC=2 only applies for brake squeal and only if the BRKSQL entry is used for releases
prior to MD Nastran R2.1 and MSC Nastran 2007.

MARCRBAL
Default = 0, SOL 600 only.
This parameter is used only for eigenvalue analysis in the Nastran-Marc interface where natural
frequencies or buckling modes need to be calculated using the deformed geometry from a nonlinear
analysis. The parameter is only necessary if the last nonlinear increment created a non-positive definite
matrix. When MARCRBAL=1 is set, the system will be rebalanced and a positive-definite matrix is
assured. Do not use this parameter unless it is known that a non-positive definite system occurs just prior
to eigenvalue analysis.

MARCRBAR
Default = 0, SOL 600 only.
Determines how RBAR is treated.

Main Index
 MARCRBE2 815
Parameter Descriptions

0 RBARs will be simulated using Marc’s Servo Link. This option is best only for small
incremental deformation and rotations. (Default)
1 RBARs will be converted to RBE2 with GN=GA, CM=123456, GM1=GB. The
MARCRBE2 option specified will then be used to translate the converted RBARs to
Marc.

MARCRBE2
Default = 3, SOL 600 only.

ID Determines the type of RBE2 used. The default should be used (parameter not entered)
with models comprised of solid elements or a mixture of solid elements and other types
of elements.
0 RBE2s will be simulated using Marc’s Servo Link. This option is best only for small
incremental deformations and rotations.
1 RBE2s will be simulated using Marc’s TYING type 80 for translation and Servo Link for
rotations. This option is capable of larger incremental deformations but requires small
rotational increments. The MARCRBE2=1 option is only available if all 6 DOF’s are
specified in the CM field (4) of the RBE2 entry.
2 RBE2s will be simulated using the new RBE2 element introduced into Marc Version
2003 for a 2D analysis.
3 RBE2s will be simulated using the new RBE2 element introduced into Marc Version
2003 for a 3D analysis.

Note: If RBAR, RROD or RTRPLT elements are found in the model and if MARCRBE2=2 or 3,
these elements will be converted to equivalent RBE2’s and used with the new Marc RBE2
element during the Marc execution (thus providing higher accuracy for large deformations
and/or rotations).

The default should be used (parameter not entered) with models comprised of solid
elements or a mixture of solid elements and other types of elements.

MARCRBE3
Default = 3 SOL 600 only.
Determines the type of RBE3 used.

Main Index
 816 MARCREVR
Parameter Descriptions

0 RBE3s will be simulated using Marc’s Servo Link. This option is best only for small
incremental deformations and rotations (see option 4 for a similar alternative).
2 RBE3s will be simulated using the new Marc RBE3 element introduced into Marc Version
2003 for a 2D analysis.
3 RBE3s will be simulated using the new Marc RBE3 element introduced into Marc Version
2003 for a 3D analysis. (Default)
4 Same as MARCRBE3=0 except that all MPC’s due to RBE3 will be placed ahead of all
other MPC’s. This option might improve the Marc solution for versions where Marc has
not implemented AUTOMSET logic (those versions prior to MSC.Nastran 2005 r3).

MARCREVR
Default = 0
Specifies that all rigid surfaces need to be modified.

0 Rigid contact surfaces are correct as entered and no changes are made by the translator.
(Default)
1 All rigid surfaces are entered backwards and will be reversed.

MARCREVRX
SOL 600 only.
Determines whether coordinates for NURBS2D (BCBODY) will be reversed or not if CQUADX,
CTRIAX, and/or CTRIAX6 elements exist.

0 Reverse the coordinates (Y becomes X, X becomes Y).

1 In addition to reversing the coordinates (option 0) all points are also reversed. For example,
if there are 4 points (1,2,3,4) they are reversed to (4,3,2,1). (Default)
-1 Do not reverse the coordinates.
-2 Reverse the coordinates for CQUADX and CTRIAX abut not for CTRIAX6.

MARCRIGD
Default = 0, SOL 600 only.
The parameter should only be entered if PARAM,MARMPCHK and/or PARAM,AUTOMSET options
fail during a Marc execution.

Main Index
 MARCSAME 817
Parameter Descriptions

0 All RBEi will not be converted to stiff beams or plates. (Default)

1 All RBEi will be converted to stiff beams or plates for the Marc input file using a stiffness
scale factor from parameter MARCRSCL. This parameter allows such elements to have
large rotations for versions of Marc which do not include large rotations of rigid elements.

Remarks:
1. This option may not be used if RBAR, RROD or RTRPLT elements are in the model. See
PARAM,MSTFBEAM for an alternative.
2. See PARAM,MARCSCLR to specify a scale factor for the “default” properties of these stiff
beams.

MARCSAME
Default = 0, SOL 600 only.
Determines whether SOL 600 runs with multiple subcase having the same LOAD ID or loads (see note
below) in more than one subcase will be processed or not. SOL 600 will usually run under such
circumstances but may get the wrong results.

Important: Do not use this parameter if the loading contains enforced displacements or the results may
be incorrect.

0 The job will be aborted before Marc is spawned with a “Severe Warning” message.
(Default)
1 The job will run to completion (if there are no other errors) and a standard Warning
message will be issued.

It is recommended that if the same loads are to be used in multiple subcases that each subcase have a
different LOAD ID. A typical file setup for SOL 600 should be setup in the following manner:
SOL 600,NLSTATIC PATH=1 STOP=1
CEND
DISP=ALL
STRESS=ALL
SPC=123
TEMP(INIT)=33
PARAM,MARCSAME,1
SUBCASE 1
LOAD=100
SUBCASE 2
LOAD=200
TEMP(LOAD)=300
BEGIN BULK
LOAD, 100, 1., 1.0, 1000, 1.0, 2000
LOAD, 200, 1., 1.0, 1000, 1.0, 2000

Main Index
 818 MARCSCLR
Parameter Descriptions

PLOAD4, 1000, 10, 20.0

PLOAD4, 2000, 20, 25.0
(Other Bulk Data entries)
ENDDATA

Note: In the above example if the Bulk Data LOAD entries are changed to:

LOAD,100,1.,1.0,1000,1.0,2000
LOAD, 200,0.9,1.0,1000,1.0,2000
The loads are the same before the overall scale factor (1.0 and 0.9, respectively) are applied
and PARAM,MARCSAME,1 is needed. However if the entries were as follows, it is not
needed because the loads before the overall scale factor is applied are different.

LOAD,100,1.,1.0,1000,1.0,2000
LOAD,200,1.0,0.9,1000,1.0,2000

MARCSCLR
SOL 600 only.
Sets property values for stiff beams when PARAM,MARCRIGD or PARAM,MSTFBEAM are used in
SOL 600.
The value of this parameter scales the “default” properties of stiff beams or plates if parameter
MARCRIGD=1. The “default” (unscaled) values for the stiff beams are A = 10, I = 100 (both directions)
J = 200, shear area = 5 and plate thickness of 1.5. Linear scaling is used for all areas and thickness, all
inertia terms are multiplied by the square of the Value entered.

MARCSETS
Integer, Default = 0, SOL 600 only.
Controls the type of sets used for the Marc input file element and node sets.

0 Sets will have the format DEFINE, ELEMENT, ... or DEFINE, NODE, ...
1 Sets will have the format DEFINE, ELSQ, ... or DEFINE, NDSQ, ...

Remarks:
1. PARAM,MARCSETS,1 can speed up certain large Marc jobs by a considerable amount.
2. The parameter may be set in RC files.

Main Index
 MARCSETT 819
Parameter Descriptions

MARCSETT
Default = 0, SOL 600 only.

0 The current environment is not printed. (Default)

1 The current environment is printed in the .f06 file. A user program named eodenv.f must
be compiled, linked and placed in the input file directory. The contents of eodevn.f
resembles the following:

Program eodenv
call system(“set”)
stop
end

MARCSINC
Default = 0, SOL 600 only.
This parameter controls how often a spline file is written if the spline option (analytical contact for
deformable bodies) is requested. If this parameter is not entered or if it is 0 or -1, then a file is not written.
If N is greater or equal to 1, then every nth time step is written. Spline files have the extension *.mfd
which may be processed by MSC Mentat.

MARCSIZ3, Value
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered here is the third value on Marc’s SIZING entry
representing the maximum number of elements.

MARCSIZ4, Value
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered here is the fourth value on Marc’s SIZING entry
representing the maximum number of grid points.

MARCSIZ5, Value
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered here is the fifth value on Marc’s SIZING entry
representing the maximum number of constrained degrees-of-freedom.

Main Index
 820 MARCSIZ6, Value
Parameter Descriptions

MARCSIZ6, Value
Default = Program determines value, SOL 600 only.

Value If entered, the integer value entered here is the sixth value on Marc’s SIZING entry
representing the maximum number of elements in the largest list of distributed loads (the
internal Marc to Nastran translator generates these one at a time, so this value is normally
1).

MARCSLHT
Default = 5, SOL 600 only.
Number of layers through the shell thickness used to integrate shell and beam elements. For linear
behavior, N=1 is sufficient. For most plasticity problems, N=5 is adequate. For extremely nonlinear
plasticity problems N=11 should be used. SOL 600 requires that N be 5 or larger. If N is entered with a
positive value less than 5, SOL 600 will set it to 5. To use values smaller than 5, enter N as a negative
number. The absolute value will be used, however the job may fail or results may be incorrect if the model
has plasticity.

Note: Use of PARAM,MARCDEF can effect the value of Marc’s SHELL SECT parameter if
PARAM,MARCSLHT is not entered. To eliminate SHELL SECT from the Marc file set N
to -9999.

MARCSOLV
Default = 8, SOL 600 only.
Determines the solver to use for Marc.

0 The profile solver will be used (solver 8 should normally be used instead)
2 The Sparse Iterative Solver will be used.
4 The Direct Sparse Solver will be used.
6 A hardware-provided solver will be used.
8 A sparse solver similar to the one used by Nastran will be used (Default)
9 The CASI element based iterative solver will be used.
10 The mixed direct/iterative solver will be used.
11 Pardiso direct solver (see param,mrthread)
12 MUMPS parallel direct solver (see param,mrthread)

Main Index
 MARCSPCC 821
Parameter Descriptions

Note: If any NLSTRAT entries are entered, the solver type must be specified using the IOLSVER
option of NLSTRAT rather than this parameter.

MARCSPCC
Default = 0 if no SPCD’s are entered or 2 if there are SPCD’s in the input.
Determines how SOL 600 will proceed if non-zero value enforced displacements are found in SPC
entries for multiple subcase models.

0 A fatal error will be issued and the user will be requested to change all non-zero value
enforced displacements to SPCD’s.
1 The job will continue without any changes (wrong results could be produced).
2 All displacements on SPC entries will be set to blank and the job will continue (will
usually produce the correct results if SPCD’s with the correct values are specified).

Remark:
Non-zero enforced displacements should always be specified using SPCD (not SPC) for SOL 600. It is
not necessary to specify SPC’s for degrees of freedom where SPCD’s are applied for SOL 600, but it will
not do not harm unless non-zero enforced displacements are specified on the SPC entries (either in
addition to being specified on SPCD’s or without having any SPCD’s). If there is only one subcases, the
non-zero enforced displacements may be specified on SPCD’s and/or SPC’s, however for multiple
subcases wrong results can result even if the displacements specified on the SPC’s and SPCD’s are the
same. The results will be even further off if the displacements are different. The remedy is to ensure that
the SPCD’s reflect the correct applied displacements, and then either remove the applied displacements
from all SPC’s or to set MARCSPCC=2.

MARCSTIFF, Time
Default = 1.0, SOL 600 only.

Time This parameter specifies what time matrices entered using PARAM,MARCFILi will be
used in a Nastran solution. The file may contain matrices at several times, but only the
matrices specified by the parameter will be used. This parameter is not usually used,
MRMTXNAM,NAME is used instead.

Main Index
 822 MARCSTOP
Parameter Descriptions

MARCSTOP
SOL 600 only.

0 Normal Marc execution when spawned from Nastran.

1 Marc will exit (with exit code 7) after phase 0 (corresponds to Marc parameter stop).

MARCSUMY
Default = 0, SOL 600 only.
Determines if the summary of maximum values is to be printed.

0 A summary of maximum displacements, stresses and strains will be printed in the Marc
output file. (Default)
-1 The summary of maximum values is not output.

MARCT16
Default = 2, SOL 600 only.
Controls generation of a Marc t16 file. MARCT16=0, Marc does not generate a .t16 output file.

-1 or 0 Does not generate a t16 file.

Parameter omitted generates a t16 file. All entries are controlled by the MARCOUT
Bulk Data entry, or if MARCOUT is not specified, by the default shown in option 2
below.
1 Generates a .t16 output file with the following post codes:
11 11,1 11,N 12 12,1 12,N 13 13,1 13,N 14 14,1 14,N
15, 15,1 15,N 16 16,1 16,N 17 17,1 17,N 18 18,1 18,N
7 7,1 7,N 27 27,1 27,N 301 301,1 301,N 321 321,1 321,N
341 341,1 341,N 401 401,1 401,N
Nodal: 1, 2, 3, 4, 5, 6, 35, 36, 37, 38, 39, 40, 46, 48, 51, 52
2 Generates a .t16 output file with the following post codes. (Default)
301, 301,1 301,N 341 341,1 341,N 47
Nodal: 1, 2, 3, 4, 5, 6, 34, 35, 36, 37, 38, 39, 46, 48

3 Generates a .t16 output file with the following post codes (op2, xdb, f06, punch results
cannot be made using this option):
301, 341 47
Nodal: 1, 2, 5, 6, 34, 35, 36, ,37, 38, 39

Main Index
 MARCT19 823
Parameter Descriptions

4 Generates a .t16 output file with the following post codes (op2, xdb, f06, punch results
cannot be made using this option):
301 341 47
Nodal: 1

Remarks:
1. This entry is used as an easy way to control which results are placed on Marc’s op2 file. All entries
can be overridden using the MARCOUT Bulk Data entry. For MARCOUT values of 1 and larger,
MARCOUT should be omitted for the input file. MARCOUT should not be used if
PARAM,MARCT16 is entered.
2. The frequency of output is controlled by the NLPARM or TSTEPNL Bulk Data entries (variables
INTOUT and NO respectively).
3. Items such as 341,1 and 341,N designate stresses at the bottom and top surfaces (for applicable
elements). Items such as 341 designate stress at mid-thickness.
4. When stress 341 is specified for models with composite elements, the value will be changed to
391 to obtain stresses in the fiber (layer) direction.
5. Consult Marc Volume C documentation for the meaning of the above blocks. Option 1 provides
most of the structural output anyone might want, option 2 provides total strain, Cauchy stress,
displacement and contact information at the top, center and bottom of surfaces. Option 3 provides
the information of option 2 but only at the center (not at the top and bottom).
6. It is necessary to generate a t16 file in order to produce op2, xdb, f06 or punch results.
7. Op2, xdb, punch and f06 results can only be created using option 1 and 2 although option 0 can
also be used if the selected outputs are the same as option 1 or 2.
8. If a Bulk Data VCCT entry is included in the model, nodal post codes 57-64 and 74 will be added
to any of the previous defaults if MARCOUT is not entered in the model.

MARCT19
Default = 0, SOL 600 only.

0 Marc does not generate a .t19 output file. (Default)

1 Generates a .t19 output file.

MARCTABL
Default = 0, SOL 600 only.
Determines if contact table is to be generated.

Main Index
 824 MARCTEDF
Parameter Descriptions

0 Contact tables will be generated for the main Marc input (phase 0) and for each subcase if
specified by the user (Default). When MARCTABL=0, each subcase may have a
BCONTACT Case Control command and a matching BCTABLE ID entry. In addition,
Marc’s “Phase 0” entry is supported by entering a BCTABLE with an ID of zero (or
1,000,000). Each separate BCTABLE will reference the BCBODY entries defined which,
in turn, reference BSURF entries. (Default)
1 No contact tables will be generated and all contact bodies (if any) will be placed in the main
input data section. Contact will thus be the same for all subcases. When MARCTABL=1,
there must only be one BCTABLE entry in the file. There must only be one BCONTACT
command in the Case Control and it must be above all subcases. The BCONTACT and
BCTABLE entry must have the same ID. The BCTABLE entry can reference several
BCBODY entries which, in turn, reference BSURF entries.

MARCTEDF
Character*8, no Default, SOL 600 only.
Enter the Marc nthcnt file name without extension. Use this option only if PARAM,MARCTEDN,1 is
entered (the file name without extension is limited to 8 characters). The characters “.nthcnt” will
automatically be appended to the name specified.

MARCTEDN
Default = 0, SOL 600 only.
Determines whether a thermal contact analysis will use the Marc jid.nthcnt file generated by this run or
use one input by the user.

0 Analysis uses the Marc jid.marc.nthcnt file generated in this run. (Default)
1 Analysis uses a Marc nthcnt file generated by the user or in a previous run.

Note: If MARCTEDN=1, PARAM,MARCTEDF below must be entered to specify the file name.

MARCTEMP
Default = 1, SOL 600 only.

0 The scratch files produced by Marc will be in the same directory as the Nastran input file.
1 The scratch files produced by Marc will be in the same directory as the Nastran scratch files.
(Default)

Main Index
 MARCTETT 825
Parameter Descriptions

Note: The Marc scratch files cannot be split.

MARCTETT
Integer, Default = 0, SOL 600 only.
Determines how CTETRA elements will be mapped to marc.

0 4-node or 10-node Nastran CTETRA elements will be mapped to the Marc tet-4 or tet-10
elements.
11 4-node or 10-node Nastran CTETRA elements will be mapped to Marc solid element type
7. for tet-10 elements, the mid-side nodes are neglected. the 4 CTETRA nodes
(N1,N2,N3,N4) are mapped to the 8 solid shell nodes as follows N1,N2,N3,N4,N4,N4,N4.
12 Same as MARCTETT=11 except debug is turned on (for the tetra conversion only)

Remark:
MARTETT should not be greater than zero for heat transfer or Herrmann elements.

MARCTIEC
Default = 1, SOL 600 only.

1 Transient Time Integration Error Check for Marc’s AUTO STEP method. A value of 1 turns
the check on. (Default)
0 A value of 0 turns the check off. Turn the check off to match Marc results for version prior
to Marc 2003 r1.

MARCTOL
Default = 0, SOL 600 only.
Determines the method of convergence tolerance.
If parameter MARCTOL=0, convergence tolerances are based on residuals (loads). If parameters
MARCTOL and MARCTVL are not entered, the tolerances are determined by TSTEPNL and/or
NLPARM Bulk Data entries. However, parameters MARCTOL and MARCTVL provide extra control
over these convergence tolerances particularly in the case where TSTEPNL or NLPARM specify more
than one convergence type (such as load and energy).

Main Index
 826 MARCTOTD
Parameter Descriptions

1 Convergence tolerances are based on displacement.

2 Convergence tolerances are based on strain energy.
4 Convergence is achieved when either residual or displacement satisfies the criteria.
5 Convergence is achieved when both residual and displacement satisfies the criteria.

MARCTOTD
Default = 0, SOL 600 only
Determines whether for SOL 600 dynamic analyses will use full table association.

0 Full table vs time association is not used. (Default)

1 Full table vs time association will be used

Remarks:
1. param,marctott,1 must also be set if MARCTOTD=1
2. This parameter may be set in RC files.

MARCTOTL
Default = 0, SOL 600 only
Determines whether total or incremental loads are used in a SOL 600 static nonlinear analysis.

0 Incremental loads are used. (Default)

1 Total loads are used

Remarks:
1. Warning - If MARCTOTL=1, MRFOLOW3=1 will be set if possible (see
PARAM,MRFOLOW3)
2. This parameter may be set in RC files.

MARCTOTT
Default = 0, SOL 600 only
Determines whether total loads, including pressures, gravity, spcd, etc., with associated tables are used
in a SOL 600 static or dynamic analysis (Remark 3.)

Main Index
 MARCTUBE 827
Parameter Descriptions

0 Total loads with tables are not used. (Default)

1 Total loads with tables are used

Remarks:
1. Warning - If MARCTOTT=1, MRFOLOW3=1 will be set if possible (see
PARAM,MRFOLOW3)
2. This parameter may be set in RC files.
3. For full table association, dynamic analyses require PARAM,MARCTOTD,1 to also be set.

MARCTUBE
Default = 0, SOL 600 only.
Determines whether CTUBE maps to Marc element 31 or 98 (Default = 0 if this parameter is omitted).

0 CTUBE elements map to Marc tube element 31 (see Remark) (Default)

1 CTUBE elements map to Marc element 98 (elastic beam)

Remarks:
Marc element 31 does not support thermal loading or creep. If the model contains thermal Loading or
creep (even if not applicable to the CTUBE elements, option 1 is always used.

MARCTVL, Value
SOL 600 only.

Value If parameter MARCTVL is entered, it must have a real value. The value entered is the
convergence tolerance used by Marc (see PARAM,MARCTOL). If parameters
MARCTOL and MARCTVL are not entered, the tolerances are determined by
TSTEPNL and/or NLPARM Bulk Data entries. However, parameters MARCTOL and
MARCTVL provide extra control over these convergence tolerances particularly in the
case where TSTEPNL or NLPARM specify more than one convergence type (such as
load and energy).

Main Index
 828 MARCUSUB, chr
Parameter Descriptions

MARCUSUB, chr
No Default, SOL 600 only.

chr chr is the name of a “user subroutine” to be included in the Marc run. chr is limited to 8
characters without the .f extension. This file must be located in the same directory as the
Nastran input data. The subroutine name must have all lowercase letters. chr should be in
lower case to prevent confusion. (Nastran will convert the file name to uppercase, but it
will be reconverted to lower case when Marc is spawned.) Any user subroutine available
to Marc may be specified. Multiple user subroutines must be combined into one file.

Restriction: The computer must have a Fortran compiler and Linker and the Fortran compiler must be
the same as used to create the original Marc executable (see the Marc installation manual). The Marc
input file does not as yet call out user subroutines, so manual editing of the Marc input file may be
necessary in some cases to invoke them. Existing regular Marc subroutines can be modified and handled
in the same manner if available to you.

Note: If more than one user subroutine is required, all should be combined into one file before
execution.

MARCVERS
SOL 600 only.
This parameter has been replaced by the following parameters:
param,mrconver
param,mrcontab
param,mrsprver

MARCWDIS
Default = 1, SOL 600 only.
Determines whether Marc parameter section DIST LOADS Is written or not. If any of the three values
for DIST LOADS are entered (see PARAM,MARCDIS2 PARAM,MARCDIS3 PARAM,MARCDIS4)
it will be written. If PARAM,MARCWDIS,1 is entered, it will be written. If PARAM,MARCWDIS,-1
is entered, it will not be written.

Caution: Nastran cannot estimate these values very well and produces overly conservative numbers
that sometimes leads to failure of the Marc run due to lack of memory. We suggest that the
user should use this parameter sparingly and enter the MARCDIS2, MARCDIS3 and
MARCDIS4 values for best Marc memory usage.

Main Index
 MARCWELD 829
Parameter Descriptions

MARCWELD
Default = 0 if this parameter is omitted, SOL 600 only.
Determines how CWELD/PWELD elements will be translated to Marc.

0 Add extra nodes and elements to simulate the weld.

1 Use Marc CWELD/PWELD formulation (available starting with MD Nastran R2 and
MSC Nastran 2007).

This parameter may be set in RC files.

MARELSTO
Default = 0, SOL 600 only.
Determines whether Marc’s parameter ELSTO will be created.

-1 ELSTO will not be created.

0 ELSTO will be created only for large models as determined by Nastran. The value of ELSTO
will be 40960 except for parallel runs (where a PARAMARC entry exists in the input file) in
which case ELSTO will not be created. (Default)
>0 ELSTO will be created with the value specified used as the Marc ELSTO parameter whether
or not the run uses parallel processing.

MARGPFEL
Default = 0, SOL 600 only.
Used to determine if Marc GRID FORCE output will occur by element, by node, or both ways.

-1 Output is by element only.

0 Output is by node only. (Default)
1 Output is by both element and node.

Notes: 1. This parameter effects the contents of the Marc jid.marc.grd file. Option 0 or 1 is
required for GPFORCE output in op2, xdb, punch, and/or f06 files.
2. This parameter can be set in RC files.

Main Index
 830 MARGPFOR
Parameter Descriptions

MARGPFOR
Default = 0, SOL 600 only.
Used to determine whether GPFORCE is active for SOL 600. A Case Control request GPFORCE must
be specified to obtain grid point forces (see note 4). The grid point forces are output from Marc on a file
named jid.marc.grd. The t16op2 program reads this file, puts the data on the f11 file along with
displacements, stresses, etc. After t16op2 finishes, the f11 file is brought into DBALL, from which
DMAP generated on the fly can produce op2, xdb, punch, or f06 output.

-1 GPFORCE is ignored (Default).

0 GPFORCE is output for the last time in the last subcase only.
1 GPFORCE is output at all times given in the .sts file.
N GPFORCE is output for times 1, 1+N, 1+2N, etc.

Notes: 1. This parameter can be set in RC files.

2. Output is available only in the new Marc jid.marc.gid file.
3. The Case Control GPFORCE request must be above all subcases, or the same
within all subcases.
4. The jid.marc.grd file can become very large if option 0 or N is not used.

MARFACEA
Default = 1, SOL 600 only.
Face number for “A” side of weld if welds are made of solid elements. Not used if welds involve plates
or shells.

MARFACEB
Default = 1, SOL 600 only.
Face number for “B” side of weld if welds are made of solid elements. Not used if welds involve plates
or shells.

MARFATAL
Default = 1, SOL 600 only.
Determines whether non-existent grid id’s for BCBODY entries will cause fatal errors or not.

Main Index
 MARHEATM 831
Parameter Descriptions

0 Non-existent grid ID in BCBODY entries will only cause warning messages. The grid ID
will be reset to zero and the job will continue. The results should be checked carefully. In
some cases this could results in an entire contact body being skipped.
1 Non-existent grid ID in BCBODY entries will cause FATAL ERRORS. (Default)

MARHEATM
Default = 0, SOL 600 only.
Determines whether a file named heatm.rc is necessary to run the second phase of SOL 600 heat transfer
initial contact job.

0 heatm.rc is not required. Defaults will be used. The defaults are scr=yes batch=no
mem=80mw
1 A heatm.rc file will be supplied by the user in the same directory as the original Nastran input
file. The heatm.rc can contain any information used by other rc files except that batch=no. If
the original Nastran input file is named jid.dat (or jid.bdf) and out=jid is specified, the final
output will be in files such as jid.f06, jid.op2, jid.xdb. If out=jid is not specified the final
output will be in files such as jid.nast.f06, jid.nast.op2, jid.nast.xdb.

MARHTPRT
SOL 600 only.
Controls heat transfer output in the Marc .out file.

0 Do not print any output except for summary table.

1 Print the nodal temperatures.
2 Print all possible nodal heat transfer output.

MARIBOOC
Default = 0, SOL 600 only.

0 Incremental backup data will be stored in memory. (Default)

1 For large problems, incremental backup data will be stored on disk. This option triggers
Marc’s parameter IBOOC.

MARIPROJ
Default = 0, SOL 600 only.

Main Index
 832 MARLDCMB
Parameter Descriptions

Flag to determine if auxiliary nodes of a CWELD will be projected on the model or not. (If this parameter
is not entered)

0 Nodes are not projected on to the model.

1 Nodes are projected on to the model.

MARLDCMB
Default = -1, SOL 600 only.
Determines whether extraneous loads in the input file will be filtered out at an early stage to save
computer time. This applies only to SOL 600,ID where ID=1, 3, 6, 101, 105, 106.

-1 Extra loads will not be filtered out.

2 Extra Bulk Data LOAD entries will be filtered out early in SOL 600 to save computer time.

Note: If PARAM,MARLDRMV,-1 is not entered, extra FORCE, MOMENT and PLOAD4

entries not used in the present analysis will also be filtered out early in SOL 600. Computer
time saving can be appreciable for certain models with many extra loads.

MARLDRMV
Default = 1, SOL 600 only.
Determines whether extraneous FORCE, MOMENT, and/or PLOAD4 entries in the input file will be
filtered out at an early stage to save computer time. This applies only to SOL 600,ID where ID=1, 3, 6,
101, 103, 105, 106.

-1 Extra loads will not be filtered out.

1 Extra Bulk Data FORCE, MOMENT, and/or PLOAD4 entries will be filtered out early in
SOL 600 to save computer time. (Default)

Note: This option will be ignored (same as PARAM,MARLDRMV,-1) if

PARAM,MARLDCMB,-1 is entered.

Main Index
 MARMPCHK 833
Parameter Descriptions

MARMPCHK
Default = -1, SOL 600 only.
Determines whether Marc parameter MPC-CHECK is written.

-1 MPC-CHECK is not written. (Default)

1 Apply the MPCs in the default order:
1. MPCs obtained from SERVO LINK option.
2. MPCs obtained from INSET option.
3. MPCs obtained from TYING, RBE2, or RBE3 options (the actual order follows from the
order of these options in the model definition block of the data file.)
4. MPCs obtained from CYCLIC SYMMETRY option.
5. MPCs obtained from CONTACT option.
Print a warning message if a tied degree of freedom is being used by a subsequent MPC.
2 Same as 1, but instead of warning, a fatal error message is printed and the analysis will stop
with exit 2001.
3 Try to rearrange the MPCs in such a way that a tied degree of freedom will not be used in a
subsequent MPC. If this reordering cannot successfully be completed, print a fatal error
message and stop the analysis with exit 2011.
-999 Skip MPC-CHECK entirely, prevent Marc’s error message “Exceed the max trial to order
RBE2/3”. This option should be used in conjunction with PARAM,AUTOMSET,YES only.
(Marc feature,3901 is set)

Note: This parameter can be set in RC files.

MARMPCID
Integer, Default = 1, SOL 600 only
Determines the ID of the MPC Case Control command for SOL 600 jobs using a CONTINUE=101 to
CONTINUE=159 (see SOL 600 Executive Control statement, CONTINUE option).

0 or 1 A line MPC=1 will be inserted in the Case Control (remark)

N A line MPC=N will be inserted in the Case Control (N must be between 2 and 9999)

Remark:
When models with contact and if BCPARA,INITCON,4 is specified, MPC’s for each increment will be
produced and placed in files named jid.marc.conmpc_xxxx where xxxx ranges from 0001 to the number
of increments in the solution. The ID of these MPC’s is usually equal to one. If for some reason it is not
one, the actual value may be specified by this parameter.

Main Index
 834 MARMPICH
Parameter Descriptions

MARMPICH
Default = 0, SOL 600 only.
Determines whether MPICH for Marc parallel processing on Windows 32-bit systems has been installed
or not.

0 MPICH has been installed. (Default)

1 MPICH has not been installed and will be installed as part of this Nastran run. The
installation requires a “data file” in the same directory as the Nastran input named mpich.dat
with the following three lines starting in column 1:

PC Login Name (Name you use to login to the PC)

Domain Name (if not part of a domain, enter local)
Password (the password you use to login to your PC)
This needs to be done only once unless the Nastran or Marc versions are changed, the login
name, domain or password is changed. All subsequent jobs should use MARMPICH=0 or
omit this parameter.

MARMTLCK
Default = 0, SOL 600 only.
Determines whether a check of various property-material combinations for SOL 600 will be made or not.

0 The checks will not be made. (Default)

1 Check will be made. These take extra computer processing time and for most models are not
required. The user should turn on these check if he is in doubt if any property-type of material
combinations entered into the model may be in error. Current check made are for the
following illegal combination.
PSOLID/MATHE (model should be PLSOLID/MATHE)
PSOLID/MATHP (model should be PLSOLID/MATHP)

MARNOCID
Default = 0, SOL 600 only.
SOL 600 does not support MCID defined by cylindrical or spherical coordinate systems. This parameter
determines whether MCID defined by cylindrical or spherical coordinate systems will be ignored or
“fataled out” for shell and solid elements.

Main Index
 MARNOSET, Name 835
Parameter Descriptions

0 The run will be “fataled out” if MCID defined by cylindrical or spherical coordinate systems
are found for shell or solid elements. (Default)
1 MCID defined by cylindrical or spherical coordinate systems for shell or solid elements will
be ignored.

MARNOSET, Name
No Default, SOL 600 only.

Name Character. If entered, this parameter will not write out a set with the specified name. This
is useful, when portion of the model specify sets that are not actually used in the present
analysis. Up to 20 of these can be specified.

MAROFSET
Default = 1, SOL 600 only.
Determines how beam and shell offsets are applied.

0 Extra grids and rigid elements will be created to model the offsets.
1 Marc will automatically handle offsets for beam and shell elements. No extra grids or
elements will be created. The offsets will be found in Marc’s GEOMETRY data. (Default)
2 Marc will automatically handle offsets for beam elements only.
3 Marc will automatically handle offsets for shell elements only.

Note: If MAROFSET is 1 or 2, the beam orientation can be specified using the CBAR/CBEAM
“BIT” flag. It is suggested that only combinations, GGG or BGG be used.

MARPLANE
Default = 0, SOL 600 only.
For composite structures described using PCOMP, together with CQUAD4, CQUADR, etc., it is not
possible to tell whether a standard 3D shell or a plane strain shell has been modeled. If MARPLANE is
set to 1, such composite models will be assumed to be plane strain (as if a PLPLANE property had been
entered rather than PCOMP).

Main Index
 836 MARPROCS
Parameter Descriptions

MARPROCS
Determines the number of domains to be used in a DDM parallel execution.
.

1 Use 1 processor.
2 Use 2 processors.
N Use N processors.

Remarks:
1. This parameter is not intended to be used by parallel jobs using several different machines.
2. This parameter and PARAMARC may not both be entered in the same run.
3. This parameter and PARAM,MRTHREAD may both be used in the same job.
4. The parameter may be used with most of the solver types except for the MUMPS solver (type 12).

MARRBAR2
Default = 1, SOL 600 only.
If MARCRBAR is set to 1, all CMA fields will be changed to 123456.

0 CMA field will remain as coded by user, Marc run may fail.
1 CMA field will be set to 123456. (Default)

MARROUTT
Default = -1, SOL 600 only.
Determines whether an inconsistent set of outputs between the Marc t16 file (selected using MARCOUT)
and standard Nastran output selected using Case Control requests (and param,post) is allowed or not.
.

-1 Inconsistent output is not allowed, if the outputs are inconsistent, the job will fatal early
before spawning Marc. (Default)
1 Inconsistent output is allowed. However, if the output requests are inconsistent, the job
may fail during the t16op2 conversion after Marc has finished.

Remark:
Nastran outputs in the op2, xdb, punch or f06 files are obtained by converting the Marc output from the
t16 file. If output is not available in the t16 file, or if it is in the wrong form, errors will occur during the
t16op2 conversion. For most problems, if op2, xdb, f06 and/or punch output is required, it is best not to
enter MARCOUT. In most cases MARCOUT should only be used if post-processing using the Marc t16
file is to be done.

Main Index
 MARSHRII 837
Parameter Descriptions

MARSHRII
Integer > 0, Default = 0, SOL 600 only.
Controls how the properties of bars added to the edges of CSHEAR elements when f1 or f2 of PSHEAR
is nonzero.
.

0 CBAR elements at the edges of CSHEAR elements (if any) will only have area (I1, I2, J
are all 0.0). See PSHEAR Remark 2 as to how the area of these bars is calculated.
>0 The value specified will be used to calculate I1, I2 and J from the area as
I1=I2=A/MARSHRII. J = 2.0 * I1

Remark:
This parameter must be entered in the Case Control above any subcases.

MARTET10
Integer, Default = 10, SOL 600 only
Controls how to treat badly shaped 10-node tetra elements in SOL 600 if renumbering the element does
not correct problems.

-1 Stop the analysis if all possible re-numbering options doe not correct the bad element. See
Remark 4.
0 Continue the analysis with the best re-numbering option and let Marc possibly fail with
inside out messages.
1 If all possible re-numbering options fail, change the bad tet 10 element to tet 4. See
Remarks 1 and 5.
2 If all possible renumbering options fail, deactivate the bad tet 10 element. (See Remarks
2., 3., and 5.)
3 Change the coordinates of bad tet 10 midside nodes to line at the midpoints of the vertices.
(See Remark 6.)

Remarks:
1. Changing bad tet 10 elements to tet 4 may ignore continuity on the edges of adjacent tet 10
elements unless they also get changed to tet 4 elements. If many tet 10 elements are changed to
tet 4 elements, the accuracy of the stresses could be inaccurate. In addition, if the elements are
used in contact, the same contact body can’t have mixed elements with midside and without
midside nodes.

Main Index
 838 MARTETIN
Parameter Descriptions

2. Deactivating bad tet 10 elements creates holes in the model. If only a few bad elements are
deactivated in a fine-grid model, the overall behavior will usually be nearly the same as if the
elements were good and remained in the model, however the stresses near the deactivated
elements may be too large. If many bad elements are deactivated, all analysis results will probably
be inaccurate.
3. Setting PARAM,MARTET10,2 will deactivate all types of elements for which Marc gets inside
out elements (not just tet 10 elements). This option maps to Marc’s 10-DEACT parameter.
4. This parameter is available starting with MD Nastran 2010. Prior to this release, only option 0 was
available.
5. Use options 1 or 2 with extreme care and only when all other alternatives including remeshing
using the gui have been exhausted.
6. If martet10=3, any midside nodes whose coordinates are changed and lie on the boundary of the
structure will redefine the exterior of the structure by a small amount. Also, if the element is used
in contact and the stress-free option is invoked, the coordinates may be changed again and the
elements may become badly shaped again.

MARTETIN
Integer, Default = 0, SOL 600 only.
Controls whether additional information messages are output to the .f06 file or not when param,martet10
is set to a positive value.

0 Do not output additional tet10 information messages.

1 Output additional tot10 information messages regarding checking of all tet10 elements.
(The .f06 file could be very large using this option.)

MARUPDAT
Default = 1, SOL 600 only.
If this parameter is omitted, the Updated Lagrange method will be used if plasticity is involved. Ensure
that all elements in the analysis are capable of using the Updated Lagrange method. If not, enter
PARAM,MARUPDAT,-1. The Updated Lagrange Method is more accurate for many problems and also
runs faster for some problems.

-1 The Total Lagrange solution procedure will be used when Marc is executed from Nastran.
1 The Updated Lagrange solution procedure will be used when Marc is executed from
Nastran. This corresponds to Marc parameter update. (Default)
2 The updated Lagrange solution with large rotations for beam elements. This corresponds
to Marc parameter (see Marc VOL C documentation for details): update,0,2

Main Index
 MARVFCUT 839
Parameter Descriptions

3 The following Marc parameter will be set, in which LARGE DISP need not be specified
elsewhere (see Marc VOL C documentation for details): update,0,2,1
4 The following Marc VOL C parameter will be set, in which case LARGE DISP need not
be specified elsewhere. (see Marc documentation for details): update,0,,1
5 The following Marc parameter will be set (see Marc VOL C documentation for details):
update,0,1

MARVFCUT
Default = 0.0001, SOL 600 only.
Controls the fraction of the maximum view factor that is to be used as a cutoff. View factors calculated
below this cutoff are ignored. (Used in SOL 600 radiation heat transfer only.)

MAUTOSPC
Default = -1, SOL 600 only.
Determines whether Marc AUTOSPC will be added.

-1 Do not add AUTOSPC. (Default)

1 Add AUTOSPC to Marc’s parameter’s section. It will remain throughout the run.
2000 Turn on AUTOSPC by adding the integer 1 to Marc’s model definition SOLVER option
2001 Turn on AUTOSPC by adding the integer 1 to Marc’s SOLVER option in subcase 1
2002 Turn on AUTOSPC by adding the integer 1 to Marc’s SOLVER option in subcase 2
...
2999 Turn on AUTOSPC by adding the integer 1 to Marc’s SOLVER option in subcase 999
3000 Turn off AUTOSPC by adding the integer 1 to Marc’s model definition SOLVER option.
3001 Turn off AUTOSPC by adding the integer 1 to Marc’s SOLVER option in subcase 1.
3002 Turn off AUTOSPC by adding the integer 1 to Marc’s SOLVER option in subcase 2.
...
3999 Turn off AUTOSPC by adding the integer 1 to Marc’s SOLVER option in subcase 999.

Main Index
 840 MAXIREVV
Parameter Descriptions

MAXIREVV
Default = 1, SOL 600 only.
Determines whether to reverse axisymmetric coordinates (x y y x) and reorder nodes in the elements
or not.

-1 Do not reverse coordinates and renumber elements

1 Reverse coordinates and renumber grid ID’s for each element. (Default)

Remark:
Experience has demonstrated that certain models require the -1 option and others require the +1 option.
The majority require the +1 option. If one of the options produces inside out messages in the first
increment or other error messages, switch to the other option.

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.

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 (p. 408) in the MSC Nastran Reference Manual.)

Main Index
 MBENDCAP 841
Parameter Descriptions

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.

MBENDCAP
Default = 1, SOL 600 only.
Determines how PBEND internal pressure will be treated.

-1 Stress stiffening and axial loading due to pressure is ignored

0 Stress stiffening and axial loading occurs (this usually happens with end caps)
1 Only stress stiffening occurs. (Default)
2 Stress stiffening and axial loading occurs for CBEND elements with any nodes having SPC
or SPC1 and stress stiffening occurs for all other CBEND elements regardless whether the
SPC/SPC1 is referenced above the subcase level or within a subcase.

MCNLPARM
Default = 1, SOL 600 only.
Determines whether to make all field 5 (KMETHOD) consistent if more than one NLPARM entry occurs
in the input stream. If mixed KMETHOD fields are provided for different NLPARM entries, SOL 600
can sometimes encounter difficulties.

-1 KMETHOD will not be changed to be consistent.

1 KMETHOD will be changed to be consistent with that used with the NLPARM entry with
the lowest ID. (Default)

Remark:
This parameter may be set in RC files.

MCON2D3D
Integer, Default = -1, SOL 600 only.
Controls whether a mixture of 2D and 3D contact will be allowed in a SOL 600 model. For most models
a mixture of 2D and 3D contact will fail but there are a few cases where it will run properly. The default
will stop the run should a mixture of 2D and 3D contact as specified in field 3 of the first BCBODY line
is found. PARAM,MCONF2D3D,1 will allow the job to continue but the job may fail later in the run.
.

0 Stop job with a FATAL ERRO if a mixture of 2D and 3D contact is found.

1 Allow job to continue if a mixture of 2D and 3D contact is found.

Main Index
 842 MCORDUPD
Parameter Descriptions

MCORDUPD
Default = 0, SOL 600 only.
Determines if the coordinates will be updated if one of the CONTINUE options is specified on the
SOL 600 Executive Control statement.

0 Original coordinates are used for the continue option. (Default)

1 Coordinates are revised to reflect the final position after the nonlinear analysis. These
updated coordinates are used in the continue option.

Remark:
If mcordupd=1, parampmarct19,1 is automatically set and jid.marc.t19 will be generated (jid.marc.t16
may also be generated if desired).

MCSSHLCK
Default = 1, SOL 600 only.
Case Control parameter that determines whether to check that the thickness direction of CSSHL elements
is in the direction pointing from grids 1-2-3-4 to 5-6-7-8 or not.

-1 Do not make the check.

1 Make the check. (Default)
2 Make the check only for 6-sided elements (looking like chexa) and ignore for 5-sided
elements (looking like cpenta).

Remark:
This parameter must be set in the Case Control above the first subcase.

MCSSHORR
Default = 1, SOL 600 only.
Case Control parameter that sets the orientation of the thickness direction of CEHXA converted to solid
shells.

-1 The smallest CEHXA direction will be determined and the element will be renumbered
such that the thickness of the renumbered elements points from grids 1-2-3-4 to 5-6-7-8
1 The thickness direction will be in the grid 1 to 5 direction (thickness points from grids 1-
2-3-4 to 5-6-7-8). (Default)

Main Index
 MDAREAMD 843
Parameter Descriptions

2 The thickness direction will be in the grid 1 to 2 direction (grid numbering that originally
was 1,2,3,4,5,6,7,8 will be changed to 1,5,6,2,4,8,7,3)
3 The thickness direction will be in the grid 1 to 4 direction (grid numbering that originally
was 1,2,3,4,5,6,7,8 will be changed to 1,4,8,5,2,3,7,6)
11 The thickness direction will be along the side closest to the basic X-direction
12 The thickness direction will be along the side closest to the basic Y direction
13 The thickness direction will be along the side closest to the basic Z direction.

Remarks:
1. This parameter must be set in the Case Control above the first subcase.
2. This entry is only used in conjunction with the CSSHLM entry only.
3. This entry should only be used if all elements converted to solid shells are CHEXA, none should
be CPENTA.
4. See the CSSHL entry for a description of grids 1 to 8.
5. For options other than mcsshorr=1 the material properties and material orientation direction must
be orientated properly.

MDAREAMD
Default = 1, SOL 600 only.
Option to modify or not modify all DAREA entries which are not associated with any other loads
(DAREA entries that supply the actual load).

-1 Do not modify any DAREA entries.

1 Modify all DAREA entries that are not associated with any other load entries and supply the
actual loading. (Default)

MDEFSEPP
Integer, Default = see below
This SOL 600 parameter allows an eaasy way to set the defaults for contact separation control. Since this
parameter may be placed in RC files, the user can set default separation controls appropriate to the type
of problems normally run and apply the same values to all models without having to enter them in the
bulk data for each run. These values are normally entered on the BCPARA entry. The form of
MDEFSEPP is as follows:
PARAM,MDEFSEPP,AABBBBCD
where AABBBBCD is a packed integer field comprised of the following 4 controls:

Main Index
 844 MDK4OPT
Parameter Descriptions

Values that
Standard can be
Variable Default Entered Max Digits Min Digits
AA NODSEP 5 0 to 99 2 0
BBBB MAXSEP 9999 0 to 9999 4 4
C ICSEP 0 0 to 3 1 1
D IBSEP 0 0 to 4 1 1

Remarks:
1. All values of AA, BBBB, C, D override the standard defaults.
2. NODSEP, MAXSEP, ICSEP, IBSEP entered on BCPARA override values on this parameter.
3. This parameter can be set in RC files.
4. Max digits is the maximum number of digits that can be entered.
Min digits is the minimum number of digits that must be entered if this parameter is used.
5. A common setting for moderately difficult separation problems is MDEFSEPP=5001004
AA=NODSEP=5
BBBB=MAXSEP=10
C=ICSEP=0
D=IBSEP=4
6. A common setting for more difficult separation problems is MDEFSEPP=2999934
AA=NODSEP=5
BBBB=MAXSEP=9999
C=ICSEP=3
D=IBSEP=4

MDK4OPT
Default = 1
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 = NO
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

Main Index
 MDOTM 845
Parameter Descriptions

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.

MDUMLOAD
Default = 0, SOL 600 only.

0 For subcases with no applied loads and enforced displacement or velocity of rigid contact
bodies, a small magnitude dummy load will be created. Without these dummy loads,
Nastran becomes confused and does not produce the correct contact information. If there
is only one subcase, the dummy loads are not necessary. (Default)
1 Dummy loads will not be produced for any subcase and rigid contact with enforced motion
may be incorrectly described.

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.

MECHFIX
Default = AUTO

Main Index
 846 MECHPRT
Parameter Descriptions

Control for fixing the massless mechanism problem. The new capability is provided automatically for
the default of this parameter, listed above. The new 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 new capability is blocked, and the eigensolution uses the pre MSC.Nastran 2001 rules, i.e.,
three failed shifts and a fatal exit. See also MMFIL, 856.

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.

MEXTRNOD
Default = 0, SOL 600 only.
Determines whether extra grids will be added to SOL 600 parallel analyses.

Main Index
 MEXTSEE,N 847
Parameter Descriptions

0 Extra grids will not be added. (Default)

1 Extra grids will be added so that all grids from 1 to the highest grid are defined this was
necessary for certain version of Marc prior to the 2005 version. All extra grids that are added
have coordinates of 0.0 in all three directions.

MEXTSEE,N
Default = 0, SOL 600 only, Case Control Parameter
Determines whether SOL 600 external superelement residual runs contain loads in the main input file or
not.

0 External Superelement residual runs will not contain any loads. (Default)
1 External Superelement residual runs will contain all loads.

MFASTCMP
Default = 1, SOL 600 only.
Determines default composite shell integration method.

1 Standard integration method is used. Failure, plasticity, thermal loads, etc. are all allowed.
(Default)
2 A “fast integration” through the thickness technique is used which ignores thermal strains,
plasticity, and temperature-dependent material properties (which should not be entered in
the model).
3 A “fast integration” through the thickness technique is used which only ignores plasticity.
Thermal strains and temperature-dependent materials are allowed.

Remarks:
1. To override the default integration method, use Bulk Data entry PCOMPF.
2. If option 2 is used and temperature loading is present in the model, the option will automatically
be re-set to 3.

MFEA5701
Default = 1, SOL 600 only.
Determines whether feature 5701 is written to the Marc file. When this feature is set to 1, it disables
default rotation checking set to 0.001, which was initially set for early versions of Marc when RBE2 and
similar elements were added because the 0.001 value proved to be responsible for convergence problems.
For models that need rotation checking, you can enter the value using the NLSTRAT variable RLROTT.

Main Index
 848 MFORCOR1
Parameter Descriptions

We recommend always using MFEA5701,1 to turn off the default 0.001 checking value in Marc whether
or not the value is entered using NLSTRAT RLROTT.

0 Rigid rotation checking of 0.001 is turned on.

1 Rigid rotation checking of 0.001 is turned off. (Default)

MFORCOR1
Default = 1, SOL 600 only.
Option to correct forces entered twice (at the same node) in multiple subcases. This is not commonly
found in the input files.

0 Do not correct the forces.

1 Correct the forces. (Default)

Remark:
This parameter can be set in RC files.

MFORDUPE
Default = 0, SOL 600 only.
Controls how duplicate forces encountered for the same load case are handled in SOL 600.

0 Forces will be translated to Marc as encountered even if duplicates are present. In the case
of duplicates (more than one set of forces for the same node in the same subcase), all forces
found will be translated directly to the Marc input. (Default)
1 If duplicates exist, only the last set of forces will be translated.

Note: To prevent confusion, it is suggested that duplicate forces not be used.

MFSKIPPP
Integer, Default = 0, SOL 600 only.
Controls memory near the end of SOL 600 translations will be freed or not.

Main Index
 MGAPINIT 849
Parameter Descriptions

0 Memory is freed.
1 Memory is not freed (can save computer time, and, in some cases may be necessary for
some models.)

MGAPINIT
Integer, Default = 0, SOL 600 only.
Controls whether CGAP elements are initially open or closed (during Marc increment zero).

0 Gaps are initially open.

1 Gaps are initially closed.

MGLUETOL
Real, Default = 1.0E-6, SOL 600 only
Determines the tolerance for the PERMGLUP option of the SOL 600 Executive Control statement for
situation where the primary method (same as SOL 101 with permanent glue) fails to find any glued
contact possibilities (for example, for edge contact will usually find no glued contact using SOL 101). If
not glued contact is found using the primary method a secondary method, which can sometimes take a
significant amount of computer time for large models is used. The second method evaluates all grids that
have the same coordinates as the grids within the tolerance specified by this parameter. They will be tied
together unless they have SPC’s, MPC’s or are grids attached to rigid elements.

MHEATSHL
Default = 0, SOL 600 only.
Determines whether a membrane or thick shell element formulation is used for heat transfer. This
parameter can be overridden by individual PSHELL entries. In the current release, the membrane
elements should not be used for thermal contact analysis.

-1 All “quad” elements in the model will have membrane capability regardless of MIDi values
on the PSHELL entries.
0 All “quad” elements in the model will have membrane capability. (Default)
1 All “quad” elements in the model will have thick shell capability (shell sect, 1).
2 Shells use 2 dof per node, linear variation of temperature through thickness (shell sect, 2).
3 Shells use 3 dof per node, quadratic variation of temperature through thickness (shell sect, 3).
>3 Shells use 2*n+1 dof per node (where ni is the value of MHEATSHL specified). (shell sect,
2*(n-2)+1)

Main Index
 850 MHEATUNT
Parameter Descriptions

Notes: 1. Membrane capability in heat transfer means that the temperature is constant
throughout the thickness, The MHEATSHL=0 option can be overridden by
entering a non-blank value for MID2, MID3 and/or MID4 on an applicable
PSHELL entry in which case the MHEATSHL=1 option will be used if no
MHEATSHL parameter is entered.
2. Post options will be added to be the same as the value for Marc’s shell sect. For
example, if shell sect, 3 is generated, post codes 9,1 9,2 and 9,3 will also be
generated.

MHEATUNT
Default = 2, SOL 600 only.
Specifies the units for heat transfer using SOL 600.

0 SI mm units used
1 SI m units used
2 US units used. (Default)

Note: This parameter is used by Marc’s ISOTROPIC (heat transfer) third datablock, fourth field.

MHEMIPIX
Default = 500, SOL 600 only.
Controls the number of pixels used in radiation heat transfer for SOL 600 using the hemi-cube method.

MHOUBOLT
Default = 0, SOL 600 only.

0 SOL 600 transient dynamics will use the single step Houbolt numerical integration
method. (Default)
1 SOL 600 transient dynamics will use the Newmark Beta numerical integration method.
2 SOL 600 transient dynamics will use the standard Houbolt numerical integration method.
7 SOL 600 transient dynamics will use the generalized alpha (Hilber-Hughes Taylor)
numerical integration method.

Main Index
 MHRED 851
Parameter Descriptions

MHRED
Default = NO
The default 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
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.

MINCLDSB
Integer, Default = 0, SOL 600 only
Determines whether the SB value in field 4 of MATF will be included or not in the stiffness formulation
of the model (Marc COMPOSITE datablock 3 field 4):

0 SB will not be included.

1 SB will be included.

Remarks:
1. For releases prior to MD Nastran 2010, SB was not included.

Main Index
 852 MINIGOA
Parameter Descriptions

2. If SB is included, Marc parameter TSHEAR will also be included.

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.

MINRECCC, N
Default = 0, SOL 600 only.

N Integer. Minimum number of iterations per load step. This is the same as MINREC on
the NLSTRAT entry. If no other NLSTRAT values are entered, it is easier to enter this
parameter. The value can range from 0 to 9. For certain problems, the value should be 2
or greater or accuracy will be poor.

Minimum number of iterations per load step. This is the same as MINREC on the NLSTRAT entry. If
no other NLSTRAT values are entered, it is easier to enter this parameter. The value can range from 0 to
9. For certain problems, the value should be 2 or greater or accuracy will be poor.

MINSOUTT
Default = 0, SOL 600 only
Determines elements that deform so much that they go inside-out in an analysis will be deactivated.

0 Issue an error message and terminate the job if an element goes inside-out. (Default)
1 Deactivate any element that goes inside-out and continue the analysis. This option is
particularly useful for models which allow failure (for example those using MATF).

Remark:
param,minsoutt,1 maps to Marc’s parameter IO-DEACT.

MINVASHF
Default = 1.0, SOL 600 only

Main Index
 MINVCITR 853
Parameter Descriptions

Inverse Power “auto shift” value. A new shift point (in frequency squared) is determined as the highest
frequency squared plus this entry times the difference between the highest and next highest distinct
frequency squared.

MINVCITR
Default = 40, SOL 600 only
Inverse Power method, number of iterations.

MINVCSHF
Default = 0.0, SOL 600 only
Inverse Power shift frequency in Hz.)

MINVCTOL
Default = 1.0E-5, SOL 600 only
Inverse Power convergence tolerance.

MINVFMAX
no Default, use MINVNMOD, SOL 600 only
Real. Inverse Power max frequency to extract in Hz.

MINVNMOD
Default = 5, SOL 600 only
Integer. Inverse Power max number of modes to extract.

MLDALLOW
Integer, Default = 0
Determines whether forces (FORCE, MOMENT, PLOAD4, etc.) are allowed in SOL 600 if their ID is
the same as the value N of any Case Control LOAD=N entry.

0 Forces with the same ID are not allowed.

1 Forces with the same ID are allowed.

Remarks:
1. MLDALLOW=0 is the only option available for most other Nastran solution sequences.

Main Index
 854 MLSTRAIN
Parameter Descriptions

2. MLDALLOW=1 was the only option available in SOL 600 prior to MD Nastran 2010.
3. MLDALLOW=1 cannot be used with PARAM,MNASTLDS if MNASTLDS>0.
4. This parameter can be set in RC files.

MLSTRAIN
Default = -1, SOL 600 only.
Corresponds to Marc’s “LARGE STRAIN” parameter and optionally allows large rotation of beams and
shells.

-1 Small strain, small rotation analysis is used. (Default)

1 Large strain and large rotation analysis of beams and shells is implemented in a way to
automatically select the best options for a large strain analysis based upon the element type
(see the following table).
2 Use large strain and large rotation analyses of beams and shells for hyperelasticity and
multiplicative plasticity with radial return mapping
11 Same as option 1 except beams and shells are limited to small rotations (see Remark 1.)
12 Same as option 2except beams and shells are limited to small rotations (see Remark 1.)

Element Type/ 1-Dimensional Plane Stress or Plane Strain or Plane Strain or

Material Model Membranes or Shell Axisymmetric, or 3- Axisymmetric, or 3-
Elements Dimensional Dimensional Hermann
Displacement Form Form
Conventional Updated Lagrange Updated Lagrange Updated Lagrange Updated Lagrange
elastic-plastic additive plasticity; additive plasticity; additive plasticity; multiplicative
no finite strain includes finite strain includes finite strain plasticity; includes
utilized constant finite strain
strain
Mooney, Ogden, Total Lagrange Total Lagrange Updated Lagrange Updated Lagrange
Gent, or Arruda-
Boyce
Foam Total Lagrange Total Lagrange Updated Lagrange Updated Lagrange;
incompressibility
neglected

Remarks:
1. Starting with MD Nastran 2010, if MLSTRAIN=1 or 2, feature,2103 will also be added to provide
the best large rotation solution of beam and shell models using updated Lagrange. To prevent
feature,2103 from being used MLSTRAIN can be set to 11 or 12 instead of 1 or 2 respectively if
large strain small rotation is desired.

Main Index
 MLSTRAN2 855
Parameter Descriptions

2. Starting with MD Nastran 2010, if hyperelastic materials are found in the model,
PARAM,MLSTRAIN,12 will be set automatically unless a different value of MLSTRAIN has
been set by the user.

MLSTRAN2
Integer, Default = 0, SOL 600 only
Determines how the LARGE STRAIN option is written in the Marc input file for SOL 600.

0 LARGE STRAIN, (other options if applicable)

1 LARGE STRA, (other options if applicable)

Remark:
Since SOL 600 writes the Marc input file using large-field free-format input either option will work
properly. If the input file is modified by hand and this entry is changed to fixed-format, the LARGE
STRA option must be used.

MMAT2ANI
Default = 2, SOL 600 only.
Determines how MAT2 will be mapped to Marc.

0 MAT2 will be mapped to Marc’s ORTHOTROPIC option.

1 MAT2 will be mapped to Marc’s ANISOTROPIC option.
2 MAT2 will be mapped as explained in the following note. (Default)

Note: The default, MMAT2ANI=2, maps MAT2 to Marc’s ORTHOTROPIC option if G13 and
G23 are both zero or blank and to Marc’s ANISOTROPIC option if G13 and/or G23 are
non-zero.

MMBOLTUS
Integer, Default = -1, SOL 600 only
Controls how the top and bottom nodes are placed in the Marc “tying 69” input when MBOLTUS is used
in a SOL 600 model.

Main Index
 856 MMEMDETT
Parameter Descriptions

-1 Same as pre-MD Nastran 2010 versions tying 69 node order is top, bottom, control
1 Reversed - tying 69 node order is bottom, top control

Remarks:
1. If it appears that a bolt preload may be backwards for bolts modeled using MBOLTUS, this
parameter may be entered to reverse the mpc equations internally generated in Marc by tying 69
instead of reversing the loads.
2. For the MBOLTUS entry to be consistent with the SOL 400 BOLT entry
PARAM,MMBOLTUS,1 is usually required.

MMEMDETT
Default = -1, SOL 600 only.
Determines the Nastran portion of SOL 600 determines how much usable memory is available just before
spawning Marc and informs Marc through the –ml flag. If Marc needs more memory than this value, it
will go out of core.

-1 Do not determine the amount of usable memory. (Default)

1 Determine the amount of usable memory and set the –ml Marc command line option to that
value

Remarks:
1. Marc can determine this memory, however the computations determine the amount of installed
memory and do not take into account memory used by the operating system or by other user
processes.
2. This parameter may be entered in RC files.

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.

MNASTLDS
Integer, Default = See Remark 1., SOL 600 only.
Option to determine complex forces using OLOADS datablock or the foes, moments, pressures, etc. in
the Nastran input file. Positive values of MNASTLDS may also significantly speed up the SOL 600
translation and, in the case of RFORCE, the marc portion of the run will also usually be faster.

Main Index
 MNASTLDS 857
Parameter Descriptions

-1 or 0 Loads for Marc are translated or calculated directly from the forces, moments, pressures,
etc. in the Nastran input file. (Remark 1.)
1 Complex loads and moments are obtained from the OLOADS datablock, pressures,
rforce and other distributed loads are translated from the values found in the Nastran
input. (Remark 3.)
4 Same as MNASTLDS=1 if the model has Bulk Data LOAD entries with more than one
term (L2, L3, … on the Bulk Data LOAD entry is defined), otherwise same as
mnastlds=0.
99 Same as MNASTLDS=1 regardless of whether complex loads or Bulk Data LOAD
entries with more than one term exist in the mode.
777 Same as MNASTLDS=99 except that all type of distributed loads (pressures, rforce, etc.)
will be converted to force and obtain from the OLOADS datablock. (Remark 5.)

Remarks:
1. Default=99 if any GRID entry has field 7 defined. Default=777 if there are multiple subcases and
RFORCE or PLOAD4 with continuation lines exist in the model or if any FORCE entry with
nonzero (or blank) field 4 is defined, otherwise the default is 4.
2. MNASTLDS=-1 (or 0) was the only option prior to MD Nastran 2010.
3. Complex loads are defined as those forces or moments whose grid appears more than once when
the Case Control and Bulk Data LOAD entries are evaluated. For example consider the following
situation:
….
SUBCASE 1
LOAD = 10
SUBCASE 2
LOAD = 20
BEGIN BULK
LOAD, 10, 1.0, 2.0, 1, 3.0,2
LOAD, 20, 1.0, 4.0, 1, 5.0,2
FORCE,1,51, ,1.0,0.0,0.0,100.0
FORCE,2,51, ,1.0,0.0,0.0,200.0
Although the force at grid 51 occurs for different load ID’s when combined using the LOAD
entries it actually occurs twice in each subcase. This is the simplest form of a complex load and
can be handled by either MNASTLDS option. However, some models will have much more
complex situation, even having different entries for the Fx, Fy and Fz directions. In such
circumstances, particularly if multiple subcases are involved MNASTLDS > 0 is recommended.
4. This parameter may be set in RC files.

Main Index
 858 MODACC
Parameter Descriptions

5. When MNASTLDS=777 pressures (and other forms of distributed loads) are converted to nodal
forces and the follower force effects will be lost. However, for multiple subcases the follower
force effects are not available in SOL 600 unless the loading is the same between subcases except
for a scale factor.

MODACC
Default = -1

0 Selects the mode acceleration method for data recovery in dynamic analysis. See
Formulation of Dynamic Equations in SubDMAP GMA (p. 369) in the MSC Nastran
Reference Manual for further discussion. If PARAM,SPARSEDR,NO is specified, then
PARAM,DDRMM,-1 must also be specified.
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.

MOFFCORE
Default = 1, SOL 600 only.
Determines how memory for PARAM,MARCOFFT above is to be allocated (for increased speed).

-1 Additional memory is not allocated.

1 Additional memory is allocated if available. (Default)

MOP2TITL
Default = 1, SOL 600 only.
Determines how titles are placed on the 146 word record for op2 output records generated by SOL 600.

Main Index
 MOUTRCOR 859
Parameter Descriptions

1 Standard titles will not be placed, however titles of the form “CQUAD4 STRESS FROM
MARC”, and similar titles for other element types, strains, displacements, etc. will be
written. This option is useful for certain postprocessors.
-1 Standard Nastran title, subtitles will be placed on op2 files generated by SOL 600. This
option is useful for postprocessors that require SOL 600 op2 data to be exactly in the same
format as that generated by other Nastran solution sequences. (Default)

Note: The SOL 600 op2 file follows that of SOL 109 as closely as possible.

MOUTRCOR
Integer, Default = 0, SOL 600 only
Determines whether SOL 600 OUTR options are disabled or not if any CORD2i references another
coordinate system.

0 Disable OUTR options

1 Do not disable OUTR options

Remarks:
1. In some cases, OUTR results are inaccurate if a CORD2i references another CORD.
2. CORD2i entries are not checked to see if they are actually used in the model.

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 and splining. For the value of "G", no redistribution occurs. The default is
a function of the solution sequence.
SOL 144 - Default = "F"
All other sequences - Default = "G"

MPCX
Default = 0
See OLDSEQ.

Main Index
 860 MPERMPRT
Parameter Descriptions

MPERMPRT
SOL 600 only.
Determines whether to print permanent glue MPC’s in the f06 file.

0 Do not print permanent glue MPC’s

1 Print permanent glue MPC’s

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

MQUATERN
Integer, Default = 2, SOL 600 only
Controls whether quaternions will be used for SOL 600 models with large rotation.

-1 Do not use quaternion “feature” for large rotation

1 Use quaternion feature,2103 which allows large rotations for total Lagrange or updated
Lagrange
2 Use quaternion feature,2105 which allows large rotations only if updated Lagrange is used

Remarks:
1. The use of MQUATERN = -1 allows backwards compatibility such that most models will obtain
the same results using MD Nastran R3 as were obtained using MD Nastran R3.
2. The use of MQUATERN = 1 is believed to yield the most accurate large rotation results for most
models.
3. With PARAM,MQUATERN,1 large rotation may be used both with updated Lagrange and total
Lagrange.
4. mquatern = -1 does not set Marc feature 2103 (feature 2105 is not set).
5. mquatern = 1 sets Marc feature 2103

MRADUNIT
SOL 600 only.

Main Index
 MRAFFLOR, N 861
Parameter Descriptions

Controls the units used in radiation heat transfer for SOL 600.

1 Degrees Celsius
2 Degrees Kelvin (default if parameter not entered)
3 Degrees Fahrenheit

Note: Degrees Rankin are not available.

MRAFFLOR, N
Default = N0, SOL 600 only.

N Integer. If N=0, a new AF_flowmat file containing temperature-dependent stress-strain

curves will be generated during the current Nastran execution and also used in the
spawned Marc run. If N=1, an existing AF_flowmat file will be used. The name of the
file is always determined by the value of PARAM,MRAFFLOW, but
PARAM,MRAFFLOT determines if other characters are added.

MRAFFLOT, N
Default = N0, SOL 600 only.

N Integer. If N=0, the file name as specified using PARAM,MRAFFLOW,Name will be

used with no changes except that all characters will be in lower case and the extension
“.mat” will be added. If N=1, the characters “asm_” will be added at the beginning of
Name, the first character of Name will be upper case (the other characters of Name will
be lower case) and the extension “.mat” will be added. This will make the AF_flowmat
file name compatible with many names in Marc’s AF_flowmat directory.

Main Index
 862 MRAFFLOW, Name
Parameter Descriptions

MRAFFLOW, Name
No Default, SOL 600 only.

Name Character. Name of a file containing temperature dependent stress versus plastic strain
curves in Marc’s AF_flowmat format. This file can be generated from the current
Nastran run using TABLEST and TABLES1 entries or a pre-existing file can be used
depending on the value of PARAM,MRAFFLOR. The extension “.mat” will be added to
Name. If this is a new file, it will be saved in the directory from which the Nastran
execution is submitted. If a pre-existing file is to be used, it can either be located in the
directory where the Nastran execution is submitted or in the Marc AF_flowmat
directory.

MRALIAS ID (MALIAS02, MALIAS03, etc.)

No Default, SOL 600 only. This parameter is not usually used.
The purpose of the parameter is to map the advance nonlinear element type selected by the internal Marc
translator in Nastran to a different type. For example, if the element type 75 for CQUAD4 is normally
used, a mapping to advance nonlinear element type 139 could be made. ID is a 6 digit number. The left
3 digits are the element type normally selected by the translator and the right 3 digits are the element type
to be mapped. In the above example, element type 75 is to be mapped to 139. The user would enter
ID=075139. If element type 165 is to be mapped to element type 1 (which is not a real case), ID=165001.
Consult Marc Volume B for a list of elements and their meaning. The user is responsible for ensuring
that the mapping selected is proper. There is a limit of 18 aliases that may be entered in any model. Since
Nastran can only accept one parameter with a given name, the second alias should be named
PARAM,MALIAS02 and the third PARAM,MALIAS03, etc. All original element types mapped must
actually exist in the model.

Remark:
These entries should only be used if the Marc GEOMETRY entries are identical for the original and new
element types.

Note: If you use one of the MRALIAS parameters, certain “parameters” in the Marc file may no
longer be correct. For example, an element originally capable of using the updated
Lagrange method may be aliased to one that must use the total Lagrange method. Such
conditions are not checked by the translator when you use alias and you will need to make
modifications to the Marc input file yourself to reflect them. To resolve this use
PARAM,MLSTRAIN.

The Bulk Data entry, ALIASM, is available and subsequent version are more powerful.

Main Index
 MRALLOCG 863
Parameter Descriptions

MRALLOCG
No Default, SOL 600 only.
Integer. The value entered here is the amount of memory (MB) allocated for general Marc memory when
Marc is spawned from Nastran. It specifies the initial allocation of “general memory”. This is used for
storing element stiffness matrices and part or all of the matrix solver workspace among other things.
Please note that element data like stresses and strains are not part of the general memory. Solvers 6, 8,
and 9 use the main part of the workspace in separate memory. Initial allocation of the general memory
can be used for avoiding reallocation (increase of the workspace). For parallel processing the amount
specified is the total for the job. It is divided by the number of domains used.

MRALLOCS
No Default, SOL 600 only.
Integer. The value entered here is the amount of memory (MB) allocated for Marc solver memory when
Marc is spawned from Nastran. It specifies the initial allocation of memory for solver 8. By giving a value
that is more than the maximum used during the run, one avoids that the solver workspace is increased
(reallocated). This can be particularly useful for large contact jobs, where additional memory may be
allocated due to contact. If the given workspace is less than what is needed, it is automatically increased.
This option is only for use with solver type 8. No check is done to see if solver type 8 is used in the job.
For parallel processing the amount specified is the total for the job. It is divided by the number of domains
used.

MRBE3SNG
SOL 600 only.
Option to check the singularity of RBE3’s in SOL 600. The real value entered is the singularity threshold
allowed. If MRBE3SNG is entered as a positive value, all RBE3’s with poor singularity values above the
value entered will be output in the jid.marc.out file as warning messages. If MRBE3SNG is entered as a
negative value, all RBE3’s with poor singularity values above the absolute value entered will be output
in the jid.marc.out file as error messages and the job will abort if they are found in increment zero, but if
they are found after increment zero the messages are warning messages and the job will continue.

Note: A “good” RBE3 element using the original geometry in increment zero could become
singular as the structure deforms in subsequent increments.

Main Index
 864 MRBEAMB
Parameter Descriptions

MRBEAMB
Default = 0, SOL 600 only.

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. (Default)
-1 Do not write equivalent radius (7th field is blank). This might be necessary for versions
of Marc earlier than 2003.

MRBEPARM, IJK
Default = 0, SOL 600 only.
IJK provides settings for Marc’s RBE parameter. If PARAM,MRBEPARM parameter is entered, Marc’s
RBE parameter will be set using this IJK If PARAM<MRBEAMPM is not entered,
PARAM,MARCRBE2 or PARAM,MARCRBE3 can be used to set Marc’s RBE parameter.
IJK is a combination of three variables. For example 311. Descriptions for individual entries are as
follows:

I Enter 3 or 6 to control the number of degrees-of-freedom. For the dependent grid

(reference grid) of each rbe2 or rbe3. The independent grids can have 3 or 6 dof and can
be different than what is specified by I.
J Enter 1 to use large displacement formulation of rbe2. Enter 3 to deactivate automatic
convergence test for rbe2.
K Enter 1 to use large displacement formulation of rbe3. Enter 2 to activate non-normalized
rotation constraint coefficient for rbe3.

Note: If IJK values other than specified above are entered, IJK will be set to zero and the
parameter will not be used. This parameter should not be entered unless there are rbe2’s or
rbe3’s in the model and they are to be used as such in Marc (rather than mpc or stiff beams).

MRBDYCVT
Default = 0, SOL 600 only.
Determines if CHBDYG is converted to CHBDYE for SOL 600 heat transfer.

Main Index
 MRBIGMEM 865
Parameter Descriptions

0 Do not convert. (Default)

1 Attempt to convert CHBDYG to CHBDYE. All grids specified by all CHBDYG entries
must reference actual conduction elements (CQUAD4, CHEXE, CTETRA, etc.) If even one
CHBDYG does not reference an existing conduction element, this parameter will be re-set
to zero.

Note: If MRBDYCVT=0, CHBDYG will normally result in point heat transfer loads rather than
distributed heat transfer loads.

MRBIGMEM
Integer, Default = 0, SOL 600 only.

N If N=0, memory allocations during loads translation phases are sized for computers with
limited memory and swap space (paging space). Some large problems and/or unusual
problems may not run. If this happens, use a newer modern computer with lots of
memory and disk space (and lots of swap space) and set N=1. Larger memory allocations
will then be available. This parameter is not usually required unless the available
memory is extremely small.

MRBUKMTH
Default = 2, SOL 600 only
.

1 Buckling modes will be computed using the Inverse Power method.

2 Buckling modes will be computed using the Lanczos method. Matrices must be positive-
definite for this option. (Default)
3 Use Lanczos if EIGRL is specified, Inverse Power if EIGB is specified.

Note: MRBUKMTH should be specified if EIGR or EIGRL is used for buckling unless
SOL 600,105 is the solution sequence. An alternative is to use ANALYSIS=BUCK. In
SOL 600, it is not possible to compute natural frequencies and buckling modes in the same
run. If ANALYSIS=BUCK is specified anywhere in the Case Control and if
PARAM,MRBUKMTH is omitted, param,mrbukmth=3 will be set automatically.

Main Index
 866 MRC2DADD
Parameter Descriptions

MRC2DADD
Default = 0, SOL 600 only.
Allows an offset to be added to all coordinates for 2D analyses so that X and Y will always be positive.

0 Offsets will not be added. (Default)

1 Offsets will be determined so that all Marc X and Y coordinates are positive (will exceed
0.1).

MRCKBODY
Integer, Default = 1, SOL 600 only.
Determines whether each BCBODY will be checked to see if the 2nd line is present when more than 2
lines exist. If the 2nd line is missing for BCBODY entries with more than 2 lines, errors can occur.

-1 BCBODY entries are not checked.

1 BCBODY entries are checked. If the 2nd line is not present for BCBODY entries having
more than 2 lines, a 2nd line will be added internally.

Remark:
This parameter can be set in RC files.

MRCKLOAD
Integer, Default = 0, SOL 600 only.
Controls whether each subcase has LOAD or DLOAD specified. SOL 600 will usually not run correctly
unless each subcase has some type of load (dummy or real). If a subcase only has a change in SPC, MPC,
or contact to obtain the correct results a dummy load is usually required.

0 No check is made to see if each subcase has a Case Control LOAD or DLOAD entry.
1 A check is made to see if each subcase has a Case Control LOAD or DLOAD entry and if
any subcase does not have such entry, a fatal error will be issued.

Remarks:
1. This parameter must be entered in the Case Control above any subcases.
2. This parameter may be set in RC files.

Main Index
 MRCONADD 867
Parameter Descriptions

MRCONADD
Integer, Default = 1, SOL 600 only.
Controls whether PARAM,MRCONVER,11 will be added automatically if any BCTABLE with FBSH,
BKGL and/or SEGS sub-headers is found. Also controls whether a BCTABLE with ID=0 will be added
if one is not present in the input file.
.

-1 Do not change value of PARAM,MRCONVER and do not add a BCTABLE with ID=0
if it is missing.
1 Change PARAM,MRCONVER to 11 if any sub-headers FBSH, BKGL and/or SEGS are
found. Also add BCTABLE=0 if there are other BCTABLEs and non with ID=0 exists.
2 Change PARAM,MRCONVER to 11 if any sub-headers FBSH, BKGL and/or SEGS are
found but do not add BCTABLE=0 if there are other BCTABLEs and none with ID=0
exists.
3 Do not change PARAM,MRCONVER to 11 if any sub-headers FBSH, BKGL and/or
SEGS are found. Add BCTABLE=0 if there are other BCTABLEs and none with ID=0
exists.

Remarks:
1. PARAM,MRCONVER,11 is necessary if BCTABLE sub-headers FBSH, BKGL and/or SEGS
exist in the model.
2. BCTABLE with ID=0 is sometimes necessary for certain contact problems. It never hurts to have
one as it will be ignored for those contact problems where it is not needed.
3. This parameter may be used in MD Nastran 2010 and subsequent versions. The behavior of
previous versions was the same as PARAM,MRCONADD,-1.
4. This parameter may be set in RC files.
5. This parameter, if used, must be placed in the Case Control above any subcases.

MRCONRES
Default = 0, SOL 600 only.
For restart runs, Marc will produce “continuous” results files (t16/t19) which contain the results of the
original run(s) as well as the results of the restart run. If Nastran postprocessing is requested to generate
op2, xdb, etc. files, they will also contain the results from prior runs as well as the restart run.
MRCONRES=1, output results files will contain the results of the restart run only.

MRCONTAB
Default = 0, SOL 600 only.
Determines whether CONTACT and CONTACT TABLE for SOL 600 use table-driven form or not.

Main Index
 868 MRCONUSE
Parameter Descriptions

0 Do not use table-driven form. (Default)

11 Use table-driven from of CONTACT and CONTACT TABLE

Remarks:
1. If MRCONTAB=11 then MRCONVER must also be set to 11
2. This parameter should is not necessary for SOL 600 heat transfer analysis and should not be set

MRCONUSE
Integer, Default = 0, SOL 600 only
Determines which increment for which contact MPC’s will be used for SOL 600 jobs using a
CONTINUE=101 to CONTINUE=159 (see the SOL 600 Executive Control statement, CONTINUE
option).

0 The last increment will be used (remark).

N Increment N will be used.

Remark:
When models with contact and if BCPARA<INITCON,4 is specified, MPC’s for each increment will be
produced and placed in files named jid.marc.conmpc_xxxx where xxxx ranges from 0001 to the number
of increments in the solution. This parameter allows the user to specify which increment will be used in
the continuation run spawned by the primary Nastran run after Marc finished. N must be less than or
equal to the number of actual increments.

MRCONVER
Default = 0, SOL 600 only.
Determines version of Marc to use for CONTACT and CONTACT TABLE for structural analysis.

0 Uses enhanced Marc version 9 (Marc 2001 with added fields).

11 Users Marc version 11 (Marc 2005).

Remarks:
1. This parameter only affects contact and only options 0 and 11 are available. It is not needed unless
BCTABLE with FBSH and/or BKGL is entered.
2. This parameter may be set in RC files.

Main Index
 MRCOORDS 869
Parameter Descriptions

3. If PARAM,MRCONVER,11 is entered it is usually also necessary to enter

PARAM,MRSPRVER,11.

MRCOORDS
Default = 0, SOL 600 only.
Determines whether Marc COORD SYSTEM will be added if any CORD1i or CORD2i entries are in the
model and if CBUSH elements, orientation vectors or other items requiring coordinate system
transformation are present in the model or if PARAM,MRPLOAD4,2 is entered which signifies that
PLOAD4 with continuation entries with CID, N1, N2, N3 are to be taken into account in the model.

0 Add Marc COORD SYSTEM. (Default)

1 Do not add MARC COORD SYSTEM

MRCQUAD4
Default = 75, SOL 600 only.
Controls the “Default” advance nonlinear element type for CQUAD4 elements in SOL 600.

75 Advance nonlinear element type 75 is used. (Default)

139 Advance nonlinear element type 139 is used.

Note: Element 75 is capable of thick shell behavior and element type 139 is applicable to thin
shells.

MRCTRIA3
Default = 75, SOL 600 only.
Controls the “Default” advance nonlinear element type for CTRIA3 elements in SOL 600.

75 Advance nonlinear element type 75 with a duplicate node is used. (Default)

138 Advance nonlinear element type 138 with 3 nodes is used.

Main Index
 870 MRCWANGL
Parameter Descriptions

Note: Element 75 is capable of thick shell behavior and compatible with the default element 75
used for CQUAD4, but since one node is degenerate (repeated) stresses may not be
accurate. Element 138 is accurate for thin shell behavior but may not be accurate for thick
shell behavior. Currently there is no triangle thick shell in Marc.

MRCWANGL
Default = 0.0, SOL 600 only.
Angle in degrees over which to rotate the cross-section about the beam axis to obtain its final orientation.

MRDELTTT
Default = 3, SOL 600 only.
Determines how delta time is set for each “step” of a SOL 600 transient nonlinear analysis.

0 DTI=Ti/N
1 DTI=Ttot/N
2 DTi=min(Ttot/N, Ti/2.0)
3 DTi=min(Ttot/N, Ti/10.0) (Default)
4 DTi=min(Ttot/N, Ti/100.0)
5 DTi=min(Ti/N, Ti/2.0)
6 DTi=min(Ti/N, Ti/10.0)
7 DTi=min(Ti/N, Ti/100.0)

1. SOL 600 transient dynamics is run by taking each pair of points on the applicable TABLED1
entry for the applied forcing function as a step. For example, if the following TABLED1 is given,
the time steps will be as shown below:
TABLED1, 1
+, 0.0, 0.0, 1.0E-3, .2 4.0E-3, .3, 6.0e-3, -.3
+,1.0E-2, 0.0

Step Final Time Delta Step Time (Ti)

1 1.0E-3 1.0E-3
2 4.0E-3 3.0E-3
3 6.0E-3 2.0E-3
4 1.0E-2 4.0E-3

Main Index
 MRDISCMB 871
Parameter Descriptions

If the TSTEPNL entry for this model is (N=100, Ttot=1.0E-2)

DTi is the initial delta time (AUTO STEP (2,1) for the particular step, the six selections of
MRDELTTT would give for the DTi values shown in the table below. Note that option 3 gives at
least 10 points per step and the old option 0 is probably too conservative.

Time DTi for MRDELTTT

Final Step
Step Time (Ti) 0 1 2 3 4 5 6 7
1 1.0E-3 1.0E-3 1.0E-5 1.0E-4 1.0E-4 1.0E-4 1.0E-5 1.0E-5 1.0E-5 1.0E-5
2 4.0E-3 3.0E-3 3.0E-5 1.0E-4 1.0E-4 1.0E-4 3.0E-5 3.0E-5 3.0E-5 3.0E-5
3 6.0E-3 2.0E-3 2.0E-5 1.0E-4 1.0E-4 1.0E-4 2.0E-5 2.0E-5 2.0E-5 2.0E-5
4 1.0E-2 4.0E-3 4.0E-5 1.0E-4 1.0E-4 1.0E-4 4.0E-5 4.0E-5 4.0E-5 4.0E-5

2. If Dti is set using NLAUTO variable TINIT, this parameter will be ignored.

MRDISCMB
Default = 0 without gravity, =1 with gravity, SOL 600 only.
Determines whether distributed loads, such as pressure, are combined in the Marc input file into one list
if the magnitude of the distributed loads are the same. This parameter applies to MSC.Nastran 2005 only.
For previous MSC.Nastran versions, MRDISCMB was 1. Option 0 save Marc memory and processing
time.

0 Distributed loads with the same magnitude are combined.

1 All distributed loads are input individually. Must be used if multiple subcases with the same
loadings are present in the model.

Caution: This parameter should be used with caution. For multiple load cases, MRDISCMB=0 may
produce the wrong results particularly if gravity loading is present. MRDISCMB=1 must
be used if multiple subcases with the same loadings are present in the model.

MRDUPMAT
Default = 1 without gravity loading and -1 with gravity loading, SOL 600 only.
Controls whether to create duplicate materials for elements used by both the Marc pshell
(PARAM,MRPSHELL,1 or the smear option on the SOL 600, ID statement) or not. If the user knows in
advance that no materials are used by shells and any other types of elements, this step can be skipped to
same considerable computer time.

Main Index
 872 MRDYNOLD
Parameter Descriptions

1 Check for materials used by shells and other types of elements and create duplicate materials
if any are used by both.
-1 Do not check or create duplicate materials.

MRDYNOLD
Default = 1, SOL 600 only.
Determines whether dynamic loads created by SOL 600 are the same as in MD Nastran R3 (and MSC
Nastran 2008) and prior releases or uses a new calculation method.

-1 Dynamic loads are the same as in MD Nastran R3 (and MSC Nastran 2008) and prior
releases.
1 Dynamic loads are “total loads” and may be more accurate for multiple subcases. (Default)

MREIGMTH
Default = 1, SOL 600 only.

1 Eigenvalue analysis will be done in Marc using the Lanczos method. (Default)
0 Eigenvalue analysis will be done in Marc using the inverse power sweep with double
eigenvalue extraction.
3 Eigenvalue analysis will be done in Marc using the inverse power sweep with single
eigenvalue extraction.

MREL1103
Default = 0, SOL 600 only.

0 Maps CQUAD4 to Marc’s element type 11 for plane strain problems. (Default)
3 Maps CQUAD4 to Marc’s element type 3 for plane stress problems.

MRELRB
Default = 0, SOL 600 only.

Main Index
 MRELSPCD 873
Parameter Descriptions

0 If BCMOVE with the release option is specified, IDRBODY (see the BCMOVE entry) will
refer to the actual IDs of BCBODY entries. (Default)
1 The release option of BCMOVE is used, IRDBODY (see the BCMOVE entry) will be in the
order of occurrence of the BCBODY entries in the sorted Nastran Bulk Data file. For
example, if there are two BCBODY entries with ID 12 and 22, the MRELRB=1 option means
that you should specify IRDBODY on the BCMOVE entry using values of 1 and 2. If
MRELRB=0, the IRDBODY values should be 12 and 22.

MRELSPCD
Integer, Default = 0, SOL 600.
Controls whether SPCD for the second or subsequent subcase represents total (absolute) displacements
or incremental displacements (relative to the displacement at the end of the previous subcase). SPCD for
the first subcase is always total (absolute).

0 SPCD represents relative displacements (same as SPCR) for subcases 2 and above
unless PARAM,MARCTOTT,1 has been set, in which case the SPCD’s represent
absolute displacements.
1 SPCD represents absolute displacements for subcases 2 and above (relative
displacements for subcases 2 and above must be entered using SPCR).

Remarks:
1. This parameter may be set in RC files.
2. PARAM,MRELSPCD,1 will automatically set PARAM,MARCTOTT,1 which means total loads
using table-driven input will be used in the analysis. This is the only way total (absolute)
displacements for subcases 2 and above can be used in Marc.
3. The behavior of SPCD prior to the MD Nastran 2010 release was to consider SPCD as relative
displacements for subcases 2 and above.

MRENUELE
Default = -1 if parameter is not entered and MRENUELE is not entered on the SOL 600 statement,
SOL 600 only.
It is best if MRENUELE is specified in the SOL statement. Some models will not have memory allocated
properly if this parameter is placed in the bulk data.

Main Index
 874 MRENUGRD
Parameter Descriptions

-1 No renumbering will occur (suggested for models with largest element number less than
approximately 20000). (Default)
1 All elements will be renumbered and the new numbers will be used in the Marc analysis (see
Remark 4.)
2 All elements will be renumbered, the new numbers are used internally during translation
however the original element numbers will be used in the Marc input file and Marc analysis.

Remarks:
1. This parameter can be set in RC files or on the SOL 600 statement.
2. To use models where the maximum element number is greater than 9,999,999 this parameter must
be set on the SOL 600 statement (see MRENUELE on the SOL 600 statement).
3. MRENUELE should not be set both on the SOL 600 statement and as a parameter.
4. For MRENUELE=1 an equivalence list of original and re-numbered element numbers is output
on file elenum.txt.

MRENUGRD
Default = -1 if parameter is not entered and MRENUGRD is not entered on the SOL 600 statement,
SOL 600 only.
It is best if MRENUGRD is specified in the SOL statement. Some models will not have memory
allocated properly if this parameter is placed in the bulk data.

-1 No renumbering will occur (suggested for models with grid IDs less than approximately
20000). (Default)
1 All grid IDs will be renumbered and the new numbers will be used in the Marc analysis (see
Remark 4.)
2 All grid IDs will be renumbered, the new numbers are used internally during translation
however the original element numbers will be used in the Marc input file and Marc analysis.

Remarks:
1. This parameter can be set in RC files or on the SOL 600 statement.
2. To use models where the grid ID is greater than 9,999,999 this parameter must be set on the
SOL 600 statement (see MRENUGRD on the SOL 600 entry).
3. MRENUGRD should not be set both on the SOL 600 statement and as a parameter.
4. For MRENUGRD=1 an equivalence list of original and re-numbered grid IDs is output on file
gridnum.txt.

Main Index
 MRENUMBR 875
Parameter Descriptions

MRENUMBR
Default = 0, SOL 600 only.
Determines if both grid and element IDs for SOL 600 will be renumbered or not.
)

0 No renumbering will occur (suggested for models with largest grid ID less than
approximately 20000). (Default)
1 All grid and element IDs will be renumbered and the new numbers will be used in the Marc
analysis. An equivalence list will be output on file grdid.txt
2 All grid and element IDs will be renumbered internally during translation, however the
original element numbers will be used in the Marc input file and Marc analysis.

Remarks:
1. This parameter can be set in RC files or on the SOL 600 statement.
2. To use models where the grid ID is greater than 9,999,999 this parameter must be set on the
SOL 600 entry (see MRENUMBR on the SOL 600 statement).
3. MRENUMBR should not be set both on the SOL 600 statement and as a parameter.
4. For MRENUMBR=1 an equivalence list of original and re-numbered grid IDs is output on file
gridnum.txt.

MRESTALL
Default = 1, SOL 600 only.
Controls rotational restraints for solid element-only models.

0 SPCs for DOFs 4-6 will be ignored if entered in the Nastran file
1 SPCs for DOFs 4-6 will be included if entered in the Nastran file. (Default)

Note: This option might produce an input-data error in the Marc run but is sometimes required if
RBEs or other special items are included in the model.

MRESULTS
Default = 0, SOL 600 only.
If MRESULTS is set to 3, postprocessing of a previously-generated Marc t16 file to a results-only op2
file (normally called an f11 file) will be accomplished. OUTR=f11 and STOP=3 should also be set on the
SOL 600 command line. This capability is available starting with MSC.Nastran 2004.1.0. If

Main Index
 876 MREVPLST
Parameter Descriptions

MRESULTS=0 the t16 file from the current job will be processed if requested by OUTR options on the
SOL 600 statement.

MREVPLST
Default = -1, SOL 600 only.
Determines whether 2D plain stress triangular element node numbers will be reversed or not.

-1 or 0 Do not reverse the node numbers

1 Reverse the node numbers

MRFINITE
No Default, SOL 600 only.
Controls Marc’s FINITE parameter. If entered, with an integer value of 1, Marc’s FINITE option will be
employed. If this option is entered, parameters MRFOLOW1, MRFOLOW3 and MARUPDAT should
also be entered. Other parameters to be considered are MARCDILT, MARCASUM and LGDISP.

MRFOLLOW
Default = 0, SOL 600 only.

0 FORCE1, FORCE2, MOMENT1, MOMENT2 will act as non-follower forces. (Default)

1 Follower forces entered using FORCE1, FORCE2, MOMENT1, MOMENT2 will be
mapped to Marc’s new follower force option.
-1 Follower forces will be turned off even if requested to be on using other options. This is
sometimes necessary for multiple load cases where pressures are applied to different
elements in the different load cases.

MRFOLLO2
Default = 0, SOL 600 only.
Controls whether Marc’s follow for, 2 is used when multiple subcases are present.

0 Marc’s follow for, 2 will not be used when multiple subcases are present. (Default)
1 Marc’s follow for, 2 will be used when multiple subcases are present

MRFOLOW1
No Default, SOL 600 only.

Main Index
 MRFOLOW3 877
Parameter Descriptions

Controls the second field of Marc’s follow for, N, M, L parameter (in this case, value N). If entered,
options 1, 2, 3 and -1 are currently available. Enter:

0 If follower force due to distributed loads (pressure) is not to be considered.

1 If follower force stiffness due to distributed loads is not required.
2 If follower force stiffness due to distributed loads is to be included.
3 If the follower force for distributed loads is based upon the displacement at the beginning
of the increment, as opposed to the last iteration.
-1 If the undeformed geometry is required but total values of distributed loads are to be used
(not presently available)

MRFOLOW3
Default = 0 for statics and 1 for dynamics.
Controls the 3rd field of Marc’s follow for, N, M, L parameter (in this case, value M). This parameter is
normally set internally by SOL 600 and should not normally be set by users, please see the following
remarks.

Remarks:
1. Starting with MD Nastran 2010 and MSC Nastran 2009, MRFOLOW3 must be 1 for SOL 600
dynamics and if entered as zero for dynamics will be reset to 1. If the user enters dynamic loads
using MARCIN they should be in the form of total loads rather than incremental loads.
2. Starting with MD Nastran 2010 and MSC Nastran 2009, MRFOLOW3 must be 1 for SOL 600
statics if PARAM,MARCTOTL,1 is entered. IF PARAM,MRFOLOW3 is entered as zero when
PARAM,MARCTOTL,1 is entered, it will be reset to 1 if possible.
3. Starting with MD Nastran 2010 and MSC Nastran 2009, MRFOLOW3 must be 1 for SOL 600 if
PARAM,MARCTOTT,1 is entered. If PARAM,MRFOLOW3 is entered as zero when
PARAM,MARCTOTT,1 is entered, it will be reset to 1 if possible.

MRFOLOW4
SOL 600 only.
Controls the 4th field of Marc’s follow for N, M, L parameter (in this case, value L). This parameter is
normally set internally by SOL 600 and should not normally be set by users, please see the following
remark.

0 If follower force for point loads is not required. (Default)

1 If follower force for point loads is to be considered.

Main Index
 878 MRGAPUSE
Parameter Descriptions

Remark:
To activate follower forces (concentrated loads) PARAM,MRFOLOW,1 must be entered as well as the
forces using FORCE1, FORCE2, MOMENT1 and/or MOMENT2. PARAM,MRFOLOW4 should also
be set to one.

MRGAPUSE
Default = 0, SOL 600 only.
Determines whether Nastran CGAP elements will be approximated as Marc gap elements. The default is
to fatal SOL 600 analyses if CGAP elements are found in the model.

0 Do not translate Nastran models using Nastran CGAP elements.

1 Translate Nastran models using CGAP elements. Marc gap elements are quite different than
Nastran elements and usually can’t be translated. In a few limited cases the Nastran and
Marc gap elements are equivalent. It is up to the user to determine whether the gap Nastran
elements can be used with SOL 600 or not. It is suggested that the user read Marc Volume
A and C and run small test models to access each particular use of gaps. If gaps can be used,
set PARAM,MRGAPUSE,1 and re-run the analysis. See also MARCGAPP, MARCGAPN,
and MARCGAPD,.

MRHERRMN
Default = 1, SOL 600 only.
This entry controls whether extra grid created for such items as hyperelastic Herrmann elements,
CWELD, et.c are output or not in the op2, f06, punch and/or xdb files. When Herrmann grids are output,
the displacement value is actually pressure which might be confusing when looking at an f06 file.

-1 Nodal output for extra grids is not provided.

1 Nodal output for extra grids is provided when the above files are requested. (Default)

MRHYPMID
Default = 0, SOL 600 only.

0 Hyperelastic models with mid-side nodes will be translated to Marc including the mid-side
nodes. Such models might run quite slowly. (Default)
1 Hyperelastic models with mid-side nodes will be translated to Marc leaving out the mid-
side nodes. These models will normally run faster, but the displacements of the mid-side
nodes will be zero and thus plots might look strange unless the model without mid-side
nodes is read into the postprocessor using the .marc.dat or .t16 files.

Main Index
 MRITTYPE, 879
Parameter Descriptions

MRITTYPE,
Default = 0, SOL 600 only.
Type of “constraint” used to connect the auxiliary nodes in all CWELDs.

0 RBE3 constraints will be used. (Default)

44 Kirchhoff constraints will be used
80 Combined RBE2 and RBE3 constraints will be used.

MRMAT8A3, Value
Default = 1.0, SOL 600 only.

Value If solid composites are modeled using MAT8, the third coefficient of thermal expansion,
ALPHA3 is not defined. ALPHA3 is calculated as ALPHA3=value * ALPHA1.

MRMAT8E3, Value
Default = 0.1, SOL 600 only.

Value If solid composites are modeled using MAT8, the third modulus, E3 is not defined. E3
is calculated as E3=value * E1.

MRMAT8N1, Value
Default = 0.5, SOL 600 only.

Value If solid composites are modeled using MAT8, NU31 is not defined. NU31 will be
calculated as NU31=value * NU12.

MRMAT8N3, Value
Default = 1.0, SOL 600 only.

Value If solid composites are modeled using MAT8, the NU23 is not defined. NU23 is
calculated as NU23=value * NU12.

MRMAXISZ
Default = Value in Marc include file in tools directory. SOL 600 only.

Main Index
 880 MRMAXNUM
Parameter Descriptions

If this value is entered, the integer value will be used on the command line to run Marc as -maxsize N
where N is the integer entered.

MRMAXNUM
Default = Value in Marc include file in tools directory. SOL 600 only.
If this value is entered, the integer value will be used on the command line to run Marc as -maxnum N
where N is the integer entered.

MRMEMSUM
Default = 0, SOL 600 only.
If MRMEMSUM=1, a summary of memory used by the internal Nastran-to-Marc translator will be
printed in the f06 file. Each line will contain four numbers (all are in 4-byte words). The first number is
the current memory request, the second the current memory (in addition to standard MD Nastran open
core), the third is the memory limit with zero meaning no memory limit, and the fourth is the high water
memory used so far by the Nastran-to-Marc translator and/or the t160p2 results conversion.
This parameter must be entered in the Case Control.

MRMTXKGG, Name
No Default, SOL 600 only.

Name Character. The NAME will be used for K2GG entries if entered. This parameter is
similar to MRMTXNAM. Either MRMTXKGG or MRMTXNAM can usually be
entered. The proper Case Control K2GG=NAME or K2PP=NAME will be selected
automatically by SOL 600 as follows: If the continue option involves dynamic response
analysis, K2PP will be used. If the continue option involves eigenvalue extraction or
static analysis, K2GG will be used.

MRMTXNAM, Name
No Default, SOL 600 only.

Main Index
 MRNOCOMP 881
Parameter Descriptions

Name Character. The NAME (field 2 of the DMIG entry) that will be used for DMIG values in
a spawned Nastran execution. For example, a common name used frequently is K2XX.
The Case Control command K2PP=Name will be added (in this example K2PP=K2XX
will be added) at the end of the Case Control of the spawned job. DMIG entries with
other names may exist on the file, but only those with NAME will be used in the spawned
execution. Either MRMTXKGG or MRMTXNAM can usually be entered. The proper
Case Control K2GG=NAME or K2PP=NAME will be selected automatically by
SOL 600 as follows: If the continue option involves dynamic response analysis, K2PP
will be used. If the continue option involves eigenvalue extraction or static analysis,
K2GG will be used.

MRNOCOMP
Default = 1, SOL 600 only.
Determines whether n-layer composite will be created if CORDM is defined on the PSOLID entry. This
allows output in material coordinate systems.

-1 Composite are not created (automatically activated for brake squeal). (Default)
1 1-layer composites are created.
N N-layer composites are created.

MRNOCOR
Default = 0, SOL 600 only.

0 Marc parameters ELASTICITY, PLASTICITY, UPDATE, LARGE DISP, CONSTANT

DILATATION will be automatically adjusted as recommended by the Marc developers.
1 the above parameters will be adjusted as determined to be the most consistent in correlation
between Nastran and Marc results for similar problems. This parameter should be entered
for buckling problems without plasticity. PARAM,LGDISP,1 should also be entered.

MRNOECHO
Default = 0, SOL 600 only.
Determines whether various outputs are placed in the Marc file.

0 Output is not suppressed (unless other entries are made to suppress it). (Default)
1 Suppress echo of nodes and element lists

Main Index
 882 MRORINTS
Parameter Descriptions

2 Suppress echo of boundary conditions

3 Suppress echo of nurbs data

Note: Enter any combination to suppress whatever is desired. To suppress all items, enter 123.

MRORINTS
Default = 99, SOL 600 only.
Controls orientation type for all solid elements in model (see Marc Volume C documentation,
ORIENTATION option).

1 Edge 1-2
2 Edge 2-3
3 Edge 3-4
4 Edge 3-1
5 Edge 4-1
6 XY Plane
7 YZ Plane
8 ZX Plane
9 XU Plane
10 YU Plane
11 ZU Plane
12 UU Plane
13 UORIENT Define transformation matrix with orient.f user subroutine
14 3D ANIO
91 Composite orientations will be Edge 1-2 for shells and 3D ANSO for solids and all non-
composites will use option 99. This option provides compatibility with earlier versions and
requires that all referenced coordinate systems by composite elements by rectangular.
99 All orientations are specified by coordinate systems (CORD2R, CORD2C, etc.). (Default)
101-112 Shell elements will have options 1-12, solid element will have option 14. (See Note 2)

Main Index
 MROUTLAY 883
Parameter Descriptions

Notes: 1. For solid composites, it is necessary to use the PSOLID entry as well as the PCOMP
entry. The PSOLID entry should normally have an entry in field 4 which specifies
a CORDi entry to use for the material alignment direction.
2. If option 101 is picked, shells will have edge 1-2 and solids will have 3D ANISO.
If option 102 is picked, shells will have edge 2-3 and solids will have 3D ANISO,
etc.

MROUTLAY
Default = -9999, SOL 600 only.
Indicates which shell or composite layers are to be output using the MARCOUT Bulk Data entry or by
default. Options are as follows:

-9999 All layers will be output. (Default)

-N Layers 1 and abs(N) will be output. (N must not be -1.)
-1 If the number of layers is less than 21, same as -N option. If the number of layers is greater
than 21, layers 1, 11, 21, 31, ..., N will be output.
0 Top and Bottom layers only will be output.
N Layers 1 through N will be output.
9999 Stresses at the element center only will be output (top and bottom are not output). This
option produces output with the assumption that the element has constant stress and strain
throughout the element.

Remarks:
1. Options -9999, -N, -1 and N also produce output at the element center.
2. MROUTLAY = 0 is the same as MROUTLAY = -1.
3. Do not enter this parameter if Bulk Data entry MLAYOUT is used.

MRPARALL
Default = 0, SOL 600 only.
Determines whether parallel processing for SOL 600 will be forced even if Nastran detects that it might
fail prior to spawning Marc.

Main Index
 884 MRPBUSHT
Parameter Descriptions

0 Spawn Marc in single-processor mode if Nastran detects Marc may fail in DDM mode.
(Default)
1 Spawn Marc in DDM mode even if Nastran detects Marc may fail. Leave any COORD
SYS entries in the Marc input file. If COORD SYS occur in the input file a DDM Marc job
may fail depending on the version of Marc being used. Please read the following remark
carefully before using this option.
2 Spawn Marc in DDM mode even if Nastran detects Marc may fail. Remove all COORD
SYS entries from the Marc input file. Please read the following remark carefully before
using this option.

Remark:
Known situations where Marc does not presently work in parallel are as follows:

When local coordinate systems are specified for the following:

Field 7 of any GRID entry.
Material coordinate systems (for example field 8 of CQUAD4).
If CBUSH uses coordinate systems.

For the following cases, this situation can be avoided and PARAM,MRPARALL does not need to be
entered:
If coordinate systems are used only for input (field 3 of the GRID entry) or just entered in the Nastran
input but not actually used, enter PARAM,MRCOORDS,1 to allow parallel processing to proceed.
If coordinate systems are only used for shell orientation (such as field 8 of CQUAD4) and if all such
coordinate systems are rectangular the following two parameters may be used to allow parallel
processing.
PARAM,MRCOORDS,1
PARAM,MRORINTS,1

MRPBUSHT
Default = 0, SOL 600 only.
Determines whether the requirement that when PBUSHT and contact occur in the same model,
BCTABLE must be specified for each subcase.
)

0 This requirement is enforced and the job will abort if BCTABLE’s are not entered
1 This requirement will be ignored and the job will proceed. Wrong results may occur and/or
the job may terminate later in the run.

Main Index
 MRPIDCHK 885
Parameter Descriptions

MRPIDCHK
Integer, Default = 1, SOL 600 only.
Controls whether a check for duplicate PIDs (property IDs) will be made in SOL 600.

-1 Do not make a check for duplicate PIDs.

1 Check for duplicate PIDs for structural elements - if any are found fatal the job.

Remarks:
1. This parameter may be set in RC files.
2. This parameter may be used in the MD Nastran 2010 and subsequent versions.
3. Duplicate PIDs will usually cause SOL 600 to fail or obtain the wrong results if the duplicates
occur for structural elements. It is usually acceptable to have a duplicate PID for a spring or
damper and for a structural element.
4. For versions prior to MD Nastran 2010, SOL 600 behaved as if PARAM,MRPIDCHK,-1 was set.

MRPELAST
Default = -1, SOL 600 only.
Determines whether PELAST will be skipped or cause the job to abort for SOL 600. SOL 600 does not
support PELAST. PBUSHT along with CBUSH and PBUSH should be used instead.

-1 SOL 600 jobs with PELAST that are referenced by any CELAS will abort.
1 PELAST entries will be skipped (ignored).

MRPLOAD4
Default = 2, SOL 600 only.
Determines whether continuation entry for PLOAD4 will cause the run to stop or if the continuation
line(s) are to be ignored.

0 The job will stop and a “Severe Warning” message will be issued.
1 The job will continue and the continuation lines will be ignored. A warning message will
be issued for the first few such entries.
2 CID, N1, N2, N3 and SOLR will be used. If SORL=LINE, the direction must be specified
using the CID, N1, N2, N3 fields for SOL 600. LDIR is ignored. (Default)
3 If any CSSHL elements are used, the pressures at the corners will be averaged and applied
to the entire element for all element types in the model.

Main Index
 886 MRPLOD4R
Parameter Descriptions

Remarks:
1. MRPLOAD4 should not be set to 2 for axisymmetric or plain strain analyses or if parallel
processing is used unless the “single file Marc input file” option is used. In some cases, but not
all, if MRPLOAD4=2 is set it will automatically be changed to zero one of these conditions exist.
2. See parameter MRPLOD4R for a companion control.
3. If any CSSHL elements are used, the pressures at the corners will be averaged and applied to the
entire element for all element types in the model.

MRPLOD4R
Integer, Default = 0
Determines how PLOAD4 pressures are treated in Marc when PARAM,MRPLOAD4,2 is set.

0 Pressures are treated as constant over the element if the pressure over the element varies,
the average is applied.
1 The Marc PLOAD4 style of loads is used which allows the pressures at the four corners
of a quad surface to be different.

Remark:
Versions of Marc including MDR3 and Marc 2008R1 and versions previous to these versions produce
incorrect results for some models using MRPLOD4R=1 if total loads (specified by
PARAM,MARCTOTL,1 or MARCTOTT,1) are used even if the pressure is the same at the four corners
of each quad element.

MRPLSUPD
Default = 1, SOL 600 only.
Determines whether Marc’s PLASTICITY,3 will be used or not for fast integrated composites or smeared
composites. Wrong results may be obtained if PLASTICITY,3 is used for these types of analyses even
if the plasticity is in non-composite portions of the model (Default = 1 if this parameter is omitted).

-1 Use PLASTICITY,3 if it is necessary for non-composite regions of the model

1 Replace PLASTICITY,3 with UPDATE (FINITE and CONSTATN DIALITATION are not
used. (Default)

Remark:
SOL 600 determines if smeared composites are used by the presence or lack of the SMEAR word on the
SOL 600,ID entry. Fast composites are determine if PARAM,MFASTCMP is set to 2 or 3 or if any
PCOMPF Bulk Data entries are present in the model.

Main Index
 MRPOISCK 887
Parameter Descriptions

MRPOISCK
Integer, Default = 2, SOL 600 only
Controls whether to check if a “bad” Poisson ratio has been entered in SOL 600 for MAT1 entries.

0 Do not check or correct “bad” Poisson ratios.

1 Check if Poisson ratio is negative or > 0.5, if so change it to 0.333.
2 Check if Poisson ratio is negative or > 0.5, if so change MAT1 to MATORT with all three E
values, the same as E for MAT1, all three G values the same as G for MAT1 and
v12=v223=v31=0.333

Remarks:
1. Current Marc versions do not allow isotropic materials with Poisson ratios having negative values
or values greater than 0.5. Previous Marc versions may have allowed this.
2. “Bad” Poisson ratios may occur if the user specifies E and G and leaves the Poisson field on
MAT1 blank.
3. If mrposick=1, the value of G will change. The value of E remains as originally specified.
4. If mrposick=0, the job will error out in the Marc phase of SOL 600.
5. This parameter is available starting the MD Nastran 2010.

MRPREFER
Default = 1, SOL 600 only.
Determines to output SOL 600 stresses on the t16 file in the standard Marc coordinate system for the
element or the “preferred” (layer) coordinate system when the model contains composite elements.

0 Stresses are output in the standard coordinate for the element

1 Stresses are output in the “preferred” (layer) coordinate system. (Default)

Remarks:
1. The standard coordinate system for solids is usually the basic coordinate system. The standard
coordinate system for shells and beams is usually the element coordinate. See Marc
documentation volumes A and B for further details.
2. Some versions of Patran cannot plot stresses for MRPREFER=1.

MRPRSFAC
Default = 0.0, SOL 600 only.

Main Index
 888 MRPSHCMP
Parameter Descriptions

This parameter is primarily used by Versions of SOL 600 prior to MD Nastran R2 and MSC Nastran 2007
which could not support different pressures at the different corners, pressures applied in directions that
are not normal to a surface or edge loads. This parameter is not necessary starting with the MD Nastran
R2 and MSC Nastran 2007 Version 5 if PARAM,MRPLOAD4,2 is set.
Factor by which pressure loads are scaled for SOL 600. Prior to MD Nastran 2006 R1 and MSC Nastran
2006, Marc was not capable of handling different pressure applied to different corners of a surface. In
other words, different values of p1, p2, p3, p4 on the PLOAD4 entry could not be handled.
Approximations can be made by assuming the pressure is uniform over the surface if the surface is small
enough. For SOL 600, the pressure (P) used by Marc is calculated using the following:
If p1 is not blank (or zero) regardless of the value of mrprsfac
P = p1
If mrprsfac is positive and p1 is blank or zero and one or more of p2, p3, or p4 are not zero or blank,
P=mrprsfac*(p1+p2+p3+p4) (This default if p2 or p3 or p4 are not zero or blank)
If mrprsfac is zero or negative,
If none of p1, p2, p3, p4 are blank or zero P=0.25*(p1+p2+p3+p4)
Otherwise,
p=(+/-)pp where pp is the value largest absolute value of p1, p2, p3, p4 and P will have the proper
associated sign.

Remarks:
1. If MRPLOAD4=2, MRPRSFAC is ignored and p1,p2,p3,p4 are used as entered.
2. If MRPLOAD4 is not 2, the default for mrprsfac varies from element to element. For each element
it is 1.0 divided by the number of Pi defined. For example, if only one of p1,p2,p3,p4 is defined,
the default mrprsfac is 1.0. If two of p1,p2,p3,p4 are defined, the default for mrprsfac is 0.5. If
three are defined the default is 0.33333 and if all four are defined the default is 0.25. When
PARAM,MRPRSFAC is entered, the value is the same for all elements with pressure specified
by PLOAD4.

Note: The default for mrpsfac varies from element to element. For each element it is 1.0 divided
by the number of Pi defined. For example, if only one of p1,p2,p3,p4 is defined, the default
mrprsfac is 1.0. If two of p1,p2,p3,p4 are defined, the default for mrpsfac is 0.5. If three
are defined the default is 0.33333 and if all four are defined the default is 0.25. When
PARAM,MRPRSFAC is entered, the value is the same for all elements with pressure
specified by pload4.

MRPSHCMP
Integer, Default = 0, SOL 600 only
If MRPSHELL=1 and there is a Marc PSHELL and composite for the same elements, this option controls
which will be used.

Main Index
 MRPSHELL 889
Parameter Descriptions

0 Use Marc composite and ignore Marc pshell. (Default)

1 Use Marc pshell and ignore Marc composite.
2 Do not make any corrections (this works for some models and fails for others)

MRPSHELL
Default = 0, SOL 600 only.
Used to control shell property specifications for Marc in SOL 600.

0 Classical GEOMETRY options will be used for all shell elements. (Default)
1 The Marc PSHELL option will be used, (can only be used with CQUAD4, CQUAD8,
CTRIA3, and CTRIA6).

Important: If MRPSHELL=1, shell elements will use Marc’s new PSHELL option. No materials used
by PSHELL may be referenced by other types of elements that this option has used. For
commonly used elements, duplicate materials will automatically be created by SOL 600 to
satisfy this criteria, however this can take considerable computer time. If the user knows
that no materials are used by both PSHELL and other properties, he can set
PARAM,MRDUPMAT,-1 to bypass the checking and creation for duplicate materials. To
speed up this process, set PARAM,MSPEEDPS,1. The Marc PSHELL formulation is more
stable if MID3=MID2. To set MID3=MID2, set PARAM,MARCMID3,1.

MRRBE3TR
Default = 0, SOL 600 only.
Controls whether all translations or all translation and rotations will be used for the reference degrees of
freedom or whether fewer than 3 are allowed.

0 Fewer then 3 reference degrees-of-freedom may be used. (Default)

3 All RBE3’s with REF C (field 5 of the RBE3 entry) not having 123 will have all translations
for the Marc REFC (field 5 of the Marc RBE3 entry) set to 123.
6 All RBE3’s with REF C (field 5 of the Nastran RBE3 entry) not having 123456 will have
all translations and rotationf or the Marc REFC (field 5 of the Marc RBE3 entry) set to
123456.

Main Index
 890 MRRCFILE, RCF
Parameter Descriptions

Remarks:
1. Marc frequently gives a singular tying message if there are not at least degrees of freedom 123 for
REFC. This sometimes results in poor singularity ratios and incorrect results for nonlinear
analyses. It also can prevent eigenvalues from being calculated.
2. It is recommended that option 3 or 6 be used for all SOL 600 analyses unless the user is certain
that REFC can have fewer then three dof’s for the particular analysis.

MRRCFILE, RCF
No Default, SOL 600 only.

RCF Character. Name of RCF file name (limited to 8 characters) used in conjunction with
another MSC Nastran run spawned from an original MSC Nastran run as specified by
the CONTINUE option on the SOL 600 command. The RCF file may contain any
information required (such as scratch=yes, exe=, etc.) as discussed in The nastran
Command, 2 of this guide. This rcf file does not have to use the same options as the
primary rcf file and should normally set batch=no as one of the options.

MRRELNOD
Default = -1, SOL 600 only.
Controls enforced displacements using SPCD.

0 For multiple subcases with SPCDs, the SPCDs from the previous subcase will be
released at the start of the current subcase.
1 SPC’s and SPCD’s from the previous subcase, not specified again in the current subcase,
will be released gradually during the current subcase.
-1 SPC’s and SPCD’s from the previous subcase, not specified again in the current subcase,
will be subtracted out. For example, if the previous subcase applied a SPCD of 0.1 to a
particular dof, the current subcase will apply -1.0. This will bring the displacement of
that dof to zero for the current subcase.

MRRSTOP2
Default = 0, SOL 600 only
Integer, Normally op2, xdb, punch and f06 output is not available for SOL 600 restart analyses. Setting
this parameter to 1 will allow the program to attempt to create one or more of these files. Only in limited
cases will the job be successful.

Main Index
 MRSCMOD 891
Parameter Descriptions

0 Do not attempt to create .0p2, xdb, punch, f06 output for restart runs (default if parameter
is not entered). (Default)
1 Attempt to create .op2, xdb, punch, f06 output as specified by other options.

MRSCMOD
Default = 0.0, SOL 600 only.
Solution scaling factor for linear buckling analysis (SOLs 600, 105) using the Lanczos method. If the
applied load in the first subcase is too large, the Lanczos procedure may fail. This number may be used
to scale the solution for numerical reasons. The collapse load will be output based upon the total load
applied.

Remark:
This parameter applies to rigid surfaces described using 4-node patches only.

MRSETNA1, N
Default = Program calculated, SOL 600 only.

N If this parameter is entered with N>0, the integer value entered will be used in Marc’s
SETNAME parameter section as the first value of SETNAME,N,M which is an
undocumented Marc option. N is the number of sets and M is the largest number of items
in any set. This entry is sometimes necessary if large lists of elements or nodes are used
to describe materials, properties or contact. Both MRSETNA1 and MRSETNA2 must be
included for either to take effect. This option is no longer required for MSC.Nastran
2005 r2 and subsequent releases.

MRSETNA2, M
Default = Program calculated, SOL 600 only.

M If this parameter is entered with M>0, the integer value entered will be used in Marc’s
SETNAME parameter section as the second value of SETNAME,N,M which is an
undocumented Marc option. N is the number of sets and M is the largest number of items
in any set. This entry is sometimes necessary if large lists of elements or nodes are used
to describe materials, properties or contact. Both MRSETNA1 and MRSETNA2 must be
included for either to take effect. This option is no longer required for MSC.Nastran
2005 r2 and subsequent releases.

Main Index
 892 MRSETNAM, N
Parameter Descriptions

MRSETNAM, N
Integer, Default = Program calculated, SOL 600 only.

N If this parameter is entered with N>0, the value entered will be used in Marc’s
SETNAME parameter section. This entry is sometimes necessary if large lists of
elements or nodes are used to describe materials, properties or contact. To get around a
Marc bug, if a computed setname value is large, Nastran will normally use the
undocumented form (see MRSETNA1). To prevent this, set N to -1.

MRSPAWN2, CMD
Default = Nastran, SOL 600 only.

CMD Character. Name a command to run D Nastran (limited to 8 characters single field or 16
for large field) used in conjunction with the CONTINUE options on the SOL 600
command. The Nastran run to be spawned will have the form:

CMD jid.nast.dat rcf=RCF

where file RCF is provided by PARAM,MRRCFILE,RCF. As an example, if CMD is
nastran, jid is myjob (original file myjob.dat) and RCF=nast.rc, the spawned run will
execute using:

nastran myjob.nast.dat rcf=nast.rc

Notes: 1. See PARAM*,HEATCMD for SOL 600 thermal contact heat transfer analysis.
2. CMD will be converted to lower case regardless of the case entered.

MRSPLINE
Default = 2, SOL 600 only.
Determines whether RSPLINE will be converted to CBAR or to MPC’s.

-1 RSPLINE will ignored (this option should only be used for model checkout)
1 RSPLINE will be converted to stiff CBAR elements
2 RSPLINE will be converted to MPC’s (Marc’s servo link) using the same equations used
by other Nastran solutions, except that the MPC’s are capable of large rotation. This
option requires somewhat longer translation times than the others but can save computer
time during the Marc execution phase. (Default)

Main Index
 MRSPRING 893
Parameter Descriptions

MRSPRING
Default = 0.0, SOL 600 only.
Specifies a stiffness value to be added to the main diagonal of each translational term of the stiffness
matrix. This option is useful in nonlinear static analysis with 3D contact of two or more separate
structures. Some of the pieces may not be grounded until contact occurs. By adding a small spring to
ground, such as K=1.0, these pieces are stabilized until contact occurs. This option applies to SOL 600
only and generates SPRINGS in the Marc input file for all nodes in the model and all three translational
degrees-of-freedom. IF K is entered as a negative number, the absolute value of K will be added to all 6
degrees of freedom of each grid in the model.
If the run is for heat transfer and K is positive, the spring will only be added to DOF 1.

MRSPRVER
Integer, Default = -1, SOL 600 only
Controls how CELAS and all other items map to the Marc input data.

0 Non-table form is used which generally means the Marc input file version is less than 11.
11 The table form for SPRINGS is used which requires two lines, the first with spring rates
and the second with table ID’s. PARAM,MRSPRVER,11 is usually required if
PARAM,MRCONVER,11 is entered.

MRSTEADY
Default = 1, SOL 600 only.
Controls the solution method for SOL 600 steady state heat transfer.

1 Marc STEADY STATE is used with TIME STEP of 1.0. (Default)

2 AUTO STEP is used.

Main Index
 894 MRT16STP, N
Parameter Descriptions

MRT16STP, N
Default = 0, SOL 600 only.
Enter in Case Control at the subcase level.

N Number of load increments to put on the t16/t19 files for each subcase when the AUTO
STEP method is used. The default of 0 puts all adaptive increments on the t16/t19 file.
If a value of N is entered, load steps for times=tmax/N will always be introduced into
the auto stepping process and the t16/t19 files will have outputs only at zero and those
times. This corresponds to field 1 of Marc’s AUTO STEP 2nd option and can also be set
using the NLAUTO option. If this is the only non-default NLAUTO variable to set, it is
more easily accomplished using this parameter. It is suggested that this parameter
always be used for large models and that N be 10 or greater, otherwise the size of the
t16/t19 files may become very large. This is especially important for Windows systems,
which presently has a 4GB limit in converting t16 to op2 files due to compiler
limitations.

MRTABLIM
Integer, Default = 0, SOL 600 only
Determines the maximum number or points in any TABLES1 used when tables are specified or MATHE
input.

-1 Unlimited, not recommended - If used could lead to numerical errors or program aborts
0 The limit is 500 points.
N The limit is set to N points. It is recommended that N does not exceed 500.

Remark:
If more than about 500 points are used for the tables, the curve filling processes used to determine the
material constants may encounter numerical errors and the program could abort. If a table with more than
the number points specified by this parameter is entered, the number of points will be reduced to the
specified limit so that numerical errors are unlikely to occur.

MRTABLS1
Default = 0, SOL 600 only.
TABLES1 stress-strain curves are converted to Marc WORK HARD stress-plastic strain curves
according to the following formulas for the value entered for MRTABLS1. In the formulas s is the stress
entered for TABLES1, e is the strain entered in TABLES1, S is the Marc WORK HARD stress and E is
the Marc WORK HARD Plastic strain. ey is the yield strain (sy/E) where EE is Young’s modulus, sy is
the yield stress. The first point of the Nastran curve will be skipped unless MRTABLS2 is set to 1.

Main Index
 MRTABLS2 895
Parameter Descriptions

0 (Default) S=s
E=e - ey
1 S=s(1+e)
E=ln(e+1)
2 S=s
E=e - s/E
3 S=s(1+e)
E=ln(1+e) - s/EE
4 S=s
E=e
5 S=s
E=ln(1+e)
6 S=s
E=ln(1+e-s/E)
7 S=s(1+e)
E=1n(1+e)-S/EE
8 S=s(1+E)
E=In(1+e)
9 S=s(1+E)
E=In(1+e)-In(1+ey)

Note: This parameter (like any other parameter) can only be entered once in an input file.

MRTABLS2
Default = 0, SOL 600 only.

0 TABLES1 stress-strain curves are converted to Marc WORK HARD stress-plastic strain
curves starting with the yield point. The first point will be skipped. (Default)
1 All points in TABLES1 will be connected to WORK HARD, however, the first plastic
strain will be set to zero if entered as non-zero.

Note: This parameter (like any other parameter) can only be entered once in an input file.

Main Index
 896 MRTABPRC
Parameter Descriptions

MRTABPRC
Integer, Default = 0, SOL 600 only
Determines the precision of stress-strain curves when translated from Nastran to Marc using SOL 600.

0 Standard precision (8 significant figures) is used.

1 Maximum precision (14 significant figures) is used.

Remarks:
1. This parameter is available starting with the 2010 entry. For MD Nastran 2010 it only applies to
stress-strain curves entered in conjunction with MATEP.
2. Prior to MD Nastran 2010, only option zero was available.
3. In most cases, the stress-strain values are not known to even 8 significant figures. However, if the
stress-strain is calculated from other data the extra precision might be useful.

MRTFINAL
SOL 600 only.
Real. In some dynamic problems, due to numerical roundoff an extra time step with very small initial and
final times is generated. If these times are too small, Marc sometimes will diverge even though the “final
time” actually desired by the user has been reached within reasonable accuracy. MRTFINAL is a value
below which this extra step will be eliminated to prevent excess computations and/or possible
divergence. If this parameter is not entered, the default value is 1.0E-8. This parameter is only used with
the AUTO STEP procedure. The ‘extra’ step will also be eliminated if the initial time step is less then
MRTFINAL/100.0.

MRTHREAD
Integer > 0, Default = 1, SOL 600 only.
Determines the number of threads to be used by the run. For multi-core processors speed can frequently
be gained by specifying a number of threads equal to the number of cores assuming the job has exclusive
use of the machine.
.

1 Use 1 thread.
2 Use 2 threads.
N Use N threads.

Remarks:
1. This parameter may only be used by solver types 8 (multifrontal direct sparse) and 11 (Pardiso).

Main Index
 MRTIMING 897
Parameter Descriptions

2. This parameter may be combined with PARAM,MARPROCS to use several processors each
using several threads.

MRTIMING
Default = 0, SOL 600 only.
If MRTIMING is 1, timing summaries for various portions of the internal Marc translator will be
provided in the f06 and log files.

MRTSHEAR
Default = 0, SOL 600 only.
By default, parabolic shear deformation is not included in the formulation of beam and shell elements if
there are no composite elements. If composite shell elements are present, parabolic shear deformation is
included by default. This parameter can be used to override these defaults.

1 Parabolic shear deformation is included in the formulation of beam and shell elements.
-1 or 0 Parabolic shear deformation is not included even if composite elements are present.
(Default)

Remark:
This parameter maps to Marc TSHEAR parameter.

MRUSDATA
Default = 0, SOL 600 only.
Determines whether user subroutine USDATA will be activated and if so the size of data.

0 User subroutine USDATA is not active in the current run. (Default)

N User subroutine USDATA will be active the in the current run and N is the number or
real*4 words needed for the data stored in common block /usdam/

Remark:
In addition to adding this parameter, the user must enter USDATA on Bulk Data entry USRSUB6.

MRVFIMPL
Default = 0.01, SOL 600 only.
Controls the fraction of the maximum view factor that is to be treated implicitly (contribute to operator
matrix). View factor values smaller than this cutoff are treated explicitly.

Main Index
 898 MRV09V11
Parameter Descriptions

MRV09V11
Default = 1, SOL 600 only.
Determines whether certain Marc “features” which are default in Marc “version 11” are added for
SOL 600-generated models that use “version 9”.

-1 Do not add the features.

1 Add the following features:
feature,4703 to speed up DDM jobs for one-processor jobs, it has no effect)
feature,5701 to disable old rigid rotation checking which was too stringent
feature,601 to improve contact
feature,5301 to improve deformable-deformable contact
feature,3201 to improve contact friction types 6 and 7‘
feature,5601 to improve thickness updating when the updated Lagrange method is used
feature5801 to improve in-plane bending of advance nonlinear element type 140
feature,6001 to improve concrete cracking analysis

Note: The above features are only used for certain problems, even though all are included with
the default option, they have no effect on models that do not use advance nonlinear element
type 140, feature 601 has no effect on models that do not have contact, etc.

MSIZOVRD
Default = -1, for small models and +1 for large models, SOL 600 only.
Determines whether Marc SIZING values for large models will be updated or not. Nastran includes Marc
directories with a file named “include” in the tools directory which includes a line MAXNUM=N, where
N is some value like 1000000. If the maximum number of nodes or elements in the model exceeds N,
memory overwrites or job aborts are possible unless either N is set larger than the actual max node or
element number in the model or the values are specified on the SIZING entry (field 3 for max element
and field 4 for max node).

-1 The sizing entry will not be updated (either the model is not large, MAXNUM in the include
file has been updated or parameters such as MARCSIZ3 and/or MARCSIZ4 have been
entered into the run to provide values that are large enough. (Default)
1 If the number of nodes or elements in the model exceeds 1,000,000 the sizing entry will be
updated to the max number of nodes and elements actually in the model. Extra nodes and or
elements to account for welds, pinned members, Herrmann elements, etc. will be included.

Main Index
 MSOLMEM, MBYTE 899
Parameter Descriptions

Note: For PARAM,MSIZOVRD large models are considered to be those with more than
1,000,000 nodes and/or elements.

MSOLMEM, MBYTE
Default = Program determined value, SOL 600 only.

MBYTE If entered, the integer value entered here is the 8th field of Marc’s SOLVER option, and
is the maximum memory in Mega Bytes that can be used by Marc’s solver types 6
(hardware provided direct) and 8 (multi-frontal direct, which is the default solver for
SOL 600) before going out of core. This parameter is the same as the MBYTE field on
the NLSTRAT entry any may be easier to enter as a parameter if no other NLSTRAT
values are needed.

Note: This parameter should only be entered if NLSTRAT entries are not required. If any
NLSTRAT entries are made, use the MBYTE field instead of this parameter.

MSPCCCHK
Integer, Default = 0, SOL 600 only
Effects multiple subcases where SPCD’s are applied and SPC’s potentially change between the subcases..

0 A comprehensive check is made to ensure that all SPC changes are accounted for all
subcases.
1 The check is not made. The check can take significant computer time and in most cases it is
not actually needed. If the user knows it is not needed, computer time can be saved by
turning it off.

Remarks:
1. This parameter is available starting with MD Nastran 2010.
2. This parameter may be set in rc files.

Main Index
 900 MSPCKEEP
Parameter Descriptions

MSPCKEEP
Default = 0, SOL 600 only.
Determines which SPC’s entered in the bdf file are retained in the Marc input file for 2D models.

0 Only retain those dof’s that are normally associated with the type of 2D analysis (normally
2 translations) (Default)
1 Retain all dof entered in the bdf file in the Marc input file.

Remark:
Some types of Marc 2D analyses support one rotation in addition to two translations and it is important
to restrain this rotation.

MSPEEDCB
Default = -1, SOL 600 only.
Determines whether CBEAM increased speed options are to be applied. This option may be necessary
for models with a large number of beams whose element IDs are large.

-1 No increased speed options are used for CBEAM. (Default)

1 cbeam.prp file will be standard unformatted rather than direct access. A small table to
provide the location of each entry is saved in memory.
2 The entire cbeam.prp file is saved in memory

Note: See param,marccbar,1 to change CBAR to CBEAM.

MSPEEDCW
Default = 0, SOL 600 only.
Determines whether CWELD elements will be translated to Marc in core (for increased speed) or out of
core. This parameter is needed if many CWELD elements are present in the model to avoid large
translation times.

0 Processed out of core. (Default)

1 Process in core.

Main Index
 MSPEEDOU 901
Parameter Descriptions

MSPEEDOU
Default = 1, SOL 600 only.
Determines whether speed enhancements are activated for the t16op2 conversion.

0 Speed enhancements are not activated.

1 Speed enhancements are activated which will place certain scratch data in memory. For large
models make sure enough memory is available (if PARAM,MSPEEDSE and/or
PARAM,MSPEEDP4 are used, there is probably sufficient memory unless there is a large
number of output “time” points. (Default)

MSPEEDP4
Default = -1, SOL 600 only.
Determines whether PLOAD4 entries will be translated to Marc in core (for increased speed) or out of
core.

1 PLOAD4 will be processed in core.

-1 PLOAD4 will be processed out of core. (Default)

Note: The MSPEEDP4=1 option may require more memory than is available on certain
computers for large models. Do not use if CWELD elements are present.

MSPEEDPS
Default = -1, SOL 600 only.
Determines whether additional memory will be used if the Marc PSHELL option is invoked
(PARAM,MRPSHELL,1) or smear option on SOL 600,ID in order to speed up processing. This will be
beneficial if there are many materials and properties in the model and not very beneficial if all elements
use just a few properties and materials.

-1 No additional memory will be used. (Default)

1 Additional memory will be used if available.

Main Index
 902 MSPEEDSE
Parameter Descriptions

MSPEEDSE
Default = -1, SOL 600 only.
Determines whether speed enhancements are activated using extra memory and/or special low level I/O
routines.

-1 No speed enhancements will be activated. (Default)

1 Solid elements 2D elements data will be processed in core.
2 All elements will be processed in core.
3 2D and 3D elements will be processed in core, 1D elements will be processed using bioxxx
(low level direct access routines used by gino).

Note: The MSPEEDSE=1 option may require more memory than is available on certain
computers for large models. MSPEEDSE > 0 should not be used for 64-bit integer versions
of Nastran or DEC Alpha computer systems.

MSPEEDS2
Default = -1, SOL 600 only.
Determines whether additional memory will be used when PARAM,MSPEEDSE with options 1, 2, 3 is
entered to obtain additional speed.

-1 Additional memory will not be used. (Default)

1 Additional memory will be used and additional speed will usually be obtained.

MSPEEDSH
Default = -1, SOL 600 only.
Determines whether additional speed enhancements will be used to process shell/plate elements
(CQUAD4, CTRIA3, etc.) using incore memory.

-1 No additional speed enhancements are used. (Default)

1 Additional speed in-core enhancements will be used. Sufficient memory must be available.
If not, the job will abort with an appropriate message.

Main Index
 MSPLINC0 903
Parameter Descriptions

Note: This parameter should only be used if shell speed enhancements are selected with one of
the PARAM,MSPEEDSE options.

MSPLINC0
Integer, Default = 0, SOL 600. For SOL 400, MSPLINC0 =1 is always used.
This parameter controls whether to enforce C0 continuity for all spline options if any are requested by
setting IDSPL=1 on any BCBODY entry.

0 C0 continuity is not enforced.

1 C0 continuity is enforced.

MSTFBEAM
Default = 0, SOL 600 only.
Determines if all rigid elements (RBE2, RBE3, RBAR, RTRPLT) will be converted to stiff beams. This
parameter should only be used if PARAM,MARMPCHK and/or PARAM,AUTOMSET options fail
during a Marc execution.

1 All rigid elements will be converted to stiff beams or plates after they have initially been
formed in the Marc file as RBE2 or RBE3 elements. All 6 dof’s at each end of the rigid beam
will be used.
2 All rigid elements will be converted to stiff beams or plates after they have initially been
formed in the Marc file as RBE2 or RBE3 elements. Pin codes specified by the original
Nastran rigid elements will be used when possible.

Remark:
See PARAM,MARCSCLR to specify a scale factor for the “Default” properties of these stiff beams.

MSTRFREE
Integer, Default = 0
Determines whether the nodal coordinates in the GEOM1 datablock of SOL 600 OOP2 files will have
the original coordinates or revised stress-free coordinates.

0 GEOM1 will have the original coordinates (same as defined on GRId entries)
1 GEOM1 will have modified coordinates to enforce stress-free conditions if applicable

Main Index
 904 MSTTDYNE
Parameter Descriptions

Remarks:
1. ICOORD on the BCTABLE with ID=0 entry must be set to 1 or 3 for at least one slave-master
combination.
2. The parameter only addresses op2 files (t16 and t19 files automatically use MSTRFREE=1)
3. This capability is available starting with MD Nastran 2010. Prior version always used
MSTRFREE=0.

MSTTDYNE
Integer, Default = 0, SOL 600 only
Controls whether SOL 600 may have static and dynamic load cases in the same analysis.

0 All subcases must either be static or dynamic

1 Mixed static and dynamic load cases are allowed.

Remarks:
1. Use of this entry requires SOL 600,106 or SOL 600,NLSTATIC (not SOL 600,NLTRAN).
2. Do not enter TSTEPNL, DLOAD, LOADSET, LSEQ, TLOADi in the Case Control or Bulk Data.
3. Each subcase must have NLAUTO entries. Whether the subcase is static or dynamic is controlled
by IFLAG on each NLAUTO entry. For static subcases IFLAG=3 and for dynamic subcases
IFLAG=0.
4. All loads in each subcase build up from an initial value at the end of the previous subcase to the
full value entered on the various load-type entries (such as FORCE, PLOAD4, SPCD, etc.) at the
end of the subcase. Time histories for individual load cases are not allowed with this parameter.
If all loads for a particular subcase use the same time history, this subcase may be divided into N-
1 smaller subcases where N is the number of points on the time history curve. For this situation,
the loads for each smaller subcase should be scaled by the amplitude of each point on the time
history curve. This technique may also be used to simulate force vs. time for an analysis with all
static subcases.
5. When MSTTDYNE=1, the following will automatically be added to the Bulk Data:
marcin,-1,0,dynamic,6
param,marcauov,0
These two entries may be added by the user in place of PARAM,MSTTDYNE,1 however both
should not be done.

MTABIGNR
Default = 0, SOL 600 only.
Determines whether tables for VCCT analyses will be ignored or used.

Main Index
 MTABLD1M 905
Parameter Descriptions

-1 VCCT tables are not used

0 VCCT tables are used. (Default)

Remark:
Use of tables for VCCT SOL 600 2D analyses with contact is not supported. If the table variation is not
important, this parameter may be used to obtain an approximate solution.

MTABLD1M
Default = 1, SOL 600 only.
Option to modify or not modify all TABLED1 entries which do not start with the first point of (0.0, 0.0).

-1 Do not modify any TABLED1 entries

1 Modify all TABLD1 entries that do not start with (0.0, 0.0). (Default)

Remark:
See PARAM,MTABLD1T.

MTABLD1T
Default = 0.01, SOL 600 only.
Specifies the second time value of all TABLED1 entries that do not start with the first point being (0.0,
0.0) if PARAM,MTABLD1M=1. Modified tables will start with the first point of (0.0, 0.0), the second
point will be at the time specified by this parameter with an amplitude of the original first amplitude. The
3rd point will be at time 2*MTABLD1T and amplitude of the original first amplitude.

Remark:
The proper value of MTABLD1T to enter to analyze a step input depends on the fundamental natural
frequency of the model. If MTABLD1T is too small, the response will not fully build up and if it is too
large, it will act like a ramp input rather than a step. The best value to use is approximately 0.1/fn, where
fn is the first linear natural frequency in Hz.

MTDYMAT9
Default = 0, SOL 700 only
Determines if MAT9 will be translated to MATD2AN or not.

Main Index
 906 MTEMPCHK
Parameter Descriptions

0 Translate to MATD2AN. (Default)

1 Leave MAT9 as is – This might fail in LS-Dyna if the material angles are not fully defined.

MTEMPCHK
Integer, Default = 0, SOL 600 only
Controls how temperature-dependent properties are checked in the Marc portion of SOL 600.

0 Check at zero degrees only. (Marc feature 9601)

1 Check at all temperatures, stop checking and fatal the job when the first problem is found.
(Marc feature 9600)
2 Check at all temperatures and report all problems, then fatal the job if any problems were
found. (Marc feature 9602)

Remarks:
1. This parameter is available starting with MD Nastran 2010.
2. The default in Marc previously was feature 9601.
3. The default in SOL 600 is different than in Marc. The default in Marc is 9600.
4. Checking in Marc will occur from the lowest temperature of any curve to the highest of any curve.
Thus, to ensure that all curves pass, define all curves from the lowest temperature of any curve to
the highest temperature of any curve (even though one particular curve can never reach the lowest
or highest temperature specified on another curve).
5. features,960i will be entered if any TABLEMi or TABL3Di are found.

MTEMPDWN
Default = -1, SOL 600 only.
Option to automatically choose the FeFp multiplicative decomposition plasticity model
(PARAM,MARCPLAS,5) for plasticity problems with thermal loading when the temperature decreases
(see PARAM,MARCPLAS).

-1 Use the standard mean normal with large strain method unless PARAM,MARCPLAS is
entered. (Default)
1 Attempt to determine whether the temperature at the start of the run is lower than the initial
temperature, and if so choose the FeFp method.

Main Index
 MTET4HYP 907
Parameter Descriptions

Remarks:
1. For some problems with very soft materials, the FeFp method is required to achieve convergence
for plasticity cases where the temperature decreases during the early stages of the run. Since most
users would not know this, PARAM,MTEMPDWN is offered to automatically let Nastran decide
to invoke this method or not.
2. The FeFp method takes substantially more computer time than the default mean normal method.
3. This parameter can be entered in RC files if it is desired to be used for a large number of runs.

MTET4HYP
Integer, Default = 0, SOL 600 only
Controls settings for TET4 elements with hyperelasticity.

0 Use Marc element 157 which uses the Herrmann formulation.

1 Use Marc element 134 and automatically set PARAM,MARUPDAT,1

Remarks:
1. MTET4HYP=1 should normally only be set if any tet4 elements use MATHE or MATHP and if
one or more of the grids in such tet4 have field 7 set to a cylindrical or spherical coordinate
system.
2. If Remark 1 does not apply, MTET4HYP=0 is more accurate, although it is highly recommended
that tet10 elements be used for all SOL 600 models which will be even more accurate.

MTLD1SID
Integer, Default = 0 for SOL 700 and -1 for SOL 600
Determines whether the SID of TLOAD1s entered in the input will be changed or not. (SOL 600 and
SOL 700 only)

-1 Do not change the SID of any TLOAD1 entry

0 Change the SID of all TLOAD1s to match the lowest SID of any TLOAD1 found in the
original input.
N Change the SID of all TLOAD1s to the value N.

Remark:
This parameter may only be set in the input file.

Main Index
 908 MUALLUDS
Parameter Descriptions

MUALLUDS
Integer, Default = 0, SOL 600 only
Controls how material, contact and element-related user subroutines are specified in SOL 600.

0 User subroutines are entered using the MATUSR entry (material), contact-related (BCBODY,
BCTABLE, etc.) or element entries as well as the USRSUB6 entry.
1 User subroutines are entered using the MATUDS, BCONDUDS and/or ELEMUDS. They
should not be specified on MATUSR. BCxxx, element entries or by using the USRSUB6
entry.

Remark:
For version prior to MD Nastran 2010 only option 0 was available.

MULRFORC
Default = -1, SOL 600 only.
Option to activate multiple RFORCE entries for different portions of The model in the same subcase.

-1 Do not allow this capability (only one RFORCE entry for subcase can be entered).
(Default)
1 Allow multiple RFORCE entries for each subcase

MUMPSOLV
Integer > 0, Default = 1, SOL 600 only.
This can also be set by the Bulk Data entry PARAMARC.

1 Use 1 processor.
2 Use 2 processor.
N Use N processor.

Remarks:
1. This parameter may only be used by solver the MUMPS solver (solver type 12).
2. The PARAMARC Bulk Data entry cannot specify this type of parallel processing.

Main Index
 MUSBKEEP 909
Parameter Descriptions

MUSBKEEP
Default = 0, SOL 600 only.

0 If user subroutines are included, they are compiled and linked to form a new version of
Marc if MUSBKEEP=0, the new version of Marc will be deleted at the end of the run.
(Default)
1 The new Marc executable will be saved on disk in the same directory as the Nastran input
file. Its name will be the name used in PARAM,MARCUSUB with the extension marc.

MVERMOON
Integer, Default = 0, SOL 600 only
Controls whether 5-term Mooney series or 5-constant Mooney will be used in the Marc portion of
SOL 600.

0 5-constant Mooney formulation will be used.

1 5-term series Mooney formulation will be used.

Remark:
Prior to MD Nastran 2010, the Marc only allowed a 5-constant Mooney formulation with no volumetric
terms. Now Marc allows a full 5-term series for both distortional and volumetric behavior for both
MATHP and MATHE entries. If a version of Marc prior to this is to be used, set param,mvermoon,0 or
use the default.

MWINQUOT
Integer, Default = 0, SOL 600 only
Determines whether SOL 600 run on Windows will attempt to place quote strings in the command to
execute Marc when PATH is not specified on the SOL 600 Executive Control statement.

0 Attempt to place quote strings around various fields.

1 Do not place any quote strings.

Remarks:
1. Quotes are normally only required if spaces are needed in the file names or directory names.
2. This parameter may be placed in rc files.
3. Depending on the complexity of the command to execute Marc, quote strings may sometimes be
incorrect. If the command is complex, it is suggested that PATH=1 be placed on the SOL 600
Executive statement and the statement to execute Marc be placed in the marcrun.pth file.

Main Index
 910 MWLDGSGA
Parameter Descriptions

MWLDGSGA
Integer, Default = 1, SOL 600.
Controls CWELD type ELEMID GS, GA, GB usage in SOL 600.

0 When GS, GA and GB are all greater than zero for CWELD type ELEMID, Marc ignores
GS and uses GA and GB to determine if a connection is possible. MWLDGSA=0 retains
this default behavior, however experience shows that some models will fail with a message
that the weld connection could not be achieved.
1 This option will re-set GA and GB to zero so that GS will be used to achieve the connection.
Experience shows that this option may be more reliable for many models with CWELD type
ELEMID.

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:

Main Index
 NDAMP, NDAMPM 911
Parameter Descriptions

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
TSTEPNL 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.
SOL 400 Mechanical: In SOL 400, numerical damping may be specified for all METHODS (ADAPT,
FNT, etc. on the TSTEPNL 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

Main Index
 912 NEWMARK
Parameter Descriptions

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

NEWMARK
Default = NO
See CQC under SCRSPEC, 943.

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=11) (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.

Main Index
 NLHTLS 913
Parameter Descriptions

NLHTLS
Default = 0
See Remarks under Case Control command, TSTRU (Case), 558.

NLHTOL
Default = 1.0E-5
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, 910.

NLMAX
Default = 60
The number of suspected mm’s is determined from the number of high ratio messages. If this number
exceeds NLMAX the number of trial mm’s is reduced to NLMAX. This is a means to avoid an expensive
debug run when there may be thousands of mm’s 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 it is possible that
there are many high ratio DOFs, and you’d rather see them all at once rather than on successive runs
where you remove only a part of them at one time.

NLMIN
Default = 10
If there are only one or a few high ratio DOFs there may be more mm’s present. More trial mm vectors
are used, and those that do not indicate true problems are discarded. A smaller value could be considered
on a stable model undergoing small modeling changes.

Main Index
 914 NLPACK
Parameter Descriptions

NLPACK
SOL 400 only.
NLPACK is used in the nonlinear solution sequence SOL 400 only. The SOL 400 will pack output data
for NLPACK output time steps and restart data for 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 TSTEPNL Bulk Data
entry.

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
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.

Main Index
 NOCOMPS 915
Parameter Descriptions

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.
Homogenous stresses are based upon a smeared representation of the laminate’s properties and in general
will be incorrect. Element strains are correct however.

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
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.

Main Index
 916 NOMSGSTR
Parameter Descriptions

NOMSGSTR
Default = 0
If NOMSGSTR = -1, the MSGSTRES module will be skipped even though Bulk Data entries provided
for it. See Part III of the MSGMESH Analyst Guide for a discussion of MSGSTRESS.

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
(Default) of 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.
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

See S1, S1G, S1M.

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.

Main Index
 OG 917
Parameter Descriptions

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.

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.

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.

Main Index
 918 OLDSEQ
Parameter Descriptions

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 Suitable
Method 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.

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

Main Index
 OMACHPR 919
Parameter Descriptions

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 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.

OMACHPR
Default = NO
See POST < 0.

Main Index
 920 OMAXR
Parameter Descriptions

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, set the parameter OMID to yes.
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 post-processors (xdb and op2 output are not changed) nor by grid point stress output that assumes
output is in element coordinate system.

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.

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.

OPGTKG
Default = -1
OPGTKG > -1 prints the matrix for the interpolation between the structural and aerodynamic degrees-
of-freedom.

Main Index
 OPPHIB 921
Parameter Descriptions

OPPHIB
Default = -1
In the flutter (SOLs 145 and 200) and 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
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.

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.

Main Index
 922 OPTION
Parameter Descriptions

OPTEXIT
Value Description
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, 716.

OSETGRD
Default = 1
See AUTOGOUT, 716.

OSWELM
Default = -1
Offset for identification numbers of internally generated m-set constraint elements corresponding to
CWELD elements with formats ELEMID and GRIDID. 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. 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.
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.

Main Index
 OSWPPT 923
Parameter Descriptions

OSWPPT
Integer, Default = -1
Offset for internally generated grid identification numbers for connector elements. 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. 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.
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.

OUNIT1
Default = Value of OUNIT2
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

Main Index
 924 PANELMP
Parameter Descriptions

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 blocks
GPFORCE, ESE, EKE, EDE, WETSENS, and ESE-(with PARAM,XFLAG,2) 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.
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

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.

PEDGEP
Default = 0
Cubic edges of p-elements can be created with the FEEDGE Bulk Data entry by defining two vertex grids
and two points in between. By default, the two points on an edge are moved to the parametric 1/3 and

Main Index
 PEMMAPC 925
Parameter Descriptions

2/3 locations of the edge. For PEDGEP = 1 the points are not moved. MSC.Patran V7 generates points
so that adjacent edges are C1 continuous. These points should not be moved. Therefore, MSC.Patran
generates a Bulk Data Section with PARAM,PEDGEP,1 if p-elements are in the model.

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.

For SET ID Generic File name

Structure GID coupled 10000 <deckname>.<job
with all TRMCs seq>.x_nas.structure_component1.set
Fluid GID coupled with 20000 <deckname>.<job
all TRMCs seq>.x_nas.fluid_component2.set
Structure GID coupled 17xxx for GLUED or <deckname>.<job seq
with TRIMID=xxx only 18xxx for SLIDING >.x_nas.structure_component1.trim_coup
ling.<xxx>.<sliding or glued>.set
Fluid GID coupled with 27xxx for OPEN or <deckname>.<job
TRIMID=xxx only 28xxx for IMPER seq>.x_nas.fluid_component2.trim_coupl
ing.<xxx>.<open or impervious>.set
TRIMID=xxx GID Xxx0001 <deckname>.<job seq
coupled with structure >.x_nas.trim<xxx>.structure.set
TRIMID=xxx GID Xxx0002 <deckname>.<job seq
coupled with fluid >.x_nas.trim<xxx>.fluid.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 1000.
3. With 'PARAM,PEMNPART,n', PEMMAPC login has a TRIM ID limit of less than 10.

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.

Main Index
 926 PENFN
Parameter Descriptions

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.
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.

PENFN
Default = 1.0e+5 (See LMFACT)

PERCENT
Default = 40
See CQC under SCRSPEC, 943.

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

Main Index
 PLTMSG 927
Parameter Descriptions

If PKRSP=0, the magnitude of the output quantities at the time of peak acceleration of the modal
variables is output. The SRSS technique that is used for response spectra is described in Additional Topics
(p. 515) in the . This option is available only for modal transient analysis.

PLTMSG
Default = 1
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 (p. 445) in the MSC Nastran Reference
Manual 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.

Main Index
 928 POST
Parameter Descriptions

• 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.

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 OP2=‘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
-1 or 1 -2 -4 -5 -6 Data Block Description
YES NO NO NO NO GEOM1S, Grid Point Definitions (Superelement)
GEOM1VU
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
NO 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

Main Index
 POST 929
Parameter Descriptions

POST
Geometry
-1 or 1 -2 -4 -5 -6 Data Block Description
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
GEOM2VU
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. 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.

Main Index
 930 POST
Parameter Descriptions

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
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
NO YES none none ERRORN p-element error summary table

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

Main Index
 POST 931
Parameter Descriptions

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)
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.

Data Block
PARAMeter Name Case Control Name Description
OUG DISPLAC OPHIG Eigenvectors in the global coordinate
system.

Main Index
 932 POST
Parameter Descriptions

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

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.

PARAMeter Data Block

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

Main Index
 POSTEXT 933
Parameter Descriptions

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
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

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.

Main Index
 934 POSTU
Parameter Descriptions

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.

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. PARAM,PROUT,-1
prints a list of all elements sorted on EID and summary tables giving the range of element identification
numbers for each element type.

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.

Main Index
 PRPHIVZ 935
Parameter Descriptions

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”.

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.

PVALINIT
Default = 1
Starting p-value in a p-adaptive analysis restart.

Main Index
 936 Q
Parameter Descriptions

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.

RESLTOPT
Default = 8
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.

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.

RKSCHEME
Default = Remark 1., SOL 700 only

Main Index
 RMSINT 937
Parameter Descriptions

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)

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.

ROHYDRO
Default = Remark 3., SOL 700 only
Defines the minimum density for hydrodynamic, single-material Eulerian elements.

Main Index
 938 ROMULTI
Parameter Descriptions

Format:
PARAM,ROHYDRO,VALUE

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)

Main Index
 ROSTR 939
Parameter Descriptions

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.
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.

ROTSEKE
Default = -1
Controls the printout of rotor energies in the .f06 file. For a model with only one rotor, the strain and
kinetic energy percentages will always be 100%.

Main Index
 940 RSPECTRA
Parameter Descriptions

-1 Rotor energies are printed in the .f06 file. (Default)

0 Rotor energies are not printed in the .f06 file.

RSPECTRA
Default = -1
RSPECTRA = 0 requests that response spectra be calculated for transient analysis. See Additional Topics
(p. 515) in the 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 Additional Topics (p. 515) in the . 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.

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

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.

Main Index
 S1, S1G, S1M 941
Parameter Descriptions

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 CQUAD4,
elements connect CTRIA3

NUMOUT, in conjunction with BIGER, controls the amount of stress output.

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.
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.

Main Index
 942 S1AG,S1AM
Parameter Descriptions

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.

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.

SBOLTZ
SOL 700 only
Real, Defines a value for the Stephan-Boltzmann constant.
1. Must be used if the RADIATE option is used on the AIRBAG entry.
2. Specify only one universal gas constant per problem.
3. In SI units, SBOLTZ equals 5.670 × 10 –8 J K –4 m – 2 s – 1

Main Index
 SCALEMAS 943
Parameter Descriptions

SCALEMAS
No Default, SOL 700 only

DTMIN Real. Option to scale all element masses (generated by density times volume) such that
its time step never becomes less than:
dt=STEPFCT*DTMIN
where
DT = timestep originally calculated by Dytran a this particular time
STEPFCT = timestep safety factor (see PARAM,STEPFCT)
DTMIN = value specified on this parameter

Note: The amount of mass scaling varies with time. Added mass does contribute to total (kinetic)
energies in the model and should be used carefully. Generally, a 5-8% mass increase at
each component level (not global level) is usually acceptable.

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 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

Main Index
 944 SDRPOPT
Parameter Descriptions

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.

SDRPOPT
Default = SDRP
SDPROPT controls the storage of the principal stresses and strains in the stress and strain tables (OES1
and OSTR1 data blocks) in p-version analysis. By default, the principal stresses and strains are stored in
the stress and strain tables to support postprocessing. PARAM,SDRPOPT,OFP requests that the
principal stresses and strains are not stored in the tables. This can result in a significant reduction in disk
space usage.

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.

Main Index
 SENSUOO 945
Parameter Descriptions

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.
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.

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.

Main Index
 946 SEP1XOVR
Parameter Descriptions

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
Default = AUTO
By default, all restarts are considered automatic (see Restart Procedures (p. 343) in the MSC Nastran
Reference Manual). 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 (p. 408) in the MSC Nastran Reference Manual). 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

Main Index
 SESDAMP 947
Parameter Descriptions

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
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.

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. For very stiff model
(1000. hz for the first flexible mode), consider using a larger value.

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.

Main Index
 948 SIGMA
Parameter Descriptions

SIGMA
Default = 0.0
The radiant heat flux is proportional to
4
SIGMA ⋅ ( T grid + T ABS )

where SIGMA is the Stefan-Boltzmann constant, T grid is the temperature at a grid point, and T ABS is the
scale factor for absolute temperature and may be specified by PARAM,TABS. These parameters must
be given in units consistent with the rest of the data in the model. The value for SIGMA in SI units is
–8 2 4
5.67 × 10 watts/m K

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.

Main Index
 SMALLQ 949
Parameter Descriptions

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 5-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.

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 5-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.

Main Index
 950 SNORMPRT
Parameter Descriptions

Grid Point
Normal

Local Normal of Shell 1 Local Normal of Shell 2

SNORM SNORM

Shell 1 Shell 2
Figure 5-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)

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:

Main Index
 SOLID 951
Parameter Descriptions

-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

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.
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

Main Index
 952 SPARSEPH
Parameter Descriptions

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.
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, 845 and SPARSEDR, 951.

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
 SRCOMPS 953
Parameter Descriptions

See AUTOQSET, 717.

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.9 for Lagrangian elements and 0.666 for Euler elements, 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 = t N where t N 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 t N as though the original run contained the new subcase data.

Main Index
 954 STRUCTMP
Parameter Descriptions

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.
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 Additional Topics (p. 515) in the for further
discussion.

Main Index
 SUPAERO 955
Parameter Descriptions

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.

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 Additional Topics (p. 515) in the . 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.

Main Index
 956 TESTNEG
Parameter Descriptions

Refer to the Bulk Data entry, CREEP, 1626 for a creep analysis with SOLs 106 or 153. Refer to
PARAM,SlGMA for heat transfer analysis.

TESTNEG

Default =  – 2 for Newtons method
 – 1 for Arc-length method

In nonlinear static analysis (SOLs 106 and 153), 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.

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 [ E mh ]
described in Geometry Processing in SubDMAP PHASE0 (p. 345) in the MSC Nastran Reference
Manual.

Main Index
 TOLRSC 957
Parameter Descriptions

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.
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
TRMBIM is used to define the formulation used for reduced impedance matrix, RIM, for all trim
components requested under TRIMGRP case control commands. It is default to 'PHYSICAL' which will
generate RIM in physical coordinates. The other valid option 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.
It is important to note that data recovery for trim components are supported only under
'PARAM,TRMBIM,PHYSICAL' and 'PARAM,PEMNPART,1 (default)' for all trim components. In
addition, SOL 200 supports for trim components is limited to following conditions,
1. Design model on structure and/or fluid model only (not the trim/PEM material).
2. Design responses/constraints on responses of structure and/or fluid only (not the trim/PEM
material).

TSTATIC
Default = -1 (SOLs 129, 159, 400 and 600 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

Main Index
 958 UGASC
Parameter Descriptions

METHOD = “ADAPT” on the Bulk Data entry, TSTEPNL, 3720). For SOL 600, TSTATIC=1 may only
be used for the default auto step iteration procedure.

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.
3. In IS units, R equals 8.3145 J mol – 1 K –1 .
Using the tonne, mm, system of units R has a value of 8314.5 tonne mm 2 s –2 mol – 1 K –1 .
In imperial units, R equals 1.9859 Btu lbmol –1 °R –1 or 1545.3 ft lbf lbmol – 1 °R –1

UNSYMF
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, 1069. To print aerodynamic degree-of-freedom sets, please see OPGEOM.

Main Index
 USETPRT 959
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 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).
The row sort is not recommended in p-version analysis because large integers are generated for
hierarchical grid point identification numbers and they will be truncated.
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):

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

Main Index
 960 USETSEL
Parameter Descriptions

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.

USETSEL Sets Printed

-1 All sets as defined in Degree-of-Freedom Sets, 1069.
0 Mutually exclusive sets only; i.e., sets M, SB, SG, O, Q, R, C, B, E, and A.

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, 1069 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

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), 369 and Bulk Data
entry, HADAPTL, 2139), singular geometric features such as sharp edges or sharp corners must be
detected. To this end the face outward normals N 1, N 2 of each pair of adjacent mesh faces and the edge
oriented tangents T 1, T 2 of each pair of adjacent mesh edges are computed (see Figure 5-3). If the angle
between N 1 and N 2 for mesh faces, or between T 1 and T 2 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.

Main Index
 VELCUT 961
Parameter Descriptions

Edge Vertex
N1
N2

T2
T1

Faces Edge
Figure 5-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)

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.
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.

Main Index
 962 VREF
Parameter Descriptions

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.
For SOL 400, VMOPT=2 is not supported, and, if entered, the virtual mass will be included with the mass
matrix.

VREF
Default = 1.0
In modal flutter analysis, the velocities are divided by VREF to convert units or to compute flutter
indices.

VUELJUMP, VUGJUMP
Default = 1000
Specifies the separation in identification numbers for display elements and grid points generated in
p-version analysis. The defaults are sufficient for a 9 9 9 display element mesh.
Identification numbers for display elements and grid points start with 10001001 and 201001001,
respectively. For example, by default the identification numbers for the display elements of the first
p-element will be numbered 100001001 through 100002000 and the second p-element 100002001
through 100003000, etc.

VUBEAM, VUHEXA, VUPENTA, VUQUAD4, VUTETRA, VUTRIA3

Default = VUBEAM
Default = VUHEXA
Default = VUPENTA
Default = VUQUAD4
Default = VUTETRA
These parameters are used in p-version analysis to specify the names of the display elements in the data
recovery output tables; such as those created by the VUGRID Case Control command and
PARAM,POST. They should be used if your postprocessor does not recognize display elements. For

Main Index
 WRBEAMB 963
Parameter Descriptions

example, PARAM,VUHEXA,CHEXA renames the display element VUHEXA to “CHEXA” in the

output files.

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.

WTMAS600
Integer, Default = 1
Determines whether GRAV entries will be scaled by WTMASS or not for SOL 600 only.

0 The value of A (4th field) on the GRAV entry will not be scaled by WTMASS.
1 The value of A (4th field) on the GRAV entry will be scaled by WTMASS.

Remarks:
1. This parameter is available starting with the MD Nastran 2010.
2. Prior to MD Nastran 2010, WTMAS600=1 for all analyses.

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.
In SOL700, WTMASS affects on the items below.
• Density of all materials.
• fluid density (RHOF) of MAD069
• water density (RHOWAT) of MATD147
• mass (MASS) and inertia (IXX~IZZ) of MATRIG
• non structural mass (NSM) of properties. (beam, shell and composite shell)
• INER of PBDISCR

Main Index
 964 W3, W4, W3FL, W4FL
Parameter Descriptions

• mass (MASS) and inertia (I11~I33) of CONM2

• Density (DENS) of CFD option of AIRBAG
• DENSITY of TICEL and TICVAL
• MASS of CSPH
• mass (TM) and inertia (IXX~IZZ) of RBE2D and D2RINER
• mass (M) of EXPLSV
• MASS of MOVING option of WALL

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 the [ K 1dd ] and [ K 4dd ] items to be ignored in the damping matrix, regardless of the presence of the
PARAM, G or GFL or [ K 4dd ] . [ K 1dd ] is the stiffness.

4
[ K dd ] is the structural damping and is created when GE is specified on the MATi entries.

1
is the stiffness. The units of W3, W4, W3FL, and W4FL are radians per unit time. (See Real
[ K dd ]
Eigenvalue Analysis in SubDMAPs SEMR3 and MODERS (p. 390) in the MSC Nastran Reference
Manual for 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.

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” on page 192 of the MSC.Nastran 2004 Release Guide for equations.

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:

Main Index
 XYUNIT, n 965
Parameter Descriptions

1 T T
E = --- u K e u – u P et
2

where u is the deformation, K e is the element stiffness and P et 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:

E = 1 1 T
T
--- 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, if Nastran
detects frequency dependent elements (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.

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
 966 ZROVEC
Parameter Descriptions

Main Index
 Parameter Applicability Tables 967
Parameter Applicability Tables

Parameter Applicability Tables

Table 5-1, Table 5-2, Table 5-3, Table 5-4, and Table 5-5 list parameter applicability to the solution
sequences (SOLs 101 through 112).
Table 5-6, Table 5-7, Table 5-8, Table 5-9, Table 5-10, Table 5-11, Table 5-12, Table 5-13, Table 5-14,
Table 5-15, and Table 5-16 list parameter applicability to the solution sequences (SOLs 114 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.

Main Index
 968 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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
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
ALTSHAPE B B B B B 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

Main Index
 Parameter Applicability Tables 969
Parameter Applicability Tables

Table 5-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
AUTOGOUT E E E E E E E E E E E
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
CAMPBLL 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, 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 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
DBALL E E E E E E E E E E E

Main Index
 970 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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
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 5-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
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
ESLFSAV
ESLMOVE

Main Index
 Parameter Applicability Tables 971
Parameter Applicability Tables

Table 5-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
ESLRCF
EST E E E E E E E E E E E
EXTDR B B B B B B B B
EXTDROUT B B B B B B B B
EXTDRUNT B B B B B B B B
EXTOUT B B B B B B B B B B B
EXTRCV E E E E E E E E E E 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 B B B B B B
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
GRDPNT E E E E E E E E E E E
GUSTAERO
GYROAVG 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 E E E E E E E

Main Index
 972 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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 5-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
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
MODACC B B B

Main Index
 Parameter Applicability Tables 973
Parameter Applicability Tables

Table 5-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
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
NEWSET B
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
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 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
OELMSET E E E E E E E E E E E
OES E E E E E E E E E E E

Main Index
 974 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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
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 5-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
OUMU E

Main Index
 Parameter Applicability Tables 975
Parameter Applicability Tables

Table 5-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
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
PEDGEP 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
PVALINIT B B B B B B B B
Q
RBSETPRT E E E E E E E E E E E

Main Index
 976 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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
RHOCP
ROTSEKE E E
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 5-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
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
 Parameter Applicability Tables 977
Parameter Applicability Tables

Table 5-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
TCHECK
TDMIN
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

Main Index
 978 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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
VARPHI C
VMOPT E E E E E E E E E E
VREF B B
VUBEAM E E E E E E E E
VUELJUMP E E E E E E E E
VUGJUMP E E E E E E E E
VUHEXA E E E E E E E E
VUPENTA E E E E E E E E
VUQUAD4 E E E E E E E E
VUTETRA E E E E E E E E
WTMASS E E E E E E E E E E E
W3 E E
W3FL E E
W4 E E
W4FL E E
XFLAG E E E
XYUNIT
ZROCMAS E E E E E E E E
ZROVEC E E E E E E E E

Table 5-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 600 700
ACEXTMTD B
ACEXTSET B
ACOUT E
ACOWEAK B
ACSYM B
ADJMETH B
ADPCON E E E E
ADSTAT

Main Index
 Parameter Applicability Tables 979
Parameter Applicability Tables

Table 5-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 600 700
AERODOF E E E E
AESDISC B B
AESMAXIT B B
AESMETH B B
AESRNDM B B
AESTOL B B
ALPHA1 B B B B B B B
ALPHA2 B B B B B B B
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
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

Main Index
 980 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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 600 700
BIGER1 E E E E E
BIGER2 E E E E E
BLADEDEL B
BLADESET B
BLDRSTRT B
BLDTHETA B
BUCKLE
CASIEMA E
CASPIV E E
CB1, CB2 E E E E E E E E E E E
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 E E
CK1, CK2, CK3 E E 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
COPOR 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
CWLDIGNR B
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

Main Index
 Parameter Applicability Tables 981
Parameter Applicability Tables

Table 5-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 600 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
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
DYBEAMIP B
DYBLDTIM B
DYBULKL B
DYBULKLQ1 B
DYCMPFLG B
DYCONECDT B
DYCONENMASS B
DYCONIGNORE B
DYCONPENOPT B
DYCONRWPNAL B
DYCONSKIPRWG B
DYCONSLSFAC B

Main Index
 982 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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 600 700
DYCONTHKCHG B
DYCOWPRD B
DYCOWPRP B
DYDCOMP B
DYDEFAUL C
DYDTOUT B
DYDYLOAD B
DYELAS1C B
DYELAS1F B
DYELAS1R B
DYELPLET B
DYELPLFL B
DYELPLSY B
DYENDTIM B
DYENERGYHGEN B
DYENGFLG B
DYHRGIHQ B
DYHRGQH B
DYIEVERP B
DYINISTEP B
DYLDKND B
DYMATS1 B
DYMAXINT B
DYMAXSTEP B
DYMINSTEP B
DYNAMES B
DYNEIPH B
DYNINT B
DYNEIPS B
DYNINTSL B
DYNLOADS B

Main Index
 Parameter Applicability Tables 983
Parameter Applicability Tables

Table 5-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 600 700
DYNRBE23 B
DYNREAL B
DYN3THDT B
DYPRMSPC B
DYRBE3 B
DYRBE2TY B
DYRLTFLG B
DYNSPCF E E E E E
DYSHELLFORM B
DYSHGE B
DYSHINP B
DYSHTHICK B
DYSIGFLG B
DYSTATIC B
DYSTRFLG B
DYSTSSZ B
DYTERMNDTMIN B
DYTERMNENDMAS B
DYTSTEPDT2MS B
DYTSTEPERODE B
ENFMETH E E
ENFMOTN E E
EPPRT
EPSILONT
EPZERO
ERPC
ERPREFDB
ERPRHO
ERPRLF
ERROR E E E E E E E E E E E E
ESLFSAV E
ESLLCOMP E

Main Index
 984 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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 600 700
ESLMOVE E
ESLMPC1 E
ESLOPTEX E
ESLPRT E
ESLPRT1 E
ESLRCF E
EULBND B
EULBULKL B
EULBULKQ B
EULBULKT B
EULSTRES B
EXTOUT B B B B B B B B B B
EXTRCV E E E E E E E E E E
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
FIXEDB E
FKSYMFAC E
FLEXINCR
FLUIDMP
FLUIDSE B
FMULTI B
FOLLOWK E E E E B
FRQDEPO B B
FULLSEDR E E E E E E E E E E E
FZERO E
G B E B B B B B
GFL
GEOMU E E E E E E E E E E
GFL B B
GPECT E E E E E E E E E E

Main Index
 Parameter Applicability Tables 985
Parameter Applicability Tables

Table 5-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 600 700
GRADMESH B
GRDPNT E E E E E E E E E E E

Main Index
 986 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-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 600 700
GUSTAERO B B B
GYROAVG
HEATCMD B
HEATSTAT
HFREQ B B B
HFREQFL B B
HTOCITS
HTOCPRT
HTOCTOL
IFP E E E E E E E E E
INREL B
INRLM
IRES E E E E E E E E E
ISOL70G0 B
ITAPE B
IUNIT B
JWLDET X
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 X X
LFREQ B B B
LFREQFL B B
LGDISP E E E E B
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
 Parameter Applicability Tables 987
Parameter Applicability Tables

Table 5-9 PARAMeter Names in SOLs 115 Through 700 Part 4 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MALIAS02 B
MALIAS03 B
MARALPHA B
MARAUTOC B
MARBK105 B
MARBK106 B
MARC3901 B
MARC3D C
MARC4401 B
MARCASUM B
MARCAUTO B
MARCAXEL B
MARCBEAM B
MARCBUG C
MARCBUSK B
MARCCBAR B
MARCCENT B
MARCCON2 B
MARCCON3 B
MARCCPY B
MARCDEF B
MARCDILT B
MARCDIS2 B
MARCDIS3 B
MARCDIS4 B
MARCDMIG B
MARCEKND B
MARCEXIT B
MARCFEAT,N B
MARCFIL B
MARCFRIC B

Main Index
 988 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-10 PARAMeter Names in SOLs 115 Through 700 Part 5

Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MARCGAPP B
MARCGLUE B
MARCHOST B
MARCIAMN B
MARCINTC B B
MARCINTF B B
MARCITER B
MARCL001 B
MARCLOWE B
MARCLUMP B
MARCMATT B
MARCMEM B
MARCMNF B
MARCMPII B
MARCND99 B
MARCNOER B
MARCOFFT B
MARCONLY B
MARCONTF B
MARCOOCC B
MARCOPT B
MARCOTIM B
MARCPARR B
MARCPENT B
MARCPINN B
MARCPOS B
MARCPOST B
MARCPR99 B
MARCPRES B
MARCPRN B
MARCPRNG B
MARCPRNR B

Main Index
 Parameter Applicability Tables 989
Parameter Applicability Tables

Table 5-10 PARAMeter Names in SOLs 115 Through 700 Part 5 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MARCPROG B
MARCPTH B
MARCRBAL B
MARCRBAR B
MARCRBE2 B
MARCRBE3 B
MARCREVR B
MARCRIGD B
MARCRUN B
MARCSAME C
MARCSCLR B
MARCSETS B
MARCSETT B
MARCSINC B
MARCSIZ3 B
MARCSIZ4 B
MARCSIZ5 B
MARCSIZ6 B
MARCSLHT B
MARCSOLV B
MARCSPCC B
MARCSTIFF B
MARCSUMY B
MARCT16 B
MARCT19 B
MARCTABL B
MARCTEDF B
MARCTEDN B
MARCTEMP B
MARCTETT B
MARCTIEC B
MARCTOL B
MARCTOTD B

Main Index
 990 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-11 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 600 700
MARCTOTL B
MARCTOTT B
MARCTUBE B
MARCTVL B
MARCUSUB B
MARCVERS B
MARCWDIS B
MARCWELD B
MARCWIND B
MARELSTO B
MARFACEA B
MARFACEB B
MARFATAL B
MARGPFOR B
MARIBOOC B
MARIPROJ B
MARMPCHK B
MARMPCID C
MARNOSET B
MARNOT16 B
MARPLANE B
MARPROCS
MARRBAR2 B
MARROUTT B
MARSHRII B
MARUPDAT B
MAXIREVV B
MAXLP E E
MAXRATIO E E E E E E E E E E E
MBENDCAP B
MCNLPARM B
MCON2D3D B

Main Index
 Parameter Applicability Tables 991
Parameter Applicability Tables

Table 5-11 PARAMeter Names in SOLs 115 Through 700 Part 6 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MCORDUPD B
MCSSHLCK C
MCSSHORR C
MDAREAMD B
MDK4OPT B
MDOPT14 B
MDOTM B
MDOTMFAC B
MDUMLOAD B
MESH B B B
METHCMRS E E E E E E
MEXTRNOD B
MEXTSEE C
MFASTCMP B
MFORCOR1 B
MFSKIPPP B
MGAPINIT B
MGLUETOL B
MHEATSHL B
MHEATUNT B
MHOUBOLT B
MHRED E E E E E E E
MICRO B
MINCLDSB B
MINIGOA B B B B B B B B B B B
MINRECCC B
MINSOUTT B
MINVASHF B
MINVCITR B
MINVCSHF B
MINVCTOL B
MINFMAX B
MINVNMOD B

Main Index
 992 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-11 PARAMeter Names in SOLs 115 Through 700 Part 6 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MLSTRAIN B
MLSTRAN2 B
MMEMDETT B

Table 5-12 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 600 700
MNASTLDS B
MODACC B B
MODEL B B B B B B B B B B B
MOFFCORE B
MOP2TITL B
MOUTRCOR B
MPCX B B B B B B B B B B B
MPERMPRT B
MPTUNIT E
MRAFFLOR B
MRAFFLOT B
MRAFFLOW B
MRALIAS B
MRBE2SNG B
MRBEAMB B
MRBEPARAM B
MRBIGMEM B
MRBUKMTH B
MRC2DADD B
MRCKBODY B
MRCKLOAD B
MRCONADD B
MRCONTAB B
MRCONUSE C
MRCONRES B

Main Index
 Parameter Applicability Tables 993
Parameter Applicability Tables

Table 5-12 PARAMeter Names in SOLs 115 Through 700 Part 7 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MRCONVER B
MRCOORDS B
MRCWANGL B
MRCWELD B
MRDELTTT B
MRDISCMB B
MRDYNOLD B
MREIGMTH B
MREL1103 B
MRELRB B
MRELSPCD B
MRENUELE B
MRENUGRD B
MRENUMBR B
MRENUMMT B
MRESTALL B
MRESULTS B
MREVPLST B
MRFINITE B
MRFOLLO2 B
MRFOLLOW B
MRFOLOW1 B
MRFOLOW3 B
MRFOLOW4 B
MRGAPUSE B
MRHYPMID B
MRITTYPE B
MRMAT8A3 B
MRMAT8E3 B
MRMAT8N1 B
MRMAT8N3 B
MRMAXISZ B
MRMAXNUM B

Main Index
 994 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-12 PARAMeter Names in SOLs 115 Through 700 Part 7 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MRMEMSUM B
MRMTXKGG B
MRNOCOR B
MRORINTS B
MRPARALL B
MRPELAST B
MRPBUSHT B

Table 5-13 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 600 700
MRPIDCHK B
MRPLOAD4 B
MRPLOAD4R B
MRPLSUPD B
MRPREFER B
MRPSHCMP B
MRPSHELL B
MRRELNOD B
MRRCFILE B
MRSETNAM B
MRSPAWN2 B
MRSPLINE B
MRSPRING B
MRT16STP B
MRTABLIM B
MRTABLS1 B
MRTABLS2 B
MRTABPRC B
MRTFINAL B
MRTIMING B
MRTHREAD B

Main Index
 Parameter Applicability Tables 995
Parameter Applicability Tables

Table 5-13 PARAMeter Names in SOLs 115 Through 700 Part 8 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
MRTSHEAR B
MRUSDATA B
MSOLMEM B
MSPCCCHK B
MSPCKEEP B
MSPEEDCB B
MSPEEDCW B
MSPEEDOU B
MSPEEDP4 B
MSPEEDSE B
MSOLMEM, MBYTE B
MSTFBEAM B
MTABINGNR B
MTABLD1M B
MTABLD1T B
MTDYMAT9 B
MTEMPDWN B
MTLD1SID B
MULRFORC B
MUMPSOLV B
MUSBKEEP B
MWINQUOT B
MWLDGSGA B
MXLAGM1 B
NASPRT B
NDAMP E E E
NDAMPM E
NEWSET
NINTPTS E E E E
NLAYERS E E
NLHTLS E E
NLMAX E
NLMIN E E

Main Index
 996 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-13 PARAMeter Names in SOLs 115 Through 700 Part 8 (continued)
Solution Sequence Numbers (115 through 700)
PARAMeter
Name 115 116 118 129 144 145 146 153 159 200 400 600 700
NMLOOP
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

Table 5-14 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 600 700
NUMOUT2 E E E E
OCMP E E E
OEE 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
OELMSET E E E E E E E E E E E
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 E
OGEOM E E E E E E E E E E E
OGPF E E E E E
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 B
OMAXR E E E E E E E E E E E

Main Index
 Parameter Applicability Tables 997
Parameter Applicability Tables

Table 5-14 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 600 700
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 E
OPGEOM B B B B
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 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
OSWPPT 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
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
PEDGEP
PENFN B
PH2OUT B
PLTMSG 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
PREFDB E

Main Index
 998 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-14 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 600 700
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
PRTBGPDT E E E E E E 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 5-15 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 600 700
PVALINIT B
Q B
RADMOD B B B
RBSETPRT E E E
RCONTACT B
RESLTOPT E E E E E E E E E E E
RHOCP
RKSCHEME B
RMSINT
ROHYDRO B
ROMULTI B
ROSTR B
RSPECTRA

Main Index
 Parameter Applicability Tables 999
Parameter Applicability Tables

Table 5-15 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 600 700
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
SCALEMAS B
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
SPARSEDM E E
SPARSEDR E E
SPARSEPH E E E

Main Index
 1000 Parameter Applicability Tables
Parameter Applicability Tables

Table 5-15 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 600 700
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
TCHECk
TDMIN
TESTNEG E E
TFSYMFAC E E E E E E E E

Table 5-16 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 600 700
TINY E E E E
TOLRSC B B B B B B B B B B
TOPOCONV E
TSTATIC E E E E
UNSYMF B
UNSYMKB B B B B B B B
UPDTBSH E

Main Index
 Parameter Applicability Tables 1001
Parameter Applicability Tables

Table 5-16 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 600 700
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
VUBEAM
VUELJUMP
VUGJUMP
VUHEXA
VUPENTA
VUQUAD4
VUTETRA
WTMASS E E E E E E E E E E B B
W3 B E B E B
W3FL B
W4 B E B B
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
 1002 Parameter Applicability Tables
Parameter Applicability Tables

Main Index
 Item Codes MSC Nastran Quick Reference Guide

6 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=ELEMENT on FTGPARM

Fatigue Item Codes for LOC=NODE 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
 1004 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 (p. 459) in the MSC Nastran Reference Manual.
• DTI,INDTA entry for stress sorting.

The following tables provide item codes for:

• Table 6-1. Element Stress or Strain.
• Table 6-6. Element Force.
• Table 6-8. Fluid Virtual Mass Pressure.
• Table 6-9. Heat Transfer Flux.
• Table 6-10. Slideline Contact Output.
• Table 6-13. Element Strain Energy Item Codes.
• Table 6-14. Fatigue Item Codes (LOC=ELEMENT)
• Table 6-15 Fatigue Item Codes (LOC=NODE)

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.

Main Index
 Item Codes 1005
Element Stress (or Strain) Item Codes

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 .

Main Index
 1006 CAXIF2 (47)
Element Stress (or Strain) Item Codes

Table 6-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
1 1
3 Axial axis 3 Axial axis RM
1 1
4 Tangential edge 4 Tangential edge RM
51 Circumferential edge 51 Circumferential edge RM
61 Radial axis IP
1
7 Axial axis IP
1
8 Tangential edge IP
91 Circumferential edge IP
CAXlF3 (48) 21 Radial centroid 21 Radial centroid RM
1
3 Circumferential centroid 31 Circumferential centroid RM
1
4 Axial centroid 41 Axial centroid RM
51 Tangential edge 1 51 Tangential edge 1 RM
1
6 Circumferential edge 1 61 Circumferential edge 1 RM
1
7 Tangential edge 2 71 Tangential edge 2 RM
1
8 Circumferential edge 2 81 Circumferential edge 2 RM
91 Tangential edge 3 91 Tangential edge 3 RM
1
10 Circumferential edge 3 101 Circumferential edge 3 RM
1
11 Radial centroid IP
1
12 Circumferential centroid IP
131 Axial centroid IP
1
14 Tangential edge 1 IP
1
15 Circumferential edge 1 IP
1
16 Tangential edge 2 IP
171 Circumferential edge 2 IP
181 Tangential edge 3 IP
1
19 Circumferential edge 3 IP
CAXIF4 (49) 21 Radial centroid 21 Radial centroid RM
31 Circumferential centroid 31 Circumferential centroid RM
1 41
4 Axial centroid Axial centroid RM
1
5 Tangential edge 1 51 Tangential edge 1 RM
1
6 Circumferential edge 1 61 Circumferential edge 1 RM

Main Index
 CAXISYM (241) 1007
Element Stress (or Strain) Item Codes

Table 6-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
1 1
8 Circumferential edge 2 8 Circumferential edge 2 RM
91 Tangential edge 3 91 Tangential edge 3 RM
101 Circumferential edge 3 101 Circumferential edge 3 RM
1
11 Tangential edge 4 111 Tangential edge 4 RM
1
12 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
1 1
3 End A-Point D 3 End A-Point D RM
Linear
41 End A-Point E 41 End A-Point E RM
1
5 End A-Point F 51 End A-Point F RM
61 Axial 61 Axial RM
1
7 End A maximum 7 End A-Point C IP

Main Index
 1008 CBAR (100)
Element Stress (or Strain) Item Codes

Table 6-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
8 End A minimum 81 End A-Point D IP
1
9 Safety margin in tension 9 End A-Point E IP
101 End B-Point C 101 End A-Point F IP
111 End B-Point D 111 Axial IP
1
12 End B-Point E 121 End B-Point C RM
1
13 End B-Point F 131 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
 CBAR (238) 1009
Element Stress (or Strain) Item Codes

Table 6-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
3 Max Axial Stress
Arbitrary Cross
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
4 Long. Stress at Point C 41 Long. Stress at Point C RM
51 Long. Stress at Point D 51 Long. Stress at Point D RM
61 Long. Stress at Point E 61 Long. Stress at Point E RM
1
7 Long. Stress at Point F 71 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
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 to the
item code points to the same item code points to the same
information for other stations, where K information for other stations, where K
is the station number. K=11 for end B is the station number. K=11 for end B
and 2 through10 for intermediate and 2 through 10 for intermediate
stations.) 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
 1010 CBEAM (239)
Element Stress (or Strain) Item Codes

Table 6-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 at RM
point C point C
12 Shear stress in y-direction at 12 Shear stress in y-direction at RM
point D point D
13 Shear stress in y-direction at 13 Shear stress in y-direction at RM
point E point E
14 Shear stress in y-direction at 14 Shear stress in y-direction at RM
point F point F
15 Maximum shear stress in y- 15 Shear stress in y-direction at IP
direction point C
16 Minimum shear stress in y- 16 Shear stress in y-direction at IP
direction point D
17 (Not applicable) 17 Shear stress in y-direction at IP
point E
18 (Not applicable) 18 Shear stress in y-direction at IP
point F
19 Shear stress in z-direction at 19 Shear stress in z-direction at RM
point C point C

Main Index
 CBEND (69) 1011
Element Stress (or Strain) Item Codes

Table 6-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 at RM
point D point D
21 Shear stress in z-direction at 21 Shear stress in z-direction at RM
point E point E
22 Shear stress in z-direction at 22 Shear stress in z-direction at RM
point F point F
23 Maximum shear stress in z- 23 Shear stress in z-direction at IP
direction point C
24 Minimum shear stress in z- 24 Shear stress in z-direction at IP
direction point D
25 (Not applicable) 25 Shear stress in z-direction at IP
point Z
26 (Not applicable) 26 Shear stress in z-direction at IP
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. They
respectively) 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

1
4 Long. Stress at Point C 41 Long. Stress at Point C RM
51 Long. Stress at Point D 51 Long. Stress at Point D RM
61 Long. Stress at Point E 61 Long. Stress at Point E RM
1
7 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
1
10 Safety margin in tension 10 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 (Item codes are given for end A. Item
codes 12 through 21 point to the same codes 12 through 21 point to the same
information for end B.) 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
51 Rotation-x 51 Rotation-x R
1 1
6 Rotation-y 6 Rotation-y R
1 71
7 Rotation-z Rotation-z R
1
8 Translation-x I

Main Index
 1012 CBUSH1D (40)
Element Stress (or Strain) Item Codes

Table 6-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
1
10 Translation-z I
111 Rotation-x I
121 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

Main Index
 CCONEAX (35) 1013
Element Stress (or Strain) Item Codes

Table 6-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
1
4 Normal v at Z1
51 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
1
12 Normal v at Z2
131 Normal u at Z2
1
14 Shear uv at Z2
15 Shear angle at Z2
16 Major principal at Z2
17 Minor principal at Z2
18 Maximum shear at Z2
CDUM3 21 S1 21 S1 RM
1
thru 3 S2 31 S2 RM
41 S3 41 S3 RM
CDUM9 (55-61) 5 1 S4 51 S4 RM
1 61
6 S5 S5 RM
1 71
7 S6 S6 RM
81 S7 81 S7 RM
CELAS1 (11) 21 Stress 21 Stress RM
1
3 Stress IP
CELAS2 (12) 21 Stress 21 Stress RM
31 Stress IP
CELAS3 (13) 21 Stress 21 Stress RM
1
3 Stress IP

Main Index
 1014 CGAP (86)
Element Stress (or Strain) Item Codes

Table 6-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
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)
1
6 Normal x 61 Normal x RM
1
7 Shear xy 71 Normal y RM
8 First principal 81 Normal z RM
1
9 First principal x cosine 9 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
1
13 von Mises or octahedral shear 13 Normal y IP
stress
141 Normal y 141 Normal z IP
1 151
15 Shear yz Shear xy IP
1
16 Second principal 16 Shear yz IP
17 First principal y cosine 171 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
1
21 Shear zx
22 Third principal
23 First principal z cosine
24 Second principal z cosine

Main Index
 CHEXA (93) 1015
Element Stress (or Strain) Item Codes

Table 6-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
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
15 Strain-X
16 Strain-Y
17 Strain-Z
18 Strain-XY
19 Strain-YZ
20 Strain-ZX
21-148 Items 3 through 18
Repeated for 8 corners
CHEXAFD 2 Grid/Gauss
(202) 3 Grid/Gauss ID (0=center)
Nonlinear Finite 4 Cauchy stress-X
Deformation with 8 grid
points 5 Cauchy stress-Y
6 Cauchy stress-Z
7 Cauchy stress-XY
8 Cauchy stress-YZ
9 Cauchy stress-ZX
1
10 Pressure p = --- ( σ x + σ y + σ z ) Not applicable
3

Main Index
 1016 CHEXAFD (207)
Element Stress (or Strain) Item Codes

Table 6-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
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 2-17 Same as CHEXAFD (202)
(207) 18-407 Items 3 through 17 repeated Not applicable
Nonlinear Finite for 26 Gauss points
Deformation with 20
grid points
CIFHEX (65) 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-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

Main Index
 CIFQDX (73) 1017
Element Stress (or Strain) Item Codes

Table 6-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
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
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
Linear 1
3 Axial safety margin 3 Axial stress IP
1 41
4 Torsional stress Torsional stress RM
1
5 Torsional safety margin 5 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

Main Index
 1018 CPENTA (91)
Element Stress (or Strain) Item Codes

Table 6-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
(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
9 First principal x cosine 91 Shear xy RM
1
10 Second principal x cosine 10 Shear yz RM
11 Third principal x cosine 111 Shear zx RM
12 Mean pressure 121 Normal x IP
1
13 von Mises or Octahedral shear 13 Normal y IP
stress
141 Normal y 141 Normal z IP
1
15 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-95 Items 5 through 17 repeated
for 6 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-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

Main Index
 CPENTAFD (204) 1019
Element Stress (or Strain) Item Codes

Table 6-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 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 3 through 18
Repeated for 6 corners
CPENTAFD 2-17 Same as CHEXAFD (201)
(204) 18-92 Items 3 through 17 repeated Not applicable
Nonlinear Finite for 5 Gauss points
Deformation with 6 grid
points
CPENTAFD 2-17 Same as CHEXAFD (201)
(209) 18-317 Items 3 through 17 repeated Not applicable
Nonlinear Finite for 20 Gauss points
Deformation with 15
grid points

Main Index
 1020 CQUAD4 (33)
Element Stress (or Strain) Item Codes

Table 6-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
51 Shear xy at Z1 51 Normal y at Z1 RM
6 Shear angle at Z1 61 Normal y at Z1 IP
1
7 Major principal at Z1 7 Shear xy at Z1 RM
1
8 Minor principal at Z1 8 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
11 NormaI x at Z2 111 NormaI x at Z2 IP
1
12 Normal y at Z2 121 Normal y at Z2 RM
1
13 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)

Main Index
 CQUAD42 (95) 1021
Element Stress (or Strain) Item Codes

Table 6-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 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
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-1 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 Output 2 CEN/ 2 CEN/
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 11 Z2-Fiber distance
at 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

Main Index
 1022 CQUAD8 (64)
Element Stress (or Strain) Item Codes

Table 6-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
18 Minor principal at Z2 18 Grid 1
19 von Mises or maximum shear 19-32 Same as 4 through 17 for
at Z2 corner 1
20 Grid 1 33 Grid 2
21-36 Same as 4 through19 for 34-47 Same as 4 through 17 for
corner 1 corner 2
37 Grid 2 48 Grid 3
38-53 Same as 4 through19 for 49-62 Same as 4 through 17 for
corner 2 corner 3
54 Grid 3 63 Grid 4
55-70 Same as 4 through 19 for 64-77 Same as 4 through 17 for
corner 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
6 Normal y at Z1 61 Normal x at Z1 IP
1
7 Shear xy at Z1 71 Normal y at Z1 RM
1
8 O 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 NormaI x at Z2 IP
1 141
14 Normal y at Z2 Normal y at Z2 RM
1 1
15 Shear xy at Z2 15 Normal y at Z2 IP
16 Q Shear angle at Z2 161 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 for
maximum shear at Z2 corner 2
22-36 Same as items 5 through 19 for 50-62 Same as items 5 through 17 for
corner 1 corner 3
39-53 Same as items 5 through 19 for 65-77 Same as items 5 through 17 for
corner 2 corner 4

Main Index
 CQUAD82 (96) 1023
Element Stress (or Strain) Item Codes

Table 6-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
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
CQUADFD 2 Grid/Gauss
(201) 3 Grid/Gauss ID (0=center)
Nonlinear Finite 4 Cauchy stress-X
Deformation with
4 grid points 5 Cauchy stress-Y
6 Cauchy stress-Z
7 Cauchy stress-XY
1
8 Pressure p = --- ( σ x + σ y + σ z ) Not applicable
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 2-13 Same as CQUADFD (201)
(208) 14-101 Items 3 through 13 repeated Not applicable
Nonlinear Finite for 8 Gauss points
Deformation with 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
 1024 CQUADX(18)
Element Stress (or Strain) Item Codes

Table 6-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)
2 Harmonic 2 Harmonic
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 2 Grid/Gauss
(214) 3 Gauss ID
Nonlinear Finite 4 Cauchy stress-X (radial)
Deformation with 4 grid
points 5 Cauchy stress-Y (axial)
6 Cauchy stress-Z
(circumferential)
7 Cauchy stress-XY
1
8 Pressure p = --- ( σ x + σ y + σ z ) Not applicable
3
9 Volumetric strain
J-1
10 Logarithmic strain-X (radial)
11 Logarithmic strain-Y (axial)
12 Logarithmic strain-Z
(circumferential)
13 Logarithmic strain-XY

Main Index
 CQUADXFD (215) 1025
Element Stress (or Strain) Item Codes

Table 6-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
14-46 Items 3 through 13 repeated
for remaining 3 Gauss points
CQUADXFD 2-13 Same as QUADXFD (214) Not applicable
(215) 14-101 Items 3 through 13 repeated
Nonlinear Finite for remaining 8 Gauss points
Deformation with 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
4 Safety margin 41 Average shear RM
51 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
 1026 CTETRA (39)
Element Stress (or Strain) Item Codes

Table 6-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
6 Normal x 61 Normal x RM
1
7 Shear xy 71 Normal y RM
8 First principal 81 Normal z RM
1
9 First principal x cosine 9 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
1
13 von Mises or octahedral shear 13 Normal y IP
stress
141 Normal y 141 Normal z IP
1
15 Shear yz 151 Shear xy IP
1
16 Second principal 16 Shear yz IP
17 First principal y cosine 171 Shear zx IP
18 Second principal y cosine 18-69 Items 5 through 17 repeated
for four corners
19 Third principal y cosine
1
20 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-109 Items 5 through 25 repeated
for four corners

Main Index
 CTETRA (85) 1027
Element Stress (or Strain) Item Codes

Table 6-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 3 through 18
Repeated for four corners
CTETRAFD 2-17 Same as CHEXAFD (202) Not applicable
(205)
Nonlinear Finite
Deformation with 4 grid
points
CTETRAFD 2-17 Same as CHEXAFD (202)
(210) 18-77 Items 3 through 17 repeated Not applicable
Nonlinear Finite for 4 Gauss points
Deformation witn 10
grid points

Main Index
 1028 CTRIA3 (74)
Element Stress (or Strain) Item Codes

Table 6-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 1 61
6 Normal y at Z1 Normal x at Z1 IP
1 71
7 Shear xy at Z1 Normal y at Z1 RM
1
8 Q shear angle at Z1 8 Normal y at Z1 IP
9 Major principal at Z1 91 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
1 131
13 NormaI x at Z2 Normal x at Z2 IP
1 141
14 Normal y at Z2 Normal y at Z2 RM
1 151
15 Shear xy at Z2 Normal y at Z2 IP
16 Q shear angle at Z2 161 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 for
maximum shear at Z2 corner 2
22-36 Same as items 5 through 19 for 50-62 Same as items 5 through 17 for
corner 1 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
 CTRIAFD (211) 1029
Element Stress (or Strain) Item Codes

Table 6-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 grid for 2 Gauss points
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)

2 Harmonic 2 Harmonic
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
5 Axial 51 Azimuthal RM
1
6 Shear stress 61 Azimuthal IP

Main Index
 1030 CTRIAXFD (212)
Element Stress (or Strain) Item Codes

Table 6-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 for 12-19 Same as items 3 through 10 for
corner 1 corner 1
19-25 Same as Items 3 through 9 for 21-28 Same as items 3 through 10 for
corner 2 corner 2
27-33 Same as items 3 through 9 for 30-37 Same as items 3 through 10 for
corner 3 corner 3
CTRIAXFD 2-13 Same as CQUADXFD (214) Not applicable
(212)
Nonlinear Finite
Deformation with 3 grid
points
CTRIAXFD 2-13 Same as CQUADXFD (214)
(213) 14-35 Items 3 through 13 repeated Not applicable
Nonlinear Finite for 2 Gauss points
Deformation with
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
 VUHEXA (145) 1031
Element Stress (or Strain) Item Codes

Table 6-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
VUHEXA (145) 1 VU element ID * 10 + device
code
2 Parent p-element ID
VUPENTA (146)
3 VU grid ID for corner 1
4 Normal x 4 Normal x RM
VUTETRA (147)
for HEXAp, PENTAp, 5 Normal y 5 Normal y RM
TETRAp if 6 Normal z 6 Normal z RM
SDRPOPT=SDRP
(with principals) 7 Shear xy 7 Shear xy RM
8 Shear yz 8 Shear yz RM
9 Shear zx 9 Shear zx RM
10 First principal 10 Normal x IP
11 Second principal 11 Normal y IP
12 Third principal 12 Normal z IP
13 Mean pressure 13 Shear xy IP
14 von Mises/ Octahedral 14 Shear yz IP
15-26 Repeat items 3-14 for corner 2 15 Shear zx IP
27-38 Repeat items 3-14 for corner 3 16-28 Repeat items 3-15 for corner 2
39-50 Repeat items 3-14 for corner 4 29-41 Repeat items 3-15 for corner 3
51-62 Repeat items 3-14 for corner 5 42-54 Repeat items 3-15 for corner 4
(VUPENTA, VUHEXA)
63-74 Repeat items 3-14 for corner 6 55-67 Repeat items 3-15 for corner 5
(VUPENTA, VUHEXA) (VUPENTA, VUHEXA)
75-86 Repeat items 3-14 for corner 7 68-80 Repeat items 3-15 for corner 6
(VUHEXA) (VUPENTA, VUHEXA)
87-98 Repeat items 3-14 for corner 8 81-93 Repeat items 3-15 for corner 7
(VUHEXA) (VUHEXA)
94- Repeat items 3-15 for corner 8
106 (VUHEXA)

Main Index
 1032 VUHEXA (145)
Element Stress (or Strain) Item Codes

Table 6-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
VUHEXA (145) 1 VU element ID * 10 + device
code
2 Parent p-element ID
VUPENTA (146)
3 VU grid ID for corner 1
4 Normal x 4 Normal x RM
VUTETRA (147)
for HEXAp, PENTAp, 5 Normal y 5 Normal y RM
TETRAp if 6 Normal z 6 Normal z RM
SDRPOPT=OFP
(no principals) 7 Shear xy 7 Shear xy RM
8 Shear yz 8 Shear yz RM
9 Shear zx 9 Shear zx RM
10-16 Repeat items 3-9 for corner 2 10 Normal x IP
17-23 Repeat items 3-9 for corner 3 11 Normal y IP
24-30 Repeat items 3-9 for corner 4 12 Normal z IP
31-37 Repeat items 3-9 for corner 5 13 Shear xy IP
(VUPENTA, VUHEXA)
38-44 Repeat items 3-9 for corner 6 14 Shear yz IP
(VUPENTA, VUHEXA)
45-51 Repeat items 3-9 for corner 7 15 Shear zx IP
(VUHEXA)
52-58 Repeat items 3-9 for corner 8 16-28 Repeat items 3-15 for corner 2
(VUHEXA)
29-41 Repeat items 3-15 for corner 3
42-54 Repeat items 3-15 for corner 4
55-67 Repeat items 3-15 for corner 5
(VUPENTA, VUHEXA)
68-80 Repeat items 3-15 for corner 6
(VUPENTA, VUHEXA)
81-93 Repeat items 3-15 for corner 7
(VUHEXA)
94- Repeat items 3-15 for corner 8
106 (VUHEXA)

Main Index
 VUQUAD (189) VUTRIA (190) 1033
Element Stress (or Strain) Item Codes

Table 6-5 Element Stress-Strain Item Codes Part 5

Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
VUQUAD (189) 1 VU element ID * 10 + device
code
VUTRIA (190)
2 Parent p-element ID
for QUADp
3 CID coordinate system ID
and TRIAp if
4 ICORD flat/curved etc.
STRAIN= FIBER; 4th
char. of ICORD= 5 THETA material angle
X Y, Z (local coordinate 6 ITYPE strcur=0, fiber=1
system); and SDRPORT
=SDRP (with 7 VU grid ID for corner 1
principals)
8 Z1 fiber distance
9 Z2 fiber distance
10 Normal x at Z1 10 Normal x at Z1 RM
11 Normal y at Z1 11 Normal y at Z1 RM
12 Shear xy at Z1 12 Shear xy at Z1 RM
13 Shear Angle at Z1 13 0.0 RM
14 Major principal at Z1 14 0.0 RM
15 Minor principal at Z1 15 0.0 RM
16 vonMises/Max.Shear at Z1 16 Normal x at Z2 RM
17 NormaI x at Z2 17 Normal y at Z2 RM
18 Normal y at Z2 18 Shear xy at Z2 RM
19 Shear xy at Z2 19 0.0 RM
20 Shear Angle at Z2 20 0.0 RM
21 Major principal at Z2 21 0.0 RM
22 Minor principal at Z2 22 Normal x at Z1 IP
23 vonMises/Max.Shear at Z2 23 Normal y at Z1 IP
24 Shear xy at Z1 IP
25 0.0 IP
26 0.0 IP
27 0.0 IP
28 Normal x at Z2 IP
29 Normal y at Z2 IP
30 Shear xy at Z2 IP
31 0.0 IP

Main Index
 1034 VUQUAD (189) VUTRIA (190)
Element Stress (or Strain) Item Codes

Table 6-5 Element Stress-Strain Item Codes Part 5 (continued)

Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
32 0.0 IP
33 0.0 IP
24-40 Repeat items 7-23 for corner 2 34-60 Repeat items 7-33 for corner 2
41-57 Repeat items 7-23 for corner 3 61-87 Repeat items 7-33 for corner 3
58-74 Repeat items 7-23 for corner 4 88- Repeat items 7-33 for corner 4
(VUQUAD) 104 (VUQUAD)
VUQUAD (189) 1 VU element ID * 10 + device
code
VUTRIA (190)
for QUADp and TRIAp 2 Parent p-element ID
if STRAIN= FIBER; if 3 CID coordinate system ID
4th char. of ICORD=X
Y, Z (local coordinate 4 ICORD flat/curved etc.
system); and SDRPOPT
=OFP (no principals) 5 THETA material angle
6 ITYPE strcur=0, fiber=1
7 VU grid ID for corner 1
8 Z1 fiber distance
9 Z2 fiber distance
10 Normal x at Z1 10 Normal x at Z1 RM
11 Normal y at Z1 11 Normal y at Z1 RM
12 Shear xy at Z1 12 Shear xy at Z1 RM
13 0.0 13 0.0 RM
14 0.0 14 0.0 RM
15 0.0 15 0.0 RM
16 0.0 16 Normal x at Z2 RM
17 Normal x at Z2 17 Normal y at Z2 RM
18 Normal y at Z2 18 Shear xy at Z2 RM
19 Shear xy at Z2 19 0.0 RM
20 0.0 20 0.0 RM
21 0.0 21 0.0 RM
22 0.0 22 Normal x at Z1 IP
23 0.0 23 Normal y at Z1 IP
24 Shear xy at Z1 IP
25 0.0 IP
26 0.0 IP

Main Index
 VUQUAD (189) VUTRIA (190) 1035
Element Stress (or Strain) Item Codes

Table 6-5 Element Stress-Strain Item Codes Part 5 (continued)

Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
27 0.0 IP
28 Normal x at Z2 IP
29 Normal y at Z2 IP
30 Shear xy at Z2 IP
31 0.0 IP
32 0.0 IP
33 0.0 IP
24-40 Repeat items 7-23 for corner 2 34-60 Repeat items 7-33 for corner 2
41-57 Repeat items 7-23 for corner 3 61-87 Repeat items 7-33 for corner 3
58-74 Repeat items 7-23 for corner 4 88- Repeat items 7-33 for corner 4
(VUQUAD) 104 (VUQUAD)
VUQUAD (189) 1 VU element ID * 10 + device
code
VUTRIA (190)
2 Parent p-element ID
for QUADp and
3 CID coordinate system ID
TRIAp if
4 ICORD flat/curved etc.
STRAIN= FIBER and
4th char. of ICORD=F 5 THETA material angle
(fixed coordinate 6 ITYPE strcur=0, fiber=1
system)
7 VU grid ID for corner 1
8 Z1 fiber distance
9 Z2 fiber distance
10 Normal x at Z1 10 Normal x at Z1 RM
11 Normal y at Z1 11 Normal y at Z1 RM
12 Shear xy at Z1 12 Shear xy at Z1 RM
13 Shear yz at Z1 13 Shear yz at Z1 RM
14 Shear zx at Z1 14 Shear zx at Z1 RM
15 Normal z at Z1 15 Normal z at Z1 RM
16 NormaI x at Z2 16 Normal x at Z2 RM
17 NormaI y at Z2 17 Normal y at Z2 RM
18 Shear xy at Z2 18 Shear xy at Z2 RM
19 Shear yz at Z2 19 Shear yz at Z2 RM
20 Shear zx at Z2 20 Shear zx at Z2 RM
21 Normal z at Z2 21 Normal z at Z2 RM

Main Index
 1036 VUQUAD (189) VUTRIA (190)
Element Stress (or Strain) Item Codes

Table 6-5 Element Stress-Strain Item Codes Part 5 (continued)

Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
22 0.0 22 Normal x at Z1 IP
23 0.0 23 Normal y at Z1 IP
24 Shear xy at Z1 IP
25 Shear yz at Z1 IP
26 Shear zx at Z1 IP
27 Normal z at Z1 IP
28 Normal x at Z2 IP
29 Normal y at Z2 IP
30 Shear xy at Z2 IP
31 Shear yz at Z2 IP
32 Shear zx at Z2 IP
33 Normal z at Z2 IP
24-40 Repeat items 7-23 for corner 2 34-60 Repeat items 7-33 for corner 2
41-57 Repeat items 7-23 for corner 3 61-87 Repeat items 7-33 for corner 3
58-74 Repeat items 7-23 for corner 4 88- Repeat items 7-33 for corner 4
(VUQUAD) 104 (VUQUAD)
VUQUAD (189) 1 VU element ID * 10 + device
code
VUTRIA (190)
for QUADp and TRIAp 2 Parent p-element ID
if 3 CID coordinate system ID
STRAIN= STRCUR
and 4th char. of 4 ICORD flat/curved etc.
ICORD=X Y, Z (local
coordinate system) 5 THETA material angle
6 ITYPE strcur=0, fiber=1
7 VU grid ID for corner 1
8 0.0
9 0.0
10 Membrane Strain x 10 Membrane Strain x RM
11 Membrane Strain y 11 Membrane Strain y RM
12 Membrane Strain xy 12 Membrane Strain xy RM
13 0.0 13 0.0 RM
14 0.0 14 0.0 RM
15 0.0 15 0.0 RM
16 Bending Curvature x 16 Bending Curvature x RM

Main Index
 VUQUAD (189) VUTRIA (190) 1037
Element Stress (or Strain) Item Codes

Table 6-5 Element Stress-Strain Item Codes Part 5 (continued)

Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
17 Bending Curvature y 17 Bending Curvature y RM
18 Bending Curvature xy 18 Bending Curvature xy RM
19 Shear yz 19 Shear yz RM
20 Shear zx 20 Shear zx RM
21 0.0 21 0.0 RM
22 0.0 22 Membrane Strain x IP
23 0.0 23 Membrane Strain y IP
24 Membrane Strain xy IP
25 0.0 IP
26 0.0 IP
27 0.0 IP
28 Bending Curvature x IP
29 Bending Curvature y IP
30 Bending Curvature xy IP
31 Shear yz IP
32 Shear zx IP
33 0.0 IP
24-40 Repeat items 7-23 for corner 2 34-60 Repeat items 7-33 for corner 2
41-57 Repeat items 7-23 for corner 3 61-87 Repeat items 7-33 for corner 3
58-74 Repeat items 7-23 for corner 4 88- Repeat items 7-33 for corner 4
(VUQUAD) 104 (VUQUAD)
VUQUAD (189) 1 VU element ID *10 + device
code
VUTRIA (190)
for QUADp and TRIAp 2 Parent p-element ID
if STRAIN= STRCUR 3 CID coordinate system ID
and 4th char. of
ICORD=F 4 ICORD flat/curved etc.
(fixed coordinate
system) 5 THETA material angle
6 ITYPE strcur=0, fiber=1
7 VU grid ID for corner 1
8 0.0
9 0.0
10 Membrane Strain x 10 Membrane Strain x RM
11 Membrane Strain y 11 Membrane Strain y RM

Main Index
 1038 VUBEAM (191)
Element Stress (or Strain) Item Codes

Table 6-5 Element Stress-Strain Item Codes Part 5 (continued)

Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
12 Membrane Strain xy 12 Membrane Strain xy RM
13 Membrane Strain yz 13 Membrane Strain yz RM
14 Membrane Strain zx 14 Membrane Strain zx RM
15 Membrane Strain z 15 Membrane Strain z RM
16 Bending Curvature x 16 Bending Curvature x RM
17 Bending Curvature y 17 Bending Curvature y RM
18 Bending Curvature xy 18 Bending Curvature xy RM
19 Bending Curvature yz 19 Bending Curvature yz RM
20 Bending Curvature zx 20 Bending Curvature zx RM
21 Bending Curvature z 21 Bending Curvature z RM
22 0.0 22 Membrane Strain x IP
23 0.0 23 Membrane Strain y IP
24 Membrane Strain xy IP
25 Membrane Strain yz IP
26 Membrane Strain zx IP
27 Membrane Strain z IP
28 Bending Curvature x IP
29 Bending Curvature y IP
30 Bending Curvature xy IP
31 Bending Curvature yz IP
32 Bending Curvature zx IP
33 Bending Curvature z IP
24-40 Repeat items 7-23 for corner 2 34-60 Repeat items 7-33 for corner 2
41-57 Repeat items 7-23 for corner 3 61-87 Repeat items 7-33 for corner 3
58-74 Repeat items 7-23 for corner 4 88- Repeat items 7-33 for corner 4
(VUQUAD) 104 (VUQUAD)
VUBEAM (191) 1 VU element ID * 10 + device
code
for
BEAMp 2 Parent p-element ID
3 CID coordinate system ID
4 ICORD (not used)
5 VU grid ID for end 1
6 x/L position

Main Index
 VUBEAM (191) 1039
Element Stress (or Strain) Item Codes

Table 6-5 Element Stress-Strain Item Codes Part 5 (continued)

Real Stresses or Strains Complex Stresses or Strains
Element Name Item Item Real/Mag. or
(Code) Code Item Code Item Imag./Phase
7 Y-coordinate of output point C
8 Z-coordinate of output point C
9 W-coordinate of output point
C
10 Normal x at C 10 Normal x at C RM
11 Shear xy at C 11 Shear xy at C RM
12 Shear zx at C 12 Shear zx at C RM
13 Normal x at C IP
14 Shear xy at C IP
15 Shear zx at C IP
13-18 Repeat items 7-12 for output 16-24 Repeat items 7-15 for output
point D point D
19-24 Repeat items 7-12 for output 25-33 Repeat items 7-15 for output
point E point E
25-30 Repeat items 7-12 for output 34-42 Repeat items 7-15 for output
point F point F
31 Max longitudinal
32 Min longitudinal
33-60 Repeat items 5-32 for end 2 43-80 Repeat items 5-42 for end 2

Main Index
 1040 CBAR (34)
Element Force Item Codes

Element Force Item Codes

All items are element forces (or moments) unless otherwise indicated.

Table 6-6 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
3 Bending End A plane 2 31 Bending End A plane 2 RM
Linear
41 Bending End B plane 1 41 Bending End B plane 1 RM
1
5 Bending End B plane 2 51 Bending End B plane 2 RM
1
6 Shear plane 1 61 Shear plane 1 RM
1
7 Shear plane 2 71 Shear plane 2 RM
81 Axial force 81 Axial force RM
1
9 Torque 91 Torque RM
1
10 Bending End A plane 1 IP
1
11 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
3 Bending Moment Plane 1 3 Bending Moment Plane 1 RM
Intermediate
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

Main Index
 CBEAM (2) 1041
Element Force Item Codes

Table 6-6 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
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 for end B 11 Shear Force Plane 1 IP
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

3 Station distance/length 3 Station distance/length
Linear
41 Bending moment plane 1 41 Bending moment plane 1 RM
51 Bending moment plane 2 51 Bending moment plane 2 RM
1
6 Web shear plane 1 61 Web shear plane 1 RM
1
7 Web shear plane 2 71 Web shear plane 2 RM
1
8 Axial force 81 Axial force RM
91 Total torque 91 Total torque RM
101 Warping torque 101 Warping torque RM
1
(Item codes are given for end A. 11 Bending moment plane 1 IP
Addition of the quantity (K-1) 9 to the 1
item code points to the same 12 Bending moment plane 2 IP
information for other stations, where K
is the station number. K=11 for end B 131 Web shear plane 1 IP
and 2 through 10 for intermediate
stations.) 141 Web shear plane 2 IP
1
15 Axial force IP
1
16 Total torque IP
171 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.)

Main Index
 1042 CBEAM3 (184)
Element Force Item Codes

Table 6-6 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
CBEAM3 2 External grid point ID 2 External grid point ID
(184) 3 Bending moment in y- 3 Bending moment in y- RM
direction direction
Linear
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
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
3 Bending moment plane 1 31 Bending moment plane 1 RM
1
4 Bending moment plane 2 41 Bending moment plane 2 RM
1
5 Shear plane 1 51 Shear plane 1 RM
61 Shear plane 2 61 Shear plane 2 RM
1
7 Axial force 71 Axial force RM

Main Index
 CBUSH (102) 1043
Element Force Item Codes

Table 6-6 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
81 Torque 81 Torque RM
1
(Item codes are given for end A. Item 9 Bending moment plane 1 IP
codes 9 through 15 point to the same
information for end B.) 101 Bending moment plane 2 IP
1
11 Shear plane 1 IP
1
12 Shear plane 2 IP
1
13 Axial force IP
141 Torque IP
(Item codes are given for end A.
Item codes 15 through 27 point to
the same information for end B.)

CBUSH 21 Force-x 21 Force-x RM

(102) 31
Force-y 31 Force-y RM
1
4 Force-z 41 Force-z RM
1
5 Moment-x 51 Moment-x RM
1
6 Moment-y 61 Moment-y RM
71 Moment-z 71 Moment-z RM
1
8 Force-x IP
1
9 Force-y IP
1
10 Force-z IP
111 Moment-x IP
1
12 Moment-y IP
1
13 Moment-z IP
CCONEAX 2 Harmonic or point angle Not applicable
(35) 3 Bending moment v
4 Bending moment u
5 Twist moment
6 Shear v
7 Shear u
CDAMP1 Same as CELAS1 Same as CELAS1
(20)
CDAMP2 Same as CELAS1 Same as CELAS1
(21)

Main Index
 1044 CDAMP3 (22)
Element Force Item Codes

Table 6-6 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
CDAMP3 Same as CELAS1 Same as CELAS1
(22)
CDAMP4 Same as CELAS1 Same as CELAS1
(23)
CDUM3 thru 21 F1 21 F1 RM
CDUM9 (55 - 31
F2 31 F2 RM
61)
41 F3 41 F3 RM
1
5 F4 51 F4 RM
1
6 F5 61 F5 RM
1
7 F6 71 F6 RM
81 F7 81 F7 RM
1
9 F8 91 F8 RM
1
10 F9 101 F9 RM
1
11 F1 IP
121 F2 IP
1
13 F3 IP
1
14 F4 IP
1
15 F5 IP
161 F6 IP
1
17 F7 IP
1
18 F8 IP
1
19 F9 IP
1 1
CELAS1 2 Force 2 Force RM
(11) 3 Force 3 Force IP
CELAS2 Same as CELAS1 Same as CELAS1
(12)
CELAS3 Same as CELAS1 Same as CELAS1
(13)
CELAS4 Same as CELAS1 Same as CELAS1
(14)
CGAP (38) 2 Normal x Not applicable
3 Shear y

Main Index
 CONROD (10) 1045
Element Force Item Codes

Table 6-6 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 Shear z
5 Axial u
6 Shear v
7 Shear w
8 Slip v
9 Slip w
CONROD 21 Axial force 21 Axial force RM
(10)
31 Torque 31 Axial force IP
1
4 Torque RM
51 Torque IP
CQUAD4 21 Membrane force x 21 Membrane force x RM
(33) 31
Membrane force y 31 Membrane force y RM
Linear 41
Membrane force xy 41 Membrane force xy RM
51 Bending moment x 51 Bending moment x RM
1
6 Bending moment y 61 Bending moment y RM
1
7 Bending moment xy 71 Bending moment xy RM
1
8 Shear x 81 Shear x RM
91 Shear y 91 Shear y RM
1
10 Membrane force x IP
1
11 Membrane force y IP
1
12 Membrane force xy IP
1
13 Bending moment x IP
1
14 Bending moment y IP
1
15 Bending moment xy IP
1
16 Shear x IP
171 Shear y IP
CQUAD4 2-3 Theory or blank Not applicable
(95) 4 Lamina number
Composite 5 FP (failure index)
/SP (strength ratio)
for direct stresses
6 Failure mode for

Main Index
 1046 CQUAD4 (144)
Element Force Item Codes

Table 6-6 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
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 1 EID 1 EID
(144) 2 CEN/ 2 CEN/
Corner Output 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
 CQUAD8 (64) 1047
Element Force Item Codes

Table 6-6 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 1 EID 1 EID
(64) 2 CEN/ 2 CEN/
Linear 3 4 3 4
1
4 Membrane force x 41 Membrane force x RM
51 Membrane force y 51 Membrane force y RM
1
6 Membrane force xy 61 Membrane force xy RM
1
7 Bending moment x 71 Bending moment x RM
1
8 Bending moment y 81 Bending moment y RM
91 Bending moment xy 91 Bending moment xy RM
1
10 Shear x 101 Shear x RM
1
11 Shear y 111 Shear y RM
1
12 Grid1 12 Membrane force x IP
13-20 Same as items 4 through 11 131 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
1
40-47 Same as items 4 through 11 19 Shear y IP
for corner 4
20 Grid1
21-36 Same as items 4 through
19 for corner 1
37 37 Grid2

Main Index
 1048 CQUAD82 (96)
Element Force Item Codes

Table 6-6 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 Same as CQUAD4(95) Same as CQUAD4(95)

(96)
Composite
CQUADR Same as CQUAD8(64) Same as CQUAD8(64)
(82)
CQUADR Same as CQUAD4(33) Same as CQUAD4(33)
(235)
Center

Main Index
 CROD (1) 1049
Element Force Item Codes

Table 6-7 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)

CSHEAR (4) 21 Force 4 to 1 21 Force 4 to 1 RM

1
3 Force 2 to 1 31 Force 2 to 1 RM
1
4 Force 1 to 2 41 Force 1 to 2 RM
1
5 Force 3 to 2 51 Force 3 to 2 RM
1
6 Force 2 to 3 61 Force 2 to 3 RM
71 Force 4 to 3 71 Force 4 to 3 RM
1
8 Force 3 to 4 81 Force 3 to 4 RM
1
9 Force 1 to 4 91 Force 1 to 4 RM
1
10 Kick force on 1 101 Force 4 to 1 IP
111 Shear 12 111 Force 2 to 1 IP
1
12 Kick force on 2 121 Force 1 to 2 IP
1
13 Shear 23 131 Force 3 to 2 IP
1
14 Kick force on 3 141 Force 2 to 3 IP
151 Shear 34 151 Force 4 to 3 IP
1
16 Kick force on 4 161 Force 3 to 4 IP
1
17 Shear 41 171 Force 1 to 4 IP
1
18 Kick force on 1 RM
191 Shear 12 RM
1
20 Kick force on 2 RM
1
21 Shear 23 RM
1
22 Kick force on 3 RM
231 Shear 34 RM
1
24 Kick force on 4 RM
1
25 Shear 41 RM
1
26 Kick force on 1 IP
271 Shear 12 IP
1
28 Kick force on 2 IP
1
29 Shear 23 IP
1
30 Kick force on 3 IP
311 Shear 34 IP

Main Index
 1050 CTRIA3 (74)
Element Force Item Codes

Table 6-7 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
321 Kick force on 4 IP
1
33 Shear 41 IP
CTRIA3 (74) Same as CQUAD4(33) Same as CQUAD4(33)
Linear

CTRIA32 Same as CQUAD4(95) Same as CQUAD4(95)

(97)
Composite
CTRlA6 (75) 41 Membrane force x 41 Membrane force x RM
Linear 1 51
5 Membrane force y Membrane force y RM
1 61
6 Membrane force xy Membrane force xy RM
71 Bending moment x 71 Bending moment x RM
81 Bending moment y 81 Bending moment y RM
1 91
9 Bending moment xy Bending moment xy RM
1 101
10 Shear x Shear x RM
111 Shear y 111 Shear y RM
1
13-20 Same as items 4 through 11 12 Membrane force x IP
for corner 1
22-29 Same as items 4 through 11 131 Membrane force y IP
for corner 2
31-38 Same as items 4 through 11 141 Membrane force xy IP
for corner 3
151 Bending moment x IP
1
16 Bending moment y IP
1
17 Bending moment xy IP
181 Shear x IP
191 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 Same as CQUAD4(95) Same as CQUAD4(95)

(98)
Composite

Main Index
 CTRIAR (70) 1051
Element Force Item Codes

Table 6-7 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
CTRIAR (70) Same as CTRIA6(75) Same as CTRIA6(75)

CTRIAR Same as CQUAD4(33) Same as CQUAD4(33)

(236)
Center
CTUBE (3) Same as CONROD(10) Same as CONROD(10)

CVlSC (24) Not applicable Same as CONROD(10)

CWELDP 2 mz bending end A plane 1 2 mz bending end A plane 1 RM

(118) 3 my bending end A plane 2 3 my bending end A plane 2 RM
if PARTPAT or 4 mz bending end B plane 1 4 mz bending end B plane 1 RM
ELPAT
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 9 mx torque 9 mx torque RM
(117) 10 mz bending end A plane 1 IP
if MSET = OFF 11 my bending end A plane 2 IP
CWELD 12 mz bending end B plane 1 IP
(200) 13 my bending end B plane 2 IP
if MSET = ON 14 fy shear force plane 1 IP
15 fz shear force plane 2 IP
16 fx axial force IP
17 mx torque IP
VUQUAD 1 VU element ID * 10 + device
code
(189)
VUTRIA 2 Parent p-element ID
(190) 3 CID coordinate system ID
for QUADp and 4 ICORD flat/curved etc.
TRIAp if 4th char.
of ICORD=X Y, Z 5 THETA material angle
(local coordinate
system) 6 0.0
7 VU grid ID for corner 1
8 Membrane Force x 8 Membrane Force x RM
9 Membrane Force y 9 Membrane Force y RM

Main Index
 1052 VUQUAD (189) VUTRIA (190)
Element Force Item Codes

Table 6-7 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
10 Membrane Force xy 10 Membrane Force xy RM
11 0.0 11 0.0 RM
12 0.0 12 0.0 RM
13 0.0 13 0.0 RM
14 Bending Moment x 14 Bending Moment x RM
15 Bending Moment y 15 Bending Moment y RM
16 Bending Moment xy 16 Bending Moment xy RM
17 Shear zx 17 Shear zx RM
18 Shear yz 18 Shear yz RM
19 0.0 19 0.0 RM
20 Membrane Force x IP
21 Membrane Force y IP
22 Membrane Force xy IP
23 0.0 IP
24 0.0 IP
25 0.0 IP
26 Bending Moment x IP
27 Bending Moment y IP
28 Bending Moment xy IP
29 Shear zx IP
30 Shear yz IP
31 0.0 IP
20-32 Repeat items 7-19 for corner 2 32-56 Repeat items 7-31 for
corner 2
33-45 Repeat items 7-19 for corner 3 57-81 Repeat items 7-31 for
corner 3
46-58 Repeat items 7-19 for corner 4 82-106 Repeat items 7-31 for
(VUQUAD) corner 4 (VUQUAD)

Main Index
 VUQUAD (189) VUTRIA (190) 1053
Element Force Item Codes

Table 6-7 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
VUQUAD 1 VU element ID *10 + device
code
(189)
VUTRIA 2 Parent p-element ID
(190) 3 CID coordinate system ID
for QUADp and 4 ICORD flat/curved etc.
TRIAp if 4th char.
of ICORD=F 5 THETA material angle
(fixed coordinate
system)
6 0.0
7 VU grid ID for corner 1
8 Membrane Force x 8 Membrane Force x RM
9 Membrane Force y 9 Membrane Force y RM
10 Membrane Force xy 10 Membrane Force xy RM
11 Membrane Force yz 11 Membrane Force yz RM
12 Membrane Force zx 12 Membrane Force zx RM
13 Membrane Force z 13 Membrane Force z RM
14 Bending Moment x 14 Bending Moment x RM
15 Bending Moment y 15 Bending Moment y RM
16 Bending Moment xy 16 Bending Moment xy RM
17 Bending Moment yz 17 Bending Moment yz RM
18 Bending Moment zx 18 Bending Moment zx RM
19 Bending Moment z 19 Bending Moment z RM
20 Membrane Force x IP
21 Membrane Force y IP
22 Membrane Force xy IP
23 Membrane Force yz IP
24 Membrane Force zx IP
25 Membrane Force z IP
26 Bending Moment x IP
27 Bending Moment y IP
28 Bending Moment xy IP
29 Bending Moment yz IP
30 Bending Moment zx IP
31 Bending Moment z IP

Main Index
 1054 VUBEAM (191)
Element Force Item Codes

Table 6-7 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
20-32 Repeat items 7-19 for corner 2 32-56 Repeat items 7-31 for
corner 2
33-45 Repeat items 7-19 for corner 3 57-81 Repeat items 7-31 for
corner 3
46-58 Repeat items 7-19 for corner 4 82-106 Repeat items 7-31 for
(VUQUAD) corner 4 (VUQUAD)
VUBEAM 1 VU element ID * 10 + device
code
(191)
for BEAMp 2 Parent p-element ID
3 CID coordinate system ID
4 ICORD (not used)
5 VU grid ID for end 1
6 x/L position
7 Force x 7 Force x RM
8 Shear Force y 8 Shear Force y RM
9 Shear Force z 9 Shear Force z RM
10 Torsional Moment x 10 Torsional Moment x RM
11 Bending Moment y 11 Bending Moment y RM
12 Bending Moment z 12 Bending Moment z RM
13 Force x IP
14 Shear Force y IP
15 Shear Force z IP
16 Torsional Moment x IP
17 Bending Moment y IP
18 Bending Moment z IP
13-20 Repeat items 5-12 for end 2 19-32 Repeat items 5-18 for end
2

Main Index
 VUBEAM (191) 1055
Fluid Virtual Mass Pressure Item Codes

Fluid Virtual Mass Pressure Item Codes

Table 6-8 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 6-9 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
8 Total
CHBDYG Same as Same as CHBDYE
(108) CHBDYE
CHBDYP Same as Same as CHBDYE
(109) CHBDYE

Main Index
 1056 CSLIFID (116)
2D Slideline and 3D Surface Contact Item Codes

2D Slideline and 3D Surface Contact Item Codes

Table 6-10 Contact Item Codes
Real Element Data
Element Name Item
(Code) Code Slideline Item 3D Surface Item (SOL 600)
CSLIFID (116) 1 Slave grid point GRID ID
2 Contact region identification number (39) Contact Touched Body
3 Master grid 1
4 Master grid 2
5 Surface coordinate (38) Contact Status
6 Normal force (35) Normal Force
7 Shear force (37) Friction Force
8 Normal stress (34) Normal Stress
9 Shear stress (36) Friction Stress
10 Normal gap
11 Slip
12 Slip ratio (Shear force/u*normal force)
13-14 Slip code (Character)

Notes:
1. Numbers in parenthesis refer to MARCOUT nodal post codes.
2. 3D Surface contact is available in SOL 600 only.

Main Index
 203 1057
2D Slideline and 3D Surface Contact Item Codes

Table 6-11 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 fy

Table 6-12 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

Remarks:
1. F nx, F ny, F nz are normal force components in the global coordinate system.

Main Index
 1058 203
2D Slideline and 3D Surface Contact Item Codes

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 slave grids (touching node) only.
6. A slave grid may not contact more than 3 bodies.
7. Only slave 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 6-11 and Table 6-12 are saved in datablock OFCON3D.

Main Index
 203 1059
Element Strain Energy Item Codes

Element Strain Energy Item Codes

Table 6-13 Element Strain Energy Item Codes
Real Element Data
Item
Element Name 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, CQUAD4, CQUADR, CROD, CSHEAR, CTETRA, CTRIA3, CTRIA6, CTRIAR,
and CTUBE. Element group B includes elements of CELAS1, CELAS2, CELAS3, AND CGAP.

Main Index
 1060 203
Fatigue Item Codes

Fatigue Item Codes

Table 6-14 Fatigue Item Codes for LOC=ELEMENT 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 15 Fatigue life in Repeats of the loading sequence
(for Z2 layer - top) 16 Log of fatigue life in Repeats of the loading sequence
17 Fatigue life in user defined fatigue equivalent units
18 Log of fatigue life in user defined fatigue equivalent units
19 Fatigue damage
20 Log of fatigue damage
23 Scale factor from Factor of Safety analysis

Remark:
1. Element Group A consists of elements: CHEXA, CPENTA, CTETRA, CTRIA3, CSHEAR
2. Element Group B consists of elements: CQUAD4, CQUAD8, CQUADR, CTRIA6, CTRIAR
3. For CTRIA3 and CSHEAR elements, LOC=ELEMENT and LOC=NODE options on
FTGPARM use the same item codes in Table 6-14.
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
 203 1061
Fatigue Item Codes

Table 6-15 Fatigue Item Codes for LOC=NODE 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,27,50,73 Life in Repeats of the loading sequence
CQUAD8 (-4,-27,-50,-73) See remark 7.
CQUADR 5,28,51,74 Log of life in Repeats of the loading sequence
(for Z1 layer - bottom) (-5,-28,-51,-74)
6,29,52,75 Life in user defined fatigue equivalent units
(-6,-29,-52,-75)
7,30,53,76 Log of life in user defined equivalent units
(-7,-30,-53,-76)
8,31,54,77 Fatigue damage
(-8,-31,-54,-77)
9,32,55,78 Log of fatigue damage
(-9,-32,-55,-78)
12,35,58,81 Scale factor from Factor of Safety analysis
(-12,-35,-58,-81)
(for Z2 layer - top) 15,38,61,84 Life in Repeats of the loading sequence
16,39,62,85 Log of life in Repeats of the loading sequence
17,40,63,86 Life in user defined fatigue equivalent units
18,41,64,87 Log of life in user defined equivalent units
19,42,65,88 Fatigue damage
20,43,66,89 Log of fatigue damage
23,46,69,92 Scale factor from Factor of Safety analysis

Main Index
 1062 203
Fatigue Item Codes

Table 6-15 Fatigue Item Codes for LOC=NODE on FTGPARM

Element Name Item Codes Real Element Data Item
CTRIA6 4,27,50 Life in Repeats of the loading sequence
CTRIAR (-4,-27,-50) See remark 7.
(for Z1 layer - bottom) 5,28,51 Log of life in Repeats of the loading sequence
(-5,-28,-51)
6,29,52 Life in user defined fatigue equivalent units
(-6,-29,-52)
7,30,53 Log of life in user defined equivalent units
(-7,-30,-53)
8,31,54 Fatigue damage
(-8,-31,-54)
9,32,55 Log of fatigue damage
(-9,-32,-55)
12,35,58 Scale factor from Factor of Safety analysis
(-12,-35,-58)
(for Z2 layer - top) 15,38,61 Life in Repeats of the loading sequence
16,39,62 Log of life in Repeats of the loading sequence
17,40,63 Life in user defined fatigue equivalent units
18,41,64 Log of life in user defined equivalent units
19,42,65 Fatigue damage
20,43,66 Log of fatigue damage
23,46,69 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
 203 1063
Fatigue Item Codes

Table 6-15 Fatigue Item Codes for LOC=NODE on FTGPARM

Element Name Item Codes Real Element Data Item
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. CQUAD4, CQUAD8, CQUADR, CTETRA item codes are listed for Grids 1-4, respectively.
2. CTRIA6 and CTRIAR item codes are listed for Grids 1-3, respectively.
3. CPENTA item codes are listed for Grids 1-6, respectively.
4. CHEXA item codes are listed for Grids 1-8, respectively.
5. For CTRIA3 and CSHEAR elements, LOC=ELEMENT and LOC=NODE options on
FTGPARM use the same item codes in Table 6-14.
6. If it is desired to use a life response (or other item) for all nodes (using LOC=NODE 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).
7. 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
8. These item codes are used for LOC=NODE and all other element nodal values of LOC on the
FTGPARM entry, namely, “SGAGE”, “CORNER”, “BILIN”, and “CUBIC” also.

Main Index
 1064 203
Fatigue Item Codes

Table 6-16 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
degrees) units
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 7+12*NANGLE Log of fatigue life in user defined fatigue equivalent
Nugget at Angle units
= 0.0 degrees) 8+12*NANGLE Fatigue damage
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
Sheet at Angle = units
0.0 degrees) 8+24*NANGLE Fatigue damage
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
 203 1065
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.

Main Index
 1066 203
Fatigue Item Codes

Table 6-17 Item Codes for Fatigue Analysis of Seam Welds

Element Name Item Code Real Element Data Item
CQUAD4 4, 16, 28, 40 Fatigue life in Repeats of the loading sequence
CQUAD8 5, 17, 29, 41 Log of fatigue life in Repeats of the loading sequence
CQUADR
6, 18, 30, 42 Fatigue life in user defined fatigue equivalent units
7, 19, 31, 43 Log of fatigue life in user defined fatigue 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
CTRIA6 4, 16, 28 Fatigue life in Repeats of the loading sequence
CTRIAR 5, 17, 29 Log of fatigue life in Repeats of the loading sequence
6, 18, 30 Fatigue life in user defined fatigue equivalent units
7, 19, 31 Log of fatigue life in user defined fatigue equivalent units
8, 20, 32 Fatigue damage
9, 21, 33 Log of fatigue damage
12, 24, 36 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
 203 1067
Equivalent Radiated Power (ERP) Item Codes

Equivalent Radiated Power (ERP) Item Codes

Table 6-18 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
 1068 203
Equivalent Radiated Power (ERP) Item Codes

Main Index
 Degree-of-Freedom Sets MSC Nastran Quick Reference Guide

7 Degree-of-Freedom Sets

 Degree-of-Freedom Set Definitions


Degree-of-Freedom Set Bulk Data Entries

Main Index
 1070 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
 Degree-of-Freedom Sets 1071
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 + lm the 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 + mr all 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
 1072 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 – lm ne-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, BSETi, or CSETi
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:

uh = ξ i + u e , the set of all modal degrees-of-freedom

Main Index
 Degree-of-Freedom Sets 1073
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
 1074 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, GMBC, GMSPC*
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

*Placed in set only if constraints are not specified in the basic coordinate system.

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
 Bulk Data Entries MSC Nastran Quick Reference GuideMSC Nastran Quick Reference Guide

8 Bulk Data Entries


Key to Descriptions
 Bulk Data Entry Descriptions

Main Index
 1076 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 ModelingIfParameters

a box in fields 2 through
9 is shaded, then the field
Defines modeling parameters for the interface between the fluid and themust be left blank.
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
INFORIndicates whether FSET and SSET are to bedetails maythe
used to define befluid-structure
discussedinterface.
under(Character
Remarks. =
“ALL”
Character or “NONE”,
constants areDefault = “NONE”).
enclosed in
quotation marks to distinguish
FSETIdentification number ofthem from
a SET1 entry that contains a list of fluid grid points on the interface. See
field names.
RemarkDo
2. not input
(Integer > 0these quotation
or blank).
marks. Under contents, “blank” usually means that
this
SSETIdentification number of a SET1 entry that contains feature
a list cangrid
of structural bepoints
optionally 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 determining the fluid-structure interface. (Real > 0.0; Default =
0.001). content item is listed as, for example,
(Integer>0 or blank) a value of 0 entered in
the field is equivalent to "blank".
Remarks:
1. Only one ACMODL entry is allowed.
The If this entrytype
field’s is not(Integer,
present, then the program
Real, will
or Character),
assume INTER = “DIFF” and FSTOL = .001. range, and default value are enclosed
allowable
2. If INFOR = “ALL”, then both FSETinand parentheses. If no default
SSET must be specified value isisgiven, then
and matching
a valuebymust
checked at only those grid points referenced FSETbeandspecified
SSET. by the user.
3. See the MSC Nastran Reference Manual, 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. A fatal message is issued if: (a) INTER = “IDENT” and a point in SSET or
The remarks are generally arranged in order of
FSET does not have a corresponding and coincident point in FSET or SSET,
importance and indicate such things as the
respectively, or (b) INTER = “DIFF” and any point in SSET or FSET does not lie on the
entry’s relationship to other entries or
interface.
commands, restrictions, and recommendations
on usage, or further details regarding the fields.

Main Index
 Bulk Data Entries 1077
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. Entries that are used by the MSGMESH program are not included in this guide. For a
description of the various format options and the MSGMESH entries, see the Use of Parameters (p. 29)
in the MSC Nastran Reference Manual.
New Bulk Data Entries added after the MSC Nastran 2011 version are only valid with the default option
IFPSTAR=YES.

Main Index
 1078 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.

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
 Bulk Data Entries 1079
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, NASTRAN IFPSTAR=YES (default) is
used 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, 1084 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.

Main Index
 1080 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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 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 This shaded box means that a
data continuation is not used
for the GRID 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.

Main Index
 Bulk Data Entries 1081
Bulk Data Entry Descriptions

• 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.
• 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

• 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

Main Index
 1082 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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:
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

Main Index
 Bulk Data Entries 1083
Bulk Data Entry Descriptions

MATT9,1355,2 ,3 ,,5 ,,,8 ,+

*,,10 ,,,+
+,17

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

Main Index
 1084 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
• 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

Main Index
 Bulk Data Entries 1085
Bulk Data Entry Descriptions

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):

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 103 5 7115 17 +000001
2-++00000119 134 6 8210 11 +000002
3-++00000212 916 18 2014 +000003

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.

Main Index
 1086 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

3. The continuation fields are incremented by +1 regardless of the value specified by the user.
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. The MSGMESH capability includes the capabilities described here, plus the following
capabilities as long as NASTRAN MESH is specified in the File Management Section.
• 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
=(4), *(1),=,*(0.2),==$
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:

Main Index
 Bulk Data Entries 1087
Bulk Data Entry Descriptions

BSET1,123,1,2,3,4,5,6,7
,,*7,*7,*7,*7,*7,*7,*7
=(3)
Generated entries:

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:

Main Index
 1088 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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
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.

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 SOL 600 have been grouped together at the end of the summary. 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.

Main Index
 Bulk Data Entries 1089
Bulk Data Entry Descriptions

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 fixed boundary points for superelement.
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.
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.

Main Index
 1090 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

Multipoint Constraints

MONSUM Defines a new monitor result that is the weighted sum of existing monitor results.
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.

p-element Geometry Constraints

GMBC Defines enforced displacements for GRID, FEEDGE, FEFACE, GMCURV, and
GMSURF entries.
GMSPC Defines constraints for entries.

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
 Bulk Data Entries 1091
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.
SPCOFF 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 -- Small Strain Elements (p. 43) in the MSC Nastran Reference Manual.

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.

Main Index
 1092 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
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.

Main Index
 Bulk Data Entries 1093
Bulk Data Entry Descriptions

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.
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.
MREVERS Defines which elements, if any, required node numbering to be reversed in SOL 600.
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.

Main Index
 1094 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
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.

Contact or Gap Elements

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.
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.

Main Index
 Bulk Data Entries 1095
Bulk Data Entry Descriptions

Damping Elements

CBUSH1D See line elements.

CDAMPi 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.
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).

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.

Main Index
 1096 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
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.
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.

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.
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.
CBEAM3 Defines a three-node beam element.

Main Index
 Bulk Data Entries 1097
Bulk Data Entry Descriptions

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.
CMREBAI Defines Rebar elements and matching “Matrix” solid element using the Marc REBAR
with INSERT Method. (SOL 600)
CMREBAR Defines Rebar elements with matching “Matrix” solid elements using the Marc
REBAR without INSERT Method. (SOL 600)
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).
PMREBAI Defines Rebar property information for CMREBAI elements. (SOL 600)
PMREBAR Defines Rebar property information for CMREBAR elements. (SOL 600)

Main Index
 1098 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.

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).

p-element Interface Elements

GMINTC Defines a p-interface element along a curve.

GMINTS Defines a p-interface element along a surface.
PINTC Property definition for GMINTC.
PINTS Property definition for GMINTS.

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.

Main Index
 Bulk Data Entries 1099
Bulk Data Entry Descriptions

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.
MGRSPR Defines grids to add soft spring to ground. (SOL 600)
PBUSH Defines the nominal property values for a generalized spring-and-damper structural
element.
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.
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.

Main Index
 1100 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

PSOLID Defines the properties of solid elements (CHEXA, CPENTA, and CTETRA entries).
PSOLIDD Additional property specification information may be provided using the entry when
materials MATD010 or MATD015 are used.

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. (SOLs 400/600 only)
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.
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.

Main Index
 Bulk Data Entries 1101
Bulk Data Entry Descriptions

Geometry
Adaptive Meshing

HADACRI Specifies Mesh adaptivity criterion and corresponding parameters.

HADAPTL Specifies local adaptive Mesh refinement control parameters.

Aeroelastic Control 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.
UXVEC Specification of a vector of aerodynamic control point (extra point) values.

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.
CORDiC Cylindrical coordinate system definition.

Main Index
 1102 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

CORDiR Rectangular coordinate system definition.

CORDiS 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.
NLCYSYM Defines information to perform nonlinear cyclic symmtry analysis using SOL 600

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.

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
 Bulk Data Entries 1103
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.

p-Element and p-Adaptivity Analysis

FEEDGE Defines a finite element edge and associates it with a curve.

FEFACE Defines geometric information that will be used in elements, surface definition, load
definition, and boundary condition definition.
GMBNDC Defines a geometric boundary consisting of p-element edges along a curve interface.
The boundary may consist of edges of shell, beam, or p-solid elements.
GMBNDS Defines a geometric boundary consisting of p-element faces along a surface interface.
The boundary may consist of faces of p-solid or p-shell elements.
GMCORD Defines a convective/follower coordinate system on an FEEDGE, GMCURV, FEFACE,
or GMSURF entry.
GMCURV Defines geometric curve that will be used in element geometry, load definition, and
boundary condition definition.
GMINTC Defines curve interface elements to connect dissimilar meshes.
GMINTS Defines an interface element along a surface interface between boundaries of multiple
subdomains.
GMSURF Defines geometric information that will be used in elements, surface definition, load
definition, and boundary condition definition.
PINTC Defines properties for curve interface elements (see GMINTC).
PINTS Defines the properties for interface elements along surface interfaces between
boundaries of multiple subdomains of p-elements.
POINT Define edge point for FEEDGE entry.

Scalar Points

EPOINT Defines extra points for use in dynamic problems.

SEQGP Grid and scalar point number resequencing.
SPOINT Defines scalar points.

Main Index
 1104 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
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.
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
 Bulk Data Entries 1105
Bulk Data Entry Descriptions

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.
NOLINi Nonlinear transient load definition.
NLRGAP Defines a nonlinear transient radial (circular) gap.
RBE3U Defines methods to distribute applied loads to a surface. (SOL 600)
RLOADi Frequency dependent excitation definition.
TABLEDi Tabular functions for generating dynamic loads.
TLOADi 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.
QBDY3 Defines a uniform heat flux load for a boundary surface.

Main Index
 1106 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
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.
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.

Main Index
 Bulk Data Entries 1107
Bulk Data Entry Descriptions

p-element Loads

GMBC Defines enforced displacements for GRID, FEEDGE, GMCURV, FEFACE, and
GMSURF entries.
GMCONV Defines convection boundary conditions.
GMLOAD Defines the forces and moments to be applied to a FEEDGE, GMCURV, FEFACE,
or GMSURF entry.
GMQVOL Defines volumetric heat loads.
TEMPF Defines the thermal loading to be applied to a group of elements.

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.
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

Main Index
 1108 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
LOADOF Specifies table IDs for individual degrees of freedom for the static loads with tables
described using LOADT entries for SOL 600 only.
LOADT Specifies static loads that will use a table to describe their variation with pseudo-
time.
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.
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.
RBE3U Defines methods to distribute applied loads to a surface. (SOL 600)
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.

Main Index
 Bulk Data Entries 1109
Bulk Data Entry Descriptions

TEMPPi 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).

Fatigue

MATFTG Defines cyclic material properties (S-N + ε -N) for use in fatigue analysis.

Fluid

AXIF Includes default values for mass density and bulk modulus.
AXSLOT Includes default values for mass density and bulk modulus.
BDYLIST Defines the boundary between a fluid and a structure.
CFLUIDi Includes mass density and bulk modulus.
CSLOTi 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.

Main Index
 1110 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.
TABLEMi 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.
TEMPD Defines a temperature value for all grid points of the structural model that have not
been given a temperature on a TEMP entry.
TEMPPi 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.

Main Index
 Bulk Data Entries 1111
Bulk Data Entry Descriptions

Miscellaneous
Brake Squeal (SOL 400)

BSQUEAL Specifies data for brake squeal analysis using Implicit Nonlinear (SOL 400).

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.
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.

Main Index
 1112 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

Include File

INCLUDE Inserts an external file into the input file. The INCLUDE statement may appear
anywhere within the input data file.

Materials (SOLs 400/600)

COHESIV Defines data for cohesive materials.

MATEP Elasto-plastic material properties.
MATF Specifies material failure model.
MATG Gasket material properties.
MATHE Hyperelastic material properties.
MATHED Damage model properties for hyperelastic materials.
MATNLE The MATNLEx entries specify advanced forms of nonlinear elastic materials.
MATORT Elastic 3D orthotropic material properties.
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. SOL 400 only.
MATS8 Specifies NLELAST option for advanced orthotropic, nonlinear elastic material for
plane stress and shell elements SOL 400 only.
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
MDELAM Defines materials for which delamination may occur.

Non-Structural Mass Distribution Selection

NSM Non Structural Mass entry by id,value.

NSM1 Non Structural Mass entry by value,id.
NSMADD Non Structural Mass as sum of listed sets.

Main Index
 Bulk Data Entries 1113
Bulk Data Entry Descriptions

NSML Lumped non structural mass entry by id,value.

NSML1 Lumped non structural mass entry by value,id.

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 slave 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.
MARPRN Defines “print” options for SOL 600.
MLAYOUT Selects layered composite shell output to be placed in Marc’s t16 and/or t19 files
and (if requested) to be transferred from Marc to the Nastran Database. (SOL 600)
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.
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.

Main Index
 1114 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

p-element Output Control

OUTPUT Output control for p-adaptive analysis.

OUTRCV Defines options for the output of displacements, stresses, and strains of p-elements.

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.
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 Define model units for non-unitless operations.
TABDMP1 Defines modal damping as a tabular function of natural frequency.
TABLEDi Tabular functions for generating dynamic loads.
TABLEL1 Specifies a table of amplitude vs pseudo-time for static loads specified in LDTABL
entries SOL 600 and SOL 700 only.
TABLEMi 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).

Main Index
 Bulk Data Entries 1115
Bulk Data Entry Descriptions

TABL3D Specifies a table where an entry can be a function of up to 4 variables such as strain,
temperature, strain rate, etc. (SOLs 400/600)
TABLE3D Specify a function of three variables for the GMBC, GMLOAD, and TEMPF
entries only.
TABLFTG Defines cyclic load variation for use in fatigue analysis.
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. (SOLs 400/600)
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.
GMNURB 3D contact region made up of NURBS.
Old Contact Format
BCTABLE Defines a contact table.
BCBODY Defines a flexible rigid contact body in 2D or 3D.
New Contact Format
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

User-Defined Subroutines and Services

BCONUDS Allows the user to provide contact routines for use with enhanced MSC Nastran
contact analysis. (SOL 600 and SOL 400)
MATUDS Allows the user to provide material routines for use with enhanced MSC Nastran
material models. (SOL 600 and SOL 400)

Main Index
 1116 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

MATTUSR Specifies table variation of user defined generic materials in SOL 600 and SOL 400
only.
MATUSR Specifies user-defined, generic material properties for hypoelastic material models in
SOL 600 and user defined material models in SOL 400 only.

Nastran Implicit Nonlinear (SOL 600)

3D Contact Region (SOL 600)

BCBMRAD Allows the equivalent radius in beam-to-beam contact to be different for each beam
cross section. (SOL 600)
SANGLE Defines automatic analytical contact threshold angle for multiple subcases.
UNGLUE Defines grids that should be eliminated from glued contact for SOL 600 and SOL
400.
WEAR Specifies values for modeling mechanical wear in deformable contact bodies for SOL
600 only.

Analysis Termination Options (SOL 600)

TERMIN Control to terminate a SOL 600 analysis under certain conditions

Bolts (SOL 600)

MBOLT Defines a bolt for use in countries outside the USA.

MBOLTUS Defines a bolt for use in the USA and all other countries.

Brake Squeal (SOL 600)

BRKSQL Specifies data for brake squeal calculations using SOL 600.

Composite Integration Options (SOL 600)

MIXTURE Defines consitituents of “composite” material on original and potentionally damaged

state.
PCOMPF Defines the integration procedure for through the thickness integration of composite
shells.

Main Index
 Bulk Data Entries 1117
Bulk Data Entry Descriptions

Creep Analysis (SOL 600)

MACREEP Controls a transient creep analysis.

MPCREEP Specifies input values for Marc’s creep parameter when creep analysis is performed
using SOL 600.
MTCREEP Controls a transient thermal creep analysis. This entry or the MACREEP entry is
required if ITYPE is not zero on the MPCREEP entry.

Element Birth and Death (SOL 600)

ACTIVAT This entry allows the user to re-activate certain elements that were previously
deactivated in a previous subcase.
DEACTEL This entry allows the user to deactivate elements that have failed or are no longer
necessary in a particular subcase.

Elements (SOL 600)

ALIASM Allows selected elements which normally use a default formulation to be aliased to a
different formulation.
CSSHL Defines a connection for a Solid Shell with 6 or 8 grid points.
CSSHLH Defines conversion of CHEXA elements to Solid Shell elements.
CSSHLM Defines conversion of CHEXA or CPENTA elements described by material ID to
Solid Shell elements.
CSSHLP Defines conversion of CPENTA elements to Solid Shell elements.
MISLAND Defines an island of connected elements that will be completely removed if the
number of elements within the island becomes smaller than a specified value.

Element Properties (SOL 600)

NTHICK Defines nodal thickness values for beams, plates, and/or shells.
PSSHL Defines the properties for Solid Shell (CSSHL) elements.

Fatigue, Fracture and Crack Propagation (SOL 600)

LORENZI This option gives an estimation of the J-Integral for a crack configuration using the
domain integration method.
VCCT Virtual crack closure technique

Main Index
 1118 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

General Tables (SOL 600)

MTABRV Defines a list of tables to reverse positive and negative values and/or add points at
the lower and upper end of tables.
TABD1MD Defines how TABLED1 entries are internally modified in SOL 600.
TABL3D Specifies a table where an entry can be a function of up to 4 variables such as
strain, temperature, strain rate, etc.

Heat Transfer (SOL 600)

MPHEAT Maps to Marc’s HEAT parameter for SOL 600 heat transfer analysis.
MTHERM Iteration control for automatic thermal loading for structural analysis following a
heat transfer analysis.
NLHEATC Defines numerical analysis parameters for SOL 600 heat transfer analysis

Inertia Relief (SOL 600)

SUPORT6 Inertia relief used in Nastran Implicit Nonlinear (SOL 600 only).

Initial Conditions (SOL 600)

IPSTRN Defines initial plastic strain values.

ISTRESS Defines initial stress values.

Input/Output (SOL 600)

MARCIN Inserts a text string in Marc.

MARCOUT Selects data recovery output.

Matrix Input/Output (SOL 600)

DMIGOUT Defines DMIG matrices to be output from the Marc Portion of SOL 600.
DMIGROT Defines large rotation and other characteristics of a matrix entered using DMIG..
MDMIAUX Specifies the DOMAINSOLVER command to be used in conjunction with
secondary spawned jobs when MDMIOUT is used. SOL 600 only.
MDMIOUT Defines full or reduced stiffness and mass matrices to be output from the Marc
portion of SOL 600.

Main Index
 Bulk Data Entries 1119
Bulk Data Entry Descriptions

MESUPER Defines external superelement DMIG input for SOL 600 residual analyses
MNF600 Defines auxiliary data for MSC Adams MNF files.

Solid Composites (SOL 600)

MSTACK Defines the direction in which 3D solid composites are stacked.

Solution Control (SOL 600)

MPROCS Provides additional control for parallel processing

NLAUTO Parameters for automatic load/time stepping.
NLHEATC Defines damping constants.
NLSTRAT Strategy parameters for nonlinear structural analysis.
PARAMARC Parallel domain decomposition.
RESTART Restart data.

Structural Analysis Following a Heat Transfer Analysis (SOL 600)

MINSTAT This option is used to enter initial (stress free) temperatures calculated from a
previous heat transfer analysis and saved on a t16 or t19 file.

t16 Output Control (SOL 600)

MT16SEL Limits elements and/or grid results to selected elements or grids for t16 and t19
file results.
MT16SPL Determines how to split a Marc t16 file into one or more smaller t16 files.

User Subroutine Control (SOL 600)

USRSUB6 Defines user subroutines used in SOL 600 only.

Explicit Nonlinear (SOL 700)

Air Bags (SOL 700)

AIRBAG Defines an airbag.

GBAG Defines the pressure within an enclosed volume.

Main Index
 1120 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

GRIA Grid Point in Air Bag Reference Geometry

INFLFRC Defines the gas fractions as a function of time for hybrid inflators.

Contact (SOL 700)

BCTABLE Defines a contact table (old format).

BCTABL1 Defines a contact table (new format).
BCGRID Grids to be included in contact analyses.
BCSEG Grids which are part of an element to be used in contact analyses.

Coordinate Systems (SOL 700)

CORD1RX Alternate rectangular coordinate system specification for SOL 700.

CORD2RX Alternate rectangular coordinate system specification for SOL 700.
CORD3RX Alternate rectangular coordinate system specification for 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.
CSPR Springs with offsets for use in SOL 700.
DAMPMAS Defines mass weighted damping by property ID.
DAMPSTF Assigns Rayleigh stiffness damping coefficient by property ID.
PSPRMAT Defines spring and damper elements for translation and rotation.

Direct Text Input (SOL 700)

ENDDYNA Defines the end of direct text to Dytran-lsdyna.

TODYNA Defines the start of direct text to Dytran-lsdyna.

Main Index
 Bulk Data Entries 1121
Bulk Data Entry Descriptions

Dynamic Relaxation (SOL 700)

DAMPGBL Defines parameters to be used for static analysis simulation using Dynamic
Relaxation for use in SOL 700 only.
DYRELAX Define controls for dynamic relaxation for restart runs.

Element Properties (SOL 700)

CTQUAD Defines an isoparametric membrane-bending or plane strain triangular plate

element. (SOL 700 only).
CTTRIA Defines a six-node thick shell element which is available with either fully
reduced or selectively reduced integration rules.
PBEAM71 Defines complex beam properties that cannot be defined using the PBAR or
PBEAM entries.
PBEAM71 Defines more complex beam properties that cannot be defined using the PBAR
or PBEAM entries.
PBEAM71 Defines more complex beam properties that cannot be defined using the PBAR
or PBEAM entries.
PBEAMD Defines cross-sectional properties for beam, truss, discrete beam, and cable
elements.
PCOMPA Defines additional properties of a multi-ply laminate composite material.
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.
PSHELLD Defines properties for shell elements.
PSOLIDD Additional property specification information may be provided using this entry
when materials MATD010 or MATD015 are used.
PTSHELL Defines properties for thick shell elements (CTQUAD, CTTRIA).

Eulerian Boundary (SOL 700)

BARRIER Defines a barrier for transport in a Eulerian mesh.

BCSEG Grids which are part of an element to be used in SOL 700 contact analyses.
FLOW Defines the properties of a material for the boundaries of an Eulerian mesh.
FLOWDEF Definition of default Eulerian flow boundary condition.

Main Index
 1122 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

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.

Eulerian Materials (SOL 700)

EOSGAM Defines the properties of a Gamma Law equation of state where the pressure p
is defined.
EOSGRUN Used in Explicit Nonlinear (SOL 700) only.
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.
EOSPOL Defines the properties of a polynomial equation of state where the pressure p is
defined.
EOSTAIT Defines the properties of an equation of state based on the Tait model in
combination with a cavitation model 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.

Main Index
 Bulk Data Entries 1123
Bulk Data Entry Descriptions

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.
YLDMC Defines a Mohr-Coulomb yield model.
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.
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.

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.
GBAGCOU Defines a switch from full gas dynamics to uniform pressure formulation.

Main Index
 1124 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

HEATLOS Defines the heat-transfer model to be used with GBAG or COUPLE.

HTRCONV Defines the heat transfer through convection for a COUPLE and/or GBAG
surface.
HTRRAD Defines the heat transfer through radiation for a COUPLE and/or GBAG
surface.
INFLCG Defines the cold gas-inflator characteristics of a COUPLE and/or GBAG
subsurface.
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.
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.

Main Index
 Bulk Data Entries 1125
Bulk Data Entry Descriptions

Explicit/Implicit Analysis (SOL 700)

PRESTRS Performs a prestress run to calculate an initially stressed model and writes out the
initial state to a file that can be used for a subsequent explicit SOL 700 run.
SPRBCK Performs in springback analysis simulation to calculate the final shape of a model
after an explicit simulation has been performed. It must be started from a file that
contains stresses and nodal displacements that were created by a previously run
explicit SOL 700 simulation.

Hourglass Control (SOL 700)

HGSUPPR Defines the hourglass suppression method, the corresponding hourglass

damping coefficients and sets for the bulk viscosity method and coefficients.

Inertial Properties (SOL 700)

D2RINER Inertial properties can be defined for the new rigid bodies that are created when
the deformable parts are switched.

Initial Conditions (SOL 700)

ISTRSBE Initialize stresses and plastic strains in the Hughes-Liu beam elements.
ISTRSSH Initialize stresses, history variables and the effective plastic strain from shell
elements.
ISTRSSO Initialize stresses and plastic strains for solid elements.
ISTRSTS Initialize stresses, history variables and the effective plastic strain for thick shell
elements.
TICD Defines values for the initial conditions of variables used in structural transient
analysis. Both displacement and velocity values may be specified at independent
degrees-of-freedom. This entry may not be used for heat transfer analysis. Used
in Explicit Nonlinear (SOL 700) only.
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)

EOSPOL Defines the properties of a polynomial equation of state.

EOSTAB Defines tabular equation of state.
EOSTABC Defines tabular equation of state with compaction.

Main Index
 1126 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

MATD001 Isotropic elastic material available for beam, shell and solid elements. A
specialization of this material allows the modeling for fluids. The fluid option is
valid for solid elements only. Used in Explicit Nonlinear (SOL 700) only.
MATD2AN For modeling the elastic-anisotropic behavior of solids, shells, and thick shells.
Defines material properties for anisotropic materials in the LS-DYNA style.
Used in Explicit Nonlinear (SOL 700) only.
MATD2OR Used to model the elastic-orthotropic behavior of solids, shells, and thick shells.
For orthotropic solids and isotropic frictional damping is available. Used in
Explicit Nonlinear (SOL 700) only.
MATD003 Used to model isotropic and kinematic hardening plasticity with the option of
including rate effects. Used in Explicit Nonlinear (SOL 700) only.
MATD005 Used to model soil and foam. This is a very simple model and works in some
ways like a fluid. Used in Explicit Nonlinear (SOL 700) only.
MATD006 Used to model the viscoelastic behavior of beams, shells, and solids. Used in
Explicit Nonlinear (SOL 700) only.
MATD007 Used to model nearly incompressible continuum rubber. The Poisson’s ratio is
fixed to 0.463. Used in Explicit Nonlinear (SOL 700) only.
MATD009 This material allows equations of state to be considered without computing
deviatoric stresses.
MATD012 Low cost isotropic plasticity model for three-dimensional solids. This is the only
model in LS-DYNA for plane stress that does not default to an iterative
approach. Used in Explicit Nonlinear (SOL 700) only.
MATD013 This is a non-iterative plasticity with simple plastic strain failure model. Used in
Explicit Nonlinear (SOL 700) only.
MATD014 Input for this model is the same as for MATD005; however, when the pressure
reaches the failure pressure, the element loses its ability to carry tension. Used
in Explicit Nonlinear (SOL 700) only.
MATD015 Johnson/Cook strain and temperature sensitive plasticity sometimes used for
problems where the strain rates vary over a large range and adiabatic temperature
increases due to plastic heating cause material softening. Used in Explicit
Nonlinear (SOL 700) only.
MATD016 This model has been used to analyze buried steel reinforced concrete structures
subjected to impulsive loadings.
MATD018 An isotropic plasticity model with rate effects that uses a power law hardening
rule. Used in Explicit Nonlinear (SOL 700) only.
MATD019 Used to model strain rate dependent material. For an alternative, see MATD024.
Used in Explicit Nonlinear (SOL 700) only.
MATD020 Used to model rigid materials. Used in Explicit Nonlinear (SOL 700) only.
MATD20M Merges two or more rigid materials defined using MATD020. Used in Explicit
Nonlinear (SOL 700) only.

Main Index
 Bulk Data Entries 1127
Bulk Data Entry Descriptions

MATD022 Used to model an orthotropic material with optional brittle failure for
composites. Used in Explicit Nonlinear (SOL 700) only.
MATD024 Used to model an elasto-plastic material with an arbitrary stress versus strain
curve and arbitrary strain rate dependency. Used in Explicit Nonlinear (SOL
700) only.
MATD025
MATD026 Used to model honeycomb and foam materials with real anisotropic behavior.
Used in Explicit Nonlinear (SOL 700) only.
MATD027 Used to model rubber using two variables. Used in Explicit Nonlinear (SOL 700)
only.
MATD028 A resultant formulation for beam and shell elements including elasto-plastic
behavior can be defined. Used in Explicit Nonlinear (SOL 700) only.
MATD029 Plastic hinge forming at the ends of a beam can be modeled using curve
definitions.
MATD030 This material model describes the superelastic response present in shape-
memory alloys (SMA). Used in Explicit Nonlinear (SOL 700) only.
MATD031 Used to model rubber using the Frazer-Nash formulation. Used in Explicit
Nonlinear (SOL 700) only.
MATD032 Used for Automotive Glass
MATD034 Fabric Material
MATD036 This model was developed by Barlat and Lian (1989) for modeling sheets with
anisotropic materials under plane stress conditions. This material allows the use
of the Lankford parameters for the definition of the anisotropy.
MATD037 This model is for simulating sheet forming processes with anisotropic material.
Only transverse anisotropy can be considered. Optionally an arbitrary
dependency of stress and effective plastic strain can be defined via a load curve.
This plasticity model is fully iterative and is available only for shell elements.
MATD039 This model is for simulating sheet forming processes with anisotropic material.
Only transverse anisotropy can be considered. Optionally, an arbitrary
dependency of stress and effective plastic strain can be defined via a table. A
Forming Limit Diagram (FLD) can be defined using a table and is used to
compute the maximum strain ratio which can be post processed. This plasticity
model is fully iterative and is available only for shell elements.
MATD040 Nonlinear Orthotrropic Material
MATD053 This allows the modeling of low density, closed cell polyurethane foam.
MATD054 This material is an enhanced version of the composite model material type 22.
Arbitrary orthotropic materials, e.g., unidirectional layers in composite shell
structures can be defined. Used in Explicit Nonlinear (SOL 700) only.

Main Index
 1128 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

MATD057 Material used to model highly compressible low density foams. Used in Explicit
Nonlinear (SOL 700) only.
MATD058 Composite and Fabrics
MATD059 Material used to model shells or solid composite structures. Used in Explicit
Nonlinear (SOL 700) only.
MATD062 Used to model viscous foams. It was written to represent the Confor Foam on the
ribs of EuroSID side impact dummy. It is only valid for solid elements, mainly
under compressive loading. Used in Explicit Nonlinear (SOL 700) only.
MATD063 Used to model crushable foams. It is dedicated to modeling crushable foam with
optional damping and tension cutoff. Used in Explicit Nonlinear (SOL 700) only.
MATD064 Used to model strain rate sensitive elasto-plastic material with a power law
hardening. Used in Explicit Nonlinear (SOL 700) only.
MATD066 This material model is defined for simulating the effects of a linear elastic beam
by using six springs each acting about one of the six local degrees-of-freedom.
MATD067 This material model is defined for simulating the effects of nonlinear elastic and
nonlinear viscous beams by using six springs each acting about one of the six
local degrees-of-freedom.
MATD068 This material model is defined for simulating the effects of nonlinear
elastoplastic, linear viscous behavior of beams by using six springs, each acting
about one of the six local degrees-of-freedom.
MATD069 The side impact dummy uses a damper that is not adequately treated by the
nonlinear force versus relative velocity curves since the force characteristics are
dependent on the displacement of the piston.
MATD070 This special purpose element represents a combined hydraulic and gas-filled
damper which has a variable orifice coefficient
MATD071 This model permits elastic cables to be realistically modeled; thus, no force will
develop in compression.
MATD072 This model is used to analyze buried steel reinforced concrete structures
subjected to impulsive loadings.
MATD72R The Karagozian & Case (K&C) Concrete Model - Release III is a three-invariant
model, uses three shear failure surfaces, includes damage and strain-rate effects,
and has origins based on the Pseudo-TENSOR Model (Material Type 16).
MATD073 This material is for Modeling Low Density Urethane Foam with high
compressibility and with rate sensitivity which can be characterized by a
relaxation curve.
MATD074 This model permits elastic springs with damping to be combined and represented
with a discrete beam element type 6.
MATD076 This material model provides a general viscoelastic Maxwell model having up
to 6 terms in the prony series expansion and is useful for modeling dense
continuum rubbers and solid explosives.

Main Index
 Bulk Data Entries 1129
Bulk Data Entry Descriptions

MATD077 Used to model a general hyperelastic rubber model combined optionally with
linear viscoelasticity as outlined by Christensen. Used in Explicit Nonlinear
(SOL 700) only.
MATD77H This material model provides a general hyperelastic rubber model combined
optionally with linear viscoelasticity as outlined by Christensen [1980].
MATD77O This material model provides the Ogden [1984] rubber model combined
optionally with linear viscoelasticity as outlined by Christensen [1980].
MATD078 This model permits concrete and soil to be efficiently modeled.
MATD080 Used to model Ramberg-Osgood plasticity. This model is intended as a simple
model of shear behavior and can be used in seismic analysis. Used in Explicit
Nonlinear (SOL 700) only.
MATD081 Used to model elasto-visco-plastic materials with arbitrary stress versus strain
curves and arbitrary strain rate dependency. Used in Explicit Nonlinear (SOL
700) only.
MATD083 Rate effects can be modeled in low and medium density foams.
MATD087 This material model provides a cellular rubber model with confined air pressure
combined with linear viscoelasticity as outlined by Christensen [1980].
MATD089 An elasto-plastic material with an arbitrary stress versus strain curve and
arbitrary strain rate dependency can be defined.
MATD093 This material model is defined for simulating the effects of nonlinear elastic and
nonlinear viscous beams by using six springs each acting about one of the six
local degrees-of-freedom.
MATD094 This model permits elastoplastic springs with damping to be represented with a
discrete beam element type 6.
MATD095 This material model is defined for simulating the effects of nonlinear inelastic
and nonlinear viscous beams by using six springs each acting about one of the
six local degrees-of-freedom.
MATD097 This model is used to define a general joint constraining any combination of
degrees of freedom between two nodes.
MATD098 The Johnson/Cook strain sensitive plasticity is used for problems where the
strain rates vary over a large range.
MATD099 This model, which is implemented only for shell elements with multiple through
thickness integration points.
MATD100 MATD100 usage is no longer recommended and will be removed from the code
in a future version. Use MATDSW1-5 in combination with PBSPOT.
MATD112 An elasto-plastic material with an arbitrary stress versus strain curve and
arbitrary strain rate dependency can be defined.
MATD114 A layered elastoplastic material with an arbitrary stress versus strain curve and
an arbitrary strain rate dependency can be defined.

Main Index
 1130 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

MATD116 This material is for modeling the elastic responses of composite layups that have
an arbitrary number of layers through the shell thickness.
MATD119 This is a very general spring and damper model. This beam is based on the
MATDS06 material model.
MATD121 This is a very general spring and damper model. This beam is based on the
MATDS06 material model and is a one-dimensional version of MATD119.
MATD123 An elasto-plastic material with an arbitrary stress versus strain curve and
arbitrary strain rate dependency can be defined.
MATD126 The major use of this material model is for aluminum honeycomb crushable
foam materials with anisotropic behavior.
MATD127 Used to model rubber using the Arruda-Boyce formulation. Used in Explicit
Nonlinear (SOL 700) only.
MATD130 This model is available the Belytschko-Tsay and the C0 triangular shell elements
and is based on a resultant stress formulation in SOL 700
MATD145 The model is appropriate for geomaterials including soils, concrete, and rocks.
MATD147 This is an isotropic material with damage and is available for solid elements.
MATD158 Depending on the type of failure surface, this material description may be used
to model rate sensitive composite materials with unidirectional layers, complete
laminates, and woven fabrics.
MATD159 This is a smooth or continuous surface cap model and is available for solid
elements. The user has the option of inputting his own material properties or
requesting default material properties for normal strength concrete.
MATD163 Crushable foam with optional damping, tension cutoff, and strain rate effects.
MATD170 This model is available the Belytschko-Tsay and the C0 triangular shell elements
and is based on a resultant stress formulation in SOL 700.
MATD181 Used to model rubber or foam using a simplified formulation. Used in Explicit
Nonlinear (SOL 700) only.
MATD190 This model was developed by Barlat and Lian [1989] for modeling sheets with
anisotropic materials under plane stress conditions. The material allows the use
of the Lankford parameters for the definition of the anisotropy. It has been
modified to include a failure criterion based on the Forming Limit Diagram. The
curve can be input as a table, or calculated based on the n-value and sheet
thickness.
MATD193 This material enables soil to be modeled effectively.
MATD196 General spring discrete spring material
MATDB01 Defines a seat belt material.
MATDERO Defines failed elements to be removed after failure.

Main Index
 Bulk Data Entries 1131
Bulk Data Entry Descriptions

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.
MATDS01 Defines a translational or rotational elastic spring located between two nodes.
MATDS02 Defines a translational or rotational linear damper located between two nodes.
MATDS03 Defines a translational or rotational elastoplastic spring with isotropic hardening
located between two nodes.
MATDS04 Defines a translational or rotational nonlinear elastic spring with arbitrary force
versus displacement or moment versus rotation, located between two nodes.
MATDS05 Defines a translational or rotational viscous damper with arbitrary force versus
displacement or moment versus rotation, located between two nodes.
MATDS06 Defines a translational or rotational nonlinear spring with arbitrary loading and
unloading definitions, located between two nodes.
MATDS07 Defines a translational or rotational three Parameter Maxwell Viscoelastic spring
located between two nodes.
MATDS08 Defines a translational or rotational inelastic tension or compression only spring
located between two nodes.
MATDS13 Defines a translational spring located between two nodes.
MATDS14 Define a translational spring located between two nodes.
MATDS15 Defines a translational spring located between two nodes.
MATDSW1 - The material model applies to beam element type PBSPOT and to solid element
MATDSW5 type 1 with type 6 hourglass controls. The failure models apply to both beam
and solid elements.
MATM Defines material data for the advanced composite progressive failure model.
MATRIG Defines the properties of a rigid body.
MATTM Specifies temperature dependencies for material properties defined on MATM
entry field via tables.

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.
CROSSEC Defines a cross section for resultant forces written to SECFORC in SOL 700.
DETSPH Defines the ignition point from which a spherical detonation wave travels,
causing the reaction of high explosive materials.

Main Index
 1132 MSC Nastran Quick Reference Guide
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.
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.
SEQROUT At the end of an explicit simulation write out the initial state to a file that can be
used for a subsequent explicit SOL 700 run.

Multi-Variable Parameters (SOL 700)

DYPARAM Bulk Data parameters for with extra fields.

DYPARAM,AXIALSYM Axial symmetric analysis.
DYPARAM,COHESION Cohesion for Coulomb Friction
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,FASTCOUP Defines the fast coupling algorithm.
DYPARAM,HYDROBOD Defines a body force for single hydro material in Euler.
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,LSDYNA,ACCURACY Define control parameters that can improve the accuracy of
the calculation.
DYPARAM,LSDYNA,BINARY Bulk Data parameters for Explicit Nonlinear (SOL 700) only.
DYPARAM,LSDYNA,CONTACT Changes the defaults for computation with contact surfaces.
DYPARAM,LSDYNA,DBEXTENT Specify output files to be written.
DYPARAM,LSDYNA,ENERGY Provide controls for energy dissipation options.
DYPARAM,LSDYNA,HOURGLAS Controls for energy dissipation options.
DYPARAM,LSDYNA,IMPLICIT Options to modify convergence tolerances and
initial/geometric stiffness of prestress (PRESTRS) or
springback (SPRBCK) simulations.
DYPARAM,LSDYNA,OUTPUT Set miscellaneous output parameters.
DYPARAM,LSDYNA,RELAX Define controls for dynamic relaxation.

Main Index
 Bulk Data Entries 1133
Bulk Data Entry Descriptions

DYPARAM,LSDYNA,SHELL Provide controls for energy dissipation options.

DYPARAM,LSDYNA,SOLID Define control parameters that can improve the accuracy of
the calculation.
DYPARAM,LSDYNA,TIMESTEP Set structural time step size control using different options.
DYPARAM,SPHERSYM Enables an efficient and accurate 1D spherical symmetric
solution for Euleran materials.
DYPARAM,VELMAX Defines the maximum velocity in Eulerian meshes.

Output Control (SOL 700)

DBEXSSS Output request for sub system statistics.

DYTIMHS Specifies various types of time history output and form of the output for
SOL 700.

Prescribed Boundary Motion (SOL 700)

SPCD2 Defines an imposed nodal motion (velocity, acceleration, or displacement) on a

node or a set of nodes.

Response Measurement (SOL 700)

ACC ACC usage is no longer recommended and will be removed from the code in a
future version. Use ACCMETR.
ACCMETR Accelerometer
SBSENSR Defines a seat belt sensor.

Restarts (SOL 700)

DYCHANG For a SOL 700 restart analysis, change certain solution options.
DYDELEM Deletes properties or element using a list for SOL 700 restarts.
DYRIGSW Defines materials to be switched from rigid to deformable and deformable to
rigid in a restart.
RESTART Specifies writing or reading of restart data for Nonlinear Analysis when Marc or
Dytran-LsDyna is executed from MSC Nastran.

Main Index
 1134 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

Rigid Elements (SOL 700)

BJOIN Defines (multiple) pairs of grid points of one-dimensional and/or shell elements
to be joined during the analysis.
RBE2A Defines extra nodes for rigid body.
RBE2D Defines a nodal rigid body.
RBE2F Defines nodal constraint sets for translational motion in global coordinates.
RBE2GS Defines an RBE2 connecting the two closest grids to GS.
RBE3D Defines rigid interpolation constraints in the Dytran style. Used in Explicit
Nonlinear (SOL 700) only.
RBJOINT Defines a joint between two rigid bodies.
RCONN Defines a rigid connection between the different parts of Lagrangian meshes
(tied surfaces).
WALL Defines a rigid plane through which specified Lagrangian grid points
cannot penetrate. Used in Explicit Nonlinear (SOL 700) only.
WALLGEO Defines a geometric rigid wall with an analytically described form. Four forms
are possible.

Seat Belts (SOL 700)

CBELT Defines a seat belt element.

PBELTD Defines section properties for the seat belt elements.
PBDISCR Defines properties for 6 DOF discrete beam elements.
SBPRET Defines a seat belt pretensioner.
SBRETR Defines a seat belt retractor.
SBSLPR Defines seat belt slipring.

Smooth Particle Hydrodynamics (SOL 700)

CSPH Defines a SPH particle.

PSPH Defines properties for SPH particles.
SPHDEF Provides controls for computing SPH particles.
SPHSYM Defines a symmetry plane for SPH. This option applies to continuum domains
modeled with SPH particles.

Main Index
 Bulk Data Entries 1135
Bulk Data Entry Descriptions

Switch Rigid/Deformable (SOL 700)

D2RAUTO Defines a set of parts to be switched to rigid or to deformable at some stage in

the calculation.
D2R0000 Defines materials to be switched to rigid at the start of the calculation.

Tables (SOL 700)

TABLEDR Defines a table to reference other tables.

Time Step Control (SOL 700)

DYTERMT Stop a SOL 700 analysis depending on specified displacement conditions.

TIMNAT Defines input data which specifies the natural frequencies selected from
amplitude-frequency plots output from a previous SOL 700 time domain NVH
run.
TIMNVH Defines input data to perform time domain NVH.
TIMSML Defines input data for one of the controls to determine which peaks in the
amplitude vs frequency curves (normally specified by SMALL on the TIMNVH
entry) are available for selection for SOL 700 time domain NVH.
TSTEPNL Defines parametric controls and data for nonlinear transient structural or heat
transfer analysis. TSTEPNL is intended for SOLs 129, 159, 400, 600 and 700.

Welds (SOL 700)

CBUTT Defines a butt weld. Replaces CWELD for SOL 700.

CCRSFIL Defines a cross-fillet weld. Replaces CWELD for SOL 700.
CFILLET Defines a fillet weld. Replaces CWELD for SOL 700.
COMBWLD Defines a complex or combined weld. Replaces CWELD for SOL 700.
CONSPOT A spotweld is defined between segments of the two property ID’s.
CSPOT Defines a complex or combined weld. Replaces CWELD for SOL 700.

Main Index
 1136 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.

Aeroelastic Stability Analysis

FLFACT Used to specify density ratios, Mach numbers, reduced frequencies, and velocities
for flutter analysis.
FLUTTER Defines data needed to perform flutter analysis.
DIVERG Defines Mach numbers (m) for a static aeroelastic divergence analysis.

Main Index
 Bulk Data Entries 1137
Bulk Data Entry Descriptions

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.

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, RVDOF1 Degrees-of-freedom specification for residual vector calculation.

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.
FTGEVNT Groups simultaneously applied loads into loading events for pseudo-static
fatigue analysis using SOL 101 or modal analysis using SOL 103 by referencing
FTGLOAD entries.
FTGLOAD Defines cyclis loading variation for pseudo-static fatigue analysis using SOL
101 or modal analysis using SOL 103.
PFTG Defines fatigue properties.
MATFTG Defines fatigue material properties.
TABLFTG Defines tabular data for specifying fatigue cyclic loading variation.

Main Index
 1138 MSC Nastran Quick Reference Guide
Bulk Data Entry Descriptions

DTI,UNITS Defines units necessary for conversion during the analysis for the
Nastran/ADAMS interface and Nastran fatigue analysis.
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 and 153.
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).

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.
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.

Main Index
 Bulk Data Entries 1139
Bulk Data Entry Descriptions

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.

p-element and p-Adaptivity Analysis

ADAPT Defines controls for p-version adaptive analysis.

PSET Describes polynomial order distribution and is selected by the ADAPT Case Control
command.
PVAL Describes polynomial order distribution and is selected by the ADAPT Bulk Data
entry.

Main Index
 1140 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

BLDOUT Defines bladeout force output information and mapping criteria for a sequential
SOL 700 - SOL 400 Bladeout analysis.
RGYRO Specifies synchronous or asynchronous analysis, reference rotor, and rotation speed of
the reference rotor.
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. TSTEPNL is intended for SOLs 129, 159, and 99.

Main Index
 Entries A - B 1141
Bulk Data Entries

Entries A - B MSC Nastran Quick Reference GuideMSC Nastran Quick Reference Guide
Bulk Data Entries

$ 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
 1142 /
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

Field Contents
/ 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)

Main Index
 / 1143
Control Input Stream

Field Contents
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.
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.

Example:
/DUPMETH=OLD
/DUPTOL=0.1
With the following NASTRAN entry required:
NASTRAN SYSTEM(402)=0.1

Main Index
 1144 /
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
 / 1145
Control Input Stream

5.0, 1.0
6.0, 1.0
/listoff
,endt

Main Index
 1146 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

Field Contents
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)

Main Index
 ABINFL 1147
Inflator Model to be Used With GBAG or COUPLE Entries

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.
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
 1148 ACC
Accelerometer Output

ACC Accelerometer Output

ACC usage is no longer recommended and will be removed from the code in a future version. Use
ACCMETR.
ACC

Main Index
 ACCEL 1149
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

Field Contents
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.

Main Index
 1150 ACCEL
Acceleration Load

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.
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

Main Index
 ACCEL1 1151
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

Field Contents
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 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.

Main Index
 1152 ACCMETR
Accelerometer

ACCMETR Accelerometer

The accelerometer is fixed to a rigid body containing the three nodes defined below. Whenever computed
accelerations are compared to experimental results or whenever computed accelerations are compared
between different runs, accelerometers are essential. Raw nodal accelerations contain considerable
numerical noise and their comparisons are generally meaningless and, therefore, misleading. Used in
SOL 700 only.
ACCMETR

Format:

1 2 3 4 5 6 7 8 9 10
ACCMETR SBACID NID1 NID2 NID3 IGRAV INTOPT

Example:
ACCMETR 12 64 54 53 0 0

Field Contents
SBACID Accelerometer ID. A unique number must be used. (Integer > 0; Required)
NID1 Node 1 ID. (Integer > 0; Required)
NID2 Node 2 ID. (Integer > 0; Required)
NID3 Node 3 ID. (Integer > 0; Required)
IGRAV Gravitational accelerations due to body force loads. (Integer > 0; Default = 0)
-6 Z and X components removed from acceleration output
-5 Y and Z components removed from acceleration output
-4 X and Y components removed from acceleration output
-3 Z component removed from acceleration output
-2 Y component removed from acceleration output
-1 X component removed from acceleration output
0 All components included in acceleration output
1 All components removed from acceleration output
INTOPT Integration option. If the accelerometer undergoes rigid body translation without
rotation this option has no effect; however, if rotation occurs, option 1 may provide
better agreement with the output of the accelerometer. (Integer > 0; Default = 0)

Main Index
 ACCMETR 1153
Accelerometer

Field Contents
0 Velocities are integrated from the global accelerations and transformed
into the local system of the accelerometer
1 Velocities are integrated directly from the local accelerations of the
accelerometer.

Remarks:
1. The presence of the accelerometer means that the accelerations and velocities of node 1 will be
output to all output files in local instead of global coordinates.
The local coordinate system is defined by the three nodes as follows:
• local x from node 1 to node 2,
• local z perpendicular to the plane containing nodes, 1, 2, and 3 (z = x × a), where a is from
node 1 to node 3),
• local y = z × x.
The three nodes should all be part of the same rigid body. The local axis then rotates with the
body.

Main Index
 1154 ACLOAD
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

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)

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.

Main Index
 ACMODL 1155
Fluid-Structure Interface Parameters

ACMODL Fluid-Structure Interface Parameters

Optional entry to define modeling parameters for Fluid-Structure Interface.

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

Field Contents
INTER Type of structure-fluid interface. (Character = “IDENT” or “DIFF”;
Default = “DIFF”)
INFOR For METHOD = “BW” 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. (Integer > 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. (Integer > 0 or blank)
NORMAL Fluid normal tolerance. See Remark 5. (Real; Default = 1.0 (Real; .001 for IDENT)
METHOD Default = “BW”
“BW” = Body in White method
“CP” = Closed Pressure Vessel Method
See Remarks 10. and 11.
SKNEPS Fluid skin growth tolerance. (Real; Default 0.5)

Main Index
 1156 ACMODL
Fluid-Structure Interface Parameters

Field Contents
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.
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.

Main Index
 ACMODL 1157
Fluid-Structure Interface Parameters

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)).
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
ALLSET=NO Delete fluid element faces

Main Index
 1158 ACMODL
Fluid-Structure Interface Parameters

Table of Fluid/Structure Search Control and Override METHOD=BW

ALLSET=YES Add fluid element faces
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 = Value_input * L, Height of box +normal to plane of fluid.
SKNEPS = D * (1.0 + Value_input), Search plane diagonals.
DSKNEPS = D * (1.0 + Value_input) Secondary search plane diagonals
DSKNEPS is only used when SKNEPS < DSKNEPS
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 = Value_input
SKNEPS = As defined above but projected using ABS normal units
DSKNEPS = As defined above but projected using ABS normal units
INTOL = Value_input
ALLSSET NO Designed to take a modified PARAM SKINOUT PUNCH set and
DELETE elements from either the FLUID element set or the
STRUCTURE element set or BOTH. 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 or vice versa. This is
because not all of the UNMODIFIED structure elements of the set
project with the reduced set of Fluid elements or vice versa.

Recommended for DELETE only.

Main Index
 ACMODL 1159
Fluid-Structure Interface Parameters

Table of Fluid/Structure Search Control and Override METHOD=BW

YES Designed to take a modified PARAM SKINOUT PUNCH set and
ADD elements to either the FLUID element set or the STRUCTURE
element set or BOTH. If some previously found FLUID and
STRUCTURE are also deleted the algorithm keeps all the added set
elements but will of course recomputed the interface for the deleted
boundary so that a sensible set intersection is computed.

Recommended for DELETE ADD.

Do NOT use ALLSET =YES when no SETs are specified or one SET
is specified and the search algorithm is being used for the other
unspecified SET as ALLSET means USE ALL and all of the elements
of the unspecified SET may be used.
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
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.

Main Index
 1160 ACMODL
Fluid-Structure Interface Parameters

Table of Fluid/Structure Search Control and Override METHOD=BW

5. Run acoustic analysis with ACMODL using final FSET, SSET sets with
ALLSET=YES if sets contain both deleted and added elements. Or
ALLSET=NO (default) if sets only delete.
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
Structural an element of the closest mesh to the fluid face. All elements connected to this first
Element element are then checked to see if they are in the search box. Once and element, such as
Meshes in the elements of the outer parallel mesh, are found not to connect to the inner patch it is
the Search eliminated from the search. Thus outer patch elements tend to be excluded from the
Box search unless some 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 new “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.

Main Index
 ACPEMCP 1161
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
SCUX SCUY SCUZ SCRX SCRY SCRZ SCFP

Example:

ACPEMCP 1 1002 1004

Field Contents
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. (Integer0 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. (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.
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.
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.
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.
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.

Main Index
 1162 ACPEMCP
Trim Component Interface Coupling and Constraints Definition

Field Contents
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.
SCFP ID of SET1/SET3 with which grid IDs in the trim component TID is zero-
constrained in fluid pressure.

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.

Main Index
 ACSRCE 1163
Acoustic Source Specification

ACSRCE Acoustic Source Specification

Defines acoustic source as a function of power vs. frequency.

1 8πCP ( f ) i ( θ + 2πfτ )
Source Strength = { A } ⋅ --------- ---------------------- e
2πf ρ
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

Field Contents
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.

Main Index
 1164 ACSRCE
Acoustic Source Specification

2. For additional remarks, see the RLOAD1 entry description.

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.

Main Index
 ACTIVAT 1165
Defines Elements That Were Previously Deactivated and Should Be Reactivated for a Particular

ACTIVAT Defines Elements That Were Previously Deactivated and Should Be

Reactivated for a Particular Subcase in SOL 600

This entry allows the user to re-activate certain elements that were previously deactivated in a previous
subcase in SOL 600.

Format:

1 2 3 4 5 6 7 8 9 10
ACTIVAT ID IGEOM ISET

Example:
ACTIVAT 3 0 300

Field Contents
ID Identification number of a matching Case Control ACTIVAT command defining the
subcase to which these elements should be activated. (Integer; no Default)
IGEOM Flag to control whether to update the geometry on the post file. (Integer; Default = 0)
0 Update the geometry.
1 Do not update the geometry.
ISET ID of a list of elements described by SET3 is ID=ISET to be activated. (Integer; no
Default)

Remark:
1. This entry maps to Marc's ACTIVATE History definition option.

Main Index
 1166 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
 ADAPT 1167
Version Adaptivity Control

ADAPT Version Adaptivity Control

Defines controls for p-version adaptive analysis.

Format:

1 2 3 4 5 6 7 8 9 10
ADAPT SID ADGEN MAXITER PSTRTID PMINID PMAXID
PART=name1, option1=value1, option2=value2, etc., PART=name2
option1=value1, option2=value2, etc., PART=name3, etc.

Example:

ADAPT 127 3 23 45
PART=LOWSTR, ELSET=11, TYPE=UNIP, SIGTOL=22
PART=HISTR, ELSET=111, ERREST=2, EPSTOL=.002

Field Contents Type Default

SID Adapt entry ID selected in Case Control by Integer > 0 None
ADAPT command.
ADGEN ID of the first PVAL entry generated in the Integer > 1000
adaptive process. See Remark 14. PSTRTID,
PMINID,
PMAXID
MAXITER Number of analyses performed before Integer > 0 3
adaptive process is stopped.
PSTRTID ID of PVAL entry describing the starting Integer > 0 None
p-order distribution.
PMINID ID of PVAL entry describing the minimum Integer > 0 PSTRTID
p-order distribution. See Remark 10.
PMAXID ID of PVAL entry describing the maximum Integer > 0 PSTRTID
p-order distribution. See Remark 10.
optioni = Assigns a value to an option described later.
valuei See Remark 16.
PART Part name of the elements defined in ELSET Character PART = MODEL
and controlled by TYPE, ERREST, ERRTOL,
SIGTOL, and EPSTOL.
ELSET ID of the SET command under the SETS Integer > 0 ELSET = 999999
DEFINITION command. See Remark 7.

Main Index
 1168 ADAPT
Version Adaptivity Control

Field Contents Type Default

TYPE p-order adjustment. See Remark 3. Character or TYPE = EBEP
Integer > 0
ERREST Error estimator activation flag. See Remark 2. Integer > 0 ERREST = 1
ERRTOL Error tolerance. Required if MAXITER is not 0.0<Real<1. ERRTOL=0.01
specified. 0
SIGTOL Stress tolerance. If the von Mises stress at the Real > 0.0 SIGTOL = 0.0
center of the element is below this value, the
element will not participate in the error
analysis.
EPSTOL Strain tolerance. If the von Mises strain at the Real > 0.0 EPSTOL = 1.0E-8
center of the element is below this value, the
element will not participate in the error
analysis.

Remarks:
1. Only one ADAPT entry may be specified. On the continuation entries, no commas can appear in
columns 1 through 8 and the data in fields 2 through 9 must be specified in columns 9 through 72.
2. The error estimator is activated by ERREST = 1 and is based on strain energy density sensitivity
and stress discontinuity in neighboring elements. ERREST = 0 means no error estimation will be
performed on the PART.
3. The types of p-order adjustment are:

Type Description
EBEP The p-order will increase only in the elements that are required by the
error analysis.
UNIP If any element in the group has an error larger than the tolerance, all
elements will be increased by one order in each direction.
NOCH The p-order of the group does not change during the iterations.
LIST The PVAL distribution specified as PSTRTID is used for the first
iteration. The user is required to provide PVAL entries with IDs starting
with ADGEN, and these p-distributions will be used in the following
iterations

4. If a PVAL ID is not specified for PSTRTID, PMINID, or PMAXID, then this is equivalent to no
change at the last PVAL ID found for the element.
5. The elements specified in the SET could overlap. In this case, the highest p 1 , highest p 2 , highest
p 3 (the polynomial order of the elements in three directions) determined by the error estimator
will be used.

Main Index
 ADAPT 1169
Version Adaptivity Control

6. n restart, PMINID and PMAXID must not refer to any PVAL identification number that was
generated in the previous run(s). Also, PARAM,PVALINIT must specify the desired PVAL
identification number from which to restart.
7. If an element in the SET does not have a PVAL for PSTRTID or PMINID or PMAXID, it will be
excluded from the adaptivity process.
8. SET = 999999 is a reserved set that includes all elements.
9. The user can specify as many PARTs as needed.
10. Each finite element has to have a unique PVAL for PSTRTID, PMINID, PMAXID. Any overlap
of the PVAL specification will result in a warning message and the use of the PVAL with the
highest pi field (highest p 2 if same p 1 and highest p 3 if same p 1 and p 2 ) and the lowest CID value.
11. The p-distribution for an element specified by the PVAL entry referenced by PMAXID must be
larger than the distribution specified by the PSTRTID, which must be larger than the distribution
specified by the PMINID. A warning message will be issued if these conditions are not met, and
the data is reset.
12. The solution vector of all the elements listed in the SET entries for all loads and boundary
conditions will be used in the error estimation. New p values are generated for all the elements.
13. When ERREST = 0, no error analysis is performed. The p-value of the elements in the set are
increased uniformly starting from p-values specified on the PVAL entry referenced by PSTRTID
up to values specified on the PVAL entry referenced by PMAXID.
14. The intermediate PVAL entries generated will have an ID starting with ADGEN; thus, ADGEN
must be larger than PSTRTID, PMINID, and PMAXID.
15. The displacement and stress output can be requested by a DATAREC Case Control command.
16. Each optioni = valuei must be specified on the same entry. In other words, optioni and valuei may
not be specified on two separate continuation entries.

Main Index
 1170 ADUMi
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

Field Contents
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
 AECOMP 1171
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

Field Contents
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
 1172 AECOMPL
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

Field Contents
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
 AEDW 1173
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

Field Contents
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
 1174 AEFACT
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

Field Contents
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
 AEFORCE 1175
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

Field Contents
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.

Main Index
 1176 AEGRID
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

Field Contents
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
 AELINK 1177
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
ui = 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

Field Contents
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
 1178 AELIST
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

Field Contents
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
 AELISTC 1179
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

Field Contents
SID Set identification number. (Integer > 0)
Ci List of 8-character strings.

Remark:
1. Intervening blank fields are not allowed.

Main Index
 1180 AEPARM
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

Field Contents
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
 AEPRESS 1181
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

Field Contents
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
 1182 AEQUAD4
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

Field Contents
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
 AERO 1183
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

Field Contents
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
 1184 AEROS
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

Field Contents
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
 AESCALE 1185
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

Field Contents
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
 1186 AESTAT
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

Field Contents
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 8-1 Standard Labels Defining Rigid Body Motions

Degree-of-Freedom
LABEL Motion Description
ANGLEA u r (R2) Angle of Attack
SIDES u r (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
 AESTAT 1187
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 (as it will with
AESTAT). 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
 1188 AESURF
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

Field Contents
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,HMULIM Lower and upper hinge moment limits for the control surface in force-length
units. (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
 AESURF 1189
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
 1190 AESURFS
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

Field Contents
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
 AETRIA3 1191
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

Field Contents
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
 1192 AIRBAG
Defines an Airbag

AIRBAG Defines an Airbag

Defines an airbag. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
AIRBAG AID BID REVERSE

“CFD” EOSID SWITCH DENS DXEL DYEL DZEL

RESIZE TID-X TID-Y TID-Z XREF YREF ZREF
XOBX YOBX ZOBY DXBX DYBX DZBX
“ENVIRONM” PENV TENV GAMMENV RENV CPENV CVENV
“INITIAL” PINIT TINIT GAMMINIT RINIT CPINIT CVINIT
GASIID1 FRAC1
GASIID2 FRAC2
GASIIDi FRACi
“INFLATOR” BFID MFTID TEMPC TEMPTID FRACID COEFF COEFID
GASFD1, RINF CPINF CVINF
GAMMINF
GASFD2
GASFDi
“SMALHOLE” BSHID ASHID FLOW COEFF COEFID
“LARGHOLE” BLHID ALHID FLOW COEFF COEFID
“PERMEAB” BPID APID FLOW PERM PERMTID COEFF COEFID
“CONVECT” BCID HTRCF HTRTID COEFF COEFID
“RADIATE” BRID EMISS EMISTID COEFF COEFID
“GAS” GASID
R MILWT CPTYPE CP1 CP2 CP3 CP4

Main Index
 AIRBAG 1193
Defines an Airbag

Example:
AIRBAG 1 25 1
CFD 3 1.527 0.009 0.009 0.009
INITIAL 101325 293.0 1.4 294.0
INFLATOR 1001 1 350 0.7
1.557 243.
LARGHOLE 301 2 1.0
LARGHOLE 302 3 1.0
LARGHOLE 303 4 1.0
LARGHOLE 304 5 1.0
LARGHOLE 305 6 1.0

Field Contents
AID Airbag identification number. (Integer; no Default; Required)
BID Identification number of a BSURF, BCPROP, BCMATL, BSURF, BCPROP or
BCSEG can only reference shell elements. The collection of shell elements
referenced must form a closed surface. (Integer; no Default; Required)
REVERSE Auto-reverse switch for the airbag surface segments: Recommendation is to use
ON. (Character. Default = ON)
ON Normal of all faces of the surface is checked and reversed if
necessary.
OFF Normal of all faces of the surface is not checked.
“CFD” Entries for this continuation line describe the properties of the Eulerian domain.
Only one “CFD” section can be defined. If this section is not defined, the uniform
pressure method is used (GBAG).
EOSID EOSGAM ID. Used to define the gas properties of the gas inside the air bag
(Integer; no Default; Required)
SWITCH Time to switch from CFD method to Uniform Pressure method. If zero, the
Uniform Pressure method is active the entire simulation. (Real; Default = 1.0E20)
DENS Reference density of the gas inside the air bag. The reference density must be the
same for all AIRBAGs that are defined in one simulation. (Real; no Default;
Required).
DXEL, DYEL, Initial size of the Euler Elements of the CFD domain in X, Y and Z-direction
DZEL respectively. (Real; DXEL=Required; Default: DYEL=DXEL, DYEL=DXEL)
RESIZE Option to change the Euler element size during the simulation (Character; Default
= NONE):
NONE No resizing of Euler mesh
SCALE The mesh is resized by a scale factor as a function of time

Main Index
 1194 AIRBAG
Defines an Airbag

Field Contents
LENGTH The mesh is resized by specifying the length as a function of time
TID-X, TID-Y, TABLED1 ID with resize information for X, Y and Z-direction respectively. Table
TID-Z must be a step function. See RESIZE for contents of table. (Integer; Required if
RESIZE is SCALE or LENGTH)
XREF, YREF, Provides control over location of the CFD domain. Used to avoid exact overlap of
ZREF the air bag surface with the Eulerian mesh. (Real; Default = 1.0E-6)
X0BX,Y0BX,Z0B Definition of an auxiliary box for output purposes. By defining an auxiliary box,
X,DXBX,DYBX, all elements that are within the box for one of the cycles requested are stored in
DZBX the archive. This allows multiple cycles in one Euler archive. This box should be
sufficiently large such that it contains all elements. The fields X0BX, Y0BX and
Z0BX specify the start point and DXBX, DYBX and DZBX specify the width of
box. If the there are elements outside the box the run is terminated and a larger box
needs to be specified. (Real; Blank)
“ENVIRONM” Entries for this continuation line describe the properties of the environmental
conditions for the airbag. Only one “ENVIRONM” section can be defined. If not
defined, the values for “INITIAL” will be used.
PENV Pressure of the environment (Real; Default = PINIT)
TENV Temperature of the environment (Real; Default = TINIT)
GAMMENV Gamma gas constant of the environment. Define only 2 of 4 gas constants. The 2
remaining values will be calculated. (Real; Default = GAMMINIT)
RENV R gas constant of the environment. Define only 2 of 4 gas constants. The 2
remaining values will be calculated. (Real; Default = RINIT)
CPENV Cp gas heat constant of the environment. Define only 2 of 4 gas constants. The 2
remaining values will be calculated. (Real; Default = CPINIT)
CVENV Cv gas heat constant of the environment. Define only 2 of 4 gas constants. The 2
remaining values will be calculated. (Real; Default = CVINIT)
“INITIAL” Entries for this continuation line describe the properties of the environmental
conditions for the airbag. Only one “INITIAL” section can be defined and is
required.
PINIT Initial pressure of the gas inside the air bag. (Real; Default = Required)
TINIT Initial Temperature of the gas inside the air bag. (Real; Default = Required)
GAMMINIT Initial Gamma gas constant of the gas inside the air bag. Define only 2 of 4 gas
constants. The 2 remaining values will be calculated. (Real; Default = Required)
RINIT Initial R gas constant of the gas inside the air bag. Define only 2 of 4 gas constants.
The 2 remaining values will be calculated. (Real; no Default; Required)
CPINIT Initial Cp gas heat constant of the gas inside the air bag. Define only 2 of 4 gas
constants. The 2 remaining values will be calculated (Real; no Default; Required)

Main Index
 AIRBAG 1195
Defines an Airbag

Field Contents
CVINIT Initial Cv gas heat constant of the gas inside the air bag. Define only 2 of 4 gas
constants. The 2 remaining values will be calculated (Real; no Default; Required)
GASIIDi GAS identification number. Alternative way to specify the consistency of the
initial gas inside the bag. (Integer; Default = blank)
FRACi Initial fraction of gas GASIDi inside the air bag. The sum of the material fractions
must be 1.0, or else they will be scaled to meet this criterion. (Real; Default = 0.0)
“INFLATOR” Entries for this continuation line describe the properties of an inflator that is
attached to the air bag. More than 1 inflator may be defined.
BFID Identification number of a BSURF, BCPROP, BCMATL or BCSEG entry. It can
only reference shell elements that belong to the airbag surface, as defined by
BSID. (Integer; no Default; Required)
MFTID TABLED1 ID which defines the mass flow rate. (Integer; no Default; Required)
TEMPC, Constant or tabular temperature of inflowing gas. One must be defined. (Real; no
TEMPTID Default)
FRACID ID of INFLFRC which is used to define the fractions of all gases of the inflator as
a function of time. (Integer; Default = blank.)
COEFF, Constant or table id for tabular scale factor of available inflow area. COEFF or
COEFTID COEFTID must be defined. (Real, or Integer)
GASIDi, Gamma gas constant of the inflator gas when real value. When gamma is
GAMMINF specified, define 1 of the other 3 remaining values, RINF, CVINF or CPINF. The
2 remaining values will be calculated.
When an integer is specified, this is the GAS identification number. When using
this option, FRACID must be defined. More GASIDs may follow on the
continuation lines. Also RINF, CPINF and CVINF will be ignored.
GASIDi and GAMMINF are mutually exclusive and can not be used together for
the same inflator definition. (Real or Integer; no Default; Required)
RINF R gas constant of the inflator gas. Define only 2 of 4 gas constants. The 2
remaining values will be calculated. (Real; no Default; Required)
CPINF Cp gas heat constant of the inflator gas. Define only 2 of 4 gas constants. The 2
remaining values will be calculated. (Real; no Default; Required)
CVINF Cv gas heat constant of the inflator gas. Define only 2 of 4 gas constants. The 2
remaining values will be calculated. (Real; no Default; Required)
“SMALHOLE” Entries for this continuation line describe the properties of a small hole in the air
bag. More than 1 SMALHOLE may be defined. A small hole should be used when
the size of the hole is of the same order as the size of the elements of the Euler
mesh.

Main Index
 1196 AIRBAG
Defines an Airbag

Field Contents
BSHID Identification number of a BSURF, BCPROP, BCMATL or BCSEG entry. It can
only reference shell elements that belong to the airbag surface, as defined by
BSID. If blank or zero, the whole air bag surface will be considered. (Integer;
Default = 0.)
ASHID Identification number of another AIRBAG into which the gas flows. If not defined
or zero, the gas will flow into the environment. (Integer; Default = 0)
FLOW Allowed direction of flow (Character; Default = BOTH)
BOTH Gas may flow in both directions and is determined by the difference of the
pressure inside and outside the bag.
IN Only inflow of gas is allowed.
OUT Only outflow of gas is allowed.
COEFF, Constant or table id for tabular scale factor of available hole area. Either COEFF
COEFTID or COEFTID must be defined. (Real; or Integer)
“LARGHOLE” Entries for this continuation line describe the properties of a large hole in the air
bag. More than 1 LARGHOLE may be defined. A large hole should be used when
the size of the hole is of the larger than the size of the elements of the Euler mesh.
BLHID Identification number of a BSURF, BCPROP, BCMATL or BCSEG entry. It can
only reference shell elements that belong to the airbag surface, as defined by
BSID. If blank or zero, the whole air bag surface will be considered. (Integer;
Default = 0.)
ALHID Identification number of another AIRBAG into which the gas flows. If not defined
or zero, the gas will flow into the environment. (Integer; Default = 0)
FLOW Allowed direction of flow (Character; Default = BOTH)
BOTH Gas may flow in both directions and is determined by the difference of the
pressure inside and outside the bag.
IN Only inflow of gas is allowed.
OUT Only outflow of gas is allowed.
COEFF, Constant or table id for tabular scale factor of available hole area. Either COEFF
COEFTID or COEFTID must be defined. (Real; or Integer)
“PERMEAB” Entries for this continuation line describe the properties of the permeability of the
air bag fabric. More than 1 PERMEAB may be defined.
BPID Identification number of a BSURF, BCPROP, BCMATL or BCSEG entry. It can
only reference shell elements that belong to the airbag surface, as defined by
BSID. If blank or zero, the whole air bag surface will be considered. (Integer;
Default = 0.)
APID Identification number of another AIRBAG into which the gas flows. If not defined
or zero, the gas will flow into the environment. (Integer; Default = 0)
FLOW Allowed direction of flow (Character; Default = BOTH)

Main Index
 AIRBAG 1197
Defines an Airbag

Field Contents
BOTH Gas may flow in both directions and is determined by the difference of the
pressure inside and outside the bag.
IN Only inflow of gas is allowed.
OUT Only outflow of gas is allowed.
PERM, Constant or table id for tabular permeability. Either PERM or PERMTID must be
PERMTID defined. (Real or Integer; no Default)
COEFF, Constant or table id for tabular scale factor of available permeable area. Either
COEFTID COEFF or COEFTID must be defined. (Real or Integer)
“CONVECT” Entries for this continuation line describe the properties of the loss of energy of the
gas in the air bag by means of convection through the air bag surface. More than
1 CONVECT may be defined.
BCID Identification number of a BSURF, BCPROP, BCMATL or BCSEG entry. It can
only reference shell elements that belong to the airbag surface, as defined by
BSID. If blank or zero, the whole air bag surface will be considered. (Integer;
Default = 0.)
HTRCF, HTRTID Constant or table id for tabular convection heat transfer coefficient. Either HTRCF
or HTRTID must be defined. (Real or Integer)
COEFF, Constant or table id for tabular scale factor of available hole area. Either COEFF
COEFTID or COEFTID must be defined. (Real or Integer)
“RADIATE” Entries for this continuation line describe the properties of the loss of energy of the
gas in the air bag by means of radiation through the air bag surface. More than 1
RADIATE may be defined. When this option is used, the Stephan-Boltzmann
constant must be defined by PARAM, SZ.
BRID Identification number of a BSURF, BCPROP, BCMATL or BCSEG entry. It can
only reference shell elements that belong to the airbag surface, as defined by
BSID. If blank or zero, the whole air bag surface will be considered. (Integer;
Default = 0.)
EMISS, EMISTID Constant or table id for tabular emissivity coefficient. Either EMISS or EMISTID
must be defined. (Real or Integer)
COEFF, Constant or table id for tabular scale factor of available hole area. Either COEFF
COEFTID or COEFTID must be defined. (Real or Integer)
“GAS” Entries for this continuation line describe the properties of gases. More than 1
GAS may be defined and the gases defined in one AIRBAG entry can be
referenced by other AIRBAG entries.
GASID ID of the gas. Must be unique including gas definitions in other AIRBAG
definitions. (Integer; no Default; Required.)
R, MOLWT Either specify the specific gas constant (R), or the molecular weight (MOLWT).
If MOLWT is given, the universal gas constant must be defined with PARAM,
UGASC. (Real; no Default)

Main Index
 1198 AIRBAG
Defines an Airbag

Field Contents
CPTYPE Type of the definition of Cp. (Character)
CONSTAN CP1 is gas constant cp and is independent of the temperature.
T (Real.)
TABLED CP1 is TABLED1 ID. Cp is a function of temperature in tabular
format. (Integer)
POLY CP1, CP2, CP3, CP4 are polynomial values. Cp is a function of the
temperature described by a polynomial function: (Real)

c p ( T ) = CP1 + CP2 ⋅ T + CP3 ⋅ T + CP4

2
-----------
2
T

Remarks:
1. When the molar weight is given, the universal gas constant Runi must be specified using
PARAM, UGASC, so that: R spec = R uni ⁄ MILWT
2. The specific heat constant at constant volume cv is calculated from the specific heat constant at
constant pressure cp, the universal gas constant and the molecular weight according to:
c v = c p ( T ) – R spec

3. The ratio of specific heats is given as: γ = c p ⁄ c v and: R = c p – c v

Main Index
 ALIASM 1199
Alias Element Formulation in SOL 600

ALIASM Alias Element Formulation in SOL 600

Allows selected elements which normally use a default formulation to be aliased to a different
formulation in SOL 600.

Format:

1 2 3 4 5 6 7 8 9 10
ALIASM TYPE ID1 THRU ID2 BY ID

Example:

ALIASM 139 101 THRU 300 BY 2

138 501 THRU 600

Field Contents
ITYPE Desired element formulation type. (Integer; no Default.) See Marc Vol B for a list
of element types in the example, type 139 is a bilinear 3-node thin shell. ITYPE = -
1 means to use the companion reduced integration element formulation (if it exists)
default full integration formulation. (See Note 4)
ID1 Starting element number to be aliased. (Integer; no Default)
THRU Enter “THRU” if a range of elements is to be specified. (Character; no Default)
ID2 Ending element number to be aliased. (Integer; no Default)
BY Enter “BY” if the range of elements is not to be incremented by one.
ID3 Element “increment by” value. (Integer; Default = 1; must be positive)

Remarks:
1. This entry should only be used if the Marc GEOMETRY entries are identical for the original and
new element types.
2. This entry may be repeated as often as desired to identify all elements requiring aliases.
3. ITYPE and ID1 are required fields. All other data fields may be blank.
4. This entry may not be combined with parameters MRALIAS, MALIAS02, MALIAS03, etc.
5. If all elements of a particular type should have alias values, it may be easier to use parameters
MRALIAS, MALIAS02, MALIAS03, etc. than this entry.

Main Index
 1200 ALIASM
Alias Element Formulation in SOL 600

6. For ITYPE = -1, the following reduced integration element types will be used:

Original Reduced
Type Integration Type Description
26 53 Plane stress 8-node quad
27 54 Plane strain 8-node quad
28 55 Axisymmetric 8-node quad
29 56 Generalized plane strain 8+2 node quad
21 57 20-node brick
32 58 Plane strain Herrmann quad
33 59 Axisymmetric Herrmann 8-node quad
34 60 Plane strain Herrmann 8+2 node quad
35 61 Herrmann 20-node brick
62 73 Axisymmetric 8-node quad, arbitrary
63 74 Axisymmetric Herrman 8-node quad
3 114 Plane stress quad
11 115 Plane strain quad
10, 20 116 Axisymmetric ring (quad)
7 117 8-node brick
80 118 Plane strain incompressible quad
82, 83 119 Axisymmetric incompressible ring
84 120 8-node incompressible brick
75 140 4-node quad

Main Index
 ASET 1201
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

Field Contents
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, 1069 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.

Main Index
 1202 ASET1
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

Field Contents
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, 1069 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.

Main Index
 AXIC 1203
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

Field Contents
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
 1204 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) (p. 141) in
the MSC Nastran Reference Manual.

Main Index
 AXIF 1205
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

Field Contents
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
 1206 AXIF
Fluid Related Axisymmetric Parameters

Field Contents
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 1207
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

Field Contents
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
 1208 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

Field Contents
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)
(p. 58) in the MSC Nastran Reference Manual.
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.

Main Index
 BAROR 1209
CBAR Entry Default Values

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:

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
 1210 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

Field Contents
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.

Main Index
 BARRIER 1211
Barrier for Eulerian Transport

6. DIR is optional. It will only be used when BCID is blank. When DIR is used XMIN, XMAX,
YMIN etc. are ignored.
7. 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.
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.

Main Index
 1212 BCBDPRP
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

Field Contents
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 8-2 (Character).
VALi Value of a parameter. See Table 8-2 (Real or Integer).

Table 8-2 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 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.
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.

Main Index
 BCBDPRP 1213
Contact Body Parameters in SOLs 101 and 400

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)
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)
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.

Main Index
 1214 BCBDPRP
Contact Body Parameters in SOLs 101 and 400

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.
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 SPLINE option. (Integer; Default = 0)
=0 or blank, SPLINE option is turned off
>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.

Main Index
 BCBDPRP 1215
Contact Body Parameters in SOLs 101 and 400

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”).
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.)
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 SPLINE 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.

Main Index
 1216 BCBDPRP
Contact Body Parameters in SOLs 101 and 400

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:
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 )

Main Index
 BCBDPRP 1217
Contact Body Parameters in SOLs 101 and 400

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).
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
 1218 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
400 and SOL 600. The BCBMRAD entry is only used for node-to-segment beam-to-beam contact.
Segment-to-segment beam contact is not available in the current release.

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

Field Contents
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

Main Index
 BCBMRAD 1219
Modify Equivalent Radius for Beam-to-Beam Contact

• ID1 ID2 ID3 ID4 ...

• ID1 THRU ID2
• 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 ⋅ ---
 pi A 

7. SOL 600 does not support the TYPE=ALL option.

8. This is only used for node-to-segment contact.

Main Index
 1220 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 MIDNOD
“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 CHEAT 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)

Main Index
 BCBODY 1221
Flexible or Rigid Contact Body in 2D and 3D

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]
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

Main Index
 1222 BCBODY
Flexible or Rigid Contact Body in 2D and 3D

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

Field Contents

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 or BCGRID 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”).
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)
IDSPL Controls SPLINE option. (Integer; Default = 0)
=0 or blank, SPLINE option is turned off
>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 1223
Flexible or Rigid Contact Body in 2D and 3D

Field Contents

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) For
SOL 600, SANGLE values on the BCBODY entry can be overridden using the
SANGLE Bulk Data entry. This allows SANGLE to change for different subcases.
It also allows analytical contact for this body to be “on” or “off” for different
subcases (see the SANGLE Bulk Data entry). (SOL 400 only) [Marc Spline option
(3,4)]
COPTB Flag to indicate how body surfaces may contact. See Remark 20. on the BCTABLE
entry. (Integer; Default = 0)

Main Index
 1224 BCBODY
Flexible or Rigid Contact Body in 2D and 3D

Field Contents

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.
CGID Grid point identification number defining the initial position of the reference point
(5,i) i=1,2,3 of 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
(9,1)/(10,1) 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.

Main Index
 BCBODY 1225
Flexible or Rigid Contact Body in 2D and 3D

Field Contents

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.
CHEAT 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
(9,4)/(10,4) 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.
HCV Convection coefficient for near field behavior (Real or Integer; Default = 0.0). If
(9,5)/(10,5) 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 =
(9,6)/(10,6) 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.
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.

Main Index
 1226 BCBODY
Flexible or Rigid Contact Body in 2D and 3D

Field Contents

EMISS Emissivity for radiation to the environment or near thermal radiation (Real or
(9,8)/(10,8) 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.
HBL Separation distance dependent thermal convection coefficient (Real or Integer;
(7,6)/(8,6) Default = 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.

Main Index
 BCBODY 1227
Flexible or Rigid Contact Body in 2D and 3D

Field Contents

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.
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

Main Index
 1228 BCBODY
Flexible or Rigid Contact Body in 2D and 3D

Field Contents

G1, G2, G3, G4 Grid numbers for each of the NPTU control points
X1, Y1, X2, Alternate method to define control points without using GRID points. There must
Y2, etc. be abs(NPTU)*NPTV (x,y,z) entries.
Homo1, Homogeneous coordinates (0.0 to 1.0) (Real). There must be NPTU entries.
Homo2,
Homo3, etc.
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, etc. Grid point IDs defining control points (Integer > 0). There must be NPTU*NPTV
entries.
X1, Y1, Z1, X2, Alternate method to define control points without using GRID points. There must
Y2, Z2, etc. be 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)

Main Index
 BCBODY 1229
Flexible or Rigid Contact Body in 2D and 3D

Field Contents

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)

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. For 3D patches, if all need to be reversed, the parameter
PARAM,MARCREVR,1 may be entered to automatically reverse all 3D patches.
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.

Main Index
 1230 BCBODY
Flexible or Rigid Contact Body in 2D and 3D

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.
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 = CHEAT ⋅ ( 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 CHEAT 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 ⋅ ( TA – TB ) +
4 4
σ ⋅ EMISS ⋅ ( TA – TB ) +
dist dist
CHEAT ⋅  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.

Main Index
 BCBODY 1231
Flexible or Rigid Contact Body in 2D and 3D

11. 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 )

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
 1232 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

BCBODY Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Defines a flexible or rigid contact body in 2D or 3D used in SOL 600 only.

Important Notes for SOL 600:

1. The 2nd line is required if any of the subsequent lines are to be entered (if this line is blank, enter
a “+” in column 1 or Nastran will ignore the entire line).
2. PARAM,MRCONVER,11 is required if CTYPE, APPROV, or GROW headers are entered.
3. PARAM,MRCONTAB,11 is required if any of the variables are described by tables.
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:

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 USER

“CTYPE” ISMALL ITYPE IAUG PENALT AUGDIST

“RIGID” CGID NENT --- Rigid Body Name ---

“APPROV” A N1 N2 N3 V1 V2 V3
“RTEMP” G(temp) Tempr T(Tempr)

“SINK” G(sink) Tsink T(Tsink)

“GROW” GF1 GF2 GF3 TAB-GF1 TAB-GF2 TAB-GF3

“HEAT” CFILM TSINK CHEAT TBODY HCV HNC ITYPE

BNC EMISS HBL

“PATCH3D” NPATCH

IDP G1 G2 G3 G4

IDP G1 G2 G3 G4

Main Index
 BCBODY 1233
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

etc. (npatch
entries)
“BEZIER” NP1 NP2 NSUB1 NSUB2

G1 G2 G3 G4 etc (np1*np2
values)
“POLY” NP1 NP2

G1 G2 G3 G4 etc (np1*np2
values)
“CYLIND” NSUB

Gtop Rtop Gbottom Rbottom

“SPHERE” NSUB

Gcenter Radius

“LINE” NPTS Ix Iy Rx Ry (2D Contact)

G1 G2 G3 G4 etc. (npts values)

“ARC” NPTS MethArc Ix Iy Rx Ry (2D Contact)

G1 G2 G3 G4 etc. (npts values)

“SPLINE” NPTS Ix Iy Rx Ry (2D Contact)

G1 G2 G3 G4 etc. (npts values)

“NURBS2D” NPTU NORU NSUB Rx Ry (2D Contact)

G1 or X1 G2 or Y1 G3 G4 or X2 G5 or Y2 G6 [abs(nptu) See Remark

grids or x, 8
y,z, values]
Homo1 Homo2 Homo3 Homo4 etc. (nptu values)

Knot1 Knot2 Knot3 Knot4 Knot5 etc. (nptu+noru

values)
“NURBS2” IDN

“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)*n See Remark
ptv values] 8
Homo1 Homo2 Homo3 Homo4 Homo5 Homo6 Homo7

Homo8 Homo9 etc. (nptu*nptv

vales)
Knot1 Knot2 Knot3 Knot4 Knot5 Knot6 Knot7 `

Knot8 Knot9 etc. (nptu+noru+

ntpv+norv
values)
IDtrim NPTUtrim NORUtrim NSUBtrim (repeat this
and all
following
lines NTRIM
times)
Xisoparam Yisoparam (NPTUtrim
entries)

Main Index
 1234 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Homo1 Homo2 Homo3 etc (NPTUtrim

entries)
Knot1 Knot2 Knot3 etc. (NPTUtrim
+ NORUtrim
entries)

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 5 for rigid bodies)

BCBODY 2 RIGID 0

PATCH3D 1
1 101 102 103 104

Example 3-- Same as Example 2 except that a user subroutine named motion.f will be
employed to specify the rigid body motion.

BCBODY 2 RIGID 0

ADVANCE M
PATCH3D 1
1 101 102 103 104

Field Contents

BID Contact body identification number referenced by BCTABLE, BCHANGE, or

(4,1) BCMOVE. (Integer > 0; Required)
DIM Dimension of body. (Character; Default = 3D)
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) DEFORM body
(4,8) is deformable, RIGID body is rigid, SYMM body is a symmetry body, ACOUS
indicates an acoustic body, WORK indicates body is a workpiece, HEAT
indicates body is a heat-rigid body. See Remark 3. for Rigid Bodies..
BSID Identification number of a BSURF, BCBOX, BCPROP or BCMATL entry if
BEHAV=DEFORM. (Integer > 0)

Main Index
 BCBODY 1235
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

ISTYP Check of contact conditions. (Integer > 0; Default = 0)

(4,3) ISTYP is not supported in segment-to-segment contact.
For a deformable body:
=0 symmetric penetration, double sided contact.
=1 unsymmetric penetration, single sided contact. (Integer > 0)
=2 double-sided contact with automatic optimization of contact constraint
equations (this option is known as “optimized contact”).
Notes: single-sided contact (ISTYP=1) with the contact bodies arranged
properly using the contact table frequently runs much faster than ISTYP=2.
For a rigid body:
=0 no symmetry condition on rigid body.
=1 rigid body is a symmetry plane.
FRIC Friction coefficient. (Real > 0 or integer; Default = 0)
(6,7) If the value is an integer it represents the ID of a TABL3Di.
IDSPL Set IDSPL=1 to activate the SPLINE (analytical contact) option for a
(4,5) deformable body and for a rigid contact surface. Set it to zero or leave blank to
not have analytical contact. (Integer; Default = 0)
SOL 600 Options:
=0 or blank, SPLINE option is turned off.
=1, The body is smoothed out with splines (2D) or Coons surfaces (3D). If
SANGLE is not entered, the default 60.0 degrees is used. IDSPL=1 triggers the
Marc SPLINE option with the 3rd field of the 3rd datablock set to 1. If
analytical contact changes between increment zero and any subcase, the
SANGLE Bulk Data entry is required (see the following SANGLE). SANGLE
is placed in the 4th field of the 3rd Mac SPLINE datablock and a value of 1 is
placed in the 3rd field of the 3rd datablock.
>1, Identification number of a BLSEG entry that lists nodes on edges of the
body which are excluded from the SPLINE option. (See Remark 10.)
This option may be used for deformable or rigid contact surfaces. See
PARAM,MSPLINC0 to enforce C0 continuity.
CONTROL Indicates the type of control for the body.
(4,6) Integer:
= -1 for position control, = 0 for velocity control.
= positive number for “load control” (the positive number is the grid number
which has translational forces or SDCP’s are applied. The position of this grid
is at the center of rotation given in the CGID field. For velocity controlled
surfaces, the velocity of the body must be specified by the VELRBi fields. For
displacement controlled surfaces the final displacement can be specified using
SPCD at the grid ID specified by CONTROL. CONTROL > 0 is not available
for enforced motion using SPCD’s for 2D contact using SOL 600.

Main Index
 1236 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

NLOAD Enter a positive number if “load controlled” and rotations are allowed (Integer).
(4,7) The positive number is the grid number where the moments or rotations are
applied. The position of this grid is at the center of rotation given in the CGID
field. 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 starting with
the MSC Nastran 2007 release by dof’s 4-6 (for rotation about x, y, z
respectively). For versions prior to MSC Nastran 2007 only dof’s 1-3 could be
used.
ANGVEL Angular velocity or angular position about local axis through center of rotation.
(6,1) (Real or Integer; Default = 0.0) If the value is an integer it represents the ID of
a TABL3Di.
DCOS1 3D - First component direction cosine of local axis if ANGVEL is nonzero.
(6,4) (Real)
2D - First coordinate of initial position of rotation of rigid body.
DCOS2 3D - Second component direction cosine of local axis if ANGVEL is nonzero.
(6,5) (Real)
2D - Second coordinate of initial position of rotation of rigid body
DCOS3 3D - Third component direction cosine of local axis if ANGVEL is nonzero.
(6,6) (Real)
2D - Not used.
VELRB1 2D & 3D - Velocity or final position (depending on the value of CONTROL) of
(5,4) rigid body in 1st direction. (Real or Integer; Default = 0.0) If the value is an
integer it represents the ID of a TABL3Di.
VELRB2 2D & 3D - Velocity or final position (depending on the value of CONTROL) of
(5,5) rigid body in 2nd direction. (Real or Integer; Default = 0.0) If the value is an
integer it represents the ID of a TABL3Di.
VELRB3 3D - Velocity or final position (depending on the value of CONTROL) of rigid
(5,6) body in 3rd direction. (Real or Integer; Default = 0.0) If the value is an integer
it represents the ID of a TABL3Di.
2D - Not used.
ADVANCE The entries for this continuation line are for advanced options starting with
MSC Nastran 2007.
SANGLE Threshold for automatic discontinuity detection in degrees. (Real, Default =
60.0) SANGLE values on the BCBODY entry can be overridden using the
SANGLE Bulk Data entry. This allows SANGLE to change for different
subcases. It also allows analytical contact for this body to be “on” or “off” for
different subcases (see the SANGLE Bulk Data entry). [Marc Spline option
(3,4)]

Main Index
 BCBODY 1237
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

COPTB Flag to indicate how body surfaces may contact. See Remark 20. on the
BCTABLE entry. (Integer; Default = 0)
USER A series of character flags to indicate which (if any) user subroutines are
required for this contact body. Enter as many characters as necessary to specify
the user subroutines desired, for example to use MOTION and UFIRC enter
MF. (Character; Default = blank meaning no user subroutines are required)
(SOL 600 Only)

M = The MOTION user subroutine is required to describe complex motion of

a rigid contact body.

F = The UFRIC or UFRICBBC user subroutine is required to describe complex

friction behavior of the contact body.

C = Film coefficient and sink temperature user subroutine UHTCON is required

(coupled structural/heat analysis only)

P = 4-Node patch user subroutine DIGEOM is required (the coordinates of the

patch are entered in the user subroutine rather than on the BCBODY entry).

S = The SEPSTR or SEPFOR user subroutine is required depending on whether

stress-based or force-based friction has been specified using BCPARA IBSEP.
“CTYPE” The entries of this continuation line define whether the original node-to-
segment or segment-to-segment contact algorithm is used. Also the selection of
general or small sliding contact and associated values when segment-to-
segment contact is selected are entered here. These options may be placed on
BCPARA instead of BCBODY (which is the recommended option. BCBODY
entries override BCPARA entries). For MSC Nastran 2012, these items should
be considered beta-test capabilities.
ISMALL Enter 0 for general contact or 1 for small sliding, small displacement contact.
[3,1] See Remarks 15 and 16. (Integer; Default = 0)
ICTYPE Enter 0 for node-to-segment contact or 1 for segment-to-segment contact. See
[3,2] Remarks 15 and 16. (Integer; Default = 0)
IAUG This entry applies only if segment-to-segment contact is selected. See Remarks
[3,3] 15 and 16. (Integer; Default = 0)
0 = No augmentation
1 = Augmentation is based on a constant Lagrange multiplier field for linear
elements and on a bilinear Lagrange multiplier field for quadratic elements.
2 = Augmentation is based on a constant Lagrange multiplier field.
3 = Augmentation is based on a bilinear Lagrange multiplier field.

Main Index
 1238 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

PENALT Augmented Lagrange penalty factor, used by segment-to-segment contact only.

[5,1] The default is derived from the contact tolerance distance and the stiffness of
the deformable contact bodies or average stiffness if two deformable bodies are
in contact. See Remark 18. (Real; Default = leave blank)
AUGDIST Penetration distance beyond which an augmentation will be applied, used by
[5,2] segment-to-segment contact only. this default is 1% of the contact tolerance
distance. See Remark 18. (Real; Default = leave blank)
“RIGID” The entries of this continuation line are for the rigid body description. See
Remark 3.
CGID Grid point identification number defining the initial position of the center of
(5,i) i=1,2,3 rotation for the rigid body or the point where a concentrated force or moment is
(4,6) applied.
NENT Number of geometric entities to describe this rigid surface. A rigid surface can
(4,2) 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 Name associated with the rigid body. (Default is blank, 24-characters
(4,9) maximum)
“APPROV” The entries for this continuation line are used for rigid contact body approach
velocity and angular velocity. (For SOL 600, APPVEL may be used instead of
APPROV if desired.)
A Angular velocity about local axis through center of rotation. The local axis is
defined by DCOS1, DCOS2, DCOS3. (Real; Default = 0.0)
Ni Not used by SOL 600. The direction cosines for approach velocity in SOL 600
are DCOS1, DCOS2, DCOS3 on the second BCBODY line. (Real; Default =
0.0; Ni values entered on this line are ignored for SOL 600)
Vi V1, V2 and V3 define the three components of approach velocity. For 2D
contact only two should be entered as defined by Rx or Ry (see each 2D rigid
contact body description for the meaning of Rx and Ry). (Real; Default = 0.0)
“RTEMP” The entries of this continuation line describe rigid contact surface temperature
variations.
G(Temp) Grid point identification number defining the location of the temperature.
(Integer; no Default)
Tempr Temperature at the start of the run. (Real; no Default)
T(Tempr) Identification number of a TABL3Di describing the variation of the rigid body
temperature during the analysis. (Integer; Default = 0 which means a constant
value Ttempr is used during the entire analysis)

Main Index
 BCBODY 1239
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

“SINK” The entries of this continuation line describe sink temperatures and their
variation for flexible or heat transfer bodies.
G(sink) Grid point identification number of defining the location of the sink
temperature. (Integer; no Default)
Tsink Sink temperature at the start of the run. (Real; no Default)
T(Tsink) Identification number of a TABL3Di describing the variation of the sink
temperature during the analysis. (Integer; Default = 0 which means a constant
value Tsink is used during the entire analysis)
“GROW” The entries for this continuation line are for rigid body growth - This line is
rarely used. If entered PARAM,MRCONVER,11 must be used. If tables are
used for growth, they should either be TABLED1 (growth vs time) or TABL3Di
(growth vs one or more variables) and PARAM,MRCONTAB,11 must be
entered.
GF1 Growth factor of rigid body in first coordinate direction. (Real; Default = 1.0)
(7,5)
GF2 Growth factor of rigid body in second coordinate direction. (Real; Default =
(7,6) 1.0)
GF3 Growth factor of rigid body in third coordinate direction. (Real; Default = 1.0)
(7,7)
TAB-GF1 Table for growth factor of rigid body in first coordinate direction. (Integer or
(8,5) blank; Default is blank which means no table and growth factor varies from 0.0
to 1.0 over the subcase being analyzed.)
TAB-GF2 Table for growth factor of rigid body in second coordinate direction. (Integer or
(8,6) blank; Default is blank which means no table and growth factor varies from 0.0
to 1.0 over the subcase being analyzed.)
TAB-GF3 Table for growth factor of rigid body in third coordinate direction. (Integer or
(8,7) blank; Default is blank which means no table and growth factor varies from 0.0
to 1.0 over the subcase being analyzed.)
“HEAT” The entries of this continuation line(s) are for contact in heat transfer. Do not
enter these line(s) for structural analyses.
CFILM Heat transfer coefficient (film) to environment. (Real or Integer; Default = 0.0
(9,1)/(10,1) for a heat transfer problem, omit for a structural problem) If Real, the value
entered is the film coefficient. If Integer, the value entered is the ID of a
TABLEM1 entry specifying the heat transfer coefficient vs temperature. This is
usually called HCVE in the Marc documentation.

Main Index
 1240 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

TSINK Environment sink temperature. (Real or Integer; Default = 0.0 for a heat transfer
(9,2)/(10,2) problem, omit for a structural problem). If Real, the value entered is the sink
temperature. If Integer, the value entered is the ID of a TABLEM1 entry
specifying temperature vs time. At present, this variable should not be a
function of temperature.
CHEAT Contact heat transfer coefficient. (Real or Integer; Default = 1.0 for a heat
(9,3)/(10,3) transfer problem, omit for a structural problem). If Real, the value entered is the
contact heat transfer coefficient. If Integer, the value entered is the ID of a
TABLEM1 entry specifying the contact heat transfer coefficient vs
temperature.
TBODY Body temperature. (Real or Integer; Default = 0.0 for a heat transfer problem,
(9,4)/(10,4) omit for a structural problem). If Real, the value entered is the body
temperature. If Integer, the value entered is the ID of a TABLEM1 entry
specifying the body temperature vs time. At present, this variable should not be
a function of temperature.
HCV Convection coefficient for near field behavior (Real or Integer; Default = 1.0
(9,5)/(10,5) for a heat transfer problem, omit for a structural problem). If Real the value
entered is the near field convection coefficient. If Integer, the value entered is
the ID of a TABLEM1 entry specifying the near field convection coefficient vs
temperature.
HNC Natural convection coefficient for near field behavior (Real or Integer; Default
(9,6)/(10,6) = 1.0 for a heat transfer problem, omit for a structural problem). If Real, the
value entered is the near field natural convection coefficient. If Integer, the
value entered is the ID of a TABLEM1 entry specifying the near field natural
convection coefficient vs temperature.
ITYPE An option entry for heat transfer only (Integer; no Default)
[4,8] 1 - Heat sink
4 - Heat conduction body
BNC Exponent associated with the natural convection coefficient for near field
(9,7)/(10,7) behavior (Real or Integer; Default = 0.0 for a heat transfer problem, omit for a
structural problem). 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 entry specifying the exponent associated with the near field
natural convection coefficient vs temperature. At present, this variable should
not be a function of temperature.
EMISS Emissivity for radiation to the environment or near thermal radiation (Real or
(9,8)/(10,8) Integer; Default = 0.0 for a heat transfer problem, omit for a structural problem).
If real, the value entered is the emissivity. If Integer, the value entered is the ID
of a TABLEM1 entry specifying the emissivity vs temperature.

Main Index
 BCBODY 1241
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

HBL Separation distance dependent thermal convection coefficient (Real or Integer;

(11,1)[12,1] Default = 0.0 for a heat transfer problem, omit for a structural problem). If Real,
the value entered is a convection coefficient. If Integer, the value entered is the
ID of a TABLEM1 entry specifying the convection coefficient vs temperature.
“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)
“POLY” Entries for this continuation line describe a rigid body made up of Poly
Surfaces.
NP1 Number of points in the 1st direction. (Integer > 0)
NP2 Number of points in the 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)
“CYLIND” Entries for this continuation line describe a cylindrical rigid body.
NSUB Number of subdivisions. (Integer > 0)
Gtop Grid point ID of a grid in the center of the top of the cylinder. (Integer > 0)
Rtop Radius of the top of the cylinder. (Real > 0.0)
Gbottom Grid point ID of a grid in the center of the bottom of the cylinder. (Integer > 0)
Rbottom Radius of the bottom of the cylinder. (Real > 0.0)
“SPHERE” Entries for this continuation line describe a spherical rigid body.
NSUB Number of subdivisions. (Integer > 0)
Gcenter Grid point ID of a grid in the center of the sphere. (Integer > 0)
Radius Radius of the sphere. (Real > 0.0)

Main Index
 1242 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

“LINE” Entries for this continuation line describe a 2D rigid body made up of as many
line segments as desired.
NPTS Number of points in the line segment.
Ix Grid direction (1, 2, or 3) of the G1, G2, ... list to be used as the first coordinate
in Marc’s 2D line description. See Remark 12. (Integer; Default = 1).
Iy Grid direction (1, 2, or 3) of the G1, G2, ... list to be used as the second
coordinate in Marc’s 2D line description. See Remark 12. (Integer; Default = 2).
Rx Direction (1, 2, or 3) used as the first VELRBi in Marc’s 2D contact description.
(Integer; Default = 1)
Ry Direction (1, 2, or 3) used as the second VELRBi in Marc’s 2D contact
description. (Integer; Default = 2)
G1, G2, G3, G4 Grid numbers for each of the NPTS points on the line segment.
“ARC” Entries for this continuation line describe a 2D rigid body made up of as many
segments as desired describing an arc.
NPTS Number of points in the arc. NPTS must be 4 for an ARC.
MethArc Method to generate arc (Integer 0 to 4) (see Marc volume C Contact description
(SOL 400 chapter 9) Figures 3-3 and 3-4).
Ix Grid direction (1, 2, or 3) of the G1, G2, ... list to be used as the first coordinate
in Marc’s 2D line description. See Remark 12. (Integer; Default = 1).
Iy Grid direction (1, 2, or 3) of the G1, G2, ... list to be used as the second
coordinate in Marc’s 2D line description. See Remark 12. (Integer; Default = 2).
Rx Direction (1, 2, or 3) used as the first VELRBi in Marc’s 2D contact description.
(Integer; Default = 1)
Ry Direction (1, 2, or 3) used as the second VELRBi in Marc’s 2D contact
description. (Integer; Default = 2)
G1, G2, G3, G4 Grid numbers for each of the 4 points as described by method.
“SPLINE” Entries for this continuation line describe a 2D rigid body made up of as many
spline segments as desired.
NPTS Number of points for the spline.
Ix Grid direction (1, 2, or 3) of the G1, G2, ... list to be used as the first coordinate
in Marc’s 2D line description. See Remark 12. (Integer; Default = 1).
Iy Grid direction (1, 2, or 3) of the G1, G2, ... list to be used as the second
coordinate in Marc’s 2D line description. See Remark 12. (Integer; Default = 2).
Rx Direction (1, 2, or 3) used as the first VELRBi in Marc’s 2D contact description.
(Integer; Default = 1)

Main Index
 BCBODY 1243
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

Ry Direction (1, 2, or 3) used as the second VELRBi in Marc’s 2D contact

description. (Integer; Default = 2)
G1, G2, G3, G4 Grid numbers for each of the NPTS points on the spline.
“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
Rx Direction (1, 2, or 3) used as the first VELRBi in Marc’s 2D contact description.
(Integer; Default = 1)
Ry Direction (1, 2, or 3) used as the second VELRBi in Marc’s 2D contact
description. (Integer; Default = 2)
G1, G2, G3, G4 Grid numbers for each of the NPTU control points
X1, Y1, X2, Y2, etc. Alternate method to define control points without using GRID points. There
must be abs(NPTU)*NPTV (x,y,z) entries.
Homo1, Homo2, Homogeneous coordinates (0.0 to 1.0) (Real). There must be NPTU entries.
Homo3, etc.
Knot1, Knot2, Knot vectors (0.0 to 1.0) (Real). There must be (NPTU+NORU) entries.
Knot3, etc.
“NURBS2” Entries for this continuation line describe a rigid body made up of nurbs.
IDN ID of a matching GMNURB entry. The GMNURB is an entry that contains the
same information as at shown for the NURBS option. (Integer > 0)
“NURBS” Entries for this continuation line describe a rigid body made up of nurbs.
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)
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, etc. Grid point IDs defining control points (Integer > 0). There must be
NPTU*NPTV entries.

Main Index
 1244 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

Field Contents

X1, Y1, Z1, X2, Y2, Alternate method to define control points without using GRID points. There
Z2, etc. must be abs(NPTU)*NPTV (x,y,z) entries.
Homo1, Homo2, Homogeneous coordinates (0.0 to 1.0). There must be NPTU*NPTV entries.
Homo3, etc (Real)
Knot1, Knot2, Knot vectors (0.0 to 1.0). There must be (NPTU+NORU)+(NPTV+NORV)
Knot3, etc entries. (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, Homo2, Homogeneous coordinates (0.0 to 1.0) of this trimming vector. There must be
Homo3, etc NPTUtrim entries. (Real)
Knot1, Knot2, Knot vectors (0.0 to 1.0) of this trimming vector. There must be
Knot3, etc NPTUtrim+NORUtrim entries. (Real)

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. 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. For 3D patches, if all need to be reversed, the parameter
PARAM,MARCREVR,1 may be entered to automatically reverse all 3D patches.
4. (i,j) refers to data block i and field j of Marc’s CONTACT model definition entry. IDSPL covers
the SPLINE history definition in Marc. For structural analysis (i,j) refers to contact without tables.
For heat transfer (i,j) refers to contact with tables.
5. For BEZIER surfaces, enter np1*np2 points in the order shown:

Main Index
 BCBODY 1245
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

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

2 3 4
1 2 1 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. The heat transfer options are available for SOL 600 starting with MSC.Nastran 2005 r2 and must
use Marc 2005 or later.
8. For heat transfer items described using a TABLEM1 ID, the smallest value in the table will be
entered into Marc’s 9th contact (with tables) datablock. The table ID will be translated directly to
Marc’s 10th contact (with tables) datablock.
9. All flexible surfaces must have smaller BID values then the rigid surfaces so that in the Marc file
all flexible surfaces are defined prior to all rigid surfaces. This is a Marc limitation.
10. 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.
11. With NURBS2D, the coordinates x1, x2, y1, y2 etc. or those given by G1, G2, etc. will be
reversed (Y becomes X and X becomes Y) if any CQUADX, CTRIAX or CTRIAX6 entries are
found in the bulk data. It is up to the user to ensure that the rigid contact surface is orientated in
the correct direction after this reversal. If the user does not want the reversal to happen, enter
PARAM,MARCREVX,-1 in the bulk data.
12. Ix and Iy for LINE, ARC, SPLINE and NURBS2D must be the same for all entries in the model.
An example would be if CTRIAX6 is defined in the Z-X plane, set Ix = 3 and Iy = 1 for all 2D
rigid surfaces in the model. For CTRIAX and CQUADX, normally Ix=2 and Iy=1.

Main Index
 1246 BCBODY
Flexible or Rigid Contact Body in 2D and 3D in SOL 600

13. Rx and Ry for LINE, ARC, SPLINE and NURBS2D must be the same for all entries in the model.
An example would be if CTRIAX6 is defined in the Z-X plane, set Ix = 3 and Iy = 1 for all 2D
rigid surfaces in the model. For CTRIAX and CQUADX, normally Ix=2 and Iy=1.
14. For SOL 600, tables using integers for ANGVEL, VELRB1, VELRB2 and/or VELRB3 require
PARAM,MRCONVER,11 and PARAM,MARCTOTT,1 to be set. the TABLE3D’s used must
define the entire motion/velocity desired.
15. If any CTYPE entries are used, PARAM,MRCONVER,11 and PARAM,MRCONVER,11 are
required.
16. ISMALL, ITYPE, IAUG should be the same for all BCTABLE entries. The first entry “CTYPE”
entry will be used for all bodies. PENALT and AUGDIST may vary from body to body.
17. 2D and 3D rigid bodies may not be mixed in the same input file.
18. The entries on the CTYPE header may optionally be specified on the BCPARA entry.
Correlation between BCBODY “CTYPE” entries and equivalent BCPARA entries:

BCPARA BCPARA CTYPE value(s)

METHOD NODESURF ictype=0, ismall=0
METHOD NODSMALL* ictype=0, ismall=1
METHOD SEGSMALL ictype=1, ismall=1
METHOD SEGMENT* ictype=1, ismall=1
METHOD SEGLARGE* ictype=1, ismall=0
AUTMENT Integer Value IAUG=Integer Value
PENALT Real Value PENALT=Real Value
AUGDIST Real Value AUTDIST=Real Value
* Not available in SOL 600.

19. Most continuation lines may be omitted if not required except that the second line is required if
the third or subsequent lines are to be entered.

Main Index
 BCBODY1 1247
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 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

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

Field Contents
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.

Main Index
 1248 BCBODY1
Flexible or Rigid Contact Body in 2D and 3D (New Form)

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..).
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 BCGM700 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)

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. For 3D patches, if all need to be reversed, the parameter
PARAM,MARCREVR,1 may be entered to automatically reverse all 3D patches
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
 BCBOX 1249
3D Contact Region

BCBOX 3D Contact Region

Defines a 3D contact region - all elements within the region define a contact body in SOL 600 and 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

Field Contents

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.

Main Index
 1250 BCBOX
3D Contact Region

Field Contents

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)

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
 BCBZIER 1251
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

Field Contents
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 NP2 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.

Main Index
 1252 BCBZIER
Defines a Rigid Contact Body Made up of Bezier Surfaces in SOLs 101 and 400

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
 BCGM700 1253
Defines a Rigid Geometrical Contact Body in SOL 700

BCGM700 Defines a Rigid Geometrical Contact Body in SOL 700

Defines a rigid geometrical contact body in SOL 700 only. BCGM700 must be assigned to MASTERS
of BCONECT. This entry is only available with METHOD=ENTITY in BCONPRG.
Although the rigid body is usually made by mesh which has rigid material, predefined rigid shape is also
available in SOL 700.
Geometric contact entities treat the impact between a deformable body defined as a set of slave nodes or
nodes in a shell part set and a rigid body. The shape of the rigid body is determined by attaching geometric
entities. Contact is treated between these geometric entities and the slave nodes using a penalty
formulation. The penalty stiffness is optionally maximized within the constraint of the Courant criterion.
As an alternative, a finite element mesh made with shells can be used as geometric entity. Also,
axisymmetric entities with arbitrary shape made with multi-linear polygons are possible. The latter is
particularly useful for metal forming simulations.
WARNING: If the problem being simulated involves dynamic motion of the entity, care should be taken
to insure that the inertial properties of the entity are correct. It may be necessary to use the inertia tensor
of MATRIG entry to specify these properties.

Format:

1 2 3 4 5 6 7 8 9 10
BCGM700 RBID PID GEOTYP INTORID SO GO INOUT
XC YC ZC AX AY AZ
BX BY BZ
G1 G2 G3 G4 G5 G6 G7

Examples:

BCGM700 4 5 2 3 1 1 0
0.0 0.0 0.0 1.0 0.0 0.0
0.0 1.0 0.0
0.15 75.0 20.0 12.7

Field Contents
RBID Unique identification number referenced by a BCBODY1 entry. (Integer > 0)
PID Shell or solid property ID of the rigid body to which the geometric entity is attached.
(Integer > 0, required) See Remark 3.

Main Index
 1254 BCGM700
Defines a Rigid Geometrical Contact Body in SOL 700

GEOTYP Type of geometric entity (Integer > 0, required):

1 plane,
2 sphere,
3 cylinder,
4 ellipsoid,
5 torus,
10 finite plane,
11 TABLED1 defining line as surface profile of axisymmetric rigid bodies.
INTORD Integration order (slaved materials only). This option allows a check of the penetration
of the rigid body into the deformable (slaved) material. Then virtual nodes at the location
of the integration points are checked. (Integer, default=0)

0 check nodes only,

1 1 point integration over segments,
2 2×2 integration,
3 3×3 integration,
4 4´4 integration,
5 5´5 integration.
SO Flag to use penalty stiffness as in surface-to-surface contact (integer, default=0):

0 contact entity stiffness formulation,

1 surface to surface contact method,
< 0 |SO| is the TABLED1 ID giving the force versus the normal penetration.
GO Flag for mesh generation of the contact entity for entity types 1-5 and 10-11. This is used
for visualization in post-processing only. (Integer, default=0)

0 mesh is not generated,

1 mesh is generated.
INOUT In-out flag. Allows contact from the inside or the outside of the entity (Integer,
default=0):

0 slave nodes exist outside of the entity,

1 slave nodes exist inside the entity.
XC, YC, Center point, (xc, yc, zc). See Remarks 5. and 6. (Real, default=0.0)
ZC
AX,AY,AZ Direction for local axis x, (Ax, Ay, Az). See Remarks 4. and 5. (Real, default=0.0)

Main Index
 BCGM700 1255
Defines a Rigid Geometrical Contact Body in SOL 700

BX,BY,BZ Direction for local axis y, (Bx, By, Bz). See Remarks 4 and 5. (Real, default=0.0)
Gi Entity coefficient gi, see remark 6. (Real, default=0.0)

Remarks:
1. BCGM700 must be assigned to MASTERS of BCONECT.
2. FRIC, VDC, TSTART, TEND and SFS contact parameters are only supported and SOFT is set to
0 (penalty contact) automatically.
3. Shell or Solid properties referenced by BCRG700 must use a rigid material, MATD020 or
MATRIG. To assign a mass and an inertia tensor, please use MATRIG.
4. The coordinates, (xc, yc, zc), are the positions of the local origin of the geometric entity in global
coordinates. The entity’s local x-axis is determined by the vector (Ax, Ay, Az) and the local y-
axis by the vector (Bx, By, Bz).
5. The second and third lines define a local to global transformation. The geometric contact entities
are defined in a local system and transformed into the global system. For the ellipsoid, this is
necessary because it has a restricted definition for the local position. For the plane, sphere, and
cylinder, the entities can be defined in the global system and the transformation becomes (xc, yc,
zc)=(0,0,0), (Ax, Ay, Az)=(1,0,0), and (Bx, By, Bz)=(0,1,0).
6. Figure 8-1 shows the definitions of the geometric contact entities. The relationships between the
entity coefficients and the variables in Figure 8-1 are as follows (please note that (Px,Py,Pz) is a
position vector and that (Qx,Qy,Qz) is a direction vector):
GEOTYP = 1:
g1 = Px (Real, required)
g2 = Py (Real, required)
g3 = Pz (Real, required)
g4 = Qx (Real, required)
g5 = Qy (Real, required)
g6 = Qz (Real, required)
g7 = L (Real, required)
If automatic generation is used, a square plane of length L on each edge is generated which
represents the infinite plane. If generation is inactive, then g7 may be ignored.
GEOTYP = 2:
g1 = Px (Real, required)
g2 = Py (Real, required)
g3 = Pz (Real, required)
g4 = r (Real, required)
GEOTYP = 3:
g1 = Px (Real, required)

Main Index
 1256 BCGM700
Defines a Rigid Geometrical Contact Body in SOL 700

g2 = Py (Real, required)
g3 = Pz (Real, required)
g4 = Qx (Real, required)
g5 = Qy (Real, required)
g6 = Qz (Real, required)
g7 = r (Real, required)
2 2 2
If automatic generation is used, a cylinder of length Qx + Qy + Qz at and radius r is generated
which represents the infinite cylinder.
GEOTYP = 4:
g1 = Px (Real, required)
g2 = Py (Real, required)
g3 = Pz (Real, required)
g4 = a (Real, required)
g5 = b (Real, required)
g6 = c (Real, required)
g7 = n (order of the ellipsoid) (Integer, required)
GEOTYP = 5:
g1 = Radius of torus (Real, required)
g2 = r (Real, required)
g3 = number of elements along minor circumference (Integer, required)
g4 = number of elements along major circumference (Integer, required)
GEOTYP =10:
g1 = Length of edge along X′ axis (Real, required)
g2 = Length of edge along Y′ axis (Real, required)
GEOTYP=11:
g1 = TABLED1 ID defining axisymmetric surface profile about Z’-axis. The x and y values
in the table represent Z’ locations and radii, respectively. (Integer, required)
g2 = Number of elements along circumference (Integer, default=10)
g3 = Number of elements along axis (Integer, default=20)
g4 = Number of sub divisions on table used to calculate contact (Integer, default=1000)

Main Index
 BCGM700 1257
Defines a Rigid Geometrical Contact Body in SOL 700

IGTYPE=1: Infinite Plane IGTYPE=2: Sphere

IGTYPE=3: Infinite Cylinder IGTYPE=4: Hyper ellipsoid

IGTYPE=5: Torus

IGTYPE=10: Finite Plate

IGTYPE=11: Load Curve

Figure 8-1 GEOTYP definitions.

Main Index
 1258 BCGRID
Contact Node Region

BCGRID 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

Field Contents
ID Unique identification number of a “cloud” of gridpoints which can be used for
contact or FLOWSPH, RCONN, SPCD2, 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 SLAVE 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
 BCHANGE 1259
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

Field Contents
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.

Main Index
 1260 BCHANGE
Changes Definitions of Contact Bodies

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.
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. f 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
 BCHANGE 1261
Changes Definitions of Contact Bodies in SOL 600

BCHANGE Changes Definitions of Contact Bodies in SOL 600

Changes definitions of contact bodies used in SOL 600.

Format:

1 2 3 4 5 6 7 8 9 10
BCHANGE ID TYPE NBOD IDBOD1 N1 N2 INC
IDBOD2 N1 N2 INC IDBOD3 etc.

Example:
BCHANGE 201 NODE 2 1 1001 1010 1
2 2001 2021 2

Field Contents
ID Identification number referenced by a SUBCASE Case Control command. See
Remark 2. (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.
NBOD Number of bodies to be modified -- must match number of bodies actually entered.
More than one N1-N2-INC range may be entered for each body, see Remark 7. See
N1 below. (Integer > 0; Default = 1)
IDBODi Identification number of a contact body, BCBODY entry. (Integer > 0)
N1 Starting grid ID.
N2 Ending grid ID.
INC Grid ID increment.

Remarks:
1. To place an entry in Marc’s phase 0, set ID=0. To activate the entry for the first SUBCASE, SET
ID=1, for the 2nd, set ID=2.
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. The BCHANGE entry covers Marc’s history definitions CONTACT NODE and EXCLUDE.
4. BCHANGE is useful only for saving computer time and is not recommended for general usage.
5. Warning -- For the NODE option, if some nodes in a body are inadvertently omitted, they may
penetrate other bodies.

Main Index
 1262 BCHANGE
Changes Definitions of Contact Bodies in SOL 600

6. If more than one N1-N2-INC range is required for a body, enter N1 as a negative value for all
ranges except for the last range for which N1 is entered as a positive value.
7. If more than one N1-N2-INC range is required, all ranges with IBOD1 must come first, followed
by all with IBOD2, etc.
8. The EXCLUDE option is obsolete. The reasons why it was added in the past have been alleviated
by better improved contact algorithms. If the EXCLUDE option is entered for 3D shapes two N1-
N2-INC ranges are normally required to define all 4 nodes of a patch. If the patch is triangular,
the last two nodes must be repeated. The following are examples of how data are entered for one
element using the exclude option. The first example is for a 4-node patch (nodes 100, 110, 200,
300) and the second is for a 3-node patch (nodes 132, 97, 95, 95).

BCHANGE 1 EXCLUDE 1 1 -100 110 10

1 200 300 100

BCHANGE 1 EXCLUDE 1 1 -132 132 0

1 -97 97 0 1 -95 95 0
1 95 95 0

Main Index
 BCMATL 1263
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 600 and 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

Field Contents
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
 1264 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

Field Contents
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
 BCMOVE 1265
Movement of Bodies in Contact in SOL 600

BCMOVE Movement of Bodies in Contact in SOL 600

Defines movement of bodies in contact to be used in SOL 600.

Format:

1 2 3 4 5 6 7 8 9 10
BCMOVE ID MTYPE IREL
IDRBOD1 IDRBOD2 IDRBOD3 etc.

Examples:
BCMOVE 33 RELEASE 20
1 3 5 7
BCMOVE 1 approach

Field Contents
ID Identification number referenced by a SUBCASE or STEP Case Control command.
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.
IREL Flag to indicate how contact forces are removed, for option RELEASE only.
(Integer)
=0 Contact forces are immediately removed. (Default)
>0 Contact forces are reduced to zero over the number of increments
specified in this load period. See NLPARM and TSTEP1 for the
number of increments.
IDRBODi Identification numbers of rigid bodies to be released, for option RELEASE only.
Points to BCBODY Bulk Data entries.

Remarks:
1. To place an entry in Marc’s phase 0, set ID=0. To activate the entry for the 1st SUBCASE, SET
ID=1, for the 2nd, set ID=2. ID must be unique (only one BCMOVE per SUBCASE).

Main Index
 1266 BCMOVE
Movement of Bodies in Contact in SOL 600

2. This entry matches Marc’s history definitions RELEASE, APPROACH, and SYNCHRONIZED.
Note that Marc’s history definition MOTION CHANGE is done in MSC Nastran by describing
the enforced motion for the grid which is defined to be the center of rotation of the rigid body, see
CGID of the BCBODY entry.
3. For MTYPE=APPROACH and MTYPE=SYNCHRON leave all following fields blank.
4. The APPROACH and SYNCHRON options apply to rigid contact surfaces only.
5. You may release a deformable body from contact with either a deformable or rigid body.

Main Index
 BCNURB2 1267
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

Field Contents
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.

Main Index
 1268 BCNURB2
Defines a 2D Rigid Contact Body Made up of NURBS in SOLs 101 and 400

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.
X1, Y1, X2, Y2, Alternate method to define control points without using GRID points. There must
etc. be 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 1269
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

Field Contents
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)

Main Index
 1270 BCNURBS
Defines a Rigid Contact Body Made up of NURBS in SOLs 101 and 400

NPTV Number of control points in V directions. (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)
“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, Homot2, Homogeneous coordinates (0.0 to 1.0) of this trimming vector. There must be
Homot3, etc. NPTUtrim entries. (Real)
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 1271
Defines the Touching and Touched Contact Bodies

BCONECT Defines the Touching and Touched Contact Bodies

Defines the touching and touched contact bodies used in SOLs 101, 400 and 700 for general contact.
Defines the touching and touched contact bodies used in SOLs 101, 103, 105, 107, 108, 109, 110, 111,
112, 200 and 400 for general contact, glued, step glue or permanent glue.

Format:

1 2 3 4 5 6 7 8 9 10
BCONECT ID BCGPID BCPPID IDSLAVE IDMASTER

“SLAVES” IDSL1 IDSL2 IDSL3 IDSL4 IDSL5 IDSL6 IDSL7

IDSL8 IDSL9 -etc.-

“MASTER IDMA1 IDMA2 IDMA3 IDMA4 IDMA5 IDMA6 IDMA7

S”
IDMA8 IDMA9 -etc.-

Examples:

BCONECT 57 306 2 1002

BCONECT 9 108
SLAVES 30 26
MASTERS 294 135 528

Field Contents
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.
IDSLAVE Identification number of BCBODY1 entry defining the touching body (Integer > 0 or
blank). See Remarks 3. and 4.
IDMASTER Identification number of BCBODY1 entry defining the touched body (Integer > 0 or
blank). See Remarks 5. and 6.
“SLAVES” Indicates the start of the list of the touching bodies. See Remark 4.
IDSLi Identification number of BCBODY1 entry defining the touching bodies (Integer > 0).

For SOL 700, leaving IDSL1 blank will result in contact for all elements in the model.
In this case, you are allowed to use ADAPT=YES.

Main Index
 1272 BCONECT
Defines the Touching and Touched Contact Bodies

“MASTERS” Indicates the start of the list of bodies touched by touching bodies. See Remark 6.
IDMAi Identification number of BCBODY1 entry defining touched bodies (Integer > 0).

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 IDSLAVE. On the other
hand, if the user leaves IDSLAVE blank, then “SLAVES” descriptor is required and IDSL1 must
be specified. Exceptions are for SOL 700 self-contact, which may use a slave IDSL1 of zero and
no “MATERS” entry.
4. “SLAVES” and IDSLi fields will be ignored if IDSLAVE exists. If IDSLAVE field is blank, then
“SLAVES” and IDSLi must be specified. In this case, each IDSLi will be processed separately.
5. A short input to define a single touched body exists if the user provides IDMASTER. On the other
hand, if the user leaves IDMASTER blank, then “MASTERS” descriptor is required and IDMA1
must be specified.
6. “MASTERS” and IDMAi fields will be ignored if IDMASTER exists. If IDMASTER field is
blank, then “MASTERS” and IDMAi must be specified.
7. The concept of Slave and Master 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 100*) or
the 1st Step (SOL 400) then the connections are considered to be permanent and do not change
(unless a BCPARA NLGLUE is used to deactivate the permanent glue).

Main Index
 BCONP 1273
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.

Format:

1 2 3 4 5 6 7 8 9 10
BCONP ID SLAVE MASTER SFAC FRICID PTYPE CID

Example:

BCONP 95 10 15 1.0 33 1

Field Contents
ID Contact region identification number. See Remark 1. (Integer > 0)
SLAVE Slave region identification number. See Remark 2. (Integer > 0)
MASTER Master 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 (slave 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 SLAVE is the identification number in the BLSEG Bulk Data entry. This is the
slave line. The width of each slave segment must also be defined to get proper contact stresses.
See the Bulk Data entry, BWIDTH, 1434 for the details of specifying widths.
3. The referenced MASTER is the identification number in the BLSEG Bulk Data entry. This is the
master line. For symmetrical penetration, the width of each master segment must also be defined.
See the Bulk Data entry, BWIDTH, 1434 for the details of specifying widths.

Main Index
 1274 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 slave nodes are checked for penetration into master
segments. This may result in master nodes penetrating the slave line. However, the error depends
only on the mesh discretization. In symmetric penetration both slave and master nodes are
checked for penetration. Thus, no distinction is made between slave and master. Symmetric
penetration may be up to thirty percent more expensive than the unsymmetric penetration.
7. In Figure 8-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 master segment.
For a master segment the direction from master node 1 to master node 2 gives the tangential
direction (t). The normal direction for a master 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 slave region. For
symmetric, penetration, the normals of master segments and slave segments must face each other.
This is generally accomplished by traversing from master line to slave 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 Slave Segment

k+1 k k-1 Slave Line • X-Y plane is the slideline

plane. Unit normal in the
l-1 Z-direction is the slideline
l+1 plane vector.
Master Line
• Arrows show positive
direction for ordering
nodes. Counterclockwise
l-th Master from master line to slave
Y Segment
line.
• Slave and master segment
X normals must face each
Slideline Plane Vector other.
Z Direction

Figure 8-2 A Typical Finite Element Slideline Contact Region

Main Index
 BCONPRG 1275
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.

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

Field Contents
BCGPID Identification number for geometric contact parameters (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 8-3 (Character).
VALi Value of a parameter. See Table 8-3 (Real or Integer).

Table 8-3 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 or is equal to 0.0, the default is the
BIAS of the BCPARA entry. A nonblank or non-zero entry will override the BIAS
entered on the BCPARA entry. To obtain a near zero value, enter 1.0E-16. (0.0 ≤ Real ≤
1.0)
CINTERF Interference closure amount, normal to the contact surface. For CINTERF > 0.0, overlap
between bodies. For CINTERF < 0.0, gap between bodies. (Real; Default = 0.0)
COPTS, Flag to indicate how slave and master surfaces may contact. See Remark 2. (Integer;
COPTM Default = 0) COPTS and COPTM apply to all slave and master surfaces on the
associated BCONECT.
ERROR Distance below which a node is considered touching a body. Default = blank, automatic
calculation. See BCPARA Bulk Data entry for more details. (Real)

Main Index
 1276 BCONPRG
Geometric Contact Parameters of Touching Bodies

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
slave nodes. (Real; Default = 2.0) This parameter is ignored for the permanently glued
contact.
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.
ISEARCH Option for contact searching order, from Slave to Master or from Master to Slave, 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 Slave to Master.

2 (Single order search) let the program decide which search order. See Remark 3.

Main Index
 BCONPRG 1277
Geometric Contact Parameters of Touching Bodies

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.

Remarks:
1. 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.
• = 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.

Main Index
 1278 BCONPRG
Geometric Contact Parameters of Touching Bodies

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 segment-to-segment contact only use B=1 or B-6.
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.
CB1= Min(1/20 of the smallest edge,1/4 of the smallest thickness) of BCBODY1 ID1
CB2= 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 CB1≤1.05*CB2.
Otherwise, if CB1>1.05*CB2 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.
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. To
define a permanently glued contact, see Remark 3.of BCONTACT Case Control command.
6. By default, the threshold value of this penetration distance is 0.05 times the default contact
characteristic distance.
AUGDIST=0.05 L
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).

Main Index
 BCONPRG 1279
Geometric Contact Parameters of Touching Bodies

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
PENALT = -----------------i
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.

Main Index
 1280 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
BCONPRP PID PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3
PARAM4 VAL4 PARAM5 VAL5 -etc.-

Example:

BCONPRP 90 IGLUE 1

Field Contents
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 8-4 (Character).
VALi Value of a parameter. See Table 8-4 (Real or Integer).

Table 8-4 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)
AUTOMV Move the master surface to close an initial gap between slave and master surfaces.
(Integer, default=0)

0: Not move
1: move to close gap
ATMVTID Only available when AUTOMV=1. Optional TABLED1 ID defining velocity versus
time. The table will be adjusted to account for the movement of the master surface. The
table should be defined by four points, and its shape should resemble a trapezoid with
the longest parallel side along the x-values. The x-values are adjusted (shortened) in the
flat part of the curve where the velocity is constant to account for the movement.
(Integer≥0, default=not used)
AUMVAT Only available when AUTOMV=1. Activation time. At this time the master surface is
moved. (Real≥0.0, Default=0.0)
AUMVXT Only available when AUTOMV=1. X-coordinate of tail of vector of direction of master
surface movement (Real; Default = 0.0)

Main Index
 BCONPRG-700 1281
Geometric Contact Parameters of Touching Bodies in SOL 700

AUMVYT Only available when AUTOMV=1. Y-coordinate of tail of vector of direction of master
surface movement (Real; Default = 0.0)
AUMVZT Only available when AUTOMV=1. Z-coordinate of tail of vector of direction of master
surface movement (Real; Default = 0.0)
AUMVXH Only available when AUTOMV=1. X-coordinate of head of vector of direction of master
surface movement (Real; Default = 0.0)
AUMVYH Only available when AUTOMV=1. Y-coordinate of head of vector of direction of master
surface movement (Real; Default = 0.0)
AUMVZH Only available when AUTOMV=1. Z-coordinate of head of vector of direction of master
surface movement (Real; Default = 0.0)
AUMVCID Only available when AUTOMV=1. Coordinate system ID to define vector in local
coordinate system. All coordinates, AUMVXT, AUMVYT, AUMVZT, AUMVXH,
AUMVYH, and AUMVZH are in respect to AUMVCID. (Integer, default=none)
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.

Main Index
 1282 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700

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 Slave 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.
1 Same as 0 above but with failure after sticking.
2 Glue contact with failure is active for nodes which are initially in contact. Until
failure, tangential motion is inhibited. If IGNOFF is set to 1 shell thickness
offsets are ignored, and the orientation of the shell surfaces is required such
that the outward normals point to the opposing contact surface. This option is
only available with METHOD=SS1WAY or SS2WAY and AUTO=YES.
3 Same as 0 above but with failure after sticking.
4 Glue contact is active for nodes which are initially in contact but tangential
motion with frictional sliding is permitted. This option is only available with
METHOD=SS1WAY or SS2WAY and AUTO=YES.
5 Glue contact is active for nodes which are initially in contact. Stress is limited
by the yield condition described in Remark 6. Damage is a function of the
crack width opening. This interface can be used to represent deformable glue
bonds. This option is only available with METHOD=SS1WAY or SS2WAY
and AUTO=YES.
6 This option is for use with solids and thick shells only. Tiebreak is active for
nodes which are initially in contact. Failure stress must be defined for tiebreak
to occur. After the failure stress tiebreak criterion is met, damage is a linear
function of the distance C between points initially in contact. When the
distance is equal to CDIST damage is fully developed and interface failure
occurs. After failure, this contact option behaves as a surface-to-surface
contact. This option is only available with METHOD=SS1WAY or SS2WAY
and AUTO=YES.
7 Dycoss Discrete Crack Model. This option is only available with
METHOD=SS1WAY or SS2WAY and AUTO=YES. METHOD=SS1WAY
is recommended. See Remarks 20.
8 This option is similar to JGLUE=6 but works with offset shell elements. This
option is only available with METHOD=SS1WAY or SS2WAY and
AUTO=YES.
9 Discrete Crack Model with power law and B-K damage models. This option is
only available with METHOD=SS1WAY or SS2WAY and AUTO=YES.
METHOD=SS1WAY is recommended. See Remarks 21.

Main Index
 BCONPRG-700 1283
Geometric Contact Parameters of Touching Bodies in SOL 700

JGLUE cont. 10 This option is similar to JGLUE=7 but works with offset of shell elements.
This option is only available with METHOD=SS1WAY or SS2WAY and
AUTO=YES. METHOD=SS1WAY is recommended. See Remarks 20.
11 This option is similar to JGLUE=9 but works with offset of shell elements.
This option is only available with METHOD=SS1WAY or SS2WAY and
AUTO=YES. METHOD=SS1WAY is recommended. See Remarks 21.
21 Glue contact with failure is active for nodes which are initially in contact.
Failure is based upon force limits for nodes to surface contact. Only allowed
for METHOD=FULL.
22 Glue contact with failure is active for nodes which are initially in contact.
Failure is based upon force limits for nodes only contact. Only allowed for
METHOD=FULL
23 Glue contact with failure is active for nodes which are initially in contact. This
option allows the definition of a resisting stress versus gap opening for the post
failure response. This option can be only used with METHOD=SS2WAY.

Main Index
 1284 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700

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
TIEDES: Tied Shell Edge to Surface
TIEDSS: Tied Surface to Surface
TIEDNSO: Tied Nodes to Surface with Offset
TIEDESO: Tied Shell Edge to Surface with Offset
TIEDSSF: Tied Surface to Surface with Failure
TIEDSSO: Tied Surface to Surface with Offset
GENERAL: General Contact Definition
INTERIOR: Interior Contact (see Remark 2.)
TIEDNSCO: Tied Nodes to Surface Constrained Offset
TIEDESCO: Tied Shell Edge to Surface Constrained Offset
TIEDSSCO: Tied surface to Surface Constrained Offset
SPOTWELD: Spotweld Contact
SPOTWTOR: Spotweld with Torsion Contact
EDGE: Single Edge Contact (Master Body no allowed)
FTRANSC: Force Transducer Constraint
FTRANSP: Force Transducer Penalty
FORMNS: Forming Nodes to Surface
FORM1SS: Forming One Way surface to Surface
FORM2SS: Forming Surface to Surface
DRAWBEAD: Drawbead contact

Main Index
 BCONPRG-700 1285
Geometric Contact Parameters of Touching Bodies in SOL 700

ADAPT Character, influences the contact type used. (Character, Default = NO)

Options are NO or YES.

When ADAPT=YES, the BCBODY1 entries IDMAi must be defined as:

behav=DEFORM
bsid references a BCPROP
THICK Shell thickness scale factor. (Real > 0.0; Default = 1.0)
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.
PENCHK Small penetration in contact search option. If the slave node penetrates more than the
segment thickness times the factor XPENE (specified by PARAM,DYXPENE), the
penetration is ignored and the slave node is set free. The thickness is taken as the shell
thickness if the segment belongs to a shell element or it is taken as 1/20 of its shortest
diagonal if the segment belongs to a solid element. This option applies to the surface-to-
surface contact algorithms. (Integer > 0, Default=1)

Options are:

1 Check is turned off.

2 Check is turned on.
3 Check is on but shortest diagonal is used.
SOFT Soft constraint option: (Integer ≥ 0; Default = 1)

0 Penalty formulation.
1 Soft constraint formulation (same as original Dytran method).
2 Segment-based contact.
4 Constraint approach for FORMING contact option
In the penalty formulation, the interface stiffness is based on the elastic bulk moduli of
the materials.

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.

Main Index
 1286 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700

DEPTH Search depth. (Integer > 0; Default = 2)

A value of 1 is sufficiently accurate for most crash applications, and is much less
expensive. For improved accuracy, the Default = 2.
ISYM Symmetry plane option. (Integer ≥ 0; Default = 0)

0 Off
1 Do not include faces with normal boundary conditions (e.g. segments of
brick elements on a symmetry plane).
This option is important to retain the correct boundary conditions in the model with
symmetry.
I2D3D Segment searching option. (Integer ≥ 0, Default = 0)

0 Search 2-D elements (shells) before 3D elements (solids)

1 Search 3-D elements (solids) before 2D elements (shells)
IGNORE Ignore initial penetrations. Only active when AUTO=YES. (Integer, Default = 0)

0 Take default from PARAM,DYCONIGNORE*,<value> (Default)

1 Allow initial penetrations to exist by tracking it
2 Move nodes to eliminate initial penetrations
SBOPT Segment-based contact options (SOFT=2). (Integer, Default = 2)

Options are:

0 Defaults to 2.
1 Pinball edge-edge contact (not recommended)
2 Assume planer segments
3 Warped segment checking
4 Sliding option
5 Do options 3 and 4
SST Optional thickness for slave surface (overrides true thickness). This option applies only
to contact with shell elements. True thickness is the element thickness of the shell
elements. For the Tied contacts, SST and MST below can be defined as negative values,
which will cause the determination of whether or not a node is tied to depend only on the
separation distance relative to the absolute value of these thicknesses. See Remark 19.
(Real, Default = element thickness)
MST Optional thickness for master surface (overrides true thickness). This option applies only
to contact with shell elements. True thickness is the element thickness of the shell
elements. For the Tied contacts see SST above. (Real, Default = element thickness)

Main Index
 BCONPRG-700 1287
Geometric Contact Parameters of Touching Bodies in SOL 700

SFST Scale factor for slave surface thickness (scales true thickness). This option applies only
to contact with shell elements. True thickness is the element thickness of the shell
elements. (Real, Default = 1.0)
SFMT Scale factor for master surface thickness (scales true thickness). This option applies only
to contact with shell elements. True thickness is the element thickness of the shell
elements. (Real, Default = 1.0)
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.
PSF Penalty scale factor. Only used for METHOD=INTERIOR. (Real, Default = 1.00)
IGNOFF Include shell thickness option. Only for JGLUE=2 and 23. (Integer; Default =0)

0 Shell thickness is included. (Currently not supported for JGLUE=23.)

1 Shell thickness is ignored.
CDIST Only for JGLUE=6, 7, 8, 9, 10 or 11. Critical distance at which the interface failure is
complete for JGLUE=6 or 8. For JGLUE=7 or 10 this is the friction angle in degrees.
For JGLUE=9 or 11, this is the exponent in the damage model. A positive value invokes
the power law, while a negative one, the B-K model. (Real; Required)
SMOOTH For smooth contact, a smooth curve-fitted surface is used to represent the master
segment, so that it can provide a more accurate representation of the actual surface,
reduce the contact noise and produce smoother results with a coarse mesh. This option
is only available for METHOD equal to: FULL, SS1WAY, SS2WAY, FORMNS,
FORM1SS, FORM2SS. (Integer; Default = 0.)

0 Not active.
1 Activate smooth contact.

Main Index
 1288 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700

FLANGL Angle tolerance in radians for feature lines option in smooth contact. Any edge with an
angle between to contact segments larger than FLANGL will be treated as a feature line
during curve fitting. If blank or 0.0 no line is considered for surface fitting. (Real > 0.0;
Default = 0.0.)
PENMAX Maximum penetration depth Nodes that are penetrated more than PENMAX released
from the contact definition. Definition and default are different for METHOD. (See
tables.) For SOFT=2, this option is ignored.

For AUTO=NO and METHOD=SS2WAY, SS1WAY or FULL, or JGLUE=21 or 22:

Maximum penetration distance. If 0.0 use small penetration search and value calculated
from thickness and XPENE.

For AUTO=YES and METHOD=SS2WAY, SS1WAY, FULL or single surface contact

or ADAPT=YES, or METHOD=GENERAL:The segment thickness multiplied by
PENMAX defines the maximum penetration allowed (as a multiple of the segment
thickness). If 0.0, the default is 0.4 for all above contacts, except for
METHOD=GENERAL for which the default is 200.0 times the segment thickness.
(Real > 0.0; Default = Blank.)

Table 8-5: Criterion for node release for nodal points which have penetrated too far.
Larger penalty stiffnesses are recommended for the contact interface which allows
nodes to be released. For node-to- surface type (METHOD=FULL) the element
thicknesses which contain the node determines the nodal thickness.

Table 8-5 Criteria for Node Release

ELEMENT Formula for Release of

Contact Type PENCHK TYPE Penetrating Nodal Point
AUTO=NO and 0 Solid/Shell d=PENMAX if an only if PENMAX>0
METHOD=SS2WAY, d=1.e+10 if PENMAX=0
SS1WAY or FULL, or 1 Solid/Shell d=XPENE*thickness of shell element
JGLUE=21 or 22
(without thickness) 2 Solid/Shell d=0.05*minimum diagonal length

AUTO=NO and N/A Solid d=XPENE*thickness of solid element

METHOD=SS2WAY, Shell d=XPENE*thickness of shell element
SS1WAY or FULL
(thickness included)
AUTO=YES and N/A Solid d=PENMAX*thickness of solid
METHOD=SS2WAY, element[default: PENMAX=0.5]
SS1WAY, FULL or Shell d=PENMAX*(slave
single surface contact or thickness+masterthickness) [default:
ADAPT=YES PENMAX=0.4]

Main Index
 BCONPRG-700 1289
Geometric Contact Parameters of Touching Bodies in SOL 700

ELEMENT Formula for Release of

Contact Type PENCHK TYPE Penetrating Nodal Point
AUTO=NO and single N/A Solid d=0.5*thickness of solid element
surface contact Shell d=0.4*(slave thickness+master
thickness)
METHOD=GENERAL N/A Solid d=PENMAX*thickness of solid element
[default: PENMAX=200.0]
Shell d=PENMAX*(slave thickness+master
thickness) [default: PENMAX=200]

THKOPT Thickness option for contact types for AUTO=NO and METHOD=SS2WAY, SS1WAY
or FULL: (Integer > 0; Default = 0)

0 Default is taken from DYPARAM, LSDYNA, CONTACT.

1 Thickness offsets are included.
2 Thickness offsets are not included (old way).
For SOFT=2, this option is ignored.
SHLTHK Define if and only if THKOPT above equals 1. Shell thickness considered in type surface
to surface and node to surface type contact options, where options 1 and 2 below activate
the new contact algorithms. The thickness offsets are always included in single surface
and constraint method contact types: (Integer > 0; Default = 0.)

0 Thickness is not considered.

1 Thickness is considered but rigid bodies are excluded.
2 Thickness is considered including rigid bodies.
For SOFT=2, this option is ignored.
SLDTHK Optional solid element thickness. The value will activate the contact thickness offsets in
the contact algorithms where offsets apply. The contact treatment will then be equivalent
to the case where null shell elements are used to cover the solid elements.(Real > 0.0;
Default = 0.0.)
ERATEN For JGLUE=7, 9, 10 and 11 only. Normal energy release rate (stress*length) used in
damage calculation, see Lemmen and Meijer [2001]. (Real; default=0.0.)
ERATES For JGLUE=7, 9, 10 and 11 only. Shear energy release rate (stress*length) used in
damage calculation, see Lemmen and Meijer [2001]. (Real; default=0.0.)
CT2CN The ratio of the tangential stiffness to the normal stiffness only for JGLUE=9 and 11.
(Real; default = 1.0.)

Main Index
 1290 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700

CN Normal stiffness (stress/length) only for JGLUE=9 and 11. If CN is not given explicitly,
penalty stiffness is used. This optional stiffness should be used with care, since contact
stability can get affected. A warning message with a recommended time step is given
initially. (Real; default=penalty stiffness.)
DAMP1 Opening mode (Mode I - a tensile stress

normal to the plane of the crack) damping force per unit velocity per unit area only for
JGLUE=9 and 11. (Real; default=0.0.)
DAMP2 Sliding mode (Mode II - a shear stress

acting parallel to the plane of the crack and perpendicular to the crack front) damping
force per unit velocity per unit area only for JGLUE=9 and 11. (Real; default=0.0.)
DAMP3 Tearing mode (Mode III - a shear stress

acting parallel to the plane of the crack and parallel to the crack front) damping force
per unit velocity per unit area only for JGLUE=9 and 11. (Real; default=0.0.)

Remarks:
1. Contact method: TIEDNSCO, TIEDESCO, and TIEDSSCO. If this option is set, then offsets are
permitted for these contact types. The Constrained Offset option is a constraint type formulation.
The nodal points in the TIEDNSCO option and the TIEDSSCO may not be connected to structural
nodes, i.e., nodes with rotational degrees-of-freedom, since the rotational degrees-of-freedom are
not affected, which will lead to an instability since the translational motions due to rotation are
imposed on the slave nodes.
2. Contact method: INTERIOR: Define interior contact for foam hexahedral and tetrahedral
elements. Frequently, when foam materials are compressed under high pressure, the solid
elements used to discretize these materials may invert leading to negative volumes and error
terminations. In order to keep these elements from inverting, it is possible to consider interior
contacts within the foam between layers of interior surfaces made up of the faces of the solid
elements. Since these interior surfaces are generated automatically, the property (material) ID’s
for the materials of interest are defined here, prior to the interface definitions. Only one
INTERIOR contact method can be defined per model. The interior penalty is determined by the
formula:

2-
--
3
SLSFAC ⋅ PSF ⋅ Volume ⋅ E
K = ----------------------------------------------------------------------------- ⋅ M
Min.Thickness

where SLSFAC is the value specified on the DYPARAM,LSDYNA,CONTACT,SLSFAC entry,

volume is the volume of the brick element, E is a constitutive modulus, and min. thickness is
approximately the thickness of the solid element through its thinnest dimension. If ED, is defined
above the interior penalty is then given instead by:

Main Index
 BCONPRG-700 1291
Geometric Contact Parameters of Touching Bodies in SOL 700

2---
3
Volume ⋅ ED
K = -----------------------------------------
Min.Thickness
where the scaling factors are ignored. Generally, ED should be taken as the locking modulus
specified for the foam constitutive model.
Caution should be observed when using this option since if the time step size is too large,
instability may result. The time step size is not affected by the use of interior contact.
3. Options JGLUE = 2, 3, and 6 the Glue contact failure criterion has normal and shear components:

σn  2  σs  2
 --------------
- + -------------- ≥ 1
 NFLS  SFLS

4. Option JGLUE = 4, SFLS or FSLIM is required input.

5. Option JGLUE = 4, the Glue contact failure criterion has only a normal stress component:

σn
--------------
-≥1
NFLS

6. Option JGLUE=5, the stress is limited by a perfectly plastic yield condition. For ties in tension,
the yield condition is

2 2
σn + 3 σs
----------------------------------
-≤1
NLFS

For ties in compression, the yield condition is

2
3 σs
------------------
-≤1
NLFS

The stress is also scaled by the damage function which is obtained from the table. For ties in
tension, both normal and shear stress are scaled. For ties in compression, only shear stress is
scaled.
7. Options JGLUE=6 or JGLUE=8, damage initiates when the stress meets the failure criterion. The
stress is then scaled by the damage function. Assuming no load reversals, the energy released due
to the failure of the interface is approximately 0.5*S*CDIST, where

2 2
S = max ( σ n, 0 ) + σ s

at initiation of damage. This interface may be used for simulating crack propagation. For the
energy release to be correct, the contact penalty stiffness must be much larger than
MIN ( NFLF,SFLS )
-------------------------------------------------
CCRIT

Main Index
 1292 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700

8. Options JGLUE = 21 and 22, both NFLF and SFLF must be defined. If failure in only tension or
shear is required then set the other failure force to a large value (1E+10). After failure, the JGLUE
= 21 contact behaves as a nodes-to-surface contact with no thickness offsets (no interface tension
possible) whereas the JGLUE=22 contact stops acting altogether. Prior to failure, the two contact
types behave identically.
9. Options JGLUE = 23, Both NFLS and SFLS must be defined. If failure in only tension or shear
is required then set the other failure stress to a large value (1E+10). When used with shells, contact
segment normals are used to establish the tension direction (as opposed to compression).
Compressive stress does not contribute to the failure equation. After failure, this contact option
behaves as a surface-to-surface contact with no thickness offsets. After failure, no interface
tension is possible.
10. For METHOD=FORMNS, FORM1SS and FORM2SS: These contacts are mainly used for metal
forming applications. A connected mesh is not required for the master (tooling) side but the
orientation of the mesh must be in the same direction. These contact types are based on the
AUTO=YES type contacts and consequently the performance is better than the original two
surface contacts.
11. For METHOD=FTRANSC and FTRANSFP. This contact allows the total contact forces applied
by all contacts to be picked up. This contact does not apply any force to the model and will have
no effect on the solution. Only the slave set and slave set type need be defined for this contact
type. Generally, only the first three cards are defined. The force transducer option FTRANSFP,
works with penalty type contact algorithms only, i.e., it does not work with the METHOD=TIED
options. For these latter options, use the FTRANSC option. If the interactions between two
surfaces are needed, a master surface should be defined. In this case, only the contact forces
applied between the slave and master surfaces are kept. The master surface option is only
implemented for the FTRANSFP option and works only with the AUTO=YES contact types.
12. Setting SOFT=1 or 2 will cause the contact stiffness to be determined based on stability
considerations, taking into account the time step and nodal masses. This approach is generally
more effective for contact between materials of dissimilar stiffness or dissimilar mesh densities.
13. SOFT=2 is for general shell and solid element contact. This option is available for
METHOD=SS2WAY, SS1WAY, FORM1SS, FORM2SS and also for single surface contact,
airbag and eroding contact. When the AUTO=YES is used, orientation of shell segment normals
is automatic. When AUTO=NO the segment or element orientations are used as input. The
segment-based penalty formulation contact algorithm checks for segments vs. segment
penetration rather than node vs. segment. After penetrating segments are found, an automatic
judgement is made as to which is the master segment, and penalty forces are applied normal to
that segment. The user may override this automatic judgement by using METHOD=SS1WAY or
FORM1SS in which case the master segment normals are used as input by the user.
14. For SOFT=2 option VC, VSF, PENMAX, THKOPT, SHLTHK and SNLOG will be ignored.

Main Index
 BCONPRG-700 1293
Geometric Contact Parameters of Touching Bodies in SOL 700

15. For SOFT=2, the SBOPT parameter controls several options. The pinball edge-to-edge checking
is not recommended and is included only for back compatibility. For edge-to-edge checking
setting DEPTH=5 is recommended instead (see Remark 18.) The warped segment option more
accurately checks for penetration of warped surfaces. The sliding option uses neighbor segment
information to improve sliding behavior. It is primarily useful for preventing segments from
incorrectly catching nodes on a sliding surface.
16. For SOFT=2, the DEPTH parameter controls several additional options for segment based
contact. When DEPTH=2 (default), surface penetrations measured at nodes are checked. When
DEPTH=3, surface penetration may also be measured at the edge. This option is useful mainly for
airbags. When DEPTH=5, both surface penetrations and edge-to-edge penetration is checked.
When DEPTH=13, the penetration checking is the same as for DEPTH=3, but the code has been
tuned to better conserve energy. Then DEPTH=23, the penetration checking is similar to
DEPTH=3, but a new algorithm is used to try to improve robustness. The airbag contact has two
additional options, DEPTH=1 and 4. DEPTH=4 activates additional airbag logic that uses
neighbor segment information when judging if contact is between interior and exterior airbag
surfaces. This option is not recommended and is maintained only for backward compatibility.
Setting DEPTH=1 suppresses all airbag logic.
17. For SOFT=2 contact, the MAXPAR has a totally different use. Positive values of MAXPAR are
ignored. If a negative value is input for MAXPAR, the absolute value of MAXPAR will be used
as an assumed time step for scaling the contact stiffness. This option is useful for maintaining
consistent contact behavior of an airbag deployment when a validated airbag is inserted into an
automobile model. For the new run, setting MAXPAR=the negative of the solution time step of
the validated run will cause the airbag contact stiffness to be unchanged in the new run even if the
solution time step of the new run is smaller.
18. When METHOD option is set to TIEDNS, TIEDES, TIEDESSCO, SPOTWELD, SPOTWTOR
or TIEDSS, these contact definitions are based on constraint equations and will not work with
rigid bodies. However, tied interfaces with the offset options (METHOD = TIEDNSO, TIEDESO
or TIEDSSO) can be used with rigid bodies. Also, it may sometimes be advantageous to use the
RBE2A instead for tying deformable nodes to rigid bodies since in this latter cae the tied nodes
may be an arbitrary distance away from the rigid body.
19. Tying will only work if the surface are near each other. The criteria used to determine whether a
slave node is tied down is that it must be “close”. For shell elements “close” is defined as distance,
δ, less than:
δ 1 = 0.60 • ( thickness_slave_node + thickness_master_segment )

δ 2 = 0.50 • min ( master_segment_diagonals )

1 2
δ = max( ( δ , δ )

If a node is further away it will not be tied and a warning message will be printed. For solid
elements the slave node thickness is zero and the segment thickness is the element volume divided
by the segment area; otherwise, the same procedure is used.

Main Index
 1294 BCONPRG-700
Geometric Contact Parameters of Touching Bodies in SOL 700

If there is a large difference in element areas between the master and slave side, the distance,
δ2may be too large and may cause the unexpected projection of nodes that should not be tied. To
avoid this difficulty the slave and master thickness can be specified as negative values on SST and
MST options in which case
δ = abs ( δ 1 )

20. JGLUE = 7 or 10 is the Dycoss Discrete Crack Model as described in Lemmen and Meijer [2001].
The relation for the crack initiation is given as:
max ( σ n, 0 ) 2 σs
----------------------------
- + ------------------------------------------------------------------------------------------ = 1
NFLS SFLS ( 1 – sin ( CDIST ) min ( 0, σ n ) )

21. JGLUE = 9 or 11 is an extension of the Dycoss Discrete Crack Model based on the fracture model
using cohesive materials. See Fiolka and Matzenmiller [2005] and Gerlach, Fiolka and
Matzenmiller [2005]. Failure stresses/peak tractions NFLS and/or SFLS can be defined as
functions of characteristic element length (square root of master segment area) via TABLED1.
This option is useful to get nearly the same global responses (e.g. load-displacement curve) with
coarse meshes compared to a fine mesh solution. In general, lower peak tractions are needed for
coarser meshes.

Reference:
Fiolka, M. and Matzenmiller, A., "Delaminationsberechnung von Faserverbundstrukturen", PAMM
Proc. Appl. Math. Mech. 5, S.393-394 (2005).
Gerlach, S., Fiolka M. and Matzenmiller, A., Modelling and analysis of adhesively bonded joints with
interface elements for crash analysis, 4. LS-DYNA Forum, 20-21, (2005) Bamberg, DYNAmore GmbH,
Stuttgart.
Lemmen, P. P. M. and Meijer, G. J., "Failure Prediction Tool Theory and User Manual," TNO Report
2000-CMC-R0018, (2001).

Main Index
 BCONPRP 1295
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 PARAM VAL2 PARAM3 VAL3
2
PARAM4 VAL4 PARAM5 VAL5 -etc.-

Example:

BCONPRP 90 FRIC 0.3

Field Contents
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowabe names are given in Table 8-6 (Character).
VALi Value of a parameter. See Table 8-6 (Real or Integer).

Table 8-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.)

Main Index
 1296 BCONPRP
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400

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 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)
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.)

Main Index
 BCONPRP 1297
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400

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
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. This feature is not supported in segment-to-segment contact analysis.
2. For near contact:
q = HCV ⋅ ( T A – T B )+

BNC
HNC ⋅ ( T A – T B ) +

BNL BNL
HNL ⋅ ( TA – TB )+

Main Index
 1298 BCONPRP
Physical Contact Parameters of Touching Bodies in SOLs 101 and 400

4 4
σ ⋅ EMISS ⋅ ( T A –T B )+

dist dist
HCT ⋅  1 – -------------------------- + HBL ⋅ -------------------------- ⋅ ( T A – T B )+
4 4
 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, 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.

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.
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 1299
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

Field Contents
PID Parameter identification number (Integer > 0).
PARAMi Name of a parameter. Allowable names are given in Table 8-7 (Character).
VALi Value of a parameter. See Table 8-7 (Real or Integer).

Table 8-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. See Remark 2. of 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)
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)
FSF Coulomb friction scale factor. The Coulomb friction value is scaled as (Real, Default =
0.0)
VSF Viscous friction scale factor. If this factor is defined then the limiting force becomes:
(Real, Default = 0.0)

Main Index
 1300 BCONPRP-700
Physical Contact Parameters of Touching Bodies in SOL 700

EROSOP Erosion/Interior node option. (Integer ≥ 0; Default = 1)

0 Only exterior boundary information is saved.

1 Storage is allocated so that eroding contact can occur. Otherwise, no
contact is assumed after erosion of the corresponding element.
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.
BSORT Number of time-steps between bucket sorts. (Integer ≥ 0; Default = 0)

0 automatic determination by the algorithm

Values of 25-100 are recommended for single-surface contact.
Values of 10-15 are recommended for master-slave contact.
FRCFRQ Number of time-steps between contact force updates for penalty contact formulations.
This option can provide significant speed-up of the contact treatment. If used, values
exceeding 3 or 4 are dangerous. Considerable care must be exercised when using this
option, as this option assumes that contact does not change for FRCFRG time-steps.
(Integer > 0; Default = 1) (force calculations are performed each cycle)
SNLOG Disable shooting node logic in thickness offset contact. With the shooting node logic
enabled, the first cycle that a slave node penetrates a master segment, that node is moved
back to the master surface without applying any contact force. (Integer ≥ 0; Default = 1)

0 On (advised for crash simulation)

1 Off (sometimes recommended for metal forming calculations or for contact
involving foam materials)
For SOFT=2, this option is ignored.
SPR Option to include the slave side in the NCFORC and the INTFOR interface force
files.(Integer, Default = 0)

Options are:

0 Slave side forces not included.

1 Slave side forces included.

Main Index
 BCONPRP-700 1301
Physical Contact Parameters of Touching Bodies in SOL 700

MPR Include the master side in the NCFORC and the INTFOR interface force files. (Integer,
Default = 0)

Options are:

0 Master side forces not included

1 Master side forces included
VDC Viscous damping coefficient in percent of critical. In order to avoid undesirable
oscillation in contact, e.g., for sheet forming simulation, a contact damping
perpendicular to the contacting surfaces is applied. Damping coefficient ζ = VDC
------------- ζ wd,
100
e.g., VDC=20. ζ crit is determined in the following fashion by LS-DYNA. (Real,
Default = 0.0)

ζ crit = 2mw ;m = min ( m slave, m master )

m slave + m master
w = k ⋅ ----------------------------------------- k interface stiffness
m slave ⋅ m mas ter

SFS Scale factor on default slave penalty stiffness. (Real, Default = 1.0)
SFM Scale factor on default master penalty stiffness. (Real, Default = 1.0)
LCID TABLED1 ID giving force versus penetration behavior for RIGID contact. See also the
definition of FCM below. Only allowed and required input when METHOD is
RB1WAY, RB2WAY or RNRB. (Integer, Required)
FCM Force calculation method for rigid contact. Only allowed and required input when
METHOD is RB1WAY, RB2WAY or RNRB. (Integer, Required)

Options are:

1 TABLED1 gives total normal force on surface versus maximum penetration of

any node (RB1WAY only).
2 TABLED1 gives normal force on each node versus penetration of node
through the surface (all rigid body contact types).
3 TABLED1 gives normal pressure versus penetration of node through the
surface (RB1WAY and RB2WAY only).
4 TABLED1 gives total normal force versus maximum soft penetration. In this
case the force will be followed based on the original penetration point.
(RB1WAY only).
US Unloading stiffness for rigid contact. The default is to unload along the loading curve.
This should be equal to or greater than the maximum slope used in the loading curve.
Only allowed input when METHOD is RB1WAY, RB2WAY or RNRB. (Real, Default
= same as LCID ID)

Main Index
 1302 BCONPRP-700
Physical Contact Parameters of Touching Bodies in SOL 700

FA Activation factor, When the crushing of the element reaches Fa times the initial
thickness the contact algorithm begins to act. Only used for METHOD=INTERIOR.
(Real, Default = 0.10)
ED Optional modulus for interior contact stiffness. Only used for METHOD=INTERIOR.
(Real; Default = 0.0)
INTTYPE Formulation for interior contact. Only used for METHOD=INTERIOR. (Integer;
Default = 1)

1 Recommended for uniform compression. (Default)

2 Designed to control the combined modes of shear and compression. Works
for type 1 brick formulation and type 10 formulation (see PSOLIDD).
NFLS Normal failure stress. Only for JGLUE = 1, 2, 3, 4, 6, 7, 8, 9, 10, 11 or 23. For JGLUE=9
or 11 and NFLS<0, a TABLED ID= - NFLS is referenced defining normal failure stress
as a function of element size. (Real; Required.)
SFLS Shear failure stress. Only for JGLUE = 1, 2, 3, 6, 7, 8, 9, 10, 11 or 23. Optional input for
JGLUE = 4. For JGLUE=9 or 11 and SFLS<0, a TABLED ID= - SFLS is referenced
defining shear failure stress as a function of element size. (Real; Required)
FSLIM Frictional stress limit. Only optional input for JGLUE=4. (Real > 0; blank)
PYS Plastic yield stress as defined in Remark 6. of BCONPRP entry. Only for JGLUE = 5.
(Real > 0; Required)
TIDC Damage table ID. The damage function is defined by a load curve which starts at unity
for a crack width of zero and decays in some way to zero at a given value of the crack
opening. Only for JGLUE=5. (Integer; Required)
NFLF Normal failure force. Only tensile failure, i.e., tensile normal forces, will be considered
in the failure criterion. Only for JGLUE=21 or 22. (Real > 0; Required)
SFLF Shear failure force. Only for JGLUE=21 or 22. (Real > 0; Required)
NEN Exponent for normal force. Only for JGLUE=21 or 22. (Real > 0; Default = 2.0)
MES Exponent for shear force. Failure criterion: Failure is assumed if the left side is larger
than 1. fn and fs are the normal and shear interface force. Only for JGLUE=21 or 22.
(Real > 0; Default = 2.0)
TBLCID Optional load curve number defining the resisting stress versus gap opening for the post
failure response. This can be used to model the failure of adhesives. Only for
JGLUE=23. (Integer; Default = 0)
TBLAB TABLED1 ID defining airbag thickness as a function of time. Only used when
METHOD=AIRBAG. (Integer > 0; Default = 0.)
IGAP Flag to improve implicit convergence behavior at the expense of creating some sticking
if parts attempt to separate. Outputted contact forces may also be too small or zero. Only
used for prestress analysis (see PRESTRS or SPRBCK). (Integer > 0; Default = 1.)

1 Apply method to improve convergence.

2 Do not apply method.

Main Index
 BCONPRP-700 1303
Physical Contact Parameters of Touching Bodies in SOL 700

FTBID TABLEDR ID, giving the coefficient of friction as a function of the relative velocity and
pressure. This option must be used in combination with the thickness offset option. See
the figure below. Only used for METHOD=SS1WAY. (Integer > 0; Default = 0)

Friction coefficient, µ, can be a function of relative velocity and pressure. Specify a flag
for the static coefficient of friction, FS, and a TABLED1 ID for the dynamic coefficient.
This option only works with METHOD=SS1WAY with thickness offsets.
VC Coefficient for viscous friction. This is necessary to limit the friction force to a
maximum. A limiting force is computed:

F lim = VC ⋅ A cont

Acont being the area of the segment contacted by the node in contact. The suggested
σ
value for VC is to use the yield stress in shear VC = ------o- where is the yield stress of the
3
contacted material. (Real > 0.0; Default = 0.0.)
SLDSTF Optional solid element stiffness. The value overrides the bulk modulus taken from the
material model referenced by the solid element. (Real > 0.0; Default = 0.0.)
INTTID1 TABLED1 ID which scales the interface stiffness during dynamic relaxation. This curve
must originate at (0,0) at time=0 and gradually increase.
INTTID2 TABLED1 ID which scales the interface stiffness during the transient calculation. This
curve generally has a constant value of unity for the duration of the calculation if
INTTID1 is defined. If INTTID1=0, this curve must originate at (0,0) at time=0 and
gradually increase to a constant value.
DBID ID of DBREG entry. Only used if METHOD=DRAWBEAD. (Integer; Default= blank)

Main Index
 1304 BCONPRP-700
Physical Contact Parameters of Touching Bodies in SOL 700

TIDRF If TIDRF is positive then it defines the TABLED1 ID giving the bending component of
the restraining force, Fbending, per unit draw bead length as a function of displacement,
δ, see Figure 8-3. This force is due to the bending and unbending of the blank as it moves
through the draw bead. The total restraining force is the sum of the bending and friction
components.

If TIDRF is negative then the absolute value gives the TABLED1 ID defining max bead
force versus normalized draw bead length. The abscissa values are between zero and 1
and are the normalized draw bead length. The ordinate gives the maximum allowed
draw bead, retaining force when the bead is in the fully closed position. If the draw bead
is not fully closed linear interpolation is used to compute the draw bead force. (Integer;
Required when METHOD=DRAWBEAD)
TIDNF TABLED1 ID giving the normal force per unit draw bead length as a function of
displacement, δ, see Figure 8-3. This force is due to the bending of the blank into the
draw bead as the binder closes on the die and represents a limiting value. The normal
force begins to develop when the distance between the die and binder is less than the
draw bead depth. As the binder and die close on the blank this force should diminish or
reach a plateau, see Remarks 1. and 2.. (Integer, Required when
METHOD=DRAWBEAD.)
DBDTH Draw bead depth, see Figure 8-3. Necessary to determine correct δ displacement from
contact displacements. (Real; Required when METHOD=DRAWBEAD.)
DFSCL Scale factor for load curve. This factor scales TABLED1 ID, TIDRF above. Only used
when METHOD=DRAWBEAD. (Real; Default = 1.0)
NUMINT Number of equally spaced integration points along the drawbead. If 0: Internally
calculated based on element size of elements that interact with drawbead. This is
necessary for the correct calculation of the restraining forces. More integration points
may increase the accuracy since the force is applied more evenly along the bead. Only
used when METHOD=DRAWBEAD. (Integer; Default = 0)
THERMAL Thermal contact option (Integer, default=0):

0 no thermal contact
1 thermal contact
2 thermal friction contact (this option is only available when
METHOD=SS2WAY and AUTO=NO)
K Thermal conductivity of fluid between the contact surfaces. If a gap with a thickness
l gap exists between the slide surfaces, then the conductance due to thermal conductivity
between the slide surfaces is
k
h con d = ---------
l gap

Note that SOL700 calculates l gap based on deformation. Only available when
THERMAL = 1 or 2 (Real, required)

Main Index
 BCONPRP-700 1305
Physical Contact Parameters of Touching Bodies in SOL 700

FRAD Radiation factor, f, between the slide surfaces.

σ
f = --------------------------
-
1 1
----- + ----- – 1
ε1 ε2

Where, σ = Stefan Boltzmann constant

ε1 = emissivity of master surface
ε2 = emissivity of slave surface
SOL700 calculates a radiant heat transfer conductance

2 2
h rad = f rad ( T m + T s ) ( T m + T s )

Only available when THERMAL = 1 or 2 (Real, required)

H0 Heat transfer conductance for closed gaps. Use this heat transfer conductance for gaps
in the range

0 ≤ l gap ≤ l min

Only available when THERMAL = 1 or 2 (Real, required)

LMIN Minimum gap (), use the heat transfer conductance defined (H0) for gap thicknesses less
than this value.

Only available when THERMAL = 1 or 2 (Real, required)

LMAX No thermal contact if gap is greater than this value ( l max ). Only available when
THERMAL = 1 or 2 (Real, required)
CHLM A multiplier used on the element characteristic distance for the search routine. The
characteristic length is the largest interface surface element diagonal. Only available
when THERMAL = 1 or 2 (Real, default=1.0)
BC_FLAG Thermal boundary condition flag. Only available when THERMAL = 1 or 2. (Integer,
default=0)

0 Thermal boundary conditions are on when parts are in contact

1 Thermal boundary conditions are off when parts are in contact
ALGO Contact algorithm type. Only available when THERMAL = 1 or 2. (Integer, Default=0)

0 Two way contact, both surfaces change temperature due to contact

1 One way contact, master surface does not change temperature due to contact.
Slave surface does change temperature
TFST TABLED1 ID for static coefficient of friction as a function of temperature. The table
value multiplies the coefficient value FS. Only available when THERMAL = 2.
(Integer, default=none)

Main Index
 1306 BCONPRP-700
Physical Contact Parameters of Touching Bodies in SOL 700

TFDT TABLED1 ID for dynamic coefficient of friction as a function of temperature. The table
value multiplies the coefficient value FD. Only available when THERMAL = 2.
(Integer, default=none)
FORMULA Formula that defines the contact heat conductance as a function of temperature and
pressure. Only available when THERMAL = 2. (Integer, default=none)

Formula =1h(P) is defined by TABLED1 “a”

“a” defines a table for the contact conductance as a function of interface
pressure.
Formula =2 h(P) = a+bP+cP2+dP3
a TABLED1 ID for the “a” coefficient used in the formula. Only available when
THERMAL = 2. (Integer, Default=none)
b TABLED1 ID for the “b” coefficient used in the formula. Only available when
THERMAL = 2. (Integer, Default=none)
c TABLED1 ID for the “c” coefficient used in the formula. Only available when
THERMAL = 2. (Integer, Default=none)
d TABLED1 ID for the “d” coefficient used in the formula. Only available when
THERMAL = 2. (Integer, Default=none)

Remarks:
1. The draw bead is defined two ways:
a. A consecutive list of slave nodes that lie along the bead using BCGRID
b. A set of property ID¡¦s of beams that lie along the draw bead using BCPROP.
2. For straight draw beads only two nodes or a single beam need to be defined, i.e., one at each end,
but for curved beads sufficient nodes or beams are required to define the curvature of the bead
geometry. When beams are used to define the bead, with the exception of the first and last node,
each node must connect with two beam elements. This requirement means that the number of
slave nodes equals the number of beam elements plus one. The integration points along the bead
are equally spaced and are independent of the nodal spacing used in the definition of the draw
bead. By using the capability of tying extra nodes to rigid bodies (see RBE2A or MATD20M) the
draw bead nodal points do not need to belong to the element connections of the die and binder.
The blank makes up the master surface. It is highly recommended to use a DBREG around the
drawbead to limit the size of the master surface considered for the draw bead. This will
substantially reduce cost and memory requirements.

Main Index
 BCONPRP-700 1307
Physical Contact Parameters of Touching Bodies in SOL 700

Figure 8-3 Drawbead contact model defines a resisting force as a function of drawbead
displacement. The friction force is computed from the normal force in the
drawbead and the given friction coefficient.

Main Index
 1308 BCONUDS
Contact Body User Defined Service

BCONUDS Contact Body User Defined Service

Allows the user to provide contact routines for use with enhanced SOL 400 and SOL 700 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

Field Contents
BID Contact body identification number referenced by BCTABLE, BCTABL1,
BCHANGE, or BCMOVE. (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)

Main Index
 BCONUDS 1309
Contact Body User Defined Service

Field Contents
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)
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 SOL 400

BCBODY motion x
BCBODY ufric x
BCBODY sepfor x
BCBODY sepstr x
BCBODY ubsqueal x

8. For SOL700, BTYPE will be ignored and UFRIC in UNAME is only available.
9. For SOL700, input must include the information for IDATA and RDATA as the table below. Others
will be ignored.

IDATA1 BCONECT ID (contact definition id) to apply this user-defined friction. (Integer > 0;
Required)
IDATA2 Number of input parameters (PARAMi). (Integer? 0; default=0)

Main Index
 1310 BCONUDS
Contact Body User Defined Service

IDATA3 Number of history variables per node to be stored in user subroutines. (Integer ? 0;
default=0)
RDATA1~ Additional material parameters. The number of additional material parameters must be
RDATAn the same as IDATA2.

Main Index
 BCONUDS 1311
Contact Body User Subroutines in SOL 600

BCONUDS Contact Body User Subroutines in SOL 600

Allows the user to provide contact routines for use with SOL 600 contact analysis.

Format:

1 2 3 4 5 6 7 8 9 10
BCONUDS BID BTYPE UNAME
“INT” IDATA1 IDATA2 IDATA3 IDATA4 IDATA5 IDATA6 IDATA7
IDATA8 IDATA9 ... ... IDATAn
“REAL” RDATA1 RDATA2 RDATA3 RDATA4 RDATA5 RDATA6 RDATA7
RDATA8 RDATA9 ... ... RDATAn

Example:
BCONUDS 17 BCBODY RTN1

BCONUDS 17 BCBODY RTN2

REAL .00134 1.467+4 .03

BCONUDS 17 BCBODY RTN3

REAL .00134 1.467+4 .03

INT 8 3

Field Contents
BID Contact body (BCBODY) identification number. (Integer > 0; Required)
BTYPE The name of the contact entry. BCBODY (Character; no Default)
UNAME The Marc user subroutine name. See Remarks 2. and 5. (Character; Required)
“INT” Keyword indicating that the following data is integer. (Character)
IDATAi Additional user supplied Integer data not already existing on the specified MAT
entry. See Remark 6. (Integer; no Default)
“REAL” Keyword indicating that the following data is real. (Character)
RDATAi Additional user supplied Real data. See Remark 6. (Real; no Defaults)

Remarks:
1. The BID must match an existing BID.
2. Certain user subroutines may require integer or real data input as specified in the UserSubroutine
interface document.

Main Index
 1312 BCONUDS
Contact Body User Subroutines in SOL 600

3. The following user subroutines are currently available for user convenience. See the User
Subroutine interface document for details.

UNAME Purpose
MOTION Define velocity of rigid surfaces
UFRIC Define friction coefficients
DIGEOM Define rigid surfaces
SEPFOR Define separation forces
SEPFORBBC Define separation forces for beam-beam contact
SEPSTR Define separations stresses
UFRICBBC Define thermal near contact file coefficients
UHTNRC Define thermal near contact file coefficients
UMDCOE Define variable mass and diffusion coefficients and sink pressures on a
free surface
UMDCON Define variable mass diffusion coefficients on surfaces in contact with
other surfaces
UMDNRC Define mass diffusion coefficients of surfaces in contact with other
surfaces
UNDRST Define normal stresses for elements in contact

4. The BCONUDS entry may be used instead of the USRSUB6 entry. Both entries should not be
used in the same run. EVAL will be stored as a character*16 name in common block /userch/
5. UNAME identifies the user subroutine name to be called.
6. IDATA and RDATA are not normally required. They are available should additional arguments
beyond those described in Marc Vol D be required. Normally only the first line is entered.

Main Index
 BCPARA 1313
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.

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

Field Contents
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 8-8. (Character)
Value(i) Value of the parameter. See Table 8-8. (Real or Integer)

Table 8-8 Contact Parameters

Description, Type and Value (Default is 0 for Integer, 0.0 for
Name Real Unless Otherwise 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 or 0.0 (to obtain a near
zero value, enter 1.0E-16).
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.
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)

Main Index
 1314 BCPARA
Contact Parameters -SOLs 101 and 400

Table 8-8 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0 for
Name Real Unless Otherwise Indicated)
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)
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)
Only option 2 and 4 can be used with mid-side node elements where the
mid-side nodes contact (LINQUAD=-1). For segment to segment
contact, the program will set IBSEP to 2 internally. See Remarks 6. and
10.
FTYPE Friction type. See Remark 5. (Integer)
0 No friction. (Default)
6 Bilinear Coulomb friction.
7 Bilinear Shear friction.

Main Index
 BCPARA 1315
Contact Parameters -SOLs 101 and 400

Table 8-8 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0 for
Name Real Unless Otherwise Indicated)
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)
NLGLUE If all slave's for the BCTABLE or BCONPRG corresponding to the first
(SOLs 101 and loadcase (first subcase and first step) contain IGLUE >0, permanent
400 only) glued contact with small rotation condition will be used for all SLAVE
entries in all subcases and all steps unless BCPARA,0,NLGLUE,1 is
specified. If IGLUE < exists, permanent glued contact for large
deformation and large rotation is activated. For further discussions of
NLGLUE, see Remark 3. of BCONTACT. (Integer; Default = 0)
NODSEP Skip separation check in contact for any grid already touched and
separated. NODSEP times within the current increment. (Integer;
Default = 2)
>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.
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)

Main Index
 1316 BCPARA
Contact Parameters -SOLs 101 and 400

Table 8-8 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0 for
Name Real Unless Otherwise Indicated)
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 slave-master; Default = 0)
DDULMT Maximum value of DDU in a Newton-Raphson cycle. (Real ≥ 0.0;
Default = 0.0, no limitation)
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)

Remarks:
1. Field 2 of the primary line should be left blank or a value of zero should be entered. Blank is
treated as zero.
2. Only one BCPARA entry should be made. If multiple entries are made, the last will be used.
3. SOLs 101 and 400 only support ID=0. This entry is only applied in the loadcase 0.
4. Refer to the Case Control command BCONTACT (Case), Remark 5.c, 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.
6. 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.

Main Index
 BCPARA 1317
Contact Parameters -SOLs 101 and 400

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.
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 contact with
separation because there is no normal stress to shell elements, and the contact normal forces for
these elements do not give a good estimation of the nodal contact stress. This means that is not
recommended to use CQUAD8 and CTRIA6 shell elements in a node-to-segment contact analysis
with separation. If users still want to use these elements, they should set IBSEP=0, IBSEP=1 or
IBSEP=3. If IBSEP is set to 2 or 4 in this case, IBSEP will automatically be set to 1 or 3,
respectively. This limitation is not applied to the segment-to-segment contact.
7. For SOLs 101/400 if BEAMB=1, Bulk Data entry BCBMRAD must be entered.
8. Parameters MAXSEP, ICSEP, IBSEP, RVCNST, BEAMB and NLGLUE 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
( μ ⋅ F NORMAL , 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.

Main Index
 1318 BCPARA
Contact Parameters in SOL 600

BCPARA Contact Parameters in SOL 600

Defines contact parameters used in SOL 600.

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 NBODIES 4 BIAS 0.5

Field Contents
ID ID is not used and should be set to zero. Only one BCPARA should be entered and
it applies to all subcases. (Integer)
Param(i) Name of a parameter. Allowable names are given in Table 8-9. (Character)
Value(i) Value of the parameter. See Table 8-9. (Real or Integer)

Table 8-9 Contact Parameters

Description, Type and Value (Default is 0 for Integer, 0.0
Name for Real Unless Otherwise Indicated)
NBODIES (2,1) Number of contact bodies defined in the analysis. (Integer > 0 or
blank)
MAXENT (2,2) Maximum number of entities created for any contact body. (Integer
> 0 or blank; default is max element number or 1.5 times the number
of nodes whichever is smaller)
MAXNOD (2,3) Maximum number of nodes that lie on the periphery of any
deformable contact body. (Integer > 0 or blank; default is the number
of nodes)

Main Index
 BCPARA 1319
Contact Parameters in SOL 600

Table 8-9 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0
Name for Real Unless Otherwise Indicated)
ERROR (3,2) Distance below which a node is considered touching a body.
Automatically calculated if left blank. If left blank, the code
calculates ERROR as the smallest nonzero element dimension
divided by 20 or the shell thickness divided by 4. (Real; Default =
blank)
BIAS (3,6) Contact tolerance bias factor. (Real, 0 < BIAS < 1, Default = 0.9 if
field left blank or not entered in the file. To obtain a near zero value,
enter 1.0E-16)
ISPLIT (2,7) Flag for increment splitting procedure. (Integer > 0; Default = 3 for
statics and 0 for dynamics)
0 Uses increment splitting procedures for the fixed time
step procedures.
1 Suppresses splitting for the fixed time step procedures.
Any penetration that occurred in the previous increment
is adjusted for equilibrium at the start of the next
increment. This method may require smaller time steps
then the other methods
2 Suppresses splitting for adaptive time step procedures.
Any penetration that occurred in the previous increment
is adjusted for equilibrium at the start of the next
increment. This method may require smaller time steps
then the other methods.
3 Uses contact procedure which does not require increment
splitting (3 is not available for dynamics). If a run does
not converge due to an excessive number of “iterative
penetration checking” messages, ISPLIT=2 may help,
however the time steps may need to be set to smaller
values.
FNTOL (3,5) 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)
MAXSEP (2,6) 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)
ICHECK (2,8) Flag for interference kinematic check and bounding box check.
(Integer > 0)
1 Activates interference kinematic check.

Main Index
 1320 BCPARA
Contact Parameters in SOL 600

Table 8-9 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0
Name for Real Unless Otherwise Indicated)
2 Suppress bounding box checking.
3 No reset of NCYCLE to zero.
4 Check for separation only when solution has converged,
for analytical surfaces only.
ICSEP (2,9) Flag to control separation. (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 (2,12) 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).
Only option 2 and 4 can be used with mid-side node elements where
the mid-side nodes contact (LINQUAD=-1).
ISHELL (2,10) Parameter governing normal direction and thickness contribution of
shells. (Integer > 0; Default = 0)
0 Check node contact with top and bottom surface.
1 Nodes only come into contact with bottom layer.
2 Nodes only come into contact with bottom layer and shell
thickness is ignored.
-1 Nodes only come into contact with top layer.
-2 Nodes only come into contact with top layer and shell
thickness is ignored.

Main Index
 BCPARA 1321
Contact Parameters in SOL 600

Table 8-9 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0
Name for Real Unless Otherwise Indicated)
IPRINT (2,11) Flag to reduce print out of surface definition. (Integer > 0; Default =
0)
0 Full print out.
1 Reduced print out.
RVCNST Relative sliding velocity between bodies below which sticking is
(3,1) simulated. If FTYPE=5, then the value of RVCNST is the stick-slip
transition region.
FTYPE Friction type. (Integer)
(2,4)
0 No friction. (Default)
1 Shear friction.
2 Coulomb Friction.
3 Shear friction for rolling.
4 Coulomb friction for rolling.
5 Stick-slip Coulomb friction.
6 Bilinear Coulomb friction. (Default if friction is present
and FTYPE is not entered.)
7 Bilinear Shear friction.
FKIND Friction kind. (Integer 0 or 1)
(2,5)
0 Friction based on nodal stress.
1 Default if friction is present and FKIND is not entered.
Friction based on nodal force.
BEAMB Beam-Beam contact flag. (Integer 0 or 1)
(2,13)
0 No beam-beam contact. (Default)
1 Activate beam-beam contact options.
FSSMULT Stick-slip friction coefficient multiplier. Applicable only to stick-
(3,7) slip friction. (The friction coefficient is multiplied by this value for
the sticking condition.) (Real > 0; Required; Default = 1.05)
FSSTOL Stick-slip friction force tolerance. Applicable only to stick-slip
(3,8) friction. (Real; Default = 0.05)
LINQUAD Higher order element contact flag (Integer; Default = 1).
(2,14)

Main Index
 1322 BCPARA
Contact Parameters in SOL 600

Table 8-9 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0
Name for Real Unless Otherwise Indicated)
1 The outer boundary of a contact body is described by the
corner nodes only and mid-side nodes can’t come into
contact.
-1 The outer boundary is described by a quadratic field and
both corner and mid-side nodes are considered in contact.
If this flag is set to -1 and IBSEP is blank, IBSEP will be
re-set to 2. This option is only available with Marc 2003
and subsequent releases.
INITCON If INITCON is set, tying relations (MPC’s) for surfaces initially in
(2,16) contact will be saved. This option maybe used to model dissimilar
meshes. See CONTINUE=101+ on the SOL 600 entry to use these
items in the same MSC Nastran execution. The following options
are available:
1 MPC’s in Marc format are saved for initial contact (if any)
in file jid.marc.t01.
3 MPC’s for each increment are saved in Marc format in file
jid.marc.conmpc_xxxx where xxxx is the increment
number.
4 MPC’s for each increment are saved in Nastran MPC
format in file jidd.marc.conmpc_xxxx where xxxx is the
increment number.
When initcon=1, the job will stop at the end of increment zero.
When initcon=3 initcon=4, the job will run to completion and the
information in jid.marc.conmpc_0000 for increment zero will
usually not be useful, but the information for increments one and
above will contain the proper contact tying relations or mpc’s.
NVSURF Rigid contact surface ID (BCBODY ID) for which the next 4
approach velocity values apply. Leave this entry and the next 4 out
if not applicable. This entry and the next 4 may be repeated as many
times as necessary to define all rigid contact surfaces with approach
velocity values. (Integer; Default = 0)
VELAPP1 Approach velocity in direction 1 of rigid contact surface - used only
(6,1) in increment zero. Requires PARAM,MRCONVER,11 (Real;
Default = 0.0)
VELAPP2 Approach velocity in direction 2 of rigid contact surface - used only
(6,2) in increment zero. Requires PARAM,MRCONVER,11 (Real;
Default = 0.0)

Main Index
 BCPARA 1323
Contact Parameters in SOL 600

Table 8-9 Contact Parameters (continued)

Description, Type and Value (Default is 0 for Integer, 0.0
Name for Real Unless Otherwise Indicated)
VELAPP3 Approach velocity in direction 3 of rigid contact surface - used only
(6,3) in increment zero. Requires PARAM,MRCONVER,11 (Real;
Default = 0.0)
VELAPAN Approach angular velocity about local axis through center of
(6,3) rotation of rigid contact surface - used only in increment zero.
Requires PARAM,MRCONVER,1 (Real; Default = 0.0)
NODSEP If NODSEP is positive, ignore separation of any node that has
touched and separated NODSEP times (corresponds to feature, 31xx
where xx=nodsep).
If NODSEP is negative, NODSEP is the number of separations of a
particular node allowed. If more separations of that node actually
occur, the node is assumed to be separated (corresponds to feature, -
31xx where xx-nodsep).
(Integer between 0 and 99; Default if not entered is 2, corresponds
to feature,3102)
METHOD Flag to select Contact Methods (Character)
NODES Regular 3D contact (Default: node to surface contact)
URF
SEGSM Segment to segment contact with small sliding
ALL
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 bilinear Lagrange
multiplier field for quadratic elements.
2 Augmentation based on a constant Lagrange multiplier
field.
3 Augmentation based on a bilinear Lagrange multiplier
field.
PENALT Augmented Lagrange penalty factor used by the segment to segment
contact algorithm only. (Real > 0; set BCBODY for Default)
AUGDIST Penetration distance beyond which an augmentation will be applied.
Used by the segment to segment contact algorithm only. (Real > 0.0;
set BCBODY for Default)

Main Index
 1324 BCPARA
Contact Parameters in SOL 600

Remarks:
1. (i,j) refers to data block i and field j of the CONTACT model definition option in Marc.
2. Field 2 of the primary line should be left blank or a value of zero should be entered.
3. Only one BCPARA entry should be made. If multiple entries are made, the last will be used.
4. For FTYPE, SOLs 400 and 600 differ as follows. For SOL 400, if friction is entered but FTYPE
is blank, friction is ignored. For SOL 600, if friction is entered but FTYPE is blank COULOMB
friction is used. (FTYPE is reset internally to 2). In addition SOL 400 can only use friction types
0, 6 and 7.

Main Index
 BCPATCH 1325
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

Field Contents
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
 1326 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 used in SOL 101 and SOLs 400 and 700 only.

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

Field Contents
ID Identification 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.

Main Index
 BCPROP 1327
3D Contact Region by Element Properties

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
 1328 BCPROP
3D Contact Region by Element Properties in SOL 600

BCPROP 3D Contact Region by Element Properties in SOL 600

Defines a 3D contact region by element properties. All elements with the specified properties define a
contact body used in SOL 600.

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

Example for Alternate Format:

BCPROP 25 101 THRU 102

Field Contents
ID Identification of a deformable surface corresponding to a BSID value on the
BCBODY entry or if the Case Control BCONTACT = BCPROP is specified. 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.

Main Index
 BCPROP1 1329
3D Contact Region by Element Properties in SOL 700

BCPROP1 3D Contact Region by Element Properties in SOL 700

Defines a 3D contact region by element properties. All elements with the specified properties define a
contact body used in SOL 700 only. This entry includes body depended contact options.

Format:

1 2 3 4 5 6 7 8 9 10
BCPROP1 ID NUMI
IP1 FS1 FD1 DC1 VC1 OPTT1 SFT1 SSF1
IPi FSi FDi DCi VCi OPTTi SFTi SSFi

Example:
BCPROP1 200 1
101 0.04

Field Contents
ID BC id. Identification 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. (Integer > 0; Required)
NUMI Number of property id that will follows. (Integer > 0; Required)
IPi Property id. (Integer > 0; Default)
FSi Static coefficient of friction. The functional coefficient is assumed to be dependent on
– DC ⋅ ν r el
the relative velocity ν rel of the surfaces in contact μ c = FD + ( FS – FD )e . (Real;
Default = 0.0)
FDi Dynamic coefficient of friction. The functional coefficient is assumed to be dependent
– DC ⋅ ν r el
on the relative velocity ν rel of the surfaces in contact μ c = FD + ( FS – FD )e .
(Real; Default = 0.0)
DCi Exponential decay coefficient. The functional coefficient is assumed to be dependent
– DC ⋅ ν r el
on the relative velocity ν rel of the surfaces on contact μ c = FD + ( FS – FD )e .
(Real; Default = 1.0)
VCi Coefficient for viscous friction. This is necessary to limit the friction force to a
maximum. A limiting force is computed F lim = VC ⋅ A cont ⋅ A cont being the area of the
segment contacted by the node in contact. The suggested value for VC is to use the
yield stress in shear VC = σ o ⁄ 3 where σ o is the yield stress of the contacted material.
(Real; Default = 0.0)

Main Index
 1330 BCPROP1
3D Contact Region by Element Properties in SOL 700

Field Contents
OPTTi Optional contact thickness. This applies to shells only. (Real; Default = 0.0)
SFTi Optional thickness scale factor for property ID in automatic contact (scales true
thickness). This option applies only to contact with shell elements. True thickness is the
element thickness of the shell elements. (Real; Default = 1.0)
SSFi Scale factor on default slave penalty stiffness for this property ID whenever it appears
in the contact definition. (Real; Default = 1.0)

Remarks:
1. As many properties may be defined as needed.
2. If FS, FD, DC, and VC are specified they will not be used unless FRIC is set to a negative value
(-1.0) on the BCTABLE or BCONPRG entries.

Main Index
 BCRIGID 1331
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.

Field Contents
BCRGID Unique identification number referenced by a BCBODY1 entry. (Inte-
ger > 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 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.

Main Index
 1332 BCRIGID
Defines a Rigid Contact Body in SOLs 101 and 400

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 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 1333
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
RBID9 -etc.-

Example:

BCRGSRF 1008 35 2

Field Contents
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
 1334 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

Field Contents
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
 BCTABLE 1335
Defines a Contact Table

BCTABLE Defines a Contact Table

Defines a contact table used in SOL 101 and SOLs 400 and 700 only. The BCTABL1 option is the
preferred method to defining contact interactions for SOL 400.

Format: (SOLs 101 and 400 only)

1 2 3 4 5 6 7 8 9 10
BCTABLE ID IDSLAVE IDMAST NGROUP COPTS COPTM
“SLAVE” IDSLA1 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
“MASTERS” IDMA1 IDMA2 IDMA3 IDMA4 IDMA5 IDMA6 IDMA7
IDMA8 IDMA9 ...

Format: (SOL 700 only)

1 2 3 4 5 6 7 8 9 10
BCTABLE ID IDSLAVE IDMAST NGROUP
“SLAVE” IDSLA1 FRIC IGLUE
JGLUE
FK EXP METHOD ADAPT THICK THICKOF PENV
FACT TSTART TEND MAXPAR PENCHK FSF VSF
EROSOP IADJ SOFT DEPTH BSORT FRCFRQ SNLOG
ISYM I2D3D IGNORE SPR MPR VDC SBOPT
SFS SFM SST MST SFST SFMT AUTO
LCID FCM US PSF FA ED INTTYPE

NFLS SFLS IGNOFF FSLIM PYS TDIC CDIST

NFLF SFLF NEN MES TBLCID TBLAB IGAP
FTBID VC SMOOTH FLANGL PENMAX THKOPT SHLTHK
SLDTHK SLDSTF INTTID1 INTTID2
DBID TIDRF TIDNF DBDTH DFSCL NUMINT
THERMAL K FRAD H0 LMIN LMAX CHLM
BC_FLAG ALGO
TFST TFDT FORMULA a b c d

Main Index
 1336 BCTABLE
Defines a Contact Table

1 2 3 4 5 6 7 8 9 10
ERATEN ERATES CT2CN CN DAMP1 DAMP2 DAMP3
“MASTERS” IDMA1 IDMA2 IDMA3 IDMA4 IDMA5 IDMA6 IDMA7
IDMA8 IDMA9 ...

Examples:
BCTABLE 2 3
SLAVE 10 0.2
MASTERS 20 30
SLAVE 20 0.3
MASTERS 10
SLAVE 30 0.2
MASTERS 10

BCTABLE 0 1 2 0

Field Contents

ID Identification number referenced by a BCONTACT Case Control command.

See Remark 5. (Integer; Required)
IDSLAVE Identification number of a BCBODY entry defining the touching body.
(Integer > 0 or blank)
IDMAST Identification number of a BCBODY Bulk Data entry defining the touched
body. (Integer > 0 or blank)
NGROUP Flag to indicate that the continuation entries “SLAVE” and “MASTERS” are
entered or not. Zero means no continuation entries are entered. Any positive
integer means one or more sets of slave/master entries are entered. (Integer;
Default = 1).
COPTS, COPTM, Flag to indicate how slave and master surfaces may contact. See Remark 20.
COPTS1, (Integer; Default = 0) COPTS and COPTM apply to all slave and master
COMPTM1 surfaces on this BCTABLE. To set individual slave/master combination
differently, use COPTS1 and/or COPTM1. Ignored by SOL 700.
“SLAVE” Indicates that this line defines the touching body and its parameters.
IDSLA1 Identification number of a BCBODY Bulk Data entry defining the touching
body. (Integer > 0)
For SOL 700, leaving IDSLA1 blank will result in contact for all elements in
the model. In this case, you are allowed to use ADAPT=YES.
ERROR Distance below which a node is considered touching a body. Default = blank
automatic calculation. See the Bulk Data entry BCPARA, 1313 for more
details. Ignored by SOL 700. (Real)

Main Index
 BCTABLE 1337
Defines a Contact Table

Field Contents

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 and
allows -1.0 to assign different static friction coefficients on properties. See
Remark 2. of BCPROP1. (Real > 0.0 or Integer > 0; Default = 0.0 for SOL400,
Real >-1.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 Slave to Master or from Master to
Slave, for deformable contact bodies. Ignored by SOL 700. ISEARCH is not
necessary in segment-to-segment contact. (Integer; Default = 0)
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 43.

Main Index
 1338 BCTABLE
Defines a Contact Table

Field Contents

1 (Single order search) the searching order is from Slave to Master

2 (Single order search) let the program decide which search order. See
Remark 43.
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 NLGLUE=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 Slave 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.
1 Same as 0 above but with failure after sticking.
2 Glue contact with failure is active for nodes which are initially in
contact. Until failure, tangential motion is inhibited. If IGNOFF is set
to 1 shell thickness offsets are ignored, and the orientation of the shell
surfaces is required such that the outward normals point to the
opposing contact surface. This option is only available with
METHOD=SS1WAY or SS2WAY and AUTO=YES.
3 Same as 0 above but with failure after sticking.
4 Glue contact is active for nodes which are initially in contact but
tangential motion with frictional sliding is permitted. This option is
only available with METHOD=SS1WAY or SS2WAY and
AUTO=YES.
5 Glue contact is active for nodes which are initially in contact. Stress
is limited by the yield condition described in Remark 11. Damage is
a function of the crack width opening. This interface can be used to
represent deformable glue bonds. This option is only available with
METHOD=SS1WAY or SS2WAY and AUTO=YES.

Main Index
 BCTABLE 1339
Defines a Contact Table

Field Contents

6 This option is for use with solids and thick shells only. Tiebreak is
active for nodes which are initially in contact. Failure stress must be
defined for tiebreak to occur. After the failure stress tiebreak criterion
is met, damage is a linear function of the distance C between points
initially in contact. When the distance is equal to CDIST damage is
fully developed and interface failure occurs. After failure, this
contact option behaves as a surface-to-surface contact. This option is
only available with METHOD=SS1WAY or SS2WAY and
AUTO=YES.
7 Dycoss Discrete Crack Model. This option is only available with
METHOD=SS1WAY or SS2WAY and AUTO=YES.
METHOD=SS1WAY is recommended. See Remark 46.
8 This option is similar to JGLUE=6 but works with offset shell
elements. This option is only available with METHOD=SS1WAY or
SS2WAY and AUTO=YES.
9 Discrete Crack Model with power law and B-K damage models. This
option is only available with METHOD=SS1WAY or SS2WAY and
AUTO=YES. METHOD=SS1WAY is recommended. See Remark
47.
10 This option is similar to JGLUE=7 but works with offset of shell
elements. This option is only available with METHOD=SS1WAY or
SS2WAY and AUTO=YES. METHOD=SS1WAY is recommended.
See Remark 46.
11 This option is similar to JGLUE=9 but works with offset of shell
elements. This option is only available with METHOD=SS1WAY or
SS2WAY and AUTO=YES. METHOD=SS1WAY is recommended.
See Remarks 47.
21 Glue contact with failure is active for nodes which are initially in
contact. Failure is based upon force limits for nodes to surface
contact. Only allowed for METHOD=FULL.
22 Glue contact with failure is active for nodes which are initially in
contact. Failure is based upon force limits for nodes only contact.
Only allowed for METHOD=FULL
23 Glue contact with failure is active for nodes which are initially in
contact. This option allows the definition of a resisting stress versus
gap opening for the post failure response. This option can be only
used with METHOD=SS2WAY.
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)

Main Index
 1340 BCTABLE
Defines a Contact Table

Field Contents

“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 or is equal to 0.0, the
default is the BIAS of the BCPARA entry. A nonblank or non-zero entry will
override the BIAS entered on the BCPARA entry. To obtain a near zero value,
enter 1.0E-16. (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)
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 o the softest body are the preferred slave 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 21. (Real;
Default = 0.0)
BGST Maximum tangential stress for breaking glue. See Remark 21. (Real; Default =
0.0)
BGM Exponent for the tangential stress term in deciding if a glue-contact will break.
See Remark 21. (Real; Default = 2.0)
BGN Exponent for the normal stress term in deciding if a glue-contact will break.
See Remark 21. (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 31. for default)

Main Index
 BCTABLE 1341
Defines a Contact Table

Field Contents

AUGDIST Penetration distance beyond which an augmentation will be applied; used by

the segment-to-segment contact algorithm only. (Real > 0, see Remark 32. 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.)
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)

Main Index
 1342 BCTABLE
Defines a Contact Table

Field Contents

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)
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)

Main Index
 BCTABLE 1343
Defines a Contact Table

Field Contents

METHOD Character, Influences the contact type used. See Remark 41. 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
TIEDES: Tied Shell Edge to Surface
TIEDSS: Tied Surface to Surface
TIEDNSO: Tied Nodes to Surface with Offset
TIEDESO: Tied Shell Edge to Surface with Offset
TIEDSSF: Tied Surface to Surface with Failure
TIEDSSO: Tied Surface to Surface with Offset
GENERAL: General Contact Definition
INTERIOR: Interior Contact (see Remarks)
TIEDNSCO: Tied Nodes to Surface Constrained Offset
TIEDESCO: Tied Shell Edge to Surface Constrained Offset
TIEDSSCO: Tied surface to Surface Constrained Offset
SPOTWELD: Spotweld Contact
SPOTWTOR: Spotweld with Torsion Contact
EDGE: Single Edge Contact (Master Body no allowed)
FTRANSC: Force Transducer Constraint
FTRANSP: Force Transducer Penalty
FORMNS: Forming Nodes to Surface
FORM1SS: Forming One Way surface to Surface
FORM2SS: Forming Surface to Surface
DRAWBEAD: Drawbead contact
ADAPT Character, influences the contact type used.
(SOL 700 only) Options are NO or YES.
Default = NO
When ADAPT=YES, the BCBODY entries IDMAi must be defined as:
behav=DEFORM
bsid references a BCPROP
THICK Shell thickness scale factor. (Real > 0.0; Default = 1.0)
(SOL 700 only)
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;
(SOL 700 only) Default = 1.E20)

Main Index
 1344 BCTABLE
Defines a Contact Table

Field Contents

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),
(SOL 700 only) 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.
PENCHK Small penetration in contact search option. If the slave node penetrates more
(SOL 700 only) than the segment thickness times the factor XPENE (specified by
PARAM,DYXPENE), the penetration is ignored and the slave node is set free.
The thickness is taken as the shell thickness if the segment belongs to a shell
element or it is taken as 1/20 of its shortest diagonal if the segment belongs to
a solid element. This option applies to the surface-to-surface contact
algorithms. (Integer) Options are:
1 Check is turned off. (Default)
2 Check is turned on.
3 Check is on but shortest diagonal is used.
FSF Coulomb friction scale factor. The Coulomb friction value is scaled as
(SOL 700 only) μ sv = FSF ⋅ μ c (Real)

VSF Viscous friction scale factor. If this factor is defined then the limiting force
(SOL 700 only) becomes: F lim = VSF ⋅ VC ⋅ A cont (Real)
EROSOP Erosion/Interior node option. (Integer > 0; Default = 1)
(SOL 700 only)
0 Only exterior boundary information is saved.
1 Storage is allocated so that eroding contact can occur.
Otherwise, no contact is assumed after erosion of the corresponding element.
IADJ Adjacent material treatment option for solid elements. (Integer > 0; Default =
(SOL 700 only) 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.
SOFT Soft constraint option: (Integer > 0; Default = 1)
(SOL 700 only) 0 Penalty formulation.

Main Index
 BCTABLE 1345
Defines a Contact Table

Field Contents

1 Soft constraint formulation (same as original Dytran method).

2 Pinball segment-based contact.
4 Constraint approach for FORMING contact option
In the penalty formulation, the interface stiffness is based on the
elastic bulk moduli of the materials.
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.
DEPTH Search depth. (Integer > 0; Default = 2)
(SOL 700 only) A value of 1 is sufficiently accurate for most crash applications, and is much
less expensive. For improved accuracy, the Default = 2.
BSORT Number of time-steps between bucket sorts.
(SOL 700 only) Values of 25-100 are recommended for single-surface contact.
Values of 10-15 are recommended for master-slave contact.(automatic
determination by the algorithm) (Integer > 0; Default = 0)
FRCFRQ Number of time-steps between contact fore updates for penalty contact
(SOL 700 only) formulations. This option can provide significant speed-up of the contact
treatment. If used, values exceeding 3 or 4 are dangerous. Considerable care
must be exercised when using this option, as this option assumes that contact
does not change for FRCFRG time-steps.
(Integer > 0; Default = 1) (force calculations are performed each cycle)
SNLOG Disable shooting node logic in thickness offset contact. With the shooting node
(SOL 700 only) logic enabled, the first cycle that a slave node penetrates a master segment, that
node is moved back to the master surface without applying any contact force..
(Integer > 0; Default = 1)
0 On (advised for crash simulation)
1 Off (sometimes recommended for metalforming calculations or for
contact involving foam materials)
For SOFT=2, this option is ignored.
ISYM symmetry plane option. (Integer > 0; Default = 0)
(SOL 700 only) 0 Off
1 Do not include faces with normal boundary conditions (e.g.,
segments of brick elements on a symmetry plane).
This option is important to retain the correct boundary conditions in the model
with symmetry.
I2D3D Segment searching option. (Integer > 0; Default = 0)
(SOL 700 only) 0 Search 2-D elements (shells) before 3D elements (solids)

Main Index
 1346 BCTABLE
Defines a Contact Table

Field Contents

1 Search 3-D elements (solids) before 2D elements (shells)

IGNORE Ignore initial penetrations. Only active when AUTO=YES. (Integer > 0)
(SOL 700 only)
0 Take default from PARAM,DYCONIGNORE*,<value> (Default)
1 Allow initial penetrations to exist by tracking it
2 Move nodes to eliminate initial penetrations
SPR Option to include the slave side in the NCFORC and the INTFOR interface
(SOL 700 only) force files. (Integer) Options are:
0 Slave side forces not included. (Default)
1 Slave side forces included.
MPR Include the master side in the NCFORC and the INTFOR interface force files.
(SOL 700 only) (Integer) Options are:
0 Master side forces not included (Default)
1 Master side forces included
VDC Viscous damping coefficient in percent of critical. In order to avoid
(SOL 700 only) undesirable oscillation in contact, e.g., for sheet forming simulation, a contact
damping perpendicular to the contacting surfaces is applied. Damping
coefficient ξ = VDC ⁄ 100 ξ wd e.g., VDC = 20. ξ crit is determined in the
following fashion by LS-DYNA. (Real)

massofmaster
ξ crit = 2mw ; m = min ( m slave, m slave )
resp· slavenode
m slave + m slave
w = k ⋅ -------------------------------------- k interface stiffness
m slave ⋅ m slave

SBOPT Segment-based contact options (SOFT=2). (Integer) Options are:

(SOL 700 only) 0 Defaults to 2.
1 Pinball edge-edge contact (not recommended)
2 Assume planer segments (Default)
3 Warped segment checking
4 Sliding option
5 Do options 3 and 4
SFS Scale factor on default slave penalty stiffness. (Real)
(SOL 700 only)
SFM Scale factor on default master penalty stiffness. (Real)
(SOL 700 only)

Main Index
 BCTABLE 1347
Defines a Contact Table

Field Contents

SST Optional thickness for slave surface (overrides true thickness). This option
(SOL 700 only) applies only to contact with shell elements. True thickness is the element
thickness of the shell elements. For the Tied contacts, SST and MST below can
be defined as negative values, which will cause the determination of whether
or not a node is tied to depend only on the separation distance relative to the
absolute value of these thicknesses. See Remark 42. (Real)
MST Optional thickness for master surface (overrides true thickness). This option
(SOL 700 only) applies only to contact with shell elements. True thickness is the element
thickness of the shell elements. For the Tied contacts see SST above. (Real)
SFST Scale factor for slave surface thickness (scales true thickness). This option
(SOL 700 only) applies only to contact with shell elements. True thickness is the element
thickness of the shell elements. (Real)
SFMT Scale factor for master surface thickness (scales true thickness). This option
(SOL 700 only) applies only to contact with shell elements. True thickness is the element
thickness of the shell elements. (Real)
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.
LCID TABLED1 ID giving force versus penetration behavior for RIGID contact. See
(SOL 700 only) also the definition of FCM below. Only allowed and required input when
METHOD is RB1WAY, RB2WAY or RNRB. (Integer)
FCM Force calculation method for rigid contact. Only allowed and required input
(SOL 700 only) when METHOD is RB1WAY, RB2WAY or RNRB. (Integer)
Options are:
1 TABLED1 gives total normal force on surface versus maximum
penetration of any node (RB1WAY only).
2 TABLED1 gives normal force on each node versus penetration of
node through the surface (all rigid body contact types).
3 TABLED1 gives normal pressure versus penetration of node through
the surface (RB1WAY and RB2WAY only).
4 TABLED1 gives total normal force versus maximum soft
penetration. In this case the force will be followed based on the
original penetration point. (RB1WAY only).
US Unloading stiffness for rigid contact. The default is to unload along the loading
(SOL 700 only) curve. This should be equal to or greater than the maximum slope used in the
loading curve. Only allowed input when METHOD is RB1WAY, RB2WAY or
RNRB. (Real)

Main Index
 1348 BCTABLE
Defines a Contact Table

Field Contents

PSF Penalty scale factor (Default = 1.00). Only used for METHOD=INTERIOR.
(SOL 700 only)
FA Activation factor, (Default = 0.10). When the crushing of the element reaches
(SOL 700 only) Fa times the initial thickness the contact algorithm begins to act. Only used for
METHOD=INTERIOR.
ED Optional modulus for interior contact stiffness. Only used for
(SOL 700 only) METHOD=INTERIOR. (Real; Default = 0.0)
INTTYPE Formulation for interior contact. Only used for METHOD=INTERIOR.
(SOL 700 only) (Integer; Default = 1)
1 Recommended for uniform compression. (Default)
2 Designed to control the combined modes of shear and compression.
Works for type 1 brick formulation and type 10 formulation.
NFLS Normal failure stress. JGLUE = 1, 2, 3, 4, 6, 7, 8, 9, 10, 11 or 23. For JGLUE=9
(SOL 700 only) or 11 and NFLS<0, a TABLED ID= - NFLS is referenced defining normal
failure stress as a function of element size. (Real; Required.)
SFLS Shear failure stress. Only for JGLUE = 1, 2, 3, 6, 7, 8, 9, 10, 11 or 23. Optional
(SOL 700 only) input for JGLUE = 4. For JGLUE=9 or 11 and SFLS<0, a TABLED ID= -
SFLS is referenced defining shear failure stress as a function of element size.
(Real; Required)
IGNOFF Include shell thickness option. Only for JGLUE=2 and 23. (Integer; Default =
(SOL 700 only) 0)
0 Shell thickness is included. (Currently not supported for
JGLUE=23.)
1 Shell thickness is ignored.
FSLIM Frictional stress limit. Only optional input for JGLUE=4. (Real > 0; blank)
(SOL 700 only)
PYS Plastic yield stress as defined in Remark 10. Only for JGLUE = 5. (Real > 0;
(SOL 700 only) Required)
TIDC Damage table ID. The damage function is defined by a load curve which starts
(SOL 700 only) at unity for a crack width of zero and decays in some way to zero at a given
value of the crack opening. Only for JGLUE=5. (Integer; Required)
CDIST Only for JGLUE=6, 7, 8, 9, 10 or 11. Critical distance at which the interface
(SOL 700 only) failure is complete for JGLUE=6 or 8. For JGLUE=7 or 10 this is the friction
angle in degrees. For JGLUE=9 or 11, this is the exponent in the damage
model. A positive value invokes the power law, while a negative one, the B-K
model. (Real; Required)

Main Index
 BCTABLE 1349
Defines a Contact Table

Field Contents

NFLF Normal failure force. Only tensile failure, i.e., tensile normal forces, will be
(SOL 700 only) considered in the failure criterion. Only for JGLUE=21 or 22. (Real > 0;
Required)
SFLF Shear failure force. Only for JGLUE=21 or 22. (Real > 0; Required)
(SOL 700 only)
NEN Exponent for normal force. Only for JGLUE=21 or 22. (Real > 0; Default =
(SOL 700 only) 2.0)
MES Exponent for shear force. Failure criterion:
(SOL 700 only)
Failure is assumed if the left side is larger than 1. fn and fs are the normal and
shear interface force. Only for JGLUE=21 or 22. (Real > 0; Default = 2.0)
TBLCID Optional load curve number defining the resisting stress versus gap opening for
(SOL 700 only) the post failure response. This can be used to model the failure of adhesives.
Only for JGLUE=23. (Integer; Default = 0)
TBLAB TABLED1 ID defining airbag thickness as a function of time. Only used when
(SOL 700 only) METHOD=AIRBAG. (Integer > 0; Default = 0.)
IGAP Flag to improve implicit convergence behavior at the expense of creating some
(SOL 700 only) sticking if parts attempt to separate. Outputted contact forces may also be too
small or zero. Only used for prestress analysis (see PRESTRS or SPRBCK).
(Integer > 0; Default = 1.)
1 Apply method to improve convergence.
2 Do not apply method.

Main Index
 1350 BCTABLE
Defines a Contact Table

Field Contents

FTBID TABLEDR ID, giving the coefficient of friction as a function of the relative
(SOL 700 only) velocity and pressure. This option must be used in combination with the
thickness offset option. See the figure. Only used for METHOD=SS1WAY.
(Integer > 0; Default = 0)

p3

p2

p1

υ rel

Friction coefficient, μ , can be a function of relative velocity and pressure.

Specify a flag for the static coefficient of friction, FS, and a TABLED1 ID for
the dynamic coefficient. This option only works with METHOD=SS1WAY
with thickness offsets.
VC Coefficient for viscous friction. This is necessary to limit the friction force to
(SOL 700 only) a maximum. A limiting force is computed:

F lim = VC ⋅ A cont

Acont being the area of the segment contacted by the node in contact. The
suggested value for VC is to use the yield stress in shear VC = σ o ⁄ 3 where σ 0
is the yield stress of the contacted material. (Real > 0.0; Default = 0.0.)
SMOOTH For smooth contact, a smooth curve-fitted surface is used to represent the
(SOL 700) master segment, so that it can provide a more accurate representation of the
actual surface, reduce the contact noise and produce smoother results with a
coarse mesh. This option is only available for METHOD equal to: FULL,
SS1WAY, SS2WAY, FORMNS, FORM1SS, FORM2SS. (Integer; Default = 0.)
0 Not active.
1 Activate smooth contact.

Main Index
 BCTABLE 1351
Defines a Contact Table

Field Contents

FLANGL Angle tolerance in radians for feature lines option in smooth contact. Any edge
(SOL 700 only) with an angle between to contact segments larger than FLANGL will be treated
as a feature line during curve fitting. If blank or 0.0 no line is considered for
surface fitting. (Real > 0.0; Default = 0.0.)
PENMAX Maximum penetration depth Nodes that are penetrated more than PENMAX
(SOL 700 only) released from the contact definition. Definition and default are different for
METHOD. (See tables.) For SOFT=2, this option is ignored.
For AUTO=NO and METHOD=SS2WAY, SS1WAY or FULL, or JGLUE=21
or 22:
Maximum penetration distance. If 0.0 use small penetration search and value
calculated from thickness and XPENE.
For AUTO=YES and METHOD=SS2WAY, SS1WAY, FULL or single surface
contact or ADAPT=YES, or METHOD=GENERAL:
The segment thickness multiplied by PENMAX defines the maximum
penetration allowed (as a multiple of the segment thickness). If 0.0, the default
is 0.4 for all above contacts, except for METHOD=GENERAL for which the
default is 200.0 times the segment thickness. (Real > 0.0; Default = Blank.)

Formula for Release of

PENCHK Element Type Penetrating Nodal Point
0 solid d=PENMAX if an only if PENMAX>0
d=1.e+10 if PENMAX=0
0 shell d=PENMAX if an only if PENMAX>0
d=1.e+10 if PENMAX=0
1 solid d=XPENE*thickness of solid element
1 shell d=XPENE*thickness of shell element
2 solid d=0.05*minimum diagonal length
2 shell d=0.05*minimum diagonal length

Table: Definition maximum penetration depth (d) for AUTO=NO and

METHOD=SS2WAY, SS1WAY or FULL, or JGLUE=21 or 22 (without
thickness).

Main Index
 1352 BCTABLE
Defines a Contact Table

Element Formula for Release of

Contact Type Type Penetrating Nodal Point
AUTO=NO and solid d=XPENE*thickness of solid element
METHOD=SS2WAY,
SS1WAY or FULL
(thickness included)
AUTO=NO and shell d=XPENE*thickness of shell element
METHOD=SS2WAY,
SS1WAY or FULL
(thickness included)
AUTO=YES and solid d=PENMAX*thickness of solid element
METHOD=SS2WAY, [default: PENMAX=0.5]
SS1WAY, FULL or
single surface contact
or ADAPT=YES
AUTO=YES and shell d=PENMAX*(slave thickness+master
METHOD=SS2WAY, thickness) [default: PENMAX=0.4]
SS1WAY, FULL or
single surface contact
or ADAPT=YES
AUTO=NO and single solid d=0.5*thickness of solid element
surface contact
AUTO=NO and single shell d=0.4*(slave thickness+master
surface contact thickness)
METHOD=GENERAL solid d=PENMAX*thickness of solid element
[default: PENMAX=200.0]
METHOD=GENERAL shell d=PENMAX*(slave thickness+master
thickness) [default: PENMAX=200]

Table Criterion for node release for nodal points which have penetrated
too far. Larger penalty stiffnesses are recommended for the contact
interface which allows nodes to be released. For node-to-surface
type (METHOD=FULL) the element thicknesses which contain
the node determines the nodal thickness.
THKOPT Thickness option for contact types for AUTO=NO and METHOD=SS2WAY,
(SOL 700 only) SS1WAY or FULL: (Integer > 0; Default = 0)
0 Default is taken from DYPARAM, LSDYNA, CONTACT.
1 Thickness offsets are included.

Main Index
 BCTABLE 1353
Defines a Contact Table

2 Thickness offsets are not included (old way).

For SOFT=2, this option is ignored.
SHLTHK Define if and only if THKOPT above equals 1. Shell thickness considered in
(SOL 700 only) type surface to surface and node to surface type contact options, where options
1 and 2 below activate the new contact algorithms. The thickness offsets are
always included in single surface and constraint method contact types: (Integer
> 0; Default = 0.)
0 Thickness is not considered.
1 Thickness is considered but rigid bodies are excluded.
2 Thickness is considered including rigid bodies.
For SOFT=2, this option is ignored.
SLDTHK Optional solid element thickness. The value will activate the contact thickness
(SOL 700 only) offsets in the contact algorithms where offsets apply. The contact treatment will
then be equivalent to the case where null shell elements are used to cover the
solid elements.(Real > 0.0; Default = 0.0.)
SLDSTF Optional solid element stiffness. The value overrides the bulk modulus taken
(SOL 700 only) from the material model referenced by the solid element. (Real > 0.0; Default
= 0.0.)
INTTID1 TABLED1 ID which scales the interface stiffness during dynamic relaxation.
This curve must originate at (0,0) at time=0 and gradually increase.
INTTID2 TABLED1 ID which scales the interface stiffness during the transient
calculation. This curve generally has a constant value of unity for the duration
of the calculation if INTTID1 is defined. If INTTID1=0, this curve must
originate at (0,0) at time=0 and gradually increase to a constant value.
DBID ID of DBREG entry. Only used if METHOD=DRAWBEAD. (Integer; Default
(SOL 700 only) = blank)
TIDRF If TIDRF is positive then it defines the TABLED1 ID giving the bending
(SOL 700 only) component of the restraining force, Fbending, per unit draw bead length as a
function of displacement, δ, see Figure 8-4. This force is due to the bending and
unbending of the blank as it moves through the draw bead. The total restraining
force is the sum of the bending and friction components.
If TIDRF is negative then the absolute value gives the TABLED1 ID defining
max bead force versus normalized draw bead length. The abscissa values are
between zero and 1 and is the normalized draw bead length. The ordinate gives
the maximum allowed draw bead, retaining force when the bead is in the fully
closed position. If the draw bead is not fully closed linear interpolation is used
to compute the draw bead force. (Integer; Required when
METHOD=DRAWBEAD)

Main Index
 1354 BCTABLE
Defines a Contact Table

TIDNF TABLED1 ID giving the normal force per unit draw bead length as a function
(SOL 700 only) of displacement, δ, see Figure 8-4. This force is due to the bending of the blank
into the draw bead as the binder closes on the die and represents a limiting
value. The normal force begins to develop when the distance between the die
and binder is less than the draw bead depth. As the binder and die close on the
blank this force should diminish or reach a plateau, see Remarks. (Integer,
Required when METHOD=DRAWBEAD.)
DBDTH Draw bead depth, see Figure 8-4. Necessary to determine correct δ
(SOL 700 only) displacement from contact displacements. (Real; Required when
METHOD=DRAWBEAD.)
DFSCL Scale factor for load curve. This factor scales TABLED1 ID, TIDRF above.
(SOL 700 only) Only used when METHOD=DRAWBEAD. (Real; Default = 1.0)
NUMINT Number of equally spaced integration points along the drawbead. If 0:
(SOL 700 only) Internally calculated based on element size of elements that interact with
drawbead. This is necessary for the correct calculation of the restraining forces.
More integration points may increase the accuracy since the force is applied
more evenly along the bead. Only used when METHOD=DRAWBEAD.
(Integer; Default = 0)
THERMAL Thermal contact option (Integer, default=0):
0 no thermal contact
1 thermal contact
2 thermal friction contact (this option is only available when
METHOD=SS2WAY and AUTO=NO)
K Thermal conductivity of fluid between the contact surfaces. If a gap with a
thickness
k
---------
l gap

exists between the slide surfaces, then the conductance due to thermal
conductivity between the slide surfaces is
k
h cond = --------
-
l ga p

Note that SOL700 calculates based on deformation. Only available when

THERMAL = 1 or 2 (Real, required)

Main Index
 BCTABLE 1355
Defines a Contact Table

FRAD Radiation factor, f, between the slide surfaces

σ
f rad = --------------------------
-
1 1
----- + ----- – 1
ε1 ε2

Where, σ = Stefan Boltzman constant

ε1 = emissivity of master surface

ε2 = emissivity of slave surface

SOL700 calculates a radiant heat transfer conductance

2 2
h rad = f ra d ( T m + T s ) ( T m + T S ) h_rad=f_rad (T_m+T_s )(T_m^2+T_s^2 )

Only available when THERMAL = 1 or 2 (Real, required)

H0 Heat transfer conductance for closed gaps. Use this heat transfer conductance
for gaps in the range

0 ≤ 1 gap ≤ 1 min

Only available when THERMAL = 1 or 2 (Real, required)

LMIN Minimum gap ( l min ) , use the heat transfer conductance defined (H0) for gap
thicknesses less than this value.

Only available when THERMAL = 1 or 2 (Real, required)

LMAX No thermal contact if gap is greater than this value ( l max ) .

Only available when THERMAL = 1 or 2 (Real, required)

CHLM A multiplier used on the element characteristic distance for the search routine.
The characteristic length is the largest interface surface element diagonal. Only
available when THERMAL = 1 or 2 (Real, default=1.0)
BC_FLG Thermal boundary condition flag. Only available when THERMAL = 1 or 2.
(Integer, default=0)
0 Thermal boundary conditions are on when parts are in contact.
1 Thermal boundary conditions are off when parts are in contact.
ALGO Contact algorithm type. Only available when THERMAL = 1 or 2. (Integer,
default=0)
0 Two way contact, both surfaces change temperature due to contact
1 One way contact, master surface does not change temperature due
to contact. Slave surface does change temperature

Main Index
 1356 BCTABLE
Defines a Contact Table

TFST TABLED1 ID for static coefficient of friction as a function of temperature. The

table value multiplies the coefficient value FS. Only available when
THERMAL = 2. (Integer, default=none)
TFDT TABLED1 ID for dynamic coefficient of friction as a function of temperature.
The table value multiplies the coefficient value FD. Only available when
THERMAL = 2. (Integer, default=none)
FORMULA Formula that defines the contact heat conductance as a function of temperature
and pressure. Only available when THERMAL = 2. (Integer, default=none)
Formula h(P) is defined by TABLED1 "a"
=1 "a" defines a table for the contact conductance as a function of
interface pressure.
2 3
Formula h ( ρ ) = a + b ρ + dρ
=2
a TABLED1 ID for the "a" coefficient used in the formula. Only available when
THERMAL = 2. (Integer, default=none).
b TABLED1 ID for the "b" coefficient used in the formula. Only available when
THERMAL = 2. (Integer, default=none).
c TABLED1 ID for the "c" coefficient used in the formula. Only available when
THERMAL = 2. (Integer, default=none).
d TABLED1 ID for the "d" coefficient used in the formula. Only available when
THERMAL = 2. (Integer, default=none).
ERATEN For JGLUE=7, 9, 10 and 11 only. Normal energy release rate (stress*length)
used in damage calculation, see Lemmen and Meijer [2001]. (Real;
default=0.0.)
ERATES For JGLUE=7, 9, 10 and 11 only. Shear energy release rate (stress*length) used
in damage calculation, see Lemmen and Meijer [2001]. (Real; default=0.0.)
CT2CN The ratio of the tangential stiffness to the normal stiffness only for JGLUE=9
and 11. (Real; default = 1.0.)
CN Normal stiffness (stress/length) only for JGLUE=9 and 11. If CN is not given
explicitly, penalty stiffness is used. This optional stiffness should be used with
care, since contact stability can get affected. A warning message with a
recommended time step is given initially. (Real; default=penalty stiffness.)
DAMP1 Opening mode (Mode I - a tensile stress normal to the plane of the crack)
damping force per unit velocity per unit area only for JGLUE=9 and 11. (Real;
default=0.0.)
DAMP2 Sliding mode (Mode II - a shear stress acting parallel to the plane of the crack
and perpendicular to the crack front) damping force per unit velocity per unit
area only for JGLUE=9 and 11. (Real; default=0.0.)

Main Index
 BCTABLE 1357
Defines a Contact Table

DAMP3 Tearing mode (Mode III - a shear stress acting parallel to the plane of the crack
and parallel to the crack front) damping force per unit velocity per unit area
only for JGLUE=9 and 11. (Real; default=0.0.)
“MASTERS” Indicates the start of the list of bodies touched by touching body IDSLA1.
IDMAi Identification numbers of BCBODY Bulk Data entries defining touched
bodies. (Integer > 0)
TPENALT Augmented Lagrange penalty factor for sticking part of friction. (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. (Real ≥ 0.0; Default = 0.0 see Remark 45.)

Remarks:
1. BCTABLE defines surface contact.
2. If BCTABLE is not 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 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 IDSLAVE and IDMAST.
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 IDSLAVE and IDMAST blank, then NGROUP is normally required and
continuation entries are usually expected for NGROUP SLAVE/MASTER combinations.
Exceptions are for SOL 700 self-contact may be designated using a slave IDSLA1 of zero and no
MASTER entry.
5. For SOLs 101 and 400, the BCTABLE with ID=0 will be used in loadcase 0 (similar to the Marc’s
phase 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) adjust the coordinates of all active
nodes, which are the Grid Points on the surface of all deformable BCBODY’s, to remove any
prestressed condition. 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.

Main Index
 1358 BCTABLE
Defines a Contact Table

7. It is not necessary to enter all continuation lines between SLAVE and MASTERS. For example,
if an entry is required on the 4th SLAVE 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.
8. For SOL 700, contact method: TIEDNSCO, TIEDESCO, TIEDSSCO. If this option is set, then
offsets are permitted for these contact types. The Constrained Offset option is a constraint type
formulation. The nodal points in the TIEDNSCO option and the TIEDSSCO may not be
connected to structural nodes, i.e., nodes with rotational degrees-of-freedom, since the rotational
degrees-of-freedom are not affected, which will lead to an instability since the translational
motions due to rotation are imposed on the slave nodes.
9. For SOL 700, contact method: INTERIOR: Define interior contact for foam hexahedral and
tetrahedral elements. Frequently, when foam materials are compressed under high pressure, the
solid elements used to discretize these materials may invert leading to negative volumes and error
terminations. In order to keep these elements from inverting, it is possible to consider interior
contacts within the foam between layers of interior surfaces made up of the faces of the solid
elements. Since these interior surfaces are generated automatically, the property (material) ID’s
for the materials of interest are defined here, prior to the interface definitions. Only one
INTERIOR contact method can be defined per model. The interior penalty is determined by the
formula:
2---
3
SLSFAC ⋅ PSF ⋅ Volume ⋅ ED
K = ---------------------------------------------------------------------------------
-
Min . Thickness

where SLSFAC is the value specified on the DYPARAM,LSDYNA,CONTACT,SLSFAC entry,

volume is the volume of the brick element, E is a constitutive modulus, and min. thickness is
approximately the thickness of the solid element through its thinnest dimension. If ED, is defined
above the interior penalty is then given instead by:
2---
3
Volume ⋅ ED
K = ----------------------------------------------
Min . Thickness

where the scaling factors are ignored. Generally, ED should be taken as the locking modulus
specified for the foam constitutive model.
Caution should be observed when using this option since if the time step size is too large,
instability may result. The time step size is not affected by the use of interior contact.
10. For SOL 700 options JGLUE = 2, 3, and 6 the Glue contact failure criterion has normal and shear
components:
σn  2  σs  2
 --------------
- + -------------- ≥ 1
 NFLS  SFLS

11. For SOL 700 JGLUE = 4, SFLS or FSLIM is required input.

Main Index
 BCTABLE 1359
Defines a Contact Table

12. For SOL 700 option JGLUE = 4, the Glue contact failure criterion has only a normal stress
component:
σn
--------------
-≥1
NFLS

13. For SOL 700 option JGLUE=5, the stress is limited by a perfectly plastic yield condition. For ties
in tension, the yield condition is
2 2
σn + 3 σs
-------------------------------
-≤1
NFLS

For ties in compression, the yield condition is

2
3 σs
------------------
-≤1
NLFS

The stress is also scaled by the damage function which is obtained from the table. For ties in
tension, both normal and shear stress are scaled. For ties in compression, only shear stress is
scaled.
14. For SOL 700 JGLUE=6 or JGLUE=8, damage initiates when the stress meets the failure criterion.
The stress is then scaled by the damage function. Assuming no load reversals, the energy released
due to the failure of the interface is approximately 0.5*S*CDIST, where
2 2
S = max ( σ n, 0 ) + σ s

at initiation of damage. This interface may be used for simulating crack propagation. For the
energy release to be correct, the contact penalty stiffness must be much larger than
MIN ( NFLF, SFLS )
----------------------------------------------------
CDIST

15. For SOL 700 JGLUE = 21 and 22, both NFLF and SFLF must be defined. If failure in only
tension or shear is required then set the other failure force to a large value (1E+10). After failure,
the JGLUE = 21 contact behaves as a nodes-to-surface contact with no thickness offsets (no
interface tension possible) whereas the JGLUE=22 contact stops acting altogether. Prior to
failure, the two contact types behave identically.
16. For SOL 700 JGLUE = 23, Both NFLS and SFLS must be defined. If failure in only tension or
shear is required then set the other failure stress to a large value (1E+10). When used with shells,
contact segment normals are used to establish the tension direction (as opposed to compression).
Compressive stress does not contribute to the failure equation. After failure, this contact option
behaves as a surface-to-surface contact with no thickness offsets. After failure, no interface
tension is possible.
17. For SOL 700, the BCTABLE formats (primary or alternate) shown in the MSC.Nastran 2005 r3
Quick Reference Guide and the MD Nastran 2006 Quick Reference Guide may still be used in
which case PARAM,MRCONVER,11 should not be entered if the “primary” format shown in
these Quick Reference Guides is used.

Main Index
 1360 BCTABLE
Defines a Contact Table

18. Many slave/masters may be entered up to the number specified in Remark 5. A new slave entry
may not begin until the masters from the previous entry are finished (as shown in the example).
The number of master surfaces for any given slave surface is limited by the number specified in
Remark 5., however most GUI’s produce one slave surface and one master surface per
slave/masters pairs.
19. For SOL 400, the entry from TOLID through DISTID, “HHHB” entry and the entry from FK
through NUMINT are not supported.
20. 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.
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.
21. Breaking Glue provides glued contact to all GRID's at their very 1st contact. This kind of glued-
contact will break if

Main Index
 BCTABLE 1361
Defines a Contact Table

(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.
22. For METHOD=FORMNS, FORM1SS and FORM2SS: These contacts are mainly used for metal
forming applications. A connected mesh is not required for the master (tooling) side but the
orientation of the mesh must be in the same direction. These contact types are based on the
AUTO=YES type contacts and consequently the performance is better than the original two
surface contacts.
23. For METHOD=FTRANSC and FTRANSFP. This contact allows the total contact forces applied
by all contacts to be picked up. This contact does not apply any force to the model and will have
no effect on the solution. Only the slave set and slave set type need be defined for this contact
type. Generally, only the first three cards are defined. The force transducer option FTRANSFP,
works with penalty type contact algorithms only, i.e., it does not work with the METHOD=TIED
options. For these latter options, use the FTRANSC option. If the interactions between two
surfaces are needed, a master surface should be defined. In this case, only the contact forces
applied between the slave and master surfaces are kept. The master surface option is only
implemented for the FTRANSFP option and works only with the AUTO=YES contact types.
24. The draw bead is defined two ways:
a. A consecutive list of slave nodes that lie along the bead using BCGRID
b. A set of property ID’s of beams that lie along the draw bead using BCPROP.
25. For straight draw beads only two nodes or a single beam need to be defined, i.e., one at each end,
but for curved beads sufficient nodes or beams are required to define the curvature of the bead
geometry. When beams are used to define the bead, with the exception of the first and last node,
each node must connect with two beam elements. This requirement means that the number of
slave nodes equals the number of beam elements plus one. The integration points along the bead
are equally spaced and are independent of the nodal spacing used in the definition of the draw
bead. By using the capability of tying extra nodes to rigid bodies (see RBE2A or MATD20M)
the draw bead nodal points do not need to belong to the element connectivities of the die and
binder. The blank makes up the master surface. It is highly recommended to use a DBREG
around the drawbead to limit the size of the master surface considered for the draw bead. This will
substantially reduce cost and memory requirements.

Main Index
 1362 BCTABLE
Defines a Contact Table

D, depth of draw bead

δ F = Ffriction + Fbending

Figure 8-4 Drawbead contact model defines a resisting force as a function of drawbead
displacement. The friction force is computed from the normal force in the
drawbead and the given friction coefficient.

26. 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.

27. 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 )

Main Index
 BCTABLE 1363
Defines a Contact Table

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.
28. For near contact:

q = HCV ⋅ ( T A – T B ) +
BNC
HNC ⋅ ( T A – T B ) +
BNL BNL
HNL ⋅ ( TA – TB ) +
4 4
σ ⋅ EMISS ⋅ ( TA – TB ) +
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.
29. 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).
30. Table IDs of tables used on the BCTABLE and the BCBODY entry must be unique.
31. 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 ( S i and S j ), 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
PENALT = -----------------i
L

32. By default, the threshold value of this penetration distance is 0.05 times the default contact
characteristic distance.

Main Index
 1364 BCTABLE
Defines a Contact Table

AUGDIST = 0.05 L

33. Setting SOFT=1 or 2 will cause the contact stiffness to be determined based on stability
considerations, taking into account the time step and nodal masses. This approach is generally
more effective for contact between materials of dissimilar stiffness or dissimilar mesh densities.
34. SOFT=2 is for general shell and solid element contact. This option is available for
METHOD=SS2WAY, SS1WAY, FORM1SS, FORM2SS and also for single surface contact,
airbag and eroding contact. When the AUTO=YES is used, orientation of shell segment normals
is automatic. When AUTO=NO the segment or element orientations are used as input. The
segment-based penalty formulation contact algorithm checks for segments vs. segment
penetration rather than node vs. segment. After penetrating segments are found, an automatic
judgement is made as to which is the master segment, and penalty forces are applied normal to
that segment. The user may override this automatic judgement by using METHOD=SS1WAY or
FORM1SS in which case the master segment normals are used as input by the user.
35. For SOFT=2 option VC and VSF are ignored.
36. For SOFT=2, the SBOPT parameter controls several options. The pinball edge-to-edge checking
is not recommended and is included only for back compatibility. For edge-to-edge checking
setting DEPTH=5 is recommended instead (see Remark 37.) The warped segment option more
accurately checks for penetration of warped surfaces. The sliding option uses neighbor segment
information to improve sliding behavior. It is primarily useful for preventing segments from
incorrectly catching nodes on a sliding surface.
37. For SOFT=2, the DEPTH parameter controls several additional options for segment based
contact. When DEPTH=2 (default), surface penetrations measured at nodes are checked. When
DEPTH=3, surface penetration may also be measured at the edge. This option is useful mainly for
airbags. When DEPTH=5, both surface penetrations and edge-to-edge penetration is checked.
When DEPTH=13, the penetration checking is the same as for DEPTH=3, but the code has been
tuned to better conserve energy. Then DEPTH=23, the penetration checking is similar to
DEPTH=3, but a new algorithm is used to try to improve robustness. The airbag contact has two
additional options, DEPTH=1 and 4. DEPTH=4 activates additional airbag logic that uses
neighbor segment information when judging if contact is between interior and exterior airbag
surfaces. This option is not recommended and is maintained only for backward compatibility.
Setting DEPTH=1 suppresses all airbag logic.
38. For SOFT=2 contact, the MAXPAR has a totally different use. Positive values of MAXPAR are
ignored. If a negative value is input for MAXPAR, the absolute value of MAXPAR will be used
as an assumed time step for scaling the contact stiffness. This option is useful for maintaining
consistent contact behavior of an airbag deployment when a validated airbag is inserted into an
automobile model. For the new run, setting MAXPAR=the negative of the solution time step of
the validated run will cause the airbag contact stiffness to be unchanged in the new run even if the
solution time step of the new run is smaller.
39. For SOFT=2 contact, PENMAX, THKOPT, SHLTHK, SNLOG will be ignored.
40. 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.

Main Index
 BCTABLE 1365
Defines a Contact Table

41. When METHOD option is set to TIEDNS, TIEDES, TIEDESSCO, SPOTWELD, SPOTWTOR
or TIEDSS, these contact definitions are based on constraint equations and will not work with
rigid bodies. However, tied interfaces with the offset options (METHOD = TIEDNSO, TIEDESO
or TIEDSSO) can be used with rigid bodies. Also, it may sometimes be advantageous to use the
RBE2A instead for tying deformable nodes to rigid bodies since in this latter case the tied nodes
may be an arbitrary distance away from the rigid body. BCPROP and BCGRID are only available
for the slave body of BCBODY when METHOD is set to TIEDESO and TIEDESCO.
42. Tying will only work if the surface are near each other. The criteria used to determine whether a
slave node is tied down is that it must be “close”. For shell elements “close” is defined as distance,
δ , less than:

δ 1 = 0.60 ⋅ ( thickness_slave_node + thickness_master_segment )

δ 2 = 0.05 ⋅ min ( master_segment_diagonals )

δ = max ( δ 1, δ 2 )
If a node is further away it will not be tied and a warning message will be printed. For solid
elements the slave node thickness is zero and the segment thickness is the element volume divided
by the segment area; otherwise, the same procedure is used.
If there is a large difference in element areas between the master and slave side, the distance,
δ 2 may be too large and may cause the unexpected projection of nodes that should not be tied. To
avoid this difficulty the slave and master thickness can be specified as negative values on SST and
MST options in which case
δ = abs ( δ 1 )
43. 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
CB1= Min(1/20 of the smallest edge,1/4 of the smallest thickness) of BCBODY ID1
CB2= Min(1/20 of the smallest edge,1/4 of the smallest thickness) of BCBODY ID2
The search order is from lower BCBODY ID1 to higher BCBODY ID2 if CB1<=1.05*CB2.
Otherwise, if CB1>1.05*CB2 the search order is from BCBODY ID2 to BCBODY ID1.
44. Fields ISEARCH, DQNEAR and "BKGL" are not supported in segment to segment contact
analysis.
45. If STKSLP is set to 0.0 (Default), the sticking stiffness K1 is equal to the maximum friction force
( μ ⋅ F NORMAL , 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.
46. JGLUE = 7 or 10 is the Dycoss Discrete Crack Model as described in Lemmen and Meijer [2001].
The relation for the crack initiation is given as

Main Index
 1366 BCTABLE
Defines a Contact Table

max ( σ n, 0 ) 2 σs
----------------------------
- + ------------------------------------------------------------------------------------------ = 1
NFLS SFLS ( 1 – sin ( CDIST ) min ( 0, σ n ) )

47. JGLUE = 9 or 11 is an extension of the Dycoss Discrete Crack Model based on the fracture model
using cohesive materials. See Fiolka and Matzenmiller [2005] and Gerlach, Fiolka and
Matzenmiller [2005]. Failure stresses/peak tractions NFLS and/or SFLS can be defined as
functions of characteristic element length (square root of master segment area) via TABLED1.
This option is useful to get nearly the same global responses (e.g. load-displacement curve) with
coarse meshes compared to a fine mesh solution. In general, lower peak tractions are needed for
coarser meshes.

Reference:
Fiolka, M. and Matzenmiller, A., "Delaminationsberechnung von Faserverbundstrukturen", PAMM
Proc. Appl. Math. Mech. 5, S.393-394 (2005).
Gerlach, S., Fiolka M. and Matzenmiller, A., Modelling and analysis of adhesively bonded joints with
interface elements for crash analysis, 4. LS-DYNA Forum, 20-21, (2005) Bamberg, DYNAmore GmbH,
Stuttgart.
Lemmen, P. P. M. and Meijer, G. J., "Failure Prediction Tool Theory and User Manual," TNO Report
2000-CMC-R0018, (2001).

Main Index
 BCTABLE - Glued Option 1367
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, 200 and SOL 400 for
the permanently-glued or general contact.

Format: (SOLs 101, 103, 105, 107, 108, 109, 110, 111, 112, 200 and 400 only)

1 2 3 4 5 6 7 8 9 10
BCTABLE ID NGROUP COPTS COPTM
“SLAVE” IDSLA1 ERROR CINTERF IGLUE
ISEARCH ICOORD
“FBSH” BIAS SLIDE COPTS1 COPTM1
“MASTERS” IDMA1 IDMA2 IDMA3 IDMA4 IDMA5 IDMA6 IDMA7
IDMA8 IDMA9 ...

Examples:
BCTABLE 101 2 61 61
SLAVE 20 0.002 0.2 1
1
FBSH 0.01 60 60
MASTERS 31 32 33
SLAVE 40 1
MASTERS 51 52 53 54

Field Contents

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 “SLAVE” and “MASTERS” entries in
the continuation lines. (Integer > 0; Required)
COPTS1, COPTM Flag to indicate how slave and master surfaces may contact. See Remark 6. for
the general contact.
“SLAVE” Indicates that this line defines the slave or touching body and its parameters.
IDSLA1 Identification number of a BCBODY Bulk Data entry defining the touching
body. (Integer > 0; Required)

Main Index
 1368 BCTABLE - Glued Option
Defines a Contact Table for Permanently Glued Contact

Field Contents

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, 1313 for more details. (Real)
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 slave (touching) to a master
(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 43. in BCTABLE.
1 (Single order search) the searching order is from Slave to Master
2 (Single order search) let the program decide which search order. See
Remark 43. in BCTABLE.

Main Index
 BCTABLE - Glued Option 1369
Defines a Contact Table for Permanently Glued Contact

Field Contents

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.
BIAS Contact tolerance bias factor. If this field is left blank or is equal to 0.0, the
default is the BIAS of the BCPARA entry. A nonblank or non-zero entry will
override the BIAS entered on the BCPARA entry. To obtain a near zero value,
enter 1.0E-16. (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)
COPTS1, COPTM1 Flag to indicate how individual pair of slave and master contact surfaces may
contact. These two fields override COPTS and COPTM. See Remark 6.
“MASTERS” Indicates the start of the list of bodies touched by touching body IDSLA1.
IDMAi 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,0,NLGLUE, 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 NLGULE 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.
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.

Main Index
 1370 BCTABLE - Glued Option
Defines a Contact Table for Permanently Glued Contact

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 0 (similar to the Marc’s
phase 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) adjust the coordinates of all active
nodes, which are the Grid Points on the surface of all deformable BCBODY’s, to remove any
prestressed condition. 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.
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)

Main Index
 BCTABLE - Glued Option 1371
Defines a Contact Table for Permanently Glued Contact

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.

Main Index
 1372 BCTABLE
Defines a Contact Table in SOL 600

BCTABLE Defines a Contact Table in SOL 600

Defines a contact table in SOL 600.

For heat transfer or thermal contact do not enter parameter PARAM,MRCONVER,11 in the bulk data.
For structural analysis, enter PARAM,MRCONVER,11 if SLAVE lines “FBSH” or beyond are used.

Format:

1 2 3 4 5 6 7 8 9 10
BCTABLE ID IDSLAVE IDMAST NGROUP
“SLAVE” IDSLA1 ERROR FNTOL FRIC CINTERF IGLUE
ISEARCH ICOORD JGLUE TOLID DQNEAR DISTID
“FBSH” FRLIM BIAS SLIDE HARDS COPTS1 COPTM1
“BKGL” BGSN BGST BGM BGN
“HHHB” HCT HCV HNC BNC EMISS HBL
“SEGS” PENALT AUGDIST
“MASTERS” IDMA1 IDMA2 IDMA3 IDMA4 IDMA5 IDMA6 IDMA7
IDMA8 IDMA9 ...

Examples:
BCTABLE 2 3
SLAVE 10 0.2
MASTERS 20 30
SLAVE 20 0.3
MASTERS 10
SLAVE 30 0.2
MASTERS 10

BCTABLE 0 1 2 0

Field Contents

ID Identification number referenced by a BCONTACT Case Control command.

See Remark 6. (Integer; Required)
IDSLAVE Identification number of a BCBODY entry defining the touching body. (Integer
(3,1) [3,1] > 0 or blank)
IDMAST Identification number of a BCBODY Bulk Data entry defining the touched
(5,1) [15,1] body. (Integer > 0 or blank)

Main Index
 BCTABLE 1373
Defines a Contact Table in SOL 600

Field Contents

NGROUP Flag to indicate that the continuation entries “SLAVE” and “MASTERS” are
(2,1) [2,1] entered or not. Zero means no continuation entries are entered. Any positive
integer means one or more sets of slave/master entries are entered. (Integer;
Default = 1).
COPTS1, Flag to indicate how slave and master surfaces may contact. See Remark 10.
COMPTM1 (Integer; Default = 0).
“SLAVE” Indicates that this line defines the touching body and its parameters.
IDSLA1 Identification number of a BCBODY Bulk Data entry defining the touching
(3,1) [3,1] body. (Integer > 0)
ERROR Distance below which a node is considered touching a body. (Real for
(3,2) [3,2] BCTABLE with ID = 0, Real or Integer for BCTABLE with ID > 0). If the
value is an Integer, it is the ID of a TABLED1 or TABL3Di providing error vs
time or other variables. Default = blank automatic calculation of ERROR
without any table dependence. See the Bulk Data entry BCPARA, 1318 for
more details.
FNTOL Separation force or stress (depending BCPARA IBSEP) on above which a node
(3,3) [5,1] separates from a body. Default is maximum residual force. (Real)
FRIC Friction coefficient. If the value is an integer, it is the ID of a TABLED1 or
(3,4) [5,2] TABL3Di providing friction vs time or friction vs other variables. (Real > 0.0
or Integer; Default = 0.0)
CINTERF Interference closure amount, normal to the contact surface. CINTERF > 0,
(3,5) [5,3] designates an overlap between bodies, CINTERF < 0 designates a gap between
bodies. If the value is an integer, it is the ID of a TABLED1 or TABL3Di
providing interference closure vs time or friction vs other variables. (Real or
Integer; Default = 0.0)

Main Index
 1374 BCTABLE
Defines a Contact Table in SOL 600

Field Contents

IGLUE Flag to activate glue option (Integer > 0). Default is 0, no glue option,
(3,7) [3,7]
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 Slave to Master or from Master to
(3,8) [3,8] Slave, for deformable contact bodies. ISEARCH is not supported in segment-
to-segment contact. (Integer; Default = 0)
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 43. in BCTABLE.
1 (Single order search) the searching order is from Slave to Master
2 (Single order search) let the program decide which search order. See
Remark 43. in BCTABLE.
ICOORD Enter 1 to modify the coordinates of a node in contact with a deformable body
(3,9) [3,9] 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)
JGLUE This option is only relevant if the glue option is invoked (IGLUE > 0). Enter 0
(3,10) [3,10] if a node should not separate (Default). Enter 1 to invoke the standard
separation behavior based on the maximum residual force. (Integer; Default
= 0)

Enter 2 to activate breaking glue.

Main Index
 BCTABLE 1375
Defines a Contact Table in SOL 600

Field Contents

TOLID Contact tolerance table ID of a TABLEDi. Used in heat transfer analysis only.
(4,2) [4,2] (Integer; Default = 0 which means no table ID)
DQNEAR Distance below which near thermal contact behavior occurs. Used in heat
(3,3) [3,3] transfer analysis only. Used in heat transfer analysis only. If the value is an
integer, it is the ID of a TABLED1 or TABL3Di providing friction vs time or
friction vs other variables. (Real; or integer; Default = 0.0; which means near
contact does not occur)
DISTID Contact near distance table ID of a TABLEDi. Used in heat transfer only.
(4,3) [4,3] (Integer; Default = 0 which means near contact does not occur) (Integer;
Default = 0 which means no table ID)
“FBSH” Enter character string FBSH if the line with items FRLIM, BAIS, SLIDE,
HARDS is required to change the defaults of any of these values.
FRLIM Friction stress limit. This entry is only used for friction type 6 (Coulomb
[5,4] 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. If the value is an integer, it is the ID of a TABLED1
or TABL3Di providing friction vs time or friction vs other variables. (Real or
integer; Default = 1.0E20)
BIAS Contact tolerance bias. A non-blank entry will override the BIAS entered on
[5,5] the BCBODY entry. (Real value between 1.0E-10 and 1.0; Default = 0.9)
SLIDE Delayed slide off distance. This entry should not be made unless ICOORD ≥ 2
[5,6] (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)
HARDS Hard-soft ratio. This entry is only used if double-sided contact with automatic
[5,7] 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 o the softest body are the preferred slave nodes. (Real; Default = 2.0)
“BKGL” Enter the character string BKGL if the line with items BGST, BGSN, BGM,
BGN is required.
BGSN Maximum normal stress for breaking glue. If the value is an integer, it is the ID
of a TABLED1 or TABL3Di providing friction vs time or friction vs other
variables. See Remark 21. (Real or integer; Default = 0.0)

Main Index
 1376 BCTABLE
Defines a Contact Table in SOL 600

Field Contents

BGST Maximum tangential stress for breaking glue. If the value is an integer, it is the
ID of a TABLED1 or TABL3Di providing friction vs time or friction vs other
variables. See Remark 21. (Real or integer; Default = 0.0)
BGM First exponent for breaking glue. If the value is an integer, it is the ID of a
TABLED1 or TABL3Di providing friction vs time or friction vs other
variables. See Remark 21. (Real or integer; Default = 2.0)
BGN Second exponent stress for breaking glue. If the value is an integer, it is the ID
of a TABLED1 or TABL3Di providing friction vs time or friction vs other
variables. See Remark 21. (Real or integer; Default = 2.0)
“HHHB” Enter the character string HHHB if the line with items HCT, HCV, HNC, etc.
is required.
HCT Contact heat transfer coefficient. If real, the value entered is the contact heat
[7,1]/[8,1] transfer coefficient. If integer, the value entered is the ID of a TABLEMi entry
specifying the contact heat transfer coefficient vs temperature. (Real or Integer;
Default = 0.0 for a heat transfer problem, omit for a structural problem.)
HCV Convection coefficient for near field behavior. If real, the value entered is the
[7,2]/[8,2] near field convection coefficient. If integer, the value entered is the ID of a
TABLEMi entry specifying the near field convection coefficient vs
temperature. (Real or Integer; Default = 0.0 for a heat transfer problem, omit
for a structural problem).
HNC Natural convection coefficient for near field behavior. If real, the value entered
[7,3]/[8,3] is the near field natural convection coefficient. If integer, the value entered is
the ID of a TABLEMi entry specifying the near field natural convection
coefficient vs temperature. (Real or Integer; Default = 0.0 for a heat transfer
problem, omit for a structural problem).
BNC Exponent associated with the natural convection coefficient for near field
[7,4]/[8,4] 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
TABLEMi entry specifying the exponent associated with the near field natural
convection coefficient vs temperature. (Real or Integer; Default = 1.0 for a heat
transfer problem, omit for a structural problem.)
EMISS Emissivity for radiation to the environment or near thermal radiation. If real,
[7,5]/[8,5] the value entered is the emissivity. If integer, the value entered is the ID of a
TABLEMi entry specifying the emissivity vs temperature. (Real or Integer;
Default = 1.0 for a heat transfer problem, omit for a structural problem.)
HBL Separation distance dependent thermal convection coefficient. If real, the value
[7,6]/[8,6] entered is the separation distance dependent thermal convection coefficient. If
integer, the value entered is the ID of a TABLEMi entry specifying the
separation distance dependent thermal convection coefficient. (Real or Integer;
Default = 0.0 for a heat transfer problem, omit for a structural problem).

Main Index
 BCTABLE 1377
Defines a Contact Table in SOL 600

Field Contents

“SEGS” Enter the character string SEGS if segment-to-segment contact is desired (note
that for MSC Nastran 2012 segment-to-segment contact cannot include
friction.)
PENALT Penalty factor (stiffness) used for segment-to-segment contact analysis. (Real;
Default = leave blank, meaning the program will calculate the value)
AUGDIST Penetration distance above which additional penalty stiffness will be added.
(Real; Default = leave blank, meaning the program will calculate the value)
“MASTERS” Indicates the start of the list of bodies touched by touching body IDSLA1.
IDMAi Identification numbers of BCBODY Bulk Data entries defining touched
(4,i) [15,1] bodies. (Integer > 0)

Remarks:
1. BCTABLE defines surface contact.
2. If BCTABLE is not 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 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 IDSLAVE and IDMAST.
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 IDSLAVE and IDMAST blank, then NGROUP is normally required and
continuation entries are usually expected for NGROUP SLAVE/MASTER combinations. An
exception if no contact is desired in increment zero or a particular subcase, fields 1 and 2 of the
primary BCTABLE entry for that subcase are entered, all other fields left blank and no
continuation lines are entered. The no contact condition may be achieved in either of two ways -
set Case Control BCONTACT=ID and enter a matching BCTABLE with that ID in field 2 and all
other fields blank or set BCONTACT=NONE and do not enter BCTABLE for that subcase.
5. The maximum number of slave-master combinations is 99 for versions prior to MSC.Nastran
2005 and 999 for current versions. For MSC.Nastran 2005 r3 and subsequent versions, the limit
is 999.
6. The BCTABLE with ID=0 will be used in “increment 0”. This phase of Marc is purely elastic and
is sometimes used to move rigid contact bodies so that they just touch flexible contact bodies. If
no BCTABLE entries are desired in “increment 0”, do not enter any BCTABLEs with ID=0. In
the examples shown, the first BCTABLE is used in subcase 2 and the second BCTABLE is used
in phase 0.

Main Index
 1378 BCTABLE
Defines a Contact Table in SOL 600

7. The BCTABLE formats (primary or alternate) shown in the MSC.Nastran 2005 r3 Quick
Reference Guide may still be used in which case PARAM,MRCONVER,11 should not be entered
if the “primary” format shown is used.
8. Many slave/masters may be entered up to the number specified in Remark 5. A new slave entry
may not begin until the masters from the previous entry are finished (as shown in the example).
The number of master surfaces for any given slave surface is limited by the number specified in
Remark 5., however most GUI’s produce one slave surface and one master surface per
slave/masters pairs.
9. (i,j) indicates the ith datablock jth field of MARC’s CONTACT TABLE (without tables) history
definition. [i,j] indicates Marc’s Contact Table (with Tables).
10. 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: For flexible bodies, B=6 for both bodies in a contact combination can only be used for
glued contact. If the contact bodies are not glued and both bodies specify B=6, a FATAL
ERROR will be issued. Should this fatal error occur, please choose a different B option and
re-run the analysis.
• = 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)

Main Index
 BCTABLE 1379
Defines a Contact Table in SOL 600

11. 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
When a contact node breaks due to the above criterion, standard contact is activated if it comes
into contact again. If BSGN = 0.0 the first term is ignored. If BGST is zero, the second term is
ignored.
12. If the “SEGS” entry is used, “CTYPE” on BCBODY must also be entered and parameters
PARAM,MRCONVER,11 and PARAM,MRCONTAB,11 must be entered.

Main Index
 1380 BCTABL1
Defines a Contact Table

BCTABL1 Defines a Contact Table

BCTABL1 specifies a list of contact pairs through the BCONECT option for SOL 101, SOL 400 and
SOL 700. This contact table is activated in the BCONTACT Case Control.

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 44

17

BCTABL1 0 23 56

Field Contents
BCID Unique identification number referenced by a BCONTACT Case Control command.

See Remark 3. (Integer ≥ 0; Required)

IDi Identification number of BCONECT entry (Integer > 0; ID1 is required).

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.
3. For SOLs 101 and 400, the BCTABL1 or BCONECT with ID=0 will be used in loadcase 0
(similar to the Marc’s phase 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) adjust the
coordinates of all active nodes, which are the Grid Points on the surface of all deformable
BCBODY1’s, to remove any prestressed condition. To place an entry in any physical loadcase
(SUBCASE or STEP), the BCID must be selected by the Case Control command

Main Index
 BCTABL1 1381
Defines a Contact Table

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.

Main Index
 1382 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.

Field Contents
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)

Main Index
 BCTRIM 1383
Defines the Geometry of a Trimming Curve

Remarks:
1. BCTRIM is referenced by a BCNURBS entry to define the trimming curve of a NURBS for a
rigid contact body.

Main Index
 1384 BDYLIST
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

Field Contents
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. See Additional Topics (p. 515) in the MSC Nastran Reference Manual. 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. See Remark 2.

Main Index
 BDYOR 1385
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

Field Contents
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
 1386 BEADVAR
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

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

Field Contents
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
 BEADVAR 1387
Topography Design Variable

Field Contents
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
 1388 BEADVAR
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
 BEADVAR 1389
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.op2 (with setting PARAM, POST, -1) has topography results (shape change) that
can be viewed by 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.

Main Index
 1390 BEAMOR
CBEAM Entry Default Values

BEAMOR CBEAM Entry Default Values

Defines default values for field 3 and fields 6 through 8 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

Field Contents
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. For p-version CBEAM elements, field 9 contains the value of the built-in twist measured in
radians. The OFFT option cannot be used for p-elements. Otherwise, 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

Main Index
 BEAMOR 1391
CBEAM Entry Default Values

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. (Note: The
character “O” in the table replaces the obsolete character “E”.)

Main Index
 1392 BFRlC
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

Field Contents
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
 BIAS 1393
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

Field Contents
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.

Main Index
 1394 BIAS
MESH Bias Definition

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.
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:

Main Index
 BIAS 1395
MESH Bias Definition

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.
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
 1396 BJOIN

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 N M EP
NF TW

Example:

BJOIN 1 2 SPOTWEL 1.E3 1.E3

D

Field Contents 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.
RIVET Rivet type failure. Real > 0.0 No failure
SN Failure force in tension. Ignored for option Real > 0.0 No failure
TYPE=RIVET.
SS Failure force in shear. Ignored for option Real > 0.0 No failure
TYPE=RIVET.
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).

Main Index
 BJOIN 1397

Field Contents Type Default

N Exponent for normal spotweld force. Ignored for Real 2.0
option TYPE=RIVET
M Exponent for shear spotweld force. Ignored for option Real 2.0
TYPE=RIVET
TF Failure time for nodal constraint set. Real 1.0E20
EP Effective plastic strain at failure. Ignored for option Real 1.0E20
TYPE=RIVET
NF Number of force vectors stored for filtering. Ignored Integer 0
for option TYPE=RIVET. If 0, filter is off.
TW Time window for filtering. Ignored for non-zero option Real Required if
TYPE=RIVET. NF

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. Failure of the spot welds occurs when:
n m
fn fs
-≥1
- + ---------
---------
Sn Ss

where fn and fs are the normal and shear interface force. Component fn is nonzero for tensile
values only.
3. When the failure time, TF, is reached the spot weld becomes inactive and the constrained nodes
may move freely.
4. Spotweld failure due to plastic straining occurs when the effective nodal plastic strain exceeds the
input value ε pfail . This option can model the tearing out of a spotweld from the sheet metal since
the plasticity is in the material that surrounds the spotweld, not the spotweld itself. A least squares
algorithm is used to generate the nodal values of plastic strains at the nodes from the element
integration point values. The plastic strain is integrated through the element and the average value
is projected to the nodes via a least square fit. This option should only be used for the material
models related to metallic plasticity and can result is slightly increased run times. Failures can
include both the plastic and brittle failures.
5. The TYPE=SPOTWELD is a rigid beam that connects the nodal points of the nodal pairs; thus,
nodal rotations and displacements are coupled. The spotwelds must be connected to nodes having
rotary inertias, i.e., beams or shells. If this is not the case, for example, if the nodes belong to solid
elements, use the option TYPE=RIVET.

Main Index
 1398 BJOIN

6. For implicit, TYPE=SPOTWELD this case is treated like a rivet, constraining only the
displacements.
7. Note that the shell elements do not have rotary stiffness in the normal direction and, therefore, this
component cannot be transmitted.
8. BJOIN nodes must not have the same coordinates. Coincident nodes in a spot weld can be handled
by the RBE2D entry.
9. Brittle and ductile failures can be specified. Brittle failure is based on the resultant forces acting
on the weld, the ductile failure is based on the average plastic strain value of the shell elements
which include the spotweld node.
10. Spotwelds, which are connected to massless nodes, are automatically deleted in the initialization
phase and a warning message is printed in the OUT-file.
11. The accelerations of spotwelded nodes are output as zero into the various output request files, but
if the acceleration of spotwelded nodes are required, use either the CSPOT, CFILLER, CBUTT,
CCRSFIL, COMBWLD, or the RBE2D input. However, if the output interval is frequent enough
accurate acceleration time histories can be obtained from the velocity time history by
differentiation in the post-processing phase.
12. 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
 BLDOUT 1399
Defines Bladeout Force Output Information and Mapping Criteria for a Sequential SOL 700 - SOL 400

BLDOUT Defines Bladeout Force Output Information and Mapping

Criteria for a Sequential SOL 700 - SOL 400 Series of
Analysis

Defines bladeout force output information and mapping criteria for a sequential SOL 700 - SOL 400
Bladeout analysis. (This entry is used in SOL 700 and subsequent SOL 400 analysis.)

Format:

1 2 3 4 5 6 7 8 9 10
BLDOUT RID KIND TOUT FILT IFILE MAP TOL MOM
MASS ROFFSET ZOFFSET GID ISET X1 X2 X3
ISLV1 IMAST1 ISVL2 IMAST2 ISVL3 IMAST3 ISLV4 IMAST4
ISLV5 IMAST5 etc.

Example (for the SOL 700 analysis):

BLDOUT 1 1 0.001 500. 2

2.5 .87 .45 4010 22 0. 1. 0.
1 3 2 4

Example (for the SOL 400 analysis):

BLDOUT 1 1 0.001 500. 2 1 .00025 0

2.5 .87 .45 250 22 0. 1. 0.

Field Contents
RID Reserved for future use. (Integer)
KIND Flag indicating how often the forces will be output. See Remark 6. (Integer; Default
= 0)
0 Forces are output at all time points calculated by SOL 700
1 Output forces at a coarsened time interval
2 Output forces at a coarsened time interval with the same area underneath
the force-time curve.
TOUT Approximate output time interval in seconds. The value of TOUT entered may be
adjusted slightly depending on the actual output times from dytran-lsdyna. To use
every nth output point, leave TOUT blank and set FILT to the negative value of the
nth points desired. (Real > 0.0; no Default; only required if KIND = 1 and FILT =
0.0 or blank)

Main Index
 1400 BLDOUT
Defines Bladeout Force Output Information and Mapping Criteria for a Sequential SOL 700 - SOL 400 Series of

FILT Frequency of low-pass filter used to prevent aliasing. (Real; Default = 0.0; only
required if KIND=1)
0.0 No filtering will be performed.
< 0.0 If FILT is negative the output increment will be abs(FILT). For example,
if FILT = -10.0, every 10th time point will be output.
> 0.0 Low pass filtering with a frequency of FILT (Hz) will be performed
IFILE Flag indicating which type of file(s) are used for the output forces. (Integer; Default
= 0)
0 Output on the database
1 An ASCII named bldout.txt will be created (see Appendix B)
2 Both database and ASCII file output
Options 11, 12, 21 and 22 are only available if FILT>0.0. If the plots described below
are desired but no filtering is desired, set FILT to a large value such as 1.0E16.
11 Same as 1 except ASCII time history files of each node with non-zero
forces will be created. These files have the format time, Fvector, Fx, Fy,
Fz in columns which may be imported to spread sheets to make plots.
These files normally have unequally spaced time histories and are
identical the what is produced by dytran-lsdyna. The name of this file is
“thist|grid|code|.txt”. Where |grid| is an 8 digit integer representing the
grid ID and |code| is one of the values in Remark 1.
12 Same as 2 except ASCII time history files of each node with non-zero
forces out will be created
21 Same as 11 except several ASCII time history files of each node with
non-zero forces will be created. The first files have the format time,
Fvector, Fx, Fy, Fz with header. In addition the “thist|grid|code|.txt” file
two additional files will be produced. The first is “eqtim|grid|code|.txt”
which contains equally spaced time histories for the forces at the grid.
The complete time history of the X direction forces is followed by the
complete time history of the Y direction forces and finally the complete
time history of the Z direction forces follows. All forces start at
time=0.0. The third file is named “ffthist|grid|code|.txt” which contains
the filtered output after both forward FFT, low-pass filtering and inverse
FFT’s have been applied. This file also contains the Fx time history
followed by the Fy time history followed by the Fz time history.
22 Same as 21 except the database file is also created.
31 Same as 21 except all ASCII time history files of each node with non-
zero forces will be created. In addition to the files described for the “21”
option, files for the output of the forward FFT in the frequency domain
prior to any filtering will be produced. These files will have the name
“fftfreq|grid|code|.txt”.

Main Index
 BLDOUT 1401
Defines Bladeout Force Output Information and Mapping Criteria for a Sequential SOL 700 - SOL 400

32 Same as 31 except the database file is also created.

MAP Flag indicating how the output forces on the stationary structure will be mapped to
the coarser model. (Integer; Default = 0)
0 If the find grid and coarse grid coordinates do not match within TOL, the
coarse grid element where the projection of the fine grid node is located
will be found and the force will be internally distributed using RBE3’s to
all corner nodes of that element.
1 The closest coarse mesh grid corresponding to the fine grid node with a
particular force will be found and the fine mesh force applied directly to
that coarse mesh node.
TOL Tolerance to decide whether a fine grid node and a coarse grid node are close enough
to be considered at the same location for the SOL 400 analysis and for the SOL 700
analysis it is the value to determine if forces are in the same location or not. (Real;
Default = 1.0E-4)
MOM Flag indicating whether the internal RBE3 transformation of the shroud forces from
the fine grid model to the coarse grid model will include moments or not (Integer;
Default = 1)
0 Do not include moments
1 Include moments
MASS Mass of broken blade (Real; no Default; required for the SOL 700 and the SOL 400
analysis)
ROFFSET Offset of unbalanced mass of the broken blade in the radial direction. (Real; no
Default; required for the SOL 700 and SOL 400 analysis)
ZOFFSET Offset of unbalanced mass of the broken blade in the Z direction of the cylindrical
coordinate system used in the SOL 400 rotordynamics analysis. (Real; no Default;
Required for the SOL 700 and the SOL 400 analysis)
GID Grid ID of the broken blade when it first breaks (Integer; no default; only required
in the SOL 400 analysis, must be a grid on a ROTORG entry, Required for SOL 400
analysis only)
ISET ID of SET3 Bulk Data entry that defines the coarse grid elements or grids that the
blade out shroud forces from the fine grid model can be mapped to (Integer; Default
= 0 which means that no SET3 will be used and the closest elements or grids within
the specified tolerance will be used with no consideration as to whether they are on
the inner portion of the shroud or elsewhere, only required in the SOL 400 analysis,
must be a grid on a ROTORG entry)
X1, X1, X3 Components of the vector, from GID, in the displacement coordinate system of GID,
which is used to define a cylindrical coordinate system centered at GID; see Remark
5. for the UNBALNC entry. (Real; Required; no Default)

Main Index
 1402 BLDOUT
Defines Bladeout Force Output Information and Mapping Criteria for a Sequential SOL 700 - SOL 400 Series of

ISLVi Flag to indicate what type of entity the “slave” surface for contact output i represents
(Integer; no Default; Required only for the SOL 700 execution, see Remark 1.)
IMASTi Flag to indicate what type of entity the “master” surface for contact output i
represents (Integer; no Default; Required only for the SOL 700 execution, see
Remark 1.)

Remarks:
1. ISLVi and IMASTi should only be specified for the slave/master pairs with output to the binout
file using the SPR/MPR flags in BCTABLE or BCONPRP entries. For example, if there are 10
slave/master contact pairs in BCTABLE and if one two of the pairs have non-zero SPR/MPR only
ISLV1, IMAST1, ISLV2 and IMAST2 should be entered on this entry. The following flags are
available
1 = Body represents the broken blade
2 = Body represents the remaining blades in the same blade group as the broken blade
3 = Body represents the portion of the shroud which can make contact with the broken blade
4 = Body represents the portion of the shroud which can contact the remaining blades (and
rubbing will occur)
5 = Body represents a portion of the shaft
99 = Body represents some other portion of the structure than listed above
2. Items marked as SOL 700 may be left blank in the coarse grid model SOL 400 execution.
Similarly, items marked as SOL 400 may be left blank for the fine grid model SOL 700 execution.
3. The FFT option should be used with care because the impacts between the broken blade and the
case sometimes occur quite quickly and last for a short time with relatively long intervals between
impacts. In such cases, the low pass filtering whether using FFT’s or analog filters may not
produce the desired responses.
4. ASCII files that can be plotted with programs such as Microsoft Excel are as follows:

Produced
if IFILT

File ≥ Contents Format

bldthist.txt 11 All untiltered time histories point,time,Fvect,Fx,Fy,Fz from
dytran-lsdyna with titles
(unequal times)
thist*.txt 11 Unfiltered time history from time,Fvect,Fx,Fy,Fz
dytran-lsdyna (unequal times) (1p5e15.7)
eqtim*.txt 21 Unfiltered time history with time,Fx (all points)
equal time spacing time,Fy (all points)
time,Fz (all points)

Main Index
 BLDOUT 1403
Defines Bladeout Force Output Information and Mapping Criteria for a Sequential SOL 700 - SOL 400

Produced
if IFILT

File ≥ Contents Format

(1p2e15.7)
nzero 21 Unfiltered time history Same as thist*.txt
Non-zero amplitudes only
ffthist 21 Filtered time history Same as eqtim*.txt
fftfreq 31 Forces in frequency domain freq(Hz),Fvect,Freal,Fimag
after forward FFT (1p4e15.7)
For bldthis.txt, thist*.txt, nzero*.txt Fvect=sqrt(Fx**2+Fy**2+Fz**2)
For fftfreq*.txt Fvect=sqrt(Freal**2+Fimag**2)

5. If the PBLDOUT datablock is saved in the database using one of the IFILT options, the SOL 700
entry should usually contain a new keyword BLADEOUT to flag the DMAP compiler to generate
DMAP on the fly to accomplish this task. The SOL 700 entry should then be as follows:
SOL 700,129 BLADEOUT for no TABPT and DBDICT output checking
or
SOL 700,129 BLADEPRT in include TABPT and DBDICT output check (see DMAP
below)
An alternate is to insert the following DMAP before the CEND entry and leave out the
BLADEOUT keyword:
COMPILE IFPS $
ALTER 'TOPTAB'(2) $
FILE GEOM3K=OVRWRT $
IFPX='DBALL' $
TDBX='MASTER'
ALTER 'DOSHR'(3),'DOSHR'(3) $
IF ( CWELD=-1 OR CWSEAM=-1 OR CSEAM=-1 OR CFAST=-1 OR
DOSHR OR BAROFF OR BEMOFF OR BCBODY=-1
) GP1 IGEOM1.5,IGEOM2.6,,,,,,CASEXX,/
XGPL,XEQEXIN,XGPDT,XCSTM,XBGPDT,XSIL,,GEOM3K,,/
S,N,XLUSET/0/0 $
EQUIVX GEOM3K/PBLDOUT/ALWAYS $
TABPT PBLDOUT/ $
DBDICT $
EXIT $
The user should not use both approaches – either enter the BLADEOUT keyword and do not enter
the above DMAP or enter the DAMP and leave out the BLADEOUT keyword. If additional dmap
is desired, the second approach should be used and the BLADEOUT keyword should not be
entered. (CWSEAM is no longer supported.)

Main Index
 1404 BLDOUT
Defines Bladeout Force Output Information and Mapping Criteria for a Sequential SOL 700 - SOL 400 Series of

6. Sometimes it is desirable for the implicit analysis to have a coarser time step than the explicit
analysis, sometimes as large as a factor of 100 to 1000. One method to do this uses the “equivalent
impulse method” which generates an approximate equivalent force time history by computing the
area underneath the force-time history curve in the explicit run and then averaging the area over
a larger time step in the implicit run.
As shown in figures below, the force time history area is equivalent between two different time
steps. If the time steps of implicit and explicit analyses are not varying, the equivalent force can
be calculated by averaging forces in the implicit time step.

Main Index
 BLSEG 1405
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

Field Contents
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)

Main Index
 1406 BLSEG
Boundary Line Segments

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.
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 1407
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

Field Contents
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, 1069 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
 1408 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

Field Contents
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, 1069 for a list of these entries.

Main Index
 BNDFIX1 1409
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
 1410 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

Field Contents
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, 1069 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 1411
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

Field Contents
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)

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.

Main Index
 1412 BNDFRE1
Free Boundary Degrees-of-Freedom, Alternate Form of BNDFREE Entry

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, 1069 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
 BNDGRID 1413
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

Field Contents
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, 1069 for a list of these entries.

Main Index
 1414 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

Field Contents
ID Element ID of the bolt. (Integer; Required; no Default)
GRIDC Control GRID ID where forces or displacements are applied. (Integer; no Default;
Required)
TOP Enter the character string TOP to define the start of the entry that defines all of the
grids at the “top” of the bolt intersection with the structure. (Integer; no Default)
GT1, GT2, etc. Grid IDs of the grid points at the top of the bolt intersection. (Integer; no Default)
BOTTOM Enter the character string BOTTOM to define the start of the entry that defines all
of the grids at the “bottom” of the bolt intersection with the structure (do not enter
the ID for GRIDC). (Integer; no Default)
GB1, GB2, etc. Grid IDs of the grid points at the bottom of the bolt intersection. (Integer; no
Default)

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.

Main Index
 BOLT 1415
Defines the Multi-Point Constraints for a Bolt

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.
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 SPC or 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 SPC or SPC1 includes control grid and any other additional desired
SPC requirements.

Main Index
 1416 BOLT
Defines the Multi-Point Constraints for a Bolt

17. The BOLT may also be used in SOL101 and SOL103. In this case PARAM, AUTOMSET, YES
is recommended.

Main Index
 BOUTPUT 1417
Output for Slideline Contact

BOUTPUT Output for Slideline Contact

Defines slave 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

Field Contents
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 Slave node numbers for which output is desired. (Integer > 0)
INC Grid point identification number increment. See Remark 1. (Integer or blank)

Main Index
 1418 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
 BRKSQL 1419
Specifies Data for Brake Squeal Calculations In SOL 600

BRKSQL Specifies Data for Brake Squeal Calculations In SOL 600

Specifies data for brake squeal calculations in SOL 600 only.

Format:

1 2 3 4 5 6 7 8 9 10
BRKSQL METH AVSTIF GLUE ICORD
R1 R2 R3 X Y Z
NASCMD

RCFILE

Example:

BRKSQL 1 5.34E6
0.0 0.0 1.0 2.0 3.0 4.0
tran
nastb

Field Contents
METH Method flag corresponding to the type of brake squeal calculations to be performed.
(Integer; Default = 1)

0 = Performs brake squeal calculations before any nonlinear analysis has taken
place (corresponds to Marc feature, 4302).

1 = Performs brake squeal calculations after all nonlinear load cases (corresponds
to Marc feature, 4304).

-1 = Same as ID=0 except it corresponds to Marc feature, 4301 (not recommended).

AVSTIF Approximate average stiffness per unit area between the pads and disk.
Corresponds to Marc’s PARAMETERS fifth datablock, field 1. This value is also
known as the initial friction stiffness in Marc Volume C documentation. AVSTIF is
used as a penalty contact stiffness for brake squeal, 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; no Default. Required field)
GLUE Flag specifying whether MPC for non-pad/disk surfaces with glued contact are
used or ignored. A value of 0 means ignore the MPC; a value of 1 means include
the MPCs. See Remark 6. (Integer; Default = 1)

Main Index
 1420 BRKSQL
Specifies Data for Brake Squeal Calculations In SOL 600

Field Contents
ICORD Flag indicating whether coordinates are updated or not. A value of 0 means
coordinates are not updated. A value of 1 means coordinates are updated using the
formula Cnew=Corig+Defl where Cnew are updated coordinates, Corig are
original coordinates, and Defl are the final displacements from last Marc increment.
(Integer; Default = 0)
R1 X direction cosine (basic coord system) of axis of rotation; corresponds to Marc
ROTATION A second datablock. (Real; no Default. Required field)
R2 Y direction cosine (basic coord system) of axis of rotation; corresponds to Marc
ROTATION A second datablock
R3 Z direction cosine (basic coord system); corresponds to Marc ROTATION A
second datablock. (Real; no Default. Required field)
X X coordinate in basic coord system of a point on the axis of rotation; corresponds
to Marc ROTATION A third datablock. (Real; no Default. Required field)
Y Y coordinate in basic coord system of a point on the axis of rotation; corresponds
to Marc ROTATION A third datablock. (Real; no Default. Required field)
Z Z coordinate in basic coord system of a point on the axis of rotation; corresponds
to Marc ROTATION A third datablock. (Real; no Default. Required field)
NASCMD Name of a command to run Nastran (limited to 64 characters) -- used in conjunction
with the CONTINUE options on the SOL 600 entry. The full path of the command
to execute Nastran should be entered. Enter the string entirely in lower case. The
string will be converted to lower case. See Remark 2. (Character; Default=nastran)
RCFILE Name of an RC file to be used with a secondary Nastran job (limited to 8 characters)
-- used in conjunction with the CONTINUE options on the SOL 600 entry. An
extension of “.rc” will automatically be added. Enter the string entirely in lower
case. See Remark 2. (Character; Default=nastb.rc)

Remarks:
1. This entry is used to calculate complex eigenvalues for brake squeal using unsymmetric stiffness
friction matrices calculated by Marc. Options exist to obtain the unsymmetric stiffness matrices
using the undeformed geometry (initial contact) or after all specified nonlinear subcases.
2. SOL 600 performs brake squeal calculations, using the following approach. The main (original)
Nastran job with input file jid.dat or jid.bdf spawns Marc just as it does for any other SOL 600
job. Marc calculates unsymmetric friction stiffness matrices that are saved on a file (jid.marc.bde
with associated file jid.marc.ccc). The primary Nastran job then creates input data for a second
Nastran job (jid.nast.dat) to use the unsymmetric stiffness matrices in an complex eigenvalue
extraction. The primary Nastran job spawns a second Nastran job to calculate the complex
eigenvalues. The complex eigenvalues and eigenvectors are found in jid.nast.f06, jid.nast.op2,
etc.

Main Index
 BRKSQL 1421
Specifies Data for Brake Squeal Calculations In SOL 600

NASCMD is the name of the command to execute the secondary Nastran job. NASCMD can be
up to 64 characters long and must be left justified in field 2. The sting as entered will be used as
is - except that it will be converted to lower case regardless of whether it is entered in upper or
lower case.
RCFILE is the name of an RC file to be used for the secondary Nastran job. Normally it should
be similar to the RC file used for the primary run except that additional memory will normally be
necessary to calculate the complex eigenvalues and batch=no should also be specified for Linux
systems. RCFILE is limited to 8 characters and an extension of “.rc” will be added automatically.
This entry will be converted to upper case in Nastran but will be converted to lower case before
spawning the complex eigenvalue run. This RC file must be located in the same directory as the
Nastran input file. This entry is the same as specifying PARAM,MRRCFILE. Only one or the
other should be used.
3. MPCs are produced for contact surfaces with glued contact. DMIGs are produced for contact
surfaces without glued contact. The brakes and drums should not use glued contact; other regions
of the structure can used glued contact.
4. The continuation lines may be omitted if defaults are appropriate.
5. When a BRKSQL entry is used, PARAM,MRMTXNAM and PARAM,MARCFIL1 should not
be entered.
6. When brake squeal matrices are output by Marc, unsymmetric friction stiffness matrices are
output for non-glued contact surfaces. For surfaces with glued contact, MPCs are output. The
GLUE flag signals SOL 600 to look for these MPCs and combine them with other MPCs that
might be in the model using MPCADD, or if no MPCs were originally used to add the MCPs due
to glued contact. Glued contact surfaces may not be used for the disk-rotor interface. If IGLUE
is zero or blank, the MPCs for glued contact in the Marc brake squeal bde file (if any) will be
ignored. Sometimes, Marc puts out MPCs with only one degree-of-freedom defined. Such MPCs
will be ignored; otherwise Nastran will generate a fatal error.
7. If METH=1, a Marc t19 file will be produced.
8. The names NASCMD and RCFILE must be entered in small fixed field and start in column 9 (i.e.,
left justified in the field).
9. The Nastran input file name used for a brake squeal analysis may only contain lower case letters
and the underscore and/or dash characters.
10. Brake squeal is not available with DDM (parallel processing). Do not enter a PARAMARC when
using the BRKSQL entry.

Main Index
 1422 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

Field Contents
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, 1069 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
 BSET1 1423
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

Field Contents
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, 1069 for a list of these entries.

Main Index
 1424 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.

Main Index
 BSQUEAL 1425
Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

BSQUEAL Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

Defines data for brake squeal calculations involving one wheel (Primary Format) or multiple wheels
(Alternate Format) as well as other rotating or stationary sliding objects used in SOLs 400 and 600.

Primary Format (One Wheel, SOL 400 and SOL 600):

1 2 3 4 5 6 7 8 9 10
BSQUEAL ID OMETH AVSTIF BSONLY IGLUE ICORD
RX RY RZ X Y Z
NASCMD

RCFILE

Alternate Format (Multiple Wheels, SOL 600 Only):

1 2 3 4 5 6 7 8 9 10
BSQUEAL ID OMETH NGROUP ICORD ITYPE BSONLY
“BODY” ID1 ID2 AVSTIF T(AVSTIF)

IVEC IDRF1 IDRF2 IGLUE

RX1 RY1 RZ1 X1 Y1 Z1
RX2 RY2 RZ2 X2 Y2 Z2
“BODY” ID1 ID2 AVSTIF T(AVSTIF)

IVEC IDRF1 IDRF2 IGLUE

RX1 RY1 RZ1 X1 Y1 Z1
RX2 RY2 RZ2 X2 Y2 Z2
NASCMD

RCFILE

Example, Primary Format (SOL 400):

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

Example, Primary Format (SOL 600):

1 2 3 4 5 6 7 8 9 10
BSQUEAL 1.0 5.34E6
0.0 0.0 1.0 2.0 3.0 4.0

Main Index
 1426 BSQUEAL
Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

1 2 3 4 5 6 7 8 9 10
nastran
nastb.rc

Example, Alternate Format (SOL 600):

1 2 3 4 5 6 7 8 9 10
BSQUEAL 1.0 2 1 1
BODY 2 3 60000. 0
0 1
0.0 0.0 1.0 10.0 10.0 25.0
0.0 0.0 -1.0 10.0 10.0 30.0
BODY 6 8 1.0 5
0 110 120 1

nastran
nastb.rc

Field Contents
ID Identification number of a corresponding BSQUEAL Case Control command
(Integer > 0). Ignored by SOL 600.
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., for SOL 600 the
value must be 0.0 or 1.0, Remark 11.)
NGROUP Number of pairs of contact bodies (Integer > 0; Default = 1)
ICORD Flag indicating whether coordinates are updated or not. A value of 0 means
(SOL 600 coordinates are not updated. A value of 1 means coordinates are updated using the
Only) formula Cnew=Corig+Defl where Cnew are updated coordinates, Corig are original
coordinates, Defl are the final displacements from last Marc increment. (Integer;
Default = 0)
ITYPE Flag determining type of analysis. See Figure 8-5 and Figure 8-6 (Integer;
(SOL 600 Default = 1)
Only) 1 Brake squeal
2 Complex engenvalue analysis following general sliding contact analysis.
BSONLY Brake-Squeal-Only flag to control whether or not to continue nonlinear iterations
(SOL 400 after brake squeal analysis is performed. BSONLY=YES means to perform brake
Only) squeal analysis only and exit nonlinear iteration immediately afterwards;
BSONLY=NO means to continue nonlinear analysis. (Character; Default = YES)

Main Index
 BSQUEAL 1427
Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

Field Contents
“BODY” Character string that signals the start of a pair of contact bodies for which instability
calculations are to be made (Character; Required)
ID1 BCBODY ID of the first contact body. (Integer > 0; no Default; bcbody id1 must
exist)
ID2 BCBODY ID of the second contact body. (Integer > 0; no Default; bcbody id2 must
exist)
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; no Default;
Required field)
T(AVSTIF) Table ID of a TABL3Di providing temperature or spatial variation of the average
stiffness (Integer; Default = 0 which means FC is constant)
IVEC Flag specifying whether friction vector at center of master contact body is in the same
direction as that of the slave nodes. (Integer; Default = 0)
0 In same direction
1 Slave vector is in tangential direction
IDRFi ID of a matching RFORCE entry (if any) for body 1 or 2. (Integer; Default = 0, which
(SOL 600 means this body is not rotating)
Only)
IGLUE Flag specifying whether MPC’s for non-pad/disk surfaces with glued contact are
(SOL 600 used or ignored. A value of 0 means ignore the MPC’s, a value of 1 means include
Only) the MPC’s. See Remarks 12. and 14. (Integer; Default = 1)
RXi X direction cosine (basic coord system) of axis of rotation for body i if IDRFi is zero
or blank (Real; or blank)
RYi Y direction cosine (basic coord system) of axis of rotation for body i if IDRFi is zero
or blank (Real; or blank)
RZi Z direction cosine (basic coord system) of axis of rotation for body i if IDRFi is zero
or blank (Real; or blank)
Xi X coordinate in basic coord system of a point on the axis of rotation for body i if
IDRFi is zero or blank (Real; or blank)
Yi Y coordinate in basic coord system of a point on the axis of rotation for body i if
IDRFi is zero or blank (Real; or blank)
Zi Z coordinate in basic coord system of a point on the axis of rotation for body i if
IDRFi is zero or blank (Real; or blank)

Main Index
 1428 BSQUEAL
Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

Field Contents
NASCMD Name of a command to run Nastran (limited to 64 characters) - used in conjunction
(SOL 600 with the CONTINUE options on the SOL 600 statement. The full path of the
Only) command to execute Nastran should be entered. Enter the string entirely in lower
case. (Character; Default = nastran) If the string exceeds 8 characters, do not enter
this string using free-field also see Remark 9.
RCFILE Name of a RC file to be used with a secondary Nastran job (limited to 8 characters)
(SOL 600 - used in conjunction with the CONTINUE options on the SOL 600 statement. An
Only) extension of “.rc” will automatically be added. Enter the string entirely in lower case.
(Character; Default=nastb.rc) If the string exceeds 8 characters, do not enter this
string using free-field also see Remark 9.

Retained node

Tied node

Tied node

Tangential vector
Vector at retained node is the same as at tied node

rotation circle

Figure 8-5 Vectors of frictional stiffness at tied and retained node.

Main Index
 BSQUEAL 1429
Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

BODY 1

BODY 2

Sliding Vector User Defines

Figure 8-6 Sliding model

Remarks:
1. This entry is used to perform multiple-body brake squeal analysis or other contact with friction
sets of bodies using unsymmetric stiffness friction matrices.
2. One or more pairs of bodies may be specified. Each pair of bodies is described by the four lines
beginning with the header “BODY”. For example, there may be one rotating body, such as brake
disk or rotor, and one contact body or bodies, such as brake pad under each “BODY” keyword.
There may be other bodies or parts in the assembly.
3. 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.
4. Entries ICORD, ITYPE, IDBFi, IGLUE, NASCMD and RCFILE are used by SOL 600 only.
5. Entry BSONLY is used by SOL 400 only.
6. Brake squeal is not available with segment-to-segment contact.

SOL 400 Only

7. 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.
8. User subroutine UBSQUEAL is available using the BCONUDS entry.

Main Index
 1430 BSQUEAL
Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

SOL 600 Only

9. SOL 600 performs brake squeal calculations as follows. The main (original) Nastran job with
input deck jid.dat or jid.bdf spawns Marc just as done for any other SOL 600 job. Marc calculates
unsymmetric friction stiffness matrices which are saved on a file (jid.marc.bde with associated
file jid.marc.ccc). The primary Nastran job then creates input data for a second Nastran job
(jid.nast.dat) to use the unsymmetric stiffness matrices in an complex eigenvalue extraction. The
primary Nastran job spawns a second Nastran job to calculate the complex eigenvalues. The
complex eigenvalues and eigenvectors are found in jid.nast.f06, jid.nast.op2, etc.
NASCMD is the name of the command to execute the secondary Nastran job. NASCMD can be
up to 64 characters long and must be left justified in field 2. The sting as entered will be used as
is - except that it will be converted to lower case regardless of whether it is entered in upper or
lower case. RCFILE is the name of an RC file to be used for the secondary Nastran job. Normally
it should be similar to the RC file used for the primary run except that additional memory will
normally be necessary to calculate the complex eigenvalues and batch=no should also be
specified. RCFILE is limited to 8 characters and an extension of “.rc” will be added
automatically. This entry will be converted to upper case in Nastran but will be converted to
lower case before spawning the complex eigenvalue run. This RC file must be located in the same
directory as the Nastran input file. This entry is the same as specifying PARAM,MRRCFILE.
Only one or the other should be used.
10. OMETH can only be one of the following two values in SOL 600.
0.0=Perform brake squeal calculations before any nonlinear analysis has taken place
1.0=Perform brake squeal calculations after all nonlinear load cases
11. Options exist to obtain the unsymmetric stiffness matrices using the undeformed geometry (initial
contact) or after all specified nonlinear subcases.
12. MPC’s are produced for contact surfaces with glued contact. DMIG’s are produced for contact
surfaces without glued contact. The brakes and drums may not use glued contact, other regions
of the structure can used glued contact.
13. When the BSQUEAL entry is used, PARAM,MRMTXNAM and PARAM,MARCFIL1 should
not be entered.
14. When brake squeal matrices are output by Marc, unsymmetric friction stiffness matrices are
output for non-glued contact surfaces. For surfaces with glued contact, MPC’s are output. The
GLUE flag signals SOL 600 to look for these MPC’s and combine them with other MPC’s that
might be in the model using MPCADD, or if no MPC’s were originally used to add the MCP’s.
due to glued contact. Glued contact surfaces may not be used for the disk-rotor interface. If
IGLUE is zero or blank, the MPC’s for glued contact in the Marc brake squeal bde file (if any)
will be ignored. Sometimes, Marc puts out MPC’s with only one degree-of-freedom defined.
Such MPC’s will be ignored otherwise Nastran will generate a fatal error.
15. The names NASCMD and RCFILE must be entered in small fixed field and start in column 9 (i.e.
left justified in the field).
16. The Nastran input file name used for a brake squeal analysis may only contain lower case letters
and the underscore and/or dash characters.
17. Brake squeal is not available with DDM (parallel processing). Do not enter a PARAMARC when
using the BSQUEAL entry.

Main Index
 BSQUEAL 1431
Specifies Data for Brake Squeal Analysis Using SOLs 400 and 600

18. The Bulk Data entry BRKSQL is the alternate format in SOL 600 when there is only one body.

Main Index
 1432 BSURF
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

Field Contents
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 600 and 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, 600, 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.

Main Index
 BSURF 1433
Contact Body or Surface

5. Only one kind of entry (BSURF, BCBOX, BCPROP, or BCMATL) may be used to define a
particular deformable surface.
6. For SOLs 600 and 700, Format 1 and the Alternate Format cannot be mixed for a particular
BSURF entry.
7. For SOLs 600 and 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
 1434 BWIDTH
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

Field Contents
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
 BWIDTH 1435
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
 1436 MSC Nastran Quick Reference Guide
Frequency-Dependent Acoustic Absorber Element

Entries CA - CM MSC Nastran Quick Reference Guide

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

Field Contents
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 8-7.
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
 CAABSF 1437
Frequency-Dependent Acoustic Absorber Element

G2 G3

G1

G2
G1 G4

G1
G1
G3

G2
Figure 8-7 Four Types of CAABSF Elements

Main Index
 1438 CACINF3
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

Field Contents
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.

Main Index
 CACINF4 1439
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

Field Contents

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.

Main Index
 1440 CAERO1
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

Field Contents
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
 CAERO1 1441
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 8-8.
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 8-8 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
 1442 CAERO2
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.

Field Contents
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
 CAERO2 1443
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
 1444 CAERO3
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.

Field Contents
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
LISTC2 they 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 8-9). 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
 CAERO3 1445
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 8-9 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
 1446 CAERO4
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

Field Contents
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
 CAERO4 1447
Aerodynamic Macro-Strip Element Connection

zelem
1 yelem

xaero = xelem
Figure 8-10 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
 1448 CAERO5
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

Field Contents
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Λ = 1.0).
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
 CAERO5 1449
Aerodynamic Panel Element Configuration

zelem
1 yelem
Λ
4

3
2

xaero = xelem
Figure 8-11 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 1⁄2
C 1 = m ⁄ ( m – sec Λ )
4. 2
4 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
 1450 CAERO5
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

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 8-12 CAERO5 I and J Thickness Integral Definitions

Main Index
 CAERO5 1451
Aerodynamic Panel Element Configuration

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
 1452 CAMPBLL
Campbell Diagram Parameters

CAMPBLL Campbell Diagram Parameters

Specifies the parameters for Campbell diagram generation.

Formats:

1 2 3 4 5 6 7 8 9 10
CAMPBLL CID VPARM DDVALID TYPE

Examples:
CAMPBLL 10 SPEED 100 FREQ

Field Contents
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’.

Remarks:
1. CAMPBLL is only supported in SOL 107 (Not in SOL 110).

Main Index
 CAXIFi 1453
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

Field Contents
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
 1454 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

Field Contents
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.
Z-element
Y-basic
G2
n

G3

G1
X-basic
θ -element R-element

Main Index
 CBAR 1455
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

Field Contents
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 8.
(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 8.

Main Index
 1456 CBAR
Simple Beam Element Connection

Field Contents
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 8-13). 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 combined with offsets are not
allowed for SOL 600. Pin flags are not allowed in SOL 700.
Components of offset vectors w a and w b , respectively (see Figure 8-13) 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 7.
and 8. (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. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Figure 8-13 and Figure 8-14 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 8-13 CBAR Element Geometry with Offsets

Main Index
 CBAR 1457
Simple Beam Element Connection

v x elem

Plane 1
y elem End b
GB

Plane 2

End a
GA z elem

Figure 8-14 CBAR Element Geometry without Offsets

3. Figure 8-15 and Figure 8-16 define the elemental force and moment sign convention.

y v1

M 1a M 1b
T
x
Fx T
a Plane 1 b

v1

Figure 8-15 CBAR Element Internal Forces and Moments (x-y Plane)

z v2

M 2a M2 b

Plane 2

v2

Figure 8-16 CBAR Element Internal Forces and Moments (x-z Plane)

4. The continuation may be omitted if there are no pin flags or offsets.

5. 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
 1458 CBAR
Simple Beam Element Connection

6. See Grid Point and Coordinate System Definition (p. 33) in the MSC Nastran Reference Manual
for a definition of coordinate system terminology.
7. Offset vectors are treated 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.
• 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 the enhanced method is used.
• 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.
8. 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

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

Main Index
 CBAR 1459
Simple Beam Element Connection

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”.)
9. For SOL 600, the BIT field is ignored unless param,MAROFSET is 1 or 2. An extra flag
10. For SOL 700, the BIT field is ignored and a warning is issued.
11. For RC network solver in thermal analysis, the G0, OFFT, PA, PB, W1A, W2A, W3A, W1B,
W2B and W3B are ignored.

Main Index
 1460 CBARAO
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.

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

Field Contents
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.

Main Index
 CBARAO 1461
Auxiliary Output Points Along Bar Element Axis (CBAR Entry)

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.
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
 1462 CBEAM
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/BIT

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/BIT

PA PB W1A W2A W3A W1B W2B W3B

SA SB

CBEAM 2 39 7 13 105 GOG

513

Field Contents
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 9.
(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 9. (Character or blank)

Main Index
 CBEAM 1463
Beam Element Connection

Field Contents
BIT Built-in twist of the cross-sectional axes about the beam axis at end B relative
to end A. For beam p-elements only. (Real; Default = 0.0)
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 8-17). 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 allowed for beam
p-elements. Pin flags combined with offsets are not allowed for SOL 600. Pin
flags are not presently allowed in SOL 700.
W1A, W2A, W3A Components of offset vectors from the grid points to the end points of the axis
W1B, W2B, W3B of the shear center. See Remarks 7., 8. and 9. (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 . SA
and SB cannot be specified for beam p-elements. (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) (p. 50) in the
MSC Nastran Reference Manual. Figure 8-17 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 8-17 CBEAM Element Geometry System (Non p-adaptive)

Main Index
 1464 CBEAM
Beam Element Connection

As
FEEDGE Bs
ZA
V
YA
WB
WA A XA
YB GB
YA
V BIT
ZB XB
GA B

Figure 8-18 CBEAM Element Geometry System (p-adaptive)

zelem yelem

Plane 1

Plane 2
M1

V2 M2

Neutral Axis
V1
Fx
xelem
Shear Center

Tx

Figure 8-19 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.

Main Index
 CBEAM 1465
Beam Element Connection

• 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 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 SOLs 106, 129, 153, and 159 the differential stiffness for offset vectors will give incorrect
results with PARAM, LGDISP, 1.
8. If the CBEAM element is referenced by a PSET or PVAL entry, then a p-version formulation is
used and the element can have curved edges.
• By default, the edge of the element is considered straight unless the element is a p-element and
the edge is associated to curved geometry with a FEEDGE entry.
• If a curved edge of a p-element is shared by an h-element without midside nodes, the geometry
of the edge is ignored and considered to be straight. Edges with midside nodes cannot be
shared by p-elements.
• For the beam p-element, components of the offset vectors parallel to the beam axis (FEEDGE)
will be ignored.
• For the beam p-element, offset vectors can only be specified in the displacement coordinate
systems at the grid points.
9. If the element is a p-version element, BIT in field 9 contains the value of the built-in-twist
measured in radians. Otherwise, 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

Main Index
 1466 CBEAM
Beam Element Connection

String Orientation Vector End A Offset End B 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”.)
10. For RC network solver in thermal analysis, the X1, X2, X3, OFFT, PA, PB, W1A, W2A,
W3A,W1B, W2B, W3B, SA and SB are ignored.

Main Index
 CBEAM3 1467
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

Field Contents
EID Unique element identification number. (0 < Integer < 100,000,000)
PID Property identification number of PBEAM3 or PBMSECT entries.
(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
 1468 CBEAM3
Three-Node Beam Element Connection

Field Contents
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. This entry is not available in SOL 600.

Main Index
 CBEAM3 1469
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 8-20 CBEAM3 Element Geometry System

eb

ez

ey

Shear
Center en

Figure 8-21 Local Coordinate System on Beam Cross-Section

8. Offset vectors are treated 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
 1470 CBELT
Seat Belt Element

CBELT Seat Belt Element

Defines a seat belt element. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
CBELT EID PID N1 N2 SBRID SLEN

Example:

CBELT 12 21 1001 1002 11 .04

Field Contents
EID Element ID. Unique number relative to all elements. (Integer; Required)
PID Property ID. (Integer; Required)
N1 Node 1 ID. (Integer; Required)
N2 Node 2 ID. (Integer; Required)
SBRID Retractor ID of a SBRETR entry. (Integer; Required)
SLEN Initial slack length. (Real; Default = 0.0)

Remarks:
1. The retractor ID should be defined only if the element is initially inside a retractor, see the
SBRETR entry.
2. Belt elements are single degree of freedom elements connecting two nodes. When the strain in
an element is positive (i.e. the current length is greater then the unstretched length), a tension force
is calculated from the material characteristics and is applied along the current axis of the element
to oppose further stretching. The unstretched length of the belt is taken as the initial distance
between the two nodes defining the position of the element plus the initial slack length.

Main Index
 CBEND 1471
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

Field Contents
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
 1472 CBEND
Curved Beam or Pipe Element Connection

2. For an additional explanation of the CBEND element, see the PBEND entry description.
Figure 8-22 and Figure 8-23 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 8-22 CBEND Element Coordinate System

zelem

Plane 2
GA
M1
GB
Relem V2
v
θelem
Plane 1 V1

M2 Fθ Mθ

Figure 8-23 CBEND Element Internal Forces and Moments

Main Index
 CBEND 1473
Curved Beam or Pipe Element Connection

3. The options for element connection to GA, GB using GEOM are the following.

Table 8-10 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
A B element arc. Point O (or vector v ) lies on the
opposite side of line AB from the center of the
O curvature.
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
A B from the center of curvature.

4. For RC network solver in thermal analysis, the X1, X2, X3 and GEOM are ignored.

Main Index
 1474 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.

Field Contents
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 8-24 and Remark 3. (Integer > 0 or blank)
S Location of spring damper. See Figure 8-24. (0.0 < Real < 1.0; Default = 0.5)

Main Index
 CBUSH 1475
Generalized Spring-and-Damper Connection

Field Contents
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 8-24)
S1, S2, S3 Components of spring-damper offset in the OCID coordinate system if OCID > 0.
See Figure 8-25 and Remark 9. (Real)

Remarks:
1. Element identification numbers should be unique with respect to all other element identification
numbers.
2. Figure 8-24 shows the bush element geometry.
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. Nastran does not convect
user specified coordinate systems, thus with this option, in nonlinear analysis the element stiffness
direction does not change with deformation.
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
 1476 CBUSH
Generalized Spring-and-Damper Connection

z elem

GA v

y elem
S•l

(1 – S) ⋅ l
Bush location
GB

x elem

Figure 8-24 CBUSH Element

z elem
y elem

Bush location
CID
x elem
( S1, S2, S3 ) OCID

GB

GA
The material stiffness and damping properties of
the elastomer are located at (S1, S2, S3).

Figure 8-25 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 1477
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. For SOL 600, if G0, X1, X2, X3, CID or OCID are entered, a Severe Warning will be issued and
Marc will not run. SOL 600 translates the spring and damping terms in global coordinates of GA
and GB and will use K1 to K6 and B1 to B6 whether or not GA and GB are coincident or not. S,
S1, S2, S3 are ignored. CID is ignored unless it is zero, in which case K1 and B1 are along the
axis of GA to GB and K2-K6 and B2-B6 are ignored if entered.

Main Index
 1478 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

Field Contents 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 8-26.
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 8-26 Spring and Damper Element

Main Index
 CBUSH2D 1479
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

Field Contents
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.

Main Index
 1480 CBUTT
Butt Weld for SOL 700 Only

CBUTT Butt Weld for SOL 700 Only

Defines a butt weld for use in SOL 700 only. Replaces CWELD for SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
CBUTT EID NSID CID FILTER WINDOW NPRT
TFAIL EPSF SIG BEAT L D LT

Example:

CBUTT 1002 11 5 0 0 3 1
0.005 .07 2.5 4.0 2.0 1.5

Field Contents
EID Unique element identification number. EID must be unique with respect to all other
welds, CSPOT, COMBWLD, CFILLET, CBUTT and CCRSFIL. (0 <
Integer < 100,000,000; Required; no Default)
NSIDs BCGRID ID of a set number containing the grid points comprising this weld (Integer
> 0; Required; no Default)
CID ID of a CORDi entry providing the local output coordinate system for this weld
(Integer > 0 or blank, blank is the same as zero indicating the basic coordinate
system)
FILTER Number of force vectors saved for filtering. This option can eliminate spurious
failures due to numerical force spikes buy memory will be larger if this option is
envoked. Enter 0 for no filtering and N for a simple average of force components
divided by N or the maximum number of force vectors that are stored for the time
window option WINDOW (Integer > 0; Default = 0)
WINDOW Time window for filtering (Real; Default = 0.0 for no filtering)
NPRT Control of weld force output in file RBDOUT (Integer > 0; Default = 1)
NPRT=1 data is output
NPRT=2 data is not output
TFAIL Failure time for this weld (Real > 0 or blank; Default = blank which means not used)
Used for ductile failures.
EPSF Effective plastic strain at failure (Real > 0 or blank; Default = blank which means not
used). Used for ductile failures.
SIG Stress at failure (Real > 0 or blank; Default = blank which means not used) Used for
brittle failures.

Main Index
 CBUTT 1481
Butt Weld for SOL 700 Only

Field Contents
BETA Failure parameter for brittle failure (Real > 0 or blank; Default = blank which means
not used) Used for brittle failures.
L Length of butt weld (Real > 0; Required; no Default)
D Thickness of butt weld (Real > 0; Required; no Default)
LT Transverse length of butt weld (Real > 0; Required; no Default)

Remarks:
1. No property entry is needed for the CBUTT entry.
2. Ductile butt weld failure, due to plastic straining, is treated identically to spotweld failure. Brittle
failure of the butt welds occurs when:

β 2 2 2
σn + 3 ( τn + τt ) ≥ σf

where

σ = normal stress
τn = shear stress in direction of weld (local y)
τt = shear stress normal to weld (local z)
σf = failure stress
β = failure parameter

Component σ n is nonzero for tensile values only. When the failure time, t f , is reached the nodal
rigid body becomes inactive and the constrained nodes may move freely. The nodes in the butt
weld may coincide.

Main Index
 1482 CBUTT
Butt Weld for SOL 700 Only

1 1 1 1 1 1 1
z

2 2 2 2 y 2 2 2

x
2 tied nodes that can
be coincident
d

2 tied nodes

Lt

L y

4 tied nodes

Orientation of the local coordinate system and nodal ordering is shown for butt weld failure.

Main Index
 CCONEAX 1483
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

Field Contents
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 Manual, 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
 1484 CCRSFIL
Cross-Fillet Weld for SOL 700 Only

CCRSFIL Cross-Fillet Weld for SOL 700 Only

Defines a cross-fillet weld for use in SOL 700 only. Replaces CWELD for SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
CCRSFIL EID NSID CID FILTER WINDOW NPR NPRT
TFAIL EPSF SIG BETA L W A ALPHA
Repeat this line NPR times
GA GB NCID

Example:

CCRSFIL 1002 11 5 0 0 2 1
0.005 40000. 2.5 4. 3. 2. 25.0
101 201 11
103 203 15

Field Contents
EID Unique element identification number. EID must be unique with respect to all other
welds, CSPOT, COMBWLD, CFILLET, CBUTT and CCRSFIL. (0 <
Integer < 100,000,000; Required; no Default)
NSID BCGRID ID of a set number containing the grid points comprising this weld (Integer
> 0; Required; no Default)
CID ID of a CORDi entry providing the local output coordinate system for this weld.
(Integer > 0 or blank, blank is the same as zero indicating the basic coordinate
system)
FILTER Number of force vectors saved for filtering. This option can eliminate spurious
failures due to numerical force spikes but memory will be larger if this option is
envoked. Enter 0 for no filtering and N for a simple average of force components
divided by N or the maximum number of force vectors that are stored for the time
window option WINDOW (Integer > 0; Default = 0)
WINDOW Time window for filtering (Real; Default = 0.0 for no filtering)
NPR Number of individual nodal pairs in this weld. The third line is repeated NPR times.
(Integer > 0; no Default)
NPRT Control of weld force output in file RBDOUT (Integer > 0; Default = 1)
NPRT=1 data is output
NPRT=2 data is not output
TFAIL Failure time for this weld (Real > 0 or blank; Default = 1.0E20)

Main Index
 CCRSFIL 1485
Cross-Fillet Weld for SOL 700 Only

Field Contents
EPSF Effective plastic strain at failure (Real > 0 or blank; Default which means not used)
Used for ductile failures.
SIG Stress at failure. (Real > 0 or blank; Default = blank which means not used) Used for
brittle failures.
BETA Failure parameter for brittle failure. (Real > 0 or blank; Default = blank which means
not used) Used for brittle failure. Which means not used. Used for brittle failures.
L Length of weld. (Real > 0; Required; no Default)
W Width, W, of flange, see the following figure. (Real > 0; Required; no Default)
A Width, A, of flange, see the following figure. (Real > 0; Required; no Default)
ALPHA Weld angle, see the following figure. (Real > 0; Required; no Default)
GA Grid A ID, see the following figure. (Integer > 0; Required; no Default)
GB Grid B ID, see the following figure. (Integer > 0; Required; no Default)
NCID Local coordinate system of weld. (Integer > 0 or blank; blank is the same as zero
indicating the basic coordinate system)

Remarks:
1. No property entry is needed for the CCRSFIL entry.
2. A simple cross fillet weld illustrates the required input. Here NPR=3 with nodal pairs (GA=2,
GB=1), (GA=3, GB=1), and (GA=3, GB=2). Node 1, 2 and 3 are located in body 1, 2 and 3
respectively. The local coordinate axes of each pair are shown in the following figure. These axes
are fixed in the rigid body and are referenced to the local rigid body coordinate system which
tracks the rigid body rotation.

Body 3
2
Body2

3
1

Body 1

Main Index
 1486 CCRSFIL
Cross-Fillet Weld for SOL 700 Only

z2
z1
x2
y1

x1 y2

2 3

1 1

y3

x3
2
z3

Main Index
 CDAMP1 1487
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

Field Contents
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; 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.)

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) (p. 174)
in the MSC Nastran Reference Manual.
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
 1488 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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
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.

Main Index
 CDAMP1D 1489
Scalar Damper Connection for SOL 700 Only

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
 1490 CDAMP2
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

Field Contents
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.)

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) (p. 174)
in the MSC Nastran Reference Manual.
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.
8. RC network solver does not support CDAMP2 for thermal analysis.

Main Index
 CDAMP2D 1491
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
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.

Main Index
 1492 CDAMP2D
Scalar Damper Connection for SOL 700 Only

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 1493
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
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.
7. RC network solver does not support CDAMP3 for thermal analysis.

Main Index
 1494 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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
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.
7. RC network solver does not support CDAMP4 for thermal analysis.

Main Index
 CDAMP5 1495
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

Field Contents
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.
5. This entry is not supported in SOL 600.
6. RC network solver does not support CDAMP5 for thermal analysis.

Main Index
 1496 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

Field Contents
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 1497
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
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-
ocincident 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
 1498 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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.

Main Index
 CELAS1D 1499
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-
ocincident 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
 1500 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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
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, 707.
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 1501
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.

Main Index
 1502 CELAS2D
Scalar Spring Connection for SOL 700 Only

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.
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 conguent. Connecting non-
ocincident 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 1503
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.

Main Index
 1504 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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
7. A scalar point specified on this entry need not be defined on an SPOINT entry.

Main Index
 CFAST 1505
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 600 and 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

Field Contents
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 8-27.
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 8-27.
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)

Main Index
 1506 CFAST
A Shell Patch Fastener Connection

Remarks:
1. The CFAST defines a flexible connection between two surface patches. Depending on the
location for the piercing points GA and GB, and the size of the diameter D (see PFAST), the
number of unique physical grids per patch ranges from a possibility of 3 to 16 grids. (Currently
there is a limitation that there can be only a total of 16 unique grids in the upper patch and only a
total of 16 unique grids in the lower patch. Thus, for example, a patch can not hook up to four
CQUAD8 elements with midside nodes and no nodes in common between each CQUAD8 as that
would total to 32 unique grids for the patch.)

GS

PIDB

GB

PIDA
L

SHIDB GA

D SHIDA

Figure 8-27 Patches Defined with TYPEj= ‘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. The locations will then 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.

Main Index
 CFAST 1507
A Shell Patch Fastener Connection

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 9 for that entry.
6. In a SOL 400 analysis the CFAST element internally gets decomposed in a CBUSH element and
a number of RBE3 elements. The CBUSH element obtains the properties assigned thru the
PFAST input and its length is determined by the final locations of the GA and GB grids of the
CFAST. The RBE3 elements connect the GA and GB grids to the plate structures. Five RBE3
elements are used on each side to establish the connection. These internal RBE3 elements respond
in the same way to the value of the RIGID Case Control command as any other rigid elements that
may have been defined in the model. The behavior of this element in SOL400 is therefore
controlled by the Case Control Command RIGID.

Main Index
 1508 CFILLET
Fillet Weld for SOL 700 Only

CFILLET Fillet Weld for SOL 700 Only

Defines a fillet weld for use in SOL 700. Replaces CWELD for SOL 700.

Formats:

1 2 3 4 5 6 7 8 9 10
CFILLET EID NSID CID FILTER WINDOW NPRT
TFAIL EPSF SIG BETA L W A ALPHA

Examples:

CFILLET 1002 11 5 0 0 3 1
0.005 .07 2.5 4.0 3.0 2.0 25.0

Field Contents
EID Unique element identification number. EID must be unique with respect to all other
welds, CSPOT, COMBWLD, CFILLET, CBUTT and CCRSFIL. (0 <
Integer < 100,000,000; Required no Default)
NSID BCGRID ID of a set number containing the grid points comprising this weld.
(Integer > 0; Required; no Default)
CID ID of a CORDi entry providing the local output coordinate system for this weld.
(Integer > 0 or blank - blank is the same as zero indicating the basic coordinate
system)
FILTER Number of force vectors saved for filtering. This option can eliminate spurious
failures due to numerical force spikes but memory will be larger if this option is
envoked. Enter 0 for no filtering and N for a simple average of force components
divided by N or the maximum number of force vectors that are stored for the time
window option WINDOW. (Integer > 0; Default = 0)
WINDOW Time window for filtering. (Real; Default = 0.0 for no filtering)
NPRT Control of weld force output in file RBDOUT. (Integer > 0; Default = 1)
NPRT = 1 data is output
NPRT = 2 data is not output
TFAIL Failure time for this weld. (Real > 0 or blank; Default = 1.0E20)
EPSF Effective plastic strain at failure. (Real > 0 or blank; Default = blank which means
not used) Used for ductile failures.
SIG Stress at failure. (Real > 0 or blank; Default = Blank which means not used) Used
for brittle failures.
BETA Failure parameter for brittle failure. (Real > 0 or blank; Default = blank which
means not used) Used for brittle failures.

Main Index
 CFILLET 1509
Fillet Weld for SOL 700 Only

Field Contents
L Length of fillet weld. (Real > 0; Required; no Default)
W Width, A of fillet weld. See Figure 8-28. (Real > 0; Required; No Default)
A Width, A of fillet weld, See Figure 8-28. (Real > 0; Required; No Default)
ALPHA Weld angle in degrees. (Real > 0; Required; No Default)

Remarks:
1. No property entry is needed for the CFILLET entry.
2. Ductile fillet weld failure, due to plastic straining, is treated identically to spotweld failure. Brittle
failure of the fillet welds occurs when:

β 2 2 2
σn + 3 ( τn + τt ) ≥ σf

σn = normal stress
ιn = shear stress in direction of weld (local y)
ιt = shear stress normal to weld (local x)
σf = failure stress
β = failure parameter

Component σ n is nonzero for tensile values only. When the failure time, t f , is reached the nodal
rigid body becomes inactive and the constrained nodes may move freely. In Figure 8-28 the
ordering of the nodes is shown for the 2 node and 3 node fillet welds. This order is with respect
to the local coordinate system where the local z axis determines the tensile direction. The nodes
in the fillet weld may coincide. The failure of the 3 node fillet weld may occur gradually with
first one node failing and later the second node may fail.

Main Index
 1510 CFILLET
Fillet Weld for SOL 700 Only

z local coordinate z
system

2 NODE FILLET WELD

α

2
x
1
y

w a L

3 NODE FILLET WELD

Figure 8-28

Nodal ordering and orientation of the local coordinate system is shown for fillet weld failure. The
angle is defined in degrees.

Main Index
 CFLUIDi 1511
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

Field Contents
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
 1512 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 8-29:
15
Polar
Axis

14
φ = 0.0

Element Element Element

100, 120, 110,
CFLUID2 CFLUID4 CFLUID3

11 12 13
Radius
Figure 8-29 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 1513
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

Field Contents
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 are coincident (distance from GA to GB < 10 – 4 ). 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.

Main Index
 1514 CGAP
Gap Element Connection

• If the CID field is blank and the grid points GA and GB are not coincident (distance from A
to B ≥ 10 – 4 ), then the line AB is the element x-axis and the orientation vector v lies in the x-y
plane (like the CBEAM element).
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 8-30 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 1515
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

Field Contents
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. The second continuation is optional.
5. It is recommended that the edge points be located within the middle third of the edge.
6. The face consisting of grid points G1 through G4 and G9 through G12 is assumed to be in contact
with the structure.

Main Index
 1516 CHACAB
Acoustic Absorber Element Connection

G18
G7
G6

G19

G17
G20
G8
G2
G10 G5
G3

G11 G9

G4 G12

G1

Figure 8-31 CHACAB Element Connection

7. 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 1517
Acoustic Barrier Element Connection

bulk_

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

Field Contents
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. The second continuation is optional.
5. It is recommended that the edge points be located within the middle third of the edge.
6. 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.
7. 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
 1518 CHACBR
Acoustic Barrier Element Connection

G18
G7
G6

G19
G17
G20
G8
G2
G10 G5
G3

G11 G9

G4 G12

G1

Figure 8-32 CHACBR Element Connection

8. 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 1519
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

Field Contents
EID Surface element identification number for a specific side of a particular element.
See Remarks 1. and 9. (Unique (0 < Integer < 100,000,000) among all elements.)
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.

Main Index
 1520 CHBDYE
Geometric Surface Element Definition (Element Form)

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.
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

Main Index
 CHBDYE 1521
Geometric Surface Element Definition (Element Form)

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, 1522 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.
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
 1522 CHBDYG
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

Field Contents
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 8-33, Figure 8-34, and Figure 8-35.
• TYPE = REV

Main Index
 CHBDYG 1523
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 8-33 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 .

ey is the unit vector in the y direction.

• 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
 1524 CHBDYG
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 8-34 TYPE Examples

G3 or G4
n
T 1x
G2

G1 T 12

Figure 8-35 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
 CHBDYG 1525
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.
8. 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.

Main Index
 1526 CHBDYP
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

Field Contents
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
 CHBDYP 1527
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.

G1

Figure 8-36 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 8-37 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
 1528 CHBDYP
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.

R1
R2

Figure 8-38 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.

Main Index
 CHBDYP 1529
Geometric Surface Element Definition (Property Form)

• 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.
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.
9. For RC network solver in thermal analysis, the G0, GMID, CE, E1, C2 and E3 are ignored.

Main Index
 1530 CHEXA
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

Field Contents 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 connection Integer > 0 or blank Required
points.

G18
G7
G6

G19
G15 G17
G14
G20
G8
G2
G10 G5
G16 G3

G11 G13 G9

G4 G12

G1

Main Index
 CHEXA 1531
Six-Sided Solid Element Connection

Figure 8-39 CHEXA 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. 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.
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 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
 1532 CHEXA
Six-Sided Solid Element Connection

T
G7
G6

G8 G5 R
S

G3

G4
G2
G1
Figure 8-40 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, 1003.
9. If a CHEXA element is referenced by a PSET or PVAL entry, then a p-version formulation is used
and the element can have curved edges.
• If a curved edge of a p-element is shared by an h-element without midside nodes, the geometry
of the edge is ignored and set straight.
• Elements with midside nodes cannot be p-elements and edges with midside nodes cannot be
shared by p-elements.
10. By default, all of the twelve edges of the element are considered straight unless:
• For p-elements there is an FEEDGE or FEFACE entry that contains the two grids of any edge
of this element. In this case, the geometry of the edge is used in the element.
• For h-elements, any of G9 through G20 are specified.
11. This element may be used as a three-dimensional eight-node solid shell element when
PSLDN1entry with BEH8 = SLCOMP (INT8 = ASTN) (SOL 400 only).
12. When this element is used as a three-dimensional eight-node 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.

Main Index
 CIFHEX 1533
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

Field Contents
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
G17-G20 top 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
 1534 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 11
12 7
˜ 15
v3
˜ 3
5 18
13 v2
17 ˜ 10
y 1
9 6
14
2

x
z

6. This element does not support thermal load. No thermal strain will be generated.

Main Index
 CIFPENT 1535
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

Field Contents
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
G13-G15 top 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
 1536 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
1 13 v2 8
y ˜
7 5
11
2

x
z

6. This element does not support thermal load. No thermal strain will be generated.

Main Index
 CIFQDX 1537
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

Field Contents
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.

Main Index
 1538 CIFQDX
Axisymmetric InterFace Cohesive Zone Modeling Element

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.

7. This element does not support thermal load. No thermal strain will be generated.

Main Index
 CIFQUAD 1539
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

Field Contents
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
 1540 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 1541
Line Interface Element Connection

CINTC Line Interface Element Connection

Defines a line interface element with specified boundaries.

Format:

1 2 3 4 5 6 7 8 9 10
CINTC EID TYPE
LIST = (BID1(INTP1), BID2(INTP2),...,BIDn(INTPn))

Example:

CINTC 1001 GRDLIST

LIST=(101,102(Q),-103(Q),104(L))

Field Contents
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
 1542 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

Field Contents
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 { P IDVi }
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, 2205 Bulk Data
entry and the LOADSET (Case), 390.
4. In the CID or IDV fields, a CLOAD entry may not reference an identification number defined by
another CLOAD entry.

Main Index
 CMARKB2 1543
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

Field Contents
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
 1544 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

Field Contents
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 1545
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

Field Contents
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 Manual, 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

Main Index
 1546 CMASS1
Scalar Mass Connection

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
 CMASS2 1547
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
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, 1545.

Main Index
 1548 CMASS3
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.

Main Index
 CMASS4 1549
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

Field Contents
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) (p. 174)
in the MSC Nastran Reference Manual.
5. A scalar point specified on this entry need not be defined on an SPOINT entry.

Main Index
 1550 CMREBAI
Defines Rebar Elements and Matching “Matrix” Solid Elements using the Marc REBAR with INSERT Method in SOL

CMREBAI Defines Rebar Elements and Matching “Matrix” Solid Elements using
the Marc REBAR with INSERT Method in SOL 600

In some cases, particularly for modeling of concrete or tires, it is beneficial to add rebar or cord material
to a matrix. The resulting combined material is similar to a composite but it is sometimes easier to
postprocess the stresses of the rebar and matrix separately to determine failure conditions. Unlike the
CMREBAR element, this element can span multiple matrix CHEXA elements (for example, could be
allied to all elements on the bottom of a flat surface modeled with several layers of CHEXA matrix
elements through the thickness).

Format:

1 2 3 4 5 6 7 8 9 10
CMREBAI ID IP G1 G2 G3 G4 G5 G6
G7 G8

Example:
CMREBAI 100 2 31 32 88 87
CMREBAI 250 8 1 2 3 4 5 6
7 8

Field Contents
ID Rebar element ID should be distinct between all element ID’s. (Integer; Required;
no Default)
IP Property identification of a matching PMRBAR entry. (Integer; Required; no
Default)
G1-G4 Grid point identification numbers of the four corner points. (Integer > 0; all unique)
G5-G8 Grid point identification numbers of the four mid-side nodes similar to G5-G8 for
the CQUAD8 element. (Integer > 0, or blank. If any of G5-G8 are not blank, all
nodes in the range G5 to G8 must be defined and must be unique among the range
G1-G8.)

Remarks:
1. This entry makes use of Marc’s REBAR and INSERT capabilities for membrane element types
147 and 148. If G5-G8 are blank, Marc element 147 with 4 nodes is used. If G5-G8 are not blank,
Marc element 148 with 4 corner nodes and 4 mid-side nodes is used. Entry CMREBAR makes
use of Marc’s REBAR capability (without INSERT) and uses rebar elements 23 and 146.
2. The grid ID’s do not have to correspond to those of any matrix CHEXA element. The PMREABI
entry is used to describe the matrix CHEXA elements that these rebar elements will be inserted
into.

Main Index
 CMREBAI 1551
Defines Rebar Elements and Matching “Matrix” Solid Elements using the Marc REBAR with INSERT

3. Cord-reinforced composites are characterized by a group of reinforcing cords with arbitrary

spatial orientations embedded in various matrix materials. The different constituents may have
different mechanical properties. Two typical examples of the cord-reinforces composites are tires
and cord-reinforced concretes. In modeling such materials, the rebar technique is very useful. The
basic idea of rebar layer concept contains (1) the reinforcing cords and the matrix materials of the
composites are represented independently by different types of elements along with different
constitutive models, (2) the reinforcing cords within the elements modeling these cords (the so-
called rebar elements) are assumed to be in the form of layers, and (3) the rebar elements are then
embedded into the matrix elements. The compatibility between the cord elements and the matrix
elements is enforced by embedding membrane rebar elements into solid matrix elements using
Marc’s INSERT option. Membrane rebar elements types 147 and 148 are available with this
option. They are empty 4-node or 8-node quadrilaterals. You can place reinforcing cord layers
within these empty elements. These elements are then embedded into their corresponding solid
elements representing the matrix materials. Independent meshes can be used for the rebar
membrane elements and the matrix elements. Marc’s INSERT option is automatically invoked by
the CMREBAI elements and used to enforce the compatibility between two different meshes.
4. The major difference between the CMREBAR and CMREBAI elements is that CMREBAR
elements share the same grids as the matrix CHEXA elements while CMREBAI elements
typically have different grid ID’s than the matrix CHEXA elements. Marc’s INSERT option
automatically adds tyings (MPC’s) between the CMREBAI grids and the CHEXA grids.
5. CMREBAI elements are preferred over the CMREBAR elements when re-meshing is involved.
6. See MPREBAI for additional information and figures defining these rebar elements.
7. Only CHEXA elements may be used for the matrix elements.

Main Index
 1552 CMREBAR
Defines Rebar Elements and Matching “Matrix” Solid Elements using the Marc REBAR without INSERT Method in

CMREBAR Defines Rebar Elements and Matching “Matrix” Solid Elements using
the Marc REBAR without INSERT Method in SOL 600

In some cases, particularly for modeling of concrete or tires, it is beneficial to add rebar or cord material
to a matrix. The resulting combined material is similar to a composite but it is sometimes easier to
postprocess the stresses of the rebar and matrix separately to determine failure conditions. CMREBAR
elements require that the rebar be placed in matching CHEXA matrix elements on a one-to-one basis.
For a similar capability where the rebar can span multiple CEHXA matrix elements, see the CMREBAI
entry.

Format:

1 2 3 4 5 6 7 8 9 10
CMREBAR ID IP ID2 IDD ID22

Example:
CMREBAR 100 2 1
CMREBAR 1001 50 101 1100 200

Field Contents
EID Rebar element ID should be distinct between all element ID’s. (Integer; Required;
no Default)
IP Property identification of a matching PMRBAR entry. (Integer; Required; no
Default)
ID2 CHEXA (8 node or 20 node) “matrix” element that the rebar will be added to.
(Integer; Required; no Default)
IDD If more than one rebar element in a continuous range is to be added to a continuous
range of rebar elements, IDD represents the first rebar element identification number
in the range. (Integer; Required; Default = 0, IDD must be larger than ID)
ID22 If more then one rebar element in a continuous range is to be added to a continuous
range of “matrix” elements, ID22 represents the last CHEXA matrix element
identification number in the range. (Integer; Required; Default = 0, ID22 must be
larger then ID2)

Remarks:
1. This entry makes use of Marc’s REBAR capability for element types 23 and 146. Entry
CMREBAI makes use of Marc’s REBAR and INSERT capabilities and uses membrane rebar
elements 147 and 148.
2. If IDD is entered, IDD2 must also be entered and the difference IDD-ID must match the difference
IDD2-ID2.

Main Index
 CMREBAR 1553
Defines Rebar Elements and Matching “Matrix” Solid Elements using the Marc REBAR without INSERT

3. The same grid ID’s are used to define element ID and ID2. Similarly the same grid ID’s define
the other elements if a range of elements are used. Element ID is an “empty shell element” and
up to 5 rebar layers (each containing multiple rebar) are placed in the empty shell as specified by
the PMREBAR property entries.
4. Cord-reinforced composites are characterized by a group of reinforcing cords with arbitrary
spatial orientations embedded in various matrix materials. The different constituents may have
different mechanical properties. Two typical examples of the cord-reinforces composites are tires
and cord-reinforced concretes. In modeling such materials, the rebar technique is very useful. The
basic idea of rebar layer concept contains that (1) the reinforcing cords and the matrix materials
of the composites are represented independently by different types of elements along with
different constitutive models, (2) the reinforcing cords within the elements modeling these cords
(the so-called rebar elements) are assumed to be in the form of layers, and (3) the rebar elements
are then embedded into the matrix elements. The compatibility between the cord elements and the
matrix elements is enforced by superimposing solid rebar elements on corresponding solid matrix
elements using the same element connectivity. The rebar elements are empty 8-node or 20-node
CHEXA elements derived from the matching matrix elements. The reinforcing cord layers are
placed within the elements. Each solid rebar element is then superimposed on a solid matrix
element. The two elements share the same space with the same element connectivity (therefore,
the same element nodes). The compatibility condition between the reinforcements and the matrix
materials is then automatically enforced.
5. The major difference between the CMREBAR and CMREBAI elements is that CMREBAR
elements share the same grids as the matrix CHEXA elements while CMREBAI elements
typically have different grid ID’s than the matrix CHEXA elements. Marc’s INSER T option
automatically adds tyings (MPC’s) between the CMREBAI grids and the CHEXA grids.
6. CMREBAI elements are preferred over the CMREBAR elements when re-meshing is involved.
7. See PMREBAR for additional information and figures defining these rebar elements.
8. Only CHEXA elements may be used for the matrix elements.

Main Index
 1554 CNTRUDS
User-defined Solution Control

CNTRUDS User-defined Solution Control

Specifies user-defined solution control. the user can control the I/O, monitor the energies and other
solution norms of interest, and to terminate the problem. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
CNTRUDS CID GROUP UNAME

Example:

In FMS Section of the MSC Nastran input stream:

CONNECT SERVICE DAMPEN SCAI.MDSo
lver700

In Bulk Data:
CNTRUDS 2 DAMPEN UCTRL1

Field Contents
CID Unique user-defined solution control id. It must be only once in the model. (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 required.

Remarks:
1. Only can be used for SOL 700.
2. UNAME=UCTRL1 can only be used.

Main Index
 Entries CO - CY 1555
Defines Data for Cohesive Materials in SOL 600

Entries CO - CY MSC Nastran Quick Reference Guide COHESIV

COHESIV Defines Data for Cohesive Materials in SOL 600

This option allows you to define material properties for interface elements, that may be used to simulate
the onset or progress of delamination, and to associate these material properties with a list of element
numbers. The cohesive material is defined using the cohesive energy (also called critical energy release
rate), that equals the area below the equivalent traction versus equivalent relative displacement curve.
The shape of this curve can be bilinear, exponential, or combined linear-exponential. Mixed mode
delamination is incorporated by converting the normal and shear components of the relative
displacements into an equivalent using the normal shear weighting factor.
As an alternative to the standard linear, exponential, and liner-exponential model, the user can also utilize
this option to trigger the call to the UCOHESIVE user-subroutine. Used in SOL 600 only.

Format:

1 2 3 4 5 6 7 8 9 10
COHESIV MID ITYPE IACT NAME
EN COD MOD NSW SNW DECAY ‘
VISC RATE STIFF
ISET

Example:
COHESIV 101 1 1 material number10 1
2000. .01 .015 23. 24. 1.
.05 0.0 1.0
101

Field Contents
MID (3,1) Material ID - Must match a MATXXX entry. (Integer; no Default)
ITYPE (3,2) Type of cohesive model. (Integer > 0; Default = 1)
1 Bilinear model (Default)
2 Exponential modes
3 Combined linear-exponential model
-1 User-defined using user-subroutine UCOHESIVE
IACT (3,3) Option to deactivate elements and output to t16 file. (Integer; Default = 0)
0 Elements remain active regardless of the damage level.

Main Index
 1556 COHESIV
Defines Data for Cohesive Materials in SOL 600

Field Contents
1 Deactivate the elements if the maximum damage in all the element
integration points has been reached. Do not remove the elements from the
t16 file.
2 Deactivate the elements if the maximum damage in all the element
integration points has been reached. Remove the elements from the t16 file.
NAME (3,5) Name of the material. (Character up to 40 characters; no Default; optional entry)
EN (4,1) Cohesive energy. (Real; no Default; Required value)
COD (4,2) Critical opening displacement. (Real; no Default; Required value)
MOD (4,3) Maximum opening displacement (Bilinear model only). (Real; no Default)
NSW (4,4) Normal-shear weighting factor, beta. (Real; no Default; Required value)
SNW (4,5) Shear-normal weighting factor. (Real; Default = 1.0)
DECAY (4,6) Exponential decay factor. (Linear-Exponential model only).(Real; Default = 1.0)
VISC (4,7) Viscous energy dissipation factor (zero implies no viscous energy dissipation). (Real;
Default = 0.0)
RATE (4,8) Relative displacement reference rate. Only sued if viscous energy dissipation is by
setting VISC to a non-zero value. (Real; Default = 0.0)
STIFF (4,9) Stiffening factor in compression. (Real; Default = 1.0)
ISET (5) ID of a SET3 entry defining the elements associated with this cohesive material.
(Integer, no Default, Required value)

Remarks:
1. Values in parenthesis (i,j) refer to Marc’s COHESIVE entry. (Datablock, field)
2. For solid elements, this entry may be used to add a “layer” or interface between the solid elements
(CHEXA, CTETRA or CPENTA). This interface can fail or delaminate depending on the
properties entered. It is used in conjunction with Marc element types 188, 192 and 193 and
provides the material properties for these element types.
3. For shell elements (CQUADi, CTRIAi) this entry may be used to add a layer between the edges
of adjacent shells. It is used in conjunction with Marc element types 186 and 187 and provides the
material properties for these element types.
4. Solid or shell elements with a COHESIV MID will automatically be assigned Marc element types
186, 187, 188, 189, 192, 193 as appropriate to the type and number of grids defined for that
element. These solid elements must either only have corner nodes or have the full parabolic
number of nodes (for example, CHEXA must either have 8 nodes or 20 nodes).
5. For SOL 600, cohesive behavior is not available for axisymmetric or plane strain analyses.
6. MID must not be used by any other material such as MAT1, MAT2, etc.
7. All continuation lines are required.

Main Index
 COMBWLD 1557
Complex Combined Weld for SOL 700 Only

COMBWLD Complex Combined Weld for SOL 700 Only

Defines a complex or combined weld for use in SOL 700 only. Replaces CWELD for SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
COMBWLD EID NSID FILTER WINDOW NPR NPRT M32
TFAIL EPSF SIG BETA L W A ALPHA
GA GB NCID WTYP
The second and third entries are repeated NPR times (as many welds as are in the combined weld).

Example:
COMBWLD 1002 11 0 0 12 1
44000. 2.5 4.0 3.0 2.0 22.5
1520 2520 0
42000. 2.5 2.0 1.25 0.75 -22.5
101 201 1 1

Field Contents
EID Unique element identification number. EID must be unique with respect to all other
welds, CSPOT, COMBWLD, CFILLET, CBUTT and CCRSFIL. (0 <
Integer < 100,000,000; Required; no Default)
NSID BCGRID ID of a set number containing the grid points comprising this weld. (Integer
> 0; Required; no Default)
CID ID of a CORDi entry providing the local output coordinate system for this weld.
(Integer > 0 or blank, blank is the same as zero indicating the basic coordinate system)
Filter Number of force vectors saved for filtering. This option can eliminate spurious
failures due to numerical force spikes but memory will be larger if this option is
invoked. Enter 0 for no filtering and N for a simple average of force components
divided by N or the maximum number of force vectors that are stored for the time
window option WINDOW. (Integer > 0; Default = 0)
WINDOW Time window for filtering. (Real; Default = 0.0 for no filtering)
NPR Number of individual nodal pairs in this weld. (Integer > 0; Required; no Default)
NPRT Control of weld force output in file RBDOUT. (Integer > 0; Default = 1)
1 Data is output
2 Data is not output

Main Index
 1558 COMBWLD
Complex Combined Weld for SOL 700 Only

Field Contents
TFAIL Failure time for this weld. (Real > 0 or blank; Default = 1.0E20)
EPSF Effective plastic strain at failure. (Real > 0 or blank; Default = blank which means not
used) – Used for ductile failures.
SIG Stress at failure. (Real > 0 or blank; Default = blank which means not used) – Used
for brittle failures.
BETA Failure parameter for brittle failure. (Real > 0 or blank; Default = blank which means
not used) – Used for brittle failures.
L Length of weld. (Real > 0; Required; no Default)
W Width, W, of flange, see Figure 8-41. (Real > 0; Required; no Default)
A Width, A, of flange, see Figure 8-41. (Real > 0; Required; no Default)
ALPHA Weld angle, see Figure 8-41. (Real > 0; Required; no Default)
GA Grid A ID, see Figure 8-41. (Integer > 0; Required; no Default)
GB Grid B ID, see Figure 8-41. (Integer > 0; Required; no Default)
NCID Local coordinate system of weld. (Integer > 0 or blank - blank is the same as zero
indicating the basic coordinate system)
WTYPE Weld pair type – see Figure 8-41. (Integer > 0; Required; no Default)
0 Fillet weld
1 Butt weld

Remarks:
1. No property entry is needed for the COMBWLD entry.

Main Index
 COMBWLD 1559
Complex Combined Weld for SOL 700 Only

2. The 2nd and 3rd entries are repeated for each portion of the combined weld

Figure 8-41 A Combined Weld is a Mixture of Fillet and Butt Welds.

Main Index
 1560 CONM1
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

Field Contents
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
 CONM2 1561
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

Field Contents
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.

Main Index
 1562 CONM2
Concentrated Mass Element Connection, Rigid Body Form

5. The form of the inertia matrix about its center of gravity is taken as:

M
M symmetric
M
I11
– I21 I22
– I31 – I32 I33

where

M =  ρ dV
2 2
I11 =  ρ ( x 2 + x 3 ) dV
2 2
I22 =  ρ ( x 1 + x 3 ) dV
2 2
I33 =  ρ ( x 1 + x 2 ) 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 nonpositive 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.
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 1563
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

Field Contents
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.
4. For RC network solver in thermal analysis, the J, C and NSM are ignored.

Main Index
 1564 CONROD
Rod Element Property and Connection

P
G2

G1

T
Figure 8-42 CONROD Element Forces and Moments

Main Index
 CONSPOT 1565
Connection Spotweld

CONSPOT Connection Spotweld

A spotweld is defined between segments of the two property ID’s in SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
CONSPOT CID PID1 PID2
ELM1 ELM2 ELM3 ELM4 ...

Example:
CONSPOT 101 21 22
ELM1 ELM2 ELM3 ELM4 ...

Field Contents
CID Connection Spotweld identification. (Integer > 0; no Default; Required)
PID1 Property 1. (Integer > 0; no Default; Required)
PID2 Property 2. (Integer > 0; no Default; Required)
ELMx Beam element ID. (Integer > 0; no Default; Required)

Remarks:
1. The surface of each segment should project to the other and in the most typical case the node
defining the weld, assuming only one node is used, should lie in the middle; however, this is not
a requirement.
2. Only elements can be referenced that are beams and reference the PBSPOT property.
3. Two property ID's are tied by the spot weld element. If the CONSPOT is not defined for the
PBSPOT elements the nodal points of the spot weld are located to the two nearest segments. The
surface of each segment should project to the other and in the most typical case the node defining
the weld, assuming only one node is used, should lie in the middle; however, this is not a
requirement. Note that with the spot weld elements only one node is needed to define the weld,
and two nodes are optional.

Main Index
 1566 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 FCTMIN FCTMAX
GAIN1 GAIN2 GAIN3

Example:
CONTRLT 100 20 T TSTAT 68. 73. 7 1.
0.1 0.01 0. 0. 1.
0. 0. 0.

Field Contents
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)

Main Index
 CONTRLT 1567
Thermal Control Element for Heat Transfer Analysis

Field Contents
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)
FCTMIN/MAX Minimum factor/Maximum factor on load to apply. (Real; Default = 0.0)
GAINx Gain variables for heat controller. Use GAIN1 for P value, GAIN2 for I value,
and GAIN3 for D value. (Real; Default = 0.0)

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).
6. RC network solver only supports PTYPE=1 and PTYPE=2 thermostat controller, SFORM,
CTYPE, PZERO, DT, DELAY, TAUC and TA8 are ignored.

Main Index
 1568 CONTRLT
Thermal Control Element for Heat Transfer Analysis

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
 CONTRLT 1569
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

7. The last 5 parameters are for RC Network solver only.

8. RC Network solver only supports controllers (thermostats) on source data. This entry can be used
in either steady-state (static) or transient state (dynamic). For more details about these parameters,
please reference the MSC SINDA User’s Guide and Library Reference.

Main Index
 1570 CONV
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

Field Contents
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:
• q = H ⋅ ( T – TAMB ) EXPF ( T – TAMB ) , CNTRLND = 0
• q = ( H ⋅ u CNTRLND ) ( T – TAMB ) EXPF ( T – TAMB ) , CNTRLND ≠ 0
• q = H ( T EXPF – TAMB EXPF ) , CNTRLND = 0
• q = ( H ⋅ u CNTRLND ) ( T EXPF – TAMB EXPF ) , CNTRLND ≠ 0
EXPF is specified on the PCONV entry.
(See PCONV, 3163 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
 CONV 1571
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, 3163, for an explanation of the mathematical relationships
involved in free convection and the reference temperature for convection film coefficient.
7. RC network solver only supports CNTRLND node defined by SPC or SPCD entries, FLMND is
ignored.

Main Index
 1572 CONV3
Convection Boundary

CONV3 Convection Boundary

Define convection boundary conditions for a thermal or coupled thermal/structural analysis. Used in
SOL 700 only.

Format

1 2 3 4 5 6 7 8 9 10
CONV3 ID HTID HMULT TTID TMULT C
EID1 EID2 EID3 etc

Field Contents
ID CONV3 identification number. (Integer > 0, required)
HTID TABLED1 ID or TABLEMi for heat transfer coefficient, h (Integer, default=0)
>0: function versus time,
=0: use constant multiplier value, HMULT,
<0: function versus temperature.
HMULT Table multiplier for h (Real, default=0.0)
TTID TABLED1 ID for TAMB versus time (Integer >0, default=0)
0: use constant multiplier, TMULT.
TMULT Table multiplier for TAMB (Real, default=0.0)
C Component numbers. (0 < Integer < 3; up to 3 unique Integers may be placed in the
field with no embedded blanks.) 1=TOP, 2=BOT, 3=MID. (Integer > -1; Default =
1)
EIDi CHBDYi element identification number. (Integer > 0 or “THRU” or “BY”)

Remarks:
1. A convection boundary condition is calculated using
q′′ = h(T - TAMB) where
hheat transfer coefficient
(T - TAMB)temperature potential
Three alternatives are possible for the heat transfer coefficient which can be a function
of time, a function of temperature, or constant. Also, the temperature of the boundary
T ∞ can be either constant or a function of time. For both curves, multipliers can be
used to scale the values.
2. CONV3 cards are only available when ANALYSIS=HTRAN.

Main Index
 CONVM 1573
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

Field Contents
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).
Case 1: Define a thermostat controller using the CONTRLT Bulk Data entry.

Main Index
 1574 CONVM
Heat Boundary Element Forced Convection 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

Main Index
 CONVM 1575
Heat Boundary Element Forced Convection Entry

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).
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, 3166, for an explanation of the mathematical relationships
available for forced convection and the reference temperature for fluid material properties.
6. RC network solver does not support CONVM for thermal analysis, it uses PRJCON for forced
convection.

Main Index
 1576 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

Field Contents
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.

Main Index
 CORD1C 1577
Cylindrical Coordinate System Definition, Form 1

4. The location of a grid point (P in Figure 8-43) in this coordinate system is given by (R, θ, Z) where
θ is measured in degrees.
z

uz
G2

G3
uθ

G1 P

Z
θ ur

x R y

Figure 8-43 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 Point and
Coordinate System Definition (p. 33) in the MSC Nastran Reference ManualSOL 700 Reference
Manual.
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
 1578 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

Field Contents
CIDA, CIDB Coordinate system identification number. (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 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.

Main Index
 CORD1R 1579
Rectangular Coordinate System Definition, Form 1

4. The location of a grid point (P in Figure 8-44) in this coordinate system is given by (X, Y, Z).
z

uz
G2

P
G3 uy

ux Z
G1 y

Y
x

Figure 8-44 CORD1R Definition

5. The displacement coordinate directions at P are shown above by ( u x, u u, u z ) .

Main Index
 1580 CORD1RX
Rectangular Coordinate System Definition, Form 1 Alternate for SOL 700

CORD1RX Rectangular Coordinate System Definition, Form 1 Alternate for

SOL 700

Alternate rectangular coordinate system specification for SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
CORD1RX CID G1 G2 G3 CID2 G4 G5 G6

Example:
CORD1RX 1 22 456 457

Field Contents Type Default

CID Coordinate-system number. I>0 Required
G1, G2, G3 Grid-point numbers G1, G2, and G3. The grid points I>0 Required
must be unique.
CID2 Optional second coordinate-system number I>0 Blank
G4, G5, G6 Grid-point numbers G4, G5, and G6. The grid-point I>0 Blank
numbers must be unique.

Remark:
1. First node is the origin, 2nd node is the local x-axis, 3rd node is the node on the XY plane.

Main Index
 CORD1S 1581
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

Field Contents
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.

Main Index
 1582 CORD1S
Spherical Coordinate System Definition, Form 1

4. The location of a grid point (P in Figure 8-45) in this coordinate system is given by (R, θ, φ) where
θ and φ are measured in degrees.
z

G2
uφ

θ
ur
G3 P

G1 R

φ uθ
x

Figure 8-45 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 Point and
Coordinate System Definition (p. 33) in the MSC Nastran Reference ManualSOL 700 Reference
Manual.
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
 CORD2C 1583
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

Field Contents
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.

Main Index
 1584 CORD2C
Cylindrical Coordinate System Definition, Form 2

5. The location of a grid point (P in Figure 8-46) in this coordinate system is given by (R, θ, Z),
where θ is measured in degrees.
z

uz
B
uθ

P
C

A
Z
ur

x R
y

Figure 8-46 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 Point and
Coordinate System Definition (p. 33) in the MSC Nastran Reference ManualSOL 700 Reference
Manual. 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 (Ch. 3).

Main Index
 CORD2R 1585
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

Field Contents
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 (Ch. 3).

Main Index
 1586 CORD2R
Rectangular Coordinate System Definition, Form 2

6. The location of a grid point (P in the Figure 8-47) in this coordinate system is given by (X, Y, Z).
z

uz
B

P
C uy
ux Z
A
y

Y
x
Figure 8-47 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
 CORD2RX 1587
Rectangular Coordinate System Definition, Form 2 Alternate for SOL 700

CORD2RX Rectangular Coordinate System Definition, Form 2 Alternate for

SOL 700

Alternate rectangular coordinate system specification for SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
CORD2RX CID RID A1 A2 A3 B1 B2 B3
C1 C2 C3

Example:
CORD2RX 1 22 0. 0. 1.0
0.1 1.0

Field Contents Type Default

CID Coordinate-system number. I>0 Required
RID Reference coordinate system that is defined I>0 0
independent of the new coordinate system.
A1, A2, A3 Coordinate of three points in the coordinate system Real 0.0
B1, B2, B3 referenced by RID.
C1, C2, C3

Remark:
1. First node is the origin, 2nd node is the local x-axis, 3rd node is the node on the XY plane.

Main Index
 1588 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

Field Contents
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 (Ch. 3).

Main Index
 CORD2S 1589
Spherical Coordinate System Definition, Form 2

6. The location of a grid point (P in Figure 8-48) in this coordinate system is given by (R, θ, φ), where
θ and φ are measured in degrees.
z

B
uφ

θ
ur
C P

A R

uθ
φ
x

Figure 8-48 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 Point and
Coordinate System Definition (p. 33) in the MSC Nastran Reference ManualSOL 700 Reference
Manual.
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
 1590 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

Field Contents
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 1591
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
 1592 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

Field Contents
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
 CORD3RX 1593
Moving rectangular coordinate system Alternate in SOL 700 only.

CORD3RX Moving rectangular coordinate system Alternate in SOL 700 only.

Alternate moving rectangular coordinate system specification for SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
CORD3RX CID G1 G2 G3 CID2 G4 G5 G6

Example:
CORD3RX 1 22 456 457

Field Contents Type Default

CID Coordinate-system number. I>0 Required
G1, G2, G3 Grid-point numbers G1, G2, and G3 must be unique. I>0 0

Remark:
1. First node is the origin, 2nd node is the local x-axis, 3rd node is the node on the XY plane.

Main Index
 1594 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 CONSTAN
T
CONSTAN 1.E5
T

Field Contents
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 1595
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
 1596 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.

Field Contents
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 1597
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

Field Contents
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
 1598 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

Example:
COUPLE 100 37 INSIDE ON ON
0.3 0.0

Field Contents
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
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 1599
General Euler-Lagrange Coupling Surface

Field Contents
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
 1600 COUPLE
General Euler-Lagrange Coupling Surface

Field Contents
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)

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.
7. An initial gas composition is for use with the single-material hydrodynamic Euler solver and an
ideal-gas equation of state (EOSGAM) only.

Main Index
 COUPLE 1601
General Euler-Lagrange Coupling Surface

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.

Main Index
 1602 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

Field Contents 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.

G6

G15 G14
G12
G13
G4 G5

G10 G3
G11
G9 G8

G7
G1
G2

Figure 8-49 CPENTA Element Connection

Main Index
 CPENTA 1603
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. 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.
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

G11
G10 x

G3 G8
G9

G7 G2
G1

Figure 8-50 CPENTA Element Coordinate System

Main Index
 1604 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, 1003.
8. If a CPENTA element is referenced on a PSET or PVAL entry, then a p-version formulation is
used and the element can have curved edges.
• If a curved edge of a p-element is shared by an h-element without midside nodes, the geometry
of the edge is ignored and set straight.
• Elements with midside nodes cannot be p-elements and edges with midside nodes cannot be
shared by p-elements.
9. By default, all of the nine edges of the element are considered straight unless:
• For p-elements there is an FEEDGE or FEFACE entry that contains the two grids of any edge
of this element. In this case, the geometry of the edge is used in the element.
• For h-elements any of G7 through G15 are specified.

Main Index
 CQUAD 1605
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

Field Contents
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PLPLANE entry. (Integer > 0)
G1, G2, Identification numbers of connected corner grid points. Required data for all four
G3, G4 grid points. (Unique Integers > 0)
G5, G6, Identification numbers of connected edge grid points. Optional data for any or all
G7, G8 four 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 the
PLPLANE entry has an associated PSHLN2 or PLCOMP 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
 1606 CQUAD
Fully Nonlinear Plane Strain Element

Field Contents
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
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.
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, 1003.
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 8-51 CQUAD Element Coordinate System

Main Index
 CQUAD4 1607
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

Field Contents
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. See Figure 8-53. 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
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. For SOL 600, only CORD2R is allowed. See Remark 10.
(Integer > 0; If blank, then THETA = 0.0 is assumed.)

Main Index
 1608 CQUAD4
Quadrilateral Plate Element Connection

x
MCID
Coordinate
System

z
G2
y G3
ymaterial

xmaterial

G4

G1

Figure 8-52 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 1609
Quadrilateral Plate Element Connection

yelement
G3

G4

β+γ xelement
α = ------------
2

α
xmaterial
zelement

β
THETA γ

G1 G2

Figure 8-53 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 p-elements and 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 CQUAD4 elements referenced by a PSET or PVAL entry, the stresses, strains and element
forces are output in the local tangent plane of the element. The local tangents are oriented in
a user defined direction which is uniform across a set of elements. By default, the local
tangent x-direction is oriented in the positive x-direction of the basic coordinate system. See
the Bulk Data entry, OUTRCV, 3016 for user defined output coordinate systems.
• 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 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
 1610 CQUAD4
Quadrilateral Plate Element Connection

7. For finite deformation hyperelastic analysis, the plot codes are given by the CQUADFD element
name in Item Codes, 1003.
8. If a CQUAD4 element is referenced by a PSET or PVAL entry, then a p-version formulation is
used and the element can have curved edges.
• If a curved edge of a p-element is shared by an h-element CQUAD4, the geometry of the edge
is ignored and set straight.
9. By default, all of the four edges of the element are considered straight unless the element is a
p-element and the edge is associated to curved geometry with a FEEDGE or FEFACE entry.
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.
11. For RC network solver in thermal analysis, the ZOFFS is ignored.
12. In SOL 600, when PCOMP is used, one must define the material property with orientation,
MCID>0.

Main Index
 CQUAD8 1611
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

Field Contents
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHELL, PCOMP, PCOMPG or PLPLANE
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. (Integer > 0 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. 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 8-54. 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
 1612 CQUAD8
Curved Quadrilateral Shell Element Connection

Field Contents
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
(see Remark 3.) MCID is ignored for hyperelastic elements. For SOL 600, only
CORD2R is allowed. 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 8-54.
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.

Main Index
 CQUAD8 1613
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) (p. 118) in the MSC Nastran Reference Manual.
Stresses and strains are output in the local coordinate system identified by x l and y l in
Figure 8-54. 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, 1003.

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

eη
yl
η

α
B eξ
A
α⁄2 ξ

α
β = 45° – ---
2
β 45°

Gi
xl

Main Index
 1614 CQUAD8
Curved Quadrilateral Shell Element Connection

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
yl is formed by bisection of A and B
xl is perpendicular to y l

Figure 8-54 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.
11. For RC network solver in thermal analysis, the ZOFFS is ignored.
12. In SOL 600, when PCOMP is used, one must define the material property with orientation,
MCID>0.

Main Index
 CQUADR 1615
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

Field Contents
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PSHELL, PCOMP or PCOMPGentry.
(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 8-56. (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
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. For SOL 600, only CORD2R is
allowed. (Integer > 0; If blank, then THETA = 0.0 is assumed.)
ZOFFS Offset from the surface of grid point to the element plane. See Remark 8.

Main Index
 1616 CQUADR
Quadrilateral Plate Element Connection

x
MCID
Coordinate
System

z
G2
y G3
ymaterial

xmaterial

G4

G1

Figure 8-55 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 (Ch. 1) in the MD Nastran Reference ManualSOL 700
Reference Manual for additional information.

Main Index
 CQUADR 1617
Quadrilateral Plate Element Connection

7. The CTRIAR element is the triangular companion to the CQUADR element and should be used
instead of CTRlA3 or CTRlA6.
yelement
G3

G4

β+γ xelement
α = ------------
2

α
xmaterial

zelement
β
THETA γ

G1 G2

Figure 8-56 CQUADR Element Geometry and Coordinate Systems

8. 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 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.
9. In SOL 600, when PCOMP is used, one must define the material property with orientation,
MCID>0.

Main Index
 1618 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 eight 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

Field Contents
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 Identification numbers of connected corner grid points. Required data for all four
G3, G4 grid points. (Unique Integers > 0). See Remark 3., 6., 7.
G5, G6 Identification numbers of connected edge grid points. Optional data for any or all
G7, G8 four 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 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 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 1619
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 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 8-57.
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, 1003.
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 Constant η or ξ
ξ = 1
η = 0 ξ = constant
G8 G9 G6

η = –1
G5 G2
G1

r = xbasic

Figure 8-57 CQUADX Element Coordinate System

Main Index
 1620 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

Field Contents
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 8-58.
7. The ratio of the element dimensions in the y to x axis shown for the element coordinate system in
Figure 8-58 should be in the range 2.0 to 0.5.
8. The stress output is interpreted as shown in Crack Tip Elements (CRAC2D, CRAC3D) (p. 178) in
the MSC Nastran Reference Manual.

Main Index
 CRAC2D 1621
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 8-58 CRAC2D Element Connection for Full and Symmetric Options

Main Index
 1622 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

Field Contents
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 1623
Three-Dimensional Crack Tip Element

3. This element, including grid point numbering conventions, is shown in Figure 8-59 and
Figure 8-60. 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 8-59 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) (p. 178) in
the MSC Nastran Reference Manual.
10. As depicted in Figure 8-59 and Figure 8-60, 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
 1624 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 8-59 CRAC3D Solid Crack Tip Element with Required Connection Points Only

Main Index
 CRAC3D 1625
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 G33
y G36 G63 G61
Y1 X1 G62

G25
G38 G27 G35 G26 G34
XB
G37 G42
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 8-60 CRAC3D Solid Crack Tip Element with All Connection Points

Main Index
 1626 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

Field Contents
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)
EXP Temperature-dependent term, e ( –ΔH ⁄ ( R ⋅ T0 ) ) , 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
TIDCP, parameters K p ( σ ) , C p ( σ ) , and C s ( σ ) , respectively. See Remarks 3. through 4.
TIDCS (Integer > 0)
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.

Main Index
 CREEP 1627
Creep Characteristics

Creep Law Class 1

The first creep law class is expressed as:

c – R ( σ )t
ε ( σ, t ) = A ( σ ) [ 1 – e ] + K ( σ )t (8-1)

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 bσ
A(σ) aσ i=1 ae i=2
dσ d
R(σ) ce j=1 cσ j=2
g fσ
K(σ) e ⋅ [ sinh ( fσ ) ] k=1 ee k=2

TYPE=ijk where i, j, and k are digits equal to 1 or 2, according to the desired function in the table
above. For example, TYPE=122 defines A ( σ ) = aσ b , R ( σ ) = cσ d , and K ( σ ) = ee fσ .

Creep Law Class 2

The second creep law class (TYPE=300) is expressed as:

c b d
ε ( σ, t ) = aσ t (8-2)
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:
1⁄d
 εc 
λ = C p ⁄ K pi =  --------- (8-3)
 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
1 λ 2ε t0 εc
------ =  ---- ---- ( 1 – d )d – -----
- + ----
Kp  t 0
 σ Cs σ

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

Main Index
 1628 CREEP
Creep Characteristics

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 ) (8-4)

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 (8-5)
·c
εo

where:

·c
ε = corrected creep rate
·c
εo = creep rate at T0
T0 – 1
 ------
 T  = correction factor
EXP

Main Index
 CREEP 1629
Creep Characteristics

3. Creep model parameters Kp, Cp, and Cs represent parameters of the uniaxial rheological model as
shown in Figure 8-61.
Tabular values (Xi, Yi) in the TABLES1 entry correspond to ( σ i, K pi ) , ( σ i, C pi ) , and ( σ i, C si ) 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 8-61 CREEP Parameter Idealization

Creep model parameters, as shown in Figure 8-62 through Figure 8-64, 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 )

Figure 8-62 Kp Versus σ Example for CREEP

Main Index
 1630 CREEP
Creep Characteristics

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 8-63 Cp Versus σ Example for CREEP

6
50,000 × 10

6
40,000 × 10

Kips-hours 6
( C s ) -------------------------
2
- 30,000 × 10
in
6
20,000 × 10

6
10,000 × 10

0
5 10 15 20 25 30

σ ( ksi )

Figure 8-64 Cs 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 1631
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

Field Contents
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, 1563 for alternative method of rod definition.
3. Only one element may be defined on a single entry.

Main Index
 1632 CROD
Rod Element Connection

P
G2

G1

T
Figure 8-65 CROD Element Internal Forces and Moments

Main Index
 CROSSEC 1633
Cross-Section Output Request

CROSSEC Cross-Section Output Request

Define a cross section for resultant forces written to SECFORC in SOL 700. If the SETS option is used,
just one card is needed which identifies a node set and at least one element set. In this latter case the node
set defines the cross section and the forces from the elements belonging to the element set(s) are summed
up to form the section forces. Thus the element set(s) should include elements to only one side (not both
sides) of the cross section. The cross-section should cut through deformable elements only, not rigid
bodies. Forces in the Eulerain domain will be excluded as well. Cutting through master segments for
deformable solid element spot welds can lead to incorrect section forces since the constraint forces are
not accounted for in the force and moment summations. Beam element modeling of welds does not
require any special precautions.

Format:

1 2 3 4 5 6 7 8 9 10
CROSSEC CSID OPTION DT TYPE CID SIDG SIDE
PSID XCT YCT ZCT XCH YCH ZCH RADIUS
XHEV YHEV ZHEV LENL LENM

Example:
CROSSEC 14 PLANE 1.0E-4
0.0 0.0 0.0 0.0 0.0 0.0 100.

Field Contents
CID Unique number of a CROSSEC entry. (Integer > 0; Required)
OPTION Type of cross section. (Character; Required.)
PLANE Define a cutting plane at the location of the cross section, see
Figure 8-66.
SET Define cross section from a set of grid points and a set of elements. See
Remark 1.
DT Output request interval. If more than one CROSSEC is defined, the lowest DT will
be used for all cross section output requests. See remark 4. (Real > 0; Required)
TYPE Output option for local coordinate system. (Integer > 0; Default = 2)
0 Rigid Body
1 Accelerometer
2 Coordinate System ID
CID ID of local coordinate system for output. (Integer > 0; Default = 0)
TYPE = 0 ID of a MATRIG

Main Index
 1634 CROSSEC
Cross-Section Output Request

Field Contents
TYPE = 1 ID of ACCMETR
TYPE = 2 ID of CORDx
SIDG ID of SET1 with grid point ids. Only for TYPE = SET. (Integer; Required)
SIDE ID of SET1 with element ids. Only for TYPE = SET. (Integer; Required)
PID ID of BCPROP. Only for TYPE = PLANE. If blank or 0 all properties in the model
will be used. (Integer; Default = 0.)
XCT, YCT, Coordinates of tail of any outward drawn normal vector, N, originating on wall (tail)
ZCT and terminating in space (head), see Figure 8-66. Only for TYPE = PLANE. (Real;
Default = 0.0.)
XCH, YCH, Coordinates of head of any outward drawn normal vector, N. Only for TYPE =
ZCH PLANE. (Real; Default = 0.0.)
RADIUS Optional radius. If RADIUS > 0., a circular cut plane centered at (XCT, YCT, ZCT)
of radius=RADIUS, with the normal vector originating at (XCT, YCT, ZCT) and
pointing towards (XCH, YCH, ZCH) will be created. In this case the variables
XHEV, YHEV, ZHEV, LENL, and LENM, which are defined on the continuation
line, will be ignored. Only for TYPE = PLANE. (Real; Default = 0.0)
XHEV, YHEV, Coordinates of head of edge vector, L. Only for TYPE = PLANE. (Real; Default =
ZHEV 0.0.)
LENL Length of edge a, in L direction. Only for TYPE = PLANE. (Real; Default = 1.0E20.)
LENM Length of edge b, in M direction. Only for TYPE = PLANE. (Real; Default =
1.0E20.)

Main Index
 CROSSEC 1635
Cross-Section Output Request

Resultants are computed

on this plane
M

N L

b
a

Origin of cutting plane

Figure 8-66 Definition of cutting plane for automatic definition of interface for cross-sectional
forces. The automatic definition does not check for springs and dampers in the
section. For best results the cutting plane should cleanly pass through the
middle of the elements, distributing them equally on either side. Elements that
intersect the edges of the cutting plane are deleted from the cross-section.

Remarks:
1. If the SET option is used, the grid point set defines the cross section and the forces from the
elements belonging to the element set are summed up to form the section forces. Thus the element
set should include elements to only one side (not both sides) of the cross section. The cross-
section should cut through deformable elements only, not rigid bodies.
2. Forces in the Eulerian domain are not included.
3. Cutting through master segments for deformable solid element spot welds can lead to incorrect
section forces since the constraint forces are not accounted for in the force and moment
summations. Beam element modeling of welds does not require any special precautions.
4. When DT is set, the cross section time history results will be stored in secforc of binout file.
The time history results will includes:
• x, y, z force
• x, y, z moment
• x, y, z center
• area
• resultant force

Main Index
 1636 CSEAM
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

Field Contents
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.

Main Index
 CSEAM 1637
A Shell Patch SEAM Connection

Field Contents
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 = 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.
If CTYPE = “ELEM”, element id defining patches A and B. IDAE ≠ IDBE.
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 8-67.

Main Index
 1638 CSEAM
A Shell Patch SEAM Connection

Figure 8-67 Connected Shell Elements for a CSEAM Element

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.

Main Index
 CSEAM 1639
A Shell Patch SEAM Connection

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.
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 8-68). 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 8-68 Seam Weld at an Edge

Main Index
 1640 CSEAM
A Shell Patch SEAM Connection

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.
• 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

This model is acceptable - CONVEX

θ ( > CNRAGLI).

Main Index
 CSEAM 1641
A Shell Patch SEAM Connection

S2 E4

M
θ
S1 ⁄ E1

EIDSA
EIDEA
S3
E3
EIDMA

S4

E2
This model fails - not CONVEX
θ ( < CNRAGLI and point M does not project
to EIDSA, EIDMA or EIDEA.

This shared grid is a shell grid of another two different shell elements.

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

Main Index
 1642 CSEAM
A Shell Patch SEAM Connection

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

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
S4 E1 E4

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

Main Index
 CSEAM 1643
A Shell Patch SEAM Connection

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

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

Main Index
 1644 CSEAM
A Shell Patch SEAM Connection

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.

Caution: 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 9 for that entry.

Main Index
 CSET 1645
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

Field Contents
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, 1069 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
 1646 CSET1
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

Field Contents
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.

Main Index
 CSET1 1647
Free Boundary Degrees-of-Freedom, Alternate Form of CSET Entry

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, 1069 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
 1648 CSHEAR
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

Field Contents
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 8-69 CSHEAR Element Connection and Coordinate System

Main Index
 CSHEAR 1649
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 8-70 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
 1650 CSHEAR
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 ) MAX( τ 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
 CSLOT3 1651
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

Field Contents
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
 1652 CSLOT4
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

Field Contents
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
 CSPOT 1653
Spot Weld for SOL 700 Only

CSPOT Spot Weld for SOL 700 Only

Defines a complex or combined weld for use in SOL 700 only. Replaces CWELD for SOL 700.

Format:

1 2 3 4 5 6 7 8 9 10
CSPOT EID NSID CID FILTER WINDOW NPRT
TFAIL EPSF SN SS N M

Example:

CSPOT 1001 11 5 0 0 1
0.005 .07

Field Contents
EID Unique element identification number. EID must be unique with respect to all other
welds, CSPOT, COMBWLD, CFILLET, CBUTT and CCRSFIL. (0 <
Integer < 100,000,000; Required; no Default)
NSID BCGRID ID of a set number containing the grid points comprising this weld
(Integer > 0; Required; no Default)
CID ID of a CORDRiX entry providing the local output coordinate system for this weld.
(Integer > 0, Default = 0).
FILTER Number of force vectors saved for filtering. This option can eliminate spurious
failures due to numerical force spikes but memory will be larger if this option is
envoked. Enter 0 for no filtering and N for a simple average of force components
divided by N or the maximum number of force vectors that are stored for the time
window option WINDOW. (Integer > 0, Default = 0)
WINDOW Time window for filtering.(Real > 0.0, Default = 0.0 for no filtering)
NPRT Control of weld force output in file RBDOUT. (Integer > 0; Default = 1)
NPRT=1 data is output.
NPRT=2 data is not output.
TFAIL Failure time for this weld (Real > 0 or blank; Default = 1.0E20)
EPSF Effective plastic strain at failure (Real > 0 or blank; Default = blank which means
not used). Used for ductile failures.
SN Sn, normal force at failure (Real > 0 or blank; Default = blank which means not
used) Used for brittle failures
SS Ss, shear force at failure (Real > 0 or blank; Default = blank which means not used)
Used for brittle failures.

Main Index
 1654 CSPOT
Spot Weld for SOL 700 Only

Field Contents
N Exponent n for normal force (real > 0 or blank; Default = blank which means no
used) Used for brittle failures.
M Exponent m for normal force (Real > 0 or blank; Default = blank which means not
used) Used for brittle failures

Remarks:
1. No property entry is needed for the CSPOT entry.
2. Spotweld failure due to plastic straining occurs when the effective nodal plastic strain exceeds the
input value, ε pfail . This option can model the tearing out of a spotweld from the sheet metal since
the plasticity is in the material that surrounds the spotweld, not the spotweld itself. A least squares
algorithm is used to generate the nodal values of plastic strains at the nodes from the element
integration point values. The plastic strain is integrated through the element and the average value
is projected to the nodes via a least square fit. This option should only be used for the material
models related to metallic plasticity and can result in slightly increased run times.
Brittle failure of the spotwelds occurs when:

 max ( f n, 0 ) n  f s  m
-------------------------
- + ------- ≥ 1
 Sn   Ss 

where f n and f s are the normal and shear interface force. Component f n contributes for tensile
values only. When the failure time, t f , is reached the nodal rigid body becomes inactive and the
constrained nodes may move freely. In Figure 8-71 the ordering of the nodes is shown for the 2
node and 3 node spotwelds. This order is with respect to the local coordinate system where the
local z-axis determines the tensile direction. The nodes in the spotweld may coincide. The failure
of the 3 node spotweld may occur gradually with first one node failing and later the second node
may fail. For n noded spotwelds the failure is progressive starting with the outer nodes (1 and n)
and then moving inward to nodes 2 and n-1. Progressive failure is necessary to preclude failures
that would create new rigid bodies.

Main Index
 CSPOT 1655
Spot Weld for SOL 700 Only

z
z

node 3
node 2

node 2
node 1
y
y
3 NODE SPOTWELD
2 NODE SPOTWELD
node 1
z x
x

node n

node n-1

3 NODE SPOTWELD

node 2

node 1

Figure 8-71

Main Index
 1656 CSPOT
Spot Weld for SOL 700 Only

Nodal ordering and orientation of the local coordinate system is important for determining
spotweld failure.

Main Index
 CSPH 1657
SPH Particle

CSPH SPH Particle

Defines a SPH particle. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
CSPH NID PID MASS

Example:

CSPH 1490 2 4.4736E-3

Field Contents
NID Node ID for SPH particle. (Integer > 0; Required)
PID Property ID to which this SPH belongs referencing a PSPH entry. (Integer > 0;
Required)
MASS Mass value. (Real > 0.0; Default = 0.0)

Remark:
1. SPH ID is the node referenced (NID).

Main Index
 1658 CSPR
Springs With Offsets

CSPR Springs With Offsets

Springs with offsets for use in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
CSPR EID PID G1 G2 VID IOP S PF
OFST

Example:

CSPR 1 22 456 457 1.0

0.1

Field Contents 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. If zero, the spring/damper connects node G1 to I > 0 0
ground.
VID ID of CORDiRX. Orientation option. The orientation I>0 0
option should be used cautiously since forces, which are
generated as the nodal points displace, are not orthogonal to
rigid body rotation unless the nodes are coincident.
0: The spring/damper acts along the axis from node G1 to
G2,
> 0: The spring/damper acts along the axis defined by the
direction of coordinate CORDiRX system.

Main Index
 CSPR 1659
Springs With Offsets

Field Contents Type Default

IOP 0 Deflections/rotations are measured and forces/moments Integer 0
applied along the z-axis of a CORD2RX coordinate
system.
1 Deflections/rotations are measured and forces/moments
applied along the axis between the two spring/damper
nodes projected onto the plane normal to the z-axis of a
CORD2RX coordinate system.
2 Deflections/rotations are measured and forces/moments
applied along a vector defined by the z-axis of a
CORD1RX or CORD3RX coordinate system.
3 Deflections/rotations are measured and forces/moments
applied along the axis between the two spring/damper
nodes projected onto the plane normal to a vector defined
by the z-axis of a CORD1RX or CORD3RX coordinate
system.
S Scale factor on forces. R>0 1.0
PF Print flag: I>0 0
EQ.0: forces are printed in DEFORC file
EQ.1: forces are not printed DEFORC file.
OFFSET Initial offset. The initial offset is a displace mentor rotation R>0 0.0
at time zero. For example, a positive offset on a
translational spring will lead to a tensile force being
developed at time zero.

Main Index
 1660 CSSCHD
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

Field Contents
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.

Main Index
 CSSCHD 1661
Aerodynamic Control Surface Schedule Input

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
 1662 CSSHL
Solid Shell Element Connection

CSSHL Solid Shell Element Connection

Defines a connection for a Solid Shell with 6 or 8 grid points in SOL 600 only.

Format:

1 2 3 4 5 6 7 8 9 10
CSSHL EID PID G1 G2 G3 G4 G5 G6
G7 G8

Example:

CSSHL 44 11 1 2 3 4 5 6 quad
7 8

CSSHL 51 22 11 12 13 21 22 tria
23

CSSHL 51 22 11 12 13 13 21 22 tria
23 23
(Note: the 2nd and 3rd examples are equivalent to each other.)

Field Contents
EID Element identification number. (0 < Integer < 100,000,000; Required)
PID Property identification of a PSSHL entry. (Integer > 0; Required)
Gi Grid point identification number of connection points. (Integer U or blank, for quad
shapes all 8 values are required, for triangle shapes only G4 and G8 may be left blank
in which case G4=G3 and G8=G7.)

Remarks:
1. This element can degenerate to a triangle either by leaving G4 and G8 blank or by entering G4=G3
and G8=G7 (see 2nd and 3rd examples).
2. This element is usually only used when contact on each of the shell is anticipated.
3. Mid-side nodes are not available for this element.

Main Index
 CSSHL 1663
Solid Shell Element Connection

4. Grid point ordering is shown in the following figure.

6
ζ
η
ξ
4
1

5. The stiffness of this element is formed using one integration point in the element plane and a user
defined number through the element thickness. In this way the element can capture accurate
material plasticity under bending load. An additional variationally consistent stiffness term is
included to eliminate the hourglass modes that are normally associated with reduced integration.
6. The number of integration points through the thickness is given by PARAM,MARCSLHT
7. This element may be collapsed to a triangular solid shell to attach to a standard shell such as
CQUAD4 as follows:

8. This element is not currently available with Total Lagrange, finite strain plasticity or hyperelastic
materials.

Main Index
 1664 CSSHLH
CHEXA to Solid Shell Element Connection

CSSHLH CHEXA to Solid Shell Element Connection

Defines conversion of CHEXA elements to Solid Shell elements in SOL 600 only.

Format:

1 2 3 4 5 6 7 8 9 10
CSSHLH EID1 PID EID2 EID3 EID4 EID5 EID6

Example:

CSSHLH 44 11 54 200 250

Field Contents
EIDi CHEXA element identification numbers. See Remark 1. (0 < Integer < 100,000,000;
no Default; EID1 is required)
PID Property identification of a PSSHL entry to be used with all the elements with EIDi.
(Integer > 0; Required)

1. All CHEXA elements in the range EID1 to EID2 will be converted to solid shells. The original
CHEXA elements will be deleted and the solid shell elements will have the same element ID’s as
the original CHEXA elements.
2. All CHEXA elements in the range EID3 to EID4 as well as EID5 to EID6 will be converted to
solid shells if these fields are entered.
3. Mid-side nodes are not allowed.
4. Elements for this entry are mapped to Marc element type 185.
5. Please see the remarks for CSSHL for additional items.
6. The PSSHL entries associated with CSSHLH are not generated automatically. They must be
input using a GUI or with a text editor.

Main Index
 CSSHLM 1665
CHEXA or CPENTA to Solid Shell Material Conversion

CSSHLM CHEXA or CPENTA to Solid Shell Material Conversion

Defines conversion of CHEXA or CPENTA elements described by material ID to Solid Shell elements
in SOL 600 only.

Format:

1 2 3 4 5 6 7 8 9 10
CSSHLM MID1 MID2 MID3 MID4 MID5 MID6 MID7
MID8 MID9

Example:

CSSHLM 100 200 700 90250

Field Contents
MIDi Material identification numbers. See Remark 1. (Integer > 0; no Default; MID1 is
required)

Remarks:
1. All CHEXA and CPENTA elements with the MID’s specified will be converted to solid shells.
The original CHEXA and CPENTA elements will be deleted and the solid shell elements will
have the same element ID’s as the original elements.
2. All PSOLID entries which reference all MIDi values will automatically be converted to PSSHL
entries retaining the MID and CORDM values. The PSSHL property ID’s will be the same as the
PSOLID ID’s plus IPOFF. The value of IPOFF should not be zero since the original PSOLID
entries are not deleted and all property ID’s should normally be unique.
3. Mid-side nodes are not allowed.
4. Elements for this entry are mapped to Marc element type 185.
5. Please see the remarks for CSSHL for additional items.
6. If this entry is used, CSSHLH and CSSHLP entries should not be used.
7. See parameters MCSSHLCK and MCSSHORR for additional options for this entry.

Main Index
 1666 CSSHLP
CPENTA to Solid Shell Element Connection

CSSHLP CPENTA to Solid Shell Element Connection

Defines conversion of CPENTA elements to Solid Shell elements in SOL 600 only.

Format:

1 2 3 4 5 6 7 8 9 10
CSSHLP EID1 PID EID2 EID3 EID4 EID5 EID6

Example:

CSSHLP 44 11 54 200 250

Field Contents
EIDi CPENTA element identification numbers. See Remark 1.
(0 < Integer < 100,000,000; no Default; EID1 is required)
PID Property identification of a PSSHL entry to be used with all the elements with EIDi.
(Integer > 0; Required)

Remarks:
1. All CPENTA elements in the range EID1 to EID2 will be converted to solid shells. The original
CPENTA elements will be deleted and the solid shell elements will have the same element ID’s
as the original CPENTA elements.
2. All CPENTA elements in the range EID3 to EID4 as well as EID5 to EID6 will be converted to
solid shells if these fields are entered.
3. The solid shell elements will be collapsed Marc element 185 type elements with the 3rd and 4th
grids set to G3 of the CPENTA and the 7th and 8th grids set to the 6th grid of the CPENTA.
4. Mid-side nodes are not allowed.
5. Please see the remarks for CSSHL for additional items.
6. The PSSHL entries associated with CSSHLH are not generated automatically. They must be
input using a GUI or with a text editor.

Main Index
 CSUPER 1667
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

Field Contents
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
 1668 CSUPER
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, 766.
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, 765, EXTDRUNT,
766 and EXTUNIT, 769.

Main Index
 CSUPEXT 1669
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

Field Contents
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
 1670 CTETRA
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

Field Contents 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 points. Integer > 0 or blank Required

G4

G8
G10

G9

G3
G7

G1
G6

G5
G2

Figure 8-72 CTETRA Element Connection

Main Index
 CTETRA 1671
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. 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.
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
 1672 CTETRA
Four-Sided Solid Element Connection

Figure 8-73 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, 1003.
8. If a CTETRA element is referenced by a PSET or PVAL entry, then p-version formulation is used
and the element can have curved edges.
• If a curved edge of a p-element is shared by an h-element without midside nodes, the geometry
of the edge is ignored and set straight.
• Elements with midside nodes cannot be p-elements and edges with midside nodes cannot be
shared by p-elements.
9. By default, all of the six edges of the element are considered straight unless:
• For p-elements, there is an FEEDGE or FEFACE entry that contains the two grids of any edge
of this element. In this case, the geometry of the edge is used in the element.
• For h-elements, any of G5 through G10 are specified.

Main Index
 CTQUAD 1673
Defines an 8-Node Thick Shell Element

CTQUAD Defines an 8-Node Thick Shell Element

Defines an isoparametric membrane-bending or plane strain triangular plate element. Used in SOL 700
only.

Format:

1 2 3 4 5 6 7 8 9 10
CTQUAD EID PID N1 N2 N3 N4 N5 N6
N7 N8

Example:
CTQUAD 1 34 101 102 103 201 202 203
204 205

Field Contents
EID Element identification number. Unique numbers have to be used.
(0 < Integer < 100,000,000; Required)
PID Property identification number referencing a PTSHELL. (Integer > 0; Required)
N1 - N8 Grid points. (Integer; Required)

Remarks:
1. The correct numbering of the nodes is essential for correct use. Nodes N1 to N4 define the lower
surface, and Nodes N5 to N8 define the upper surface. If one point integration is used (see
PTSHELL), the integration points then lie along the t-axis as depicted in the following figure.
Two by two selective reduced integration is also available. Extreme care must be used in defining
the connectivity to insure proper orientation.

Main Index
 1674 CTQUAD
Defines an 8-Node Thick Shell Element

t
n5 n8

n4
n1

n6 n7

n2 n3
r

2. The stresses for this shell element are output in the global coordinate system.
3. To define a thick shell wedge element, CTTRIA can be used, or one can use CTQUAD where
nodal pairs N3 and N4 and N7 and N8 are repeated. The ordering in the latter case is N1, N2, N3,
N3, N4, N5, N6, N6, where Nodes N1, N2, N3 form the lower triangular face and Nodes N4, N5,
N6 for the upper triangular face of the wedge.

Main Index
 CTRIA3 1675
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

Field Contents
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-
CORD1S, G2 line to the to the projected r-axis
CORD2S
Use DIAG 38 to print the computed THETA values. MCID is ignored for
hyperelastic elements. For SOL 600, only CORD2R is allowed. (Integer > 0; if
blank, then THETA = 0.0 is assumed.)

Main Index
 1676 CTRIA3
Triangular Plate Element Connection

x MCID
Coordinate
System

y z

G3

ymaterial

G1 G2
xmaterial

Figure 8-74 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
 CTRIA3 1677
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 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 8-75 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 p-elements and not hyperelastic, the reference
coordinate system for output is the element coordinate system.
• For CTRIA3 elements referenced by a PSET of PVAL entry, the stresses, strains and element
forces are output in the local tangent plane of the element. The local tangents are oriented in
a user defined direction which is uniform across a set of elements. By default, the local
tangent x-direction is oriented in the positive x-direction of the basic 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, 1003.
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. If a CTRIA3 element is referenced by a PSET or PVAL entry, then a p-version formulation is used
and the element can have curved edges.
• If a curved edge of a p-element is shared by an h-element CTRIA3, the geometry of the edge
is ignored and set straight.
8. By default, all of the three edges of the element are considered straight unless the element is a
p-element and the edges are associated to curved geometry with FEEDGE or FEFACE Bulk Data
entries.
9. For RC network solver in thermal analysis, the ZOFFS is ignored.

Main Index
 1678 CTRIA3
Triangular Plate Element Connection

10. In SOL 600, when PCOMP is used, one must define the material property with orientation,
MCID>0.

Main Index
 CTRIA6 1679
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

Field Contents
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. (Integer > 0 or blank)
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
MCID is ignored for hyperelastic elements. For SOL 600, only CORD2R is allowed.
(Integer > 0; if blank, then THETA = 0.0 is assumed)

Main Index
 1680 CTRIA6
Curved Triangular Shell Element Connection

x MCID
Coordinate
System

y z

G3

ymaterial

G1 G2
xmaterial

Figure 8-76 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 8-77.
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 1681
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.
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) (p. 118) in the MSC Nastran Reference Manual.
Stresses and strains are output in the local coordinate system identified by x l and y l in
Figure 8-77. For hyperelastic elements, stresses and strains are output in the coordinate system
defined by the CID field on the PLPLANE entry.
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 8-77 CTRIA6 Element Geometry and Coordinate Systems

Main Index
 1682 CTRIA6
Curved Triangular Shell Element Connection

9. For hyperelastic elements, the plot codes are specified under the CTRIAFD element name in Item
Codes, 1003.
10. For RC network solver in thermal analysis, the ZOFFS is ignored.
11. In SOL 600, when PCOMP is used, one must define the material property with orientation,
MCID>0.

Main Index
 CTRIAR 1683
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

Field Content
s
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
, material angle is measured from the G1-G2 line to the to the projected
CORD2R x-axis
CORD1C r-axis of MCID the coordinate is projected onto shell surface through the
, element center and the material angle is measured from the G1-G2 line
CORD2C to the to the projected r-axis
CORD1S
,
CORD2S
Use DIAG 38 to print the computed THETA values. For SOL 600, only CORD2R
is allowed. (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
 1684 CTRIAR
Triangular Plate Element Connection

x MCID
Coordinate
System

y z

G3

ymaterial

G1 G2
xmaterial

Figure 8-78 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 (Ch. 3) in the SOL 700 Reference Manual for additional
information.

Main Index
 CTRIAR 1685
Triangular Plate Element Connection

yelement G3

xmaterial

THETA
xelement
G1 G2

Figure 8-79 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 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. In SOL 600, when PCOMP is used, one must define the material property with orientation,
MCID>0.

Main Index
 1686 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

Field Contents
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. (Integer > 0 or blank). See Remark 3., 4., 6., 7.
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 1687
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 8-80.
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, 1003.
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 8-80 CTRIAX Element Coordinate System

Main Index
 1688 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

Field Contents
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. Note that the alternate corner-edge grid point pattern is different
from the convention used on the CTRIA6 element.
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 ( r m, z m ) coordinate
system shown in Figure 8-82.
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.5 m ) = 314.

Main Index
 CTRIAX6 1689
Axisymmetric Triangular Element Connection

Figure 8-81 CTRIAX6 Element Idealization

z = zbasic
zm
rm

G5

axial G4
G3
G6
TH

G2
G1
radial r = xbasic

Figure 8-82 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
 1690 CTRIAX6
Axisymmetric Triangular Element Connection

2
2

8
1

1
Z
4
Y 2
X

Figure 8-83 Normal Vectors That Point in a Negative Y Direction.

3 6 4

2
2 5 8 12 15 18
1
11 14 17

7 13 16
1 4 10

Figure 8-84 View Factor Boundary Conditions.

Main Index
 CTRIAX6 1691
Axisymmetric Triangular Element Connection

$ 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
 1692 CTTRIA
Six-Node Thick Shell for SOL 700 Only

CTTRIA Six-Node Thick Shell for SOL 700 Only

Defines a six-node thick shell element which is available with either fully reduced or selectively reduced
integration rules. This plane stress element can be used as an alternative to the 3-node shell elements in
cases where a 6-noded element is desired. Care must be taken in defining the element connectivity as N1
to N3 define the lower surface of the thick shell. The number of through-thickness integration points is
defined by the user. The property of this element is defined on the PTSHELL entry. Used in SOL 700
only.

Format:

1 2 3 4 5 6 7 8 9 10
CTTRIA EID PID N1 N2 N3 N4 N5 N6

Example:

CTTRIA 1 34 101 102 103 201 202 203

Field Contents
EID Element identification number. Unique numbers have to be used. (Required;
0 < Integer < 100,000,000)
PID Property identification number, referencing a PTSHELL. (Required; Integer > 0)
N1-N6 Grid points. (Integer; Required)

Remarks:
1. The correct numbering of the nodes is essential for correct use. Nodes n1 to n3 define the lower
surface, and nodes n4 to n6 define the upper surface. The element corresponds to a collapsed
CTQUAD, with n3=n4 and n7=n8.
2. If one point integration is used (see PTSHELL), the integration points then lie along the t-axis as
depicted in Figure 8-85. Two by two selective reduced integration is also available. Extreme care
must be used in defining the connectivity to insure proper orientation.
3. The stresses for this shell element are output in the global coordinate system.

Main Index
 CTTRIA 1693
Six-Node Thick Shell for SOL 700 Only

n4
t

n1

n5 n6

n2 n3

Figure 8-85

Main Index
 1694 CTUBE
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

Field Contents
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
 CVISC 1695
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

Field Contents
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
 1696 CWELD
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 600 and 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

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

Main Index
 CWELD 1697
Weld or Fastener Element Connection

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

Field Contents Type Default

EWID CWELD element identification number. See Remark 0 < Integer < Required
1. 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 up to 3x3 elements per
patch. See Remark 4.
GA, GB Grid point identification numbers of piercing points Integer > 0 or blank
on surface A and surface B, respectively. See Remark blank
5.
MCID Specifies the element stiffness coordinate system. See Integer > -1 or Default = -1
Remark 15. 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 Real Required if
Remark 2. GS and GA
are not
defined.

Main Index
 1698 CWELD
Weld or Fastener Element Connection

For the alternate formats, the field contents are described below:

Field Contents 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
up to 3x3 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 Integer > 0 Required for
to 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 8-86 through Figure 8-90.

Main Index
 CWELD 1699
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 8-86. Depending on the location of the
piercing points GA, GB and the size of the diameter D, the number of connected elements per
patch ranges from a single element up to 3x3 elements. 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 8-86 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

Main Index
 1700 CWELD
Weld or Fastener Element Connection

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. The locations of GA and GB
are 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.
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 8-86. The connectivity is similar
to the format “PARTPAT”. Depending on the location of the piercing points GA, GB and the size
of the diameter D, the number of connected elements per patch may range from a single element
up to 3x3 elements. 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 8-87. 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 8-88. Then grid GS is connected to shell
SHIDA.

GS

GB4 SHIDB
GA3

GB3

GB
GB1
GA2
GB2

GA
SHIDA

GA1

Figure 8-87 Patch to Patch Connection Defined with Format ELEMID or GRIDID

Main Index
 CWELD 1701
Weld or Fastener Element Connection

GS

GA4
GA3

GA

GA1

GA2

Figure 8-88 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 8-87. In addition, the format “GRIDID” can define a point to
patch connection if all GBi fields are left blank, see Figure 8-88. 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.

Main Index
 1702 CWELD
Weld or Fastener Element Connection

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 8-89. Missing midside nodes are allowed.
GA4 GA7 GA3
GA3

GA6
GA6 GA5
GA8

GA1 GA2 GA1 GA4 GA2

GA5
Figure 8-89 Quadrilateral and Triangular Surface Patches defined with
Format GRIDID

11. The format “ALIGN” defines a point to point connection, see Figure 8-90. 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 8-90 Point to Point Connection Defined with Format ALIGN

12. Forces and moments are output in the element coordinate system, see Figure 8-91. 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

Main Index
 CWELD 1703
Weld or Fastener Element Connection

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
i i
ce 1 = e 1

j min i
ce 1 = { ce 1 }.
i = 1, 2, 3

Note that ce i1 will be set to 10 – 6 if cei1 < 10 –6 .

In case of two equal components we take the one with the smaller i . The corresponding basic
vector
 0 
 
bj , 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 – ----------
- e1 e 2 = ---------
- element y-axis
e˜2
T
e1 e1

and e 3 is just the cross product

e3 = e1 × e2 element z-axis

The final transformation matrix is

T be = e1 e2 e3

Main Index
 1704 CWELD
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
fx mx Torque
m yA Bending moment end A, plane 2
zb m yB Bending moment end B, plane 2
yb m zA Bending moment end A, plane 1
mx m zB Bending moment end B, plane 1

xb
Basic
Figure 8-91 Element Coordinate System and Sign Convention of
Element Forces

13. 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 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

Main Index
 CWELD 1705
Weld or Fastener Element Connection

establish the connection. These internal RBE3 elements respond in the same way to the value of
the RIGID Case Control command as any other rigid elements that may have been defined in the
model. The behavior of this element in SOL400 is therefore controlled by the Case Control
Command RIGID.
14. The output format of the forces and moments including the sign convention is identical to the
CBAR element, see Element Force Item Codes, 1040.
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 9 for that entry.

Main Index
 1706 CYAX
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

Field Contents
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
 CYJOIN 1707
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

Field Contents
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.

Main Index
 1708 CYJOIN
Cyclic Symmetry Boundary Points

7. All grid points that are implicitly or explicitly referenced must be defined.
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
 CYLINDR 1709
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

Field Contents
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
 1710 CYSUP
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

Field Contents
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.

Main Index
 CYSUP 1711
Fictitious Supports for Cyclic Symmetry

b. Displacement coordinate system at the referenced grid point must be cylindrical with z-axis
along the axis of 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
 1712 CYSYM
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

Field Contents
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. See Additional Topics (p. 515) in the MSC Nastran
Reference Manual.

Main Index
 Entries D - E 1713
Deformable to Rigid

Entries D - E MSC Nastran Quick Reference GuideMSC Nastran Quick Reference Guide

D2R0000 Deformable to Rigid

Defines materials to be switched to rigid at the start of the calculation. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
D2R0000 PID MRB

Example:

D2R0000 12 0

Field Contents
PID Property ID of the deformable group of elements, which is switched to a rigid material.
(I > 0; Required)
MRB ID of the master rigid body (MATRIG MID) to which the deformable group of elements
is merged. If zero, the deformable group of elements with property PID becomes either
an independent or master rigid body. (I > 0; Default = 0)

Main Index
 1714 D2RAUTO
Automatic Deformable to Rigid Body Switch

D2RAUTO Automatic Deformable to Rigid Body Switch

Defines a set of properties to be switched to rigid or to deformable at some stage in the calculation. Used
in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
D2RAUTO SWSET CODE TIME1 TIME2 TIME3 ENTNO RELSW PAIRED
NRBF NCSF RWF DTMAX D2R R2D
PID1 MRB1
PID2 MRB2
PIDi MRBi
IPID1
IPID2
IPIDj

Example:
*

1 2 3 4 5 6 7 8 9 10
D2RAUTO 100 1 .005 .008 .00002 2
0 2 2 .00002 2 3
400 1400
401 1401
1001
1002
1003

Field Contents
SWSET Set number for this automatic switch set. Must be unique. (Integer; no Default)
CODE Activation switch code. Defines the test to activate the automatic material switch of the
property. (Integer; Default = 0; see Remark 1.)
0 Switch takes place at TIME1
1 Switch takes place between TIME1 and TIME2 if rigid wall force (specified
below) is zero.
2 switch takes place between TIME1 and TIME2 if contact surface force
(specified below) is zero.

Main Index
 D2RAUTO 1715
Automatic Deformable to Rigid Body Switch

Field Contents
3 switch takes place between TIME1 and TIME2 if rigid wall force (specified
below) is non-zero.
4 switch takes place between TIME1 and TIME2 if contact surface force
(specified below) is non-zero.
TIME1 Switch will not take place before this time (Real; Default = 0.0)
TIME2 Switch will not take place after this time (Real; Default = 1.E20)
TIME3 Delay period. After this switch has taken place, another automatic switch will not take
place for the duration of the delay period. If set to zero a switch may take place
immediately after this switch (Real; Default = 0.0)
ENTNO Rigid wall/contact surface number for switch codes 1, 2, 3, 4 (Integer; Default = 0; see
Remarks 1., 2.)
RELSW Related switch set. The related switch set is another automatic switch set that must be
activated before this switch can take place. If 0or blank, no related switch is set. (Integer;
Default = 0)
PAIRED Define a pair of related switches (Integer; Default = 0; see Remark 3.)
0 Not paired
1 Paired with switch set RELSW and is the Master switch.
-1 Paired with switch set RELSW and is the Slave switch.
NRBF Flag to delete or activate nodal rigid bodies. (Integer; Default = 0; see Remark 4.)
If nodal rigid bodies or generalized, weld definitions are active in the deformable bodies
that are switched to rigid, then the definitions should be deleted to avoid instabilities:
0 No change
1 Delete
2 Activate
NCSF Flag to delete or activate nodal constraint set (Integer; Default = 0; see Remark 4.)
If nodal constraint/spotweld definitions are active in the deformable bodies that are
switched to rigid, then the definitions should be deleted to avoid instabilities:
0 No change
1 Delete
2 Activate
RWF Flag to delete or activate rigid walls (Integer; Default = 0; see Remark 4.)
0 No change
1 Delete
2 Activate
DTMAX Maximum permitted time step size after switch (Real; Default = 0)

Main Index
 1716 D2RAUTO
Automatic Deformable to Rigid Body Switch

Field Contents
D2R Number of deformable properties to be switched to rigid plus number of rigid bodies for
which new master/slave rigid body combinations will be defined. (Integer; Default = 0)
R2D Number of rigid bodies to be switched to deformable. (Integer; Default = 0)
PIDi Property ID of the group of deformable elements, which is switched to a rigid material.
Repeat D2R times. (Integer; Required if D2R is non-zero)
MRB MID of the master rigid body to which the group of deformable elements with property
PID is merged. If zero, the new rigid body becomes either an independent or master rigid
body. Repeat D2R times. (Integer; Default = 0)
IPID Property ID of the group of deformable elements, which is switched to a deformable
material. Repeat R2D times. (Integer; no Default)

Remarks:
1. Only surface to surface and node to surface contacts can be used to activate an automatic part
switch.
2. Contact surface numbers are the order in which they are defined in the file. The first contact pair
encountered in the BCTABLE will have an entity number of 1.
3. Switch sets may be paired together to allow a pair of switches to be activated more than once.
Each pair of switches should use consistent values for CODE, i.e. 1 and 3 or 2 and 4. Within each
pair of switches the related switch, RELSW, should be set to the ID of the other switch in the pair.
The Master switch (PAIRED = 1) will be activated before the Slave switch (PAIRED = -1).
4. If the delete switch is activated, ALL corresponding constraints are deactivated regardless of their
relationship to a switched property. By default, constraints which are directly associated with a
switched property are deactivated/activated as necessary.

Main Index
 D2RINER 1717
Rigid Body Definition of Switched Properties

D2RINER Rigid Body Definition of Switched Properties

Inertial properties can be defined for the new rigid bodies that are created when the deformable properties
are switched. These can only be defined in the initial input if they are needed in a later restart. Unless
these properties are defined, the new rigid body properties will be recomputed from the finite element
mesh. The latter requires an accurate mesh description. When rigid bodies are merged to a master
rigid body, the inertial properties defined for the master rigid body apply to all members of the
merged set. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
D2RINER PID
XC YC ZC TM
IXX IXY IXZ IYY IYZ IZZ

Example:
D2RINER 300
100. 200. 300. 5
2.0 .02 .04 5.0 .05 5.0

Field Contents
PID Property ID. (Integer; Required)
XC x-coordinate of center of mass. (Real; Required)
YC y-coordinate of center of mass. (Real; Required)
ZC z-coordinate of center of mass. (Real; Required)
TM Translational mass. (Real; Required)
IXX, IXY, Inertia tensor of the rigid body about the center of gravity. (Real; Required)
IXZ, IYY,
IYZ, IZZ

Main Index
 1718 DAMPGBL
Defines Values to Use for Dynamic Relaxation

DAMPGBL Defines Values to Use for Dynamic Relaxation

Define mass weighted nodal damping that applies globally to the nodes of deformable bodies and to the
mass center of the rigid bodies for use in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DAMPGBL TID VLDMP STX STY STZ SRX SRY SRZ

Example:
DAMPGBL 2 1.01 1.02 1.03 0.0 0.0 0.0

Field Contents
TID ID of TABLED1 defining system damping constant. The damping force applied to
each grid is f=d(t)mv where d(t) is described in TABLED1. (Integer > 0; Default =
0)
VALDMP System damping constant if LCID is not used. Will apply for all grids all the time.
(Real > 0.0; Default = 0.0)
STX Scale factor for basic coordinate system x direction damping forces. (Real > 0.0;
Default = 0.0)
STY Scale factor for basic coordinate system y direction damping forces. (Real > 0.0;
Default = 0.0)
STZ Scale factor for basic coordinate system z direction damping forces. (Real > 0.0;
Default = 0.0)
SRX Scale factor for basic coordinate system rotation about x direction damping forces.
(Real > 0.0; Default = 0.0)
SRY Scale factor for basic coordinate system rotation about y direction damping forces.
(Real > 0.0; Default = 0.0)
SRZ Scale factor for basic coordinate system rotation about z direction damping forces.
(Real > 0.0; Default = 0.0)

Main Index
 DAMPING 1719
Parameter and Hybrid Damping Specification

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
W3 W4 WH

Example:
DAMPING 100 .02

Field Contents
ID Damping entry identification number. (Integer > 0; no Default)
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)
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
 1720 DAMPING
Parameter and Hybrid Damping Specification

new [ K4 ] = G [ K ] + GEFACT [ K4 ]

The GFACT value used is GEFACT = 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 and W4 values are used in transient response only. A zero value (default) will result in
no damping. The equivalent viscous damping is calculated as:
G GEFACT 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. 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.

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
3. Specify hybrid damping for superelement 1. Use modal damping of two percent critical for the
first 6 modes.
Case Control:

Main Index
 DAMPING 1721
Parameter and Hybrid Damping Specification

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
 1722 DAMPMAS
Mass Damping per Property

DAMPMAS Mass Damping per Property

Defines mass weighted damping by property ID. The referenced property may be either rigid or
deformable. In rigid bodies the damping forces and moments act at the center of mass. Used in SOL 700
only.

Format:

1 2 3 4 5 6 7 8 9 10
DAMPMAS PID TID SF
STX STR STZ SRX SRY SRZ

Example:
DAMPMAS 33 12 1.0
1.0 1.0 1.0 0.0 0.0 0.0

Field Contents
PID Property ID (Integer > 0; no Default; Required)
TID TABLED1 ID which specifies mass weighted system damping as a function of time for
property PID. If TID = 0, no damping is applied. (Integer > 0; Default = 0)
SF Scale factor for load curve. This allows a simple modification of the load curve values
(Real > 0; Default = 1.0)
STX Scale factor on global x translational damping forces. (Real > 0; Default = 0.0)
STY Scale factor on global y translational damping forces (Real > 0; Default = 0.0)
STZ Scale factor on global z translational damping forces. (Real > 0; Default = 0.0)
SRX Scale factor on global x rotational damping moments. (Real > 0; Default = 0.0)
SRY Scale factor on global y rotational damping moments. (Real > 0; Default = 0.0)
SRZ Scale factor on global z rotational damping moments. (Real > 0; Default = 0.0)

Remarks:
Mass weighted damping damps all motions including rigid body motions. For high frequency oscillatory
motion stiffness weighted damping may be preferred. With mass proportional system damping the
acceleration is computed as:
n –1 n n n
α = M ( P – F – F damp )

Main Index
 DAMPMAS 1723
Mass Damping per Property

where, M is the diagonal mass matrix, P n is the external load vector, F n is the internal load vector, and
n
F damp is the force vector due to system damping. This latter vector is defined as:

n
F damp = D s mν

The best damping constant for the system is usually based on the critical damping factor for the lowest
frequency mode of interest. Therefore,
D s = 2ω min

is recommended where the natural frequency (given in radians per unit time) is generally taken as the
fundamental frequency of the structure. The damping is applied to both translational and rotational
degrees of freedom. The component scale factors can be used to limit which global components see
damping forces.
Energy dissipated by through mass weighted damping is reported as system damping energy in the ASCII
file GLSTAT. This energy is computed whenever system damping is active.

Main Index
 1724 DAMPSTF
Stiffness Damping per Property

DAMPSTF Stiffness Damping per Property

Assign Rayleigh stiffness damping coefficient by property ID. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DAMPSTF PID COEF

Example:
DAMPSTF 40 .025

Field Contents
PID Property ID (Integer > 0; no Default; Required)
COEF Rayleigh damping coefficient. Two methods are now available: (Real; Default = 0.0)
< 0.0 Rayleigh damping coefficient is set based on a given frequency and applied
uniformly to each element in the property ID.
= 0.0 Inactive
> 0.0 Rayleigh damping coefficient for stiffness weighted damping. Values
between 0.01 and 0.25 are recommended. Higher values are strongly
discouraged, and values less than 0.01 may have little effect. The damping
coefficient is uniquely defined for each element of the property ID.

Remarks:
The damping matrix in Rayleigh damping is defined as:
C = αM + βK

where C, M, and K are the damping, mass, and stiffness matrices, respectively. The constants α and β
are the mass and stiffness proportional damping constants. The mass proportional damping can be
treated by system damping, see keywords: DAMPGBL and DAMPMAS. Transforming C with the ith
eigenvector φ i gives:

t t 2
φ i Cφ i = φ i ( αM + βK )φ i = α + βω i = 2ω i ξ i δ ij

where ωi is the ith frequency (radians/unit time) and ξ i is the corresponding modal damping parameter.

Generally, the stiffness proportional damping is effective for high frequencies and is orthogonal to rigid
body motion. Mass proportional damping is more effective for low frequencies and will damp rigid body
motion. If a large value of the stiffness based damping coefficient is used, it may be necessary to lower
the time step size significantly. This must be done manually by reducing the time step scale factor on the

Main Index
 DAMPSTF 1725
Stiffness Damping per Property

PARAM,STEPFCT control card. Since a good value of β is not easily identified, the coefficient, COEF,
is defined such that a value of .10 roughly corresponds to 10% damping in the high frequency domain.
In versions prior to 960, one damping coefficient is defined that applies to all elements are referenced
from the same property. With this older approach if 10% of critical damping is sought in the ith mode
then set:

.20
β = -------
ωi

and input β as a negative number. Typically, β is some fraction of the time step size.
Energy dissipated by Rayleigh damping is computed if and only if the flag, RYLEN, on the control
command of PARAM, LSDYNA, ENERGY is set to 2. This energy is accumulated as element internal
energy and is included in the energy balance. In the GLSTAT file this energy will be lumped in with the
internal energy.

Main Index
 1726 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

Field Contents
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
 DBEXSSS 1727
Sub System Statistics

DBEXSSS Sub System Statistics

Output request for sub system statistics. Energies and momentum for all elements referenced by the same
property ID are accumulated and stored as time history data. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DBEXSSS PID PID1 PID2 PID3 PIDi

Example:
DBEXSSS 1 5 6

Field Contents
DID Unique DBEXSS ID. (Integer > 0; no Default; Required)
PIDn BCPROP ID for subsystem n. (Integer > 0; no Default; Required)

Remarks:
1. As many continuation cards may follow as necessary.
2. The following information can be output for each property ID:
Kinetic Energy
Internal Energy
Hourglass Energy
X, Y and Z-Momentum

Main Index
 1728 DBREG
Drawbead Region

DBREG Drawbead Region

Defines a drawbead region. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DBREG DBID RTYPE BID
PID BID2 IDIR TYPE RADIUS CID

Example:
DBREG 2 AUTO
11 1 3 TUBE 18.0

Field Contents
DBID Drawbead region identification. A unique number must be specified. (Integer > 0;
Required)
RTYPE Drawbead region type. (Character; Default = USER)
USER User-defined box region
AUTO Automatic region definition.
BID Identification number of a BCBOX entry defining the stationary box around the
drawbead. Only required when RTYPE=USER. (Integer; Default=blank)
PID Identification number of a BCPROP ID that holds the property id of the blank. Only
required when RTYPE=AUTO. (Integer; Default=blank)
BID2 Identification number of a BCGRID or BCPROP entry that defines the nodal points
that lie along the draw bead. If BCGRID is defined, the nodes in the set must be
consecutive along the draw bead. If a BCPROP is defined, the set must consist of
beam or truss elements. Within the BCPROP set, no ordering of the elements is
assumed, but the number of nodes must equal the number of beam elements plus 1.
(Integer; only required when RTYPE=AUTO.)
IDIR Direction of tooling movement. The movement is in the global coordinate direction
unless the tubular box option is active and CID is nonzero. In this latter case, the
movement is in the local coordinate direction. (Integer; Only required when
RTYPE=AUTO)
1 tooling moves in x-direction,
2 tooling moves in y-direction,
3 tooling moves in z-direction.
TYPE Region type: Char. Only used when RTYPE=AUTO. (Default = BOX.)

Main Index
 DBREG 1729
Drawbead Region

Field Contents
BOX Rectangular box.
TUBE Tubular region. This option is recommended for curved draw beads and for
draw beads that are not aligned with the global axes
RADIUS The radius of the tube, which is centered around the draw bead. Elements of the
property defined in BID2, that lie within the tube will be included in the contact.
(Real; Only required when TYPE=TUBE)
CID Optional coordinate system ID. This option is only available for the TYPE=TUBE.
(Integer; Default = 0)

Main Index
 1730 DCONADD
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

Field Contents
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
 DCONSTR 1731
Design Constraints

DCONSTR Design Constraints

Defines design constraints.

Format:

1 2 3 4 5 6 7 8 9 10
DCONSTR DCID RID LALLOW/L UALLOW/ LOWFQ HIGHFQ
ID UID

Example:
DCONSTR 10 4 1.25

Field Contents
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
 1732 DCONSTR
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 RTYPE with a 'FR' or a 'PSD' prefix, e.g.,
FRDISP or on DRESP2 or DRESP3 entries that inherit the frequency value from these RTYPES.
The bounds provided in LALLOW and UALLOW are applicable to a response only when the
value of forcing frequency of the response falls between the LOWFQ and HIGHFQ. If the ATTB
field of the DRESP1 entry is not blank and these responses are subsequently referenced on a
DRESP2 or DRESP3, the LOWFQ and HIGHFQ are ignored when the DCONSTR refers to these
DRESP2/DRESP3 responses. LOWFQ/HIGHFQ are not ignored when the DCONSTR refers to
a DRESP1 that has a real number in the ATTB field.
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
 DDVAL 1733
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

Field Contents
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 CAMPBLL entry in its DDVALID field (field 4) or a
RSPINR entry in its SPTID field (field 6).

Main Index
 1734 DDVAL
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.

Main Index
 DEACTEL 1735
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 only.

Format:

1 2 3 4 5 6 7 8 9 10
DEACTEL ID ISET

Example:
DEACTEL 2 200

Field Contents
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
 1736 DEACTEL
Define Elements that Should be Deactivated for a Particular Subcase in SOL 600

DEACTEL Define Elements that Should be Deactivated for a Particular Subcase

in SOL 600

This entry allows the user to deactivate elements that have failed or are no longer necessary in a particular
subcase. Some or all of these elements can be re-activated in a subsequent subcase using the ACTIVAT
entry.

Format:

1 2 3 4 5 6 7 8 9 10
DEACTEL ID STRESS STRAIN IGEOM ISET

Example:
DEACTEL 2 1 1 0 200

Field Contents
ID Identification number of a matching DEACTEL Case Control command defining the
subcase to which these elements should be deactivated. (Integer; no Default)
STRESS Flag to control output stresses after the elements have been deactivated. (Integer;
Default = 0)
0 Stresses have the same value as just prior to deactivation
1 Stresses are set to zero
STRAIN Flag to control output strains after the elements have been deactivated. (Integer;
Default = 0)
0 Strains have the same value as just prior to deactivation
1 Strains are set to zero
IGEOM Flag to control whether to update the geometry on the post file. (Integer; Default = 0)
0 Update the geometry.
1 Do not update the geometry.
ISET ID of a list of elements described by SET3 is ID=ISET to be deactivated. (Integer; no
Default)

Remarks:
1. This entry maps to Marc's DEACTIVATE (option A) History definition (option B is not
supported in SOL 600).

Main Index
 DEFORM 1737
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

Field Contents
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
 1738 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

Field Contents
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, 1069. 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 1739
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

Field Contents
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
 1740 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

Field Contents
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 1741
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-11 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-11 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 8-12 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 8-12 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
 1742 DEQATN
Equation Definition

Table 8-12 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
20.0 ⋅ log  ----------------
decibel  PREF

DBA(P, PREF, F) sound pressure in P

20.0 ⋅ log  ---------------- + 10.0 ⋅ log ( Ta1 ) + 10.0 ⋅ log ( Ta 2 )
decibel (perceived)  PREF

DIM(x,y) positive difference x-MIN(x,y)

EXP(x) exponential ex
INVDB(DB, PREF) inverse Db DB
 --------- 
 20.0- + logPREF
10

INVDBA(DBA, inverse Dba  DBA – 10.0 ⋅ log ( Ta1 ) – 10.0 ⋅ log ( Ta2 )-
-------------------------------------------------------------------------------------------------------
 20.0 
PREF, F) 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

2
squares  Xi
i =1

SIN(x) sine sin x

SINH(x) hyperbolic sine sinh x
SQRT(x) square root x

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

Main Index
 DEQATN 1743
Equation Definition

Table 8-12 DEQATN Entry Functions (continued)

Format Description Mathematical Expressions
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.
• DRESP2 entry, then X i represents the DVIDj, LABLk, NRm, Gp, DPIPq, DCICr, DMIMs,
DPI2Pt, DCI2Cu, DMI2Mv, and NRRw fields in that order.
• GMLOAD, GMBC, or TEMPF entries, then
X1 represents x in the basic coordinate system,
X2 represents y in the basic coordinate system, and
X 3 represents z in the basic coordinate system.

• GMCURV entry, then

X1 represents line parameter u.
• GMSURF entry, then
X1 represents surface parameter u and
X2 represents surface parameter v.

Main Index
 1744 DEQATN
Equation Definition

6. If the DEQATN entry is referenced by the GMLOAD, GMBC, TEMPF, GMCURV, or GMSURF
entries and your computer has a short word length (e.g., 32 bits/word), then EQUATION is
processed with double precision and constants may be specified in double precision; e.g., 1.2D0.
If your machine has a long word length (e.g., 64 bits/word) then EQUATION is processed in
single precision and constants must be specified in single precision; e.g., 1.2. 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 MAX and MIN are limited to <100 arguments. If more arguments are desired,
the functions may be concatenated.
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 1745
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

Field Contents
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
 1746 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

Field Contents
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 1747
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

Field Contents
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
 1748 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

Field Contents
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 1749
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

Field Contents
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. For RC network solver in thermal analysis, the S and Si factors are always taken as 1.

Main Index
 1750 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 + iBij ) . 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

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

Main Index
 DMI 1751
Direct Matrix Input

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

Field Contents
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
 1752 DMI
Direct Matrix Input

Field Contents
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 1753
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 8-13.

Table 8-13 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.

Main Index
 1754 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:

DMIAX B2PP 0 1 3 4
DMIAX B2PP 32
1027 3 4.25+6 2.27+3

Field Contents
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 1755
Direct Matrix Input for Axisymmetric Analysis

Field Contents
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.

Remarks:
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 (p. 408) in the MSC Nastran Reference Manual.
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
 1756 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.

Field Contents
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

Main Index
 DMIG 1757
Direct Matrix Input at Points

Field Contents
3 Complex, single precision
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. (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
 1758 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.

Main Index
 DMIG,UACCEL 1759
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
G2 C2 X2 G3 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

Field Contents
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)
Gi 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
 1760 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 (p. 408) in the MSC Nastran Reference Manual 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
 DMIGOUT 1761
DMIG Matrices to be Output from the Marc Portion of SOL 600

DMIGOUT DMIG Matrices to be Output from the Marc Portion of SOL 600

Defines DMIG matrices to be output from the Marc Portion of SOL 600.

Header Entry Format:

1 2 3 4 5 6 7 8 9 10
DMIGOUT ID ISTIFF IDIFF IMASS IDAMP ICOND ISPECIF ISOL
ICTRL IFREQ ICORD KIND AMIN IUSEK IUSEM
IE1 THRU IE2 IE3 THRU IE4

Example:
DMIGOUT 100 1 1 0 0 0 0 103
2 -1 2 2 1.0E-16

Field Contents
ID Subcase for which the reduced matrices will be output. ID must correlate to a
SUBCASE Case Control ID, for example if the Case Control contains SUBCASE 20,
ID would be 20. To output matrices in Marc’s phase zero, etc ID=0. (Integer; Default
= 1, see Remark 11.)
ISTIFF Flag to output stiffness matrices. (Normally contains the differential stiffness and all
other stiffness terms.) (Integer; Default = 0)
0 Do not output the matrix
1 Output the matirx
IDIFF Flag to output differential stiffness matrices. (Only available for buckling analysis or
subcases.) (Integer; Default = 0)
0 Do not output the matrix
1 Output the matrix
IMASS Flag to output mass matrices. (Integer; Default = 0)
0 Do not output the matrix
1 Output the matrix (must be a dynamic analysis)
IDAMP Flag to output damping matrices. (Integer; Default = 0)
0 Do not output the matrix
1 Output the matrix (must be a dynamic analysis)
ICOND Flag to output conductivity matrices. (Integer; Default = 0)
0 Do not output the matrix

Main Index
 1762 DMIGOUT
DMIG Matrices to be Output from the Marc Portion of SOL 600

Field Contents
1 Output the matrix
ISPECIF Flag to output specific heat matrices. (Integer; Default = 0)
0 Do not output the matrix
1 Output the matrix
ISOL Solution sequence to run using the DMIG matrices. (Integer absolute value > 100;
Default = 0, which means do not run any solution sequence using the DMIG’s created
by Marc in this execution). To speed up the solution, use DOMAINSOLVER ACMS
(PARTOPT=DOF) for eigenvalues and set ISOL to the negative value of the solution
sequence desired (–103, -111 or –112).
ICTRL Controls type of matrix. (Integer; Default = 2)
1 Element matrices
2 Global matrices
3 Element and global matrices
IFREQ Controls how often the matrices are output (Integer; no Default)
1 Output at every increment
2 Output every other increment, etc.
3 Output every 3rd increment, etc.
-1 Output only at start of the subcase. (See Remark 12.)
ICORD Controls matrix output coordinate system (Integer; no Default)
1 Nastran basic coordinate system
2 Current transformed coordinate system (at the start of the run, this is the
Nastran global coordinate system)
KIND Controls which elements are written (Integer; Default = 2)
1 A list of elements starting with the 3rd entry will be specified
2 All elements will be written
AMIN Values below AMIN will not be written (Real; Default = 1.0E-15). Values below
AMIN will be skipped.
IUSEK Increment to use in SOL 600 CONTINUE option for the stiffness matrix (if
CONTINUE is specified on the SOL 600 entry). (Integer; Default = -1) Increments
0 to 9999 may be specified. If -1 is specified, the last increment output by Marc will
be used. As an example, the Marc DMIG file for the global stiffness matrix for
increment 10 will have the name jid.marc_cglsti_0020.

Main Index
 DMIGOUT 1763
DMIG Matrices to be Output from the Marc Portion of SOL 600

Field Contents
IUSEM Increment to use in SOL 600 CONTINUE option for the mass matrix (If CONTINUE
is specified on the SOL 600 entry). (Integer, Default = -1) Increments 0 to 9999 may
be specified. If -1 is specified, the last increment output by Marc will be used. As an
example, the Marc DMIG file for the global mass matrix for increment 20 will have
the name jid.marc_cglmas_0020.
IE1, IE3 Starting element number of a range of elements (Integer; no Default) Only enter IE1
is KIND=1
IE2, IE4 Ending element number of a range of elements (Integer; no Default) Only enter IE2
is KIND=1 (IE2 is required if IE1 is entered).

Remarks:
1. The first continuation line is required.
2. The second continuation line should only be entered if KIND=1 and may be repeated as many
times as necessary to define all applicable elements.
3. ICTRL, IFREQ, ICORD, KIND and AMIN apply to all types of matrices to be written for the
subcase.
4. Only one DMIGOUT entry can be entered per subcase. If more than one is entered, only the first
encountered will be used.
5. DMIGOUT entries may be made for each subcase desired.
6. Marc DMIG element output will be in files named jid.marc_dmigXX_inc where XX is shown
below and inc is the increment number.

ST Stiffness Matrices
DF Differential stiffness matrices
MS Mass matrices
DM Damping
CO Conductivity matrices
SP Specific heat matrices

Global matrices are named jid_marc_cglsti_inc.

7. If the SOL 600 CONTINUE options is invoked, Case Control commands and a Bulk Data include
statement to receive the matrices will be automatically added to the original input data file. A
second Nastran execution will be spawned from the original Nastran execution after completion
of the Marc execution.
8. ID may not be 600 or 700 in the Executive Control statement, SOL 600,ID.

Main Index
 1764 DMIGOUT
DMIG Matrices to be Output from the Marc Portion of SOL 600

9. The following Bulk Data parameters are usually required in addition to the DMIGOUT entry:
$2345678x234567890123456x34567890123456
param* mrspawn2 nastcmd
pram,mrmtxnam,KAAX
param,marcfile,nastb.rc
where
a. nastcmd is the name of the command to run the primary and continuation jobs (examples are
nastran, nast2006t1, nast2006t2, etc.)
b. nastb.rc should be changed to the name of the rc file to be used for the continuation run. It
usually will specify mem= with a larger value than that of the primary run and also include a
line bat=no (except for windows systems).
c. PARAM,MARCFILi should not be used.
10. For standard nonlinear static or dynamic analyses the stiffness matrix contains all contributions
including the differential stiffness matrix and it is not possible to obtain the differential stiffness
matrix separately. For a buckling analysis, the differential stiffness matrix may be obtained
separately.
11. To obtain stiffness and mass matrices for SOL 600,103, ID in field 2 of this entry must be must
be zero.
12. If IFREQ is 1 or a small number, the number of matrices output for dynamic analyses
(SOL 600,109 or SOL 600,120) can be extremely large.
13. If ID=0, IFREQ should be 1.
14. Setting IFREQ to a value larger than the actual number of increments in a subcase will produce
no matrices.

Main Index
 DMIGROT 1765
DMIG Matrices for which large rotation in SOL 600

DMIGROT DMIG Matrices for which large rotation in SOL 600

Defines large rotation and other characteristics of a matrix entered using DMIG in SOL 600.

Format for K2GG and K2PP Stiffness DMIG Matrices:

1 2 3 4 5 6 7 8 9 10
DMIGROT Name G1 G2 G3 SCALE ITRAN IACT IDEACT

Format for M2GG and M2PP Mass DMIG Matrices:

DMIGROT Name SCALE IACT

Example:
DMIGROT KAAX 375
DMIGROT KAAY 401 402 403
DMIGROT KAAX 1.25 1 2 5
DMIGROT MAAX 0.001 7 8

Field Contents
Name Name of the DMIG matrix for which large rotation is specified. See Remark 1.
(Character; Required field; no Default)
G1 Grid ID specifying the rotation of the matrix. See Remark 2. (Integer; Required field;
no Default)
G2 Grid ID which combined with G1 and G3 specifies a plane whose rotation provides
the rigid body rotation of the matrix. See Remark 2. (Integer; Default = 0; )
G3 Grid ID which combined with G1 and G2 specifies a plane whose rotation provides
the rigid body rotation of the matrix. See Remark 2. (Integer; Default = 0)
SCALE Scale factor. Each term in the DMIG matrix will be scaled by this value. (Real;
Default = 1.0)
ITRAN Flag indicating whether to transform the DMIG’s or not. (Integer, Default = 0)
0 Do not transform the DMIG matrix.
1 Transform the DMIG using G1, G2, G3 to form the transformation matrix.
IACT Subcase ID for which this DMIG matrix will be activated. See Remark 5. (Integer;
Default = 0).
0 The matrix is active for all subcases.

Main Index
 1766 DMIGROT
DMIG Matrices for which large rotation in SOL 600

Field Contents
N The matrix is activated starting with subcase N
IDEACT Subcase ID for which this DMIG matrix will be deactivated. See Remark 5. (Integer;
no Default; leave blank if the matrix should be active fro the entire analysis or
starting with subcase IACT)

Remarks:
1. All DMIG matrices with the name specified in field 2 will rotate with grids Gi.
2. If G1 has 6 dof it is not necessary to specify G2 or G3 and the DMIG matrix will rotate with the
same rotation as G1. If G1 has fewer that 6 dof, or if it is desired that the DMIG matrix rotation
with a plane defined by G1, G2 and G3, G2 and G3 must be entered and may not all be collinear.
3. If a transformation is to be applied to the stiffness matrix, the DMIG must contain all of the
degrees of freedom associated with the node to which the transformation is applied.
4. This bulk data entry maps to Marc’s K2GG (and K2PP) model definition entry.
5. IACT and IDEACT are ID’s of the Case Control SUBCASE entry.
6. G1, G2, G3 and ITRAN may not be entered for mass matrices.

Main Index
 DMIJ 1767
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

Field Contents
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)

Main Index
 1768 DMIJ
Direct Matrix Input at js-Set of the Aerodynamic Mesh

Field Contents
1 Real, single precision
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 1769
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 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 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
 1770 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

Field Contents
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)

Main Index
 DMIJI 1771
Direct Matrix Input at js-Set of the Interference Body

Field Contents
1 Real, single precision
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 < 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.

Main Index
 1772 DMIJI
Direct Matrix Input at js-Set of the Interference Body

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 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 1773
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

Field Contents
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
 1774 DMIK
Direct Matrix Input at ks-Set of the Aerodynamic Mesh

Field Contents
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
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

Main Index
 DMIK 1775
Direct Matrix Input at ks-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 (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 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 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
 1776 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

Field Contents
PARAMi Name of the design optimization parameter. Allowable names are given in
Table 8-14. (Character)
VALi Value of the parameter. (Real or Integer, see Table 8-14.)

Table 8-14 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 1777
Design Optimization Parameters

Table 8-14 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 ITRMOP consecutive iterations
(see ITRMOP) 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 ITRMOP 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)

Main Index
 1778 DOPTPRM
Design Optimization Parameters

Table 8-14 PARAMi Names and Descriptions (continued)

Name Description, Type, and Default Value
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)
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)

Main Index
 DOPTPRM 1779
Design Optimization Parameters

Table 8-14 PARAMi Names and Descriptions (continued)

Name Description, Type, and Default Value
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
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.

Main Index
 1780 DOPTPRM
Design Optimization Parameters

Table 8-14 PARAMi Names and Descriptions (continued)

Name Description, Type, and Default Value
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 SOL
700 User Defined Services)
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.
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)
P2 > 13 Print design variables for topology, topography, and
topometry optimization
2 Print properties.
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.)

Main Index
 DOPTPRM 1781
Design Optimization Parameters

Table 8-14 PARAMi Names and Descriptions (continued)

Name Description, Type, and Default Value
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.)
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.
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, 707) (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)

Main Index
 1782 DOPTPRM
Design Optimization Parameters

Table 8-14 PARAMi Names and Descriptions (continued)

Name Description, Type, and Default Value
TDMIN Minimum diameter of members in topology optimization. This option is applied
on 2 and 3D elements only. (Real > 0.0)
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 1783
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
 1784 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

Field Contents
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.
5. RC network solver does not support DPHASE for thermal analysis.

Main Index
 DRESP1 1785
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

Field Contents
ID Unique entry identifier. (Integer > 0)
LABEL User-defined label. (Character)
RTYPE Response type. See Table 8-15. (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 8-15. (Integer > 0 or Real or blank)
ATTi

Main Index
 1786 DRESP1
Design Sensitivity Response Quantities

Table 8-15 Design Sensitivity Response Attributes

Response Attributes
Response
Type ATTB (Integer > 0 or
(RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
WEIGHT Row Number Column Number SEIDi or All or blank.
(1 < ROW < 6) (1 < COL < 6) See Remark 12.
See Remark 24.
VOLUME Blank Blank SEIDi or ALL or
blank. See Remark 12.
FRMASS Blank Blank Blank or Property ID
(see Remarks (PID). See Remark 37.
28. & 29.)
COMP (see Blank Blank Blank
Remark 28.)
EIGN Normal Modes Mode Approximation Code. Blank
Number. See Remark 33. See Remark 19.
CEIG Complex Eigenvalue ALPHA or OMEGA Blank
Mode Number. (Default = ALPHA)
(Integer > 0)
FREQ Normal Modes Mode Approximation Code. Blank
Number. See Remark 19.
See Remarks 18. and 33.
LAMA Buckling Mode Number Approximation Code. Blank
See Remark 19.
DISP Displacement Blank or Mode Number Grid ID
Component
STRAIN Strain Item Code Blank or Mode Number Property ID (PID) or
Element ID (EID)
ESE Strain Energy Item Code Blank or Mode Number Property ID (PID) or
See Remark 21. Element ID (EID)
STRESS Stress Item Code Blank or Mode Number Property ID (PID) or
Element ID (EID)
FORCE Force Item Code Blank or Mode Number Property ID (PID) or
Element ID (EID)
FATIGUE Fatigue Item Code. See ID of a FATIGUE case Property ID (PID) or
See Remark Remark 43. control. See Remark 40. Element ID (EID)
39.
SPCFORCE SPC Force Component Blank Grid ID

Main Index
 DRESP1 1787
Design Sensitivity Response Quantities

Table 8-15 Design Sensitivity Response Attributes

Response Attributes
Response
Type ATTB (Integer > 0 or
(RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
CSTRAIN Strain Item Code LAMINA Number or Property ID (PID) or
See Remark GPLYIDi Element ID (EID)
2. (Integer; Default = 1)
CSTRESS Stress Item Code LAMINA Number or Property ID (PID) or
See Remark GPLYIDi Element ID (EID)
2. (Integer; Default = 1)
CFAILURE Failure Indices Item Code LAMINA Number or Property ID (PID) or
See Remark GPLYIDi Element ID (EID)
2. (Integer; Default = 1)
CSTRAT Composite Strength LAMINA Number or Property ID (PID) or
See Remark Ratio Item Code GPLYIDi Element ID (EID)
2. (Integer; Default = 1)
TOTSE Blank Blank or Mode Number SEIDi or All or blank.
(Total Strain See Remark 12.
Energy)
GPFORCE GPFORCE Component Blank Element ID
Code (1-6; see Remark
25.)
GPFORCP Grid Point (see Remark Blank Grid ID connected to
26.) ATTA grid to specify
orientation.
ABSTRESS Arbitrary Beam Stress Blank Property ID (PID) or
Item Code (see Remark Element ID (EID)
30.)
FRDISP Displacement Frequency Value. (Blank; Grid ID
Component Real > 0.0 or Character)
See Remarks 15. and 20.
PRES Acoustic Pressure Frequency Value. (Blank; Grid ID
Component (= 1 or 7) Real > 0.0 or Character)
See Remarks 15. and 20.
FRVELO Velocity Component Frequency Value. (Blank; Grid ID
Real > 0.0 or Character)
See Remarks 15. and 20.
FRACCL Acceleration Component Frequency Value. (Blank; Grid ID
Real > 0.0 or Character)
See Remarks 15. and 20.

Main Index
 1788 DRESP1
Design Sensitivity Response Quantities

Table 8-15 Design Sensitivity Response Attributes

Response Attributes
Response
Type ATTB (Integer > 0 or
(RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
FRSPCF SPC Force Component Frequency Value. (Blank; Grid ID
Real > 0.0 or Character)
See Remarks 15. and 20.
FRSTRE Stress Item Code Frequency Value. (Blank; Property ID (PID) or
Real > 0.0 or Character) Element ID (EID)
See Remarks 15. and 20.
FRFORC Force Item Code Frequency Value. (Blank; Property ID (PID) or
Real > 0.0 or Character) Element ID (EID)
See Remarks 15. and 20.
PSDDISP Displacement Frequency Value. (Blank; Grid ID
Component (see Remarks Real > 0.0 or Character).
27. and 31.) See Remarks 15. and 20.
PSDVELO Velocity Component (see Frequency Value (Blank; Grid ID
Remarks 27. and 31.) Real > 0.0 or Character).
See Remarks 15. and 20.
PSDACCL Acceleration Component Frequency Value. (Blank; Grid ID
(see Remarks 27. and 31.) Real > 0.0 or Character).
See Remarks 15. and 20.
RMSDISP Displacement RANDPS ID Grid ID
Component (see Remark
31.)
RMSVELO Velocity Component (see RANDPS ID Grid ID
Remark 31.)
RMSACCL Acceleration Component RANDPS ID Grid ID
(see Remark 31.)
ACPWR - Blank Frequency value. (Blank Blank
acoustic for all forcing frequency;
power Real > 0.0)
radiated
through a
panel. (See
Remark 34.)
ACINTS - Blank Frequency value. (Blank Grid ID of wetted
acoustic for all forcing frequency; surface.
intensity Real > 0.0)

Main Index
 DRESP1 1789
Design Sensitivity Response Quantities

Table 8-15 Design Sensitivity Response Attributes

Response Attributes
Response
Type ATTB (Integer > 0 or
(RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
AFPRES - Acoustic Pressure Frequency value (Blank Grid ID of AFPMID.
Acoustic Component (Integer = 1 for all forcing frequency;
Intensity for or 7) Real > 0.0)
AFPM. (See
Remark 35.)
AFINTS - Component Code - Frequency value. (Blank Grid ID of AFPMID.
Acoustic 0 - normal to AFPM, for all forcing frequency;
Intensity for 1 - x-dir Real > 0.0)
AFPM. (See 2 - y-dir
Remark 35.) 3 - z-dir
AFVELO - Component Code - Frequency value. (Blank Grid ID of AFPMID.
Velocity for 11 - Real/Mag in x-dir for all forcing frequency;
AFPM. (See 12 - Real/Mag in y-dir Real > 0.0)
Remark 35.) 13 - Real/Mag in z-dir
71 - Img/Ph in x-dir
72 - Img/Ph in y-dir
73 - Img/Ph in z-dir
AFPWR - Blank Frequency value. (Blank Blank
Acoustic for all forcing frequency;
Power for Real > 0.0)
AFPM. (See
Remark 35.)
ERP (See ERP Item Code Frequency Value. (Blank; Set3 ID or Blank
Remarks 41. Real > 0.0 or Character)
and 42.) See Remarks 15. and 20.
TDISP Displacement Time Value. (Blank; Grid ID
Component Real; or Character) See
Remarks 16. and 20.
TVELO Velocity Component Time Value. (Blank; Grid ID
Real, or Character) See
Remarks 16. and 20.
TACCL Acceleration Component Time Value. (Blank; Grid ID
Real, or Character) See
Remarks 16. and 20.
TSPCF SPC Force Component Time Value. (Blank; Grid ID
Real, or Character) See
Remarks 16. and 20.

Main Index
 1790 DRESP1
Design Sensitivity Response Quantities

Table 8-15 Design Sensitivity Response Attributes

Response Attributes
Response
Type ATTB (Integer > 0 or
(RTYPE) ATTA (Integer > 0) Real > 0.0) ATTI (Integer > 0)
TSTRE Stress Item Code Time Value. (Blank; Property ID (PID) or
Real, or Character) See Element ID (EID)
Remarks 16. and 20.
TFORC Force Item Code Time Value. (Blank; Property ID (PID) or
Real, or Character) See Element ID (EID)
Remarks 16. and 20.
STMONP1 Component (see Remark Blank Blank
Structural 36.)
MONPNT1
STMOND1 Component (see Remark Blank Blank
Structural 36.)
MONDSP1
MONPNT3 Component (see Remark Blank Blank
36.)
AEMONP1 Component (see Remark Blank Blank
Aerodynamic 36.)
MONPNT1
AEMOND1 Component (see Remark Blank Blank
Aerodynamic 36.)
MONDSP1
TRIM AESTAT or AESURF Blank Blank
entry ID
STABDER AESTAT or AESURF Restraint Flag. (Integer 0 Component
entry ID or 1) See Remark 13.
FLUTTER Blank Blank See Remark 14.
DIVERG Divergence Root Number Blank Mach No.
(See remark 38.)
WMPID (see MID SEID PID
Remarks 44.
and 45.)

Remarks:
1. Stress, strain, force, fatigue and ERP item codes can be found in Item Codes, 1003. 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).

Main Index
 DRESP1 1791
Design Sensitivity Response Quantities

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, 1003. “CFAILURE” and “CSTRAT” item
codes are described under Table 2 (Element Force Item Codes) in Item Codes, 1003. 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.
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.

Main Index
 1792 DRESP1
Design Sensitivity Response Quantities

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.
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 20. for additional ATTB options. The OFREQ Case Control command has no affect
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.

Main Index
 DRESP1 1793
Design Sensitivity Response Quantities

20. Character input for ATTB is available for RTYPE of “FRXXXX”, “PSDXXXX”, “TXXXX”,
“PRES” and “ERP”. 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

AVG ( X 1, X 2, …, Xn ) =  Xi ⁄ n
i=1

n
2
SSQ ( X 1, X 2, …, Xn ) =  Xi
i =1

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.

21. Element strain energy item codes can be found under Table 6-13 in Item Codes, 1003. Only
element strain energy and element strain energy density can be referenced on a DRESP1 entry.
RTYPE=”ESE” is not supported for shape optimization.
22. For RTYPE=RMSDISP, RMSVELO, or RMSACCL the ATTB specifies the appropriate
RANDPS ID.
23. 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).

Main Index
 1794 DRESP1
Design Sensitivity Response Quantities

24. 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:

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 6×6

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”.
25. 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.
26. 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.
27. For RTYPE = PSDXXXX, the PTYPE field specifies the RANDPS ID.
28. RTYPE=COMP (compliance of structures = P T u ) and FRMASS (mass fraction of topology
designed elements) entries are used for topology optimization or combined topology, sizing/shape
optimization.
29. 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.
30. Response type ABSTRESS is for element type code of 238 (CBAR) and 239 (CBEAM) only.
31. 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.
32. Response types, ESE, TOTSE, GPFORCE and GPFORCP are not supported for shape
optimization.
33. 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’.

Main Index
 DRESP1 1795
Design Sensitivity Response Quantities

34. 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.
35. For RTYPE=AFxxxx, PTYPE field can be utilized to specified the ID of Acoustic Field Point
Mesh, AFPM.
36. For monitor point responses (RTYPE = STMONP1, STMOND1, MONPNT3 AEMONP1 or
AEMOND1) the ATTA field specifies the components to be extracted. These can be any subset
of the integers 1 through 6 that appear on the monitor quantity with the NAME provided in the
PTYPE field. All of these responses can be invoked in a static aeroelastic (ANALYSIS=SAERO)
subcase. 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.
37. 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.
38. RTYPE=DIVERG is for subcases with ANALYSIS=DIVERG (aeroelastic static divergence).
Only a single Mach number can be specified for this RTYPE.
39. For RTYPE = FATIGUE, PTYPE must be set to ELEM or PSOLID, PSHELL, PBAR, PBEAM,
or PWELD. ATTB is the ID of a FATIGUE case control.
40. 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.
41. For the ERP response, the PTYPE field must be ERPPNL.
42. If the ATT1 field is blank for the ERP response, all panels are invoked.
43. Fatigue Item Codes can be found in Fatigue Item Codes, 1060. 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.
44. For the WMPID (weight as a function of material and property ID), the following conventions
apply:
a. ATTA is required, ATTB and ATTi are optional.
b. ATTB specifies the superelement with ATTB=0 indicating the residual, >0, indicates
superelement ATTB and ATTB = ALL or blank means all superelements)

Main Index
 1796 DRESP1
Design Sensitivity Response Quantities

c. 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.
d. If there is no ATTi, all material with MID=ATTA will be used to generate the response.
e. If there are multiple ATTi, a single scalar weight is calculated that is the sum of the all the
properties
f. Materials that are supported with this entry are: MAT1,MAT2, MAT3, MAT8, MAT9 and
MAT10
g. Properties that are supported are: PSHELL, PROD, PBEAM, PTUBE, PSHEAR, PBAR,
PSOLID, PBEND,PCOMP, PCOMPG, PBARL, PBEAML, PBRSECT and PBMSECT.
45. 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 material referenced on the ATTA field cannot be invoked by a property that is referenced
on a TOPVAR entry.
c. The property referenced on the ATTI field cannot also be invoked by a TOMVAR entry.

Main Index
 DRESP2 1797
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

Main Index
 1798 DRESP2
Design Sensitivity Equation Response Quantities

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

Field Contents
ID Unique identification number. (Integer > 0)
LABEL User-defined label. (Character)
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)

Main Index
 DRESP2 1799
Design Sensitivity Equation Response Quantities

Field Contents
“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 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 entries span subcases, the DRSPAN Case Control command is
required to identify DRESP1 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.
c) Referenced DRESP2 entries cannot span subcases or superelements.
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.

Main Index
 1800 DRESP2
Design Sensitivity Equation Response Quantities

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.
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
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 20. of the DRESP1
entry for an explanation of these functions.
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:

Main Index
 DRESP2 1801
Design Sensitivity Equation Response Quantities

DRESP1 10 FDISP1 FRDISP 1 10. 1001

DRESP1 20 FDISP2 FRDISP 1 20. 1001
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 β

γ Xβ – rj
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.
C3 (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
associated with DRESP1s and target values, r Tj , 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 T 2
 rj – rj 
r2 =   --------------
 r Tj 
-
j= 1

When METHOD = BETA, the design task becomes one of minimizing an objective that is the
maximum normalized difference between the analysis and target values
T
rj – rj
---------------
T
rj

Main Index
 1802 DRESP2
Design Sensitivity Equation Response Quantities

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.

Main Index
 DRESP3 1803
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

Main Index
 1804 DRESP3
Design Sensitivity Response using user-supplied routine(s)

201
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.

Field Contents
ID Unique identification number. (Integer > 0)
LABEL User-defined label. (Character)
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)

Main Index
 DRESP3 1805
Design Sensitivity Response using user-supplied routine(s)

Field Contents
“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)
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 (p. 231) in the MSC Nastran 2014 Installation and Operations Guide for a
discussion of how to incorporate external responses.
4. a) Referenced DRESP2 entries cannot span subcases or superelements.
b) If referenced DRESP1 entries span subcases, the DRSPAN Case Control command is required
to identify the DRESP1 IDs for each subcase. DRESP3 entries that span subcases must be invoked
above the subcase level by DESGLB or DESOBJ commands.
c) Referenced DRESP1 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.

Main Index
 1806 DRESP3
Design Sensitivity Response using user-supplied routine(s)

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 1807
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

Field Contents
RTYPE Response type for which the screening criteria apply. See Remark 3. (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.

Main Index
 1808 DSCREEN
Design Constraint Screening Data

7. Constraints can be retained only if they are greater than TRS. See the Remarks under the
DCONSTR, 1731 entry for a definition of constraint value.
8. Constraint screening is applied to each superelement.

Main Index
 DTABLE 1809
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.

Field Contents
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
 1810 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 PSHELLL 10 T MATIE MT1 38 E
CBARX1 CBAR 3888 X1

Field Contents
LABLi Label for the constant. (Character)
PNAMEi Property, material or connection bulk data entry name. (Character)
PIDi ID of PNAMEi entry. (Integer > 0)
FNAMEi Field name of PNAMEi. (Character)

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 utillized along with ‘NASTRAN SYSTEM(444)=1’ in input file or
‘sys444=1’ during job submittal.

Main Index
 DTI 1811
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

Field Contents
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
 1812 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.

Main Index
 DTI,ESTDATA 1813
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

Field Contents
kdi Keyword for estimation parameter. (Character from Table 8-16.)
vdi Value assigned to the estimation parameter kdi. (The type given in Table 8-16.)
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 8-16.)
vi Value for keyword ki. (Type depends on ki as shown in the Table 8-16.)

Main Index
 1814 DTI,ESTDATA
Superelement Estimation Data Overrides

Table 8-16 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
Buffsize (Optional) (p. 7) in the MSC Nastran Reference
Manual.
ML Real Machine M Arithmetic time for the multiply/add loop. See
Loop Time the 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) (p. 7)
in the MSC Nastran Reference Manual.
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 1815
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 8-17 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 
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.

Main Index
 1816 DTI,ESTDATA
Superelement Estimation Data Overrides

• 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 1817
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

Field Contents
Bi Element type identification number. See the table in Item Codes, 1003 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, 1003 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 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, 707. In order to sort force or strain quantities, a DMAP Alter
is required.

Main Index
 1818 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 8-18 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 8-18.
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, 1003.
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 1819
Stress, Strain and/or Force Sort/Filter Item Code Override

Table 8-18 Sortable Elements

Default Stress Output
Quantity and Identification Number
Element Type Stress Code
Element ID Number Quantity ID 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
 1820 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

Field Contents
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 Superelement User’s Guide for a description of user-designated trees.

Main Index
 DTI,SETREE 1821
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 8-92 Sample Superelement Tree

Main Index
 1822 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

Field Contents
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 1823
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

Field Contents
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. See Additional Topics (p. 515) in the MSC Nastran Reference Manual for example problems using
this feature.
5. 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.
6. 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
 1824 DTI,SPSEL
Response Spectra Generation Correlation Table

Main Index
 DTI,UNITS 1825
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), 217 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. Fatigue analysis as performed by MSC Nastran requires the identification of the analysis' stress
units. MSC Nastran is a unitless code and it is therefore up to the user to ensure compatible units
between all interactions. However, during the fatigue analysis, the stresses must be converted to
SI units of MPa. This is because the fatigue material property stress parameters as defined on the
MATFTG entry are internally converted to standard SI units of MPa and 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. If the model units system produces stresses in MPa, then
DTI,UNITS is not necessary or DTI,UNITs should be set to MPa (the default).

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

Main Index
 1826 DTI,UNITS
Unit Definitions

Mass Force Length Time Stress*

OZM - ounce- DYNE - dyne MI - mile US - microsecond PSF - pound
mass per square foot
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 MN - millinewton UM - micrometer BAR - bar
slugs
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.

Main Index
 DVBSHAP 1827
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

Field Contents
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
 1828 DVCREL1
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

Field Contents
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 DVIDi
i

2. The continuation entry is required.

Main Index
 DVCREL1 1829
Design Variable to Connectivity Property Relation

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. 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
 1830 DVCREL2
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

Field Contents
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
 DVCREL2 1831
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
 1832 DVGRID
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

Field Contents
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 =  COEFF j ( XDVIDj – XDVIDj ) { N } j
j

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 ] T is determined from CID and Ni. Note that it is a change in a design
variable from its initial value X 0 , and not the absolute value of the design variable itself, that
represents a change in a grid point location, { g } i – { g } 0i .
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

{ Δg } i =  { T } ij ⋅ ΔXj
j

Main Index
 DVGRID 1833
Design Variable to Grid Point Relation

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
 1834 DVLREL1
Defines the linear relation between analysis model loading and design variables

DVLREL1 Defines the linear relation between analysis model loading and
design variables

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

Field Contents
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 Table 8.x (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:
Li = C0 +  COEFF i X DVIDi

Main Index
 DVLREL1 1835
Defines the linear relation between analysis model loading and design variables

2. Supported TYPEs and their ATTi meaning are given in the following table:

Load LNAME ATT1 ATT2 ATT3 ATT4 ATT5

Type (character) (integer) (integer) (integer) (integer) (integer)
FORCE F, N1, N2 or G CID
N3
(see remark 6)
LOAD S or Si 0 if LNAME
is S, Li
otherwise
MOMENT M, N1, N2 or G CID (see
N3 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.

Main Index
 1836 DVMREL1
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

Field Contents
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 DVIDi
i

2. The continuation entry is required.

Main Index
 DVMREL1 1837
Design Variable to Material Relation

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, 1075 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.
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
 1838 DVMREL2
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

Field Contents
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
 DVMREL2 1839
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, 1075 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
 1840 DVPREL1
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

Field Contents
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:

Pj = C0 +  COEF i ⋅ X DVIDi
i

2. The continuation entry is required.

3. TYPE=“PBEND” is not supported. TYPE=“PBEAML” supports only PNAME and not FID.

Main Index
 DVPREL1 1841
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 8-19 shows several examples.

Table 8-19
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
 1842 DVPREL2
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

Field Contents
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)

Main Index
 DVPREL2 1843
Design Variable to Property Relation

Field Contents
“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)

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 8-20 shows
one example.

Table 8-20
Property
PTYPE 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
 1844 DVSHAP
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

Field Contents
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 700 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
 DVPSURF 1845
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

Field Contents
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
 1846 DYCHANG
SOL 700 restart analysis to change solution options

DYCHANG SOL 700 restart analysis to change solution options

For an SOL 700 restart analysis, change certain solution options.

Format BOUNDARY:
Defines an arbitrary number of entries giving the nodal ID and the additional translational displacement
boundary condition code. Previous boundary condition codes will continue to be imposed, i.e., a fixed
node cannot be freed with this option. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DYCHANG ID “BOUNDARY
”
BCC
C1 C2 THRU C3 BY C4

Example:
DYCHANG 101 BOUNDARY 12
101 102 THRU 112

Field Contents
ID Identification number of the DYCHANG entry – Not presently used. (Integer)
“BOUNDARY” Change the displacement boundary condition. (Character; Required)
BCC New translational boundary condition:

Component number of global coordinate (any unique combination of the digits

1 through 3 with no embedded blanks). Combinations are allowed, e.g., 12,
123. (Integer; Required)
Ci Nodal point ID. THRU indicates a range of grid points. BY is the increment to
be used within this range. (Integer; Required)

Alternate Formats and Examples:

Format RBCNSTR:
Allows translational and rotational boundary conditions on a rigid body to be changed. Also, see
RBE2D.

Main Index
 DYCHANG 1847
SOL 700 restart analysis to change solution options

Format:

1 2 3 4 5 6 7 8 9 10
DYCHANG ID “RBCNSTR” PID BCC

Example:
DYCHANG 101 RBCNSTR 200 1245

Field Contents
ID Identification number of the DYCHANG entry – Not presently used. (Integer)
“RBCNSTR” Change translational and rotational boundary conditions on a rigid body
(Character; Required)
PID Property ID of the rigid body. (Integer; Required)
BCC Translational and rotational constraint:

Component number of global coordinate (any unique combination of the digits 1

through 6 with no embedded blanks). Combinations are allowed, e.g., 12, 456.
(Integer; Required)

Format TABLED1:
Allows a load curve to be redefined. The new load curve must contain the same number of points as the
curve it replaces. The curve should be defined in a TABLED1. Any offsets and scale factors are ignored.

Format:

1 2 3 4 5 6 7 8 9 10
DYCHANG ID “TABLED1” LCID

Example:
DYCHANG 101 TABLED1 1000

Field Contents
ID Identification number of the DYCHANG entry – Not presently used. (Integer)
LCID Load curve ID. (Integer; Required)
“TABLED1” Redefine a load curve. (Character; Required)

Main Index
 1848 DYCHANG
SOL 700 restart analysis to change solution options

Format VELND:
Allow the velocity of nodal points to be changed at restart. Undefined nodes will have their nodal
velocities reset to zero if OPTION is blank. However, if OPTION=ONLY, then only the specified nodes
will have their nodal velocities modified.

Format:

1 2 3 4 5 6 7 8 9 10
DYCHANG ID “VELND” OPTION
VX VY VZ VXR VYR VZR
C1 C2 THRU C3 BY C4

Example:
DYCHANG 101 VELND ONLY
50.
1101 1105 THRU 1290 BY 1

Field Contents
ID Identification number of the DYCHANG entry – Not presently used. (Integer)
“VELND” Change the velocity of nodal points. (Character; Required)
OPTION BLANK Undefined nodes have their nodal velocities reset to zero
ONLY Only the specified nodes have their nodal velocities modified.
(Character)
VX Translational velocity in x-direction. (Real; Default = 0.0).
VY Translational velocity in y-direction. (Real; Default = 0.0).
VZ Translational velocity in z-direction. (Real; Default = 0.0).
VXR Rotational velocity about the x-axis. (Real; Default = 0.0).
VYR Rotational velocity about the y-axis. (Real; Default = 0.0).
VZR Rotational velocity about the z-axis. (Real; Default = 0.0).
Ci Nodal point ID. THRU indicates a range of grid points. BY is the increment to be
used within this range. (Integer; Required)

Remark:
If both VELND and VELZERO options are defined then all velocities will be reset to zero.

Format VELZERO:
Resets the velocities to zero at the start of the restart. For this option, no any further input is necessary.

Main Index
 DYCHANG 1849
SOL 700 restart analysis to change solution options

Format:

1 2 3 4 5 6 7 8 9 10
DYCHANG ID “VELZERO”

Example:
DYCHANG 101 VELZERO

Field Contents
ID Identification number of the DYCHANG entry – Not presently used (Integer)
“VELZERO” Resets the velocities to zero at the start of the restart (Character; Required)

Format VELRB:
Allows the velocity components of a rigid body to be changed at restart.

Format:

1 2 3 4 5 6 7 8 9 10
DYCHANG ID “VELRB” PID
VX VY VZ VXR VYR VZR

Example:
DYCHANG 101 VELRB 400
60.

Field Contents
ID Identification number of the DYCHANG entry – Not presently used (Integer)
“VELRB” Change the velocity components of a rigid body (Character; Required)
PID Property ID of rigid body (Integer; Required)
VX Translational velocity in x-direction. (Real; Default = 0.0).
VY Translational velocity in y-direction. (Real; Default = 0.0).
VZ Translational velocity in z-direction. (Real; Default = 0.0).
VXR Rotational velocity about the x-axis. (Real; Default = 0.0).
VYR Rotational velocity about the y-axis. (Real; Default = 0.0).
VZR Rotational velocity about the z-axis. (Real; Default = 0.0).

Main Index
 1850 DYCHANG
SOL 700 restart analysis to change solution options

Remarks:
1. Rotational velocities are defined about the center of mass of the rigid body.
2. Rigid bodies not defined in this section will not have their velocities modified.

Main Index
 DYDELEM 1851

DYDELEM

Deletes properties or element using a list for SOL 700 restarts. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DYDELEM ID TYPE
C1 C2 THRU C3 BY C4

Example 1:
DYDELEM 101 BEAM
1 2

Example 2:
DYDELEM 102 SHELL
7103 7104 THRU 7166 BY 2

Field Contents
ID Identification number of the DYDELEM entry – Not presently used. (Integer)
TYPE BEAM, SHELL, SOLID, TSHELL, PROP, or CONTACT. (Character; Required)
Ci Element ID, Property ID, or CONTACT ID. THRU indicates a range of elements
or properties. BY is the increment to be used within this range. See Remark 1
(Integer; Required)

Remarks:
1. For TYPE=Contact, Contact ID indicates the order of contact pairs in BCTABLE. For example,
there are three contact definitions in BCTABLE.
BCTABLE,1,…
+,SLAVE,1,…
+,MASTER,2,…
+,SLAVE,3,…
+,MASTER,4,…
+,SLAVE,5,…
+MASTER,6…
To remove the second pair (SLAVE=3 and MASTER=4) in the restart run, please set C1 to "2".

Main Index
 1852 DYFSISW
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

Field Contents
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
 DYPARAM,AXIALSYM 1853
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

Option Contents
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)

Main Index
 1854 DYPARAM,AXIALSYM
Axial Symmetric Analyses - SOL 700

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 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 1855
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.

Option Contents
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
 1856 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

Option Contents
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,ELDLTH 1857

DYPARAM,ELDLTH

Print initial time step sizes for elements in the first cycle in SOL 700.

Format:
DYPARAM,ELDLTH,<value>

Example:
DYPARAM,ELDLTH,1

Option Contents
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
 1858 DYPARAM,EULERCB
Euler Domain Decomposition Control

DYPARAM,EULERCB Euler Domain Decomposition Control

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

Option Contents
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 1859
Euler Cube Partition Control

DYPARAM,EULERPR Euler Cube Partition Control

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

Option Contents
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.

Main Index
 1860 DYPARAM,EULERPR
Euler Cube Partition Control

4. Only supports Euler domains created by MESH,BOX. Limitations are:

• No MESH,ADAPT and 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.
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 1861
Switch for Euler Transport Scheme of the Multi-Material Solver and the Single Material Strength Solver

DYPARAM,EULTRAN Switch for Euler Transport Scheme of the

Multi-Material Solver and the Single Material
Strength Solver

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

Option Contents
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

Main Index
 1862 DYPARAM,EULTRAN
Switch for Euler Transport Scheme of the Multi-Material Solver and the Single Material Strength Solver

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
 DYPARAM,EUSUBMAX 1863

DYPARAM,EUSUBMAX

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

Option Contents
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.

Main Index
 1864 DYPARAM,EUSUBMAX

Option Contents
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.

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
 DYPARAM,FASTCOUP 1865
Fast Coupling Algorithm

DYPARAM,FASTCOUP Fast Coupling Algorithm

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

Option Contents
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.
NOCHKEUL No checking
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
 1866 DYPARAM,FASTCOUP
Fast Coupling Algorithm

Option Contents
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 1867
Hydro Body Force

DYPARAM,HYDROBOD Hydro Body Force

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.

Option Contents
XACC X-acceleration (Real; Default = 0.0)
YACC Y-acceleration. (Real; Default = 0.0)
ZACC Z-acceleration. (Real; Default = 0.0)

Remark:
This parameter defines a constant body force load in Euler for single hydro material only.

Main Index
 1868 DYPARAM,JWLDET
Hydro Body Force

DYPARAM,JWLDET Hydro Body Force

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

Option Contents
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
 DYPARAM,LIMITER 1869
Original Roe-Type Euler Solver Scheme

DYPARAM,LIMITER Original Roe-Type Euler Solver Scheme

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

Option Contents
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
 1870 DYPARAM,LSDYNA,ACCURACY

DYPARAM,LSDYNA,ACCURACY

Define control parameters that can improve the accuracy of the calculation in SOL 700.

Format:
DYPARAM,LSDYNA,ACCURACY,[option],<value>

Example:
DYPARAM,LSDYNA,ACCURACY,OSU,1

Option Contents Type Default

OSU Global flag for 2nd order objective stress updates (ssee I>0 0
Remark 1.) Generally, for explicit calculations only those parts
of the model undergoing large rotations, such as rolling tires,
need this option. Objective stress updates can be activated for a
subset of property IDs by defining the property sets in columns
21-30.

0 Off
1 On
INN Invariant node numbering for shell and solid elements (See I
Remarks 2., 3., and 4.)

-4: On for both shell and solid elements except triangular shells
-2: On for shell elements except triangular shells
1: Off
2: On for shell elements only
3: On for solid elements only
4: On for both shell and solid elements
PIDOSU BCPROP ID for objective stress updates. If this set ID is given I>0 0
only those property IDs listed will use the objective stress
update; therefore, OSU is ignored.

Remarks:
1. Second order objective stress updates are occasionally necessary. Some examples include
spinning bodies such as turbine blades in a jet engine, high velocity impacts generating large
strains in a few time steps, and large time step sizes due to mass scaling in metal forming. There
is a significantly added cost which is due in part to the added cost of the second order terms in the
stress update when the Jaumann rate is used and the need to compute the strain-displacement
matrix at the mid-point geometry. This option is available for one point brick elements, the

Main Index
 DYPARAM,LSDYNA,ACCURACY 1871

selective-reduced integrated brick element which uses eight integration points, the fully
integrated thick shell element, and the following shell elements: Belytschko-Tsay, Belystchko-
Tsay with warping stiffness, Belytschko-Chiang-Wong, S/R Hughes-Liu, and the type 16 fully
integrated shell element.
2. Invariant node numbering for shell elements affects the choice of the local element shell
coordinate system. The orientation of the default local coordinate system is based on the shell
normal vector and the direction of the 1-2 side of the element. If the element numbering is
permuted, the results will change in irregularly shaped elements. With invariant node numbering,
permuting the nodes shifts the local system by an exact multiple of 90 degrees. In spite of its
higher costs [<5%], the invariant local system is recommended for several reasons. First, element
forces are nearly independent of node sequencing; secondly, the hourglass modes will not
substantially affect the material directions; and, finally, stable calculations over long time periods
are achievable.
3. Invariant node numbering for solid elements is available for anisotropic materials only. This
option has no effect on solid elements of isotropic material. This option is recommended when
solid elements of anisotropic material undergo significant deformation.
4. The default for explicit analysis is 1. For implicit analysis (see SPRBCK or PRESTRS) the default
is 2.

Main Index
 1872 DYPARAM,LSDYNA,BINARY

DYPARAM,LSDYNA,BINARY

Bulk Data parameters for SOL 700 only.

Format:
DYPARAM,LSDYNA,BINARY,TYPE,DT,TDT,BEAM,NPLTC,

Example:
DYPARAM,LSDYNA,BINARY,D3PLOT,.002, ,2,0.01

Option Contents
TYPE Type of Output File
BLSTFOR Set default for output request for blast pressure data
D3PLOT Set defaults for output request for complete output states.
D3THDT Set defaults for output requests for time history of subsets.
INTFOR Set defaults for output of contact interface data.
D3CRACK Dt for output of an ASCII "aea_crack" data file and d3crack file for the
Winfrith concrete model (MATD084). It's used by LS-PrePost together
with the D3PLOT database to display cracks in the deformed Winfrith
concrete materials.
DT Time interval between outputs.
TDT Optional TABLED1 ID specifying time interval between dumps. This option is only
available to TYPEs: D3THDT and INTFOR
BEAM Option flag for TYPE D3PLOT.
0 Discrete springs and damper elements are added to the D3PLOT
database where they are displayed as beams. The element global X, Y, Z
and the resultant forces are written to the database.
1 No discrete springs and damper elements are added to the D3PLOT
database
2 Discrete springs and damper elements are added to the D3PLOT
database where they are displayed as beams. The element resultant force
is written to its first database position.
NPLTC DT ENDTIME/NPLTC and applies only to TYPE=D3PLOT and will
override the DT specified on field 5.

Main Index
 DYPARAM,LSDYNA,BINARY 1873

Remark:
When TYPE(D3PLOT)=D3PLOT or TYPE(D3THDT)=D3THDT is used to specify the output
frequency of the D3PLOT or D3THDTfile it will overwrite the DT setting of
DYPARAM,LSDYNA,BINARY.

Main Index
 1874 DYPARAM,LSDYNA,CONTACT

DYPARAM,LSDYNA,CONTACT

Changes the defaults for computation with contact surfaces. Used in SOL 700 only.

Format:
DYPARAM,LSDYNA,CONTACT,option,value

Example:
DYPARAM,LSDYNA,CONTACT,SLSFAC,0.5

Option Contents
SLSFAC Scale factor for sliding interface penalties. (Real > 0.; Default = .1).
RWPNAL Scale factor for rigid wall penalties, which treat nodal points interacting with rigid
walls, RWPNAL. The penalties are set so that an absolute value of unity should be
optimal; however, this penalty value may be very problem dependent. If
rigid/deformable materials switching is used, this option should be used if the
switched materials are interacting with rigid walls. (Real; Default = 0.0)
< 0.0 All nodes are treated by the penalty method. This is required for implicit
calculations. Since seven (7) variables are stored for each slave node, only
the nodes that may interact with the wall should be included in the node list.
0.0 The constraint method is used and nodal points which belong to rigid bodies
are not considered.
> 0.0 Rigid bodies nodes are treated by the penalty method and all other nodes are
treated by the constraint method.
ISLCHK Initial penetration check in contact surfaces with indication of initial penetration in
output files. See Remarks. (Integer > 0.; Default = 1)
1 No checking
2 Full check of initial penetration is performed.
SHLTHK Shell thickness considered in type surface to surface and node to surface type contact
options, where options 1 and 2 below activate the new contact algorithms. The
thickness offsets are always included in single surface, constraint method, and
automatic surface to surface and node to surface contact types. See Remarks. (Integer
> 0; Default = 0.)
0 Thickness is not considered,
1 Thickness is considered but rigid bodies are excluded,
2 Thickness is considered including rigid bodies.
PENOPT Penalty stiffness value option. (Integer > 0; Default =1.)

Main Index
 DYPARAM,LSDYNA,CONTACT 1875

Option Contents
1 Minimum of master segment and slave node (default for most contact types),
2 Use master segment stiffness (old way),
3 Use slave node value
4 Use slave node value, area or mass weighted
5 Same as 4 but inversely proportional to the shell thickness. This may require
special scaling and is not generally recommended.
Options 4 and 5 can be used for metalforming calculations.
THKCHG Shell thickness changes considered in single surface contact. (Integer > 0; Default =
0.)
0 No consideration
1 Shell thickness changes are included.
ORIE Optional automatic reorientation of contact interface segments during
N initialization. (Integer > 0.; Default =1.)
1 Active for automated (part) input only. Contact surfaces are given by
BCPROP definitions.
2 Active for manual (segment) and automated (part) input.
3 Inactive for non-forming contact.
4 Inactive for forming contact.
ENMASS Treatment of the mass of eroded nodes in contact. This option affects all contact
types where nodes are removed after surrounding elements fail. Generally, the
removal of eroded nodes makes the calculation more stable; however, in problems
where erosion is important the reduction of mass will lead to incorrect results.
(Integer > 0.; Default =0.)
0 Eroding nodes are removed from the calculation.
1 Eroding nodes of solid elements are retained and continue to be active in
contact.
2 The eroding nodes of solid and shell elements are retained and continue to
be active in contact.
NSBCS Number of cycles between contact searching using three dimensional bucket
searches. Defaults recommended. (Integer > 0. Default = differs for METHOD)
INTERM Flag for intermittent searching in old surface-to-surface contact using the interval
specified as NSBCS above. (Integer > 0; Default =0.)
0 Off
1 On

Main Index
 1876 DYPARAM,LSDYNA,CONTACT

Option Contents
XPENE Contact surface maximum penetration check multiplier. If the small penetration
checking option, PENCHK, is active, then nodes whose penetration then exceeds the
product of XPENE and the element thickness are set free. (Real > 0.0.; Default = 4.0)
SSTHK Flag for using actual shell thickness in single surface contact. See Remarks 1. and 2.
(Integer > 0; Default = 0.)
0Actual shell thickness is not used in the contacts.
1 Actual shell thickness is used in the contacts. (sometimes recommended for
metal forming calculations).
ECDT Time step size override for eroding contact: (Integer > 0; Default = 0.)
0 Contact time size may control Dt.
1 Contact is not considered in Dt determination.
TIEDPRJ Bypass projection of slave nodes to master surface in METHOD=TIEDNS, TIEDES
and TIEDSS. (Integer > 0; Default = 0.)
0 Eliminate gaps by projection nodes
1 Bypass projection. Gaps create rotational constraints which can
substantially affect results.
SFRIC Default static coefficient of friction. (Real > 0; Default = 0.0)
DFRIC Default dynamic coefficient of friction. (Real > 0; Default = 0.0)
EDC Default exponential decay coefficient. (Real > 0; Default = 0.0)
VFC Default viscous friction coefficient. (Real > 0; Default = 0.0)
TH Default contact thickness. (Real > 0; Default = 0.0)
TH_SF Default thickness scale factor. (Real > 0; Default = 0.0)
PEN_SF Default local penalty scale factor. (Real > 0; Default = 0.0)
IGNORE Ignore initial penetrations in the AUTO=YES options. “Initial” in this context refers
to the first timestep that a penetration is encountered. The value defined here will be
the default for IGNORE on the BCTABLE or BCONPRG entries. (Integer > 0;
Default = 0)
0 Move nodes to eliminate initial penetrations in the model definition.
1 Allow initial penetrations to exist by tracking the initial penetrations.
2 Allow initial penetrations to exist by tracking the initial penetrations.
However, penetration warning messages are printed with the original
coordinates and the recommended coordinates of each slave node given.
FRCENG Flag to activate the calculation of frictional sliding energy: (Integer > 0; Default = 0.)
0 Do not calculate

Main Index
 DYPARAM,LSDYNA,CONTACT 1877

Option Contents
1 Calculate frictional energy in contact and store as “Surface Energy Density”
in the binary INTFOR file. Convert mechanical frictional energy to heat
when doing a coupled thermal-mechanical problem. When PKP_SEN=1 on
the keyword card PARAM, LSDYNA, DB-EXTENT, BINARY, it is
possible to identify the energies generated on the upper and lower shell
surfaces, which is important in metal forming applications.
SKIPRWG Flag not to display stationary rigid wall by default. (Integer > 0; Default = 0.)
0 Generate 4 extra nodes and 1 shell element to visualize stationary planar
rigid wall.
1 Do not generate stationary rigid wall.
OUTSEG Flag to output each beam spot weld slave node and its master segment for
METHOD=SPOTWELD and SPOTWTOR into the D3HSP file. (Integer > 0;
Default = 0)
0 Do, do not write out this information.
1 Yes, write out this information.
SPOTSTP If a spot weld node or face, which is related to a MATDSWx beam or solid element,
respectively, cannot be found on the master surface, should an error termination
occur? (Integer > 0; Default = 0)
0 No, continue calculation,
1 Yes, print error message and terminate,
2 No, delete unconstrained weld and continue calculation.
SPOTDEL If the nodes of a spot weld beam or solid element are attached to a shell element that
fails and are deleted, then the attached spot weld element is deleted if this flag is on.
There is a small cost penalty related to this option on non-vector processors. On
vector processors, however, this option can significantly slow down the calculation
if many weld elements fail since the vector lengths are reduced. (Integer > 0; Default
= 0)
0 No, do not delete the spot weld beam or solid element,
1 Yes, delete the weld elements when the attached shells on one side of the
element fail.
SPOTHIN Real: 0.0 < SPOTHIN < 1.0. Optional thickness scale factor. Premature failure of
spot welds can occur due to contact of the spot welded parts in the vicinity of the spot
weld. This contact creates tensile forces in the spot weld. Although this seems
physical, the compressive forces generated in the contact are large enough to fail the
weld in tension before failure is observed in experimental test. With this option, the
thickness of the parts in the vicinity of the weld are automatically scaled, the contact
forces do not develop, and the problem is avoided. We recommend setting the
IGNORE option to 1 or 2 if SPOTHIN is active. This option applies only to the single
surface contact with AUTO=YES and ADAPT=NO.

Main Index
 1878 DYPARAM,LSDYNA,CONTACT

Option Contents
ISYM Symmetry plane option default for automatic segment generation when contact is
defined by BCPROP: (Integer > 0; Default = 0)
0 Off
1 Do not include faces with normal boundary constraints (e.g., segments of
brick elements on a symmetry plane).
This option is important to retain the correct boundary conditions in the model with
symmetry.
NSEROD Flag to use one-way node to surface erosion. (Integer > 0; Default = 0)
0 Use two-way algorithm
1 Use one-way algorithm
RWGAPS Flag to add rigid wall gap stiffness, see parameter RWGDTH below. (Integer > 0;
Default = 1.)
1 Add gap stiffness
2 Do not add gap stiffness
RWGDTH Death time for gap stiffness. After this time the gap stiffness is no longer added.
(Real > 0; Default = 0.0)
RWKSF Rigid wall penalty scale factor for contact with deformable parts during prestress
calculations (see PRESTRS). This value is independent of SLSFAC and RWPNAL.
If RWKSF is also specified in WALL, the stiffness is scaled by the product of the two
values. (Real > 0; Default = 1.0)
SWRADF Spot weld radius scale factor for neighbor segment thinning. The radius of beam spot
welds are scaled by SWRADF when searching for close neighbor segments to thin.
If 0.0 neighbor segments are not thinned. (Real > 0; Default = 0.0.)
ITHOFF Flag for offsetting thermal contact surfaces for thick thermal shells. (Integer > 0.;
Default = 0.)
0 No offset, if thickness is not included in the contact the heat will be
transferred between the mid-surfaces of the corresponding contact segments
(shells).
1 Offsets are applied so that contact heat transfer is always between the outer
surfaces of the contact segments (shells).
SHLEDG Flag for assuming edge shape for shells when measuring penetration. This is
available for segment based contact (see SOFT on BCTABLE or BCONPRG).
(Integer > 0; Default = 0.)
0 Shell edges are assumed round,
1 Shell edges are assumed square and are flush with nodes.

Main Index
 DYPARAM,LSDYNA,CONTACT 1879

Remarks:
1. The shell thickness change option must be activated in PARAM,DYSHTHICK and a nonzero flag
specified for SHLTHK above before the shell thickness changes can be included in the surface-
to-surface contact types. An additional flag must be set, see THKCHG above, if thickness
changes are included in the single surface contact algorithms. The contact algorithms that include
the shell thickness are relatively recent and are now fully optimized and parallelized. The
searching in these algorithms is considerably more extensive and therefore slightly more
expensive.
2. In the single surface contacts and contacts with METHOD=GENERAL or INTERIOR, the
default contact thickness is taken as the smaller of two values -- the shell thickness or 40% of the
minimum edge length. This may create unexpected difficulties if it is the intent to include
thickness effects when the in-plane shell element dimensions are less than the thickness. The
default is based on years of experience where it has been observed that sometimes rather large
nonphysical thicknesses are specified to achieve high stiffness values. Since the global searching
algorithm includes the effects of shell thicknesses, it is possible to slow the searches down
considerably by using such nonphysical thickness dimensions.
3. The initial penetration check option is always performed regardless of the value of ISLCHK. If
removal of initial penetrations is not wanted, set the contact birth time so that the contact is not
active at time 0.
4. Automatic reorientation requires offsets between the master and slave surface segments. The
reorientation is based on segment connectivity and, once all segments are oriented consistently
based on connectivity, a check is made to see if the master and slave surfaces face each other
based on the right hand rule. If not, all segments in a given surface are reoriented. This procedure
works well for non-disjoint surfaces. If the surfaces are disjoint, the AUTO=YES contact options,
which do not require orientation, are recommended. In the FORMING contact options automatic
reorientation works for disjoint surfaces.
5. If SPOTHIN is greater than zero and SWRADF is greater than zero, a neighbor segment thinning
option is active. The radius of a beam spot weld is scaled by SWRADF, and then a search is made
for shell segments that are neighbors of the tied shell segments that are touched by the weld but
not tied by it.

Main Index
 1880 DYPARAM,LSDYNA,DBEXTENT

DYPARAM,LSDYNA,DBEXTENT

Specify output files to be written in SOL 700.

Format:
DYPARAM,LSDYNA,DBEXTENT,[option],<value>

Example:
DYPARAM,LSDYNA,DBEXTENT,NEIPH,4

Option Contents Type Default

NEIPH Number of additional integration point history variables I>0 0
written to the binary database for solid elements. The
integration point data is written in the same order that it is
stored in memory-each material model has its own history
variables that are stored. For user defined materials it is
important to store the history data that is needed for plotting
before the data which is not of interest. The values are
various depending on the material type.
NEIPS Number of additional integration point history variables I>0 0
written to the binary database for both shell and thick shell
elements for each integration point, see NEIPH above. The
values are various depending on the material type.
MAXINT Number of shell integration points written to the binary I 3
database. If the default value of 3 is used then results are
output for the outermost (top) and innermost (bottom)
integration points together with results for the neutral axis.
If MAXINT is set to 3 and the element has 1 integration
point then all three results will be the same. If a value other
than 3 is used then results for the first MAXINT integration
points in the element will be output. Note: If the element
has an even number of integration points and MAXINT is
not set to 3 then you will not get mid-surface results. See
Remarks. If MAXINT is set to a negative number,
MAXINT integration points are output for each in plane
integration point location and no averaging is used. This can
greatly increase the size of the binary databases D3PLOT.

Main Index
 DYPARAM,LSDYNA,DBEXTENT 1881

Option Contents Type Default

STRFLG Set to 1 to dump strain tensors for solid, shell and thick shell I > 0 0
elements and ASCII file ELOUT. For shell and thick shell
elements two tensors are written, one at the innermost and
one at the outermost integration point. For solid elements a
single strain tensor is written
SIGFLG Flag for including stress tensor in the shell D3PLOT I>1 1
database:

1: include,
2: exclude
EPSFLG Flag for including the effective plastic strains in the shell I>1 1
D3PLOT database:

1: include,
2: exclude
RLTFLG Flag for including stress resultants in the shell D3PLOT I>1 1
database:

1: include,
2: exclude
ENGFLG Flag for including shell internal energy density and I>1 1
thickness in the D3PLOT database:

1: include,
2: exclude
CMPFLG Orthotropic and anisotropic material stress and strain output I > 0 0
in local material coordinate system for solids, shells and
thick shells.

0: Global,
1: Local

This option applies to materials MATD022, MATD023,

MATD033, MATD034, MATD036, MATD040,
MATD041-50, MATD054-56, MATD058, MATD059,
MATD103, MATD116, and MATD194. It specifically does
not apply to material MATD002.
IEVERP Every plot state for “d3plot” database is written to a separate I > 0 0
file. This option will limit the database to 1000 states:

0: more than one state can be on each plotfile,

1: one state only on each plotfile

Main Index
 1882 DYPARAM,LSDYNA,DBEXTENT

Option Contents Type Default

BEAMIP Number of beam integration points for output. This option I>0 0
does not apply to beams that use a resultant formulation
DCOMP Data compression to eliminate rigid body data: I>1 1

1: off, no rigid body data compression,

2: on, rigid body data compression active,

3: off, no rigid body data compression, but nodal velocities

and accelerations are eliminated from the database.

4: on, rigid body data compression active and nodal

velocities and accelerations are eliminated from the
database
SHGE Output shell hourglass energy density: I>1 1

1: off, no hourglass energy written,

2: on
STSSZ Output shell element time step, mass, or added mass: I >1 1

1: off,
2: output time step size,
3: output mass, added mass, or time step size.
See Remark 3. below
N3THDT Material energy write option for D3THDT database I >1 2

1: off, energy is NOT written to D3THDT database,

2: on, energy is written to D3THDT database

Remarks:
1. If MAXINT is set to 3 then mid-surface, inner-surface and outer-surface stresses are output at the
center of the element to the D3PLOT database. For an even number of integration points, the
points closest to the center are averaged to obtain the midsurface values. If multiple integration
points are used in the shell plane, the stresses at the center of the element are found by computing
the average of these points. For MAXINT equal to 3 the solver assumes that the data for the user
defined integration rules are ordered from bottom to top even if this is not the case. If MAXINT
is not equal to 3, then the stresses at the center of the element are output in the order that they are
stored for the selected integration rule. If multiple points are used in plane the stresses are first
averaged.
2. Beam stresses are output to the D3PLOT database if and only if BEAMIP is greater than zero. In
this latter case the data that is output is written in the same order that the integration points are
defined. The data at each integration point consists of the following five values for elastic-plastic
Hughes-Liu beams: the normal stress, σrr; the transverse shear stresses, σrs and σtr; the effective

Main Index
 DYPARAM,LSDYNA,DBEXTENT 1883

plastic strain, and the axial strain which is logarithmic. For beams that are not elastic-plastic, the
first history variable, if any, is output instead of the plastic strain. For the beam elements of
Belytschko and his co-workers, the transverse shear stress components are not used in the
formulation. No data is output for the Belytschko-Schwer resultant beam.
3. If mass scaling is active, the output of the time step size reveals little information about the
calculation. If global mas scaling is used for a constant time step, the total element mass is output;
however, if the mass is increased so that a minimum time step size is maintained (DT2MS is
negative), the added mass is output. Also, see DYPARAM,LSDYNA,TIMESTEP.

Main Index
 1884 DYPARAM,LSDYNA,ENERGY

DYPARAM,LSDYNA,ENERGY

Provide controls for energy dissipation options. Used in SOL 700 only.

Format:
DYPARAM,LSDYNA,ENERGY,option,value

Example:
DYPARAM,LSDYNA,ENERGY,HGEN,2

Option Contents
HGEN Hourglass energy calculation option. This option requires significant additional
storage and increases cost by ten percent:
1 Hourglass energy is not computed (Default),
2 Hourglass energy is computed and included in the energy balance. The
hourglass energies are reported in GLSTAT and MATSUM, see DYTIMHS
RWEN Stonewall energy dissipation option:
1 Energy dissipation is not computed,
2 Energy dissipation is computed and included in the energy balance (Default).
The stonewall energy dissipation is reported in GLSTAT, see DYTIMHS.
SLNTEN Sliding interface energy dissipation option (This parameter is always set to 2 if
contact is active. The option SLNTEN=1 is not available.):
1 Energy dissipation is not computed,
2 Energy dissipation is computed and included in the energy balance
The sliding interface energy is reported in ASCII files GLSTAT and SLEOUT, see
DYTIMHS.
RYLEN Rayleigh energy dissipation option (damping energy dissipation):
1 Energy dissipation is not computed (Default),
2 Energy dissipation is computed and included in the energy balance.
The damping energy is reported in GLSTAT, see DYTIMHS.

Main Index
 DYPARAM,LSDYNA,HOURGLAS 1885

DYPARAM,LSDYNA,HOURGLAS

Controls for energy dissipation options in SOL 700.

Format:
DYPARAM,LSDYNA,HOURGLAS,[option],<value>

Example:
DYPARAM,LSDYNA,HOURGLAS,IHQ,2

Option Contents Type Default

IHQ Default hourglass viscosity type: I>0 See
Remark
3.
1 Standard
2 Flanagan-Belytschko integration
3 Flanagan-Belytschko with exact volume integration
4 Stiffness form of type 2 (Flanagan-Belytschko)
5 Stiffness form of type 3 (Flanagan-Belytschko)
6 Belytschko-Bindeman [1993] assumed strain co-rational stiffness
form for 2D and 3D solid elements only. This form is available for
explicit and IMPLICIT solution methods. In fact, type 6 is mandatory
for the implicit options.
8 Applicable to the type 16 fully integrated shell element. IHQ=8
activates warping stiffness for accurate solutions. A speed penalty of
25% is common for this option.
9 Puso [2000] enhanced assumed strain stiffness form for 3D
hexahedral elements. This form is available for explicit and implicit
solution methods, hence it is an alternative to the Belytschko-
Bindeman hourglass type 6 for implicit simulations.
QH Default hourglass coefficient R 0.1

Main Index
 1886 DYPARAM,LSDYNA,HOURGLAS

Remarks:
1. In the shell elements, IHQ < 4 is the viscous form based on Belytschko-Tsay. If IHQ - 4, 5, or 6,
the stiffness form is obtained. The stiffness forms, however can stiffen the response, especially if
the deformations are large, and therefore should be used with care. For high velocities the viscous
forms are recommended and for low velocities the stiffness forms are recommended. For large
deformations and nonregular solids, option 3 or 5 is recommended.
2. Hourglass coefficients and type can be set by using HGSUPPR. These will override values set
with DYPARAM,LSDYNA,HOURGLAS.
3. They default hourglass type for underintegrated elements is as follows:
For shells: viscous type (1=2=3) for explicit; stiffness type (4=5) for implicit
For solids: type 2 for explicit; type 6 for implicit (only type 6 is implemented)
4. Type 6 hourglass control (IHQ=6) is for 2D and 3D solid elements only. If IHG is set to 6, any
underintegrated shell element parts that do not have hourglass type defined by HGSUPPR data
will be automatically switched to type 4 hourglass control. If this behavior is not desired, it may
be better to use HGSUPPR to change individual solid parts to type 6 hourglass control. For a more
detailed discussion of type 6 hourglass control, please see Remark 4 in the HGSUPPR section.
5. Hourglass type 9 is available for hexahedral elements and is based on physical stabilization using
an enhanced assumed strain method. In performance it is similar to the Belytschko-Bindeman
hourglass formulation (type 6) but gives more accurate results for distorted meshes, e.g., for
skewed elements. If QH = 1.0, it produces accurate coarse bending results for elastic materials.
The hourglass stiffness is by default based on elastic properties, hence the QH parameter should
be reduced to about 0.1 for plastic materials in order not to stiffen the structure during plastic
deformation. For materials 3, 18 and 24 there is the option to use a negative value of QH. With
this option, the hourglass stiffness is based on the current material properties, i.e., the plastic
tangent modulus, and scaled by QH .

Reference:
Puso, M.A., “A Highly Efficient Enhanced Assumed Strain Physically Stabilized Hexahedral Element”,
Int. J. Numer. Meth. Eng., Vol. 49, 1029-1064 (2000).

Main Index
 DYPARAM,LSDYNA,IMPLICIT 1887

DYPARAM,LSDYNA,IMPLICIT

Options to modify convergence tolerances and initial/geometric stiffness of prestress (PRESTRS) or

springback (SPRBCK) simulations. Used in SOL 700 only.

Format:
DYPARAM,LSDYNA,IMPLICIT,OPTION1,OPTION2,VALUE

Example:
DYPARAM,LSDYNA,IMPLICIT,GENERAL,IGS,1

Option 1 Option 2 Contents

AUTO IAUTO Automatic time step control flag. The default for IAUTO depends
on the analysis type. For springback analysis, automatic time step
control and artificial stabilization are activated by default. (Integer)

0 Constant time step size

1 Automatically adjusted time step size
DTMIN Minimum allowable time step size. Simulation stops with error
termination if time step falls below DTMIN. (Real; Default = initial
time step/1000)
DTMAX Maximum allowable time step size. (Real; Default = initial time step
* 10)
GENERAL IGS Geometric (initial stress) stiffness flag. The geometric stiffness adds
the effect of initial stress to the global stiffness matrix. This effect
is seen in a piano string whose natural frequency changes with
tension. Geometric stiffness does not always improve nonlinear
convergence, especially when compressive stresses are present, so
its inclusion is optional. (Integer; Default = 2)

1 Include
2 Ignore
SOLUTION NSOLVR Solution method for implicit analysis. See Remarks 1. and 2.
(Integer; Default = 2)

1 Linear
2 Nonlinear with BFGS updates
3 Nonlinear with Broyden updates
4 Nonlinear with DFP updates
5 Nonlinear with Davidon updates

Main Index
 1888 DYPARAM,LSDYNA,IMPLICIT

Option 1 Option 2 Contents

SOLUTION ILIMIT Iteration limit between automatic stiffness reformations. See
Remark 3. (Integer; Default = 11)
SOLUTION MAXREF Stiffness reformation limit per time step.See Remark 4. (Integer;
Default = 15)
SOLUTION DCTOL Displacement relative convergence tolerance. See Remark 5. (Real;
Default = 0.001)
SOLUTION ECTOL Energy relative convergence tolerance. See Remark 6. (Real;
Default = 0.01)
SOLUTION RCTOL Residual (force) relative convergence tolerance. See Remark 7.
(Real; Default = 1.0E+10)
SOLUTION LSTOL Line search convergence tolerance. See Remark 8. (Real; Default =
0.90)
SOLUTION ABSTOL Absolute convergence tolerance. (Real; Default = 1.0E-10)
SOLUTION NLPRINT This flag controls printing of displacement and energy convergence
measures during the nonlinear equilibrium search. If convergence
difficulty occurs, this information is helpful in determining the
problem. (Integer; Default = 0)

0 No nonlinear iteration information printed.

1 Print iteration information
2 Print extra norm information (NLNORM=1)
SOLUTION NLNORM Nonlinear convergence norm type. (Integer; Default = 2)

1 Consider translational and rotational degrees of freedom

2 Consider translational degrees of freedom only
DYNAMICS IMASS Implicit analysis type. (Integer; Default = 0):

0 Static analysis
1 Dynamic analysis using Newmark time integration.
DYNAMICS GAMMA Newmark time integration constant. See Remark 9. (Real; Default =
0.50)
DYNAMICS BETA Newmark time integration constant. (Real; Default = 0.25)
DYNAMICS TDYBIR Birth time for application of dynamic terms. See Figure 8-93. (Real;
Default = 0.0)
DYNAMICS TDYDTH Death time for application of dynamic terms. (Real; Default =
1.0E20)

Main Index
 DYPARAM,LSDYNA,IMPLICIT 1889

Option 1 Option 2 Contents

DYNAMICS TDYBUR Burial time for application of dynamic terms. (Real; Default =
1.0E20)
DYNAMICS IRATE Rate effects switch. (Integer; Default = 0):

0 Rate effects are on in constitutive models

1 Rate effects are off in constitutive models

Remarks:
1. If a linear analysis is selected, equilibrium checking and iterations are not performed.
2. The Full Newton nonlinear solution method can be invoked by using the default BFGS solver,
and selecting ILIMIT=1 to form a new stiffness matrix every iteration.
3. In the default BFGS method, the global stiffness matrix is only reformed each ILIMIT iterations.
Otherwise, an inexpensive stiffness update is applied. By setting ILIMIT=1, a stiffness
reformation is performed every iteration. This is equivalent to the Full Newton method (with line
search). A higher value of ILIMIT (20-25) can reduce the number of stiffness matrix reformations
and factorizations which may lead to a significant reduction in cost. Note that the storage
requirements for implicit include storing 2 vectors per iteration. Large values of ILIMIT will
cause substantial increase in storage requirements.
4. The nonlinear equilibrium search will continue until the stiffness matrix has been reformed
MAXREF times, with ILIMIT iterations between each reformation. If equilibrium has not been
found, control will be passed to the automatic time step controller if it is activated. Otherwise,
error termination will result. When the auto time step controller is active, it is often efficient to
choose MAXREF=5 and try another stepsize quickly, rather than wasting too many iterations on
a difficult step.
5. When the displacement norm ratio is reduced below DCTOL, this condition is satisfied. Smaller
numbers lead to more accurate determination of equilibrium and, on the negative side, result in
more iterations and higher costs. Use NLPRINT to display norm data each iteration.
6. When the energy norm ratio is reduced below ECTOL, this condition is satisfied. Smaller
numbers lead to more strict determination of equilibrium and, on the negative side, result in more
iterations and higher costs. Use NLPRINT to display norm data each iteration.
7. When the residual norm ratio is reduced below RCTOL, this condition is satisfied. Smaller
numbers lead to more strict determination of equilibrium and, on the negative side, result in more
iterations and higher costs. By default this convergence criterion is effectively disabled using
RCTOL=1.e10. Use NLPRINT to display norm data each iteration.
8. A line search is performed on stiffening systems to guard against divergence of Newton-based
nonlinear solvers. With the Full Newton method, it is sometimes helpful to define a large value
(LSTOL=9999.0) to effectively disable line search.
9. For the dynamic problem, the linearized equilibrium equations may be written in the form:
n+1 n+1 n n n+1 n
Mu·· + Du· + K t ( x )Δu = P ( x ) – F(x )

Main Index
 1890 DYPARAM,LSDYNA,IMPLICIT

where
M = lumped mass matrix
D = damping matrix
n+1 n+1 0
u =x –x = nodal displacement vector
·n + 1
u = nodal point velocities at time n+1
··n + 1
u = nodal point accelerations at time n+1.

Between the birth and death times 100% of the dynamic terms, that is the terms involving M and
D, are applied. Between the death and burial time the dynamic terms are decreased linearly with
respect to time until 0% of the dynamic terms are applied after the burial time. This feature is
useful for problems that are initially singular because the parts are not in contact initially such as
in metal stamping. For these problems dynamics is required for stable convergence. When contact
is established the problem becomes well conditioned and the dynamic terms are no longer
required for stable convergence. It is recommended that for such problems the user set the death
time to be after contact is established and the burial time for 2 or 3 steps after the death time.
The time integration is by the unconditionally stable, one-step, Newmark- β time integration
scheme:
n
Δu u· 1 1
= ------------ – --------- – ---  --- – β u··
n+1 n
u··
2 βΔ t β 2 
βΔ t
n+1 n n n+1
u· = u· + Δt ( 1 – γ )u·· + γ Δtu··
n+1 n
x = x + Δu

Here, Δt is the time step size, and β and γ are the free parameters of integration. For γ = 1 ⁄ 2
and β = 1 ⁄ 4 the method reduces to the trapezoidal rule and is energy conserving. If
1
γ > ---
2
1 1
β > ---  --- + γ
42 

numerical damping is induced into the solution leading to a loss of energy and momentum.

Main Index
 DYPARAM,LSDYNA,IMPLICIT 1891

100%

Dynamic
Effects (M,D)

0%
TDYBIR TDYDTH TDYBUR

Time

Figure 8-93 Birth, death, and burial time for implicit dynamics.

Main Index
 1892 DYPARAM,LSDYNA,OUTPUT

DYPARAM,LSDYNA,OUTPUT

Set miscellaneous output parameters in SOL 700.

Format:
DYPARAM,LSDYNA,OUTPUT,[option],<value>

Example:
DYPARAM,LSDYNA,OUTPUT,NEECHO,1

Option Contents Type Default

NPOTPT Suppress print output. I 0
0 No Suppression
1 Nodal coordinates, element connectivity’s, rigid wall
definitions and initial velocities are not printed.
NEECHO Suppress echo output. I 0
0 All data printed.
1 Nodal printing is suppressed.
2 Element printing is suppressed.
3 Both nodal and element printing is suppressed.
NREFUP Flag to update the reference node coordinates for beam elements. I 0
0 No update.
1 Update.
IACCOP Set calculation of averaged accelerations from velocities. I 0
0 No average.
1 Averaged between output files.
2 Built-in, user-defined filtering.
OPIFS Output interval for interface file. R 0.0
IKEDIT Problem status report interval steps to the D3HSP file. I 100
IFLUSH Number of time steps interval for flushing I/O buffers. I 5000
IPNINT Print initial time step sizes for all elements on the first cycle. I 0
0 100 elements with the smallest time step sizes are
printed.
1 The governing time step sizes for each element are
printed.

Main Index
 DYPARAM,LSDYNA,OUTPUT 1893

Option Contents Type Default

IPRTF Default print flag for RBDOUT and MATSUM files. This option I 0
is meant to reduce the file sizes by eliminating data which is not
of interest.
0 Write part data into both MATSUM and RBDOUT
1 Write data into RBDOUT file only
2 Write data into MATSUM file only
3 not write data into RBDOUT and MATSUM
IERODE Output eroded internal and kinetic energy into the MATSUM file. I 0
Also, output to the MATSUM file under the heading of property
ID 0 is the kinetic energy from nonstructural mass, lumped mass
elements and lumped inertia elements.
0 Do not output extra data
1 Output the eroded internal and kinetic energy
TET10 Output ten connectivity nodes into D3PLOT database. I 2
1 Write the full ten node connectivity into the D3PLOT
database
2 Write the four corner nodes of the ten node
connectivity into the D3PLOT database
MSGMAX Maximum number of each error/warning message. I 10000.
NASTIN Nastin file option. See Remark 2. I 0
0 No element information except shells will be written in a nastin file
1 All element information will be written in a nastin file

Remark:
1. When TYPEVAL for IACCOP is set to 2, TYPEVAL for DT2MS on DYPARAM,TIMESTEP
must be set.
2. When NASTIN is set to 1, CBEAM, CQUAD4, CTRIA3, CTETRA, CHEXA, CPENTA,
CTQUAD and CTTRIA will be written in a nastin file. However CBEAM information is only
acceptable when Hughes-Liu beam of PBEAM71 is used. For other beam properties, please
remove CBEAM entries in a nastin file and use the original CBEAM entries.

Main Index
 1894 DYPARAM,LSDYNA,RELAX

DYPARAM,LSDYNA,RELAX

DYPARAM,LSDYNA,RELAX usage is no longer recommended and will be removed from the code in
a future version. Use DYRELAX.
.

Main Index
 DYPARAM,LSDYNA,SHELL 1895

DYPARAM,LSDYNA,SHELL

Provide controls for energy dissipation options. Used in SOL 700 only.

Format:
DYPARAM,LSDYNA,SHELL,option,value

Option Contents
WRPANG Shell element warpage angle in degrees. If a warpage greater than this angle is
found, a warning message is printed. Default is 20 degrees.
ESORT Automatic sorting of triangular shell elements to treat degenerate quadrilateral shell
elements as C0 or DKT triangular shells, see option THEORY below:
0 No sorting required (Default)
1 Full sorting (C0 triangular shells)
2 Full sorting (DKT triangular shells)
The DKT triangular element will be unstable if used to model a thick shell.
IRNXX Shell normal update option. This option affects the Hughes-Liu, Belytschko-Wong-
Chiang, and the Belytschko-Tsay shell formulations. The latter is affected if and
only if the warping stiffness option is active, i.e., BWC=1.
-2 Unique nodal fibers which are incrementally updated based on the nodal
rotation at the location of the fiber.
-1 Recomputed fiber directions each cycle
0 Default set to -1
1 Compute on restarts.
n Compute every n cycles (Hughes-Liu shells only)
ISTUPD Shell thickness change option for deformable shells. For crash analysis, neglecting
the elastic component of the strains, ISTUPD=4, may improve energy conservation
and stability.
0 No thickness change.
1 Membrane straining causes thickness change in 3 and 4 node shell
elements. This option is very important in sheet metal forming or
whenever membrane stretching is important.

Main Index
 1896 DYPARAM,LSDYNA,SHELL

Option Contents
2 Membrane straining causes thickness change in 8 node thick shell
elements, types 1 and 2. This option is not recommended for implicit or
explicit solutions which use the fully integrated type 2 element. The type
3 thick shell is a continuum based shell and thickness changes are always
considered.
3 Options 1 and 2 apply.
4 Option 1 applies, but the elastic strains are neglected for the thickness
update. This option only applies to the most common elastic-plastic
materials for which the elastic response is isotropic.
THEORY Default shell theory:
1 Hughes-Liu
2 Belytschko-Tsay (default)
3 BCIZ triangular shell (not recommended)
4 C0 triangular shell
5 Belytschko-Tsay membrane
6 S/R Hughes Liu
7 S/R co-rotational Hughes Liu
8 Belytschko-Leviathan shell
9 fully integrated Belytschko-Tsay membrane
10 Belytschko-Wong-Chiang
11 Fast (co-rotational) Hughes-Liu
12 Plane stress (x-y plane)
13 Plane strain (x-y plane)
14 Axisymmetric solid (y-axis of symmetry) - area weighted
15 Axisymmetric solid (y-axis of symmetry) – volume weighted
16 Fully integrated shell element (very fast)
17 Discrete Kirchhoff triangular shell (DKT)
18 Discrete Kirchhoff linear shell either quadrilateral or Triangular with
6DOF per node
20 C0 linear shell element with 6 DOF per node
21 C0 linear shell element with 5 DOF per node with the Pian-Sumihara
membrane hybrid quadrilateral membrane.
25 Belytschko-Tsay shell with thickness stretch.
26 Fully integrated shell with thickness stretch
27 C0 triangular shell with thickness stretch

Main Index
 DYPARAM,LSDYNA,SHELL 1897

Option Contents
BWC Warping stiffness for Belytschko-Tsay shells:
1 Belytschko-Wong-Chiang warping stiffness added.
2 Belytschko-Tsay (Default)
MITER Plane stress plasticity option (applies to materials MATD003, MATD018,
MATD019 and MATD024):
1 Iterative plasticity with 3 secant iterations (Default)
2 Full iterative plasticity
3 Radial return noniterative plasticity. May lead to false results and has to
be used with great care
PROJ Projection method for the warping stiffness in the Belytschko-Tsay shell (the BWC
option above) and the Belytschko-Wong-Chiang elements (see remarks below).
This parameter applies to explicit calculations since the full projection method is
always used if the solution is implicit and this input parameter is ignored.
0 Drill projection
1 Full projection.
ROTASCL Define a scale factor for the rotary shell mass. This option is not for general use.
The rotary inertia for shells is automatically scaled to permit a larger time step size.
A scale factor other than the default, i.e., unity, is not recommended.
INTGRD Default shell through thickness numerical integration rule:
0 Gauss integration. If 1-10 integration points are specified, the default
rule is Gauss integration.
1 Lobatto integration. If 3-10 integration points are specified, the default
rule is Lobatto. For 2 point integration, the Lobatto rule is very
inaccurate, so Gauss integration is used instead. Lobatto integration has
an advantage in that the inner and outer integration points are on the shell
surfaces.
LAMSHT For composite shells with material types MAT8, MATD022 and MATD054 . If this
flag is set laminated shell theory is used. Lamination theory is applied to correct for
the assumption of a uniform constant shear strain through the thickness of the shell.
Unless this correction is applied, the stiffness of the shell can be grossly incorrect if
there are drastic differences in the elastic constants from ply to ply, especially for
sandwich type shells. Generally, without this correction the results are too stiff. For
the discrete Kirchhoff shell elements, which do not consider transverse shear, this
option is ignored.
0 Do not update shear corrections
1 Activate laminated shell theory

Main Index
 1898 DYPARAM,LSDYNA,SHELL

Option Contents
CSTYP6 Coordinate system for the type 6 shell element. The default system computes a
unique local system at each in plane point. The uniform local system computes just
one system used throughout the shell element. This involves fewer calculations and
is therefore more efficient. The change of systems has a slight effect on results;
therefore, the older, less efficient method is the default.
1 Variable local coordinate system (Default)
2 Uniform local system.
NFAIL1 Flag to check for highly distorted under-integrated shell elements, print a message,
and delete the element or terminate. Generally, this flag is not needed for one point
elements that do not use the warping stiffness. A distorted element is one where a
negative Jacobian exist within the domain of the shell, not just at integration points.
The checks are made away from the CPU requirements for one point elements. If
nonzero, NFAIL1 can be changed in a restart.
1 Print message and delete element.
2 Print message, write D3DUMP file, and terminate
>2 Print message and delete element. When NFAIL1 elements are deleted
then write D3DUMP file and terminate. These NFAIL1 failed elements
also include all shell elements that failed for other reasons than distortion.
Before the D3DUMP file is written, NFAIL1 is doubled, so the run can
immediately be continued if desired.
NFAIL4 Flag to check for highly distorted fully-integrated shell elements, print a message
and delete the element or terminate. Generally, this flag is recommended. A
distorted element is one where a negative Jacobian exist within the domain of the
shell, not just at integration points. The checks are made away from the integration
points to enable the bad elements to be deleted before an instability leading to an
error termination occurs. If nonzero, NFAIL1 can be changed in a restart.
1 Print message and delete element
2 Print message, write D3DUMP file, and terminate
>2 Print message and delete element. When NFAIL4 elements are deleted
then write D3DUMP file and terminate. These NFAIL4 failed elements
also include all shell elements that failed for other reasons than distortion.
Before the D3DUMP file is written, NFAIL4 is doubled, so the run can
immediately be continued if desired
IRQUAD In plane integration rule for the 8 node shell element:
2 2 x 2 Gauss quadrature
3 3 x 3 Gauss quadrature.

Main Index
 DYPARAM,LSDYNA,SHELL 1899

Remark:
The drill projection is used in the addition of warping stiffness to the Belytschko-Tsay and the
Belytschko-Wong-Chiang shell elements. This projection generally works well and is very efficient, but
to quote Belytschko and Leviathan:
“The shortcoming of the drill projection is that even elements that are invariant to rigid body rotation will
strain under rigid body rotation if the drill projection is applied. On one hand, the excessive flexibility
rendered by the 1-point quadrature shell element is corrected by the drill projection, but on the other hand
the element becomes too stiff due to loss of the rigid body rotation invariance under the same drill
projection”.
They later went on to add in the conclusions:
“The projection of only the drill rotations is very efficient and hardly increases the computation time, so
it is recommended for most cases. However, it should be noted that the drill projection can result in a
loss of invariance to rigid body motion when the elements are highly warped. For moderately warped
configurations the drill projection appears quite accurate”.
In crash-worthiness and impact analysis, elements that have little or no warpage in the reference
configuration can become highly warped in the deformed configuration and may affect rigid body
rotations if the drill projection is used, i.e., DO NOT USE THE DRILL PROJECTION. Of course it is
difficult to define what is meant by “moderately warped”. The full projection circumvents these
problems but at a significant cost. The cost increase of the drill projection versus no projection as
reported by Belytschko and Leviathan is 12 percent and by timings, 7 percent, but for the full projection
they report a 110 percent increase and an increase closer to 50 percent is observed.
For implicit problems, the full projection method is used in the development of the stiffness matrix.

Main Index
 1900 DYPARAM,LSDYNA,SOLID

DYPARAM,LSDYNA,SOLID

Define control parameters that can improve the accuracy of the calculation in SOL 700.

Format:
DYPARAM,LSDYNA,SOLID,[option],<value>

Example:
DYPARAM,LSDYNA,SOLID,ESORT,1

Option Contents Type Default

ESORT Automatic sorting of tetrahedron and pentahedron elements to I>0 0
treat degenerate tetrahedron and pentahedron elements as
tetrahedron (formulation 10) and pentahedron (formulation 13)
solids, respective.

0 no sorting required
1 full sorting
FMATRX Default method used in the calculation of the deformation I>0 0
gradient matrix.

1: Update incrementally in time

2: Directly compute F
NIPTETS Number of integration points used in the quadratic tetrahedron I>0 4
elements. Either 4 or 5 can be specified. This option applies to
the type 4 and type 16 tetrahedron elements.
SWLOCL Output option for stresses in solid elements used as spotwelds I>0 1
with material MATDSWx:

1 Global
2 Local

Main Index
 DYPARAM,LSDYNA,THERMAL 1901

DYPARAM,LSDYNA,THERMAL

Set parameters for a nonlinear thermal or coupled structural/thermal analysis. Used in SOL 700 only.

Format:
DYPARAM,LSDYNA,THERMAL,OPTION1,OPTION2,VALUE

Example:
DYPARAM,LSDYNAT, THERMAL , THERMSOL,GPT,1

Option 1 Option 2 Contents

THERMSOL PTYPE Thermal problem type. (Integer, default =0)
0 linear problem,
1 nonlinear problem with material properties evaluated at gauss
point temperature.
2 nonlinear problem with material properties evaluated at element
average temperature.
THERMSOL GPT Number of Gauss points to be used in the solid elements (Integer,
default=0)
0 the default is set to 8,
1 one point quadrature is used.
THERMSOL MSGLVL Output message level (Integer, default=0)
0 no output
1 summary information
2 detailed information
THERMSOL TSF Thermal speedup factor: This factor multiplies all thermal velocity terms
for artificial time scaling for metal stamping when the punch speed is
artificially increased.
THERMTIM TS Time step control (Integer, default=0)
0 fixed time step,
1 variable timestep (may increase or decrease).
THERMTIM ITS Initial thermal timestep (Real, required)

Main Index
 1902 DYPARAM,LSDYNA,THERMAL

Option 1 Option 2 Contents

THERMTIM TMIN Minimum thermal timestep (Real, default=structural explicit time step)
THERMTIM TMAX Maximum thermal time step (Real, default=100*structural explicit time
step)
THERMTIM DTEMP Maximum temperature change in each time step above which the thermal
timestep will be decreased (Real, default=1.0)
THERMTIM LCTS TABLED1 ID which defines data pairs of thermal time breakpoint vs.
new time step. The time step will be adjusted to hit the time breakpoints
exactly. After the time breakpoint, the time step will be set to the “new
time step” ordinate value in the table. (Integer, default=none)

Main Index
 DYPARAM,LSDYNA,TIMESTEP 1903

DYPARAM,LSDYNA,TIMESTEP

Set structural time step size control using different options in SOL 700.

Format:
DYPARAM,LSDYNA,TIMESTEP,[option],<value>

Example:
DYPARAM,LSDYNA,TIMESTEP,ISDO,1

Option Contents Type Default

ERODE Erosion flag for solid and t-shell elements when TSMIN (see I>0 0
PARAM, DYTERMNDTMIN) is reached. If this flag is not set the
calculation will terminate:

0 No
1 Yes
ISDO Basis of time size calculation for 4-node shell elements. 3-node I>0 0
shells use the shortest altitude for options 0, 1 and the shortest side
for option 2. This option has no relevance to solid elements, which
use a length based on the element volume divided by the largest
surface area.

0: characteristic length=area/(minimum of the longest side or the

longest diagonal).

1: characteristic length=area/(longest diagonal).

2: based on bar wave speed and MAX [shortest side,

area/(minimum of the longest side or the longest diagonal).]. THIS
OPTION CAN GIVE A MUCH LARGER TIME STEP SIZE THAT
CAN LEAD TO INSTABILITIES IN SOME APPLICATIONS,
ESPECIALLY WHEN TRIANGULAR ELEMENTS ARE USED.

3: timestep size is based on the maximum eigenvalue. This option

is satisfactory for structural applications where the material sound
speed changes slowly. The computational cost to determine the
maximum eigenvalue is significant, but the increase in the time step
size often allows for significantly shorter run times without using
mass scaling.

Main Index
 1904 DYPARAM,LSDYNA,TIMESTEP

Option Contents Type Default

TSLIMT Shell element minimum time step assignment. When a shell controls R > 0.0 0.0
the time step, element material properties (moduli not masses) will
be modified such that the time step does not fall below the assigned
step size. This option is applicable only to shell elements using
material models: MATD003, MATD018, MATD019, MATD024.
This so-called stiffness scaling option is NOT recommended. The
DT2MS option below applies to all materials and element classes
and is preferred. If both TSLIMT and DT2MS below are active and
if TSLIMT is input as a positive number, then TSLIMT is set to 1.E-
18, which makes it inactive. If TSLIMT is negative and less than
|DT2MS|, then |TSLIMT| is applied prior to the mass being scaled.
If |DT2MS| exceeds the magnitude of TSLIMT, then TSLIMT is set
to 1.E-18.
DT2MS Time step size for mass scaled solutions. Positive values are for R > 0.0 0.0
quasi-static analyses or time history analyses where the inertial
effects are insignificant. If negative, PARAM,STEPFCT*|DT2MS|
is the minimum time step size permitted and mass scaling is done if
and only if it is necessary to meet the Courant time step size
criterion. This latter option can be used in transient analyses if the
mass increases remain insignificant. See PARAM,
DYTERMNENDMAS.
LCTM TABLED1 ID that limits the maximum time step size. This table I>0 0
defines the maximum time step size permitted versus time.
MS1ST Limit mass scaling to the first step and fix the mass vector according I>0 0
to the time steps once. The time step will not be fixed but may drop
during the calculation from the specified minimum:

0 No
1 Yes
DT2MSF Reduction (or scale) factor for initial time step size to determine the R > 0.0 0.0
minimum time step size permitted. Mass scaling is done if it is
necessary to meet the Courant time step size criterion. If this option
is used DT2MS= -DT2MSF multiplied by the initial time step size,
Δ t, before Δ t is scaled by TSSFAC. This option is active if and only
if DT2MS=0 above.
DT2MSLC TABLED1 ID specifying DT2MS as a function of time during the I>0 0
explicit solutions phase. The load curve can only be used for
increasing the magnitude of DT2MS. Consequently, the magnitude
of DT2MS is taken as the maximum of the current value and the
value from the TABLED1.

Main Index
 DYPARAM,LSDYNA,TIMESTEP 1905

Option Contents Type Default

IMSCL Flag for selective mass scaling if and only if mass scaling active. I 0
Selective mass scaling does not scale the rigid body mass and is
therefore more accurate. Since it is memory and CPU intensive, it
should be applied only to small finely meshed parts
0 no selective mass scaling.
1 all parts undergo selective mass scaling.
<0 recommended. |IMSCL| is the BCPROP ID of the parts that undergo
selective mass scaling; all other parts are mass scaled the usual way.
RMSCL Flag for using rotational option in selective mass scaling R 0.0
0.0 Only translational inertia are selectively mass scaled
≠ 0.0 Both translational and rotational inertia are selectively mass scaled

Remarks:
During the solution the program loops through the elements and determines a new time step size by
taking the minimum value over all elements.
n+1
Δt = PARAM, STEPFCT ⋅ min { Δt 1, Δt 2, Δt N }

where N is the number of elements. The time step size roughly corresponds to the transient time of an
acoustic wave through an element using the shortest characteristic distance. For stability reasons the
scale factor PARAM,STEPFCT is typically set to a value of .90 (default) or some smaller value. To
decrease solution time we desire to use the largest possible stable time step size. Values larger than .90
will often lead to instabilities.
Some comments follow:
The sound speed in steel and aluminum is approximately 5mm per microsecond; therefore, if a steel
structure is modeled with element sizes of 5mm, the computed time step size would be 1 microsecond.
Elements made from materials with lower sound speeds, such as foams, will give larger time step sizes.
Avoid excessively small elements and be aware of the effect of rotational inertia on the time step size in
the Belytschko beam element. Sound speeds differ for each material, for example, consider:
AIR 331 m/s
WATER 1478
STEEL 5240
TITANIUM 5220
PLEXIGLAS 2598

Main Index
 1906 DYPARAM,LSDYNA,TIMESTEP

Model stiff components with rigid bodies instead of increasing Young’s modulus which can substantially
reduce the time step size.
The altitude of the triangular element should be used to compute the time step size. Using the shortest
side is acceptable only if the calculation is closely examined for possible instabilities. This is controlled
by parameter ISDO.
In the explicit time integration context and in contrast to conventional mass scaling, selective mass
scaling (SMS) is a well thought out scheme that not only reduces the number of simulation cycles but
that also does not significantly affect the dynamic response of the system under consideration. The
drawback is that a linear system of equations must be solved in each time step for the accelerations, in
this implementation a preconditioned conjugate gradient method (PCG) is used. An unfortunate
consequence of this choice of solver is that the efficiency will worsen when attempting large time steps
since the condition number of the assembled mass matrix increases with the added mass. Therefore,
caution should be taken when choosing the desired time step size. For large models it is also
recommended to only use SMS on critical parts since it is otherwise likely to slow down execution, once
again the bottle neck being the solution of the linear system of equations. Finally, one should be aware
that all constraints and boundary conditions available may not be supported for SMS. The following
features are supported in this context:
Pointwise nodal constraints in global and local directions
Prescribed motion in global and local directions
Adaptivity
Rigid walls
Deformable elements merged with rigid bodies
Regarding contacts only penalty based algorithms are supported, hence constraint contacts cannot be
used with SMS. A switch is automatically activated from constraint based contacts to penalty based when
necessary and possible, and this is accompanied with a proper warning message in the output files.
By default, only the translational dynamic properties are treated. This means that only rigid body
translation will be unaffected by the mass scaling imposed. There is an option to also properly treat rigid
body rotation in this way, this is invoked by flagging the parameter RMSCL. A penalty in computational
expense is incurred but the results could be improved if rotations are dominating the simulation.

Main Index
 DYPARAM,SPHERSYM 1907
Spherical Symmetric Analyses

DYPARAM,SPHERSYM Spherical Symmetric Analyses

Enables an efficient and accurate 1D spherical symmetric solution for Euleran 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:
DYPARAM,SPHERSYM,RECT,X,2.0

Option Contents
MESHTYPE Two types of Euler meshes are supported: (Character; Required)
OPTION SPHERIC Axial symmetric meshes
RECT Rectangular meshes
RADAXIS Symmetry axis: (Character; Required)
X X axis
Y Y axis
Z Z axis
PHI Only used for MESHTYPE = RECT. (Real > 0.0; Required)
Used to create a 1D spherical mesh with angles +PHI/2 and -PHI/2

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 mesh
geometry.
2. The Euler mesh can already by 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
 1908 DYPARAM,SPREMAP
1D spherical symmetric Euler archive remap

DYPARAM,SPREMAP 1D spherical symmetric Euler archive remap

Allows import of a 1D spherical symmetric Euler archive into a 3D simulation.

Format:
1 2 3 4 5 6 7 8 9 10
DYPARAM SPREMAP x0 y0 z0 range

Example:
DYPARAM SPREMAP 0.0 0.5 0.5

Option Contents
x0,y0,z0 X, Y and Z coordinate of the point at which the 1D 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 1D spherical symmetric Euler archive. (Real, Default = 1e+20)

Remarks:
1. Since 1D spherical symmetric simulations run much faster than 3D simulation it can save much
cpu time to do the first part of the simulation with a 1D spherical symmetric mesh. Afterwards the
1D spherical symmetric Euler archive is imported into the 3D simulation. By default the 1D
spherical symmetric archive will not be expanded into 3D. To enable this expansion DYPARAM,
SPREMAP has to be used. It is useful for blast wave simulations. The 1D spherical 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 spherical symmetric meshes DYPARAM,SPHERSYM can be used.

Main Index
 DYPARAM,VELMAX 1909
Maximum Velocity

DYPARAM,VELMAX Maximum Velocity

Defines the maximum velocity in Eulerian meshes. Used in SOL 700 only.

Format:
DYPARAM,VELMAX,VALUE,OPTION

Example:
DYPARAM,VELMAX,1.E6

Option Contents
VALUE Maximum velocity. (Real > 0.0; Default = 1.0E10)
OPTION 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 individual velocity components. Therefore the
magnitude of the velocity vector is limited to:

2 2 2
V = Vx + Vy + Vz
2 2 2
= VELMAX + VELMAX + VELMAX
2
= 3VELMAX
= VELMAX 3

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
 1910 DYRELAX

DYRELAX

Define controls for dynamic relaxation for restart runs. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DYRELAX ID NRCYCK DRTOL DRFCTR DRTERM TSSFDR IRELAL EDTTL
IDRFLG

Example:
DYRELAX 102 1000 0.002 0.6

Field Contents
ID Identification number of the DYRELAX entry – Not presently used. (Integer)
NRCYCK Number of iterations between convergence checks, for dynamic relaxation option
(Integer; Default = 250).
DRTOL Convergence tolerance for dynamic relaxation option (Real; Default = 0.001).
DRFCTR Dynamic relaxation factor (Real; Default = .995).
DRTERM Optional termination time for dynamic relaxation. Termination occurs at this time
or when convergence is attained (Real; Default = 1.0E20).
TSSFDR Scale factor for computed time step during dynamic relaxation. If zero, the value is
set to PARAM,STEPFCT. After converging, the scale factor is reset to
PARAM,STEPFCT. (Real; Default = 0.0)
IRELAL Use algorithm of Papadrakakis [Papadrakakis 1981] for control of dynamic
relaxation process. (Integer; Default = 0).
0 Not activated
1 Activated
EDTTL Convergence tolerance on automatic control of dynamic relaxation. (Real; Default
= 0.04).
IDRFLG Flag for stress initialization. (Integer; Default = 0)
-999 Dynamic relaxation not activated even if specified on a TABISTR.
-1 Dynamic relaxation is activated and time history output is produced
during dynamic relaxation, see Remark 3.
0 Not active.
1 Dynamic relaxation is activated.

Main Index
 DYRELAX 1911

Remarks:
1. If a dynamic relaxation analysis is being restarted at a point before convergence was obtained,
then NRCYCK, DRTOL, DRFCTR, DRTERM and TSSFDR will default to their previous
values, and IDRFLG will be set to 1.
2. If dynamic relaxation is activated after a restart from a normal transient analysis SOL 700
continues the output of data as it would without the dynamic relaxation being active. This is
unlike the dynamic relaxation phase at the beginning of the calculation when a separate database
is not used. Only load curves that are flagged for dynamic relaxation are applied after restarting.
3. If IDRFLG is set to -1, the dynamic relaxation proceeds as normal but time history data is written
to the D3THDT file in addition to the normal data being written to the D3DRLF file. At the end
of dynamic relaxation, the problem time is reset to zero. However, information is written to the
D3THDT file with an increment to the time value. The time increment used is reported at the end
of dynamic relaxation.

Reference:
Papadrakakis, M., “A Method for the Automatic Evaluation of the Dynamic Relaxation Parameters,”
Comp. Meth. Appl. Mech. Eng., Vol. 25, pp. 35-48 (1981)

Main Index
 1912 DYRIGSW

DYRIGSW

Defines materials to be switched from rigid to deformable and deformable to rigid in a restart. It is only
possible to switch materials on a restart if part switching was activated in the time zero analysis. See
D2R0000 for details of part switching. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DYRIGSW ID TYPE
PID MRB

Example 1:
DYRIGSW 101 D2R
1 101

DYRIGSW 102 R2D

200

Field Contents
ID Identification number of the DYRIGSW entry – Not presently used (Integer)
TYPE D2R Deformable to rigid part switch
R2D Rigid to deformable part switch
(Character; Required)
PID Property ID of the part which is switched to a rigid material for D2R. Property ID of
the part which is switched to a deformable material for R2D. (Integer; Required)
MRB Property ID of the master rigid body to which the part is merged. If zero, the part
becomes either an independent or master rigid body. Only used for D2R. (Integer;
Default = 0)

Main Index
 DYTERMT 1913

DYTERMT

Stops an SOL 700 analysis depending on specified displacement conditions. Used in SOL 700 only.

Caution: The inputs are different for the nodal and rigid body stop conditions. The nodal stop
condition works on the global coordinate position, while the body stop condition works
on the relative global translation. The number of termination conditions cannot exceed
the maximum of 10 or the number specified in the original analysis.
The analysis terminates for NODE when the current position of the node specified
reaches either the maximum or minimum value (stops 1, 2 or 3), or picks up force from
any contact surface (stop 4). For BODY the analysis terminates when the center of mass
displacement of the rigid body specified reaches either the maximum or minimum value
(stops 1, 2 or 3) or the displacement magnitude of the center of mass is exceeded (stop
4). If more than one condition is input, the analysis stops when any of the conditions is
satisfied. This input completely overrides the existing termination conditions defined
in the time zero run.
Termination by other means is controlled by the RESTART entry.

Format:

1 2 3 4 5 6 7 8 9 10
DYTERMT ID TYPE
NID/PID STOP MAXC MINC

Example 1:
DYTERMT 102 NODE
1 4

DYTERMT 102 BODY

200 1 0.45

Field Contents
ID Unique identification number. (Integer > 0)
TYPE Type of run termination. (Character; Required)
NODE Terminate the job depending on nodal conditions
BODY Terminate the job depending on rigid body conditions

Main Index
 1914 DYTERMT

Field Contents
NID/PID Referenced Node or Rigid Body. (Integer; Required)
For TYPE=NODE: Node ID
For TYPE=BODY: Property ID of rigid body
STOP Stop criterion: (Integer; Required)
1 Global x direction
2 Global y direction
3 Global z direction
4 For TYPE=NODE: Terminate if node touches contact surface.
For TYPE=BODY: Terminate if displacement magnitude is
exceeded
MAXC For TYPE=NODE: Maximum (most positive) coordinate. (Required; Real)
For TYPE=BODY: Maximum (most positive) displacement. (Default = 1.0E21;
Real).
MINC For TYPE=NODE: Minimum (most negative) coordinate. (Required; Real)
For TYPE=BODY: Minimum (most negative) displacement. (Default = -1.0E21;
Real)

Main Index
 DYTIMHS 1915
Time History Output Request

DYTIMHS Time History Output Request

Specifies various types of time history output and form of the output for SOL 700.
All Lagrangian output time histories will be stored in jid.dytr.binoutxxxx file(s) while all Eulerian output
time histories (EULOUT, SUBSOUT, SURFOUT, CPLSOUT, CPLSBOUT, EMATOUT, EBDOUT and
CMARKOUT) will be stored in a THS file. The binout files can be converted to ASCII format using the
I2a tool that is delivered with the SOL 700 installation. The data is written at the intervals specified by
DTOUT on this entry. If different DTOUT values are needed, enter the DYTIMHS entry as many times
as necessary. If they are the same, enter the main DYTIMHS entry once and use continuation entries to
define all requested output. When specifying multiple DYTIMHS entries for gridpoints and elements, the
smallest DTOUT will be used for those TYPEs. This is because all sets of both these TYPEs will be
combined into one output set. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
DYTIMHS KIND DTOUT DTOUTHF CID TID TIDOPT STEPFLG
TYPE I1 I2 I3 I4 I5 I6 I7
I8 I9
TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE

Example:
DYTIMHS BINARY 1.0E-5
GRID 100 101 200 210 250 260 300
400 500 550
ELEM 1100 1101 2200 2210 2250 2260 4300
4400 6500 6550
SPH 34 35 36 47 48 49 100
101
EULOUT 5000 5001 5002 5003 5004 5005 5006
5007 5008 5009 5010 5011 5012
NODFOR 210 250 251 254 300 301 302
303 304 305
ABSTAT GLSTAT MATSUM RCFORC RWFORC SPCFORC SWFORC

Main Index
 1916 DYTIMHS
Time History Output Request

Alternate Format:

1 2 3 4 5 6 7 8 9 10
DYTIMHS KIND DTOUT DTOUTHF CID
TYPE I1 THRU I2 BY I3
TYPE I1 THRU I2 BY I3
TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE

Example:
DYTIMHS BINARY 1.0E-4 1.0E-5
GRID 100 THRU 110 BY 2
GRID 1000 THRU 2000 BY 200
ELEM 2000
ABSTAT GLSTAT MATSUM RCFORC RWFORC SPCFORC SWFORC

Field Contents
KIND Type of the file to generate options are:
BINARY
(Character; Default = Binary)
DTOUT Output time interval. For at least one DYTIMHS DTOUT is required. (Real; no
Default)
DTOUTHF Output time interval for high frequency output. Only used when TYPE=GRID. See
Remark 2. (Real; Default = 0.0)
CID Coordinate system ID for output of data in local system. Only used for TYPE =
NODFOR. (Integer > 0; Default = 0)
TID Optional TABLED1 ID specifying time interval between dumps. TABLED1 to
define the curve; x value is time and y value is time interval between dumps. When
TID is set, DT will be ignored. See remark 5. (Integer, Default=0)
TIDOPT Flag to govern behavior of the plot frequency defined by TABLED1. This is only
applicable for Lagrangian output requests. For Eulerian time history request,
TIDOPT will be ignored. See remark 6. (Integer, Default=1):
1 At the time each plot is generated, the TABLED1 1value is added
to the current time to determine the next plot time.
2 At the time each plot is generated, the next plot time T is
computed so that T = the current time plus the TABLED1 value at
time T.
3 A plot is generated for each x value in the TABLED1 definition.
The y value of the TABLED1 is ignored.

Main Index
 DYTIMHS 1917
Time History Output Request

Field Contents
STEPFLG Flag to define time interval output request or step interval output request. This is
only applicable for Eulerian output requests. See remark 7. (Integer, Default=0)
0 Time interval request
1 Step intevalrequest
TYPE A character string designating the output types. Select from:
GRID Gridpoint Output (NODOUT)
x, y, z displacement
x, y, z velocity
x, y, z acceleration
x, y, z rotation
x, y, z rotational velocity
x, y, z rotational acceleration
ELEM Element Output (ELOUT)
Beam Elements:
axial force resultant
s shear resultant
t shear resultant
s moment resultant
t moment resultant
torsional resultant
Shell Elements:
xx, yy, zz stress
xy, yz, zx stress
plastic strain
xx, yy, zz strain
xy, yz, zx strain
lower surface strain
upper surface strain
Solid Elements:
xx, yy, zz stress
xy, yz, zx stress
effective stress
yield function
SPH SPH Element Data
xx, yy, zz stress
xy, yz, zx stress
xx, yy, zz strain
xy, yz, zx strain
density
half of smoothing length
number of neighbors
plastic strain

Main Index
 1918 DYTIMHS
Time History Output Request

Field Contents
EULOUT Euler Element Data (THS)
x, y, z velocity
Pressure
x, y, and z momentum
specific internal energy
Density
Mass
Soundspeed
Characteristic element length
Material fraction
Energy
Volume uncovered fraction
Void fraction
Temperature
NODFOR Nodal Force Group for Output. See Remark 3.
NCFORC Nodal interface forces
x, y, z force
BNDOUT Boundary conditions
x, y, z force
Energies
ABSTAT Airbag statistics
Volume
Pressure
Internal energy
Input mass flow rate
Output mas flow rate
MassTemperature
Density
GLSTAT Global data

Main Index
 DYTIMHS 1919
Time History Output Request

Field Contents
Kinetic energy
Internal energy
Total energy
Ratio
Stonewall-energy
Spring & damper energy
Hourglass energy
Damping energy
Sliding interface energy
External work
x, y, z velocity
Time step
Element id controlling the time step
MATSUM Material energies
Kinetic energy
Internal energy
Hourglass energy
x ,y, z momentum
x, y, z rigid body velocity
Total kinetic energy
Total internal energy
Total hourglass energy
RCFORC Resultant interface forces
x, y, z force
Mass of nodes in contact
RWFORC Wall forces
Normal
x, x, z force
SPCFORC SPC reaction forces
x, y, z force
x, y, z moment
SWFORC Nodal constraint reaction forces - sportwelds & rivets
Axial force
Shear force

Main Index
 1920 DYTIMHS
Time History Output Request

Field Contents
SUBSOUT Output request for part of a COUPLE or GBAG surface or
subsurfaces defined by BCSEG's. See Remark 4..

Output variables include

Surface area
Average pressure
Average temperature
etc. If the part of the surface is a hole, the massflowrate of the
leakage will be stored. If it is an inflator, the inflator massflowrate
is stored.
SURFOUT Output request for entire surface of a COUPLE or GBAG surface.
Output variables include
Surface area
Volume
Total contained energy
Average pressure
Average temperature
etc. If the part of the surface is a hole, the massflowrate of the
leakage will be stored. If it is an inflator, the inflator massflowrate
is stored.
CPLSOUT Forces on the entire coupling surface.
x, y and z forces
Resultant force
CPLSBOUT Forces on the coupling subsurfaces. See Remark 4.
x, y and z forces
Resultant force
EMATOUT Euler material output.
x, y and z momentum
Kinetic
Internal and distortional energy
Total volume
Total mass
EBDOUT Euler boundary output.
x, y and z momentum
x, y and z force
Massflow
Massflowrate
Energy transport
x, y and z velocity
x, y and z impulse
DEFORC Discrete element forces.
x, y and z force

Main Index
 DYTIMHS 1921
Time History Output Request

Field Contents
JNTFORC Joint forces.
x, y and z force
x, y and z moment
NCFORC Nodal interface forces.
x, y and z force
RBDOUT Rigid body data.
x, y and z displacement
Velocity
Acceleration
SBTOUT Seat belt data.
SLEOUT Interface energies
Slave, master and frictional energy
SSSTAT Subsystem data.
SSSTATM Subsystem data including mass and inertial properties.
GLSTATM Global system data including mass and inertial properties.
CMARKOUT Eulerian marker output.
Pressure
Density
Specific internal energy
x, y, and z flow velocities
x, y, and z marker velocities
x, y, and z momentum
Sound speed
I1, I2, I3, ... Element number, grid ID or BCBODY ID of BCSEG definition for the requested
items. These are only specified for TYPE=GRID, ELEM, SPH, EULOUT,
NODFOR, CPLSBOUT or SUBSOUT. See Remark 4. (Integer; no Default)

Remarks:
1. When DTOUT is not set, it will be set to 1000. times DTOUTHF.
2. When DTOUTHF is not set, but ACCMETR entries exist, DTOUTHF will be set to
DTOUT/1000. If also DTOUT is not set, no high frequency data will be generated. The center
node for all ACCMETR inputs are automatically flagged for high frequency input and do not need
to be added in a DYTIMHS output request.

Main Index
 1922 DYTIMHS
Time History Output Request

3. The nodal reaction forces in the global or local (if CID is defined) x, y, and z directions are printed
into the NODFOR file along with the external work which is a result of these reaction forces. The
resultant force vector found by summing the reaction forces over the nodes is also written into this
file. These forces can be a result of applied boundary forces such as nodal point forces and
pressure boundary conditions, body forces, and contact interface forces. In the absence of body
forces, interior nodes would always yield a null force resultant vector. In general, this option
would be used for surface nodes.
4. CPLSBOUT needs BCBODY ID of BCSEG definition. If BCSEG's are included in multiple
coupling surfaces, multiple output depending on coupling surfaces will be generated. SUBSOUT
definition without BCBODY ID of BCSEG definition will generate all subsurface results of
GBAG and COUPLE. SUBSOUT definition with BCBODY ID of BCSEG definition will follow
the same rule as CPLSBOUT.
5. The Lagrangian time history request will follow the rule, TIDOPT and see remark 6. Eulerian
time history will use x value as the start time (or step) and y value as the time (or step) interval.
0.0 in y value will stop storing time history results. For example, if TABLED1 has (0.0,0.5),
(3.0,1.0), (6.0,0.0), the time history will be stored at 0.0, 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 4.0, 5.0 and
6.0 seconds.
6. For example, TABLED1 has (0.0,0.5), (1.25,0.5), (1.25,2.0), (1.5,2.0), (10.0,2.0). If TIDOPT is
set to 1, the time history will be stored at 0.0, 0.5, 1.0, 1.5, 3.5, 5.5, 7.5, 9.5, 11.5, etc seconds. If
TIDOPT is set to 2, the time history will be stored at 0.0, 0.5, 1.0, 2.0, 4.0, 6.0, 8.0, 10.0, etc
seconds.
7. When STEPFLG is set to 1, DT or TID will be used for STEP interval instead of time interval.

Main Index
 ECHOOFF 1923
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), 293.
2. The companion to this entry is the ECHOON entry.

Main Index
 1924 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), 293.
2. The companion to this entry is the ECHOOFF entry.

Main Index
 EIGB 1925
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

Field Contents
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 prebuckling state of stress is multiplied to produce
buckling in the shape defined by the corresponding eigenvector.

Main Index
 1926 EIGB
Buckling Analysis Set

3. The continuation entry is optional. If the continuation is not specified, than NORM = “MAX”
normalization is performed.
4. See The Nastran Theoretical Manual, Sections 10.3.6 and 10.4.2.2, for a discussion of
convergence criteria.
5. If NORM = “MAX”, components that are not in the analysis set may have values larger than
unity.
6. 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.
7. Convergence is achieved at 10 – 6 .
8. 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.

Main Index
 EIGC 1927
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

Field Contents
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 9.
IRAM Implicitly Restarted Arnoldi Method. See Remark 13.
NORM Method for normalizing eigenvectors. See Remark 8. (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.

Main Index
 1928 EIGC
Complex Eigenvalue Extraction Data

Field Contents
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)
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 12. (Default = 7; Real > 0.0)
IBLKSZ Initial block size. See Remark 12. (Default = 2; Real > 0.0)
KSTEPS Frequency of solve. (Default = 5; Integer > 0)

Table 8-21 Relationship Between METHOD Field and Other Fields

METHOD Field
Field HESS INV CLAN
NDj (Integer > 0) Desired number of Desired number of roots Desired number of roots
eigenvalues and and eigenvectors in j-th and eigenvectors to be
eigenvectors. (No search 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
OMEGABj region in complex plane. in fields MBLKSZ and
Real and imaginary (Default = 0.0) IBLKSZ below; see also
parts of Bj in radians Remark 12.
per unit time. (Real).
Lj (Real > 0.0) Not used Width of j-th search region. See alternate definitions
(Default = 1.0) in fields MBLKSZ and
IBLKSZ below; see also
Remark 12.
NEj (Integer > 0) Not used Estimated number of roots Not used
in j-th search region.

Main Index
 EIGC 1929
Complex Eigenvalue Extraction Data

Table 8-21 Relationship Between METHOD Field and Other Fields

METHOD Field
Field HESS INV CLAN
MBLKSZ Maximum Block Size
For block CLAN only Default = 7
IBLKSZ Initial Block Size
For block CLAN only Default = 2

OMEGA
A1
B2

L2

ALPHA

L1
A2
B1
Figure 8-94 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 (described in nastran Command and NASTRAN Statement, 1).

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

Main Index
 1930 EIGC
Complex Eigenvalue Extraction Data

SYSTEM(108) Specification
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
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. See The NASTRAN Theoretical Manual, Sections 10.4.4.5 and 10.4.4.6, for a discussion of
convergence criteria and the search procedure with the INV method.
6. DIAG 12 prints diagnostics for the inverse power method, the complex Lanczos method and the
QZ HESS method.

Main Index
 EIGC 1931
Complex Eigenvalue Extraction Data

7. 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.
8. The normalized eigenvectors may be output with the SDISPLACEMENT and/or
DISPLACEMENT Case Control commands.
9. 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.
10. 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.

11. For DMAP applications there are input parameters, not present in the solution sequences, that may
be used to replace the function of the EIGC and CMETHOD entries. See the MSC Software Web
site for details.
12. 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.
13. 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.

Main Index
 1932 EIGC
Complex Eigenvalue Extraction Data

14. 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.

Main Index
 EIGP 1933
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

Field Contents
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.

Main Index
 1934 EIGR
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

Field Contents
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
 EIGR 1935
Real Eigenvalue Extraction Data

Field Contents
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 8-22 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 Frequency range of interest. If ND is not blank, F1
be input. If METHOD = “SINV” and and F2 are ignored. If ND is blank, eigenvectors
ND, is blank, then F2 must be input. are found with natural frequencies that lie in the
See also Remark 21. range 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 Desired number of eigenvectors. If ND is zero, the
is blank and METHOD = “SINV”, number of eigenvectors is determined from F1 and
then 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 (p. 43) in the 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.
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

Main Index
 1936 EIGR
Real Eigenvalue Extraction Data

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 NORM. The conventions used when both the Fi and ND fields are specified are
described in Table 8-23 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 8-22.
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.
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.

Main Index
 EIGR 1937
Real Eigenvalue Extraction Data

17. For the “INV” and “SINV” methods, convergence is achieved at 10 – 6 . 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.

Main Index
 1938 EIGRL
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

Field Contents
SID Set identification number. (Unique Integer > 0)
V1, V2 For vibration analysis: frequency range of interest. For buckling analysis:
eigenvalue range of interest. See Remark 4. (Real or blank,
16 16
– 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. Default is machine dependent. See Remark 14.
SHFSCL Estimate of the first flexible mode natural frequency. See Remark 10. (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 13.
(Real > 0.0; Default = 1.0):
i
1 – ALPH -
Fi = ( V2 – V1 ) ---------------------------------------
NUMS
1. – ALPH

NUMS Number of frequency segments for the parallel method. (Integer > 0; Default = 1)

Main Index
 EIGRL 1939
Real Eigenvalue Extraction Data, Lanczos Method

Field Contents
Fi Frequency at the upper boundary of the i-th segment. See Remark 13. (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 8-23.

Table 8-23 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 11.
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
 1940 EIGRL
Real Eigenvalue Extraction Data, Lanczos Method

8. MAXSET is used to limit the maximum block size. It is otherwise set by the region size or by
ND with a maximum size of 15. It may also be reset if there is insufficient memory available.
The default value is recommended.
9. 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.
10. 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.
11. 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.
12. NASTRAN SYSTEM(146) (also known as FBSMEM) provides options for I/O reduction during
FBS operations according to the following table.

Table 8-24 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%.

13. 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.
14. 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.

Main Index
 EIGRL 1941
Real Eigenvalue Extraction Data, Lanczos Method

15. 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.
16. 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.
17. 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.
18. V2 must be specified if DOMAINSOLVER ACMS or DOMAINSOLVER MODES is also
specified in the Executive Control Section.
19. 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.

Main Index
 1942 ELEMUDS
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
“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 USELEM

ELEMUDS 17 PBUSH2D ELEMENT USELEM

REAL .00134 1.467+4 .03
INT 8 3

Field Contents
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.and 7.(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)
“INT” Keyword indicating that the following data is integer. (Character)

Main Index
 ELEMUDS 1943
Element Property User Defined Service or Subroutine

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)
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. User subroutine USELEM is available for user convenience.
8. If the ROMAC interface is being used then UNAME=THPAD is required. See the THPAD Bulk
Data entry (p. 3672) for a description of ROMAC service. (http://www.virginia.edu/romac/)

Main Index
 1944 ELEMUDS
Element Property User Defined Service or Subroutine - SOL 600

ELEMUDS Element Property User Defined Service or Subroutine - SOL 600

Allows the user to provide element property routines for use with enhanced SOL 700 nonlinear elements
in SOL 600.

Format:

1 2 3 4 5 6 7 8 9 10
ELEMUDS PID PTYPE 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

Examples:
ELEMUDS 17 PSHELL UELEM RTN1

ELEMUDS 17 PSHELL UELEM1 RTN3

REAL .00134 1.467+4 .03
INT 8 3

Field Contents
PID Element property identification number that matches the identification number on a
PSHELL, PSOLID, PCOMP, PCOMPG, PBAR, PBEAM, PSHEAR, or PROD
element property entry. (Integer > 0)
PTYPE The name of the element entry. Currently supported element property entries include:
PSHELL, PSOLID, PCOMP, PCOMPG, PBAR, PBEAM, PSHEAR, or PROD.
(Character; no Default)
GROUP The group name used for the FMS section CONNECT SERVICE entry. (Character;
no Default)
UNAME A primary or secondary name to identify the user subroutine. See Remark 6.
(Character; Default blank)
“INT” Keyword indicating that the following data is integer. (Character)
IDATAi Additional user supplied Integer data not already existing on the specified MAT entry.
(Integer; no Default)
“REAL” Keyword indicating that the following data is real. (Character)

Main Index
 ELEMUDS 1945
Element Property User Defined Service or Subroutine - SOL 600

RDATAi Additional user supplied Real data not already existing on the specified MAT entry.
(Real; no Default)
“CHAR” Keyword indicating that the following data is Character. See Remark 7. (Character)
CDATAi Additional user supplied Character data not already existing on the specified MAT
entry. (Character; no Default)

Remarks:
1. This entry triggers the call to a user element property subroutine for advanced nonlinear materials.
2. PID must match an existing PID.
3. A CDATAi entry cannot be the Character “REAL”, “INT”, or “CHAR”.
4. Certain user subroutines may require integer, real, or character data input as specified in the User
Defined Services manual.
5. The ELEMUDS entry may be used instead of the USRSUB6 entry. Both entries should not be
used in the same run. EVAL will be stored as a character*16 name in common block /userch/.
6. UNAME identifies the user subroutine name to be called.
7. Character fields CDATAi are ignored in SOL 600 are not passed to the user subroutine.

Main Index
 1946 ELIST
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

Field Contents
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
 ENDDATA 1947
Bulk Data Delimiter

ENDDATA Bulk Data Delimiter

Designates the end of the Bulk Data Section.

Format:
ENDDATA

Remark:
1. ENDDATA is optional.

Main Index
 1948 ENDDYNA
Defines the End of Direct Text to Dytran-lsdyna

ENDDYNA Defines the End of Direct Text to Dytran-lsdyna

All entries between TODYNA and ENDDYNA will be passed directly by SOL 700 to Dytran-lsdyna.
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

Field Contents
TODYNA
MAT1
ENDDYNA

Remarks:
See TODYNA, 3708 for details of how this entry is used.

Main Index
 ENTUDS 1949
User Defined Logic at Entry Point

ENTUDS User Defined Logic at Entry Point

Calls user defined logic within a SCA service at the point specified within the solution sequence.

Format:

1 2 3 4 5 6 7 8 9 10
ENTUDS ENTID ENTPNT GROUP
“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:
ENTUDS 1 RCENT1 MY_FUNC

INT 2 17
REAL .5 .25

Field Contents
ENTID Entry point identification number (Integer > 0)
ENTPNT The point of entry in the solution sequence. Acceptable values for now: “RCENT1”,
“RCENT2”, “RCOUT1”, “RCEXEC1”. (Character; Required)
GROUP The SCA group name used to identify the service (Character; Required)
“INT” Key word indicating that the following data is integer. (Character)
IDATAi Additional user supplied Integer data not already existing on the specified MAT
entry. (Integer; no Default)
“REAL” Key word indicating that the following data is real. (Character)
RDATAi Additional user supplied Real data not already existing on the specified MAT entry.
(Real; no Default)
“CHAR” Key word indicating that the following data is Character. (Character)
CDATAi Additional user supplied Character data not already existing on the specified MAT
entry. (Character; no Default)

Remarks:
1. This entry is for RC Network solver only.

Main Index
 1950 ENTUDS
User Defined Logic at Entry Point

2. In SINDA input file, there are 4 entry points for users to input customized logics.
a. RCENT1 ---- Variable 1 block
b. RCENT2 ---- Variable 2 block
c. RCOUT1 ---- Output block
d. RCEXEC1 ---- Execution block

Main Index
 EOSGAM 1951
Gamma Law Gas Equation of State

EOSGAM Gamma Law Gas Equation of State

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

Field Contents
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:

Main Index
 1952 EOSGAM
Gamma Law Gas Equation of State

c
γ = ----p- R = cp – cν
cν

4. The viscosity coefficient is the dynamic viscosity. It is the ratio between shear stress and velocity
gradient. The SI-unit of viscosity is

N kg
Pa ⋅ s = ------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
 EOSGRUN 1953
The Gruneisen Equation of State

EOSGRUN The Gruneisen Equation of State

Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
EOSGRUN EOSID C S1 S2 S3 GAMAO A E0
V0

Example:
EOSGRUN 2 3958.0 1.497 0.0 0.0 2.0 0.0 0.0
0.0

Field Contents
EOSID Equation of state ID and must be unique. (Integer; Required)
C Constant C. (Real; Required)
S1 Constant S1. (Real; Required)
S2 Constant S2. (Real; Required)
S3 Constant S3. (Real; Required)
GAMAO Gruneisen gamma. (Real; Required)
A First order volume correction to GAMAO. (Real; Required)
E0 Initial internal energy. (Real; Required)
V0 Initial relative volume. (Real; Required)

Remark:
The Gruneisen equation of state with cubic shock velocity-particle velocity defines pressure for
compressed materials as

γ α 2
ρ 0 C μ 1 +  1 – ----0 μ – --- μ
2
 2 2
p = ------------------------------------------------------------------------------------------------------ + ( γ 0 + αμ )E
2 3 2
μ μ
1 – ( S 1 – 1 )μ – S 2 ------------- – S 3 --------------------2
μ+1 (μ + 1)

and for expanded materials as

Main Index
 1954 EOSGRUN
The Gruneisen Equation of State

2
p = ρ 0 C μ + ( γ 0 + αμ )E

where C is the intercept of the vs-vp curve; S 1 , S 2 , and S 3 are the coefficients of the slope of the vs-vp
curve; γ 0 is the Gruneisen gamma; a is the first order volume correction to γ 0 ; and μ = ρ ⁄ ρ0 – 1 .

Main Index
 EOSIG 1955
Ignition and Growth Equation of State

EOSIG Ignition and Growth Equation of State

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

Field Contents
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

Main Index
 1956 EOSIG
Ignition and Growth Equation of State

Field Contents
LX17 LX-17 explosive
UNITCNV User defined conversion units: (Character; see Remarks 2. and 3.)
CGMS cm/g/ μs units
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.

Main Index
 EOSIG 1957
Ignition and Growth Equation of State

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 8-25 defines sets of units available:

Table 8-25 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 8-26.
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.

Main Index
 1958 EOSIG
Ignition and Growth Equation of State

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):
– 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   R 
1e 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 –R2 p
------------- -------------
ω p η p ηp ω p η p ηp
p p = A p  1 – ------------ + B p  1 – ------------
1
- e - e + ωp ηp ρp Ep
 R   R 
1p 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 1959
Ignition and Growth Equation of State

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

Type of
Keyword 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
 1960 EOSIG
Ignition and Growth Equation of State

Table 8-26 Coefficients for the IG Model of Several Explosions in the Database.
LANL Military
PBX- Case COMP COMP PBX-
Explosive 9404 (a) TATB PETN TNT B B 9404 (b) LX-17
Unreacted Equation of State and Constitutive Values:
RHO (g/cm3) 1.842 1.90 1.842 1.61 1.712 1.630 1.842 1.903
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 1961
JWL Explosive Equation of State

EOSJWL JWL Explosive Equation of State

Defines the properties of a JWL equation of state commonly used to calculate the pressure of the
detonation products of high explosives. Used in SOL 700 only.
–R1 –R2
---------- ----------
p = p 0 + A  1 – ωη
-------- e + B  1 – ωη
-------- e
η η
+ ωηρ 0 e
 R1   R2 

where

E = specific internal energy per unit mass

ρ = reference density
ρ = overall material density
η = ρ ⁄ ρ0

p0 = initial pressure
A, B, R1, and R2 are constants.

Format:

1 2 3 4 5 6 7 8 9 10
EOSJWL EID A B R1 R2 OMEGA P0

Example:
EOSJWL 37 5.2E11 0.77E11 4.1 1.1 0.34

Field Contents
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)
Ρ2 Constant R2. (Real, 0.0)
OMEGA Constant ω . (Real, 0.0)
P0 Initial pressure. See Remark 3. (Real, 0.0)

Remarks:
1. This equation of state can be used only with Eulerian elements.

Main Index
 1962 EOSJWL
JWL Explosive Equation of State

2. A DETSPH entry must be used to specify the detonation model.

3. 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 undex calculations where an explosive
is located at a certain depth, P0 should be preset to equal the initial hydrostatic pressure.
4. EID must unique among all EOSxx entries in one model.
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 DYPARAM,JWLDET,NOLINK can be used.

Main Index
 EOSMG 1963
Mie-Gruneisen Equation of State

EOSMG Mie-Gruneisen Equation of State

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 = ----------------------2-  1 – ---------
- + Γ0 ρ0 e
 2 
( 1 – sη )
ρ
η = 1 – -----0
ρ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

Field Contents
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
 1964 EOSMG
Mie-Gruneisen Equation of State

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
 EOSPOL 1965
Polynomial Equation of State for Solids

EOSPOL Polynomial Equation of State for Solids

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

Field Contents
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)

Main Index
 1966 EOSPOL
Polynomial Equation of State for Solids

Field Contents
B1 Coefficient b1. (Real; Default = 0.0)
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 –1
μ HVL = -----------
-
HVL

e.g., for p = a1 ⋅ μ , the pressure behavior is as follows:

a1

μHVL
μ

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
 EOSTAB 1967
Tabulated Equation of State

EOSTAB Tabulated Equation of State

Defines tabular equation of state. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
EOSTAB EOSID GAMMA E0 V0
EV1 EV2 EV3 EV4 EV5
EV6 EV7 EV8 EV9 EV10
C1 C2 C33 C4 C5
C6 C7 C8 C9 C10
T1 T2 T3 T4 T5
T6 T7 T8 T9 T10

Example:
EOSTAB 1 0.0 0.0 1.0
0.0 -1.466E-3 -1.0E-2 -4.0E-2 -7.0E-2
-1.0
0.0 25.0 104.4 306.0 557.0
7118.0
0.0 0.0 0.0 0.0 0
0.0

Field Contents
EOSID Equation of state label. Referenced from PSOLIDD or PSPH only. (Integer;
no Default; Required)
GAMMA Gamma. (Real; no Default; Required)
E0 Initial internal energy. (Real; no Default; Required)
V0 Initial relative volume. (Real; no Default; Required )
EV1,EV2,...,EV10 Natural logarithm of volumetric strain. (Real; Required)
C1,C2,..C10 Factor. (Real; Required)
T1,T2,..T10 Temperature. (Real; Required)

Remarks:
The tabulated equation of state model is linear in internal energy. Pressure is defined by

Main Index
 1968 EOSTAB
Tabulated Equation of State

p = C ( ε ν ) + γT ( ε ν ) E

The volumetric strain, εV is given by the natural logarithm of the relative volume. Up to 10 points and
as few as 2 may be used when defining the tabulated functions.

Main Index
 EOSTABC 1969
Tabulated Equation of State with Compaction

EOSTABC Tabulated Equation of State with Compaction

Defines tabular equation of state with compaction. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
EOSTABC EOSID GAMMA E0 V0
EV1 EV2 EV3 EV4 EV5
EV6 EV7 EV8 EV9 EV10
C1 C2 C33 C4 C5
C6 C7 C8 C9 C10
T1 T2 T3 T4 T5
T6 T7 T8 T9 T10
K1 K2 K3 K4 K5
K6 K7 K8 K9 K10

Example:
EOSTABC 1 0.0 0.0 1.0
0.0 -1.466E-3 -1.0E-2 -4.0E-2 -7.0E-2
-1.0
0.0 25.0 104.4 306.0 557.0
7118.0
0.0 0.0 0.0 0.0 0
0.0
17050.0 17050.0 30600.0 30600.0 30600.0
30600.0

Field Contents
EOSID Equation of state label. Referenced from PSOLIDD or PSPH only. (Integer;
no Default; Required)
GAMMA Gamma. (Real; no Default; Required)
E0 Initial internal energy. (Real; no Default; Required)
V0 Initial relative volume. (Real; Required)
EV1,EV2,...,EV10 Natural logarithm of volumetric strain. (Real; Required)
C1,C2,..C10 Factor. (Real; Required)

Main Index
 1970 EOSTABC
Tabulated Equation of State with Compaction

Field Contents
T1,T2,..T10 Temperature. (Real; Required)
K1,K2,..K10 Unloading Bulk modulus. (Real; Required)

Remarks:
The tabulated compaction model is linear in internal energy. Pressure is defined by
p = C ( ε ν ) + γ T ( ε ν )E

in the loading phase. The volumetric strain, ε ν is given by the natural logarithm of the relative volume.
Unloading occurs along the unloading bulk modulus to the pressure cutoff. Reloading always follows
the unloading path to the point where unloading began, and continues on the loading path, see
Figure 8-95. Up to 10 points and as few as 2 may be used when defining the tabulated functions.

pressure

The bulk unloading

modulus is a function of
volumetric strain

Volulmetric strain

tension cutoff
Figure 8-95 Pressure versus volumetric strain curve for Equation of state Form 8 with
compaction. In the compacted states the bulk unloading modulus depends on
the peak volumetric strain.

Main Index
 EOSTAIT 1971
Tait Equation of State

EOSTAIT Tait Equation of State

Defines the properties of an equation of state based on the Tait model in combination with a cavitation
model where the pressure p is defined as follows. Used in SOL 700 only.
No cavitation case:
γ
p = α0 + α1 ⋅ ( η – 1 ) ( ρ > ρc )

In case the fluid cavitates:

p = pc ( ρ ≤ ρc )

where

η = ( ρ ⁄ ρ0 )

ρ = The overall material density

ρ0 = The reference density

ρc = The critical density resulting in the cavitation pressure pc

Format:

1 2 3 4 5 6 7 8 9 10
EOSTAIT EID A0 A1 GAMMA RHOC VISC

Example:
EOSTAIT 3 1.E6 3.31E9 7.15 .9999578 .0001

Field Contents
EID Unique equation of state number referenced from MATDEUL. (Integer > 0;
Required)
A0 Constant α 0 (Real, default=0.0)
A1 Constant α 1 (Real, default=0.0)
GAMMA Constant η (Real ≥ 0.0, default=1.0)
RHO Constant ρ c (Real > 0.0, required)
VISC Viscosity coefficient. (Real ≥ 0.0, default=0.0)

Remarks:
1. The pressure cannot fall below the cavitation pressure

Main Index
 1972 EOSTAIT
Tait Equation of State

ρc γ
p c = α 0 + α 1   ----- – 1 ,
  ρ 0 

although the density can continue to decrease below its critical value ρ c .
2. The Tait equation of state cannot be used in combination with a spallation model.
3. For a more detailed description, see Equations of State.
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
Pαs = ------ .
2
m

5. In case you wish to analyze viscous flows and use the fluid-structure interaction coupling scheme,
it is recommended that you use the “FASTCOUP” coupling algorithm. The viscous fluxes can be
computed more accurately for the fast coupling than for the general coupling algorithm.
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. 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.
7. EID must unique among all EOSxx entries in one model.

Main Index
 EOSUDS 1973
User-defined Equation of State

EOSUDS User-defined Equation of State

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 EXEOS SCAI.MDSo
lver700

In Bulk Data:
EOSUDS 12 WATER EXEOS .01

Field Contents
EID Unique equation of state number. I > 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 Required.
VISC Viscosity coefficient R > 0 No viscosity. See Remarks 4.and 5.

Remarks:
1. The EID must be referenced by a MATDEUL 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.

Main Index
 1974 EOSUDS
User-defined Equation of State

5. UNAME can be:

Subroutine Name Function

EXEOS Standard user defined Equation of State

6. The EXEOS routine includes the arrays DAMG, VOLPLS AND SOFTE. These arrays should
only be changed or accessed for the multi-material Euler solver. For the other solvers the data in
these arrays is not set and any changes made in these arrays are ignored. When making use of
these arrays for the Multi-Euler solver the use of FAILJC entry or FAILUDS with
UNAME=EXFAIL2 entry is required. By using these arrays the pressure can depend on the
amount of failure or damage of the Euler element and on the VOLPLS and SOFTE element
variables. The amount of damage can be either specified by the damage variable of the FAILJC
entry or by a more general failure estimate by using the FAIL2UD entry. The VOLPLS and
SOFTE variables can also be defined by the YLDUDS and EXFAIL2 user subroutine.
7. Only can be used for SOL 700.

Main Index
 EPOINT 1975
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

Field Contents
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
 1976 ERPPNL
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

Field Contents
NAMEi Panel label. (CHAR)
SETIDi Identification number of a SET3 Bulk Data entry that lists the panel property entries
or the panel elements. (Integer > 0)

Remarks:
1. The SET3 entries can only refer to CQUAD4, CQUADR, CTRIA3, or CTRIAR structural
elements or PSHELL, PCOMP or PCOMPG entry associated with them. CQUAD8 and CTRIA6
entries are ignored.
2. NAMEi are used in a Case Control SET definition defining setp to select the panels in the Case
Control command ERP.
3. Duplicate Element IDs are removed if they occur on the referencing SET3 entries prior to the ERP
calculation.

Main Index
 EULFOR 1977
Body Force Loading on Euler Elements

EULFOR Body Force Loading on Euler Elements

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.

Field Contents
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
 1978 EULFOR1
Body force for Eulerian Regions

EULFOR1 Body force for Eulerian Regions

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

Field Contents
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
 EULFREG 1979
Body force for Eulerian Regions

EULFREG Body force for Eulerian Regions

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

Field Contents
ERID Unique ERID number. (Integer > 0; Required)
ESID ID of group of Euler regions referenced from the EULFOR1 entry. (Integer > 0; Re-
quired)
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;
Required)
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.

Main Index
 1980 EULFREG
Body force for Eulerian Regions

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. 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
 EXPLSV 1981
Defines an explosive source

EXPLSV Defines an explosive source

Defines an air blast function of pressure loads caused by the detonation of conventional charge. This
feature includes enhancements for treating reflected waves, moving warheads and multiple blast sources.
DYPARAM,LSDYNA,BLSTFOR generates blast pressure history database (*.blastfor). PLBLAST is
used for applying blast pressure generate by this entry. Used in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
EXPLSV EID M XBO YBO ZBO TBO IUNIT IBLAST
CFM CFL CFT CFP NINBO DEATH NEGPHS
VEL TEMP RATIO
GNID XT YT ZT XH YH ZH CID

Example:

EXPLSV 2 1.0 180.0 0.0 0.0 0.0 3 2

30.0

Field Contents
EID Unique identification number. See Remark 1. (Integer > 0; Required.)
M Equivalent mass of TNT. See Remark 2. (Real > 0; Required.)
XBO,YBO,ZBO X, Y and Z Location of explosive charge center. (Real; Required.)
TBO Time of detonation. (Real ≥ 0.0; Default=0.0.)
IUNIT Unit conversion flag. (Integer > 0; Default=2)
1. feet, pounds, seconds, psi
2. meters, kilograms, seconds, Pascals
3. inch, dozens of slugs, seconds, psi
4. centimeters, grams, microseconds, Megabars
5. user conversions will be supplied (see CFM, CFL, CFT and CFP)

Main Index
 1982 EXPLSV
Defines an explosive source

Field Contents
IBLAST Type of blast source. (Integer > 0; Default=2)

1. Hemispherical surface burst - charge is located on or very near the ground

surface. See Remark 3.
2. Spherical free-air burst – no amplification of the initial shock wave due to
interaction with the ground surface.
3. Air burst – mobbing non-spherical warhead.
4. Air burst with ground reflection – initial shock wave impinges on the ground
surface and is reinforced by the reflected wave to produce a Mach front.
CFM Optional Conversion factor when IUNIT=5 – pounds per model mass unit. (Real ≥
0.0; Default=0.0.)
CFL Optional Conversion factor when IUNIT=5 – feet per model length unit. (Real ≥
0.0; Default=0.0.)
CFT Optional Conversion factor when IUNIT=5 – milliseconds per model time unit.
(Real ≥ 0.0; Default=0.0.)
CFP Optional Conversion factor when IUNIT=5 – psi per model pressure unit. (Real ≥
0.0; Default=0.0.)
NINBO Optional grid point ID representing the charge center instead of XBO, YBO and
ZBO. If this is non-zero then XBO, YBO and ZBO are ignored. (Integer > 0;
Default=not used)
DEATH Death time. Blast Pressure are deactivated at this time. (Real ≥ 0.0;
Default=1.0E20.)
NEGPHS Treatment of negative phase. (Integer ≥ 0; Default=0)

0 Negative phase dictated by the Friedlander equation.

1 Negative phase ignored.
VEL When IBLAST=3 - Speed of Warhead. (Real ≥ 0.0; Default=0.0.)
TEMP When IBLAST=3 – Ambient air temperature. Unit is Fahrenheit. (Real;
Default=70.0).
RATIO When IBLAST=3 – Aspect ratio of the oblate spheroidal shape of the blast front.
This is the short axis radius divided by the long axis radius and thus should be a
positive value less than unity. Shaped charge and EFP warheads typically have
significant lateral blast and its effect can be captured with this opion. (0.0 ≤ Real ≤
1.0; Default=1.0.)
GNID When IBLAST=4 – Grid point ID residing on the ground surface. (Integer > 0;
Required only when IBLAST=4)

Main Index
 EXPLSV 1983
Defines an explosive source

Field Contents
XT,YT,ZT When IBLAST= 3 or 4 – X, Y and Z coordinate of tail of vector. (Real; Default=0.0)

IBLAST=3 Vector represnting the symmetry axis of the warhead. This vector is
parallel to the short axis of the oblate spheroid described in RATIO field. It is also
parallel to the velocity vector when a non-zero VEL is defined.

IBLAST=4 Vector represnting the vertically upward direction, i.e., normal to

the ground surface.
XH,YH,ZH When IBLAST= 3 and 4 – X, Y and Z coordinate of head of vector. See XT, YT
and ZT contents. (Real; Default=0.0)
CID When IBLAST= 3 and 4 –Coordinate system ID to define vector in local coordinate
system. All coordinates, XT, YT, ZT, XH, YH, and ZH are in respect to CID. (
Integer; Default = 0)

Remarks:
1. Multiple charges may be defined, however, interaction of the waves in air is not considered.
2. Several methods can be used to approximate the equivalent mass of TNT for a given explosive.
The simplest involves scaling the mass by the ratio of the Chapman-Jouguet detonation velocities
given by the relationship.

where MTNT is the equivalent TNT mass and DCJTNT is the Chapman-Jouguet detonation
velocity of TNT. M and DCJ are, respectively, the mass and C-J velocity of the explosive under
consideration. Standard TNT is considered to be cast with a density of 1.57 g/cm3 and
DCJTNT=0.693 cm/microsecond.
3. When a charge is located on or very near the ground surface it is considered to be a surface burst.
Under this circumstance the initial blast wave is immediately reflected and reinforced by the very
hard ground to produce a reflected wave that moves out hemishperically from the point of burst.
This reflected wave merged with the initial incident wave produces overpressures which are
greater than those produced by the initial wave alone. In SOL700 this wave moves out spherically
from the burst point so no distinction of the ground orientation is made. Target points equidistant
from the burst point are loaded identically with surface burst option.
4. The normal direction of surfaces assigned in PLBLAST should point toward the charge.
5. The empirical equations underlying this feature are valid for the scaled distance 0.054 m/kg1/3
(0.136 ft/lbm1/3) < Z< 39.67 m/kg1/3 (100 ft/lbm1/3) where Z=R/M1/3, R is the distance in meter
(or feet) from the charge center to the target and M is the TNT equivalent mass of the charge in
kg (or lbm). Unexpected results may occur if the scaled distance lies outside this range.

Main Index
 1984 EXTRN
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

Field Contents
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.

Main Index
 FAILJC 1985
Johnson-Cook Failure Model

Entries F - L MSC Nastran Quick Reference GuideMSC Nastran Quick Reference Guide

FAILJC Johnson-Cook Failure Model

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
·0
FAILJC FID D1 D2 D3 D4 D5 ε pl TROOM
TMELT CP MTH

Example:

FAILJC 1 .05 3.44 -2.12 0.002 0.16 1.0 297.0

1495 450 CONT

Field Contents
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
 1986 FAILJC
Johnson-Cook Failure Model

Δε p
D =  ----------
ε
frac
-
time
·
frac *  ε pl *
ε = ( D 1 + D 2 exp ( D 3 σ ) )  1 + D 4 In ------ ( 1 + D5 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
strain depends on a non-dimensional plastic strain rate ε· pl ⁄ ε· pl . If D exceeds one it set equal to
0

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 1987
Maximum Plastic Strain Failure Model

FAILMPS Maximum Plastic Strain Failure Model

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

Field Contents
FID Unique failure model number referenced from MATDEUL. (Integer > 0; Required)
MPS Maximum plastic strain that causes failure. (Real; Required)

Remarks:

Main Index
 1988 FAILUDS
User defined failure for Nonlinear explicit analysis.

FAILUDS User defined failure for Nonlinear explicit analysis.

User defined simple failure of Eulerian materials.

Format:

1 2 3 4 5 6 7 8 9 10
FAILUDS FID GROUP UNAME METH

Example:

In FMS Section of the MSC Nastran input stream:

CONNECT SERVICE FAILM2 SCAI.MDSo

lver700

In Bulk Data:
FAILUDS 200 FAILM2 EXFAIL CONT

Field Contents
FID Unique output number. I > 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 Required.
MTH Specifies how failure is applied, Character. Default is CONT

CONT continuous failure

DISC discrete failure
NOFAIL No failure
See Remark 5.

Remarks:
1. Only can be used for SOL700.
2. FID has to be referenced by a MATDEUL entry.
3. UNAME can be:

Subroutine name Function

EXFAIL Standard user defined failure
EXFAIL2 Alternative to user defined failure

Main Index
 FAILUDS 1989
User defined failure for Nonlinear explicit analysis.

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:
• “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. For
UNAME=EXFAIL2 the user subroutines has the additional arrays DAMT, VOLPLS AND
SOFTE. By using these arrays the stress in the element can depend on the amount of failure or
damage of the Euler element and on the VOLPLS and SOFTE element variables.

Main Index
 1990 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/
COMPNAME
PNTID C DELAY

Examples:
FBADLAY 15 BODY 10 3 0.5

FBADLAY 25 30 5 2 0.1

Field Contents
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 1991
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/
COMPNAME
PNTID C A

Examples:
FBALOAD 10 WING 20 3 2.5

FBALOAD 20 30 25 1 1.5

Field Contents
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
 1992 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

Field Contents
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 1993
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 LABEL LABEL LABEL LABEL LABEL LABEL LABEL

Example:
FBODYLD WINGLD WINGSB
LOAD ON THE RIGHT WING

Field Contents
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
 1994 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 LABEL LABEL LABEL LABEL LABEL LABEL LABEL

Example:
FBODYSB WING 1 1 ADM
RIGHT WING

Field Contents
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
 FEEDGE 1995
Finite Element Edge Definition

FEEDGE Finite Element Edge Definition

Defines a finite element edge and associates it with a curve.

Format:

1 2 3 4 5 6 7 8 9 10
FEEDGE EDGEID GRID1 GRID2 CIDBC GEOMIN ID1 ID2

Example:

FEEDGE 101 123 547 GMCURV 12

Field Contents Type Default

EDGEID Unique identification number. Integer > 0 Required
GRIDi Identification number of end GRIDs definingthis edge. Integer > 0 Required
CIDBC Identification number of the coordinate system in which Integer > 0
constraints specified on GMBC and GMSPC entries are
defined. See Remark 1.
GEOMIN Type of entry referenced by IDi; “GMCURV” or Character POINT
“POINT”. See Remark 2.
IDi Identification number of a POINT or GMCURV entry. Integer > 0
See Remarks 2., 3., and 4.

Remarks:
1. If CIDBC is not blank then it overrides the CIDBC specified on the GMSURF or FEFACE entries
for this particular edge. A fatal message will be issued when more than one CIDBC is associated
with any entity.
2. The Bulk Data entries referenced by ID1 and ID2 depends on the GEOMIN field:

GEOMIN ID1 ID2

POINT POINT POINT
GMCURV GMCURV not applicable

3. When GEOMIN = “GMCURV”

• FEEDGE associates the finite element model and the geometric information.

Main Index
 1996 FEEDGE
Finite Element Edge Definition

• GRID1 and GRID2 are the end points of the edge, and the edge is on the CURVID curve. A
locally parametric cubic curve is fit to the geometric curve such that the two have the same
tangent at GRIDi (C1 continuous).
FEEDGE 300

GRID 2
GRID 1 GMCURV 101
GRID 4
FEEDGE 301
ELEMENT 101

GRID 10 ELEMENT 203

ELEMENT 204

GRID 11 GRID 110

GRID 121

GMCURV 201
FEEDGE,300,1,2,,POINT,20
FEEDGE,301,10,4,,POINT,203,204

Figure 8-96 Specifying Geometry Using GEOMIN=GMCURV Method

4. When GEOMIN = “POINT”

• The edge passes through the points defined on the POINT entries referenced by ID1 and ID2.
• The shape of the edge is selected as follows:

ID1 ID2 Shape of the FEEDGE

Blank or 0 Blank or 0 Linear
>0 Blank or 0 Quadratic
>0 >0 Cubic
Blank or 0 >0 Not allowed

Main Index
 FEEDGE 1997
Finite Element Edge Definition

FEEDGE 300

POINT 20 GRID 2
GRID 1
FEEDGE 301 GRID 4
ELEMENT 101
POINT 203

POINT 204

GRID 10
ELEMENT 203

GRID 110

GRID 121

FEEDGE,300,1,2,,POINT,20
FEEDGE,301,10,4,,POINT,203,204

Figure 8-97 Specifying Geometry Using GEOMIN=POINT Method

5. A local coordinate system can be associated with an edge using the GMCORD entry.
6. The hierarchy set to resolve the conflicts arising in the Global System input data is described
under Remark 10 of the GMBC, 2083 entry description.

Main Index
 1998 FEFACE
Finite Element Face Definition

FEFACE Finite Element Face Definition

Defines geometric information that will be used in elements, surface definition, load definition, and
boundary condition definition.

Format:

1 2 3 4 5 6 7 8 9 10
FEFACE FACEID GRID1 GRID2 GRID3 GRID4 CIDBC SURFID

Example:

FEFACE 101 123 547 243 295 12

Field Contents Type Default

FACEID Unique identification number. See Remark 1. Integer > 0 Required
GRIDi Identification number of end GRIDs defining a Integer > 0 Required
triangular or quadrilateral face. See Remark 2.
CIDBC Identification number of the coordinate system in Integer > 0 Remark 3.
which constraints specified on GMBC and
GMSPC entries are defined. See Remark 3.
SURFID Alternate method used to specify the geometry of Integer > 0 0
the edges of the face. See Remarks 4. and 5.

Remarks:
1. An FEFACE entry is required if any of the following situations exist:
• The geometry of the surface defined by SURFID is to be used by a finite element;
• CIDBC is specified for a face or surface; or
• If loads or constraints or enforced boundary conditions are applied to a surface.
2. The shape (geometry) of the face is defined by the shape of the edges. The points defined by
GRIDi must be specified in either a clockwise or counterclockwise order.
3. If CIDBC is not blank, then it overrides the CIDBC specified on the GMSURF entry for this
particular face. A fatal message will be issued when more than one CIDBC is associated with any
entity.
4. When SURFID is blank or 0, the edges will be considered linear unless there is an FEEDGE entry
for the given edge.
5. When SURFID > 0,
• FEFACE associates the finite element model and the geometric information specified on the
GMSURF entry.

Main Index
 FEFACE 1999
Finite Element Face Definition

• GRIDi defines a finite element face (clockwise or counter clockwise in order) that is on the
SURFID surface.
• For the edges of this face, which are not defined by an FEEDGE entry, locally parametric
cubic curves are fit to the geometric surface such that the two have the same tangent at GRIDi
(C1 continuous).
6. Whenever a given edge of a face is common to two or more surfaces (i.e., lies on the intersecting
curve), then the user must supply GMCURV and FEEDGE entries in order to resolve the conflict
in the input geometry. A fatal message is issued if an edge is not uniquely defined.

GMSURF 3000

GRID 3
GRID 4

GRID 1 FEFACT 206

GRID 2
GMSURF 3000 FEFACT 207
GMCURV 101

ELEMENT 101
GRID 96

GRID 21

GMSURF 4000 FEEDGE 300

GMSURF 4000

Figure 8-98 Face Edge Common to Two Surfaces

7. The hierarchy set to resolve the conflicts arising in the Global System input data is described
under Remark 10 of the GMBC, 2083 entry description.

Main Index
 2000 FFCONTR
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

Field Contents
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 GBAGOUT definition. The available
variables are: PRESSURE, VOLUME, TEMPTURE, VOLGAS, VOLFLUID, GAUGEPRES
and RHOFLUID.

Main Index
 FFCONTR 2001
Closed Volume Intended for Fluid Filled Containers

5. The normals of the surface referenced by SID are reversed automatically if required.
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
 2002 FLFACT
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

Field Contents
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

( FNF – FMID ) ( NF – i ) + FNF ( FMID – F1 ) ( i – 1 )-

Fi = F1
------------------------------------------------------------------------------------------------------------------------------------
( 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
 FLFACT 2003
Aerodynamic Physical Data

⋅ F1 ⋅ FNF- gives equal values to increments of the reciprocal

FMID = 2------------------------------
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
 2004 FLOW
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

Field Contents
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.

Main Index
 FLOW 2005
Flow Boundary Condition

Field Contents
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, 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
 2006 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

Field Contents
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 2007
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
 2008 FLOWSPH

FLOWSPH

Defines a flow of particles. This option applies ot continuum domains modeled with SPH particles. Used
in SOL 700 only.

Format:

1 2 3 4 5 6 7 8 9 10
FLOWSPH FID BCID DOF SF DEATH BIRTH
NODE XT YT ZT XH YH ZH CID

Example:
FLOWSPH 2 3 1 1.0
1002

Field Contents
FID Flow ID. Referred to from the TLOAD1entry. If not referenced from TLOADn entry,
the FLOWSPH is not active. (Integer; Required)
BCID BCPROP ID or BCGRID ID. (Integer; Required)
DOF Applicable degrees-of-freedom: (Integer>0; Required)
1 x-translational degree-of-freedom
2 y-translational degree-of-freedom
3 z-translational degree-of-freedom
4 Translational motion in direction given by vector defined by XT, YT, ZT,
XH, YH, ZH and CID. Movement on plane normal to the vector is permitted
SF Scale factor. (Real; Default = 1.0)
DEATH Time imposed motion/constraint is removed. (Real > 0.0; Default = 1.0e20)
BIRTH Time imposed motion/constraint is activated. (Real > 0.0; Default = 0.0)
NODE Node fixed in space which determines the boundary between activated particles and
deactivated particles. (Integer > 0; Required)
XT X-coordinate of tail of vector R. (Default-0.0)
YT Y-coordinate of tail of vector R. (Default-0.0)
ZT Z-coordinate of tail of vector R. (Default-0.0)
XH X-coordinate of head of vector R. (Default-0.0)

Main Index
 FLOWSPH 2009

Field Contents
YH Y-coordinate of head of vector R. (Default-0.0)
ZH Z-coordinate of head of vector R. (Default-0.0)
CID Coordinate system ID to define vector in local coordinate system. All coordinates, XT,
YT, ZT, XH, YH, and ZH are in respect to CID. (Integer; Default = 0)

Remarks:
Initially, the user defines the set of particles that are representing the flow of particles during the
simulation. At time t=0, all the particles are deactivated which means that no particle approximation is
calculated. The boundary of activation is a plane determined by the NODE, and normal to the vector
VID. The particles are activated when they reached the boundary. Since they are activated, particle
approximation is started.

boundary

vector ID deactivated particle

SPH Flow
activated particle

Figure 8-99 Vector VID determines the orientation of the SPH flow.

Main Index
 2010 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

Field Contents
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)

Main Index
 FLOWT 2011
Time Dependent Flow Boundary

Field Contents
DIR Allowed values are: NEGX, POSX, NEGY, POSY, NEGZ and POSZ. See Remark 5.
(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 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.)

Main Index
 2012 FLOWT
Time Dependent Flow Boundary

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.
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 2013
User defined flow boundary

FLOWUDS User defined flow boundary

Defines a flow boundary on an Eulerian mesh specified by a user subroutine.

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 FLOWIN SCAI.MDSo

lver700

In Bulk Data:
FLOWUDS 150 FLOWIN EXFLOW 300 1

Field Contents
LID Unique flow id number. I > 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 required.
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 8. (Real)

Remarks:
1. Only can be used for SOL 700.

Main Index
 2014 FLOWUDS
User defined flow boundary

2. UNAME can be:

Subroutine name Function

EXFLOW Standard user defined flow boundary on the Euler mesh
EXFLOW3 Advanced user defined flow boundary on the Euler mesh

EXFLOW allows inflow of only one material through each Eulerian boundary face while
EXFLOW3 allows inflow of multiple materials through each Eulerian boundary face.
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
 FLOWUDS 2015
User defined flow boundary

Main Index
 2016 FLSYM
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

Field Contents
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
 FLUTTER 2017
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

Field Contents
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
–3
4. (Real > 0.0; Default = 10 .)

Remarks:
1. The FLUTTER entry must be selected with the Case Control command FMETHOD = SID.

Main Index
 2018 FLUTTER
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 estim 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
 FLUTTER 2019
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
 2020 FORCE
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

Field Contents
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 MATD020) or the EID of a RBE2D. The MID of a rigid material and the
EID of RBE2 must be different when both of a RBE2D and a rigid material are used with these
TYPEs. SOL 700 only.

Main Index
 FORCE 2021
Static Force

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
 2022 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

Field Contents
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, 773). 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 2023
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

Field Contents
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, 773). 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
 2024 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

Field Contents
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) (Ch. 3) in the 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
 FREEPT 2025
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

Field Contents
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
 2026 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

Field Contents
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.

Main Index
 FREQ1 2027
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

Field Contents
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.

Main Index
 2028 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

Field Contents
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
where d = -------- ln F2
------- 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
 FREQ3 2029
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

Field Contents
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
 2030 FREQ3
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 8-27.

ˆf = 1--- ( ˆf + ˆf ) + 1--- ( ˆf – ˆf ) ξ 1 ⁄ CLUSTER ⋅ SIGN ( ξ )

k 1 2
2 2 2 1

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 8-27 CLUSTER Usage Example

CLUSTER
Excitation c=0.25 c-0.50 c-1.0 c-2.0 c-4.0
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
 FREQ3 2031
Frequency List, Alternate 3

Table 8-27 CLUSTER Usage Example

CLUSTER
Excitation c=0.25 c-0.50 c-1.0 c-2.0 c-4.0
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.

Main Index
 2032 FREQ4
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

Field Contents
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 8-100
for the definition of frequency spread.

Main Index
 FREQ4 2033
Frequency List, Alternate Form 4

( 1 – FSPD ) ⋅ f N fN ( 1 + FSPD ) ⋅ f N

Figure 8-100 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 8-101 for the definition of half-power bandwidth.

Peak Response

2 ⋅ ξ ⋅ fN

Half-Power Point (.707 Peak)

Amplitude

fN Frequency

Half-Power
Bandwidth

Figure 8-101 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
 2034 FREQ4
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.

Main Index
 FREQ5 2035
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

Field Contents
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 Ni are the natural frequencies in the range F1 through F2.

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.

Main Index
 2036 FREQ5
Frequency List, Alternate Form 5

5. Since the forcing frequencies are near structural resonances, it is important that some amount of
damping be specified.
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.

Main Index
 FRFCOMP 2037
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

Field Contents
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.

Main Index
 2038 FRFCOMP
Frequency Response Function (FRF) Component Specification for FRF Based Assembly (FBA)

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
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.

Main Index
 FRFCOMP 2039
Frequency Response Function (FRF) Component Specification for FRF Based Assembly (FBA)

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.
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 8-28 Multiplication Factors for FRF Response Quantities in UDN 58 of the Universal
File
Factor by Which FRF Response
Quantity is Multiplied Before It
FRF Response Quantity Type of Excitation is Used in the FBA 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
 2040 FRFCONN
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

Field Contents
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.

Main Index
 FRFCONN 2041
FRF Component Explicit Connection for FRF Based Assembly (FBA)

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.
6. FRFCONN entries are also required if the user wants to combine scalar points of FRF
components in the FBA process.

Main Index
 2042 FRFFLEX
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/
COMPNAM1
POINT1 COMPID2/
COMPNAM2
POINT2 KVALUE/ BVALUE/
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

Field Contents
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)

Main Index
 FRFFLEX 2043
FRF Component Flexible Connection Specification for FRF Based Assembly (FBA)

Field Contents
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)

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
 2044 FRFRELS
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/
COMPNAM1
GRIDPNT1 COMPID2/
COMPNAM2
GRIDPNT2 COMPID3/
COMPNAM3
GRIDPNT3

Examples:
FRFRELS 100 45 10 15 BODY 20 FRAME 30

FRFRELS 20 1 WING 25 NACELLE 35

Field Contents
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.

Main Index
 FRFRELS 2045
FRF Component Grid Point Release for FRF Based Assembly (FBA)

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
 2046 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/
COMPNAM1
POINT1 COMPID2/
COMPNAM2
POINT2 COMPID3/
COMPNAM3
POINT3

Examples:
FRFSPC1 100 4 10 12 ENGINE 23 FRAME 31

FRFSPC1 20 1 STRUT 25 NACELLE 35

Field Contents
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 2047
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

Field Contents
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.

Main Index
 2048 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

Field Contents
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.

Main Index
 FSICTRL 2049

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

Examples:

FSICTRL scafsi EXPLICIT 1

Field Contents Type Default

SERV_ID OpenFSI SCA service name associated with the wetted Character None
surface loads (see WETLOAD, 3768). The OpenFSI SCA
service is defined using the CONNECT SERVICE file
management section statement.
TYPE Type of solution strategy coupling between the external Character EXPLICIT
code and SOL 700. TYPE can be either EXPLICIT or
IMPLICIT.
FREQ External force and displacement update frequency per Integer > 0 1
time step, for the exchange with the external code using
the IMPLICIT solution strategy TYPE.

Remarks:
1. This entry is used for nonlinear SOL 400 analysis.
2. In the FMS Section of the SOL 700 input stream:
CONNECT SERVICE SERV_ID ' ExternalCodeVendor.OpenFSI '
3. The SERV_ID string must be 8 characters or less.

Main Index
 2050 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

Field Contents
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 2051
Fatigue Element Definitions

FTGDEF Fatigue Element Definitions

Defines elements and their associated fatigue properties to be considered for fatigue analysis.

Format:

1 2 3 4 5 6 7 8 9 10
FTGDEF ID TOPSTR PFTGID TOPDM
G
"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.-

Examples:

FTGDEF 22 100.0 3

FTGDEF 22
ELSET 14 3 15 4

FTGDEF 22
SPOTW 44 1 45 2 46

FTGDEF 22
SEAMW 44 99 31 FILLET TOE
45 99 LASER ROOT

Main Index
 2052 FTGDEF
Fatigue Element Definitions

Field Contents
ID Unique identification number. (Integer > 0).
TOPSTR Top stress percentage. Only elements with combined stress in this top percentage
will be retained and report results. (0.0 < Real ≤ 100.0; Default = blank - 100% will
be used). Should not be used with SOL 200 or for fatigue analysis of spot and seam
welds; leave blank. See Remark 8.
PFTGID 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 Top damage percentage. Only elements with damage in this top percentage will be
retained and report results. (0.0 < Real ≤ 100.0; Default = blank). Should not be used
with SOL 200 or for fatigue analysis of spot and seam welds; leave blank. See
Remark 8.
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)
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 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 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.

Main Index
 FTGDEF 2053
Fatigue Element Definitions

Field Contents
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.

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, all elements of the model that have fatigue
material properties defined will be used with default properties except for fatigue analysis of spot
and seam welds. See Remark 5. below.
2. If no PFTGID or PTFGIDi is specified, default properties will be 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,
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.
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 via RBE3 rigid elements. And face G5-G6-G7-G8 must
have corresponding RBE3 elements connecting the bottom sheet. 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 will be associated to these generated grids.

Main Index
 2054 FTGDEF
Fatigue Element Definitions

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 and/or TOPDMG in the same analysis allows the user to perform a 2-pass or a
3-pass run to speed up the analysis times of very large models and more quickly determine the
critical damage locations.
• If TOPSTR is used alone (TOPDMG is left unspecified), than a 2-pass analysis is performed
where the first (1st) pass determines the elements with the highest combined stresses based on
the stress combination (COMB field on FTGPARM entry) and the largest range of the
combined loading time histories. The second (2nd) pass computes damage on only the
remaining elements.
• If TOPDMG is used alone (TOPSTR=100% or left unspecified), then a 2-pass analysis is
performed where the first (1st) pass determines the elements with the highest damage based
on a set of reduced loading time histories. The second (2nd) pass computes damage on only
the remaining elements using the fully populated time history loading.
• If TOPSTR and TOPDMG are both specified, then a 3-pass analysis is performed where the
first (1st) pass eliminates all but the highest stressed elements and the second (2nd) pass
eliminates more elements based on damage due to a reduced set of time histories. The third
(3rd) pass computes damage on the remaining element with the fully populated time history
loading.
• If neither TOPSTR or TOPDMG are specified (both are blank), then a 1-pass analysis is done
on all the specified elements with fully populated loading time histories. This is the default
scenario.
When using TOPDMG, the method in which the reduced time histories are created is determined
by the settings on the RAINFLOW line of the FTGPARM entry. If this entry is absent or the
RAINFLOW line is not present, then the default is RTYPE=LOAD with PCTRED=50%.

Main Index
 FTGEVNT 2055
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 by referencing FTGLOAD entries.

Format:

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

Field Contents
ID Unique ID. See Remark 1.
FLOADi ID of a FTGLOAD entry (Integer > 0, no default).
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. or 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
 2056 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.

Main Index
 FTGLOAD 2057
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.

Format:

1 2 3 4 5 6 7 8 9 10
FTGLOAD ID TID LCID LDM SCALE/ OFFSET/ TYPE CHNL
MAX MIN
"UNITS" EQUIV EQNAME

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

Field Contents
ID Unique ID which is referenced by an FTGEVNT entry or directly by a FATIGUE case
control (Integer > 0). See Remark 1.
TID 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.
LCID Subcase ID of a linear static solution SUBCASE for SOL 101 or a mode number for SOL
103 (Integer > 0, no default).
LDM 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/ Scale factor applied to the load time history (Real, default=1.0). See Remark 7. Or the
MAX 1st peak level of a constant amplitude signal if TYPE=CONST (Real, default=1.0).
OFFSET/ Offset applied to the load time history (Real, default=0.0). See Remark 7. Or the 2nd peak
MIN level of a constant amplitude signal if TYPE=CONST (Real, default = -1.0). MAX can
be < or > than MIN for TYPE=CONST.
TYPE Flag indicating the type of load being defined. Values can be: blank, "DB", "DAC",
"RPC", "CONST" or "STATIC". Default is blank. See Remarks 2. through 6.
CHNL Channel of referenced RPC file (TYPE=RPC). (Integer >0, Default is blank). See
Remark 11.

Main Index
 2058 FTGLOAD
Fatigue Cyclic Loading Variation

Field Contents
"UNITS" Flag indicating that a fatigue equivalent unit name is defined for this loading. See
Remarks 8. and 9.
EQUIV Number of equivalent units (Real>0.0, default=1.0). See Remarks 8. and 9.
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
8. and 9.

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 an FTGEVNT entry.
2. If the TYPE field is blank then TID references a TABLFTG or TABLED1 entry.
3. 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).
4. 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.).
5. 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. 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 2059
Fatigue Cyclic Loading Variation

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.
8. 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.
9. 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.
10. 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.
11. CHNL is only used for TYPE=RPC. 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
 2060 FTGPARM
Fatigue Parameters

FTGPARM Fatigue Parameters

Defines parameters for a fatigue analysis.

Format:

1 2 3 4 5 6 7 8 9 10
FTGPARM ID TYPE FACTOR NTHRD LOGLVL
"STRESS" COMB CORR PLAST LOC INTERP
or
“STRAIN”
"RAINFLOW" RTYPE GATE PCTRED
"CERTNTY" SURV
"FOS" OPTION LIFE BACKACC MAXFAC MINFAC
“DAMAGE” CHECK FLOOR MAXDAM FAILDAM
“SPOTW” COMB CORR NANGLE SWLOC MIDDLE TORSION
“SEAMW” COMB CORR THICK LOCSM RESENT
“MULTI” MMTHD NONLWR NONUPR BIAXLWR BIAXMID BIAXUPR ZERO
GATE

Examples:
FTGPARM 22 SN

FTGPARM 22 SN
STRESS SGVON NONE

FTGPARM 22 SN
SEAMW FKM 0

FTGPARM 22 SN
SPOTW STNDRD SIMPLE 18 3 0 0

FTGPARM 22 EN
MULTI AUTO 0.25 0.5 -0.6 0.25 0.6 10.0
20.0

Field Contents
ID Unique ID of the FTGPARM entry (Integer > 0). See Remark 1.
TYPE Type of fatigue analysis: "SN" or "EN" (Character, Default=SN).

Main Index
 FTGPARM 2061
Fatigue Parameters

Field Contents
FACTOR Global scale factor to be applied to combined resultant stress output (Real>0.0,
Default=1.0).
NTHRD Number of threads to use for parallel processing for this fatigue analysis (Integer ≥
0; Default = 1). Zero (0) is used as a flag to tell the code to automatically determine
the number of threads to use.
LOGLVL 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 LOGLVL >3 can result in a
significant performance penalty and should be used for debugging purposes only.
"STRESS" Flag indicating that stress is used in the fatigue calculation. See Remark 2.
“STRAIN” Flag indicating that strain is used in the fatigue calculation. Not valid for TYPE =
SN. See Remark 2.
COMB Stress/strain combination to use in the fatigue analysis. Acceptable values are listed
in Table 8-29 after the Remarks below (Character; Default=ABSMAXPR).
CORR Mean stress correction to use in the fatigue analysis. Acceptable values are listed in
Table 8-30 and Table 8-31 after the Remarks below (Character; Default=None).
PLAST Plasticity correction for TYPE = EN. Value can be "NEUBER," or "SEEGER" for
Neuber or Hoffmann-Seeger methods, respectively (Character; Default=NEUBER).
See Remark 3.
LOC Location to report fatigue lives. Valid values are "NODE”, “SGAGE”, “CORNER”,
“BILIN”, “CUBIC” or "ELEMENT" (Character; Default = NODE). See Remark 4.
INTERP Interpolation limit for multi-curve mean stress correction method (Integer ≥ 0;
0=Use Max Curve, 1=Extrapolate; Default = 0).
"RAINFLOW" Flag indicating that parameters that follow define rainflow cycle counting
parameters for rainflow data reduction. See Remark 5.
RTYPE Method of rainflow data reduction (Time History Compression). Value can be
"LOAD" for load time history data reduction on each load time history or
"FAST" for performing a less accurate, but computationally faster method
(Character; no default). See footnote in Table 8-29.
GATE Load value used as gate range. This load is used for gating out small disturbances
of "noise" in the time history using a peak-valley extraction method to speed up the
analysis. Only used if RTYPE=LOAD. GATE and PCTRED are mutually exclusive.
PCTRED ignored if GATE is supplied. (Real≥ 0.0, Default=0.0 )
PCTRED Percent reduction value based on the maximum load range used to reduce the load
time history using a peak-valley extraction method to speed up the analysis. Only
used if RTYPE=LOAD. Ignored if GATE is supplied. GATE and PCTRED are
mutually exclusive. (0.0≤ Real≤100.0,Default=50)
"CERTNTY" Flag indicating that the parameter that follows defines the certainty of survival in
fatigue analysis.

Main Index
 2062 FTGPARM
Fatigue Parameters

Field Contents
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 6.
"FOS" 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 7. and 13.
OPTION Supported option is LIFE, requesting a life-based factor of safety analysis or NONE.
(Character; default = LIFE).
LIFE 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).
BACKACC 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).
MAXFAC 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 The minimum safety factor to calculate and report. If this threshold is exceeded, the
analysis will go on to the next element and report the minimum for the exceeded
element (0.0<Real≤0.5, Default = 0.2).
"DAMAGE" Flag indicating that parameters for static failure check are to follow.
CHECK Action to take on static failure. 0, 1, or -1 for Warn, Stop, or None, respectively.
Default = 0. See Remark 8.

• 0=Warn: the calculation continues but a warning message is issued. The

damage for this entity is also assigned a numeric value equal to the value of
the FAILDAM field, 2.0, by default. Not recommended for fatigue analysis
of spot welds.
• 1=Stop: The analysis stops the damage calculation for an entity with static
failure and continues on to the next entity. At the end of the entire analysis
of all entities, if there has been a static failure, a fatal message is issued and
the job is terminated. This setting is not recommended for fatigue analysis
of spot welds. Fatigue output ( CSV, FER, etc ) that was requested is still
kept, and entities that failed the UTS test have damage/life set to 2/0.5
(assuming the FTGPARM/FAILDAM is set to default value).
• -1=False: No static failure check is made. Damage will be calculated up to
the numerical limit defined by the MAXDAM field. Note that this may be
using an extrapolation of the S-N curve and may predict damage values per
cycle greater than 1.0. This also has an additional effect using standard SN
parameters. In this case, the adjustment of the S-N curve below 1000 cycles
to take into account the static strength of the material is disabled.

Main Index
 FTGPARM 2063
Fatigue Parameters

Field Contents
FLOOR This parameter sets a lower limit on calculated damage. If a cycle has less predicted
damage, the damage value is set to zero. This parameter is somewhat redundant as
similar functionality may be accessed using the fatigue cutoff Nfc in the material
definition. (0.0≤Real≤MAXDAM; Default = 0.0).
MAXDAM This parameter sets a numerical upper limit on the damage that can be predicted for
each cycle. Setting this to >1 shows how much unacceptable damage has
accumulated. (FLOOR≤Real≤FAILDAM; Default = 1.0).
FAILDAM This parameter assigns the numerical value of damage for any entity (node or
element) when the stress exceeds the UTS. This parameter is used to identify static
failure from a single cycle when looking at damage. (1.0≤Real≤1e30 and
MAXDAM≤Real; Default = 2.0).
"SPOTW" 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 8-29 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 or
SIMPLE are valid for fatigue analysis of spot welds. See Table 8-30 and Table 8-31
below. (Character; Default = NONE).
NANGLE The number of calculation angles in 360 degrees around the spot weld.
(10≤Integer≤360; 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 = 0 - do not 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" 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 8-29 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 8-30 and Table 8-31
below. (Character; Default=NONE).
THICK Thickness correction to be applied. (Integer 0 or 1; Default =0 - no correction)

Main Index
 2064 FTGPARM
Fatigue Parameters

Field Contents
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" 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.
NONLWR Used only when MMTHD = AUTO. Lower and Upper thresholds used to check if
NONUPR the loading is proportional. This is used in combination with the biaxiality ratio
thresholds.
NONLWR: (0<Real≤NONUPR, Default = 0.25)
NONUPR: (NONLWR<Real, Default = 0.5)
NONUPR not used if TYPE=SN
BIAXLWR Used only when MMTHD = AUTO. Lower, Middle, and Upper threshold ratios
BIAXMID used to check if the loading is proportional. This is used in combination with the
BIAXUPR non-proportionality factor thresholds.

For TYPE=EN:
BIAXLWR: (-1≤Real≤BIAXMID, Default = -0.6)
BIAXMID: (BIAXLWR≤Real≤BIAXUPR, Default = 0.25)
BIAXUPR: (BIAXMID≤Real≤1, Default = 0.6)

For TYPE=SN:
BIAXLWR: (-1≤Real≤0, Default = -0.6)
BIAXMID: Not used
BIAXUPR: (0<Real≤1, Default = 0.6)

Main Index
 FTGPARM 2065
Fatigue Parameters

Field Contents
ZERO Used only when MMTHD = AUTO. Stress range below which damage is assumed
zero and therefore no recalculation is performed. Specified as a percentage of UTS.
(0<Real≤100, Default=10.0).
GATE Used only when MMTHD = AUTO. This gate value is used to prevent small stresses
from adversely affecting the biaxiality calculation. Stresses below this value are not
included in the biaxiality calculation; their biaxiality ratio will be set to zero (0). The
value is set as a percentage of UTS. (0<Real≤100, Default=20.0).

Remarks:
1. FTGPARM bulk data will be 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. 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. PLAST can be set to NEUBER or SEEGER. Please note that NEUBER can be used universally
for uniaxial stress states. SEEGER requires a 2D stress state and is generally used when the stress
state in not purely uniaxial. PLAST is only valid for TYPE=EN.
4. If LOC=ELEMENT is selected, 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). If LOC=NODE is selected, the fatigue lives are calculated from the
stresses/strains at the element nodes. 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. Note that LOC=NODE is the same as LOC=SGAGE. The SGAGE, BILIN,
CUBIC, and CORNER values 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. ELEM is the
same as CENTER on the STRESS case control.
5. This RAINFLOW flag is only necessary to use if it desired to speed up the analysis for purposes
of quick critical location identification or for sanity checks. RTYPE determines how to compress
the input time history data for the purposes of speeding up the calculation, possibly at the loss of
accuracy of the results. RTYPE=FAST simply reduces the load time histories to a single cycle
using only the minimum and maximum from the input time series data, without losing phase
information across multiple load cases. RTYPE=LOAD using PCTRED performs a multi-
channel peak-valley extraction on the time series data prior to processing with PCTRED value set
as a percentage of the range of the input data. RTYPE=LOAD using GATE performs a multi-
channel peak-valley extraction on the time series data prior to processing with GATE value
applied directly in the units of the time series data.

Main Index
 2066 FTGPARM
Fatigue Parameters

6. 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.
7. 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 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. By definition the resulting life values will be the target life, thus
only the scale factor and maximum/minimum stress results are of interest when FOS is defined.
8. The static failure check has not had any validation in regards to spot welds and any prediction of
static failure should be treated with caution. Also, setting CHECK=0 or 1 (Warn or Stop) will
result in the S-N curve being adjusted in the low cycle region (< 1000 cycles) in the same way as
for the standard S-N method, as illustrated in the figure below. This is not desirable for spot weld
fatigue. It can be avoided, either by setting CHECK = -1 (recommended), or setting a value of the
UTS such that UTS*(1 - RR) = SRI1 or greater.

9. For fatigue analysis of spot and seam welds, besides the “SPOTW” and “SEAMW” lines
themselves, “RAINFLOW”, “CERTNTY”, and “FOS” are also applicable. “MULTI” is
applicable to seam weld, but not spot welds. All other are ignored. TYPE field is ignored as an
SN analysis is force 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. MMTHD=AUTO is not allowed for
fatigue analysis of seam welds.

Main Index
 FTGPARM 2067
Fatigue Parameters

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. For this reason, MIDDLE is set off by default to omit any fatigue calculation
on the middle sheets, which might otherwise 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 on 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. MMTHD=AUTO is not allowed in fatigue
analysis of seam welds (SEAMW). The stress/strain combination (COMB) is ignored if
MMTHD=AUTO because the program will determine whether to use a critical plane or absolute
maximum principal combination method.

Main Index
 2068 FTGPARM
Fatigue Parameters

Table 8-29 Allowable Values for the COMB Field *

Stress/Strain
Combination Valid for TYPE Meaning
ABSMAXPR SN (+SeamWeld), Absolute Maximum Principal (default)
EN
MAXPRINC SN Maximum Principal Stress
SGVON SN, EN Signed von Mises Stress
VONMIS SN von Mises Stress
SGMAXSHR SN, EN Signed Maximum Shear
MAXSHR SN Maximum Shear
CRITICAL SN (+Seam Weld), Critical Plane Analysis - every 10 degrees - Not valid for 3D solid
EN or CSHEAR elements - element must have an in-plane stress state.
STNDRD SN This is basically a critical plane analysis with calculations being
(Spot Weld only) done at NANGLEs around the circumference of the spot weld.

* The six multiaxial components defined by the stress tensor (or strain tensor) are resolved into one uni-
axial or combined value for fatigue calculations for each node or element for each time step. This is nec-
essary since the fatigue damage models used are based on theories which deal with uniaxial stress. These
stress scalar combinations can be any of the above. For S-N analysis, the signed von Mises (SGVON)
will be smaller than the Absolute 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 sign on the signed parameters is taken from the sign of the absolute maximum
principal value. It is necessary to sign these stress parameters, otherwise non-conservative fatigue life
estimates will result. It is therefore not recommended to use non-signed values (MAXPRINC, VONMIS,
MAXSHR), but the options are available and if using these, do not set the RTYPE=FAST on the ‘RAIN-
FLOW” line as this will result in no cyclic stress cycling.

Main Index
 FTGPARM 2069
Fatigue Parameters

Table 8-30 Allowable Values for the CORR Field

Mean Stress
Correction Valid for TYPE Meaning
NONE SN (+Spot/Seam Weld), No mean stress correction (default)
EN
GOODMAN SN Goodman mean stress correction
GERBER SN Gerber mean stress correction
GDMANT SN Tension only Goodman mean stress correction
GRBERT SN Tension only Gerber mean stress 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 Smith-Watson-Topper mean stress correction
MORROW EN Morrow mean stress correction

Main Index
 2070 FTGPARM
Fatigue Parameters

Table 8-31 Allowable S-N vs. Mean Stress Correction Methods

S-N Method
Mean Stress Multi Mean Multi R-
Correction Standard Curve Ratio Curve Haigh Bastenaire
NONE YES YES* YES† NO YES
GOODMAN YES YES* YES† NO YES
GERBER YES YES* YES† NO YES
GDMANT YES YES* YES† NO YES
GRBERT YES YES* YES† NO YES
FKM YES YES* YES† NO YES
SIMPLE‡ YES NO NO NO NO
INTERP NO YES YES YES 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.

Main Index
 FTGSEQ 2071
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.

Format:
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

Examples:

FTGSEQ 1
6 15

Field Contents
ID Unique ID with respect to all other FTGSEQ and FTGEVNT entries. (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.
METHOD 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.
FIDi ID of a FTGEVNT or another FTGSEQ entry for pseudo-static fatigue analysis using
SOL 101 or a modal analysis using SOL 103, or 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.
Ni 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.
"UNITS" Flag indicating that a fatigue equivalent unit name is applied to this loading. See
Remark 5. and 6.

Main Index
 2072 FTGSEQ
Fatigue Load Sequence

Field Contents
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.
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 8-32 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 of the sequence is equivalent to 5 times around
a test track, the equivalent unit name, EQNAM, might be "laps," and the equivalent unit, EQUIV,
would be 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.

Main Index
 FTGSEQ 2073
Fatigue Load Sequence

7. For duty cycle jobs, temporary DAC files are created. Use EVNTOUT=1 if you wish to keep the
files, otherwise they are deleted after the job terminates. 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.

Main Index
 2074 FTGSEQ
Fatigue Load Sequence

Table 8-32 Example of a 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:
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
 GBAG 2075
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

Field Contents Type Default

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 Integer > 0 No inflators
or more inflators on subsurface(s) of the GBAG surface.
HTRID Number of a set of HEATLOS entries, that defines the I>0 No heat
heat transfer definitions for the gas-bag surface and/or transfer
subsurfaces.

Main Index
 2076 GBAG
Gas-Bag Pressure Definition

Field Contents Type Default

INTID ID of an INITGAS entry specifying the initial gas I>0 No initial gas
composition for this GBAG. composition
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

Main Index
 GBAG 2077
Gas-Bag Pressure Definition

where, P init the initial pressure, V the volume, R the gas constant, and T init the initial gas
temperature.
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 -⋅Q
m· out = ρ ⋅ Q = ----------
R⋅T
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
 2078 GBAGCOU
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

Field Contents Type Default

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 Real > 0 0.0
switch 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
 GENEL 2079
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

Main Index
 2080 GENEL
General Element

Field Contents
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)
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”, and [Z], 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
{ ui } = [ u i1, u i2, …, u im ]

Main Index
 GENEL 2081
General Element

T
{ ud } = [ u d1, u d2, …, u dn ]
[ KZ ] =
KZ11 … … …
KZ21 KZ22 … …
T
[ K ] or [ Z ] = KZ31 KZ32 … … and [ KZ ] = [ KZ ]

KZ m1 … … KZ mm

[S] =
S11 … S 1n
S21 … …
S31 … …

S m1 … S mn

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 the 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
 2082 GENUDS
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
GENUDS SRV_ID
“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

Field Contents
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
 GMBC 2083
General Enforced Displacement Definition

GMBC General Enforced Displacement Definition

Defines enforced displacements for GRID, FEEDGE, GMCURV, FEFACE, and GMSURF entries.

Format:

1 2 3 4 5 6 7 8 9 10
GMBC LID SPCID C ENTITY ID METHOD FIELD1 FIELD2
FIELD3 FIELD4 -etc.-

Example:

GMBC 127 1 2 GMCURV 1 QUAD 1. 2.

1.0

Field Contents Type Default

LID LOAD set identification number. Integer > 0 Required
See Remark 2.
SPCID SPC set identification number. See Remark 2. Integer > 0 Required
C Component number in the output coordinate 0 < Integer < 6 Required
system (global). See Remarks 3. and 4.
ENTITY Entity that the enforced displacement Character Required
is applied to (Specify GRID, FEEDGE,
GMCURV, FEFACE, or GMSURF).
See Remarks.
ID ID of the entity selected above. See Remarks. Integer > 0 Required
METHOD Method used to supply the data (EQUATION or Character Remark
TABLE, CONSTANT, LINEAR, QUAD,
CUBIC). See Remarks.
FIELDi Enforced displacement data. See Remarks. Integer or Real Required

Remarks:
1. GMBC is the recommended entry for specifying boundary conditions and must be selected with
Case Control command SPC = SPCID.
2. LID and SPCID refer to Case Control commands for specifying loads and boundary conditions.
Whenever there are several nonzero enforced motion vectors supplied, the most efficient
processing of the data (single decomposition of the stiffness matrix) is accomplished by
specifying both LID and SPCID.

Main Index
 2084 GMBC
General Enforced Displacement Definition

LID Result
>0 Generate SPC entries with zero displacements and SPCD entries with non-zero
displacements.
0 Generate SPC entries with non-zero displacements only

3. The components of motion specified by C (field 4) of all degrees-of-freedom in the output

coordinate system (Global System) associated with an entity will be constrained.
4. If C = 0 is specified then the degrees-of-freedom will be taken out of the constraint set. In this
case the method field is not required.
5. The component is a single integer (1 or 2 or 3 etc.). Use multiple GMBC entries to enforce
constraints on multiple components.
6. If METHOD = “EQUATION”, “TABLE”, or “CONSTANT” then FIELD1 is:

METHOD FIELD1 Type

EQUATION ID of a DEQATN entry defining the displacement value Integer > 0
as a function of location
TABLE ID of a TABLE3D entry defining the displacement value Integer > 0
as a function of location
CONSTANT Value of enforced displacement Real

7. When METHOD = CONSTANT, a constant displacement is specified for the FEEDGE,

GMCURV, FEFACE, and GMSURF entities.
8. If ENTITY = “FEEDGE” the METHOD field can be used to specify, linear, quadratic, and cubic
displacements. FIELD1 and FIELD2 correspond to GRID1 and GRID2 on the FEEDGE entry.
The values in FIELD3 and FIELD4 are:

Applying Linear, Quadratic, and Cubic Displacements to an FEEDGE

METHOD FIELD3 FIELD4
LINEAR blank blank
QUAD Value at 1/2 chord length blank
CUBIC Value at 1/3 chord length Value at 2/3 chord length

9. If ENTITY = “FEFACE” the METHOD field specifies linear or quadratic displacements. The
values of FIELDi are location specific:
• Quadrilateral FEFACE

Main Index
 GMBC 2085
General Enforced Displacement Definition

FIELD5
FIELD1 through through Displacement
METHOD FIELD4 FIELD8 FIELD9 Function
LINEAR Value at GRID1, 2, 3, 4 blank blank Linear
QUAD Value at GRID1, 2, 3, 4 Value at mid side Value at middle Quadratic
of EDGE1, 2, 3, 4 of FEFACE

• Triangular FEFACE

Displacement
METHOD FIELD1 through FIELD3 FIELD4 through FIELD6 Function
LINEAR Value at GRID1, 2, 3 blank Linear
QUAD Value at GRID1, 2, 3 Value at mid side of EDGE1, 2, Quadratic
3

10. In general, the hierarchy set to resolve the conflicts arising in the enforced displacement input
data is: GRIDs followed by FEEDGEs followed by GMCURVs followed by FEFACEs followed
by GMSURFs. This means that:
• In general the program does not allow the user to supply multiple values of enforced
displacements for the same component (C).
• Displacement values specified for each component of a given GMSURF entry are applied to
the same component of all GRID, FEEDGE, and FEFACE degrees-of-freedom that lie within
the GMSURF.
• Displacement values specified for each component of different GMSURF entries are
averaged and applied to the same component of all GRID, FEEDGE degrees-of-freedom that
are shared by (that are common to) the multiple GMSURFs.
• Displacement values specified for a given FEFACE entry are applied to all GRID, FEEDGE,
and FEFACE degrees-of-freedom that lie within the FEFACE. This data overrides the data
that is specified for all the components of the given GRID, FEEDGE and FEFACE degrees-
of-freedom that lie within the FEFACE by using GMSURF entries.
• Displacement values specified for each component of different FEFACE entries are averaged
and applied to the same component of all GRID, FEEDGE degrees-of-freedom that are shared
by (that are common to) the multiple FEFACEs. This data overrides the data that is specified
for all the components of the given FEEDGE and GRIDs by using GMSURF entries.
• Displacement values specified for each component of a given GMCURV entry are applied to
the same component of all GRID, FEEDGE, degrees-of-freedom that lie within the
GMCURV. This data overrides the data for all the components that are specified for the given
FEEDGE and GRIDs by using GMSURF or FEFACE entries.

Main Index
 2086 GMBC
General Enforced Displacement Definition

• Displacement values specified for each component of different GMCURV entries are
averaged and applied to the same component of all GRID degrees-of-freedom that are shared
by (that are common to) the multiple GMCURVs. This data overrides the data for all the
components that are specified for the given GRIDs by using GMSURF or FEFACE entries.
• Displacement values specified for each component of a given FEEDGE entry are applied to
the same component of all GRID, FEEDGE, degrees-of-freedom that lie within the FEEDGE.
This data overrides the data for all the components that is specified for the given FEEDGE and
GRIDs by using GMCURV or FEFACE or GMSURF entries.
• Displacement values specified for each component of different FEEDGE entries are averaged
and applied to the same component of all GRID degrees-of-freedom that are shared by (that
are common to) the multiple FEEDGEs. This data overrides the data for all the components
that are specified for the given GRIDs by using GMCURV or FEFACE or GMSURF entries.
• Grids have the highest priority, i.e., any value/property specified using a GRID entry overrides
all other information associated with that GRID. If multiple entries are used for a given GRID,
e.g., multiple SPCs, then the existing rules govern (SPCs are combined, FORCE is added,
SPCDs for the same component are not allowed).
• It is important to recall that these displacements are assumed to be in the Global Coordinate
System and that the interconsistency of the output coordinate systems of the various GRIDs,
FEEDGEs, FEFACEs is not checked.
• If an entity is specified on both a GMBC and GMSPC entry then the GMSPC specification
will be ignored.

Main Index
 GMBC 2087
General Enforced Displacement Definition

11. For the example in Figure 8-102,

GRID

FEEDGE

GMCURV 1000 GMCURV

GMSURF 30
FEFACE

GMSURF 40

FEFACE 100 FEEDGE

3000

FEFACE 200
FEEDGE
1000 FEFACE 300
GRID 100000

GMSURF 10 GMCURV 2000

FEFACE 400
GMSURF 20

Figure 8-102 Use of Multiple Surface and Curves

Main Index
 2088 GMBC
General Enforced Displacement Definition

• The enforced displacement for GRID 100000 can be specified using SPCD, GMBC referring
to an FEEDGE, GMBC referring to a GMCURV, GMBC referring to a FEFACE, and GMBC
referring to a GMSURF. Table 8-33 describes the outcome of using these different methods:

Table 8-33 Enforced Displacement Used for GRID 10000

When Specified
Using Action
SPCD Overrides all other information supplied for all components.
Single GMBC Overrides information supplied for all components using
(FEEDGE) GMBC(GMCURV) GMBC(FEFACE), GMBC(GMSURF) entries.
Multiple GMBC Values are averag